Local and remote administration

We can administer IBM MQ objects locally or remotely.

Local administration

Local administration means carrying out administration tasks on any queue managers we have defined on your local system. We can access other systems, for example through the TCP/IP terminal emulation program telnet, and carry out administration there. In IBM MQ, we can consider this as local administration because no channels are involved, that is, the communication is managed by the operating system.

Remote administration

IBM MQ supports administration from a single point of contact through remote administration. Remote administration allows you to issue commands from your local system that are processed on another system and applies also to the IBM MQ Explorer. For example, we can issue a remote command to change a queue definition on a remote queue manager. You do not have to log on to that system, although you do need to have the appropriate channels defined. The queue manager and command server on the target system must be running.

Some commands cannot be issued in this way, in particular, creating or starting queue managers and starting command servers. To perform this type of task, you must either log on to the remote system and issue the commands from there or create a process that can issue the commands for you. This restriction applies also to the IBM MQ Explorer.

Administer remote IBM MQ objects describes the subject of remote administration in greater detail.