on 04-04-2006 10:15 AM
Configured BPM and now learning Error Handling. I know that through BPM we can handle system Errors, but I doubt whether Mapping error is a system error.
I am interested to know the classification of errors with examples, preferably listing out all types of errors.
Please provide some weblogs or explain briefly how to handle system and application errors through BPM.
Thanks,
Raja
Hi Raja,
This can be easily done by configuring your alerts. When you configure the same, you can define your alert rules, RWB->Alert Configuration->alert rule, here you have the option of choosing adapter engine/integration engine which indicates where the error occured and hence you could restrict what error you exactly want to receive, for example say mapping error. You can also specify the adapter type and error category here.
Regards,
Chandra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raja,
One way to handle errors in Xi is to use ALERTS.
Just refer to this blog, to configure ALERTS and to use them in your BPM,
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
/people/michal.krawczyk2/blog/2005/03/13/alerts-with-variables-from-the-messages-payload-xi--updated
Also, if you are on SP14 or above, check the note 913858, 870232.
Regards,
Bhavesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raja,
SAp generates error for Adapter framework, Adapter Engine, Message mapping etc. Now these errors can be because of system failure, incorrect data or error in the application (Java mapping etc).
All these errors can be captured with the help of Alert framework.
So all you have to do is configure your alert framework and then you can either raise alerts, send mail etc.
Info on Alert framework:
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/content.htm
Regards
Vijaya
Hi Raja,
By using Alerts, you can trap the Adapter Framwework errors also and you do not need to configure CCMS for the same.
Since Sp14, Xi Alerting has been made independent of the Activation of End to End Monitoring.
So , define your Alert category, your Alert Rule and if you are on SP14 and above, then that will trigger your Alerts for the errors occuring in your XI.
if below Sp14, look at this blog also,
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
Regards,
Bhavesh
Hi Raja,
You will need CCMS if you want to send the Alerts to external system or you want to access the ALerts from the transaction. You can capture your alerts without this also.
When you go to Alert Configuration in the Runtime Workbench you can see Create Alert Rules. These rules are pertaining to the error generated in your AF,AE or IE.
Once you have completed the whole config. The error happening in the AE, IE or AF would trigger the alert. you can see this in your Alert Inbox.
The best would be if you go through the URL I have mentioned below.
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/content.htm
You have to use BPM only if you want to do an activity after the alerts are raised.
Regards
Vijaya
Message was edited by: vijaya kumari
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.