How to Monitor Events in Rule Execution Server

Samples > Rule Execution Server Integration > How to Monitor Events in Rule Execution Server

How to Monitor Events in Rule Execution Server

This sample shows you how to generate notifications for actions performed on property elements in the Rule Execution Server Console. For example, if a user adds or modifies a ruleset property, this could trigger an automatic notification to interested parties.

Key Features

Key features include:

MBean notification listener
Repackage the management console
Deploy the customized EAR

Installing the Sample

The sample is installed through the Samples Console.

To install the sample:

In the Samples Console locate the How to Monitor Events in RES sample in: executionserver > monitoringevents.
Make sure that the Samples Server is started. For information on how to start and stop the Samples Server, see Stopping and Restarting the Samples Server from the Samples Console.
Execute the repack command.
Execute the deploy command. This compiles the application, repackages the EAR, and deploys it to the application server.
Wait for the Java EE application to start before continuing. The server trace displays the following message when the application has started: [EARDeployer] Started J2EE application

Running the Sample

The sample can only be run through the Samples Console.

To run the sample you need to launch the Rule Execution Server Console, then modify the RuleApp or ruleset properties to generate events.

To run the sample:

Execute the deploy.ruleapp target to register the RuleApp.
Open a Web browser and type the following URL to launch the Rule Execution Server Console:

http://localhost:8080/bres

Username: bres

Password: bres

Click the Explorer tab.
Click the monitoringevents RuleApp.
Click Add Property.
Click Add to accept the default property details. The new property appears in the RuleApp View.
Events are logged to an RSS feed file. To view the file, open a new browser and use the following URL:

http://localhost:8080/bres/monitoringevents.rss

You can also use an RSS Reader to subscribe to the feed.

Return to the Samples Console and execute the reset.rss command to reset the RSS data feed on the server.

Source Files

The sample is located in <InstallDir>/executionserver/samples/monitoringevents.

EventsContextListener.java is a Web context listener, it registers a MBean Server listener and listeners on all existing Rule Execution Server MBeans at startup.

EventsFeedServlet.java generates the RSS feed (the URL to subscribe to the feed is http://localhost:8080/bres/monitoringevents.rss).

RESNotificationListener.java is the listener registered on all RuleApps and Rulesets. It adds an event to the RSS feed each time a RuleApp / Ruleset is modified.

ServerNotificationListener.java is the listener registered on the MBean Server. It adds an event to the RSS feed each time a RuleApp / Ruleset is created or removed.

ServerNotificationFilter.java filters the MBean Server events to send only Rule Execution Server events to the ServerNotificationListener.

Utils.java contains static methods used in the sample.

RSSHelper.java is a helper to generate the RSS feed.

Highlights

The principle highlight of this sample is Rule Execution Server management JMX notifications.

Rebuilding the Sample

To rebuild the sample:

Open the Samples Console.
Double-click the deploy target to clean, compile, repack and deploy the sample.

Related Concepts

Rule Execution Server Management Model

Related Tasks

Management Events Monitoring