Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 5 TIBCO BusinessEvents Monitoring and Management Tutorial : Configure Openssh, TIBCO Hawk, and TRA File

Configure Openssh, TIBCO Hawk, and TRA File
Before you begin to work with TIBCO BusinessEvents Monitoring and Management (MM) you must first install a utility and configure JMX properties. For machine level metrics you must install and configure TIBCO Hawk. For the purposes of the tutorial, the TIBCO Hawk requirement is optional.
 
Task A Install Openssh Software for Remote Start and Deployment
Ensure that Openssh software is installed and the server is running. You can use the user credentials that you used to install the SSH server (typically with administrative privileges) as the SSH login, to authenticate the host.
You can also enable a SSH to allow users other than root to login. These users may have a different set of privileges than root. Ensure that the username you choose can log on to the machine you are using for this tutorial.You can use your own credentials. Provide the user’s password as the "passphrase".
Task B Configure a JMX Property in Monitored Engine TRA Files
Running engines use JMX MBeans to expose monitoring and management information to the MM server, and for remote method invocation.
Open the BE_HOME/bin/be-engine.tra. Uncomment the jmxremote property shown next. Ensure that the value of the port property is set to %jmx_port%. You will specify the actual port value in the JMX Port field in the site topology file Processing Unit Configuration settings.
In a production system, you would do this for all TRA files for all monitored TIBCO BusinessEvents engines. When more than one PU (engine) is deployed on the same host, specify a different JMX port for each of the PUs, in the site topology file.

 
java.property.be.engine.jmx.connector.port=%jmx_port%

 
The property java.property.be.engine.jmx.connector.authenticate, is used only if you want to enable authentication. See Chapter 10, Configuring User Authentication in TIBCO BusinessEvents Administration for details.
Task C (Optional) Install and Configure TIBCO Hawk
For displaying machine-level metrics in MM Console, TIBCO Hawk is required. If you skip this step, you just won’t see machine level metrics for your deployed cluster.
Full instructions for this task are provided in the section Install and Configure TIBCO Hawk for Machine Level Metrics in TIBCO BusinessEvents Administration. Below are some basic points for a default setup, for the benefit of experienced Hawk users.
1.
2.
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
3.
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.
Summary and Next Steps
You have done the prerequisite setup for using MM. Next you will complete the main task in getting ready to deploy the project with MM: configuring the site topology for the deployed cluster.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved