Installing and Configuring a Rule Execution Server Application

ILOG JRules User Guide > Executing Rules > Tasks > Assembling and Packaging a Rule Execution Server Application > Installing and Configuring a Rule Execution Server Application

Installing and Configuring a Rule Execution Server Application

PREVIOUS NEXT

JRules provides J2EE application components that can be assembled and deployed to a J2EE server. J2EE application development occurs in phases, with a final phase required for maintenance. In small companies, one person may perform several roles:

Development phase: Web designers/developers develop Web components and package them as WAR files. EJB developers develop EJB components and package them as an EJB JAR.
Assembly phase: The application assembler takes the WAR and the EJB JAR files and assembles the Web and EJB components to produce an EAR file.
Deployment phase: During the deployment phase, the application deployer modifies the deployment descriptors in the EAR file before the J2EE application is deployed.
Maintenance phase: The system administrator makes sure that the J2EE application and server are up and running.

There are a number of generic tasks that need to be carried out to install and configure a Rule Execution Server application:

To install and configure a Rule Execution Server application:

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: http://java.sun.com/products/ejb/docs.html#specs.

J2EE applications use JNDI as the "switchboard" for making connections between loosely coupled components. J2EE 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. Interconnections between J2EE components are defined declaratively in the component deployment descriptor. The container automatically binds objects at the specified place in the namespace and ensures that all resource dependencies between components are satisfied before deploying the components.

Note

The names used inside the execution components can be mapped to real JNDI names.

Verify that the contents of the EAR or the WAR file, are well formed and comply with the J2EE specification. For more information see section J2EE 8: Application Assembly and Deployment: http://java.sun.com/j2ee/1.3/download.html#platformspec.
Deploy (install) the J2EE application (EAR file or WAR file) into the J2EE server.

The following figure shows those components (in green) not provided by JRules, which you will need to develop. These components must be configured to integrate with the Execution Unit (XU), as described in the following sections.

Note

The Execution Object Model (XOM) in the database will only contain dynamic classes, that is, classes that do not necessarily map to Java classes on a one-to-one basis.

Note

Both Java and EJB rule sessions work with XOMs that contain EJBs, that is, rules that use EJB objects.

Related Concepts

Rule Execution Server

Related Tasks

Packaging Java Rule Sessions

Packaging EJB Rule Sessions

Packaging Message-Driven Rule Beans

Packaging an Application-Scoped Rule Execution Server