MQSeries.net :: View topic

akil · Posted: Wed Oct 28, 2015 11:15 pm Post subject: IIB9: SoapAysncRequest

Hi

The SoapAsyncRequest node takes a 'uniqueidentifer' as a property, that is used to match pair it up with a SoapAsyncResponse node..

This effectively means that this node cannot be part of a sub-flow, because if that is done, and the sub-flow is included in multiple message flows, multiple instances of the SoapAsyncRequest node get created & the deployment fails..

The scenarios that i have is to create an Integration Service which has multiple operations, and all of these operations interact with a high latency external service. I was thinking of using the SoapAsync* nodes, but as I see it, i am having to use multiple SoapAysnc nodes (one for each operation's subflow).. Is this the way or am I missing something ?

The other option would be to introduce an MQ & call SoapAsyncRequest from a MQInput message flow .. This would make the code common, but it will introduce an MQ hop .. I am wondering which is the better of the 2 evils . (multiple SoapAsync* pairs or a MQ hop)..
_________________
Regards