MQSeries.net :: View topic - IIB9: IntergrationService & AggregateNode

akil

Hi

I have created and integration service project, this creates a main flow and sub-flows for every operation. One of the operations is 'processApplication'.

The processApplication operation is supposed to do the following:
1. The input is an, each application is made by a group of anywhere between 4 to 6 applicants.
2. For each of the applicants, I need to call an external SOAP service (by external I mean a public service, outside of the datacenter), to retrieve the credit Rating.
3. I am trying to follow the Aggregation Sample & the Airline sample (along with the documentation) to get this done.

Following is my understanding -
1. It is recommended to have separate flows for the FanOut, the Work & the FanIn, one of the reasons being that the number of instances of the Work & the FanIn flows will be greater than 1 ( closer to the parallelism that's required , while the FanIn will be 1 , or closer to what's needed for the in-coming message rate ).
2. The integration template creates a sub-flow for the operation, with an Input & an Output Node that handles the UOW for the operation.

Following is my approach -
1. In the operation's sub-flow I will MQOutput the incoming payload and I will wait on an MQInput for a reply.
2. I will create 3 separate flows following the Aggregation Sample (1 for FanIn, 1 for the external Soap call, and 1 for FanOut ), the FanIn will listen for messages from the operation's sub-flow, and the FanOut will reply back to the operation's sub-flow. These 3 flows will use a separate queue/pair for the aggregation.

My questions -
1. Am I on the right track or am I over-complicating the requirement?
2. In the Work flow, where I make the external Soap call, should I do a synchronous call or do I use the AsyncSOAPRequest & Response? Which is appropriate and how does one decide?
_________________
Regards