| Author |
Message
|
| chenna.hari |
 Posted: Thu May 30, 2013 3:37 am Post subject: Queue Manager Name in MQOutput Node |
 |
|
Centurion
Joined: 21 Mar 2009
Posts: 103
|
| can any one tell in which cases, we will give the queue manager name in MQOutput node. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu May 30, 2013 8:56 am Post subject: Re: Queue Manager Name in MQOutput Node |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| chenna.hari wrote: |
| can any one tell in which cases, we will give the queue manager name in MQOutput node. |
When you're required to by the WMQ topology you've created at your site. This may be never, this may be most of the time.
It's used in exactly the same cases you'd specifiy a queue manager name in any WMQ-aware application. Seriously. Think of it as doing a PUT1 call.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zpat |
| Posted: Thu May 30, 2013 9:12 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| Leave it blank. Otherwise you are making your flows non-portable. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu May 30, 2013 9:14 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zpat wrote: |
| Leave it blank. Otherwise you are making your flows non-portable. |
Assuming the queue manager name quoted is a) not promoted as a flow property to be changed to the environmentally correct value at deploy time and b) the queue manager name quoted is not an alias common to all environments.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu May 30, 2013 9:50 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I can honestly say that in my more than 10 years of using broker, I have never used this property.
If I'm using multiple queue managers and I'm outputting messages that are being writtten to a Remote Queue, I do all the configuration in the Queue Manager.
This way, I can use Alias Queues that point to Local Queues in my Dev environment and then without making changes (or even promoting the property) I can deploy the same flow into other enviroments that use a Remote Queue of the same name.
If you plan your environment(s) carefully, you can save yourself a lot of grief later on.
_________________
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 |
|
|
| Vitor |
| Posted: Thu May 30, 2013 9:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| smdavies99 wrote: |
I can honestly say that in my more than 10 years of using broker, I have never used this property.
If I'm using multiple queue managers and I'm outputting messages that are being writtten to a Remote Queue, I do all the configuration in the Queue Manager. |
I can't say I use it a lot.
| smdavies99 wrote: |
| This way, I can use Alias Queues that point to Local Queues in my Dev environment and then without making changes (or even promoting the property) I can deploy the same flow into other enviroments that use a Remote Queue of the same name. |
It's a very enlightened view and one I mostly share. But not all sites are that enlightened. I was simply pointing out alternatives.
| smdavies99 wrote: |
| If you plan your environment(s) carefully, you can save yourself a lot of grief later on. |
Again, very correct and very enlightened. But many sites perfer short term solutions to long term planning and accept the grief as a cost of doing business.
That's why so many of us are stuck using bar file overrides.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kash3338 |
| Posted: Thu May 30, 2013 8:38 pm Post subject: Re: Queue Manager Name in MQOutput Node |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| chenna.hari wrote: |
| can any one tell in which cases, we will give the queue manager name in MQOutput node. |
In cases where you need to send messages to a remote queue (queue in a different Queue Manager and not Broker default Queue Manager), you can specify the Queue Name and the Queue Manager name. But you need to have the following set-up in your Broker Default Queue Manager,
1. Have a Sender Channel in Broker Default QM to the Remote QM
2. Have a Receiver Channel at Remote QM for receiving messages from Broker Default QM.
3. Have a Transmission Queue in place for the Sender Channel
4. Have a Listener in place for the Receiver Channel
The same set-up is required in case of having a Remote Queue instead. With Remote Queue you have a flexibility of having a Alias Queue and thus using it in your flow makes it more simple than actually having the QM-Name mentioned.
It is indeed a pain to use this option when compared to having remote queue's in place. As mentioned by zpat, this option is usable, but not portable. |
|
| Back to top |
|
|
|
|
