3.2. Installing Red Hat JBoss BPM Suite on Red Hat JBoss Enterprise Application Platform
To install Red Hat JBoss BPM Suite 6.3 deployable on Red Hat JBoss EAP:
-
Download the
Red Hat JBoss Enterprise Application Platform 6.4.0
ZIP file from the Customer Portal. -
Extract the ZIP file. This location is your
EAP_HOME
. Patch the Red Hat JBoss EAP to the supported version for your Red Hat JBoss BPM Suite version.
- See Red Hat JBoss BPM Suite 6 Supported Configurations to verify which patch is applicable for your Red Hat JBoss BPM Suite version.
- See Patching a Zip/Installer Installation from the Red Hat JBoss EAP Installation Guide for further information about applying patches.
-
Download the
Red Hat JBoss BPM Suite 6.3.0 Deployable for EAP 6
ZIP file. Extract the file and copy
jboss-eap-6.4/bin/*
intoEAP_HOME/bin/*
. When asked, merge the directories.If you want to run Red Hat JBoss BPM Suite in the standalone mode:
-
Copy
jboss-eap-6.4/standalone/configuration/*
intoEAP_HOME/standalone/configuration/
. Copy
jboss-eap-6.4/standalone/deployments/*
intoEAP_HOME/standalone/deployments/
.NoteIf you already have deployments on your Red Hat JBoss EAP, ensure that your current deployments do not have colliding names with Red Hat JBoss BPM Suite deployments.
-
Copy
If you want to run Red Hat JBoss BPM Suite in the domain mode:
Copy
jboss-eap-6.4/domain/configuration/*
intoEAP_HOME/domain/configuration/
.WarningMake sure this step is performed by the same user account that was used to install Red Hat JBoss EAP. This account must not be a superuser account.
Add an application user:
./EAP_HOME/bin/add-user.sh -a --user bpmsAdmin --password password@1 --role kie-server,admin,rest-all,analyst
To start Red Hat JBoss BPM Suite in standalone mode:
-
Change into
EAP_HOME/bin
. Execute:
In a Unix environment:
./standalone.sh
In a Windows environment:
standalone.bat
You can now log into Business Central in your web browser: localhost:8080/business-central
.
Configuring Domain Mode
If you installed Red Hat JBoss BPM Suite as described in Section 3.2, “Installing Red Hat JBoss BPM Suite on Red Hat JBoss Enterprise Application Platform”, deploy Red Hat JBoss BPM Suite web applications manually.
The business-central.war
, dashbuilder.war
, and kie-server.war
applications are supplied in the Red Hat JBoss BPM Suite 6.3.0 Deployable for EAP 6
ZIP file as directories. To deploy the applications into domain mode:
Package the application directories into archives:
Extract the following files from the
Red Hat JBoss BPM Suite 6.3.0 Deployable for EAP 6
ZIP file:-
jboss-eap-6.4/standalone/deployments/business-central.war
-
jboss-eap-6.4/standalone/deployments/kie-server.war
-
jboss-eap-6.4/standalone/deployments/dashbuilder.war
-
Create a ZIP file with the content of the
business-central.war
,kie-server.war
, andkie-server.war
directories, for example:Change into the directory:
cd business-central.war
-
Execute
zip -r business-central.war .
to create a ZIP file of the content of thebusiness-central.war
directory. Repeat this procedure for all the web applications you want to deploy.
This ensures that
business-central.war
,kie-server.war
, anddashbuilder.war
are archives, not directories.
Deploy the archives:
Add a management user:
./EAP_HOME/bin/add-user.sh -b --user mgmtAdmin --password password@1 --role admin
-
Execute
./EAP_HOME/bin/domain.sh
. -
Log into
http://localhost:9990/
using your management user. - Click Deployments → Content Repository → Add.
- Select and upload the web archive from the file system.
Select the deployment and click Assign.
NoteIf you want to deploy multiple Red Hat JBoss BPM Suite nodes on a single machine, set ports and other properties before assigning the deployment to a server. See the section called “Red Hat JBoss BPM Suite Settings for Red Hat JBoss EAP” for more information.
- Select the server group.
You can now log into Business Central at localhost:8080/business-central
.
To log into 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 Section 5.2, “Creating Users”.
Red Hat JBoss BPM Suite Settings for Red Hat JBoss EAP
If you want to run multiple instances of Red Hat JBoss EAP with Red Hat JBoss BPM Suite, the best practice is to set the following properties:
-
org.uberfire.nio.git.dir
-
org.uberfire.metadata.index.dir
-
org.uberfire.nio.git.ssh.cert.dir
When multiple Red Hat JBoss BPM Suite nodes are used on a single machine, the below properties need to be specified:
-
org.uberfire.nio.git.daemon.host
: can belocalhost
. -
org.uberfire.nio.git.daemon.port
-
org.uberfire.nio.git.ssh.host
: can belocalhost
. -
org.uberfire.nio.git.ssh.port
Both the org.uberfire.nio.git.daemon.port
and the org.uberfire.nio.git.ssh.port
require different port values to avoid port conflicts.
Set the properties in the EAP_HOME/domain/configuration/host.xml
file:
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.