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

Handling Adapter Errors

I have a BPM that receives Soap messages sends a synchronous response then sends them to an R3 system. Inside the BPM, around the send step I have a block with an Exception handler to catch any errors that are generated by the call so that I can retry sending the message.

However, when an error occurs, eg the R3 system is taken down for maintenance, I get an XI error which does not get thrown back to the BPM exception handler.

Has anyone else got this to work or have any suggestions?

Thanks

Ian

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Feb 21, 2005 at 10:09 AM

    Check out note 770744.

    Add a comment
    10|10000 characters needed characters exceeded

    • It means, it can't be done before SP10.

      You might use a workaround: Define the abstract sync interface upon data types and message type similar to the RFC, but not upon the RFC itself. Use this interface in the BPM and do a mapping to the RFC outside the BPM.

      If this does not help, implement SP10.

      Regards

      Stefan

  • author's profile photo Former Member
    Former Member
    Posted on Feb 22, 2005 at 08:41 AM

    Hi Ian,

    You can set the Integration Server to automatically retry any deliver any messages failed due to a comms issue. In the Integration Server administration SXMB_ADM, run the option for Integration Engine configuration.

    In here, click on <b>Specific Configuration</b>. Add an entry for category TUNING parameter IS_RETRY_LIMIT with a value of say 25.

    This will force the Integration Engine to attempt 25 retries for delivery.

    This retry interval is 2 minutes and is not changeable.

    The message will be displayed in SXMB_MONI with a different icon instead of a red flag.

    Does this help at all ?

    Cheers

    Colin.

    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.