Enable remote administration of queue managers

In IBM MQ Explorer, we can administer queue managers that are hosted by other computers connected to your computer by TCP/IP. This includes queue managers that are hosted on z/OS .


It is possible to connect to a remote queue manager using a different transport protocol but the connection must go through another queue manager to which IBM MQ Explorer is connected.

To remotely administer a queue manager, the queue manager must be running and we must:


Procedure

  1. Ensure that there is a running command server.
  2. Create a server-connection channel to allow remote administration of the queue manager over TCP/IP.
  3. Create a listener to accept incoming network connections.
  4. Ensure that the listener is running.

Parent topic: Administer remote queue managers

Any TCP/IP listener and any server-connection channel can be used for this administration.

If we are planning to administer a IBM WebSphere MQ Version 6.0 or later queue manager from a IBM WebSphere MQ Version 5.3 computer, we must enable the Version 6.0 or later queue manager for remote administration using the default SYSTEM.ADMIN.SVRCONN server connection channel. This is because IBM WebSphere MQ Version 5.3 must use the SYSTEM.ADMIN.SVRCONN server connection channel to connect to a remote queue manager.

If we are planning to administer a Version 6.0 or later queue manager from a IBM WebSphere MQ Version 6.0 Version 6 or later computer, we can either enable the Version 6.0 or later queue manager for remote administration using the default SYSTEM.ADMIN.SVRCONN server connection channel, or specify a different server connection channel when the remote computer connects to the queue manager.

We can enable remote administration on a queue manager on Windows or Linux (x86 and x86-64 platforms) computers using IBM MQ Explorer. On other platforms, we must configure the queue manager from the command line.

For more information, see Administer remote IBM MQ objects or Authority to administer IBM MQ on UNIX and Windows systems.