Configuring Management Rules - Sun Microsystems GlassFish Enterprise Server 2.1 Administration Manual

Configuring Management Rules

notifications and take appropriate action. For details on developing a custom MBean and
deploying it, see
Server 2.1 Developer's
The Enterprise Server provides some useful events, which you can further extend by writing
custom MBeans to emit notifications. Each event can be further customized by changing its
properties.
The following event types are available:
■
■
■
Configuring Management Rules
To configure management rules in the Admin Console:
■
■
Note –
management rules are not enabled globally, none of the management rules are executed.
216 Sun GlassFish Enterprise Server 2.1 Administration Guide • December 2008
Chapter 14, "Developing Custom MBeans, " in Sun GlassFish Enterprise
Guide.
Monitor events: Monitors an attribute of an MBean. Monitor events have similar
capabilities to javax.management.monitor package capabilities. In addition to monitoring
simple attributes, as Java SE 5 javax.management.monitor does, monitor events also
support monitoring complex attributes.
Notification events: Notifies of events from a custom MBean. Use these events to write
custom events and thus extend the event dictionary. Any MBeans which can emit a
notification can be an event.
System events:
Lifecycle: Events for sever startup, showdown, and termination.
■
Log: Events triggered when the specified logger writes a log entry. For example, you
■
could create a management rule to send an alert to an administrator when an EJB
container logger logs a SEVERE log entry.
Timer: Events triggered at the specified date and time, at the specified interval, and so on.
■
These events have capabilities similar to the javax.management.timer package.
Trace: Events triggered on Entry and Exit of HTTP/IIOP request methods, EJB methods,
■
and Web methods. For example, you can design a servlet filter used to log interactions
with a servlet as a management rule using Web method Entry and Exit events.
Cluster: Events triggered when a cluster or instance starts, stops, or fails. These events
■
use the Group Management System cluster monitoring.
In the developer profile, go to Configuration → Management Rules
In the cluster and enterprise profiles, go to Configurations → Configuration →
Management Rules
On this page, check All Rules Enabled to enable management rules globally. If