PI 7.1 SOAP Adapter - Message Payload for Failed Messages - Where to find

[Former Member]

We are exposing a webservice through SAP PI. Occassionaly we have customers calling our webservice and some failure occurs. The error is usually the way that the customer is calling the webservice (missing elements, misnamed tags, bad content in the WS payload..). Generally in these cases we can see the error in communication channel monitoring.

Here is an example:

12/12/11 4:39:07 PM com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: cvc-complex-type.2.4.b: The content of element 'SupplierInvoice' is not complete. One of '{"":Invoice}' is expected. at line 1, column 227

12/12/11 4:39:06 PM request received for a channel

I understand the issue, but it would be extremely helpful to have the full SOAP Envelope and Payload of a request when it fails. The communication channel will show a SUCESSFUL message payload with a link to it. But it does not show a failed one.

Where can I find the FAILED payload that accompanies this message? These failures occurs before any mapping or being seen in RTWB Adapter Engine message monitoring... I did some searching around, but did not find anything offhand. I would greatly appreciate any pointers from anyone who has crossed this bridge.

[Former Member · Accepted solution]

Hi,

When the web service is being called by external application, the first point of contact would be the sender communication channel which converts the SOAP message into XML message and pass to integration engine ( In case of success )

But if the web service call fails due to WSDL validation, Authentication issue, Bad content, invalid content type, you would not see the payload in the sender communication channel or in Adapter engine. You can just see error message in the sender communication channel . I have experienced this many times and i always ask the web service team to provide the SOAP message for validation/investigation purpose.

[Former Member]

Baskar - These are SOAP failures that occur before Moni...

Rajesh - I see that you have felt my pain here. So far I have been asking the caller of our WS to send us their payload. This typically get us to a resolution of the issue. However, I am working through a case now where a WS user is sending us what appears to be a perfect SOAP message, but we are getting the error on the CC. There appears to be some discrepancy between what has been sent to me as SOAP Payload via email and what PI is processing. Having the payload of the SOAP message would be very helpful in this case.

[baskar_gopalakrishnan2]

SXMB_MONI: See it in pipeline steps even before message mapping. you can see the payload and errors in the main document section. Also you can see in RWB / message monitoring and pick adapter engine and check message errors and content payload.