第6章 Installing and running the headless Decision Manager controller with IBM WebSphere Application Server
To use the Decision Server REST API or Java Client API to interact with Decision Server, install the headless Decision Manager controller with IBM WebSphere Application Server. The headless Decision Manager controller manages Decision Server configuration in a centralized way so that you can use the headless Decision Manager controller to create and maintain containers and perform other server-level tasks.
For optimal results, install Decision Server and the headless Decision Manager controller on different servers in production environments. In development environments, you can install Decision Server and the headless Decision Manager controller on the same server.
Prerequisites
- The IBM WebSphere Application Server instance is configured as described in 4章Configuring IBM WebSphere Application Server for Decision Server.
- Decision Server is installed on the IBM WebSphere Application Server instance.
- You have sufficient user permissions to complete the installation.
Procedure
Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options:
- Product: Decision Manager
- Version: 7.5
- Download Red Hat Decision Manager 7.5.1 Add-Ons.
-
Extract the downloaded
rhdm-7.5.1-add-ons.zipfile to a temporary directory. -
Extract the
rhdm-7.5.1-add-ons.zipfile to a temporary directory. In the following examples this directory is calledTEMP_DIR. -
Extract the
rhdm-7.5.1-add-ons/rhdm-7.5-controller-ee7.zipfile. Repackage the
controller.wardirectory:-
Navigate to the
TEMP_DIR/rhdm-7.5.1-add-ons/rhdm-7.5-controller-ee7/controller.wardirectory. -
Select the contents of the
TEMP_DIR/rhdm-7.5.1-add-ons/rhdm-7.5-controller-ee7/controller.wardirectory and create thecontroller.zipfile. -
Rename
controller.ziptocontroller.war. This is the file that you will use to deploy the headless Decision Manager controller. -
Optionally, copy the new
controller.warfile to a location that is more convenient to deploy from.
-
Navigate to the
- In the WebSphere Integrated Solutions Console, navigate to Applications → Application Types → WebSphere Enterprise Applications.
- Click Install.
-
Navigate to the
controller.warfile that you repackaged and select it to upload. Select Fast Path and click Next.
The Install New Application wizard opens.
-
Change the Application Name to
controllerand click Next. - Map the headless Decision Manager controller modules to servers according to your specific requirements and click Next.
-
For Bind Listeners for Message-Driven Beans, select Activation Specification for both beans, enter
jms/activation/KIE.SERVER.REQUESTin the Target Resource JNDI Name field, and enter thejms/cf/KIE.SERVER.REQUESTJNDI name for theKIE.SERVER.REQUESTconnection factory. - In the Map Virtual Hosts for Web Modules section, keep the default values and click Next.
-
Set the context root to
controller. - In the Metadata for Modules section, keep the default values and click Next.
- Click Finish to install the headless Decision Manager controller and click Save to save the changes to the master configuration.
6.1. Configuring class loading for the headless Decision Manager controller
After the headless Decision Manager controller is installed, you must configure Decision Server class loading to set parent classes to load last.
Procedure
-
Navigate to Applications → Application Types → WebSphere Enterprise Applications and click
kie-server. - Click Class Loading and Update Detection under the Detail Properties heading on the left.
- In the properties, change Class Loader Order to Classes loaded with local class loader first (parent last) and WAR Class Loader Policy to Single class loader for application.
- Save the changes to the master configuration.