| Author |
Message
|
| dennis.jacob |
 Posted: Thu Aug 07, 2008 2:24 am Post subject: Creation of queue manager |
 |
|
Newbie
Joined: 05 Aug 2008
Posts: 8
|
All,
I am using MQ 5.3 on SuSe Linux and AIX.
Request your help in the below topics.
- How to create the queue manager with port number
- How to find the queue manager port if it the queue maneger already running
- Will the MQ listener will automatically start if the Queue Manager is started? |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Thu Aug 07, 2008 2:33 am Post subject: Re: Creation of queue manager |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
First of all read PDF's
| dennis.jacob wrote: |
- How to create the queue manager with port number
|
you cant create a queueu manager with port number specified to it
by default it should be 1414
you can change it later
| dennis.jacob wrote: |
- How to find the queue manager port if it the queue maneger already running
|
ps -ef | grep -i runmqlsr
| dennis.jacob wrote: |
- Will the MQ listener will automatically start if the Queue Manager is started? |
From MQ V6 onwards, yes, it starts automatically,
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| AkankshA |
| Posted: Thu Aug 07, 2008 2:33 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
How to create the queue manager with port number
create the queue manager first and then create a listener for it using runmqlsr...
How to find the queue manager port if it the queue maneger already running
ps -ef | grep runmqlsr
Will the MQ listener will automatically start if the Queue Manager is started?
No.. not in MQ 5.3
Pls do read the MQ intercommunication/Fundamentals manual
_________________
Cheers |
|
| Back to top |
|
|
| dennis.jacob |
| Posted: Thu Aug 07, 2008 2:42 am Post subject: |
|
|
Newbie
Joined: 05 Aug 2008
Posts: 8
|
Thanks for all your reply. I am new to MQ and going through the MQ docs as well to learn it asap.
Regarding my query, see this :
the queue manager is running, but am not abel to find the listener.Please advise.
[/home/usr1 ]>ps -ef | grep -i runmqlsr
tf01 2007180 774198 1 10:39:34 pts/5 0:00 grep -i runmqlsr
[/home/usr1 ]>dspmq
QMNAME(QM.A102328) STATUS(Running)
[/home/usr1 ]>runmqsc QM.A102328
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QM.A102328.
end
1 : end
No MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed. |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Aug 07, 2008 2:51 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
A listener has a port number assigned (if TCP), not the queue manager as such.
A queue manager could have several listeners. Make sure the port number is unique on the platform as there could be several queue managers defined. |
|
| Back to top |
|
|
| dennis.jacob |
| Posted: Thu Aug 07, 2008 3:12 am Post subject: |
|
|
Newbie
Joined: 05 Aug 2008
Posts: 8
|
| zpat wrote: |
A listener has a port number assigned (if TCP), not the queue manager as such.
A queue manager could have several listeners. Make sure the port number is unique on the platform as there could be several queue managers defined. |
Correct me if am wrong.
- A QM requires atleast a listener.If that is the case, there needs to be listener displayed if I am 'grep'ing for listener. But it si not showing anything |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Aug 07, 2008 3:21 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Have you defined a Listener by running the runmqlsr command? WMQ does not automatically set up a Listener for you.
Edit: sorry, forgot to mention that it could be set up in inetd instead.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Last edited by exerk on Thu Aug 07, 2008 3:24 am; edited 1 time in total |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Thu Aug 07, 2008 3:21 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
there is a file called
/etc/services in Unix/Linux
talk to your Unix Admin and get the Port number get updates over there
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Aug 07, 2008 3:31 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
You can have a queue manager without a listener.
Possibly not a lot of use other than for messaging between applications on the same platform. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Thu Aug 07, 2008 4:42 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
It is not recommended in MQ5.3 to use inetd to control your MQ listeners.
It is better to start the listener manually using the 'runmqlsr' command with the parameters specified in the System Admin manual. In most cases, only one listener is required for a queue manager.
Ask your unix admin how to include "nohup", "/dev/null" and "&" with the runmqlsr command so it runs in the background.
If you want the listener to start and stop automatically when the queue manager starts and stops, you must script that yourself. If you want the listener to start automatically when the server is rebooted, you must script the start command and have the script installed in a start directory (such as an 'rc' directory).
Best of all is to use MQv6.0, which allows creation of a listener as an MQ object that can be controlled by the queue manager itself! |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Aug 07, 2008 4:52 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| SAFraser wrote: |
| It is not recommended in MQ5.3 to use inetd to control your MQ listeners... |
A ggod point, and well made. There are however shops that have upgraded from v5.2 -> v5.3 and retained the 'old' method of firing up the Listeners - this is my second one 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Thu Aug 07, 2008 5:52 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
| exerk - Oh, me too. Upgraded and just let inetd run from benign neglect, eventually fixing it to runmqlsr with a little script to start and stop in runtime with the queue manager. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Aug 07, 2008 6:14 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
When the whole world takes the path of righteousness - upgrading to version 6 or above that is - all will be well, and control of WMQ resources can pass back to the rightful owners 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| dennis.jacob |
| Posted: Thu Aug 07, 2008 7:24 pm Post subject: |
|
|
Newbie
Joined: 05 Aug 2008
Posts: 8
|
Thaks All for your inputs.
But what puzzling me is that there are no listeners running.But there is entry in the /etc/services. And the QM in this host is communicating well to the QM in other machines
So shall I conclude that
- either the MQ listener msut be running
- or, there must be entry in /etc/services.
If that is the case,
If I am creating a new QM, it will have the basic port 1414. And now, either I can go for running MQ listener or adding an entry in /etc/services ?? In the latter case, should I restart the machine after adding entry in /etc/services? |
|
| Back to top |
|
|
| David.Partridge |
| Posted: Thu Aug 07, 2008 11:11 pm Post subject: |
|
|
Master
Joined: 28 Jun 2001
Posts: 249
|
No,
If you create a new QM, it will not have a listener to start with apart from the SYSTEM.DEFAULT.LISTENER.TCP which is intended for use as a template and doesn't have a port number associated with it.
Assuming you are using MQ 6, you will need to define a listener to the queue manager. For example using the mqsc commands:
DEFINE LISTENER(MYQM.LISTENER.TCP) TRPTYPE(TCP) PORT(1414) CONTROL(QMGR)
START LISTENER(MYQM.LISTENER.TCP)
Here's the display of the listener on one of the QM's (LOM1) that I look after:
4 : dis listener(lom*) all
AMQ8630: Display listener information details.
LISTENER(LOM1.LISTENER.TCP) CONTROL(QMGR)
TRPTYPE(TCP) PORT(1414)
IPADDR(10.160.208.1 BACKLOG(0)
DESCR( ) ALTDATE(2008-08-07)
ALTTIME(13.31.32)
This one also specifies ipaddr so that it only accepts connections from one of the the network interfaces.
I strongly advise that you get yourself booked on an MQ training course. MQ isn't an easy product to learn by just reading the manuals (though it's way easier than the broker).
_________________
Cheers,
David C. Partridge |
|
| Back to top |
|
|
|
|
