| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Build Output message from multiple input messages |
« View previous topic :: View next topic » |
| Author |
Message
|
| arkenstone |
 Posted: Tue Oct 21, 2008 1:16 am Post subject: Build Output message from multiple input messages |
 |
|
Newbie
Joined: 08 Jul 2008
Posts: 8
|
Hi,
I'm working on Broker 6.0 and here is the challenge i'm facing :
I have to build an output message from multiple input messages.
Input messages are of different types:
- first I get a technical message telling which kind of output message I have to build
- then I get multiple messages (1 to n) which contain data to map on the output
- finally, I get a commit message
My first approach has been to store every incoming message in variables under the Environment tree, save the Environment tree in a shared row after each message is processed, restore the Environment tree when a new message comes.
Once I get the commit message, as I have in memory all the input messages, I can start mapping the output message and propagate the built message to the output MQ.
But this approach sounds not very reliable, so I'm thinking about storing the messages in an Oracle table instead of the Environment.
Is this a good way to handle this scenario ?
Any better idea ?
I have never worked with Aggregate nodes, is there a more elegant way to managed this situation with these nodes ?
Thanks.
Regards,
Olivier |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Tue Oct 21, 2008 1:21 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
|
| Back to top |
|
|
| arkenstone |
| Posted: Tue Oct 21, 2008 2:06 am Post subject: |
|
|
Newbie
Joined: 08 Jul 2008
Posts: 8
|
Thanks, but it seems this topic is suggesting to upgrade to 6.1 to use the Collector node, and unfortunately, it's not on the shelves.
Yes, i'm dynamically choosing the output format depending on information in the first incoming message. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Oct 21, 2008 3:03 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You said 6.1 is not an option. Have you thought about message grouping and only processing once the full group is available? The DB as holding place is a good start, it should also allow for resending of messages. Don't forget to also have a set is complete indicator on the DB as you would not want to process incomplete sets... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
