| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Qmgr Alias |
« View previous topic :: View next topic » |
| Author |
Message
|
| dzifchock |
 Posted: Wed Nov 18, 2009 10:15 am Post subject: Qmgr Alias |
 |
|
Apprentice
Joined: 21 Feb 2007
Posts: 41
|
Here is the scenario:
MQ v6.0.2.6
There is an application that lives on 2 different servers. Each server has a qmgr named a.q.mgr , the queue manager name is the same on both servers. This application can only specify one queue manager name in its configuration, hence both queue managers having the same name. One queue manager belongs to a cluster , the other is stand alone . It would be nice if both queue managers can join the cluster for ease of administration and benefits of clustering .
Is it possible to change the qmgr name on one of the queue managers, create a Qmgr Alias to trick the application in thinking it is still writing to a.q.mgr, and join the qmgr to the cluster ? |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Wed Nov 18, 2009 10:19 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
No. QM Aliases do not get referenced for MQCONN(X) calls.
If the application can connect in MQ Client mode, even if its running on the same same server, then your problems are solved. MQ Clients do not need to specify any QM name - hostname, channel name and port # are enough.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Nov 18, 2009 11:21 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Or if you have to connect in bindings mode, you can make a.q.mgr the default Queue Manager on each server, and then the app can specify blanks for the QM name on the MQCONN call, even in bindings mode.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Nov 18, 2009 1:10 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| Each server has a qmgr named a.q.mgr |
It is not a best-practice to create multiple qmgrs with the same name.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Nov 18, 2009 1:52 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
| Quote: |
| Each server has a qmgr named a.q.mgr |
It is not a best-practice to create multiple qmgrs with the same name. |
Especially as you can't (as you intimate in your original post) "rename" a queue manager & 2 queue managers with the same name in a cluster is disaster.
(For the purists - yes, I know you can sort of rename a queue manager but there's not a "rename" command)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Nov 18, 2009 7:14 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The best you can do is recreate the qmgr with a different name.
You can then create a qmgr alias in that qmgr that allows it to process messages originally received for the other qmgr. (See MQ routing and qmgr alias in the intercommunications manual) 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Nov 18, 2009 7:33 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| Is it possible to change the qmgr name on one of the queue managers, create a Qmgr Alias to trick the application in thinking it is still writing to a.q.mgr, and join the qmgr to the cluster ? |
What you should be asking is: can I run an app on qmgr1 that successfully puts a message on a queue on qmgr2?
The answer is YES. This is basic qmgr-to-qmgr distributed queuing. This requires (on the qmgr where the app executes) a QRemote definition, a transmission queue, and a sender channel. The receiving qmgr requires: a receiver channel, a listener, the destination QLocal definition.
No tricking the qmgr is necessary. Again, this is very basic MQ stuff.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| 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
|
|
|
|
