Resolution: Description
=========
Some users have multiple client machines which deploy multiple applications. They want to monitor/restart these applications in case they are stopped or crash.
Attachments
==========
monitorapplication.hrb
monitorapplication.mar
Resolution
========
1). Create a template rulebase for monitoring your applications. In this rulebase, you must use the following variable substitution to replace the value, such as deployment name and instance name. These variables would be replaced as long as you deployed the template rulebase in your applications. See the attached example template rulebase (Filename: monitorapplication.hrb).
%%TIBCO_DOMAIN%%
%%TIBCO_DEPLOYMENT%%
%%TIBCO_COMPONENT_INSTANCE%%
%%TIBCO_COMPONENT_TYPE%%
%%TIBCO_DOMAIN_HOME%%
%%TIBCO_COMPONENT_INSTANCE_TRACE_FILE%%
2). Use Monitoring Archive Utility to create a MAR file. Refer to the document: TIBCO Hawk->Plug-in For TIBCO Administrator-> Monitoring Console->Using the Configure Monitoring Utility
Example command:
mar cvf monitorapplication.mar monitorapplication.hrb -Xtype bwengine
Note the -Xtype is the option for the type of your application. For more details, refer to the Hawk document. See the attached example bwengine type mar file (Filename: monitorapplication.mar).
3). Make sure you have Monitoring Console in your Administrator. If it does not exist, install standalone Hawk on your Admin machine.
4). Deploy your mar file on your applications via the Admin GUI. Refer to the document: TIBCO Hawk->Plug-in For TIBCO Administrator-> Monitoring Console-> Monitoring Console
Make sure you have "Adding Targets for a Monitoring Configuration".
You will be able to see rulebases deployed in your hawkagent. The variable should be replaced in each rulebases.