SOAP Sender Error - com.sap.engine.interfaces.messaging.api.exception

[Former Member]

Hi,

I am testing a SOAP Sender Channel using a SOAP Client and getting the following error. I have read almost all the posts related to errors in SOAP Channel and also have checked my URL which is correct. AS mentioned in many of the posts, my url goes like

https://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:DEMO:SOAP_s_GETLIST&version=3.0&SenderSe...;

This is the error that I get when sending a message to the interface

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP:Body>

<SOAP:Fault>

<faultcode>SOAP:Server</faultcode>

<faultstring>Server Error</faultstring>

<detail>

<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">

<context>XIAdapter</context>

<code>ADAPTER.JAVA_EXCEPTION</code>

<text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIProxy:PARSE_APPLICATION_DATA:

at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1041)

at sun.reflect.GeneratedMethodAccessor1044_10001.invoke(Unknown Source)*

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)

</s:SystemError>

</detail>

</SOAP:Fault>

</SOAP:Body>

</SOAP:Envelope>

Has Anybody got this problem before? Is it any problem with the SOAP Adapter itself or with the data that is going in the message? If so, What is the possible solution for this?

Thanks,

Rashmi.

[Former Member]

try using:

/XISOAPAdapter/MessageServlet?channel=:DEMO:SOAP_s_GETLIST:<communication channel name"

[Former Member]

Hi Horia,

Thanks for the reply.

Yes, I have used the url in that format only. Sorry if there was any confusion.

The Sender Service Name is DEMO and the comm channel name is SOAP_s_GETLIST. Theres no party here. So I have left that blank.

https://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:DEMO:SOAP_s_GETLIST&version=3.0&SenderSe...;

The messages are reaching the communication channel. In the communication channel monitoring I can see that the message was received by the channel but it was not further processed by the SOAP Adapter and so no message got into PI server.

Thanks,

Rashmi.

[former_member200962]

The URL format is still wrong...use the below format:

https://<IPAddress OR ServerName>:<PORT_No>/XISOAPAdapter/MessageServlet?channel=:<SenderBusinessService>:<SenderSOAPCC>&version=3.0&Sender.Service=<SenderBusinessService>&Interface=<SenderInterfaceNamespace>%5E<SenderMI>

Or you can also use

https://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel

[Former Member]

Hi Abhishek,

Thanks for that. Well, Just tried with the url format

https://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel

but still getting the same unsuccessful result.

I have a doubt, when the message is able to reach the communication channel on the PI server, isnt it that the URL is correct? Becasue as I already mentioned, I am able to see this error on the communication channel monitoring for that particular comm channel. Only that the message is not generated as the adapter is not getting invoked.

Please let know if I am right or wrong in my understanding.

Thanks

Rashmi.

[Shabarish_Nair]

using SOAP UI or any other test tool, validate that your request complies with the WSDL structure.

There is possibility that the parse error is coming due to incorrect request data.

[Former Member]

Hi Rashmi,

I also think your problem is data related.

Check the response in your SAP PI message monitor (SXMB_MONI) when you trigger a request using SoapUI. It sometimes provides a bit more detail. You design (data types, message types, service interfaces etc.) was done in SAP PI 7 then an Abap Proxy was generated from the service interface?

Sometimes there is an issue between the XSD data type declaration in SAP PI and the conversion to Abap data types that takes place when a proxy is generated from a PI Service Interface.

Check the data that you pass in your request, especially those like datetime fields. Maybe even change some of the data type definitions (like datetime) to a string (request & response) & then test through SoapUI & see if you still get the error. Then you can work out how to best resolve it.

Best Regards, Trevor