on 09-24-2012 4:49 PM
Hello All,
I am doing a synchronous soap-> PI -> soap scenario, my scenario is completed (and tested also). Now i have a requirement to catch application errors (in receiver system) as well as system error (which takes places while routing a message to receiver system due to mapping failure, receiver system is down etc) and inform back the sender application.
Please let me know how to achieve above requirement.
Regards
Vasant
You can request SOAP system team to capture errors from their and send back to source application as part of response message.
capturing PI side errors you need to go for BPM and use control step.
meanwhile implement alert frame work also.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Since you consume webservice, only if the target system supports capturing fault message due to application errors, you can use them. Basically your wsdl will have request, response and fault messages. You can use their fault messages to retrieve the application error messages.
You might want to check these links for your questions
http://scn.sap.com/people/alessandro.guarneri/blog/2011/01/10/soap-fault-in-sap-pi-hijack-it
Hi Baskar,
Thanks.
So, if my receiver application provides Fault Message (and at the same time if my sender application is able to except that FM response) then i can use it and if not then the receiver system has to provide the application error message in the original response structure??
I guess, this will be possible in my scenario.
But my main concern is the system errors, like sync call failed due to mapping error, connectivity issues etc. I want to handle those exceptions also?
What message my sender application will get if the message failed due to connectivity issues (and there are no error handling built, just based upon your experience you can share your opinion?)
Regards!!
Yes. For application errors you can handle via fault message provided the target system supports it. If not, if the target system handles the application errors messages they can even create a seperate field in the response mesg structure and send it over there. For system errors,you need to use BPM to capture the message and forward to the sender system. in addition you can use alert framework for the failed messages as Raja already mentioned
Hi Raj,
My client is very much specific about the error handling specifically realted to connectivity issues.
I will try for BPM option, but could you please tell me what needs to be done in the exception branch?
Customer wants that if something fails then a custom message needs to be dipslayed on the sender Web UI application (which is actually triggering the synchronous message).
Regards!!
Hi Vasant,
A few cents to Raj, i'd rather using alert configuration, more easier than to develop a BPM and you could catch some internal PI error, even to send emails, but obviously no synchronous response is generated for the call.
For alert configuration check this step by step guide: http://scn.sap.com/docs/DOC-3804
For example in this Michal Krawczyk's blog you have how to set up alerts for message mappings errors: http://scn.sap.com/community/pi-and-soa-middleware/blog/2005/09/09/xi-alerts--step-by-step
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
92 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.