#### To Create a New Management Rule

To set up a new management rule, perform the following steps:

1. Do one of the following:
   - For the developer profile, in the tree component, select the Configuration node.
   - For the cluster or enterprise profile, in the tree component select the Configurations node, then select the configuration to edit.
2. Select the Management Rules node.
3. Ensure All Rules is checked.

   This enables Management Rules globally. If this is unchecked none of the management rules will be executed.

4. Select New.
5. In the Name field, provide a name for this rule. For example, `Rule1`.
6. Check Enabled to activate this rule.
7. Enter a description that identifies this rule
8. Select the Event Type from the drop-down list.

   The Event Type specifies the condition to execute the rule. All events are based on the JMX notification mechanism. You can create a custom event by using MBeans that implement `javax.management.NotificationBroadcaster/NotificationEmitter`.

   The following event types are available:

   - 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.

9. Select the Record Event checkbox to log the occurrence of the specified event.
10. Set the log level for this management rule.

    The default is `INFO`.

11. Select Next to go to the final part of setting your management rule.

    The subsequent administration screens will depend on the type of event you have selected:

    - If you specified a Monitor event, see To Configure Monitor Event Properties.

    - If you specified a Notification event, see To Configure Notification Event Properties.

    - If you specified a lifecycle event, see To Configure Lifecycle Event Properties.

    - If you specified a log event, see To Configure Log Event Properties.

    - If you specified a timer event, see To Configure Timer Event Properties.

    - If you specified a trace event, see To Configure Trace Event Properties.