MQSeries.net :: View topic - how does an aggregate work technically?

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » how does an aggregate work technically?

how does an aggregate work technically?

« View previous topic :: View next topic »

Author

Message

EgilsJ.Rubenis

Posted: Mon Mar 24, 2003 5:35 am Post subject: how does an aggregate work technically?

Acolyte

Joined: 18 Nov 2002
Posts: 63
Location: Germany, Alfeld

Hi,

does somebody know how data comes together in an aggregate reply node. I receive in my flow two replies. They are processed in
the aggregate control node but sen to the 'unknown' node.
One reply is send by an replyFlow. The other reply comes from a
z/OS Cics Transaction.

I allready looked at the redbooks. On Windows its working fine (I have my own replyFlows). But for z/OS ist works different.

What are the keypoints I have to look at for aggregation (MsgID, CorrelID, GroupID) ?

Thanks

lung

Posted: Mon Mar 24, 2003 9:59 pm Post subject:

Master

Joined: 27 Aug 2002
Posts: 291
Location: Malaysia

Basically the aggregateReply node will check to see if the CorrelId in the reply matches the MsgId of the original msg sent (the one sent to the aggregateRequest node).

If it gets routed to the Unknown Terminal, u can turn on the trace and take a look at the CorrelId of the reply and the MsgId of the request. Both of these should match.
_________________
lung

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » how does an aggregate work technically?

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