XI SOAP receiver adapter. Java and decentral adapter engine.

[Former Member]

Hi,

I would like to send the below to a web service... have done a custom mapping to

produce the entire message below, and turned off Use SOAP envelope option in the

receiver adapter.

Can anyone point me in the right direction (in terms of the correct why to go about this)

or to why it is not working? Because I see it in the payload option of the message fine (in RWB).

Can java mapping be used to build the entire message?

<SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:noNamespaceSchemaLocation=" EnvelopeStructure.xsd">

<SOAP-ENV:Header>

<Q-ENV:Header>

<Q-ENV:Sender-Id>a03430170001</Q-ENV:Sender-Id>

<Q-ENV:Receiver-Id>1aa1150001</Q-ENV:Receiver-Id>

<Q-ENV:Correlation-Id>1231201109096878</Q-ENV:Correlation-Id>

<Q-ENV:Message-Id>M1231201109096878</Q-ENV:Message-Id>

<Q-ENV:Date-Sent>26 Apr 2004 18:01:08 CDT</Q-ENV:Date-Sent>

<Q-ENV:Document-Type>RequestForQuotation</Q-ENV:Document-Type>

<Q-ENV:Message-Format>Q 1.0</Q-ENV:Message-Format>

</Q-ENV:Header>

</SOAP-ENV:Header>

<SOAP-ENV:Body>

<Q-ENV:Body>

<Q-ENV:Content-Type>text/xml</Q-ENV:Content-Type>

<Q-ENV:Message-Type>xCBL</Q-ENV:Message-Type>

<Q-ENV:Encoding>UTF-8</Q-ENV:Encoding>

<Q-ENV:Message-Body>

blah blah

</Q-ENV:Message-Body>

</Q-ENV:Body>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

thanks

Dylan.

[stefan_grube · Accepted solution]

Sure, you can create your SOAP envelope with mapping by your own.

Sometimes you have an issue with the content type, which is automatically set to application/xml which is not accepted by all webservices. In this case you need the MessageTransformBean to set the content type to text/xml. See online help for MessageTransformBean.

Couls you let us know, what error happens when you test your scenario?

Regards

Stefan

[Former Member · Accepted solution]

I am getting various errors, because I am not sure I understand how this adapter works exactly.

I would like to send a custom SOAP message.

I use a java mapping to create the entire soap message...

In the soap adapter I turn on "Do not Use SOAP envelope".

What should the final message sent out of the SOAP adapter look like ? Will a standard SOAP

envelope be added around it anyway?

Do I need to add beans after the XISoapAdapter bean in order to remove the soap envelope?

How do the modules work? Is there a good resource on the subject?

[stefan_grube · Accepted solution]

Without knowing the exact error, it is hadr to give any advice.

I cannot see anything wrong in the structure you provided.

Maybe you find anything useful in this guide:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f...

Regards

Stefan

[Former Member · Accepted solution]

Hi All,

There was no error as such. The webservice receiving the request was unable to read the

resulting payload.

I found the solution with SAP Note 779981 - Changing content type in mapping.

Here I was able to specify the content type as "Application/x-www-urlencoded" which

then allowed the webservice to correctly read the payload.

Specifying the parameter XMLEncoding for bean XISOAPAdapter did not work for me.

thanks,

Dylan.

[stefan_grube · Accepted solution]

The note is interesting.

But it is easier to change the content type with the MessageTransformBean.

Regards

Stefan

[Former Member]

See last post

[Former Member]

hey, can you please reframe your issue?