Work with remote IBM MQ objects

We can administer IBM MQ objects on remote queue managers by using MQSC commands, PCF commands, or the administrative REST API. Before we can use any of these methods, you must define transmission queues and channels between the local queue manager and the remote queue manager so that commands can be sent to the remote queue manager, and responses received by the local queue manager. Alternatively, we can configure a queue manager cluster, and then use the same remote administration methods.

To prepare queue managers for remote administration, we must configure the following objects on the local queue manager:

• A listener.
• A transmission queue that has the name of the remote queue manager.
• A sender channel that has the connection details for the remote queue manager.
• A receiver channel that has the same name as the sender channel on the remote queue manager.

We must also configure the following objects on the remote queue manager:

• A listener.
• A transmission queue that has the name of the local queue manager.
• A sender channel that has the connection details for the local queue manager.
• A receiver channel that has the same name as the sender channel on the local queue manager.

For more information about configuring these objects, see Configure queue managers for remote administration.

Alternatively, we can configure a queue manager cluster. A cluster is a group of queue managers set up in such a way that the queue managers can communicate directly with one another over a single network without complex transmission queue, channel, and queue definitions. Clusters can be set up easily, and typically contain queue managers that are logically related in some way and need to share data or applications. Even the smallest cluster reduces system administration costs.

Establishing a network of queue managers in a cluster involves fewer definitions than establishing a traditional distributed queuing environment. With fewer definitions to make, we can set up or change your network more quickly and easily, and reduce the risk of making an error in your definitions.

To set up a cluster, we need one cluster sender (CLUSSDR) and one cluster receiver (CLUSRCVR) definition for each queue manager. You do not need any transmission queue definitions or remote queue definitions. The principles of remote administration are the same when used within a cluster, but the definitions themselves are greatly simplified.

For more information about configuring a cluster, see Configure a queue manager cluster.

• Configure queue managers for remote administration
  We can administer a remote queue manager from a local queue manager by using the administrative REST API, MQSC, or PCF commands. The remote queue manager might be on the same system, in a different installation, or on a different system with the same environment, or a different IBM MQ environment. Before we can remotely administer a queue manager from a local queue manager, create a sender and receiver channel, a listener, and a transmission queue on each queue manager. These channels and queues enable the commands to be sent to the remote queue manager and the responses to be received on the local queue manager. The procedure to create these queues and channels is the same whether we want to use the administrative REST API, MQSC, or PCF commands.
• Manage the command server for remote administration
  Each queue manager has a command server associated with it. A command server processes any incoming commands from remote queue managers, or PCF commands from applications. It presents the commands to the queue manager for processing and returns a completion code or operator message. We can start, stop, and display the status of the command server. A command server is mandatory for all administration involving PCF commands, the MQAI, and also for remote administration.
• Issuing MQSC commands on a remote queue manager
  After you configure queue managers for remote administration, we can use a particular form of the runmqsc command on a local system to run MQSC commands on a remote queue manager. Each command is sent as an Escape PCF to the command queue, SYSTEM.ADMIN.COMMAND.QUEUE, of the remote queue manager. Replies are received on the SYSTEM.MQSC.REPLY.QUEUE queue.
• Data conversion
  Message data in IBM MQ defined formats (also known as built-in formats) can be converted by the queue manager from one coded character set to another, provided that both character sets relate to a single language or a group of similar languages.

Parent topic: Administer IBM MQ