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 » Problem at the Aggregate reply node

Post new topic  Reply to topic
 Problem at the Aggregate reply node « View previous topic :: View next topic » 
Author Message
siljcjose
PostPosted: Thu May 01, 2008 12:30 am    Post subject: Problem at the Aggregate reply node Reply with quote

Apprentice

Joined: 18 Aug 2005
Posts: 27

I have a scenario where i have to enrich the incoming message, by creating a request and sending and once the response is got back the initial message is enriched with the data, i have recieved. Since there is a resticition of using databse in our environment for such purposes i am using Aggregate nodes to achieve this.

The problem i end up is, i send the request for enriching the message has one aggregate requeust and the Incoming message as another. When i try to collect the replies at the Aggregate reply node. The message doesn't come as an aggregate reply. It comes as two individual replies, which then flows to the Unknow terminal.

I am using MB 6.0. Please can you, help me find why this could be happening. Is it possible that the Control messages are not reaching the aggregate reply node. I have the Aggregate request and the Aggregate reply nodes in different flows.

Thanks In advance
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu May 01, 2008 1:23 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

V6 Aggregation doesn't use the Control terminal anymore.

Also, if you only need to enhance the input message with one reply message, you can use MQGet node instead of Aggregation.

It's not clear why your aggregation isn't working. Also if you're sending the original message, you will need a proxy replier to bounce this message back to the original flow as a reply message.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
siljcjose
PostPosted: Thu May 01, 2008 2:29 am    Post subject: Reply with quote

Apprentice

Joined: 18 Aug 2005
Posts: 27

Thanks for the Reply.

I have a proxy flow for the Input message which sends the messages back to the Aggregat reply flow.
I had this aggregate setup up and working, for a simple XML message ( Which i had carried as part of a POC). When i added a complex MRM message with Namespace, it stopped working and started seeing this behavior.

Regarding the MQGET node. I had considered using this. I had preferred Aggregate assuming that parallel processing would be possible with agrregate. That is if i have 10 input messages, i suppose that i fanned out the first two input message. I should be able to process the second message if it comes before the first one. But in MQGET node, would not the behavior be serialized. Please correct if my understanding is wrong.

The server which provides the message for enriching can proceess messages in parallell. That is, it is not necessary that the first message send to it is the first message it send back. If i use the MQGET node the parallel behavior provided by the server would be redundant right ?
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu May 01, 2008 2:34 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Using MQGet to retrieve the reply synchronously with the input will not necessarily remove the parallelism. You can use additional instances of the input flow.

Or you can consider receiving the reply with an MQInput node, and using an MQGet node to retrieve the original request message from a holding queue.

Switching from XML to MRM shouldn't be causing the problem you're seeing. There must be something else you've changed that is causing the problem.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
siljcjose
PostPosted: Thu May 01, 2008 3:42 am    Post subject: Reply with quote

Apprentice

Joined: 18 Aug 2005
Posts: 27

Thanks Jeff. The reply you gave about the MQGET node, really helps. I will work towards that. I will also try to find the problem i had with the Aggreagte flows. I wanted to make sure that the aggreagte problem which i had was not a common problem.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu May 01, 2008 10:08 am    Post subject: Reply with quote

Grand High Poobah

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

siljcjose wrote:
Thanks Jeff. The reply you gave about the MQGET node, really helps. I will work towards that. I will also try to find the problem i had with the Aggreagte flows. I wanted to make sure that the aggreagte problem which i had was not a common problem.

Read the APARS and fix pack notes. I seem to remember that there was one about Aggregation in there.


_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Problem at the Aggregate reply node
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.