Chapter 5. Installing Red Hat Process Automation Manager from ZIP files
The Red Hat Process Automation Manager ZIP files (one for Business Central and one for Process Server) do not require a graphical user interface so you can install Red Hat Process Automation Manager using SSH.
You should install Business Central and the Process Server on different servers in production environments.
For information about installing the headless Process Automation Manager controller, see Chapter 9, Installing and running the headless Process Automation Manager controller.
5.1. Installing Business Central from the ZIP file
Business Central is a web console that enables you to perform the following tasks over individual components in a unified web-based environment:
- Create, manage, and edit your rules, processes, and related assets.
- Manage connected Process Server instances and their KIE containers (deployment units).
- Execute runtime operations against processes and tasks in Process Server instances connected to Business Central.
Prerequisites
-
A backed-up Red Hat JBoss EAP installation version 7.2 or higher is available. The base directory of the Red Hat JBoss EAP installation is referred to as
EAP_HOME
. - Sufficient user permissions to complete the installation are granted.
The following file is downloaded as described in Chapter 3, Downloading the Red Hat Process Automation Manager installation files:
rhpam-7.3.0-business-central-eap7-deployable.zip
Procedure
-
Extract the
rhpam-7.3.0-business-central-eap7-deployable.zip
file to a temporary directory. In the following examples this directory is calledTEMP_DIR
. Copy the contents of the
TEMP_DIR/rhpam-7.3.0-business-central-eap7-deployable/jboss-eap-7.2
directory toEAP_HOME
. When prompted, merge or replace files.WarningEnsure the names of the Red Hat Process Automation Manager deployments you are copying do not conflict with your existing deployments in the Red Hat JBoss EAP instance.
5.2. Installing Process Server from the ZIP file
Process Server provides the runtime environment for business assets and accesses the data stored in the assets repository (knowledge store).
Prerequisites
-
A backed-up Red Hat JBoss EAP installation version 7.2 or higher is available. The base directory of the Red Hat JBoss EAP installation is referred to as
EAP_HOME
. - Sufficient user permissions to complete the installation are granted.
The following file is downloaded as described in Chapter 3, Downloading the Red Hat Process Automation Manager installation files:
rhpam-7.3.0-kie-server-ee8.zip
Procedure
-
Extract the
rhpam-7.3.0-kie-server-ee8.zip
archive to a temporary directory. In the following examples this directory is calledTEMP_DIR
. Copy the
TEMP_DIR/rhpam-7.3.0-kie-server-ee8/rhpam-7.3.0-kie-server-ee8/kie-server.war
directory toEAP_HOME/standalone/deployments/
.WarningEnsure the names of the Red Hat Process Automation Manager deployments you are copying do not conflict with your existing deployments in the Red Hat JBoss EAP instance.
-
Copy the contents of the
TEMP_DIR/rhpam-7.3.0-kie-server-ee8/rhpam-7.3.0-kie-server-ee8/SecurityPolicy/
toEAP_HOME/bin
. When asked to overwrite files, click Replace. -
In the
EAP_HOME/standalone/deployments/
directory, create an empty file namedkie-server.war.dodeploy
. This file ensures that Process Server is automatically deployed when the server starts.
5.3. Configuring JDBC data sources for Process Server
A data source is an object that enables a Java Database Connectivity (JDBC) client, such as an application server, to establish a connection with a database. Applications look up the data source on the Java Naming and Directory Interface (JNDI) tree or in the local application context and request a database connection to retrieve data. You must configure data sources for Process Server to ensure proper data exchange between the servers and the designated database.
Prerequisites
- The JDBC providers that you want to use to create database connections are configured on all servers on which you want to deploy Process Server, as described in the "Creating Datasources" and "JDBC Drivers" sections of the Red Hat JBoss Enterprise Application Server Configuration Guide.
- The Red Hat Process Automation Manager 7.3.0 Add Ons (rhpam-7.3.0-add-ons.zip) file is downloaded from the Software Downloads page in the Red Hat Customer Portal.
Procedure
-
Open
EAP_HOME/standalone/configuration/standalone-full.xml
in a text editor and locate the<system-properties>
tag. Add the following properties to the
<system-properties>
tag where<DATASOURCE>
is the name of your data source and<HIBERNATE_DIALECT>
is the hibernate dialect for your database.NoteThe default value of the
org.kie.server.persistence.ds
property isjava:jboss/datasources/ExampleDS
. The default value of theorg.kie.server.persistence.dialect
property isorg.hibernate.dialect.H2Dialect
.<property name="org.kie.server.persistence.ds" value="<DATASOURCE>"/> <property name="org.kie.server.persistence.dialect" value="<HIBERNATE_DIALECT>"/>
For example:
<system-properties> <property name="org.kie.server.repo" value="${jboss.server.data.dir}"/> <property name="org.kie.example" value="true"/> <property name="org.jbpm.designer.perspective" value="full"/> <property name="designerdataobjects" value="false"/> <property name="org.kie.server.user" value="rhpamUser"/> <property name="org.kie.server.pwd" value="rhpam123!"/> <property name="org.kie.server.location" value="http://localhost:8080/kie-server/services/rest/server"/> <property name="org.kie.server.controller" value="http://localhost:8080/business-central/rest/controller"/> <property name="org.kie.server.controller.user" value="kieserver"/> <property name="org.kie.server.controller.pwd" value="kieserver1!"/> <property name="org.kie.server.id" value="local-server-123"/> <!-- Data source properties. --> <property name="org.kie.server.persistence.ds" value="java:jboss/datasources/KieServerDS"/> <property name="org.kie.server.persistence.dialect" value="org.hibernate.dialect.PostgreSQLDialect"/> </system-properties>
The following dialects are supported:
-
DB2:
org.hibernate.dialect.DB2Dialect
-
MSSQL:
org.hibernate.dialect.SQLServer2012Dialect
-
MySQL:
org.hibernate.dialect.MySQL5InnoDBDialect
-
MariaDB:
org.hibernate.dialect.MySQL5InnoDBDialect
-
Oracle:
org.hibernate.dialect.Oracle10gDialect
-
PostgreSQL:
org.hibernate.dialect.PostgreSQL82Dialect
-
PostgreSQL plus:
org.hibernate.dialect.PostgresPlusDialect
-
Sybase:
org.hibernate.dialect.SybaseASE157Dialect
5.4. Creating users
Before you can log in to Business Central or Process Server, you must create users. This section shows you how to create a Business Central user with the admin
, rest-all
, and kie-server
roles and a Process Server user that has the kie-server
role. For information about roles, see Chapter 2, Roles and users.
Prerequisites
Red Hat Process Automation Manager is installed in the base directory of the Red Hat JBoss EAP installation (EAP_HOME
).
Procedure
-
In a terminal application, navigate to the
EAP_HOME/bin
directory. 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
NoteMake 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).
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
Make a note of your user names and passwords.
NoteIf you installed Business Central and Process Server in the same server instance, you can create a single user that has both of these roles:
$ ./add-user.sh -a --user <USERNAME> --password <PASSWORD> --role admin,rest-all,kie-server
You should install Business Central and Process Server on different servers in production environments.
5.5. Configuring Process Server with the integrated Process Automation Manager controller
Only make the changes described in this section if Process Server will be managed by Business Central and you installed Red Hat Process Automation Manager from the ZIP files. If you did not install Business Central, you can use the headless Process Automation Manager controller to manage Process Server, as described in Chapter 9, Installing and running the headless Process Automation Manager controller.
Process Server can be managed or it can be unmanaged. If Process Server is unmanaged, you must manually create and maintain KIE containers (deployment units). If Process Server is managed, the Process Automation Manager controller manages the Process Server configuration and you interact with the Process Automation Manager controller to create and maintain KIE containers.
The Process Automation Manager controller is integrated with Business Central. If you install Business Central, you can use the Execution Server page in Business Central to interact with the Process Automation Manager controller.
If you installed Red Hat Process Automation Manager from the ZIP files, you must edit the standalone-full.xml
file in both the Process Server and Business Central installations to configure Process Server with the integrated Process Automation Manager controller.
Prerequisites
Business Central and Process Server are installed in the base directory of the Red Hat JBoss EAP installation (
EAP_HOME
) as described in the following sections:- Section 5.1, “Installing Business Central from the ZIP file”
Section 5.2, “Installing Process Server from the ZIP file”
NoteYou should install Business Central and Process Server on different servers in production environments. However, if you install Process Server and Business Central on the same server, for example in a development environment, make the changes described in this section in the shared
standalone-full.xml
file.
On Business Central server nodes, a user with the
rest-all
role exists.For more information, see Section 5.4, “Creating users”.
Procedure
In the Business Central
EAP_HOME/standalone/configuration/standalone-full.xml
file, uncomment the following properties in the<system-properties>
section and replace<USERNAME>
and<USER_PWD>
with the credentials of a user with thekie-server
role:<property name="org.kie.server.user" value="<USERNAME>"/> <property name="org.kie.server.pwd" value="<USER_PWD>"/>
In the Process Server
EAP_HOME/standalone/configuration/standalone-full.xml
file, uncomment the following properties in the<system-properties>
section.<property name="org.kie.server.controller.user" value="<CONTROLLER_USER>"/> <property name="org.kie.server.controller.pwd" value="<CONTROLLER_PWD>"/> <property name="org.kie.server.id" value="<KIE_SERVER_ID>"/> <property name="org.kie.server.location" value="http://<HOST>:<PORT>/kie-server/services/rest/server"/> <property name="org.kie.server.controller" value="<CONTROLLER_URL>"/>
Replace the following values:
-
Replace
<CONTROLLER_USER>
and<CONTROLLER_PWD>
with the credentials of a user with therest-all
role. -
Replace
<KIE_SERVER_ID>
with the ID or name of the Process Server installation, for example,rhpam-7.3.0-process_server-1
. -
Replace
<HOST>
with the ID or name of the Process Server host, for example,localhost
or192.7.8.9
. Replace
<PORT>
with the port of the Process Server host, for example,8080
.NoteThe
org.kie.server.location
property specifies the location of Process Server.Replace
<CONTROLLER_URL>
with the URL of Business Central. Process Server connects to this URL during startup.If you installed Business Central using the installer or Red Hat JBoss EAP zip installations,
<CONTROLLER_URL>
has this format:http://<HOST>:<PORT>/business-central/rest/controller
If you are running Business Central using the
standalone.jar
file,<CONTROLLER_URL>
has this format:http://<HOST>:<PORT>/rest/controller
-
Replace