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 » Advantage/Disadvantage of MQGET node

Post new topic  Reply to topic
 Advantage/Disadvantage of MQGET node « View previous topic :: View next topic » 
Author Message
long.hoang
PostPosted: Mon Oct 27, 2008 9:12 pm    Post subject: Advantage/Disadvantage of MQGET node Reply with quote

Novice

Joined: 18 Sep 2007
Posts: 13
Currently, we have a request/reply architecture where:
- A message flow sends a request from Source to Target application
- Another message flow sends the response from Target to Source Application.

Issue: Target application cannot handle the size of the request from Source Application (e.g. Source request 200 client detail in 1 message while Target only can handle a max of 50)

Solution: We agree that the Integration service need to split the request to an acceptable size and combine the response from the Target application before sending to Source application. However 2 solutions was pushed forward:
+Sol1: Combine the 2 message flows into 1, using MQGET node and do split-combine within one message flow
+Sol2: Keep the 2 message flows separate and splitting and combining the request/responce base on Message GroupID

Both of the guys that bring up this solutions are away (one quits and one on leave) and i'm stuck here making the decision

I'm tend to go toward solution 2 since it seem less complex, but still concern about what are the advantage we could miss out from Solution 1 using MQGET node.

Could someone help this scape goat make a sound decision ?
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Oct 28, 2008 1:26 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447
The MQInput node is not going to automatically combine all of the group members into a single message flow thread. You would need to use Collector node for that.

So your choice is not between "MQGet" and "GroupId", it's between "MQGet" and "Collector".

It's not clear that there's a compelling advantage to using Collector in this case.
Back to top
View user's profile Send private message
long.hoang
PostPosted: Tue Oct 28, 2008 3:22 pm    Post subject: Reply with quote

Novice

Joined: 18 Sep 2007
Posts: 13
Thx jeff, the idea behind opt2 is for the 2nd flow (response) to:

1. Wait until all group messages are available (Last message in group has arrived)
2. Start reading message 1 by 1 and store the processed results in a shared variable
3. Send the combined message out when the last message has been processed

If we use option 1 with MQGET we probably have to use shared variable also and the wait time for all response could cause performance issue.
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 » Advantage/Disadvantage of MQGET 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.