Skip to Content
author's profile photo Former Member
Former Member

SOAP Adapter with protocol XI 3.0 and adapter modules


we have developed an adapter module to base64 decode and unzip the contents of an xml tag. We have successfully tested it with a soap sender channel using native soap protocol.

When trying to use it in a scenario ERP Proxy -> PI Soap Adapter (configured to expect XI 3.0 protocol) we encounter the following problem:

The payload of the message is (in the module you get the payload with message.getMainPayload().getContent() ):

<sap:Manifest xmlns:SOAP='' xmlns:sap='' xmlns:xlink='' xmlns:wsu='' wsu:Id='wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7'>
	<sap:Payload xlink:type='simple' xlink:href='cid:payload-4DAE8AFC5C960461E10080000A03112B @'>

If you look at a message in XI 3.0 format this is the part that is found in the tag <SOAP:Body>. So it seams that for the adapter module the message is treated as a normal soap message and the soap body is treated as payload.

We have tried to get the real payload (which is an attachment in the message) with message.getAttachment(String name) but getAttachmentIterator() returned an iterator pointing to an empty list.

Any ideas what could be wrong or how to remedy the problem?

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on May 09, 2011 at 07:29 AM

    I think this was due to the checkbox for "Do Not Use SOAP Envelope" which was checked but did not have an effect. This probably happened because of a cash refresh problem.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.