Configuring Rule Execution Server for different environments

According to your development phases, you can set up different Rule Execution Server environments (for example development, QA, and production) in a single cell.

About this task

Most likely, the development of your decision management system requires more than a single deployment of Rule Execution Server. The development lifecycle of a decision service application is similar to any other software development process: it includes stages for implementation, testing, deployment, and maintenance. At the very least, you are likely to need an environment for your development team, one for your QA team, and another one for in-production applications. When 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.

Consider the following guidelines to set up your different environments in a single cell.

Procedure

  1. Set up different data sources.
  2. Deploy and configure a XU for each environment.
  3. Deploy the Rule Execution Server console for each environment.
  4. To set up a data source for each environment, use unique JNDI names.

    For example: jdbc/resdatasourceEnv1 and jdbc/resdatasourceEnv2

  5. To deploy the Rule Execution Server console for each environment, proceed as follows:
    1. Modify the deployment descriptor of the Rule Execution Server EAR or WAR management archive: in the web.xml file, uncomment the JMX_XU_QUERY_PART parameter and specify xuName=xuEnv1.
    2. Deploy the Rule Execution Server EAR or WAR file to the server.
      In the resource, reference settings in the application server:
      1. Set the JNDI for the data source as:jdbc/resdatasourceEnv1.
      2. Set the JNDI name for the XU as: eis/ConnectionFactoryEnv1.
    3. Repeat a and b to deploy the Rule Execution Server console for the other environments.
  6. If you deploy to a cluster, synchronize your changes across the cluster after you complete the configuration.
  7. Call the XU instances to register the XU with the Rule Execution Server console.
Parent topic: Configuring Rule Execution Server on the Liberty profile