Connecting to a remote cluster queue manager

We can connect IBM MQ Explorer to a remote queue manager by using the cluster information source as an intermediary queue manager.

If a remote queue manager belongs to a cluster that is displayed in IBM MQ Explorer but IBM MQ Explorer does not know anything about the queue manager, the queue manager's icon shows that it is not connected. For IBM MQ Explorer to get information about the remote queue manager, it must connect to the queue manager. Of course, if we don't know the connection details of the queue manager, we cannot easily add it to the Queue Managers folder, and you might not want to be able to administer the queue manager anyway. Therefore, we can connect IBM MQ Explorer to the remote queue manager using the cluster information source as an intermediary queue manager.

For example, if QMX is the full repository queue manager from which IBM MQ Explorer obtains all its information about the cluster, we can connect to QMZ, the remote cluster queue manager, using QMX as an intermediary queue manager. This means that IBM MQ Explorer does not need to know the connection details of the remote cluster queue manager because QMX, the cluster's full repository queue manager, already has this information.

When IBM MQ Explorer is connected to the remote cluster queue manager, if you want to administer the remote cluster queue manager, we can then show the queue manager in the Queue Managers folder.

To connect to a remote cluster queue manager, in the Navigator view (in the Queue Manager Clusters folder), right-click the queue manager, and then click Connect to queue manager.

IBM MQ Explorer connects to the remote cluster queue manager using the full repository queue manager that is IBM MQ Explorer's information source about the cluster. Click the queue manager to display its cluster queues and cluster channels in the Content view.

For more information, see Distributed queuing and clusters in the IBM MQ online product documentation.