| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMQ Port and Listeners |
« View previous topic :: View next topic » |
| Author |
Message
|
| mqwbi |
 Posted: Fri Jan 02, 2009 11:11 pm Post subject: WMQ Port and Listeners |
 |
|
Novice
Joined: 15 Dec 2008
Posts: 24
|
I am using Websphere MQ 6.0
Scenario 1
===========
I open MQ Explorer in Windows. I see my queue managers listed there. I select a queue manager, right click and select properties. The default property set which opens is 'General'. I select the option TCP. The options available are TCP Port, TCP library 1, TCP library 2, TCP keepalive and TCP listener backlog.
I see that TCP port is set to 1414. This is the default for all queue managers in this machine. I change this WMQ port of queue manager to 1417. I believe this means that this queue manager is running on a WMQ port 1417.
Question: I want to do change the WMQ Port permanently for a queue manager in AIX 5.3 and WMQ 6.0 . Can you please help? How can i see what is the current wmq port for the queue manager?
Scenario 2
============
I want to create a WMQ 6.0 Cluster on AIX 5.3 . I understand that these will be the summary of steps to follow.
>> Choose queue manager for Full repository. Create Full repository.
>> Create listeners on each queue managers.
>> Create Sender-Receiver Channels
I have a question now. I want to create the listeners. Do i use listener objects? I understand that while creating this listener, i have the option to specify the port. What is the difference between this port and the WMQ port specified in Scenario 1.
Can you please help?
Thank You |
|
| Back to top |
|
 |
| Vitor |
| Posted: Sat Jan 03, 2009 2:54 am Post subject: Re: WMQ Port and Listeners |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqwbi wrote: |
| I see that TCP port is set to 1414. This is the default for all queue managers in this machine. I change this WMQ port of queue manager to 1417. I believe this means that this queue manager is running on a WMQ port 1417. |
Ok, never used that panel, never plan to but doesn't seem (on my installation) to tie back to the listener port. I suspect it's used for something else, and await a passing IBMer to explain it.
| mqwbi wrote: |
| Question: I want to do change the WMQ Port permanently for a queue manager in AIX 5.3 and WMQ 6.0 . Can you please help? How can i see what is the current wmq port for the queue manager? |
It seems that the channel ports are controlled by the listener object(s). I'd stick with those. Port numbers can be displayed as attributes.
| mqwbi wrote: |
I want to create a WMQ 6.0 Cluster on AIX 5.3 . I understand that these will be the summary of steps to follow.
>> Choose queue manager for Full repository. Create Full repository.
>> Create listeners on each queue managers.
>> Create Sender-Receiver Channels |
You'll need 2 full repositories, and you of course means cluster sender/receivers.
| mqwbi wrote: |
| Do i use listener objects? |
Yes
| mqwbi wrote: |
| What is the difference between this port and the WMQ port specified in Scenario 1. |
I don't know.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sat Jan 03, 2009 4:44 am Post subject: Re: WMQ Port and Listeners |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Vitor wrote: |
| mqwbi wrote: |
| I see that TCP port is set to 1414. This is the default for all queue managers in this machine. I change this WMQ port of queue manager to 1417. I believe this means that this queue manager is running on a WMQ port 1417. |
Ok, never used that panel, never plan to but doesn't seem (on my installation) to tie back to the listener port. I suspect it's used for something else, and await a passing IBMer to explain it.
|
That attribute is the value that will be appended to a SNDR channel's CONNAME value if you don't explicitly specify a port number at the end of the CONNAME. When you leave off the port number in a channel definition, it doesn't default to 1414, it defaults to the value you have set at the QM level for "Port", (which is often still set to the default value of 1414).
If every QM in your company has a Listener on port 14523, and you for some reason did not want to append (14523) on all your channel definitions, then you could set the QM's Port attribute to 14523.
Best practice is to not rely on this value, but to explicitly code the port # into each channel's definition.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jan 03, 2009 4:55 am Post subject: Re: WMQ Port and Listeners |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
@ mqwbi
| PeterPotkay wrote: |
If every QM in your company has a Listener on port 14523, and you for some reason did not want to append (14523) on all your channel definitions, then you could set the QM's Port attribute to 14523.
Best practice is to not rely on this value, but to explicitly code the port # into each channel's definition. |
In fact it is recommended not to use this value. Imagine the upheaval in your environment if you were to change the value from 1414 to say 14523. Now all your default definitions that used to work don't any more....
That's also another reason why it is recommended to explicitly specify the port # on any sender/clusrcvr channel. Same for listener objects. Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqwbi |
| Posted: Sun Jan 04, 2009 12:07 am Post subject: Can you please approve of my understanding of your replies |
|
|
Novice
Joined: 15 Dec 2008
Posts: 24
|
Thank You for your help!!
This is what i understand. Please correct me, if wrong.
The WMQ port (mentioned in scenario 1) is the Queue Manager Port. When defining Sender and Receiver Channels, if i do not mention the port in the connection name, it will take the WMQ Port value for the Sender/Receiver channel definition.
When defining sender/receiver channels:
Say, if i define a listener for this queue manager A on port 1417. And a remote queue manager B has defined a sender channel to the queue manager A on port 1418. Will it be a problem estabilishing connection?
What if i want to run a queue manager permanently on WMQ Port 1420 (Scenario 1). How do i go ahead with this?
I read somewhere that i can use runmqlsr and run it as a background process. In that situation, how will i ensure that when my machine is restarted, or my queue manager is restarted, will it still continue to use WMQ Port 1420 if i use runmqlsr?
Thank You once again |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Jan 04, 2009 2:52 am Post subject: Re: Can you please approve of my understanding of your repli |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqwbi wrote: |
I read somewhere that i can use runmqlsr and run it as a background process. In that situation, how will i ensure that when my machine is restarted, or my queue manager is restarted, will it still continue to use WMQ Port 1420 if i use runmqlsr?
|
You should also have read that runmqlsr is depreciated in versions past v6 and you should use the listener object in preference.
All of your other points are answered by following the advice of fjb_saper and using explicit port numbers, as recommended.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Jan 04, 2009 4:50 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And yes you will run into problems if the Listener for QMGR A is defined on port 1417 and the sender channel from B to A has 1418 defined.
The channel will never run. It needs to use the target qmgr's port number.
Have fun
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
