Use the IBM MQ Explorer with IBM MQ for IBM i

Use this information to administer IBM MQ for IBM i using the IBM MQ Explorer.

IBM MQ for Windows (x86 platform), and IBM MQ for Linux (x86 and x86-64 platforms) provide an administration interface called the IBM MQ Explorer to perform administration tasks as an alternative to using CL, control, or MQSC commands.

The IBM MQ Explorer allows you to perform local or remote administration of our network from a computer running Windows (x86 platform), or Linux (x86 and x86-64 platforms), by pointing the IBM MQ Explorer at the queue managers and clusters we are interested in. The platforms and levels of IBM MQ that can be administered using the IBM MQ Explorer are described in Remote queue managers.

With the IBM MQ Explorer, we can:

• Start and stop a queue manager (on your local machine only).
• Define, display, and alter the definitions of IBM MQ objects such as queues, topics, and channels.
• Browse the messages on a queue.
• Start and stop a channel.
• View status information about a channel.
• View queue managers in a cluster.
• Check to see which applications, users, or channels have a particular queue open.
• Create a new queue manager cluster using the Create New Cluster wizard.
• Add a queue manager to a cluster using the Add Queue Manager to Cluster wizard.
• Manage the authentication information object, used with Transport Layer Security (TLS) channel security.

Using the online guidance, we can:

• Define and control various resources including queue managers, queues, channels, process definitions, client connection channels, listeners, topics, services, namelists, and clusters.
• Start or stop a queue manager and its associated processes.
• View queue managers and their associated objects on your workstation or from other workstations.
• Check the status of queue managers, clusters, and channels.

Ensure that we have satisfied the following requirements before attempting to use the IBM MQ Explorer to manage IBM MQ on a server machine. Check that:

1. A command server is running for any queue manager being administered, started on the server by the CL command STRMQMCSVR.
2. A suitable TCP/IP listener exists for every remote queue manager. This is the IBM MQ listener started by the STRMQMLSR command.
3. The server connection channel, called SYSTEM.ADMIN.SVRCONN, exists on every remote queue manager. We must create this channel yourself. It is mandatory for every remote queue manager being administered. Without it, remote administration is not possible.
4. Verify that the SYSTEM.MQEXPLORER.REPLY.MODEL queue exists.

Parent topic: Alternative ways of administering IBM MQ for IBM i