Cluster membership and IBM MQ Explorer

IBM MQ Explorer requires information about queue managers that are members of a cluster.

If a queue manager is a member of a cluster, then the cluster tree node will be populated automatically.

If queue managers become members of clusters while the IBM MQ Explorer is running, then we must maintain the IBM MQ Explorer with up-to-date administration data about clusters so that it can communicate effectively with them and display correct cluster information when requested. In order to do this, the IBM MQ Explorer needs the following information:

• The name of a repository queue manager
• The connection name of the repository queue manager if it is on a remote queue manager

With this information, the IBM MQ Explorer can:

• Use the repository queue manager to obtain a list of queue managers in the cluster.
• Administer the queue managers that are members of the cluster and are on supported platforms and command levels.

Administration is not possible if:

• The chosen repository becomes unavailable. The IBM MQ Explorer does not automatically switch to an alternative repository.
• The chosen repository cannot be contacted over TCP/IP.
• The chosen repository is running on a queue manager that is running on a platform and command level not supported by the IBM MQ Explorer.

The cluster members that can be administered can be local, or they can be remote if they can be contacted using TCP/IP. The IBM MQ Explorer connects to local queue managers that are members of a cluster directly, without using a client connection.

Parent topic: Set up the IBM MQ Explorer