Controlling the TIBCO Rendezvous monitoring extension on Windows or UNIX platforms
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 qptibrv (Windows) qptibrv.sh (UNIX) followed by the required command parameter.
To list all available command parameters, enter:
For Windows: qptibrv --help
For UNIX: ./qptibrv.sh --help
For example, in Windows qptibrv --start starts the monitoring extension; in UNIX ./qptibrv.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 the ps command to find the active Java process.
Parameter | Options |
|---|---|
--config | Set the host and port of the TMTM Topic Service so that the monitoring extension can pass its information to it. |
| -host:name Name is the host name or IP address of the TMTM Topic Service. Optional. |
| -port:number Number is the port number of the TMTM Topic Service. The default port is 15001. Optional. |
--console | Run the monitoring extension in the foreground, displaying log messages as they are generated. It is useful when trying to locate or troubleshoot problems. |
--help | List the available command prompt options (this list) and short descriptions |
--install | Install the monitoring extension as a Windows Service. |
--registera | Registers a TIBCO Rendezvous daemon and its objects for monitoring. If you want to change or remove a topic, URL, service, TIBCO Rendezvous agent, or TIBCO Rendezvous cache from monitoring, first use the --unregister command to unregister the entire daemon and then re-register the daemon with your new settings using this --register command. |
| -rvd:service:network:daemon -rvrd:service:network:daemon -rvsd:service:network:daemon -rvsrd:service:network:daemon where: If you do not define a service, network, or daemon, then TrueSight Middleware and Transaction Monitor uses the default from TIBCO Rendezvous. |
| -http:URL:port[:user:password] :URL:port Specify the URL to retrieve administrative information to report as part of the monitoring. Required. :user:password user name and password are required if you are connecting to a secure URL. |
| -daemoncert:any Specify the daemon certificate type to use when connecting to a TIBCO Rendezvous secure daemon or a TIBCO Rendezvous secure routing daemon. :any Any certificate name is used. |
| -daemonuser:user:password Specify the user name and password to use when connecting to a TIBCO Rendezvous secure daemon or a TIBCO Rendezvous secure routing daemon. |
| -daemonusercert:user-certificate-path:certificate-password Specify a user certificate file for connecting to the daemon. :user-certificate-path |
| -rva:agent:port[:user:password] Specify whether the TIBCO Rendezvous agent should be monitored and the name and port number of the TIBCO Rendezvous agent. A user name and password are required if you are connecting to a secure TIBCO Rendezvous agent |
| -rvcache:cache:port[:user:password] Specify whether the TIBCO Rendezvous cache should be monitored. and the name and port number of the TIBCO Rendezvous cache. A user name and password are required if you are connecting to a secure TIBCO Rendezvous cache. |
| -service:service1 -service:service2 Specify additional services to monitor. A TIBCO Rendezvous daemon can have more than one service. In addition to the service that you register using -rvd:service, you can specify as many additional services as you want by adding more -service: parameters so that each one is monitored. |
| -topic:name1[:yes|no] -topic:name2:[yes|no] Specify the topic or topics to monitor. You can specify as many topics as you wish by adding more -topic: parameters. The TIBCO Rendezvous wildcards * and > are supported in topic names (for instance, TOPIC.INBOUND.* or TOPIC.OUTBOUND.>. :yes | :no If you use a wildcard when defining your topics, TrueSight Middleware and Transaction Monitor collects and aggregates the statistical information into a single view. If you want statistical information (such as message count and average size) for each topic that matches the wildcard definition, then use the :yes option. If you do not need the individual information, use :no (or leave the option blank). The :no option is the default. |
--registration | Registers a TIBCO Rendezvous daemon and its objects for monitoring in an interactive mode. The same information in --register is presented line-by-line. See the inline instructions for details. |
--remove | Remove the monitoring extension from the Windows registry. |
--start | Start the monitoring extension. |
--status | Display the current status (running or stopped) of the monitoring extension. |
--stop | Stop the monitoring extension. |
--unregister | Unregister a TIBCO Rendezvous daemon and its objects from monitoring. If you need to remove a topic, URL, or service from monitoring, first use this --unregister command to unregister the entire daemon and then re-register the daemon with your new settings |
| -rvd:service:network:daemon where: If you do not define a service, network, or daemon, then TrueSight Middleware and Transaction Monitor uses the default from TIBCO Rendezvous. |
--version | Displays version information for the monitoring extension. |
Ctrl+c | Stop the monitoring extension. This is used in console mode. The command both stops the monitoring extension and exits console mode. |