Chapter 7. Installing the headless Process Automation Manager controller
You can configure Process Server to run in managed or unmanaged mode. 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, use the Execution Server page to create and maintain KIE containers. However, if you do not install Business Central, you can install the headless Process Automation Manager controller and use the REST API or the Process Server Java Client API to interact with it.
Prerequisites
-
A Red Hat JBoss Web Server 5.0 or higher server installation is available. The base directory of the JBoss Web Server installation is referred to as
JWS_HOME
. - Sufficient user permissions to complete the installation are granted.
The
rhpam-7.1-controller-jws.zip
file is downloaded. To download this file:- Click Download next to Red Hat Process Automation Manager 7.1.0 Add Ons on the Product Downloads page of the Red Hat Customer Portal.
-
Unzip the
rhpam-7.1.0-add-ons.zip
file. This file is in the unzipped directory.
Procedure
-
Extract the
rhpam-7.1-controller-jws.zip
archive to a temporary directory. In the following examples this directory is calledTEMP_DIR
. Copy the
TEMP_DIR/rhpam-7.1-controller-jws.zip/controller.war
directory to theJWS_HOME/tomcat/webapps
directory.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 Web Server instance.
-
Remove the
.war
extensions from thecontroller.war
folder. -
Copy the contents of the
TEMP_DIR/rhpam-7.1-controller-jws/SecurityPolicy/
directory toJWS_HOME/bin
. When asked to overwrite files, select Yes. Add the
kie-server
role and user to theJWS_HOME/tomcat/conf/tomcat-users.xml
file. In the following example,<USERNAME>
and<PASSWORD>
is a user and password combination of your choice:<role rolename="kie-server"/> <user username="<USER_NAME>" password="<PASSWORD>" roles="kie-server"/>
In the
JWS_HOME/tomcat/bin
directory of the instance running Process Server, create a readablesetenv.sh
file with the following content:CATALINA_OPTS="-Xmx1024m -Dorg.jbpm.server.ext.disabled=true -Dorg.jbpm.ui.server.ext.disabled=true -Dorg.jbpm.case.server.ext.disabled=true -Dorg.kie.server.controller.user=<CONTROLLER_USER> -Dorg.kie.server.controller.pwd=<CONTROLLER_PWD> -Dorg.kie.server.id=<KIE_SERVER_ID> -Dorg.kie.server.location=http://<HOST>:<PORT>/kie-server/services/rest/server -Dorg.kie.server.controller=http://<HOST>:<PORT>/controller/rest/controller"
In the
JWS_HOME/tomcat/bin
directory of the instance running the headless Process Automation Manager controller, create a readablesetenv.sh
file with the following content:CATALINA_OPTS="-Dorg.kie.server.user=<USERNAME> -Dorg.kie.server.pwd=<USER_PWD>"
To start the headless Process Automation Manager controller, enter one of the following commands in the
JWS_HOME/tomcat/bin
directory:On Linux or UNIX-based systems:
$ ./startup.sh
On Windows:
startup.bat
-
After a few minutes, review the the
JWS_HOME/tomcat/logs
directory and correct any errors. To verify that the headless Process Automation Manager controller is working on Red Hat JBoss Web Server, enter the following command. In this command, replace
<CONTROLLER>
and<CONTROLLER_PWD>
with the values in thetomcat-users.xml
file. The output of this command provides information about the Process Server instance.curl -X GET "http://<HOST>:<PORT>/controller/rest/controller/management/servers" -H "accept: application/xml" -u '<CONTROLLER>:<CONTROLLER_PWD>'
Alternatively, you can use the Process Server Java API Client to access the headless Process Automation Manager controller.