ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » How aggregation works

Post new topic  Reply to topic
 How aggregation works « View previous topic :: View next topic » 
Author Message
Lucky
PostPosted: Tue Jun 21, 2011 5:16 am    Post subject: How aggregation works Reply with quote

Apprentice

Joined: 06 Feb 2007
Posts: 35

Hi all,

I am trying to understand how aggregate reply node works in combining all the fan-out messages and created a fan-in message.

Please share some details on this.

Thanks,
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Jun 21, 2011 5:20 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

It keeps track of information about each request message that gets sent out, and uses that mark to associate the replies.

Aggregation works from a SINGLE input message, that generates SEVERAL requests, and combines the responses from them into ONE or more replies.

If you need to work from MORE THAN ONE input message, you need Collector.

If you are asking for more specific information on how to use aggregation, you are either asking for assistance with a certification exam question or free training.
Back to top
View user's profile Send private message
Lucky
PostPosted: Tue Jun 21, 2011 6:06 am    Post subject: Reply with quote

Apprentice

Joined: 06 Feb 2007
Posts: 35

Hi,

Consider that i've a req flow and resp flow.

In request flow: req msg here is generated as 2 request msgs. Will be using aggregateControl and AggregateRequest nodes here.

In response flow: I wante to aggregare these 2 msgs that were seperated in request flow. WHich will be done using aggregateReply nodes.

So, as you said what is that mark which is used to associate the msgs by AggregateReply node. Is it messageId, CorrelId.... What is that being used.

Please provide some suggestions.

Thanks in advance.
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Jun 21, 2011 6:18 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Lucky wrote:
What is that being used.


What the InfoCenter says is being used. Start here and keep reading until you get to a topic called "Correlating input request and output response aggregation messages" or you've grasped the concept.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Jun 21, 2011 10:40 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

You may also want to look at the aggregation sample...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Lucky
PostPosted: Tue Jun 21, 2011 9:58 pm    Post subject: Reply with quote

Apprentice

Joined: 06 Feb 2007
Posts: 35

Hi Vitor,

I had gone through Info center for understanding this.

Send the original request message directly back to the AggregateReply node as one of the aggregation requests. To do this, the CorrelId must be set to the MsgId, and the MQOutput node must have its MessageContext set to 'Pass all'.

I am working on a message flow equal to above condition. When i capture the trace node after aggregate reply node. I don't see correlid of request matching with CorrelId/MsgId of response message. Also, replyIdentifiers in PROPerTIES header for these messages are different through.


That made me failed to understanding how request is correlated with response by aggregation node.

Thanks in advance.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed Jun 22, 2011 1:08 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

You have to create a separate flow, that will receive the original request and do those things, and send it back as a response to the aggregation flow.
Back to top
View user's profile Send private message
Lucky
PostPosted: Wed Jun 22, 2011 8:59 pm    Post subject: Reply with quote

Apprentice

Joined: 06 Feb 2007
Posts: 35

Hi,

I understand that there need to be a separate flow which will take original request and send the reply to the aggregate flow(which has AggregateReply node).

Apparently, my query is what is the source which AggregateReply node will consider to match the messages that were fanned out.

I am not sure if I am placing my query correctly. All I want to know is how aggreagteREply node identifies that these are my fan-out messages which need to be fan-in.

Thanks.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Thu Jun 23, 2011 1:23 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Lucky wrote:
All I want to know is how aggreagteREply node identifies that these are my fan-out messages which need to be fan-in.


You have already quoted the documentation that tells you exactly the answer to this question.

The CorrelID of the response must match the MsgId of the request.

Each AggregationRequest node stores the Aggregation ID and the MsgID of each outbound request.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » How aggregation works
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.