How to get HTTP log for the message sent from PI

[Former Member]

Dear Experts,

We have B2B scenario with one of our Customer, we have sent them messages and out of them few are not received by Customers. The messages are sent by HTTP Receiver adapter. In sxmb_moni, it is showing all the messages sent successfully.

We want more log to show that the HTTP message is succesfully sent to Customer, please let us know where we can find it.

thanks and regards,

Ravi Siddam

[bhavesh_kantilal]

Ravi,

Also, the fact that the HTTP message is successful in XI means that the message was sent to the Target System. HTTP messages even though Asynch internally request for a HTTP 200 OK and if this is not returned message fails / timeouts in XI.

Unfortunately there is no easy way to prove this in case where the partners say they did not received the message. This is exactly why connectivity protocols like AS2 are used a in a B2B flow as they provide options like Non-Repudiation ( of Origin & Content ) using MDNs so that such issues do not occur. As far as I know, plain HTTP does not support such options and I would suggest you look at alternates such as this to avoid these kind of issues.

Regards,

Bhavesh

[Former Member]

thanks Bhavesh for your very helpful reply.

we would like to know when Async processing is completed successfully as per HTTP 200 OK code. where in XI logs we can find the HTTP 200 OK code received from the Partner for the message.

thanks and regards,

Ravi Siddam

[Former Member]

Dear Ravi

No logs available in RWB for http apart from sxmb_moni.

But you can get some clue in txn smicm -> Trace File-> Display End.

Also increase the trace level to get more details.

Regards

Monika

[bhavesh_kantilal]

Not sure if this is persisted anywhere. I doubt if such a correlation can be done for Asynchronous messages.

Normally as this HTTP 200 OK is provided in the same connection session, if the message fails, it normally marks it as failed in XI.

Worth a check on Service Market place as well. Let me know your findings.

Regards

Bhavesh

[Former Member]

Thanks Monika,

we haven't got any clue in ICM, it dosen't have message-id link in ICM trace.

and such cases happens once in 15-20 days, difficult to increase the trace level for such a long time, what do you suggest?

thanks and regards,

Ravi

[Former Member]

Thanks Bhavesh,

we will update the thread if found any useful.

regards,

Ravi Siddam

[prateek]

Ravi, you may try to use the tool TCPGateway (can be searched on SCN) to trace the HTTP call. This trace then can be shown to the partner.

Regards,

Prateek Raj Srivastava

[Former Member]

Hi,

Go to rwb message monitoring and select adapter engine database. There again you need to check for the status "to be delivered" or "holding" if any exists.

If they exists, you need to reprocess/cancel them. let us know the result after performing this check.

Check this blog for details

http://scn.sap.com/people/riyaz.sayyad/blog/2006/04/27/enhanced-message-monitoring-using-runtime-wor...

Regards,

Venkata S Pagolu.

[Former Member]

Hi Venkata,

Please note the message is not going to Adapter engine as it is using HTTP adapter for sending the message.

regards.

Ravi

[rajasekhar_reddy14]

If your third party system people claiming messages were not receiver then check HTTP destination in SM59.

[Former Member]

Hello,

destination is working fine. out of 100, only 1 or 2 messages are not received by them, according to sxmb_moni log it is sent successfully.

regards,

Ravi

[Former Member]

Hi,

Check it in NWA---> log viewer--> General--->Java trace

Regards,

Venkata S Pagolu

[Former Member]

Thanks for reply Venkata,

We have our Gateway system on PI7.0 only. NWA is not available.

Please note that the Java Stack is not coming in picture while sending the HTTP message using HTTP Receiver adapter.

Please help.

regards,

Ravi Siddam

[Former Member]

you can check the Message Monitoring -> Adapter Engine in Runtime Workbench

[Former Member]

Please note the message is sent to Partner using HTTP Receiver adapeter, it is not going through Adapter Engine.

thanks and regards,

Ravi