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

About this task

Configuring Rule Execution Server in shared mode means sharing resources between client applications, such as execution unit (XU and engine pools. In this diagram, two applications use the XU to benefit from common resources.

The benefits of sharing XU resources, as opposed to scoping them to a single application, are stated in Packaging and deployment.

This is the default configuration for Rule Execution Server installation because it fosters both optimal use of the resources and easy deployment. The XU is automatically made available for all client applications that are deployed on the same server or node.

1. Configure the application for the operational environment by modifying the web.xml deployment descriptor.
2. Change or redirect the bindings that are used in the execution components to the real JNDI names of your application servers.

   Jakarta EE applications use JNDI as the switchboard for making connections between loosely coupled components. Jakarta 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 Jakarta 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 that are used inside the execution components to real JNDI names.

3. Verify that the contents of the Jakarta EE application EAR or WAR file are well formed and comply with the Jakarta EE specification.
4. Deploy the EAR file or WAR file to the Java™ EE server.

What to do next

In the following figure, the components shown in green are not provided by Operational Decision Manager. Therefore, you need to develop those components. The Jakarta 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.