Configuring Rule Execution Server for different environments

The development of your decision management system may require more than a single deployment of Rule Execution Server.

The development lifecycle of a decision service includes stages for implementation, testing, deployment, and maintenance. You may need an environment for your development team, one for your QA team, and another one for in-production applications. In cases where you configure Rule Execution Server in a single cell, it is good practice to isolate the rulesets that you use on each server, and ensure that the execution units (XUs) do not interfere with each other.

Use the following instructions to set up your different environments in a single cell.

To set up a data source for each environment:

Use a unique JNDI name. For example:
  • jdbc/resdatasourceEnv1
  • jdbc/resdatasourceEnv2

To configure a XU for each environment and define a J2C connection factory:

  1. To open and update the XU RAR archive, follow this procedure:
    1. Open the <ODM_InstallDir>/executionserver/applicationservers/jboss8EAP/jrules-res-xu-JBOSS.rar archive with a decompression tool.
    2. In the jrules-res-xu-JBOSS.rar/META-INF/ironjacamar.xml file, make the following highlighted change: <connection-definition class-name="ilog.rules.res.xu.spi.IlrManagedXUConnectionFactory" enabled="true" jndi-name="java:/eis/XUConnectionFactoryEnv1" pool-name="eis/XUConnectionFactory" use-ccm="true" use-java-context="true">. Execution components that invoke this XU must be modified and use this JNDI name instead of the default.
  2. Save the file.
  3. Repeat the same process for XUs in other environments.

To deploy the Rule Execution Server console for each environment:

  1. Modify the deployment descriptor of the Rule Execution Server console EAR. In the web.xml, uncomment the JMX_XU_QUERY_PART parameter and specify xuName=xuEnv1.
  2. Deploy the Rule Execution Server console EAR on the server.
  3. In the resource reference settings in the application server:
    1. Set the JNDI name for the data source as: jdbc/resdatasourceEnv1.
    2. Set the JNDI name for the XU as: eis/XUConnectionFactoryEnv1.
  4. Repeat the process to deploy the Rule Execution Server console for the other environments.

If you deploy to a cluster, synchronize your changes across the cluster after you complete the configuration.

Invoke the XU instances to register the XU with the Rule Execution Server console.