Stopping the Original Default Queue Manager Listener
1.
|
Select Console Root ==> WebSphere MQ Services (local) ==> ( the original default queue manager name).
|
This will cause a list of services to be displayed, one of which is the "listener" service.
2.
|
Right-click on "listener ==> properties" and stop the listener.
|
3.
|
Change the startup from Automatic to Manual.
|
This listener should no longer start-up at reboot.
Create New Queue Manager Listener for New Queue Manager
1.
|
Select Console Root ==> WebSphere MQ Services (local) ==> NMS_MGR.A ==> New ==> Listener.
|
This will invoke a dialog to create a new "listener" service. This dialog will have three tabs, General, Recovery, and Parameters.
•
|
The Parameters tab port number must be 1414.
|
•
|
The General tab startup type should be "Automatic".
|
2.
|
Click the Start button on the General tab.
|
3.
|
To check the status of the listener, select Console Root ==> WebSphere MQ Services (local) ==> NMS_MGR.A ==> Listener ==> Properties
|
Set Environment Variables
The environment configuration file (nms.rc), which is a data file listing Oracle Utilities Network Management System environment settings, should have the following:
export MQSERVER=SCH1/TCP/10.115.3.85
The environment configuration file must also have two variables set to locate the .TAB file for WebSphere MQ. The .TAB must be copied to the MQ client from the MQ server host as specified by these variables.
export MQCHLLIB=/users/proj/MQ
export MQCHLTAB=AMQCLCHL.TAB
View this environment variable (to ensure that it’s correct) by typing in the following command: echo $MQSERVER
Test the Connection Between MQ Client and MQ Server
Test the Server Connection Channel (amqscnxc)
On the Unix command line, type in the following command:
/usr/mqm/samp/bin/amqscnxc -x 10.115.3.85 -c SCH1 NMS_MGR.A
•
|
-x is the IP address of the MQ Server host
|
•
|
-c is the Server Connection Channel Name
|
•
|
the third parameter is the desired Queue Manager Name
|
Test ‘Putting’ a message from Server to Client (amqsputc)
On the Unix command line, type in the following command:
/usr/mqm/samp/bin/amqsputc NMS.A.FROMNMS Sample AMQSPUT0 starttarget queue is NMS.A.FROMNMS
<MSG-FROM-SVR>VOILA</MSG-FROM-SVR> Sample AMQSPUT0 end
The message should appear in the queue named NMS.A.FROMNMS which can be viewed on the client using the MQ Explorer GUI at:
Console Root ==> WebSphere MQ ==> Queue Managers ==> NMS_MGR.A ==>Queues ==> NMS.A.FROMNMS ==> Browse Messages
Test ‘Getting’ a Message on Client from Server (amqsgetc)
First "get" the message just written
/usr/mqm/samp/bin/amqsgetc NMS.A.FROMNMS Sample AMQSGET0 start message <<MSG-FROM-SVR>VOILA</MSG-FROM-SVR>> no more messages Sample AMQSGET0 end
Test ‘Putting’ a Message from Client to Server using WebSphere MQ GUI
1.
|
Select Console Root ==> WebSphere MQ ==> Queue Managers ==> NMS_MGR.A ==> Queues ==> NMS.A.TONMS ==> Put Test Message
|
2.
|
Paste the following into "Message Data":
|
<MSG-FROM-CLNT>VOILA</MSG-FROM-CLNT>
The following message should be displayed: "The test message was put successfully (amq4016)".
Test ‘Getting’ a Message on Server from Client (amqsgetc)
On the Unix command line:
/usr/mqm/samp/bin/amqsgetc NMS.A.TONMS Sample AMQSGET0 start message <<MSG-FROM-CLNT>VOILA</MSG-FROM-CLNT>> no more messages Sample AMQSGET0 end