What variables can I define when I use the mar utility in conjunction with TIBCO adapters and TIBCO applications?
Article ID: KB0086808
Updated On:
| Products | Versions |
|---|---|
| TIBCO Hawk | - |
| Not Applicable | - |
Description
Resolution:
This is explained in "Using the Monitoring Archive Utility" in the "TIBCO Hawk Plug-in For TIBCO Administrator " manual.
When you create a rulebase and you use mar to create a monitoring archive, it distinguishes between two types of events:
Non-application specific events
----------------------------------------
An example of this is monitoring rules written for the Hawk microagent (HMA). You can only use internal variables like ${Internal.Agent Name}
Application specific events
---------------------------------
These rules use the data source of the microagents belonging to TIBCO applications, such as TIBCO BusinessWorks or TIBCO Adapters. For example, if you install BusinessWorks and deploy the JavaMethod application in a domain called domaintest the microagent you'll see is
COM.TIBCO.ADAPTER.bwengine.domaintest.JavaMethod.Process Archive:0
(JavaMethod is under <BW home>\<version>\examples\activities\Java)
If you write a rule for this microagent, the datasource will be:
COM.TIBCO.ADAPTER.bwengine.domaintest.JavaMethod.Process Archive
When you use the mar utility the string above will become
COM.TIBCO.ADAPTER.bwengine.%%TIBCO_DOMAIN%%.%%TIBCO_DEPLOYMENT%%.%%TIBCO_COMPONENT_INSTANCE%%
so this rulebase becomes generic. If you deploy this rule and use Administrator to view it (select Monitoring Console->your domain->click on your monitoring archive name then drill down to the rulebase )
You can use the variables above in the alert string. So the following message:
bwengine uptime > 0 on ${Host}. DEPLOYMENT is %%TIBCO_DEPLOYMENT%%, TIBCO_DOMAIN is %%TIBCO_DOMAIN%%, TIBCO_DOMAIN_HOME is %%TIBCO_DOMAIN_HOME%%, and TIBCO_COMPONENT_INSTANCE IS %%TIBCO_COMPONENT_INSTANCE%%
would generate this corresponding alert:
bwengine uptime > 0 on <myhostname>. DEPLOYMENT is JavaMethod, TIBCO_DOMAIN is domaintest, TIBCO_DOMAIN_HOME is C:/tibco/tra/domain, and TIBCO_COMPONENT_INSTANCE IS Process Archive
This is explained in "Using the Monitoring Archive Utility" in the "TIBCO Hawk Plug-in For TIBCO Administrator " manual.
When you create a rulebase and you use mar to create a monitoring archive, it distinguishes between two types of events:
Non-application specific events
----------------------------------------
An example of this is monitoring rules written for the Hawk microagent (HMA). You can only use internal variables like ${Internal.Agent Name}
Application specific events
---------------------------------
These rules use the data source of the microagents belonging to TIBCO applications, such as TIBCO BusinessWorks or TIBCO Adapters. For example, if you install BusinessWorks and deploy the JavaMethod application in a domain called domaintest the microagent you'll see is
COM.TIBCO.ADAPTER.bwengine.domaintest.JavaMethod.Process Archive:0
(JavaMethod is under <BW home>\<version>\examples\activities\Java)
If you write a rule for this microagent, the datasource will be:
COM.TIBCO.ADAPTER.bwengine.domaintest.JavaMethod.Process Archive
When you use the mar utility the string above will become
COM.TIBCO.ADAPTER.bwengine.%%TIBCO_DOMAIN%%.%%TIBCO_DEPLOYMENT%%.%%TIBCO_COMPONENT_INSTANCE%%
so this rulebase becomes generic. If you deploy this rule and use Administrator to view it (select Monitoring Console->your domain->click on your monitoring archive name then drill down to the rulebase )
You can use the variables above in the alert string. So the following message:
bwengine uptime > 0 on ${Host}. DEPLOYMENT is %%TIBCO_DEPLOYMENT%%, TIBCO_DOMAIN is %%TIBCO_DOMAIN%%, TIBCO_DOMAIN_HOME is %%TIBCO_DOMAIN_HOME%%, and TIBCO_COMPONENT_INSTANCE IS %%TIBCO_COMPONENT_INSTANCE%%
would generate this corresponding alert:
bwengine uptime > 0 on <myhostname>. DEPLOYMENT is JavaMethod, TIBCO_DOMAIN is domaintest, TIBCO_DOMAIN_HOME is C:/tibco/tra/domain, and TIBCO_COMPONENT_INSTANCE IS Process Archive
Issue/Introduction
What variables can I define when I use the mar utility in conjunction with TIBCO adapters and TIBCO applications?
Feedback
Yes
No
Powered by
