Issues and solutions of SOAP Messages in XI
There are lots of weblog that speak about how to integrate existing applications with web sevices via XI. In this weblog I will discuss some of the issues that I came across while dealing with a similar kind of scenario.
The steps for developing this scenario can be found in the following weblog “Invoke Webservices using SAPXI”
This error occurs when web service does not understand the message sent to it as it expects the message in TEXT/HTML and the message is sent in Application/HTML.
For this in the module tab of the receiver communication channel ‘localejbs/AF_Modules/MessageTransformBean’ module needs to be entered before the existing XISOAPAdapterBean.
This error occurs when proper network access username and password are not maintained in the receiver communication channel.
This error occurs when the conversion parameter ‘Do Not Use SOAP Envelope’ is checked.
Due to this parameter the SOPAP Adapter does not embed the message in a SOAP Envelope. Hence the message is not understood by the Receiving Web Service.
This parameter should be set only if the message is already in the SOAP format.
This error occurs when proper Interface namespace or interface name is not maintained in the sender communication channel
The namespace mentioned here should be the proper namespace of the scenario in the Integration Repository.