http://www.wikio.fr WebSphere And Tivoli Tricks: How to create a listener for a Message Queue

Tuesday, May 17, 2011

How to create a listener for a Message Queue

Sample: Queue Manager = QM_ORANGE


Run the message queue manager script command tool


[mqm@websphere2 ~]$ runmqsc
5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QM_ORANGE.


Create the listener


DEFINE LISTENER(qm_orange.listener) TRPTYPE (TCP) PORT(60000)
1 : DEFINE LISTENER(qm_orange.listener) TRPTYPE (TCP) PORT(60000)
AMQ8626: WebSphere MQ listener created.
start listener(qm_orange.listener)
2 : start listener(qm_orange.listener)
AMQ8021: Request to start WebSphere MQ Listener accepted.
end
3 : end
2 MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.


Check to see if the listener is running as a process


[mqm@websphere2 ~]$ ps -ef | grep qm_orange.listener
mqm 12809 12709 0 22:18 pts/2 00:00:00 grep qm_orange.listener


Check to ensure port is an open (any adapter i.e not bound to any specific adapter) listener


[mqm@websphere2 ~]$ netstat -an | grep 60000
tcp 0 0 :::60000 :::* LISTEN


Create Channel


The server-connection channel, called SYSTEM.ADMIN.SVRCONN, exists on every remote queue manager. This channel is mandatory for every remote queue manager being administered. Without it, remote administration is not possible.


You can create the channel using the following MQSC command:
DEFINE CHANNEL(SYSTEM.ADMIN.SVRCONN) CHLTYPE(SVRCONN)
This command creates a basic channel definition. If you want a more sophisticated definition (to set up security, for example), you need additional parameters.


[mqm@websphere2 ~]$ runmqsc
5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED.
Starting MQSC for queue manager QM_ORANGE.


DEFINE CHANNEL(SYSTEM.ADMIN.SVRCONN) CHLTYPE(SVRCONN)
1 : DEFINE CHANNEL(SYSTEM.ADMIN.SVRCONN) CHLTYPE(SVRCONN)
AMQ8014: WebSphere MQ channel created.
end
2 : end
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.

No comments:

Post a Comment