on 10-26-2009 8:23 PM
Hi,
we have an asynchronous interface from ECC to PI and then, through a BPM, synchronous messages are sent from PI to External system.
The problem we have is that if PI is closed, we gather many messages in ECC and when PI is restarted ,
many messages are sent to PI and then to the external site at once.
Question : how can you configure the retry of messages in ECC when PI is closed ?
Question : how can I reduce the flow of messages so that less messages are sent at once to the external site ?
Thank you.
Question : how can you configure the retry of messages in ECC when PI is closed ?
There must be a scheduling mechanism at your sender to send message to PI periodically. When PI is down, ECC RFC destination call to PI would fail. You may use a report RFC_VERIFY_DESTINATION to identify if the destination is reachable. If it not, then you may increase the time duration of the next run of the schedule.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can use smqr and smqs configuration to restrict the number of processes that can handle the BPM.
Also, there are jobs to automatically restart failed queues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.