Chapter 29. KIE Server clusters in a runtime environment

Procedure

1. Download Red Hat JBoss EAP 7.4 on each node of the cluster:

   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: Enterprise Application Platform
      • Version: 7.4
   2. Click Download next to Red Hat JBoss Enterprise Application Platform 7.4.14. (jboss-eap-7.4.14.zip).
2. Extract the jboss-eap-7.4.14.zip file. The jboss-eap-7.4/jboss-eap-7.4 directory is referred to as EAP_HOME.
3. Download and apply the latest Red Hat JBoss EAP patch, if available.

4. Download KIE Server:

   1. Navigate to the Software Downloads page in the Red Hat Customer Portal and select the product and version from the drop-down options:

      • PRODUCT: Process Automation Manager
      • Version: 7.13.5
   2. Download Red Hat Process Automation Manager 7.13.5 KIE Server for All Supported EE8 Containers (rhpam-7.13.5-kie-server-ee8.zip).
5. Extract the rhpam-7.13.5-kie-server-ee8.zip archive to a temporary directory. In the following examples this directory is called TEMP_DIR.

6. Copy the TEMP_DIR/rhpam-7.13.5-kie-server-ee8/rhpam-7.13.5-kie-server-ee8/kie-server.war directory to EAP_HOME/standalone/deployments/.

   Warning

   Ensure the names of the Red Hat Decision Manager deployments you copy do not conflict with your existing deployments in the Red Hat JBoss EAP instance.

7. Copy the contents of the TEMP_DIR/rhpam-7.13.5-kie-server-ee8/rhpam-7.13.5-kie-server-ee8/SecurityPolicy/ to EAP_HOME/bin.
8. When prompted to overwrite files, click Replace.
9. In the EAP_HOME/standalone/deployments/ directory, create an empty file named kie-server.war.dodeploy. This file ensures that KIE Server is automatically deployed when the server starts.
10. Download and apply the latest Red Hat Decision Manager patch, if available.
11. Navigate to the EAP_HOME/bin directory.

12. Create a user with the kie-server role that you will use to log in to KIE Server.

    $ ./bin/jboss-cli.sh --commands="embed-server --std-out=echo,/subsystem=elytron/filesystem-realm=ApplicationRealm:add-identity(identity=<USERNAME>),/subsystem=elytron/filesystem-realm=ApplicationRealm:set-password(identity=<USERNAME>, clear={password='<PASSWORD>'}),/subsystem=elytron/filesystem-realm=ApplicationRealm:add-identity-attribute(identity=<USERNAME>, name=role, value=['kie-server'])"

13. Make a note of your user names and passwords.

14. To start the cluster, navigate to EAP_HOME/bin and enter one of the following commands:

    • On Linux or UNIX-based systems:

      $ ./standalone.sh -c standalone-full.xml

    • On Windows:

      standalone.bat -c standalone-full.xml

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: Process Automation Manager
   • Version: 7.13.5
2. Download Red Hat Process Automation Manager 7.13.5 Add Ons (the rhpam-7.13.5-add-ons.zip file).
3. Extract the rhpam-7.13.5-add-ons.zip file. The rhpam-7.13.5-controller-ee7.zip file is in the extracted directory.
4. Extract the rhpam-7.13.5-controller-ee7.zip archive to a temporary directory. In the following examples this directory is called TEMP_DIR.

5. Copy the TEMP_DIR/rhpam-7.13.5-controller-ee7/controller.war directory to EAP_HOME/standalone/deployments/.

   Warning

   Ensure that the names of the headless Process Automation Manager controller deployments you copy do not conflict with your existing deployments in the Red Hat JBoss EAP instance.

6. Copy the contents of the TEMP_DIR/rhpam-7.13.5-controller-ee7/SecurityPolicy/ directory to EAP_HOME/bin.
7. When prompted to overwrite files, click Yes.
8. In the EAP_HOME/standalone/deployments/ directory, create an empty file named controller.war.dodeploy. This file ensures that the headless Process Automation Manager controller is automatically deployed when the server starts.
9. Open the EAP_HOME/standalone/configuration/standalone.xml file in a text editor.

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

    Template files contain default configurations for specific deployment scenarios.

    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.

11. To start the headless Process Automation Manager controller, navigate to EAP_HOME/bin and enter the following command:

    • On Linux or UNIX-based systems:

      $ ./standalone.sh

    • On Windows:

      standalone.bat