Installing and configuring Red Hat Decision Manager in a Red Hat JBoss EAP clustered environment

Procedure

1. Download and unzip the Elasticsearch installation file.

2. Replace the contents of the elasticsearch/config/elasticsearch.yml file with the following content, where <ELASTICSEARCH_NODE_IP> is the IP address of the system where you unzipped the Elasticsearch file:

   cluster.name: kie-cluster
   transport.host: <ELASTICSEARCH_NODE_IP>
   http.host: <ELASTICSEARCH_NODE_IP>
   transport.tcp.port: 9300
   discovery.zen.minimum_master_nodes: 1

3. Run Elasticsearch:

   • On Linux or UNIX-based systems, enter:

     ELASTICSEARCH_HOME_/bin/elasticsearch

     On Windows, enter:

     ELASTICSEARCH_HOME\bin\elasticsearch.bat

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: AMQ Broker
   • Version: 7.2.0
2. Click Download next to Red Hat AMQ Broker 7.2.0 (amq-broker-7.2.0-bin.zip).
3. Extract the amq-broker-7.2.0-bin.zip file.
4. Change directory to amq-broker-7.2.0-bin/amq-broker-7.2.0/bin.

5. Enter the following command and replace the following placeholders to create the broker and broker user:

   • <HOST> is the IP address or host name of the server where you installed AMQ Broker.
   • <AMQ_USER> and <AMQ_PASSWORD> is a user name and password combination of your choice.

   • <BROKER_NAME> is a name for the broker that you are creating.

     ./artemis create --host <HOST> --user <AMQ_USER> --password <AMQ_PASSWORD> --require-login <BROKER_NAME>

6. To run AMQ Broker, enter the following command in the amq-broker-7.2.0-bin/amq-broker-7.2.0/bin directory:

   amq-broker-7.2.0/bin/<BROKER_NAME>/bin/artemis run

Procedure

1. Download Red Hat JBoss EAP 7.2 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.2
   2. Click Download next to Red Hat JBoss Enterprise Application Platform 7.2.0. (JBEAP-7.2.0/jboss-eap-7.2.0.zip).
2. Extract the jboss-eap-7.2.0.zip file. In the following steps, EAP_HOME is the jboss-eap-7.2/jboss-eap-7.2 directory.
3. Download and apply the latest Red Hat JBoss EAP patch, if available.

4. Download Red Hat Decision Manager on each node of the cluster:

   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: Decision Manager
      • Version: 7.3
   2. Download Red Hat Decision Manager 7.3.0 Business Central Deployable for Red Hat JBoss EAP 7 (rhdm-7.3.0-decision-central-eap7-deployable.zip).
5. Extract the rhdm-7.3.0-decision-central-eap7-deployable.zip file to a temporary directory. In the following commands this directory is called TEMP_DIR.
6. Copy the contents of TEMP_DIR/rhdm-7.3.0-decision-central-eap7-deployable/jboss-eap-7.2 to EAP_HOME.
7. Download and apply the latest Red Hat Decision Manager patch, if available.
8. Navigate to the EAP_HOME/bin directory.

9. Create a user with the admin role that you will use to log in to Business Central. In the following command, replace <username> and <password> with the user name and password of your choice.

   $ ./add-user.sh -a --user <USERNAME>  --password <PASSWORD> --role admin

   注記

   Make sure that the specified user name is not the same as an existing user, role, or group. For example, do not create a user with the user name admin.

   The password must have at least eight characters and must contain at least one number and one non-alphanumeric character, but not & (ampersand).

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

    $ ./add-user.sh -a --user <USERNAME>  --password <PASSWORD> --role kie-server

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

Procedure

1. Open the EAP_HOME/standalone/configuration/standalone-full-ha.xml file in a text editor.

2. Edit or add the following properties to the <system-properties> element and replace the following placeholders:

   • <AMQ_USER> and <AMQ_PASSWORD> are the credentials that you defined when creating the AMQ Broker.
   • <AMQ_BROKER_IP_ADDRESS> is the IP address of the AMQ Broker.
   • <ELASTICSEARCH_NODE_IP> is the IP address where Elasticseach is installed.
   • <SHARED_NETWORK_FOLDER> is the network folder that all Business Centrals in the cluster use to exchange data. This folder must be the same on all nodes of the cluster.

   <system-properties>
     <property name="appformer-jms-connection-mode" value="REMOTE"/>
     <property name="appformer-jms-username" value="<AMQ_USER>  "/>
     <property name="appformer-jms-password" value="<AMQ_USER_PASSWORD>"/>
     <property name="appformer-jms-url" value="tcp://<AMQ_BROKER_IP_ADDRESS>:61616?ha=true&amp;retryInterval=1000&amp;retryIntervalMultiplier=1.0&amp;reconnectAttempts=-1"/>
     <property name="org.appformer.ext.metadata.elastic.port" value="9300"/>
     <property name="org.appformer.ext.metadata.elastic.host"
         value="<ELASTICSEARCH_NODE_IP>"/>
     <property name="org.appformer.ext.metadata.elastic.cluster"
         value="kie-cluster"/>
     <property name="org.appformer.ext.metadata.index" value="elastic"/>
     <property name="org.appformer.ext.metadata.elastic.retries" value="10"/>
     <property name="org.uberfire.nio.git.dir" value="<SHARED_NETWORK_FOLDER>"/>
     <property name="es.set.netty.runtime.available.processors" value="false"/>
   </system-properties>

3. Save the standalone-full-ha.xml file.

4. 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-ha.xml

   • On Windows:

     standalone.bat -c standalone-full-ha.xml

Procedure

1. In a web browser, enter <node-IP-address>:8080/decision-central. Replace <node-IP-address> with the IP address of a particular node.
2. Enter the admin user credentials that you created during installation. The Business Central home page appears.
3. Select Menu → Design → Projects.
4. Click Try Samples → Mortgages → OK. The Assets window appears.
5. Click Create New Asset → Data Object.
6. Enter MyDataObject in the Data Object field and click OK.
7. Click Spaces → MySpace → Mortgages and confirm that MyDataObject is in the list of assets.

8. Enter the following URL in a web browser, where <node_IP_address> is the address of a different node of the cluster:

   http://<node_IP_address>:8080/decision-central

9. Enter the same credentials that you used to log in to Business Central on the first node, where you created the MyDataObject asset.
10. Select Menu→ Design → Projects.
11. Select the Mortgages project.
12. Verify that MyDataObject is in the asset list.
13. Delete the Mortgages project.

Procedure

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

4. Download Decision 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: Decision Manager
      • Version: 7.3
   2. Download Red Hat Decision Manager 7.3.0 Decision Server for All Supported EE8 Containers (rhdm-7.3.0-kie-server-ee8.zip).
5. Extract the rhdm-7.3.0-kie-server-ee8.zip archive to a temporary directory. In the following examples this directory is called TEMP_DIR.

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

   警告

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

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

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

    $ ./add-user.sh -a --user <USERNAME>  --password <PASSWORD> --role kie-server

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

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

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

   警告

   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.3-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.
8. Open the EAP_HOME/standalone/configuration/standalone.xml file in a text editor.

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

   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 start the headless Decision Manager controller, navigate to EAP_HOME/bin and enter the following command:

    • On Linux or UNIX-based systems:

      $ ./standalone.sh

    • On Windows:

      standalone.bat