Running the TIBCO EMS monitoring extension
This extension monitors and reports activity from TIBCO EMS servers. The information is then passed to the TMTM Extensible Agent. This section includes:
For information on installing this extension on the various supported platforms, see Installing the TIBCO EMS monitoring extension.
Some TIBCO EMS monitoring extension features are:
- monitoring of TIBCO EMS Server and associated static or dynamic objects
- parallel monitoring of multiple servers through a single TIBCO EMS monitoring extension
- monitoring of SSL-secured servers
- command prompt interface for administering the monitoring extension and retrieving EMS servers
- validation of monitored server information upon registration
Controlling the TIBCO EMS monitoring extension on Windows or UNIX
This monitoring extension is distributed as a zip file. It must be extracted before you can use it. After you have extracted the files from the archive into a directory (it must be a directory different than the TMTM Extensible Agent directory), BMC recommends installing it as a subdirectory of the TMTM Extensible Agent), use the --help
command parameter to list available command parameters.
- Open a command prompt and change to the directory containing the distributed files.
- Enter the monitoring extension command
qptibems
(Windows)qptibems.sh
(UNIX) followed by the required command parameter.
To list all available command parameters, enter:
For Windows:qptibems --help
For UNIX:./qptibems.sh --help
For example, in Windowsqptibems --start
starts the monitoring extension; in UNIX./qptibems.sh --start
starts the monitoring extension. The table below lists the available command parameters to support information available with the--help
parameter.
(UNIX only) TIBCO EMS monitoring extension (qptibems) runs as a Java process. If you want to work directly with the process, use theps
command to find the active Java process.
Note
Note
-validate
switch. Otherwise the command does not resolve to the objects on the server.Command parameters | Use to... |
---|---|
| Install the monitoring extension as a Windows Service. |
| Start the monitoring extension in the background. |
| Stop the monitoring extension. |
| Run the monitoring extension 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. |
| Display the current status (running or stopped) of the monitoring extension. |
| Display version information for the monitoring extension. |
| Remove the monitoring extension from the Windows registry. |
Ctrl+c | Stop the monitoring extension. This is used in console mode. The command both stops the monitoring extension and exits console mode. |
| Set the host and port of the TMTM Topic Service so that the monitoring extension can pass its information to it. |
Host name or IP address of the TMTM Topic Service. Optional. | |
Port used by the TMTM Topic Service. Optional. | |
| Registers an EMS server and its objects for monitoring. |
Name of the TIBCO EMS server. Required. Wildcards cannot be used when defining the server. | |
Name of the static queue. Wildcards are accepted. Dynamic or temporary queues cannot be registered for monitoring, but are registered as transient topics. You can only register static queues for monitoring with this command. Optional. | |
Name of the static topic. Wildcards are accepted. Dynamic or temporary topics cannot be registered for monitoring, but are registered as transient topics. You can only register static topics for monitoring with this command. Optional. | |
Name of the route. No wildcards are supported. Optional. | |
Name of the static durable subscriber. No wildcards are supported. Dynamic durables cannot be registered for monitoring, but are registered as transient topics. You can only register static durables for monitoring with this command. Optional. | |
Validate the server, queues, etc. Required if you used wildcards when defining any queues, topics, and so on. Any object that cannot be validated against the EMS server is ignored. | |
| Unregisters an EMS server and its objects from monitoring. |
Name of the TIBCO EMS server. Required. | |
Name of the static queue. Optional. | |
Name of the static topic. Optional. | |
Name of the route. Optional. | |
Name of the static durable subscriber. Optional. | |
| Adds an EMS server profile as a preference. |
Name of the TIBCO EMS server. Required. | |
URL used to connect to the TIBCO EMS server. Required. The syntax for URLs is: For further details, see the EMS documentation. | |
User name to connect to the TIBCO EMS server. Required. | |
Password to connect to the TIBCO EMS server. Required. | |
Name of the SSL certificate or identity file. | |
Encoding used for the SSL certificate. It can be one of the following:
| |
File containing the SSL private key. | |
Encoding used for the SSL private key. It can be one of the following:
| |
Password used for encrypting the certificate or key. | |
Validate the server, queues, etc. Required if you used wildcards when defining any queues, topics, and so on. Any object that cannot be validated against the EMS server is ignored. | |
| List the EMS server profiles that are stored as preferences. |
| Removes an EMS server profile from the preferences. |
Name of the TIBCO EMS server. Required. | |
| Alters an EMS server profile stored as a preference. |
Name of the server profile to be altered. Required. | |
New name of the TIBCO EMS server. Optional. | |
URL used to connect to the TIBCO EMS server. Optional. The syntax for URLs is: For further details, see the EMS documentation. | |
User name to connect to the TIBCO EMS server. Optional. | |
Password to connect to the TIBCO EMS server. Optional. | |
Name of the SSL certificate or identity file. | |
Encoding used for the SSL certificate. It can be one of the following:
| |
File containing the SSL private key. | |
Encoding used for the SSL private key. It can be one of the following:
| |
Password used for encrypting the certificate or key. | |
Validate the server, queues, etc. | |
| Retrieve the EMS server status and objects available. There are different options available depending on whether you are using a server profile stored as a preference to connect to the TIBCO EMS server. This section describes the options available if the TIBCO EMS server is stored as a preference. If the EMS server is not stored as a preference, see the |
Name of the TIBCO EMS server. Required. | |
Name of the queue. Optional. | |
Name of the topic. Optional. | |
Name of the route. Optional. | |
Name of the durable subscriber. Optional. | |
| Retrieve the EMS server status and objects available. There are different options available depending on whether you are using a server profile stored as a preference to connect to the TIBCO EMS server. This section describes the options available if the TIBCO EMS server is not stored as a preference. If the EMS server is stored as a preference, see the |
URL used to connect to the TIBCO EMS server. Optional. The syntax for URLs is: protocol://host:port For further details, see the EMS documentation. | |
User name to connect to the TIBCO EMS server. Optional. | |
Password to connect to the TIBCO EMS server. Optional. | |
Name of the SSL certificate or identity file. | |
Encoding used for the SSL certificate. It can be one of the following:
| |
File containing the SSL private key. | |
Encoding used for the SSL private key. It can be one of the following:
| |
Password used for encrypting the certificate or key. | |
Name of the queue. Optional. | |
Name of the topic. Optional. | |
Name of the route. Optional. | |
Name of the durable subscriber. Optional. |
Comments