Hi Xiong Liang,
The sequence where the listener will kick start the flow service or publish to UM, will depend on which IDoc came in first through the listener. With multiple threads, it’s very unlikely you will be able to control the sequence where the IDoc came in.
You’ve a dependency on the SAP side when it delivered out the Idoc. If the gap between those are different 1 2 seconds, there might be a chance at the time arriving on IS SAP listener, they’ll not come in the expected sequence.
So it will very much depend on how you plan to implement your solution to process them. You can first have them publish to different queues in UM/JMS provider/broker, then develop your flow service to process according to your steps preferred.
If just using the listener and multiple threads, you cannot ensure the sequence executed sequentially if close proximity.
#webMethods#Integration-Server-and-ESB#Application-Platform#webMethods-io-Integration#Adapters-and-E-Standards#Service-Designer#Universal-Messaging-Broker