Showing results for 
Search instead for 
Did you mean: 

Message as link in SOAP body instead of inline

Former Member
0 Kudos

Hi all!

We have a problem with the XI SOAP Adapter invoking a web service on an external system.

The SOAP message received from the external system contains something like an external link in the SOAP BODY.

The message is therefore parsed incorrectly.

Is it possible to configure the adapter to save the message inline in the soap body?

Thank you in advance.

Gianluca Collot

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

HI Naveen,

i'm working with Gianluca. The legacy system is not able to parse the SOAP message, because it can't found the payload data. In the body part of messagge, infact, there is the following tag with a link to the effective payload, sent in attachment (i think).

In the Adapter engine monitor, looking the details of the sent message, i found 2 visualization: the main message (with envelop, header and body) and the payload (with message data).

Does someone know how to put payload directly in the body?

Thankyou in advance,


--------------  Main part:

<SOAP:Envelope xmlns:SOAP="">
  <SOAP:Header xmlns:xlink="" xmlns:SAP="" xmlns:wsse="">
    <sap:Manifest xmlns:sap="" xmlns:xlink="" xmlns:wsu="" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
      <sap:Payload xlink:type="simple" xlink:href="">
        <sap:Description /> 

--------------- Message part: (

<?xml version="1.0" encoding="UTF-8" ?> 
<ns20:Messaggio xmlns:ns20="urn:testnamespace_XI_2_WBI-interface">
  <Testo>Test of message</Testo> 

Former Member
0 Kudos


can you post more information as to what error you are getting. contents of the soap message will be very helpful to see what the problem is?