| Author |
Message
|
| mqlover |
 Posted: Sun Sep 30, 2012 7:34 pm Post subject: MQinput node having multiple queue names |
 |
|
Disciple
Joined: 25 Jul 2010
Posts: 176
|
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Sun Sep 30, 2012 9:16 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
You can't configure the MQInput node to pick up messages based upon a changing queue name.
You have two (Simple) options
Just create Alias Queues for the three message types that point to the single queue that that the MQInput Node configured to read from.
OR
Use an MQInput Node configured for each queue and simply wire the 'out' terminals together.
_________________
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 |
|
|
| mqlover |
| Posted: Sun Sep 30, 2012 10:08 pm Post subject: MQinput node having multiple queue names |
|
|
Disciple
Joined: 25 Jul 2010
Posts: 176
|
Hi,
Thanks so much.
I thought so, still wanted to confirm before proposing this approach.
Thanks a ton. |
|
| Back to top |
|
|
| ar.mm |
| Posted: Tue Sep 01, 2015 12:54 am Post subject: |
|
|
Newbie
Joined: 01 Sep 2015
Posts: 2
|
Hi,
Alias Queue is perfect approach, but I'm wondering if there is a way where the message flow can know from which Alias Queue the message came? If I set the local queue in MQInput node, then it will treat all messgaes as if they ware coming from single queue, I need the flow to distinguish the source application which sending to a specific alies queue that resolves to the queue used in MQInput node.
Thanks. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Sep 01, 2015 1:26 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| ar.mm wrote: |
Hi,
Alias Queue is perfect approach, but I'm wondering if there is a way where the message flow can know from which Alias Queue the message came? If I set the local queue in MQInput node, then it will treat all messgaes as if they ware coming from single queue, I need the flow to distinguish the source application which sending to a specific alies queue that resolves to the queue used in MQInput node.
Thanks. |
There really isn't an OOTB way of detecting this.
However you could put the alias queue name (lenght permitting) into an unused field in the MQMD such as ApplIdentityData (32chars long) but this will require changes to both applications. But honestly is it worth the trouble?
_________________
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: Tue Sep 01, 2015 2:42 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
You can use the alias queue definitions to set different message priority values and detect this value in the message MQMD in the broker flow.
However it would of course cause these messages to be retrieved by priority unless you override the delivery sequence in the local queue definition to FIFO.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Sep 01, 2015 5:02 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ar.mm wrote: |
Hi,
Alias Queue is perfect approach, but I'm wondering if there is a way where the message flow can know from which Alias Queue the message came? If I set the local queue in MQInput node, then it will treat all messgaes as if they ware coming from single queue, I need the flow to distinguish the source application which sending to a specific alies queue that resolves to the queue used in MQInput node. |
See the debate here which discusses your question.
I also repeat my associate's point that you should open a new thread and reference old ones rather than just reopen 3 & 4 years old threads.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Sep 01, 2015 7:57 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20697
Location: LI,NY
|
| ar.mm wrote: |
Hi,
Alias Queue is perfect approach, but I'm wondering if there is a way where the message flow can know from which Alias Queue the message came? If I set the local queue in MQInput node, then it will treat all messgaes as if they ware coming from single queue, I need the flow to distinguish the source application which sending to a specific alies queue that resolves to the queue used in MQInput node.
Thanks. |
Smells like a request / reply scenario... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Sep 01, 2015 8:41 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
Yes, the REPLY-TO-QUEUE name field could also be used for identification of the origin message, even if it there was no reply message.
But that requires an application change.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
|
|
