error handling in Proxy - Async scenarios

[former_member474221]

Hi,

For async scneraios....if there is an exception in proxy ....how do we monitor / notify the error ( Do we create a Z table/raise mails ?? or can we create alerts in SAP as well ?? )

I understand that we can raise fault messages but that will be visible only in the receiver SAP system. What is the use of that?

[former_member184681 · Accepted solution]

Hi Hema,

If I got your requirement correctly, you mean the receiver proxy (server proxy; sending from PI to ECC over proxy) in async mode, is that right? If so, you have at least two options there:

1. Use acknowledgements mechanism. ECC receiver can send the ack for each message, that PI can return to the sender system. And it is up to the sender system, to iterpret the ack correctly (notify users and so on).

2. In the server proxy processing, you have some implementing class that can do error handling for you. For instance, in case of any errors, you could write details to standard system log (slg1) or notify your users in any other way. I mean, you can not only raise the error message to the proxy (visible in sxi_monitor of receiver ECC), but also add some "application" error handling.

Regards,

Greg

[former_member474221 · Accepted solution]

1. then the use of fault msg in File to Proxy scenario is only to show the error description in SXMB_MONI right ???

2. How can a file sender accept ack coming from proxy ??

3. Also in case of Proxy to File scenario...what if an exception is caught in the sender ( for connectiivty issues between SAP and PI ) what is typically done in this case??

[former_member184681 · Accepted solution]

#1, 2: This was more like a general remark. In case of File to Proxy you are right that this doesn't help a lot. Still, you could use a sync proxy and the RequestResponseBean on the sender file side. This way, you could produce an error details file for each file that was processed incorrectly, based on the proxy's response.

#3: It depends on your scenario and requirements. In many of my scenarios I write some more details to the slg1 log, but you could send e-mail notifications or start some workflow as well. Also, bear in mind that in sync scenarios, some errors are simply handled by the message being put in a queue for automatical reprocessing.

Regards,

Greg

[baskar_gopalakrishnan2]

There is an another different approach. Again it is purely based on your requirement.  You can create sync outbound and inbound interface.  Whereas in the sender adapter you quality of service is EO or EOIO. This way the receiver proxy sends the error messages using fault message type. But since sender system is async you ignore the response. But you will see the response message in the monitoring section of target message.

you might want to look at this approach

http://scn.sap.com/community/icc/integration-scenario-pi/blog/2011/03/07/unleash-synchronous-scenari...

[rajasekhar_reddy14]

Hi,

The best way to handle (as per my exp)Proxy errors(connectivty and Proxy execution) is handling ECC,server proxy case use Fault message type.

Regards,

Raj

[Former Member]

Hi,

Look at this topic http://scn.sap.com/thread/3154560

or this one http://scn.sap.com/thread/180717

Hope this will help you