2.2. The EAP6 bundle installation

This section describes installing the Red Hat JBoss BPM Suite package deployable for Red Hat JBoss Enterprise Application Platform (EAP).

Note

The minimum supported configuration of Red Hat JBoss EAP for Red Hat JBoss BPM Suite installation is 6.1.1 and not 6.1.0.
Report a bug

2.2.1. Downloading the EAP6 package

To download the deployable Red Hat JBoss BPM Suite package for JBoss Enterprise Application Platform, do the following:
  1. Go to the Red Hat Customer Portal and log in.
  2. Click Downloads → Products Downloads.
  3. In the Product Downloads page that opens, click Red Hat JBoss BPM Suite.
  4. From the Version drop-down menu, select version 6.0.3.
  5. On the Software Downloads page that opens, navigate to the Red Hat JBoss BPM Suite 6.0.3 Deployable for EAP 6.1.1 row and click Download.
Report a bug

2.2.2. Installing the EAP6 package

Installation on a fresh EAP instance

To install the deployable package for an EAP that has yet to be configured, do the following:
  1. Extract the zip package deployable for EAP you downloaded from the Red Hat Customer Portal.
  2. Merge the extracted zip package deployable for EAP into the EAP SERVER_HOME directory.

    Warning

    This step must be performed by the same user account that was used to install EAP. This account must not be a superuser account.
  3. In this process, multiple files in the EAP SERVER_HOME directory will be overwritten and you must let the unzip process overwrite these files. An example of a file that is overwritten is the SERVER_HOME/bin/product.conf file. After a successful merge, this file must contain the string slot=bpms. You can open this file to verify that the files have been overwritten successfully.
In Red Hat Enterprise Linux, you can use the following command to extract the BPMS zip file and merge it into your server directory correctly in one step, if you execute this command in the directory where you have downloaded the zip file: 
unzip -u jboss-bpms-VERSION-TYPE.zip -d SERVER_HOME_PARENT_DIR

Example 2.1. The unzip command

unzip -u jboss-bpms-6.0.3-redhat-7-deployable-eap6.x.zip -d /home/john/myServers/
On server start-up, Red Hat JBoss BPM Suite will be deployed.

Installation on an existing EAP configuration

Warning

