Configuring Rule Execution Server in shared mode

You can configure Rule Execution Server so that client applications can share the same deployed Execution Unit (XU) resource.

About this task

Note:

The Execution Object Model (XOM) in the database contains only dynamic classes, that is, classes that do not necessarily map to Java classes on a one-to-one basis.
Both Java and EJB rule sessions work with XOMs that contain EJBs, that is, rules that use EJB objects.

Procedure

Configure the application for the operational environment by modifying the deployment descriptor.
Change or redirect the bindings used in the execution components to the real JNDI names of your application servers.
For more information see the http://java.sun.com/products/ejb/docs.html#specs Sun Developer Network web site.

Java EE applications use JNDI as the "switchboard" for making connections between loosely coupled components. Java EE components use JNDI to find other components that they want to use, such as EJB components, and to find resources, such as JDBC and JMS connections. You define interconnections between Java EE components by declaring them in the deployment descriptor of the component. The container automatically binds the objects at the specified place in the namespace and ensures that all resource dependencies between components are satisfied before deploying the components.

Note:
You can map the names used inside the execution components to real JNDI names.
Verify that the contents of the Java EE application EAR or WAR file are well formed and comply with the Java EE specification.
For more information, see the http://java.sun.com/j2ee/1.3/download.html#platformspec Sun Developer Network web site.
Deploy the EAR file or WAR file onto the Java EE server.

What to do next

In the following figure, the components shown in green are not provided by WebSphere® Operational Decision Management. Therefore, you need to develop those components. The Java EE rule session types are available and you must configure these components so that they integrate with the Execution Unit (XU).

The XU is deployed on the application server and shared by all the applications deployed to the server. It works in a similar way to installing a device driver on an operating system, in that the application server is globally enhanced with ruleset execution capabilities. You can easily upgrade, start, stop, and monitor the XU by using the application server management console or other tools. You must deploy the XU onto all the nodes of a cluster.

The diagram shows in green the components that are not provided and that you need to develop.