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 » Dynamic aggregation pattern

Post new topic  Reply to topic
 Dynamic aggregation pattern « View previous topic :: View next topic » 
Author Message
nelson
PostPosted: Mon Jun 01, 2015 6:40 am    Post subject: Dynamic aggregation pattern Reply with quote

Partisan

Joined: 02 Oct 2012
Posts: 313

Hi all,

On your experience, do you think it is a good idea to handle the dynamic aggregation yourself in memory? something like a hash table of request(s)/reply(s), independently of the protocol..

We usually need to take advantage of existing legacy systems that do not support multiple replies (like MQ groups). For instance, a legacy back end service is designed to handle one request/response (even existing broker services that we want to reuse works this way), but a new service (to the front end application) requires multiples calls to the back end in the same request, broker then needs to reply a consolidated response.

So we are working in a pattern to handle/orchestrate dynamic aggregation...

Any advice is very appreciated.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Jun 01, 2015 8:16 am    Post subject: Reply with quote

Grand High Poobah

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

your patterns will be aggregation and collection...
Look them up!
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
mqjeff
PostPosted: Mon Jun 01, 2015 8:21 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

You should consider the memory needed.

If you do use a memory only solution, you should use Global Cache - safer that way, plus allows you to complete aggregation in separate threads of a flow or separate EGs.

You should also make sure you know when the aggregation/collection is completed...

And remember if you're making a synchronous call (like a SOAP or REST call) then you don't need aggregation, just put the input message or the responses in some useful place.
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 » Dynamic aggregation pattern
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.