Packaging and deployment

In Jakarta EE environments, you can deploy the XU as a global resource adapter or embed it in the Jakarta EE application, depending on your work environment.

The XU is a stand-alone deployable unit that is packaged as a resource adapter archive file (RAR) for all supported Jakarta EE application servers.

The path to the RAR file is <InstallDir>/executionserver/applicationservers/<appserver>/jrules-res-xu-<version>.rar.

For Java™ SE, the jrules-res-execution.jar file is provided in the <InstallDir>/executionserver/lib directory.

Note: To decompress the XU RAR, use a decompression tool.

In Jakarta EE environments, you can deploy the XU in two different ways.

XU deployed as a global Jakarta EE resource adapter
On a supported Jakarta EE application server, the usual and recommended way is to deploy the XU as a global Jakarta EE resource adapter. All deployed Jakarta EE applications can use the same instance of the XU.
Benefits:
  • XU resources, such as the Rule Execution Server persistence connections, the Rule Execution Server and third-party classes, are shared.
  • No need to configure multiple XU instances.
  • No need to package the XU into Jakarta EE applications
XU embedded in a Jakarta EE application
As any Jakarta EE resource adapter, the XU can be embedded in a Jakarta EE application as an EAR file. In this case, the XU is visible only in the application.
Benefits:
  • No material from other software vendors that might be embedded in the XU affects other applications or the application server.
  • XU resources are dedicated to the application.
  • Different versions of the XU can be used in different applications.