|
An alert is a message to the user that an event has occurred during an application run. These alerts might be triggered when the connection to BEA JRockit JVM was lost or when an attribute reaches a certain, user-determined threshold; for example, when used memory reaches 90%. You can set trigger constraints to limit when a rule is activated; for example, you can constrain Mission Control from sending alerts at night or on certain dates.
The different actions are triggered by rules that are set on the Triggers tab. This tab lists all rules you have created and allows you to activate or deactivate any trigger for the connection you are working on. When you first run the Management Console, the list of triggers is empty. You can then create triggers by using the Add feature. When you exit the Management Console, the rules that you have created are saved in the console settings file.
You set the rules for triggers by combining an attribute subscription with a trigger, with optional constraints. The action is activated as soon as the rule condition is met.
This section serves as an introduction to the Triggers tab. It includes these topics:
|
|