Filter
Top Products
Conguring Management Rules
This section contains information about setting administration policies to automate routine
administration tasks, congure self-tuning of the application server for diverse runtime
conditions and improve availability by preventing failures. This section also contains
information on the self-management templates, which are predened management rules that
you can customize.
This section contains the following topics:
■
“About Management Rules” on page 215
■
“Conguring Management Rules” on page 216
About Management Rules
Management rules enable you to automate routine administration tasks, congure self-tuning
of the application server for diverse runtime condition and improve availability by preventing
failures. A management rule contains an action to be taken when a specied event occurs or a
set threshold is reached. You can set management rules that can automatically take corrective
action, based on events that you specify.
A management rule consists of two parts — event and action:
■
An event uses the JMX notication mechanism to trigger a predened action.
■
An action is triggered when an associated event occurs. An action is an MBean which is a
notication listener which implements javax.management.NotificationListener.
For example, an event could be a SEVERE message logged by the EJB logger, and an action
could be alerting an administrator with the log message contents. When the event happens,
event data is passed as part of userData part of the javax.management.Notification.
The action specied in your rule has to be implemented as a custom MBean. Therefore, before
conguring a management rule, you should deploy a custom MBean designed to receive event
19
CHAPTER 19
215