Basic MM Configuration : Install and Configure TIBCO Hawk for Machine Level Metrics

Install and Configure TIBCO Hawk for Machine Level Metrics
If you want to monitor machine level statistics, you must use TIBCO Hawk software. If you use Hawk, you also need to use TIBCO Rendezvous as the transport.
Using Hawk allows you to visualize machine-level metrics in the MM UI. These machine-level metrics are made available by Hawk micro agents. 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.
Hawk can also be used for starting remote engines. See Install and Configure Software for Remote Start and Deployment for other options. The configuration shown here is used for both purposes.
1.
Install TIBCO Hawk and TIBCO Rendezvous software on the MM server machine, and on all client machines in the BusinessEvents cluster whose machine-level metrics you want to monitor.
2.
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.
Use the same Hawk domain name and Rendezvous transport for all the monitored engines and for the emonitor application.
3.
Import the BE_HOME/MM/project/emonitor project into your workspace and edit the MM.cdd. If you copy files into the workspace, remember to copy the MM.cdd file to the above location. In the mm-class agent properties list, add the following property to specify the Hawk domain:
   tibco.clientVar.Domain=TIBCO Hawk Domain
4.
If you use non-default values for the Hawk transport properties, you must specify them, also in the mm-class agent properties list in the MM.cdd. The properties are as follows:
   tibco.clientVar.TIBHawkDaemon=Rendezvous daemon used by Hawk
   tibco.clientVar.TIBHawkNetWork=Rendezvous network used by Hawk
   tibco.clientVar.TIBHawkService=Rendezvous service used by Hawk
To use the default client socket, omit the daemon argument. Default service is 7474, and daemon is tcp:7474. See Hawk documentation for additional information.
5.
Add the same properties you added to the MM.cdd file in step 3 and step 4 to the monitored project’s CDD file, in the Cluster tab properties sheet.
6.
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.
7.