Author |
Message
|
me@tcs |
Posted: Mon Apr 20, 2009 8:39 pm Post subject: Using a single MQInputNode to listen to multiple queues |
|
|
Novice
Joined: 22 Mar 2008 Posts: 18
|
Can a single MQInput node be configured to listen to multiple queues?
If yes, could any one please lemme know howits done..?
Thanks in advance.. |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon Apr 20, 2009 9:26 pm Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
What things have you tried?
In any case, the short answer is NO.
Defining an InputQueue either directly of via a promoted property is MANDATORY for an MQInputNode.
You may have some better results with the MQGet node....... _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
zpat |
Posted: Mon Apr 20, 2009 11:19 pm Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
You can have several MQInput nodes in a flow, with different queue names. They can all be wired up to the next node in the flow.
The effect is that the broker will start the flow several times, once for each input node. |
|
Back to top |
|
 |
vairavan |
Posted: Tue Apr 21, 2009 7:03 pm Post subject: |
|
|
Apprentice
Joined: 22 Apr 2008 Posts: 42
|
Do you mean to say... Broker will start n number of instances as per n number of input nodes?
Correct me If I am wrong... |
|
Back to top |
|
 |
zpat |
Posted: Tue Apr 21, 2009 9:47 pm Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
Yes, because each MQinput node has a MQGET WAIT and therefore is blocking the thread. |
|
Back to top |
|
 |
|