Error Handling in XI3

[Former Member]

Hi all,

I am new to XI. Can anyone guide me how to handle error in XI. To elaborate more, if we use asynchronous or syncronous scenarios and if there are any problems or errors during execution of those scenarios, how to handle that?

thanks,

KP

[Former Member · Accepted solution]

Hi KP,

XI has a good alerting mechanism, in your business processes you could trigger an alert. This alert is picked up by the alerting framework and will show up in CCMS.

The only problem is that it is very hard to configure the alerting mechanism. Documentation is very limited on this issue.

A second, more simple, option is to build a 3rd interface for error messages. In stead of using an alert trigger you could redirect your errors in the Business Process to a file or email adapter.

For both methods you must use a switch object to direct errors to a new branch. Alerts can be triggered using a control object.

Christiaan Schaake

[Former Member · Accepted solution]

Hi Christiaan,

Thanks for the reply. But can you elaborate more on that.

You are suggesting to create 3rd interface for error messages. Then redirect the errors in Business Process to file or email adapter.... didn't get this. How do I redirect errors? Do I have to use BPM? Also is there email adapter in XI?

Sorry to ask you basic questions as I am new to XI

thanks,

KP

[Former Member · Accepted solution]

Hi,

first you have to distinguish between error handling in the applications and monitoring. As writen before, there is the CCMS and the alerting functions of the XI Runtime Workbench for the monitoring.

The error handling differs in synchronous and asynchronous scenarios and by the adapters you use. If you are using proxies (ABAP or JAVA) the receiver application can raise an exception. In a synchronous scenario the exception is transported by XI to the sender and a exception is raised there too. You can define different exceptions in the XI repository and add datatypes for specific error data. These fault messages are assigned to an interface and exception classes are generated for the proxies. Unfortunately most adapters don't make it that easy. In RFCs you can use the message structure sy-msgid, sy-msgty, sy-msgno and sy-msgv1 to sy-msgv4. It depends on the adapters what is possible.

If you are in an asynchronous world, there is no return message to the sender. If a receiver proxy raises an exception, you can see the exception in the inbound monitoring (SXMB_MONI or MessagingSystem) of the receiver system. Then you can use the error monitoring via ccms or alerting, to monitor and report the errors to the operating.

Another way is to use Acknowlegments to send back the status of the process. In this case you don't handle errors, but send back success messages. If the success messages is not coming back, you know there is a problem. but you need to keep track of your outgoing messages.

Notice, that if you use the XI messsaging (standard functionality) for error messages, you can not report errors, if the messaging system is broken down. CCMS is working parallel, and low level, to the messaging functionality of XI and can operate, even if XI is not working. It may be good to have a seperate monitoring server like SAP Solution Manager.

Regards,

Christian

[moorthy]

Hi ,

If you are using File Adapter as a Sender and you want to do Error Handling, then you can go thru following link, which will help you different approachs of Error Handling.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/99593f86-0601-0010-059d-d2d...

Thanks,

Moorthy

[Former Member]

KP,

When monitoring SAP XI 3.0 you will have 4 points of failure. The Integration Engine, qRFC, tRFC, and AFW. CCMS provides alerts for Integration Engine, qRFC, and tRFC. CCMS is not difficult to setup. In fact I do not use a centralized CCMS server. All of my alerts are setup locally on the XI server. They are very reliable. The AFW side of the house is another story. SAP XI does not provide CCMS alerts for errors occurring on the AFW side of the house. We have written a very simple SQL script which monitors a single table within the XI database for errors. IF it were not for CCMS I could not sleep at night.

[Former Member]

Hi KP,

Hi ,

Did the replies help? If so, don't forget to assign points. I gave them some, but feel free to increase them!

See: /people/mark.finnern/blog/2004/08/10/spread-the-love for directions.

Click on the Yellow Star icon in each reply.

You can give:

1 - 10 pointer (solves problem, marks as answered)

2 - 6 pointers (very helpful)

Lots of 2 pointers (helpful)

Thanks!

Linda (and Mark Finnern)

[Former Member]

Hi KP,

if i have get you right, you want to monitor your scenario execution to get the information where it failed or for that matter the step by step information.

There are couple of transaction like SXMB_MONI, SXI_MONITOR & SXMB_MONI_BPE(for integration scenario) etc

provided by XI.

You can also go to RWB and do a lot of monitoring of your scenario, like message monitoring, end to end monitoring etc.

Hope this is what you were looking for.

Regards,

Satish

[Former Member]

Hi Satish,

The transactions you told is for monitoring day-today errors.

I am asking about application error handling. I mean in data transfer from Sender to Receiver, what to do, if error or exception occurs in between? How to take care of this in design?

thanks,

KP