Controlling the WebSphere MQ configuration and monitoring extensions on UNIX platforms
WebSphere MQ Configuration and Monitoring Extensions runs as a Java process. If you want to work directly with the process, use the ps command to find the active Java processes.
- Open a command prompt and change to the directory containing the distributed files.
- Enter the extension command (qpmon or qpcfg) followed by the required command parameter as described in the table below. For example,
qpcfg --startstarts the configuration extension;qpmon --stopstops the monitoring extension.
Note
Command parameters |
|
|---|---|
| Run the extension program in the foreground, displaying log messages as they are generated. It is useful when trying to locate or troubleshoot problems. |
| List the available command prompt options (this list) and short descriptions. |
| Set the host of the TMTM Topic Service so that the monitoring extension can pass its information to it. host is the host name or IP address of the TMTM Topic Service. |
| Set the port of the TMTM Topic Service so that the monitoring extension can pass its information to it. port is the port number of the TMTM Topic Service. |
| Start the extension. (Optional) Using cron or the /etc/rc.d/init.d directory, configure the WebSphere MQ Configuration and Monitoring Extensions to start automatically when the computer is restarted. |
| Provides an execution status for the extension. |
| Stop the extension. |
| Displays version information for the extension. |
Ctrl+c | Stop the extension. This is used in console mode. The command both stops the extension and exits console mode. |
Note
Permission to alter WebSphere MQ objects is set by the user who starts the configuration extension.
For information about how to secure individual agents, see Managing WebSphere MQ object security.
Comments