After you have deployed the MBean descriptors, you deploy
resource adapter archive (RAR) for the Execution Unit (XU) onto WebSphere® Application Server.
About this task
This phase of the Rule Execution Server configuration
consists in deploying the Execution Unit (XU) resource adapter archive
(RAR) on WebSphere Application Server and
add the properties by which to identify it. The RAR file contains
the XU and the persistence layer.
In the following procedure, <version_number> refers
to the version of WebSphere Application Server to
which you deploy the XU RAR.
Important: In some
cases, because of your application constraints, you might have to
deploy the XU inside the application. It is your decision to choose
the appropriate deployment mode of the XU: either embed it into the
EAR or deploy it as a global connector. In any case, be aware of the
following consequences.
- When the XU is deployed as a global connector:
- The deployed Java EE applications
might use its third-party libraries (such as ASM) instead of the libraries
deployed in the application server.
- Use a parent last setting for the XU Java EE application if your Java EE application does not support the version
of the third-party libraries distributed with Decision
Server.
If you cannot use a parent last setting, you might
need to embed the XU into the EAR that executes the rules.
- If you choose an embedded XU packaging, use a parent last setting
for the code library if the third-party libraries version deployed
at the level of the application-server code library are not compatible
with the XU.
What to do next
For more information, especially for instructions about packaging
a connector into an EAR or about installing additional XU resource
adapters, see one of the following information centers: