This section explains the steps required to connect the Monitoring and Management software (MM) with a target cluster that is to be monitored and managed. The tasks are arranged in a reasonable order, but a strict order is not required for many of them.
To use TIBCO Hawk® for remote invocations, you must have TIBCO Hawk installed and running on the MM server and on all the client machines that use this method. All machines in the same cluster must use the same TIBCO Hawk domain and use the same transport definitions (server, network, demon port).
PsTools is an open source Windows utility that enables execution on remote machines. It is used when MM runs on Windows and the target host also runs on Windows.
The SSH utility is available on UNIX machines by default. Download and install on any Windows machine that will use this method. TIBCO has tested with
Copssh. Note that
OpenSSH for Windows is not supported.
Install TIBCO Hawk and TIBCO Rendezvous software on the MM server machine, and all client machines in the BusinessEvents cluster whose machine-level metrics you want to monitor.
A Hawk domain specifies a group of TIBCO Hawk agents that acts as a monitoring set. Each machine has a Hawk agent and various micro agents (HMA) that provide useful machine-level metrics to the enterprise monitor.
Configuring a Hawk domain enables machine-level metrics that are made available by Hawk micro agents to be viewed in the Monitoring and Management component. If you do not configure a Hawk domain, the enterprise monitor won't show the machine-level metrics, but it will show all other levels of metrics.
Use the same Hawk domain name and Rendezvous transport for all the monitored processing unit, as they are configured for the emonitor application.
If you use non-default values, you must specify the Hawk domain name and TIBCO Rendezvous properties in the
mm-class agent properties list in the MM.cdd. You can alternatively provide the values in a property file used at the MM server startup. The properties are as follows:
In the BE_HOME\mm\bin\be-mm.tra file, set the
tibco.env.HAWK_HOME property and the
tibco.env.RV_HOME to point to the TIBCO Hawk and TIBCO Rendezvous installation root directories.
The running BusinessEvents engines use JMX MBeans to expose monitoring and management information to the client MM server. You must configure the TRA files for all monitored BusinessEvents engines.
JMX properties are provided in the shipped BE_HOME/bin/be-engine.tra file but are commented. Uncomment the properties.
To use MM to start BusinessEvents engines, you will need to set property java.property.com.sun.management.jmxremote.port using the variable
%jmx_port%. MM reads the JMX port number in the site topology file and passes it to the variable in the command line it composes when starting a BusinessEvents:
--propVar jmx_port=portnum. The JMX port number in turn is passed to the
java.property.com.sun.management.jmxremote.port property.
Set the property be.mm.topology.file, located in the
mm-class agent properties, within the Agent Classes tab of the CDD editor. This topology file provides the MM server with the necessary information about the cluster it is to monitor at runtime.