| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message flow invokation |
« View previous topic :: View next topic » |
| Author |
Message
|
| rkford11 |
 Posted: Tue Dec 14, 2004 7:20 am Post subject: Message flow invokation |
 |
|
Partisan
Joined: 06 Jun 2004
Posts: 316
|
I have two message flows with same input & output queues but difference in the compute node actions under the same topic.when i put
the message on to the input queue one of the flow is getting invoked, but i want the correct flow to get invoked depending on the
input message. how does this happen.is it the work of an application before the message is sent to the input queue.
Thanks |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Dec 14, 2004 7:29 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Messages that satisfy the criteria set on the input nodes will be randomly distributed to each message flow.
The message set options on the input node are NOT CRITERIA. They are DEFAULTS. That means, if an MQRFH2 header is not attached to the message - or that header does not specify a message type, format etc - then the message will be treated as having the suppleid values.
In other words, if you add MQRFH2 headers, you can use ONE message flow, and have it decide which compute node to call based on the incoming message.
Or you can otherwise detect what the incoming message is, and then decide how to process it.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rkford11 |
| Posted: Tue Dec 14, 2004 11:32 am Post subject: |
|
|
Partisan
Joined: 06 Jun 2004
Posts: 316
|
| jefflowrey wrote: |
Messages that satisfy the criteria set on the input nodes will be randomly distributed to each message flow.
The message set options on the input node are NOT CRITERIA. They are DEFAULTS. That means, if an MQRFH2 header is not attached to the message - or that header does not specify a message type, format etc - then the message will be treated as having the suppleid values.
In other words, if you add MQRFH2 headers, you can use ONE message flow, and have it decide which compute node to call based on the incoming message.
Or you can otherwise detect what the incoming message is, and then decide how to process it. |
And do we set the MQRFH2 value in the application, which is sending the message to the input queue. please correct me on this statement.
Thanks |
|
| Back to top |
|
|
| EddieA |
| Posted: Tue Dec 14, 2004 11:53 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| And do we set the MQRFH2 value in the application |
Which means that the Flow will use those values, instead of the defaults set on the Input node.
As Jeff stated:
| Quote: |
| The message set options on the input node are NOT CRITERIA. They are DEFAULTS |
Which means they are not used for selecting messages. They are used to supply values, that are not present in the message.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| kirani |
| Posted: Tue Dec 14, 2004 11:29 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
rkford11,
It does not make sense to have 2 different message flows listening to the same queue. Please use single message flow to identify different types of messages coming on the input queue. You can either route them to two different output queues for further processing or implement the logc in the same message flow.
_________________
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 |
|
|
|
|
|
| |
|
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
|
|
|
|
