Skip to Content
author's profile photo Former Member
Former Member

Proxy framework: Catch CX_AI_SYSTEM_FAULT


I am using an outbound asynch ABAP Proxy to pass detail from CRM 4.0 into XI 3.0.

Everything works fine when the Integration Server is available. However, when the Integration Server is down, the message is persisted on the CRM side (which I expect as the interface is asynch) but the system exception CX_AI_SYSTEM_FAULT is not caught. The reason I want to catch this exception on the CRM side is I would like to notify the adminstrator of the communication issue and log this fact as well but I cannot do this.

The interface must be asynchronous from CRM otherwise the CRM process hangs whilst waiting for a response back from a SOAP message posted in a 3rd party application (which can be slow in processing the message)

Any ideas how I can solve this issue ? The documentation is as helpful as a chocolate teapot.

Kind regards

Colin. 😊

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Feb 01, 2005 at 05:30 PM

    Hi Colin,

    cause you do an asynchronous call I would expect not to get back an exception. The normal way would be, that the integration engine on your application server tries to get the message delivered after a certain period of time. If the proxy would raise an exception, everyone needs to catch that exception, even if the delivery is not that time critical.

    There are probably two alternatives to your scenario.

    1) You can use the CCMS monitoring for the Exchange Infrastructure to create an alert and inform the administrator (e.g. by e-mail). There is a preconfigured monitoring node called 'Exchange Infrastructure'.

    2) XI has the concept of acknowledgements, to send a message back to get the information, if the process was successful.

    Using one of the methods, you can make sure that your messages get delivered successfully. But both are more complicated to implement/configure.

    Maybe you can also use an update task to run a synchronous XI communication in background and log the result. But I think an asynchronous communication is more robust and fault tolerant than an synchronous.

    Hope that helps.



    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.