| Author |
Message
|
| basva |
 Posted: Tue Apr 04, 2006 6:30 pm Post subject: Multiple Replies |
 |
|
Apprentice
Joined: 27 Nov 2002
Posts: 39
|
Hi
I need to handle a scenario in which each request generates multiple responses and these responses need to be aggregated. What is the best way to handle this situation.
Thanks
Satish |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Tue Apr 04, 2006 7:31 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi basva,
It would be better if you expalin your requirement...
When u say
| Quote: |
| each request generates multiple responses |
I would think of PROPAGATE
| Quote: |
| these responses need to be aggregated |
Do u mean u have to use Aggregation, or just collectively give them as output 
Btw... ur supposed to be a Solutions expert 
Regards. |
|
| Back to top |
|
|
| basva |
| Posted: Fri Apr 07, 2006 11:53 am Post subject: |
|
|
Apprentice
Joined: 27 Nov 2002
Posts: 39
|
| Here are my requirements. I have a flow which sends a request to a backend app. Back end app sends responses to some other flow. We need to aggregate all these responses. It seems the aggregate node works with multiple requests and one response for each response. Am I missing something about the aggregate node? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Apr 07, 2006 12:05 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The Aggregate nodes allow you to create multiple outbound requests from one inbound request, and then assemble the responses to all the outbound requests into one master reply.
If you have one inbound message, that generates multiple outbound requests, but does not need to assemble multiple responses into a single response, then you do not want to use the Aggregate nodes.
There are other ways, particularly in version 6, if you need to accumulate a set of messages that are not correlated together by a request/reply pattern.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| TonyD |
| Posted: Sun Apr 09, 2006 1:36 pm Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
| One request message, multiple reply messages...MQGet can handle this. Use same CorrelId (or logical grouping) in responses and PROPAGATE when processing the responses. You will need to know when you have received the last response so that you can drop out of the PROPAGATE loop. |
|
| Back to top |
|
|
|
|
