Step 3: Deploying the execution unit (XU) RAR file

Next, you deploy the resource adapter archive (RAR) for the execution unit (XU).

About this task

The execution unit (XU) is a resource adapter for Java™ EE application servers. It is supplied as a RAR archive that you must deploy on your application server. Deploy the XU by copying the XU RAR and XML files to the deployment directory of your application server.

In addition to the procedure described here, you also have the option to deploy the XU inside the application (embed the XU into the EAR). There might be some instances where, due to your application constraints, you have to deploy the XU inside the application. It is your decision to choose the appropriate deployment mode of the XU (either embed into the EAR or deploy as a global connector). Refer to the application server documentation for instructions on packaging a connector into an EAR.

Note:
  • When the XU is deployed as a global connector, its third-party libraries (such as ASM) might be used by the deployed J2EE applications instead of the libraries deployed in the application server.
  • When the XU is deployed as a global connector, use a parent last setting for its J2EE application if your J2EE application does not support the version of the libraries from independent software vendors that are distributed with Decision Server. If this is not possible, you might have to embed the XU into the EAR that is executing the rules.
  • When using an embedded XU packaging, use a parent last setting for the code library if the version of the libraries from independent software vendors that are deployed at the code library level of the application server is not compatible with the XU.
Tip: When the default configuration in shared mode is not appropriate for your use case, you can configure Rule Execution Server so that it is scoped to a single Java™ EE application. See Configuring Rule Execution Server in scoped mode.
To deploy the XU RAR, follow the procedure that applies to the version of Operational Decision Manager that you use, as explained in the following table:
Operational Decision Manager version Procedure
8.10.0 Copy the file jrules-res-xu-JBOSS6EAP.rar from <ODM_InstallDir>/executionserver/applicationservers/JBoss6EAP into the <JBOSS_HOME>/standalone/deployments directory.
8.10.1 and 8.10.2 Copy the file jrules-res-xu-JBOSS.rar from <ODM_InstallDir>/executionserver/applicationservers/JBoss into the <JBOSS_HOME>/standalone/deployments directory.

When deployed to JBoss, the XU uses the JDK logging API.

Procedure

To configure the XU log level with the JBoss Management Console, proceed as follows:

  1. Log in to the JBoss Management Console.
  2. Navigate to the logging subsystem configuration, for example Configuration > Logging + Click View.
  3. Click the Log Categories tab.
  4. Click the Add button and define the following details.
    • Name: com.ibm.rules.res.execution
    • Log Level: specifies which message levels are logged by this logger. Message levels lower than this value are discarded.
    • User Parent Handler: specifies whether or not this logger sends its output to the parent logger.
  5. Save.
  6. Restart the server.