| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Connect output terminal to multiple input terminals...smart? |
« View previous topic :: View next topic » |
| Author |
Message
|
| moogoo |
 Posted: Fri Jan 30, 2004 10:03 am Post subject: Connect output terminal to multiple input terminals...smart? |
 |
|
Acolyte
Joined: 20 Sep 2002
Posts: 54
Location: US
|
Hi,
In my message flows I have a compute node who's output terminal is connected to multiple target input terminals. These multiple input nodes then process and enrich their own version of the original message to create multiple distinct messages that are subsequently written to a queue. I'm just wondering how exactly WMQI handles this splitting of the input message into multiple messages. At the output terminal where the message is split, what happens? According to the manuals, it appears that one of the connectors is followed and needs to finish all downstream processing until the other connector is giving its turn. That connector then runs through its downstream processing as well.
Can anyone confirm this? Guess I'm just trying to understand the performance hit of splitting the input message on overall system performance. If the second line of processing is not hit until the first is completed (when its written to the queue??), seems like the system will take a bit of a hit and I'm wondering if there is a more efficient way of doing this (propagate?).
Any help would be appreciated.
Thanks,
MG |
|
| Back to top |
|
 |
| EddieA |
| Posted: Fri Jan 30, 2004 10:28 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| At the output terminal where the message is split |
The message isn't 'split' by WMQI. Whatever message tree(s) you output from the node is sent, in turn, down each ot the paths. And yes, it does complete the route down the path before it starts the next. And, unless you use the Flow Order, the order that multiple paths is taken is unpredicatable.
If you change this to use Propogate, then you will (probably) also have to add Labels, so each Propogate goes to the correct path. But, this won't have any performance benefits, because each Propogated message still travels down the complete path before returning control back to the ESQL. Unless you can 'reduce' the size of the message being Propogated.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| moogoo |
| Posted: Fri Jan 30, 2004 11:25 am Post subject: |
|
|
Acolyte
Joined: 20 Sep 2002
Posts: 54
Location: US
|
Hmmm...thanks Eddie.
So with every new message that comes in, its unpredictable to know which connector it will hit first? So the Broker determines that on a per message basis?
MG |
|
| Back to top |
|
|
| kirani |
| Posted: Fri Jan 30, 2004 2:14 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
| moogoo wrote: |
So with every new message that comes in, its unpredictable to know which connector it will hit first? So the Broker determines that on a per message basis?
|
Yes and Yes.
Each instance of the message flow is executed in one single thread, so the processing will be always sequential within that flow. If you want to build parallelism within your message flow then you should split the logic into multiple message flows.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| jfluitsm |
| Posted: Sun Feb 01, 2004 2:39 am Post subject: |
|
|
Disciple
Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands
|
My experience is that the sequence is determend at deploy time, so all messages will follow the same sequece, but this can be changed after the next deploy.
You can however force a sequence with the Flow Order node.
_________________
Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Feb 02, 2004 10:16 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| jfluitsm wrote: |
You can however force a sequence with the Flow Order node. |
Really, though, if you're branching more than twice off an output terminal, it's probably in your best intrests to use a RouteToLabel and Label nodes, instead.
This will allow you to build a controllable sequence of operations, and also have future flexibility with good performance. I don't think Flow Order nodes are very scalable as you nest them.
The RouteToLabel flow allows you to have a much clearer message flow layout that it's easier for WMQI to arrange.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
