[MQ 9.4.0 Jun 2024]

IBM MQ Console: Adding a remote queue manager

You can use the IBM® MQ Console to administer a queue manager that is running on a remote system. A remote queue manager can be either a queue manager that is running in a different installation on the same system as the IBM MQ Console, or a queue manager that is running on a different system

About this task

This task covers the steps that are required to prepare the remote queue manager to be administered with the IBM MQ Console. After you complete these steps, you must complete one of the tasks in the what to do next section before the queue manager is ready to be used with the IBM MQ Console.

Note: The steps in this task require you to run MQSC commands:
Attention: if you receive the following messages:
MQWB2026E: The request to connect to the remote queue manager 'rqmgr-qmgr_name' failed with the error message:
'JMSCC0051: The property 'JMS_IBM_MQMD_AccountingToken' should be set using type '[B', not 'java.lang.Object'.'
you are attempting to pass a java.lang.Object to the accounting token, when a Java object type byte[] is expected.

Procedure

  1. If the mqweb server is not in a stand-alone IBM MQ Web Server installation, ensure that the mqweb server is configured to allow the IBM MQ Console to connect to remote queue managers:
    1. Check whether the mqweb server allows remote queue manager connections by entering the following command on the command line:
      dspmqweb properties -u

      If the property mqConsoleRemoteSupportEnabled appears in the output, and the property is set to true, then connections to remote queue managers are allowed.

    2. If the mqweb server does not allow remote queue manager connections, enable such connections by entering the following command on the command line:
      setmqweb properties -k mqConsoleRemoteSupportEnabled -v true
  2. On the remote queue manager, create a server-connection channel to allow remote administration of the queue manager by using the DEFINE CHANNEL MQSC command.
    For example, to create a server-connection channel QM1.SVRCONN for queue manager QM1, enter the following MQSC command:
    runmqsc QM1
    DEFINE CHANNEL(QM1.SVRCONN) CHLTYPE(SVRCONN) TRPTYPE(TCP)
    end
    For more information about DEFINE CHANNEL and the options available, see DEFINE CHANNEL.
  3. Ensure that appropriate users are authorized to administer the queue manager and objects that are associated with the queue manager.
  4. [AIX, Linux, Windows]If no listener is running on the remote queue manager, create a listener to accept incoming network connections by using the DEFINE LISTENER MQSC command.
    For example, to create a listener REMOTE.LISTENER on port 1414 for remote queue manager QM1, enter the following MQSC command:
    runmqsc QM1
    DEFINE LISTENER(REMOTE.LISTENER) TRPTYPE(TCP) PORT(1414)
    end
  5. Ensure that the listener is running by using the START LISTENER MQSC command.
    [AIX, Linux, Windows]For example, on AIX, Linux, and Windows to start the listener REMOTE.LISTENER for queue manager QM1, enter the following MQSC command:
    runmqsc QM1
    START LISTENER(REMOTE.LISTENER)
    end
    [z/OS]For example, on z/OS, to start the listener, enter the following MQSC command:
    /cpf START LISTENER TRPTYPE(TCP) PORT(1414)
    The channel initiator address space must be started before you can start a listener on z/OS.

What to do next

Add the remote queue manager to the IBM MQ Console by using one of the following methods: