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.
- 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.
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: