Skip to Content

How to handle Undelivered messages when the Target Application is down

Hi

in our scenario,

sapEccSystem >OuboundProxy >PI >ReceiverAdapter >ReceiverThirdPartyApplication

the known issue with the ReceiverThirdPartyApplication is, it gets down in frequent intervals, and automatically gets up and running, but we don't know at what times it will be down and when it will be up again.

in this asynch scenario, when the scenario gets triggered from source SAP system, and at that time, if the receiverAppl is up, it is working fine.

but when the scenario gets triggered from source SAP system and at that time if the receiverAppl is down, the message exchange gets failed

to address these kinds of issues,

1. is their any concept of Queuing or anything in PI, that can keep the messages in something like Queues and process them when the receiver application gets up., if yes how can configure them

Does PI act as Queuing server, so that it delivers the pending messages one ofter another, until they are all finally sent.

or

2.is there any retry mechanism, where can specify something like, the undelivered message needs to be resent after waiting for an hour.

thanks,

Madhu_1980

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    Jan 24, 2012 at 03:13 PM

    By default if the scenario is async then an average three times the messages will be tried for reprocessing if the message gets failed due to communication error. Also refer the SAP document further help on this.

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 24, 2012 at 02:09 PM

    Hi,

    The answer for both question is: yes. These are basic PI functionalities, refer to SAP documentation and training courses for details, as these issues are to big to discuss here on the SDN Forum.

    Greg

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 24, 2012 at 02:19 PM

    Hi Madhu,

    1. First of all, you need to talk the IT team managing the Receiver System and ensure that the system is available 24*7.

    2. For your two queries, the answer is Yes, as pointed in the earlier reply as well. Any failed message is retried 3 times by default and even after 3 retries the message does not go through then PI moves it to permanent system errror.

    And when the issue is resolved permanently, you can manually resend the message.

    I hope this answers your query.

    regards,

    Younus

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 24, 2012 at 03:30 PM

    Hi, the number of retries and the retry interval are modifiable java system parameters of the [Service SAP XI Adapter: XI|http://help.sap.com/saphelp_nw04s/helpdata/en/29/22ee41c334c717e10000000a155106/content.htm], check section Properties Related to Outbound Processing. You can change these properties in NWA of PI under Configuration Management -> Infrastructure -> Java System Properties -> Services -> XPI Adapter: XI. The screen in the bottom with the heading Extended Details displays the adapter's service property.

    I found these properties in oss Note 730870 - FAQ XI 3.0/ PI 7.0/ PI 7.1/ PI 7.11/ PI 7.2/ 7.3 RFC Adapter, under Q3, when doing research on another topic.

    Regards, Martin

    Add comment
    10|10000 characters needed characters exceeded