BusinessEvents Monitoring and Management Configuration : Configuring the Connection between MM Server and the Monitored Cluster

Configuring the Connection between MM Server and the Monitored Cluster
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.
All agents and nodes to be monitored must belong to the same BusinessEvents cluster (that is, have the same cluster name). That cluster must use Cache based object management.
 
Task A Ensure the Topology File of the Monitored Cluster is Configured
Before you begin configuring MM itself to monitor and manage a cluster, you must specify and configure the topology of that cluster. See Chapter 5, Site Topology Configuration for details. In particular check the following:
In the Cluster settings, set the Master CDD and Master EAR locations. These locations are where the MM Server finds the CDD and EAR for deployment. The master files must be located in the same host where the MM server is running.
In the Deployment Unit settings, set the location where the MM Server will deploy the CDD and EAR files. This is the location on the machine hosting the deployment unit, as specified in the deployment mapping. The deployment mapping allows the user to specify which deployment units must be deployed to each host listed in the hosts section of the topology file.
Task B Configure Software for Remote Invocation
For secure data exchange and remote invocation between the MM server and the cluster machines you use one or more of the following utilities.
You can use more than one utility. However it is recommended that you choose only one.
The utility you use for each client machine is specified in the host configuration section of the topology file. See Start PU Method Setting.
Ensure that the software you choose is installed and running on all the relevant machines.
TIBCO Hawk
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).
Regardless of which software you use for remote invocations, you may wish to use Hawk® for engine-level monitoring. Machine-level monitoring is only available through Hawk. See Install and Configure TIBCO Hawk for Machine Level Metrics.
PsTools
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.
To use PsTools you must download it to BE_HOME/mm/bin/pstools.
Client machines, however, can use any OS, and don’t require any software to be installed. They do have to allow remote sessions.
SSH
Only SSH enables you to deploy BusinessEvents software to the predefined hosts, as configured in the monitored cluster’s topology file.
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.
Ensure any client machines that are configured to use SSH have this utility installed and running.
Task C Install and Configure TIBCO Hawk for Machine Level Metrics
If you want to monitor machine level metrics, you must use TIBCO Hawk software. If you use Hawk, you also need to use Rendezvous.
Install TIBCO Hawk and Rendezvous
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.
Configure a Hawk Domain
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.
Specify any Non Default Domain Values in the MM CDD File
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:
tibco.clientVar.Domain=TIBCO Hawk Domain
tibco.clientVar.TIBHawkDaemon=Rendezvous daemon used by Hawk
tibco.clientVar.TIBHawkNetWork=Rendezvous network used by Hawk
tibco.clientVar.TIBHawkService=Rendezvous service used by Hawk
Specify Hawk and Rendezvous in the be-mm.tra File
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.
Task D Configure JMX Properties in Monitored Engine TRA Files
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.
In the current release, JMX with SSL and authentication are not supported.
JMX properties are provided in the shipped BE_HOME/bin/be-engine.tra file but are commented. Uncomment the properties.

 
# Un-comment the following JMX management and monitoring Properties for working with MM
# Set the value of property java.property.com.sun.management.jmxremote.port to %jmx_port%
# When starting BE-engine from command line using this be-engine.tra file,
# add the option "--propVar jmx_port=[the port number of your choice]"
#
#java.property.com.sun.management.jmxremote.ssl=false
#java.property.com.sun.management.jmxremote.port=%jmx_port%
#java.property.com.sun.management.jmxremote.authenticate=false

 
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.
Task E Specify the Location of the Monitored Cluster’s Topology File in MM.cdd
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.
The topology file must be located on the same machine as the machine where MM is running. You can move the file from its design-time location as needed.
See Configuring MM Settings in the MM CDD File for more details.