Soap receiver status in sxmb_moni

[sunit_s]

Hi All

I am using SOAP receiver adapter to send message to our partner. Its an asynchronous EO scenario.

It works fine and the partner (receiver system) receives the message correctly.

But while testing we discovered a situation.

Whenever partner's receiver server is switched off, tcode sxmb_moni shows that message is 'Processed Successfully' in status column. I was expecting it to show an error as server was not reachable. In Runtime Workbench, it does show an error that connection was refused in receiver channel monitor.

Why does sxmb_moni show status as 'successfully processed' when it did not reach the receiver even though runtime workbench shows an error in receiver channel. I am sure http adapter would not do that as it show http error codes like 500, etc in response and marks the message with error status. Is there something wrong with SAP PI 7.1 SOAP adapter.

Please assist.

Regards

Sunny

[suman_saha · Accepted solution]

Hi,

SXMB_MONI is the log for the pipeline steps executed in Integration Engine. As the message is processed successfully in IE and delivered to Adapter Engine, the message is showing successfully processed in SXMB_MONI. With respect to IE, there is no error.

When the message is received in Adapter Engine, it tries to send the data to Web service which is throwing error. So you can find the error in Message Monitoring -> Adapter Engine or in Communication Channel monitoring.

Suman

[Muniyappan]

it works as you said for http because http adapter resides in integration engine.

you can not expect the same as soap adapter is in adapter engine. so it will show successful in sxmb_moni.

[Former Member]

Hi Sunit,

Dual stack PI system runs on two stacks JAVA and ABAP stack.

SXMB_MONI always shows the ABAP stack related message process status, in the same manner JAVA stack shows the JAVA stack message process status. Please go through below link for dual stack architecture.

Architecture (SAP NetWeaver PI Dual-Stack) - SAP NetWeaver Process Integration - SAP Library

>>>Why does sxmb_moni show status as 'successfully processed' when it did not reach the receiver even though runtime workbench shows an error in receiver channel. I am sure http adapter would not do that as it show http error codes like 500, etc in response and marks the message with error status. Is there something wrong with SAP PI 7.1 SOAP adapter

SOAP adapter developed based on JAVA stack so SOAP messages pass through JAVA stack. If any error caught at adapter engine during message processing Adapter engine shows error status. In your case message successfully processed from ABAP stack(Integration Engine) to JAVA stack (Adapter Engine) so it is showing success status in SXMB_MONI and error status Adapter engine since error encountered in JAVA stack. Coming to HTTP Adapter, HTTP adapter lies in ABAP stack so HTTP related errors caught in Integration Engine itself. That is why HTTP messages show error status in SXMB_MONI.

>>>Is there something wrong with SAP PI 7.1 SOAP adapter.

There is nothing wrong with SAP PI 7.1 SOAP adapter.

I hope this is clear for you.

Thanks,

Krupa

[former_member192343]

Hi,

Maybe http adapter shows you 500 error becouse it is synchronous?

And your scenario is async, and Integration Engine successfuly sends message to adapter.... sxmb_moni does not show adapter log.