Chapter 3. Red Hat Process Automation Manager clusters in a development (authoring) 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. Install Red Hat JBoss EAP 7.1 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.1
   2. Click Download next to Red Hat JBoss Enterprise Application Platform 7.1.0. (JBEAP-7.1.0/jboss-eap-7.1.0.zip).
   3. Extract the jboss-eap-7.1.0.zip file. In the following steps, EAP_HOME is the jboss-eap-7.1/jboss-eap-7.1 directory.

2. On the cluster node where the Red Hat JBoss EAP domain controller will be started (the master node), 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.0
3. Download Red Hat Process Automation Manager 7.0.0 Business Central Deployable for Red Hat JBoss EAP 7 (rhpam-7.0.0-business-central-eap7-deployable.zip).
4. Extract the rhpam-7.0.0-business-central-eap7-deployable.zip file to a temporary directory. In the following examples this directory is called TEMP_DIR.
5. Copy the contents of TEMP_DIR/rhpam-7.0.0-business-central-eap7-deployable/jboss-eap-7.1 to EAP_HOME.

6. Repackage the business-central.war file:

   1. Navigate to the TEMP_DIR/rhpam-7.0.0-business-central-eap7-deployable/jboss-eap-7.1/standalone/deployments/business-central.war directory.
   2. Select the contents of the TEMP_DIR/rhpam-7.0.0-business-central-eap7-deployable/jboss-eap-7.1/standalone/deployments/business-central.war directory and create the business-central.zip file.
   3. Rename business-central.zip to business-central.war. This is the file that you will use to deploy Business Central on the cluster nodes.
   4. If desired, copy the new business-central.war file to a location that is more convenient to deploy from.

Procedure

1. On the the master node of the cluster (where you will run the domain controller), open the EAP_HOME/domain/configuration/domain.xml file in a text editor.

2. Make the following changes for each server group in the server-groups element:

   1. Specify the server-group name and jvm name.
   2. To enable high availability, change the profile to "full-ha" and the socket-binding-group to "full-ha-sockets".

   3. To prevent Business Central from running out of memory, increase the JVM maximum heap size to 1500m.

      <server-group name="some-server-group" profile="full-ha">
          <jvm name="some-jvm">
              <heap size="1000m" max-size="1500m"/>
          </jvm>
          <socket-binding-group ref="full-ha-sockets"/>
      </server-group>

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

   • <ELASTICSEARCH_NODE_IP> is the IP addresses where Elasticseach is installed.
   • <JMS_USER> is a Red Hat JBoss EAP application user. It is the user that Business Central uses to connect to the embedded JMS broker.

   • <JMS_USER_PASSWORD> is the password for <JMS_USER>.

     <system-properties>
       <property name="appformer-jms-connection-mode" value="JNDI"/>
       <property name="appformer-jms-username" value="<JMS_USER>  "/>
       <property name="appformer-jms-password" value="<JMS_USER_PASSWORD>"/>
       <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="appformer-jms-connection-factory" value="java:/ConnectionFactory"/>
     </system-properties>

4. In the <subsystem xmlns="urn:jboss:domain:messaging-activemq:2.0"> element, make the following changes:

   1. Replace <cluster password="${jboss.messaging.cluster.password:CHANGE ME!!}"/> with <cluster user="<CLUSTER_USER>" password="<CLUSTER_PWD>"/> where <CLUSTER_USER> is the user used by Red Hat JBoss EAP to form a messaging cluster and <CLUSTER_PWD> is the password for that user.

   2. In the security-setting element , add the role of the <JMS_USER> to a new role-name element, for example:

      <security-setting name="#">
          <role name="guest" send="true" consume="true" create-non-durable-queue="true" delete-non-durable-queue="true"/>
          <role name="admin" send="true" consume="true" create-non-durable-queue="true" delete-non-durable-queue="true"/>
      </security-setting>

5. Save the domain.xml file.

Procedure

1. Open the EAP_HOME/domain/configuration/host.xml file or the 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 the system properties listed in Table 3.1, “Cluster node properties”
4. Save the host.xml or host-slave.xml file.

Procedure

1. Add Red Hat JBoss EAP management users to the master node of the cluster (where you configured the domain.xml file) as described in the Red Hat JBoss EAP 7.1 Configuration Guide.

2. On each node of the cluster, add the following users:

   1. Add Business Central administration users as described in Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss EAP 7.1.

   2. Add the JMS user, where <JMS_USER> and <JMS_PWD> is the JMS user and password combination that you added to the domain.xml file:

      $ ./add-user.sh -a --user <JMS_USER> --password <JMS_PWD> --role admin

3. Start the cluster by starting the the master node first, then start each of the slave nodes.

   1. To start the master node, enter one of the following commands:

      • On Linux or UNIX-based systems, enter:

        <EAP_HOME>/bin/domain.sh

      • On Windows, enter:

        <EAP_HOME>/bin/domain.bat

   2. To start the slave nodes, on each of the slave nodes enter one of the following commands, where <MASTER_NODE_IP> is the IP address of the master node (where the domain controller is configured):

      • On Linux or UNIX-based systems, enter:

        <EAP_HOME>/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=<MASTER_NODE_IP>

      • On Windows, enter:

        <EAP_HOME>/bin/domain.bat --host-config=host-slave.xml -Djboss.domain.master.address=<MASTER_NODE_IP>

        For more information, see the following sections of the Red Hat JBoss EAP 7.1 Configuration Guide:

      • "Starting JBoss EAP"
      • "Managed Domain Configuration Files"
4. On each node of the cluster, review the EAP_HOME/domain/servers/SERVER_NAME/log/server.log file to verify that the nodes are available.

5. To deploy the business-central.war file into the server group, complete the following steps:

   1. On the master node, log in to the Red Hat JBoss EAP Administration console 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 business-central.war file, and click Next.

   5. Click Enable and click Next. When the deployment is complete, Business Central starts automatically on each node.

      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.