These instructions are for installing, and NOT for updating an existing BPMS instance. Make sure that there is no existing BPMS install in the target EAP.
To install the deployable package for a previously configured EAP, do the following:
  1. Extract the zip package deployable for EAP you downloaded from the Red Hat Customer Portal.
  2. Unzip the downloaded zip archive; however, do not overwrite all of the files. Manually merge the following files into the SERVER_HOME directory.
    • jboss-eap-6.1/domain/configuration/* - (please be aware that BPMS requires JMS, so JMS is added by default into all profiles in domain.xml provided by BPMS distribution.)
    • jboss-eap-6.1/standalone/configuration/* - (please be aware that BPMS requires JMS, so JMS is added by default into all profiles config files (especially into standalone.xml and standalone-ha.xml) provided by BPMS distribution.)
    • jboss-eap-6.1/modules/layers.conf
    • jboss-eap-6.1/bin/product.conf
  3. Ensure the target EAP does not include a deployment with a colliding name. Copy the folder jboss-eap-6.1/standalone/deployments into the EAP_HOME directory from the BPMS distribution.
  4. Make sure no EAP module layer is already called BPMS and copy the folder jboss-eap-6.1/modules/system/layers/bpms into the EAP 6.1.1 folder.
Report a bug

2.2.3. Installing BPM Suite in the Domain Mode

To install the deployable package for an EAP in the domain mode, do the following steps:
  1. Extract the downloaded EAP Deployable ZIP file from Red Hat Customer Portal and copy the following directories into your local installation of EAP 6.1:
    • bin
    • domain
    • modules
    Skip the standalone directory.
  2. On the command line, move to the /domain directory and start the domain:
    In a Unix environment, run: 
    ./domain.sh
    In a Windows environment, run: 
    ./domain.bat
  3. Deploy the archive either via ${jboss-eap-home}/bin/jboss-cli.sh / ${jboss-eap-home}/bin/jboss-cli.bat, or via management web UI (localhost:9990/):

    Note

    The web applications business-central.war and dashbuilder.war supplied in the EAP deployable binaries are directories, but for deployment into the domain, you have to use WAR archives. To create them, simply zip the content of the business-central.war and the dashbuilder.war directories.
    1. To deploy the archive via ${jboss-eap-home}/bin/jboss-cli.sh or ${jboss-eap-home}/bin/jboss-cli.bat, move into the ${jboss-eap-home}/bin directory and deploy the WAR file:
      In a Unix environment, run: 
      ./jboss-cli.sh
      In a Windows environment, run: 
      ./jboss-cli.bat
    2. To deploy the archive via management web UI (localhost:9990/):
      • log in using your EAP management account
      • select Domain -> Manage Deployments -> Content Repository -> Add
      • select the web archive from the file system, upload the web archive
      • select the deployment, click the Assign button
      • select the server group

Note

In order to log in to Business Central deployed on Host Controller (HC) machines, the user created on the Domain Controller Machine has to be created on the Host Controller machines as well, by following the steps in the Section 4.2, “Creating users” section.

Installing Multiple BPMS Server Instances

In many situations, users may want to group together a set of EAP 6 nodes on the same machine and give them a meaningful name for easy maintenance. Unique values need to be incorporated for the system properties for each server instance. Listed below are the common properties that can be specified with a single BPMS node to change the default configuration; however, they should be specified for multiple nodes running on a single machine so every node can point to a different directory:
  • org.uberfire.nio.git.dir
  • org.uberfire.metadata.index.dir
  • org.uberfire.nio.git.ssh.cert.dir
When multiple BPMS nodes are used on a single machine, the below properties need to be specified:
  • org.uberfire.nio.git.daemon.host - can be left on default to bind to localhost.
  • org.uberfire.nio.git.daemon.port
  • org.uberfire.nio.git.ssh.host - can be left on default to bind to localhost.
  • org.uberfire.nio.git.ssh.port

Note

Both the org.uberfire.nio.git.daemon.port and the org.uberfire.nio.git.ssh.port require different port values in order to avoid port conflicts.
Incorporate the previous properties in the $EAP_HOME/domain/configuration/host.xml file as illustrated in the two nodes below:
Node A: 
<system-properties>
    <property name="org.uberfire.nio.git.dir" value="/valid/path/.." boot-time="false"/>
    <property name="org.uberfire.metadata.index.dir" value="/valid/path/.." boot-time="false"/>
    <property name="org.uberfire.nio.git.ssh.cert.dir" value="/valid/path/.." boot-time="false"/>

    <property name="org.uberfire.nio.git.daemon.host" value="10.10.10.10" boot-time="false"/>
    <property name="org.uberfire.nio.git.daemon.port" value="9417" boot-time="false"/>
    <property name="org.uberfire.nio.git.ssh.host" value="10.10.10.10" boot-time="false"/>
    <property name="org.uberfire.nio.git.ssh.port" value="8002" boot-time="false"/>
</system-properties>
Node B: 
<system-properties>
    <property name="org.uberfire.nio.git.dir" value="/valid/path/.." boot-time="false"/>
    <property name="org.uberfire.metadata.index.dir" value="/valid/path/.." boot-time="false"/>
    <property name="org.uberfire.nio.git.ssh.cert.dir" value="/valid/path/.." boot-time="false"/>

    <property name="org.uberfire.nio.git.daemon.host" value="10.10.10.10" boot-time="false"/>
    <property name="org.uberfire.nio.git.daemon.port" value="9418" boot-time="false"/>
    <property name="org.uberfire.nio.git.ssh.host" value="10.10.10.10" boot-time="false"/>
    <property name="org.uberfire.nio.git.ssh.port" value="8003" boot-time="false"/>
</system-properties>
The system properties depicted above should indicate the host, port, or location of the .index or .niogit files. These files, which should be used by a respective node, would then be grouped in a particular domain.
Report a bug