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


Appendix D Application Monitoring and Management by Processing Rulebases : Defining Actions

Defining Actions
Each test has one or more related actions. An action is the consequence of a rule, such as an alert message or a custom script. Whenever the rule receives information from its data source, tests are evaluated. If a test evaluates to true, the related actions are triggered. Once triggered, actions are performed unless advanced options delay or prevent the action.
Creating an Alert Message with Variable Substitution
The following example shows how to create an alert message with variable substitution as a representative action.
To define an action, perform the following steps:
1.
Click Create on the toolbar.
2.
Select a type from the Action Type area: Alert, Execute, Notification, Method, Email, and Post Condition.
These types correspond to the TIBCO Hawk action types, see Creating an Alert Message with Variable Substitution in TIBCO Hawk Administrator’s Guide for more details.
3.
In the Message field, type the following:
Gateway Service: http, inbound received:
4.
To insert an internal variable, right-click Insert and select Internal Variable.
 
Internal variables available in the Agent Menu are:
 
To insert an external variable, right-click Insert and select External Variable. ${External.<var name>} is inserted in the active string field. Replace <var name> in the syntax string with the name of the external variable defined in the properties file.
External variables are obtained from the variable file specified in the -variable option for the rulebase engine (suboption of -M RuleBaseEngine) when the agent is started.
To insert a data source variable in a string argument, select a variable name from the menu.
Figure 57 Creating an Alert Message
Variable syntax is added to the string field at the cursor location. The syntax does not require modification. You can also manually type the syntax ${<return-field-name>} in the string field for an action, where return-field-name is the label for a value returned by the method. The microagent method that returns this field must be the data source for the current rule.
5.
Using Advanced Action Features
Advanced action options add flexibility in timing when an action is performed. For example, using advanced options you can automate problem escalation procedures.
See "Using Advanced Action Features" in TIBCO Hawk Administrator’s Guide for more details.

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