How to Use a Message-Driven Rule Bean

Samples > Rule Execution Server Integration > How to Use a Message-Driven Rule Bean

How to Use a Message-Driven Rule Bean

The sample shows how to execute a ruleset on the Rule Execution Server using a point-to-point message-driven rule bean. A message-driven bean (MDB) is an enterprise bean that allows Java EE applications to process messages asynchronously.

The sample simulates a pre-trade check operation between a Java client and the message-driven rule bean.

Key Features

Key features include:

JMS integration in Rule Execution Server
Rulesets (.irl files)
XML binding
Ant tasks for RuleApp deployment

Running the Sample

The sample can only be run through the Samples Console.

To run the sample:

Go to the Samples Console and locate the rulemdb > jboss40 sample.
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 deploy command.
Execute the deploy.ruleapp command to register the RuleApp.
Launch the sample using either a Swing based mode or a command line:

Using Swing: Execute the run.ui command to launch the Swing interface. The Swing interface combines the following actions:

- Connect to the server.

- Enter an order and send a message for this order.

- Display the status of this order.

- Enter another order and send a message for this order.

- Display the status of this order, and so on.

- Disconnect from the server.

The Swing interface displays the results of multiple orders.

Using the command line: Execute the run command to launch the remote Java client. This mode is only able to execute the pre-trade operation for a single order each time it is executed.

Source Files

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

RemoteBresMdb is the class that invokes the message-driven rule bean.
SimpleJavaClient is the class that executes the pre-trade operation and displays the result for a single order on the command line.
SwingJavaClient is the class that executes the pre-trade operation and displays the results for multiple orders in the Swing mode.

The Swing user interface source files are located in /executionserver/samples/rulemdb/src/rulemdb/ui.

Controller is the class that translates user's interactions into actions to be performed by the model.
CustomerUi is the utility class to set customer input parameters.
LogAppender prints the message logged by log4j in a JTextArea
MdbRenderer is the interface that displays the JMS message.
OrderUi is the class that displays the values of an order field loaded from an XSD file in the SendMessagePanel.
OutputPanel is the class that creates the overall output display panel.
ReceiveMessagePanel is the class that creates the panel that displays the received message-driven rule bean message.
SendMessagePanel is the class that creates the panel that does sends the message-driven rule bean message.
SwingMdbRenderer is the subclass of TextMdbRenderer that displays the message-driven rule bean sample message text.