on 08-05-2008 3:16 PM
I want to maintain QOS as EOIO, and meanwhile don't want messages to stuck in queue.
Is there any blog on this topic ?? e.g I have a file-xi-proxy scenario. I want to maintain
sequencing, meanwhile, if messages fails in ECC due to application error, other messages
should not wait in the queue, and rather they should process in sequence. Is there any way
to do this ??
Regards
kumar
As far as i know,its not possible since you are using EOIO
Thanx
Aamir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Aamir,
If I fix the parallel processing for the service of this interface to 1 in both XI and ECC systems, do you think it is not possible ??
Apart from that I am using QOS as EO rather to EOIO. This way I am able to send the messages to ECC ( file-xi-proxy) in sequence even though I am not using EOIO. This way I am we can avoid messages stucking in queue and meanwhile maintaining the sequence.
What are your comments on the above implementation ??
thanks
kumar
>>Apart from that I am using QOS as EO rather to EOIO
This will only work if you are testing the interfaces with a small amount of data.once the amount of data increases,EO will never guarantee delivering the messages in same order in which it was picked up.
A big file might be picked up first but will take longer to process whereas a smaller file which was picked later on will get processed quickly and send to R/3 before.
>>If I fix the parallel processing for the service of this interface to 1 in both XI and ECC systems
I m not really sure what you mean by this.
Thanx
Aamir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.