Requirements for Remote Administration using the WebSphere MQ Explorer - Middleware News
Ensure that you have satisfied the following requirements before trying to use the WebSphere MQ Explorer to do remote administration. Verify that:
Using the WebSphere MQ Explorer for Remote Administration
Satisfy all of the requirements for Remote Administration and then you can use the WebSphere MQ to do administration tasks on your local and remote queue managers.
To show a remote queue manager, right click the WebSphere MQ Explorer Queue Manager folder, select Show/Hide, then select the Add button on the Add Queue Manager screen(see Figure 1 then type:
Reasons for Remote Administration failures:
Ensure that you have satisfied the following requirements before trying to use the WebSphere MQ Explorer to do remote administration. Verify that:
- The WebSphere MQ server and client is installed on the local and the remote machine.
- A command server is running for every queue manager.
- A TCP/IP listener exists for every queue manager. This can be the WebSphere MQ listener or the inetd daemon as appropriate for your operating system environment.
- 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.
- Create the channel using the following MQSC command:
DEFINE CHANNEL(SYSTEM.ADMIN.SVRCONN) CHLTYPE(SVRCONN). - The userID of the initiator must be a member of the "mqm" group on the local and remote machine. The model queue SYSTEM.MQEXPLORER.REPLY.MODEL must exists on every queue manager.
- Create the queue using the following MQSC command: DEFINE QMODEL(SYSTEM.MQEXPLORER.REPLY.MODEL)
Using the WebSphere MQ Explorer for Remote Administration
Satisfy all of the requirements for Remote Administration and then you can use the WebSphere MQ to do administration tasks on your local and remote queue managers.
To show a remote queue manager, right click the WebSphere MQ Explorer Queue Manager folder, select Show/Hide, then select the Add button on the Add Queue Manager screen(see Figure 1 then type:
- The name of the remote queue manager and press the Next button.
- Select the Specify connection details radio button(see Figure 2).
- Type the host name or IP address of the remote queue manager and listener port and press the Finish button.
Reasons for Remote Administration failures:
- The Command server is not running on remote queue manager. Message AMQ4042 will be issued.
- The Listener is not running on remote queue manager. Message AMQ4043 will be issued.
- The SYSTEM.ADMIN.SVRCONN is not defined on remote queue manager. Message AMQ4043 will be issued.
- The security check failed on remote queue manager. Message AMQ4043 will be issued.
- Prior releases of WebSphere MQ for z/OS (v5.3 and v5.3.1) do not provide this function and any attempt to remotely administer a queue manager will fail. The WebSphere MQ V6.0 product has been enhanced to support the remote administration of a z/OS queue manager using the WebSphere MQ Explorer on Windows and Linux Intel.
- Code page conversion failures can cause problems. Message AMQ4043 will be issued. For more information, see technote: Remote Administration through WebSphere MQ Explorer "Show Queue Manager" Fails AMQ4043
- The SYSTEM.MQEXPLORER.REPLY.MODEL is not defined on remote queue manager and you are using the V6.0 WebSphere MQ Explorer. Message AMQ4400 will be issued.
- The
Client attachment feature is not installed on WebSphere MQ for z/OS.
The CHIN joblog will contain message CSQX260E. To connect to the z/OS
queue manager using the SYSTEM.ADMIN.SVRCONN channel, you need to have
the Client Attachment feature installed, which is FMID JMS6007 for
WebSphere MQ for z/OS 6.0.0.
Note:
In WebSphere MQ V7 for z/OS you can create five “free” client attachments for use with MQ Explorer. These attachments must use the channel name SYSTEM.ADMIN.SVRCONN, which is the default channel name used by the MQ Explorer.
To use the free client attachments, you must first alter the SYSTEM.ADMIN.SVRCONN channel definition and set the maximum instances (MAXINST) attribute to 5 or less. You should also ensure that your server-connection channel is secured by the usual means.
Comments
Post a Comment