Chapter 6. Installing and running the headless Decision Manager controller

Procedure

1. On the first computer, run the installer in interactive mode or CLI mode. See Installing and configuring Red Hat Decision Manager on Red Hat JBoss EAP 7.1 for more information.
2. On the Component Selection page, clear the Decision Server box.
3. Complete the Decision Central installation.
4. On the second computer, run the installer in interactive mode or CLI mode.
5. On the Component Selection page, clear the Decision Central box.
6. On the Configure Runtime Environment page, select Perform Advanced Configuration.
7. Select Customize Decision Server properties and click Next.
8. On the Process Server Properties Configuration page, click New Server Configuration to add a Decision Server and specify a unique name for that Decision Server. This name will appear in Decision Central and enable you to distinguish between different Decision Servers.

Procedure

1. 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.1
2. Download Red Hat Decision Manager 7.1.0 Add Ons (the rhdm-7.1.0-add-ons.zip file).
3. Unzip the rhdm-7.1.0-add-ons.zip file. The rhdm-7.1-controller-ee7.zip file is in the unzipped directory.
4. Extract the rhdm-7.1-controller-ee7 archive to a temporary directory. In the following examples this directory is called TEMP_DIR.

5. Copy the TEMP_DIR/rhdm-7.1-controller-ee7/controller.war directory to EAP_HOME/standalone/deployments/.

   Warning

   Ensure that the names of the headless Decision Manager controller deployments you are copying do not conflict with your existing deployments in the Red Hat JBoss EAP instance.

6. Copy the contents of the TEMP_DIR/rhdm-7.1-controller-ee7/SecurityPolicy/ directory to EAP_HOME/bin. When asked to overwrite files, select Yes.
7. In the EAP_HOME/standalone/deployments/ directory, create an empty file named controller.war.dodeploy. This file ensures that the headless Decision Manager controller is automatically deployed when the server starts.

Procedure

1. In a terminal application, navigate to EAP_HOME/bin.

2. Enter the following command:

   • On Linux or UNIX-based systems:

     $ ./standalone.sh

     Copy to Clipboard Toggle word wrap

   • On Windows:

     standalone.bat

     Copy to Clipboard Toggle word wrap

3. To verify that the headless Decision Manager controller is working on Red Hat JBoss EAP, enter the following command where <CONTROLLER> and <CONTROLLER_PWD> is the user name and password. The output of this command provides information about the Decision Server instance.

   curl -X GET "http://<HOST>:<PORT>/controller/rest/controller/management/servers" -H  "accept: application/xml" -u '<CONTROLLER>:<CONTROLLER_PWD>'

   Copy to Clipboard Toggle word wrap

Procedure

1. 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.1
2. Download Red Hat Decision Manager 7.1.0 Add Ons (the rhdm-7.1.0-add-ons.zip file).
3. Unzip the rhdm-7.1.0-add-ons.zip file. The rhdm-7.1-controller-ee7.zip file is in the unzipped directory.
4. Extract the rhdm-7.1-controller-ee7.zip file to a temporary directory. In the following examples this directory is called TEMP_DIR.

5. Repackage the controller.war directory:

   1. Navigate to the TEMP_DIR/rhdm-7.1.0-add-ons/rhdm-7.1-controller-ee7/controller.war directory.
   2. Select the contents of the TEMP_DIR/rhdm-7.1.0-add-ons/rhdm-7.1-controller-ee7/controller.war directory and create the controller.zip file.
   3. Rename controller.zip to controller.war. This is the file that you will use to deploy the headless Decision Manager controller on the cluster nodes.
   4. If desired, copy the new controller.war file to a location that is more convenient to deploy from.
6. If you want to use a security manager with the headless Decision Manager controller, copy the contents of the TEMP_DIR/rhdm-7.1.0-add-ons/rhdm-7.1-controller-ee7/SecurityPolicy directory to the EAP_HOME/bin directory on each node of the cluster.
7. Add Red Hat JBoss EAP management users to the master node (where you configured the domain.xml file) as described in the Red Hat JBoss EAP 7.1 Configuration Guide.
8. On each node of the cluster, add users for the headless Decision Manager controller as described in the "Installing the headless Decision Manager controller" section of Installing and configuring Red Hat Decision Manager on Red Hat JBoss EAP 7.1.

9. Complete the following steps in the host.xml file on the master node and in the host-slave.xml file on each slave node:

   1. Open the EAP_HOME/domain/configuration/host.xml or EAP_HOME/domain/configuration/host-slave.xml file in a text editor.
   2. In the main-server-group <servers> element, add the servers that will be part of the cluster.

   3. Add the following properties to the <system-properties> element and replace <NFS_STORAGE> with the absolute path to the NFS storage where the template configuration is stored.

      <system-properties>
        <property name="org.kie.server.controller.templatefile.watcher.enabled" value="true"/>
        <property name="org.kie.server.controller.templatefile" value="<NFS_STORAGE>"/>
      </system-properties>

      Copy to Clipboard Toggle word wrap

      If the value of the org.kie.server.controller.templatefile.watcher.enabled property is set to true, a separate thread is started to watch for modifications of the template file. The default interval for these checks is 30000 milliseconds and can be further controlled by the org.kie.server.controller.templatefile.watcher.interval system property. If the value of this property is set to false, changes to the template file are detected only when the server restarts.

10. To deploy the controller.war file that you created previously into the server group, complete the following steps on the master node:

    1. Log in to the Red Hat JBoss EAP Administration console of your domain as a management user.
    2. Click Deployments Server Groups→ main-server-group and click Add.
    3. In the dialog box, click Upload a new deployment and click Next.
    4. In the Upload Deployments dialog box, click Browse, select the controller.war file, and click Next.

    5. Click Enable and click Next.

       Note

       Make sure to check deployment unit readiness with every cluster member.

       When a deployment unit is created on a cluster node, it takes some time before it is distributed among all cluster members. You can check the deployment status using the server Administration console or REST API. However, if the query is sent to the node where the deployment was originally issued, the query will return a value of deployed. If the query is sent to a node where the deployment has not yet been distributed, the query returns DeploymentNotFoundException.