cancel
Showing results for 
Search instead for 
Did you mean: 

Axis Adapter - Missing payload

Former Member
0 Kudos

Hi All,

I am trying to get a scenario working with the Axis adapter - however when i call the target webservice I get this returned.

In sxmb_moni i just see the manifest and not the actual payload. Anyone have any ideas ?

- <SOAP:Body>

- <SAP:Manifest wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

- <SAP:Payload xlink:href="cid:308E4A333681386D76223BF119149599">

<SAP:Name>document-0</SAP:Name>

<SAP:Description>unspecified document</SAP:Description>

<SAP:Type>Application</SAP:Type>

</SAP:Payload>

</SAP:Manifest>

</SOAP:Body>

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

I am having the same issue, the AXIS adapter seems to be putting the desired payload into document-0 rather than MainDocument and it seems the PROXY requires the MainDocument to relate the data response. Did you find a solution to getting document-0 to map to MainDocument?

Former Member
0 Kudos

There are some XI Parameters in the SOAP adapter for payload extraction, did you try the different settings like "Payload Body Child" or "SOAP Envelope"?

iaki_vila
Active Contributor
0 Kudos

HI Jon Vaughan ,

Have you tried to find your message in the runtime workbench - message monitoring?

Regards.