Chapter 2. Red Hat Process Automation Manager clusters in a development (authoring) environment

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: Data Grid
   • Version: 7.3

2. Download and unzip the Red Hat JBoss Data Grid 7.3.0 Server (jboss-datagrid-7.3.0-1-server.zip) installation file to the preferred location on your system.

   The unzipped directory is referred to as JDG_HOME.

3. To run Red Hat Data Grid, navigate to JDG_HOME/bin and enter one of the following commands:

   • On Linux or UNIX-based systems:

     $ ./standalone.sh -c clustered.xml

   • On Windows:

     standalone.bat -c clustered.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: 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. Configure a server to export NFS version 4 shares. For instructions about exporting NFS shares on Red Hat Enterprise Linux, see Exporting NFS shares in Managing file systems. For more information about creating the NFS server, see How to configure NFS in RHEL 7.

2. On the server, create an /opt/kie/data share with the rw,sync,no_root_squash options by adding the following line to the /etc/exports file:

   /opt/kie/data *(rw,sync,no_root_squash)

   In this example, /opt/kie/data is the shared folder, * are the IP addresses allowed to connect to the NFS server, and (rw,sync,no_root_squash) are the minimum options required for NFS. For example:

   /opt/kie/data 192.268.1.0/24(rw,sync,no_root_squash)

   Note

   You can use another share name instead of '/opt/kie/data'. In this case, you must use this name when configuring all nodes that run Business Central.

3. On each client node, mount the shared folder in an existing directory:

   # mount <SERVER_IP>:/opt/kie/data /opt/kie/data/niogit

4. Add the following properties to the standalone-full-ha.xml file to bind the .niogit and maven-repository directories as nfs shared folders:

   <property name="org.uberfire.nio.git.dir" value="/opt/kie/data/niogit"/>
   <property name="org.guvnor.m2repo.dir" value="/opt/kie/data/maven-repository"/>

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 Process Automation 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: Process Automation Manager
      • Version: 7.6
   2. Download Red Hat Process Automation Manager 7.6.0 Business Central Deployable for Red Hat JBoss EAP 7 (rhpam-7.6.0-business-central-eap7-deployable.zip).
5. Extract the rhpam-7.6.0-business-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/rhpam-7.6.0-business-central-eap7-deployable/jboss-eap-7.2 to EAP_HOME.
7. Download and apply the latest Red Hat Process Automation 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,rest-all

   Note

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

   You must use LDAP or RH-SSO for high availability environments. For more information, see the Red Hat Single Sign-On Server Administration Guide.

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

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

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

Procedure

1. Mount the directory shared over NFS as /data. Enter the following commands as the root user:

   mkdir /data
   mount <NFS_SERVER_IP>:<DATA_SHARE> /data

   Replace <NFS_SERVER_IP> with the IP address or hostname of the NFS server machine. Replace <DATA_SHARE> with the share name that you configured (for example, /opt/kie/data).

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

3. Edit or add the properties under 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.

   • <INFINISPAN_NODE_IP> is the IP address where Red Hat Data Grid is installed.

     <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.infinispan.port"
          value="11222"/>
       <property name="org.appformer.ext.metadata.infinispan.host"
          value="<INFINISPAN_NODE_IP>"/>
       <property name="org.appformer.ext.metadata.infinispan.realm"
          value="ApplicationRealm"/>
       <property name="org.appformer.ext.metadata.infinispan.cluster"
          value="kie-cluster"/>
       <property name="org.appformer.ext.metadata.index"
          value="infinispan"/>
       <property name="org.uberfire.nio.git.dir"
          value="/data"/>
       <property name="es.set.netty.runtime.available.processors"
          value="false"/>
     </system-properties>

4. Optional: If the Red Hat Data Grid deployment requires authentication, edit or add the properties under the <system-properties> element and replace the following placeholders:

   • <SERVER_NAME> is the server name specified in your Red Hat Data Grid server configuration.

   • <SASL_QOP> is the combination of auth, auth-int and auth-conf values for your Red Hat Data Grid server configuration.

     <property name="org.appformer.ext.metadata.infinispan.server.name"
        value="<SERVER_NAME>"/>
     <property name="org.appformer.ext.metadata.infinispan.sasl.qop"
        value="<SASL_QOP>"/>
     <property name="org.appformer.ext.metadata.infinispan.username"
        value=""/>
     <property name="org.appformer.ext.metadata.infinispan.password"
        value=""/>

5. Save the standalone-full.xml file.

6. 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. In a web browser, enter <node-IP-address>:8080/business-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. Open the MySpace space.
5. Click Try Samples Mortgages OK. The Assets window appears.
6. Click Add Asset Data Object.
7. Enter MyDataObject in the Data Object field and click OK.
8. Click Spaces MySpace Mortgages and confirm that MyDataObject is in the list of assets.

9. 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/business-central

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