Red Hat Process Automation Manager 7.0 Installing …...Installing and configuring Process Server on IBM WebSphere Application Server Installing and configuring Process Server on Oracle

Red Hat Process Automation Manager70

Installing and configuring Red Hat ProcessAutomation Manager on Red Hat JBoss EAP 71

Last Updated 2018-08-24

Red Hat Process Automation Manager 70 Installing and configuring Red

Hat Process Automation Manager on Red Hat JBoss EAP 71

Red Hat Customer Content Servicesbrms-docsredhatcom

Legal Notice

Copyright copy 2018 Red Hat Inc

The text of and illustrations in this document are licensed by Red Hat under a Creative CommonsAttributionndashShare Alike 30 Unported license (CC-BY-SA) An explanation of CC-BY-SA isavailable athttpcreativecommonsorglicensesby-sa30 In accordance with CC-BY-SA if you distribute this document or an adaptation of it you mustprovide the URL for the original version

Red Hat as the licensor of this document waives the right to enforce and agrees not to assertSection 4d of CC-BY-SA to the fullest extent permitted by applicable law

Red Hat Red Hat Enterprise Linux the Shadowman logo JBoss OpenShift Fedora the Infinitylogo and RHCE are trademarks of Red Hat Inc registered in the United States and othercountries

Linux reg is the registered trademark of Linus Torvalds in the United States and other countries

Java reg is a registered trademark of Oracle andor its affiliates

XFS reg is a trademark of Silicon Graphics International Corp or its subsidiaries in the UnitedStates andor other countries

MySQL reg is a registered trademark of MySQL AB in the United States the European Union andother countries

Nodejs reg is an official trademark of Joyent Red Hat Software Collections is not formally relatedto or endorsed by the official Joyent Nodejs open source or commercial project

The OpenStack reg Word Mark and OpenStack logo are either registered trademarksservice marksor trademarksservice marks of the OpenStack Foundation in the United States and othercountries and are used with the OpenStack Foundations permission We are not affiliated withendorsed or sponsored by the OpenStack Foundation or the OpenStack community

All other trademarks are the property of their respective owners

Abstract

This document describes how to install Red Hat Process Automation Manager on a Red Hat JBossEAP 71 installation

Table of Contents

PREFACE

CHAPTER 1 ABOUT RED HAT PROCESS AUTOMATION MANAGER

CHAPTER 2 ROLES AND USERS

CHAPTER 3 DOWNLOADING THE RED HAT PROCESS AUTOMATION MANAGER INSTALLATION FILES

CHAPTER 4 USING THE RED HAT PROCESS AUTOMATION MANAGER INSTALLER41 USING THE INSTALLER IN INTERACTIVE MODE42 USING THE INSTALLER IN CLI MODE43 USING THE INSTALLER TO CONFIGURE PROCESS SERVER WITH THE PROCESS AUTOMATION MANAGERCONTROLLER

CHAPTER 5 INSTALLING RED HAT PROCESS AUTOMATION MANAGER FROM ZIP FILES51 INSTALLING BUSINESS CENTRAL FROM THE ZIP FILE52 INSTALLING PROCESS SERVER FROM THE ZIP FILE53 CONFIGURING JDBC DATA SOURCES FOR PROCESS SERVER54 CREATING USERS55 CONFIGURING PROCESS SERVER WITH THE INTEGRATED PROCESS AUTOMATION MANAGERCONTROLLER

CHAPTER 6 RUNNING RED HAT PROCESS AUTOMATION MANAGER

CHAPTER 7 INSTALLING AND RUNNING THE HEADLESS PROCESS AUTOMATION MANAGER CONTROLLER

71 INSTALLING THE HEADLESS PROCESS AUTOMATION MANAGER CONTROLLER711 Creating a controller user712 Configuring Process Server and the headless Process Automation Manager controller

72 RUNNING THE HEADLESS PROCESS AUTOMATION MANAGER CONTROLLER

CHAPTER 8 RUNNING STANDALONE BUSINESS CENTRAL81 SUPPORTED PROPERTIES

CHAPTER 9 SETTING MAVEN DEPENDENCIES IN YOUR PROJECT91 MODIFY THE MAVEN SETTINGS FILE92 MODIFY THE MAVEN POM FILE

CHAPTER 10 IMPORTING PROJECTS FROM GIT REPOSITORIES

CHAPTER 11 VERIFYING THE RED HAT PROCESS AUTOMATION MANAGER INSTALLATION

CHAPTER 12 CUSTOMIZING BUSINESS CENTRAL121 CUSTOMIZING THE BUSINESS CENTRAL LOGIN PAGE122 CUSTOMIZING BUSINESS CENTRAL APPLICATION HEADER

CHAPTER 13 INTEGRATING LDAP AND SSL

CHAPTER 14 RELATED INFORMATION

CHAPTER 15 NEXT STEPS

APPENDIX A VERSIONING INFORMATION

1313141416

2121222224

292929

363636

Table of Contents

Red Hat Process Automation Manager 70 Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss EAP 71

PREFACEThis document describes how to install Red Hat Process Automation Manager on a Red Hat JBossEnterprise Application Platform 71 instance

Prerequisite

Review the information in Planning a Red Hat Process Automation Manager installation

PREFACE

CHAPTER 1 ABOUT RED HAT PROCESS AUTOMATIONMANAGER

Red Hat Process Automation Manager is the Red Hat middleware platform for creating businessautomation applications and microservices It enables enterprise business and IT users to documentsimulate manage automate and monitor business processes and policies It is designed to empowerbusiness and IT users to collaborate more effectively so business applications can be changed easilyand quickly

Red Hat JBoss Enterprise Application Platform (Red Hat JBoss EAP) 71 is a certified implementationof the Java Enterprise Edition 7 (Java EE 7) full and web profile specifications Red Hat JBoss EAPprovides preconfigured options for features such as high availability clustering messaging anddistributed caching It also enables users to write deploy and run applications using the various APIsand services that Red Hat JBoss EAP provides

The instructions in this document explain how to install Red Hat Process Automation Manager in a RedHat JBoss EAP 71 server instance For instruction on how to install Red Hat Process AutomationManager in other environments see the following documents

Installing and configuring Process Server on IBM WebSphere Application Server

Installing and configuring Process Server on Oracle WebLogic Server

Deploying a Red Hat Process Automation Manager 70 authoring environment on Red Hat OpenShiftContainer Platform

Deploying a Red Hat Process Automation Manager 70 immutable server environment on Red HatOpenShift Container Platform

Deploying a Red Hat Process Automation Manager 70 managed server environment on Red HatOpenShift Container Platform

For information on supported components see the following documents What is the mappingbetween RHPAM product and maven library version Red Hat Process Automation Manager 7Supported Configurations

CHAPTER 2 ROLES AND USERSTo access Business Central or Process Server you must create users and assign them appropriateroles before the servers are started This section describes available Red Hat Process AutomationManager user roles

The admin analyst developer manager process-admin user and rest-allroles are reserved for Business Central The kie-server role is reserved for ProcessServer For this reason the available roles can differ depending on whether BusinessCentral Process Server or both are installed

admin Users with the admin role are the Business Central administrators They can manageusers and create clone and manage the repositories They have full access to make requiredchanges in the application Users with the admin role have access to all areas within Red HatProcess Automation Manager

analyst Users with the analyst role have access to all high-level features They can modeland execute their projects However these users cannot add contributors to spaces or deletespaces in the Design rarr Projects view Access to the Deploy rarr Execution Servers view whichis intended for administrators is not available to users with the analyst role However theDeploy button is available to these users when they access the Library perspective

developer Users with the developer role have access to almost all features and canmanage rules models process flows forms and dashboards They can manage the assetrepository they can create build and deploy projects and they can use Red Hat JBossDeveloper Studio to view processes Only certain administrative functions such as creatingand cloning a new repository are hidden from users with the developer role

manager Users with the manager role can view reports These users are usually interested instatistics about the business processes and their performance business indicators and otherbusiness-related reporting A user with this role has access only to process and task reports

process-admin Users with the process-admin role are business process administratorsThey have full access to business processes business tasks and execution errors These userscan also view business reports and have access to the Task Inbox list

user Users with the user role can work on the Task Inbox list which contains business tasksthat are part of currently running processes Users with this role can view process and taskreports and manage processes

rest-all Users with the rest-all role can access Business Central REST capabilities

kie-server Users with the kie-server role can access Process Server (KIE Server) RESTcapabilities This role is mandatory for users to have access to Manage and Track views inBusiness Central

CHAPTER 3 DOWNLOADING THE RED HAT PROCESSAUTOMATION MANAGER INSTALLATION FILES

Depending on your environment and installation requirements download a Red Hat ProcessAutomation Manager distribution

Procedure

1 Navigate to the Software Downloads page in the Red Hat Customer Portal (login required) andselect the product and version from the drop-down options

Product Red Hat Process Automation Manager

Version 70

2 Download one of the following product distributions

To use the installer to install Red Hat Process Automation Manager on Red Hat JBoss EAP71 download Red Hat Process Automation Manager 700 Installer (rhpam-installer-700jar) The installer graphical user interface guides you through theinstallation process

To install Red Hat Process Automation Manager on Red Hat JBoss EAP 71 using thedeployable zip files download the following files

Red Hat Process Automation Manager 700 Process Server for All Supported EE7Containers (rhpam-700-kie-server-ee7zip)

Red Hat Process Automation Manager 700 Business Central Deployable for EAP 7(rhpam-700-business-central-eap7-deployablezip)

The ZIP files do not require a graphical user interface so you can install Red Hat ProcessAutomation Manager using SSH

To run Business Central without needing to deploy it to an application server downloadRed Hat Process Automation Manager 700 Decision Central Standalone (rhpam-700-business-central-standalonejar)

CHAPTER 4 USING THE RED HAT PROCESS AUTOMATIONMANAGER INSTALLER

This section describes how to install Process Server and the headless Process Automation Managercontroller using the installer JAR file The JAR file is an executable file that installs Red Hat ProcessAutomation Manager in an existing Red Hat JBoss EAP 71 server installation You can run the installerin interactive or command line interface (CLI) mode

The Red Hat Process Automation Manager JAR file installer does not support the RedHat JBoss EAP distribution installed by yum or RPM Package Manager If you want toinstall Red Hat Process Automation Manager in this type of Red Hat JBoss EAPinstallation download the Red Hat Process Automation Manager 70 Deployable forRed Hat JBoss EAP 71 file and follow the steps in Chapter 5 Installing Red Hat ProcessAutomation Manager from ZIP files

Because IBM JDK cannot use keystores generated on other JDKs you cannot installRed Hat Process Automation Manager into an existing Red Hat JBoss EAP installationrunning on IBM JDK with a keystore generated on another JDK

Next steps

Follow the instructions in one of the following sections

Section 41 ldquoUsing the installer in interactive moderdquo

Section 42 ldquoUsing the installer in CLI moderdquo

Section 43 ldquoUsing the installer to configure Process Server with the Process AutomationManager controllerrdquo

41 USING THE INSTALLER IN INTERACTIVE MODE

The installer for Red Hat Process Automation Manager is an executable JAR file You can use it toinstall Red Hat Process Automation Manager in an existing Red Hat JBoss EAP 71 server installation

For security reasons you should run the installer as a non-root user

Prerequisites

A backed-up Red Hat JBoss EAP 71 or higher server installation is available

Sufficient user permissions to complete the installation are granted

The JAR binary is included in $PATH environment variable On Red Hat Enterprise Linux it isincluded in the java-$JAVA_VERSION-openjdk-devel package

CHAPTER 4 USING THE RED HAT PROCESS AUTOMATION MANAGER INSTALLER

Red Hat Process Automation Manager is designed to work with UTF-8 encodingIf a different encoding system is used by the underlying JVM unexpected errorsmight occur To ensure UTF-8 is used by the JVM use the -Dfileencoding=UTF-8 system property

Procedure

1 In a terminal window navigate to the directory where you downloaded the installer JAR file andenter the following command

java -jar rhpam-installer-700jar

When running the installer on Windows you may be prompted to provideadministrator credentials during the installation To prevent this requirementadd the izpackmode=privileged option to the installation command

java -Dizpackmode=privileged -jarrhpam-installer-700jar

Furthermore when running the installer on a 32-bit Java virtual machine youmight encounter memory limitations To prevent this issue run this command

java -XXMaxHeapSize=4g -jarrhpam-installer-700jar

The graphical installer displays a splash screen and a license agreement page

2 Click I accept the terms of this license agreement and click Next

3 Specify the Red Hat JBoss EAP 71 server home where you want to install Red Hat ProcessAutomation Manager and click Next

4 Select the components that you want to install and click Next

You can install Business Central and Process Server on the same serverHowever you should install Business Central and Process Server on differentservers in production environments To do this run the installer twice

5 Create a user and click Next By default the new user is given the admin kie-server and rest-all roles To select another role deselect admin For more information see Chapter 2Roles and users

Make sure that the specified user name is not the same as an existing user roleor 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 onenumber and one non-alphanumeric character but not amp (ampersand)

Make a note of the user name and password You will need them to access Business Centraland Process Server

6 On the Installation Overview page click Next to start the installation The InstallationOverview page lists the components that you will install

7 When the installation has completed click Next

8 On the Configure Runtime Environment page choose whether to perform the defaultinstallation or perform an advanced configurationIf you choose Perform advanced configuration you can choose to configure databasesettings or customize certain Process Server options

9 If you selected Customize database settings on the JDBC Drive Configuration page specifya data source JDBC driver vendor select one or more Driver JAR files and click NextA data source is an object that enables a Java Database Connectivity (JDBC) client such as anapplication server to establish a connection with a database Applications look up the datasource on the Java Naming and Directory Interface (JNDI) tree or in the local applicationcontext and request a database connection to retrieve data You must configure data sourcesfor Process Server to ensure proper data exchange between the servers and the designateddatabase

10 If you selected Customize Process Server settings change any of the following if desired

Change the name of the Process Server property

Change the URL of the controller

Deselect any Process Server server options

11 Click Next to configure the runtime environment

12 When Processing finished appears at the top of the screen click Next to complete theinstallation

13 If desired click Generate Installation Script and Properties File to save the installation datain an XML file then click Done You can use this file to automatically install Red Hat ProcessAutomation Manager on the same type of server Note that you must change the installpath parameter in the XML file to specify the path of the new server that you want toinstall Red Hat Process Automation Manager on Enter the following command to perform aninstallation with the XML file

java -jar rhpam-installer-700jar ltpath-to-filegt

You have successfully installed Red Hat Process Automation Manager using the installer If youinstalled only Business Central repeat these steps to install Process Server on a separate server

42 USING THE INSTALLER IN CLI MODE

You can run the Red Hat Process Automation Manager installer through the command-line interface(CLI)

Prerequisites

The JAR binary is included in the $PATH environment variable On Red Hat Enterprise Linux itis included in the java-$JAVA_VERSION-openjdk-devel package

Procedure

1 In a terminal window navigate to the directory where you downloaded the installer file andenter the following command

java -jar rhpam-installer-700jar -console

The command-line interactive process will start and display the End-User License Agreement

press 1 to continue 2 to quit 3 to redisplay

2 Read the license agreement enter 1 and press Enter to continue

Specify the home directory of one of the following servers Red Hat JBoss EAP 71 or Red Hat JBoss Web Server 50

3 Enter the parent directory of an existing Red Hat JBoss EAP 71 installationThe installer will verify the location of the installation at the location provided Enter 1 toconfirm and continue

You can install Business Central and Process Server on the same serverHowever you should install Business Central and Process Server on differentservers in production environments

4 Follow the instructions in the installer to complete the installation

When you create the user name and password make sure that the specified username does not conflict with any known title of a role or a group For example ifthere is a role called admin you should not create a user with the user name admin

The password must have at least eight characters and must contain at least onenumber and one non-alphanumeric character (not including the character amp)

Make a note of the user name and password You will need them to accessBusiness Central and Process Server

5 When the installation has completed you will see this message

Would you like to generate an automatic installation script and properties file

6 Enter y to create an XML file that contains the installation data or n to complete theinstallation If you enter y you are prompted to specify a path for the XML file

7 Enter a path or press the Enter key to accept the suggested path

8 If you installed only Business Central repeat these steps to install Process Server on aseparate server

43 USING THE INSTALLER TO CONFIGURE PROCESS SERVER WITHTHE PROCESS AUTOMATION MANAGER CONTROLLER

Process Server can be managed by the Process Automation Manager controller or it can beunmanaged If Process Server is unmanaged you must manually create and maintain containers IfProcess Server is managed the Process Automation Manager controller manages the Process Serverconfiguration and you interact with the controller to create and maintain containers

The Process Automation Manager controller is integrated with Business Central If you install BusinessCentral you can use the Execution Server page in Business Central to interact with the controller

You can use the installer in interactive or CLI mode to install Business Central and Process Server andthen configure Process Server with the Process Automation Manager controller

If you do not install Business Central see Chapter 7 Installing and running the headlessProcess Automation Manager controller for information about using the headless ProcessAutomation Manager controller

Prerequisites

Two computers with backed-up Red Hat JBoss EAP 71 or higher server installations areavailable

Procedure

1 On the first computer run the installer in interactive mode or CLI mode See one of thefollowing sections for more information

2 On the Component Selection page clear the Process Server box

3 Complete the Business Central installation

4 On the second computer run the installer in interactive mode or CLI mode

5 On the Component Selection page clear the Business Central box

6 On the Configure Runtime Environment page select Perform Advanced Configuration

7 Select Customize Process Server properties and click Next

8 On the Process Server Properties Configuration page click New Server Configuration to adda Process Server and specify a unique name for that Process Server This name will appear inBusiness Central and enable you to distinguish between different Process Servers

CHAPTER 5 INSTALLING RED HAT PROCESS AUTOMATIONMANAGER FROM ZIP FILES

The Red Hat Process Automation Manager ZIP files (one for Business Central and one for ProcessServer) do not require a graphical user interface so you can install Red Hat Process AutomationManager using SSH

You should install Business Central and the Process Server on different servers inproduction environments

For information about installing the headless Process Automation Manager controllersee Chapter 7 Installing and running the headless Process Automation Manager controller

51 INSTALLING BUSINESS CENTRAL FROM THE ZIP FILE

Business Central is a web console that enables you to perform the following tasks over individualcomponents in a unified web-based environment

Create manage and edit your rules processes and related assets

Manage connected Process Server instances and their containers

Execute runtime operations against processes and tasks in Process Server instancesconnected to Business Central

Prerequisites

A backed-up Red Hat JBoss EAP installation version 71 or higher is available The basedirectory of the Red Hat JBoss EAP installation is referred to as EAP_HOME

The following file is downloaded from the Red Hat Customer Portal rhpam-700-business-central-eap7-deployablezip

Procedure

1 Extract the rhpam-700-business-central-eap7-deployablezip file to atemporary directory In the following examples this directory is called TEMP_DIR

2 Copy the contents of the TEMP_DIRrhpam-700-business-central-eap7-deployablejboss-eap-71 directory to EAP_HOME When prompted merge or replacefiles

CHAPTER 5 INSTALLING RED HAT PROCESS AUTOMATION MANAGER FROM ZIP FILES

WARNING

Ensure the names of the Red Hat Process Automation Managerdeployments you are copying do not conflict with your existingdeployments in the Red Hat JBoss EAP instance

52 INSTALLING PROCESS SERVER FROM THE ZIP FILE

Process Server provides the runtime environment for business assets and accesses the data stored inthe assets repository (knowledge store)

Prerequisites

The following file is downloaded from the Red Hat Customer Portal rhpam-700-kie-server-ee7zip

Procedure

1 Extract the rhpam-700-kie-server-ee7zip archive to a temporary directory In thefollowing examples this directory is called TEMP_DIR

2 Copy the TEMP_DIRrhpam-700-kie-server-ee7rhpam-700-kie-server-ee7kie-serverwar directory to EAP_HOMEstandalonedeployments

WARNING

3 Copy the contents of the TEMP_DIRrhpam-700-kie-server-ee7rhpam-700-kie-server-ee7SecurityPolicy to EAP_HOMEbin When asked to overwrite files clickReplace

4 In the EAP_HOMEstandalonedeployments directory create an empty file named kie-serverwardodeploy This file ensures that Process Server is automatically deployed whenthe server starts

53 CONFIGURING JDBC DATA SOURCES FOR PROCESS SERVER

A data source is an object that enables a Java Database Connectivity (JDBC) client such as anapplication server to establish a connection with a database Applications look up the data source onthe Java Naming and Directory Interface (JNDI) tree or in the local application context and request adatabase connection to retrieve data You must configure data sources for Process Server to ensureproper data exchange between the servers and the designated database

Prerequisite

The JDBC providers that you want to use to create database connections are configured on all serverson which you want to deploy Process Server

Procedure

1 Open EAP_HOMEstandaloneconfigurationstandalone-fullxml in a text editorand locate the ltsystem-propertiesgt tag

2 Add the following properties to the ltsystem-propertiesgt tag where ltDATASOURCEgt is thename of your data source and ltHIBERNATE_DIALECTgt is the hibernate dialect for yourdatabase

The default value of the orgkieserverpersistenceds property is javajbossdatasourcesExampleDS The default value of the orgkieserverpersistencedialect property is orghibernatedialectH2Dialect

For example

ltproperty name=orgkieserverpersistenceds value=ltDATASOURCEgtgtltproperty name=orgkieserverpersistencedialect value=ltHIBERNATE_DIALECTgtgt

ltsystem-propertiesgt ltproperty name=orgkieserverrepo value=$jbossserverdatadirgt ltproperty name=orgkieexample value=truegt ltproperty name=orgjbpmdesignerperspective value=fullgt ltproperty name=designerdataobjects value=falsegt ltproperty name=orgkieserveruser value=rhpamUsergt ltproperty name=orgkieserverpwd value=rhpam123gt ltproperty name=orgkieserverlocation value=httplocalhost8080kie-serverservicesrestservergt ltproperty name=orgkieservercontroller value=httplocalhost8080business-centralrestcontrollergt ltproperty name=orgkieservercontrolleruser value=kieservergt ltproperty name=orgkieservercontrollerpwd value=kieserver1gt ltproperty name=orgkieserverid value=local-server-123gt

lt-- Data source properties --gt ltproperty name=orgkieserverpersistenceds

The following dialects are supported

DB2 orghibernatedialectDB2Dialect

MSSQL orghibernatedialectSQLServer2012Dialect

MySQL orghibernatedialectMySQL5InnoDBDialect

MariaDB orghibernatedialectMySQL5InnoDBDialect

Oracle orghibernatedialectOracle10gDialect

PostgreSQL orghibernatedialectPostgreSQL82Dialect

PostgreSQL plus orghibernatedialectPostgresPlusDialect

Sybase orghibernatedialectSybaseASE157Dialect

54 CREATING USERS

Before you can log in to Business Central or Process Server you must create users This section showsyou how to create a Business Central user with the admin rest-all and kie-server roles and aProcess Server user that has the kie-server role For information about roles see Chapter 2 Rolesand users

Prerequisites

Red Hat Process Automation Manager is installed in the base directory of the Red Hat JBoss EAPinstallation (EAP_HOME) as described in Chapter 5 Installing Red Hat Process Automation Manager fromZIP files

Procedure

1 In a terminal application navigate to the EAP_HOMEbin directory

2 Create a user with the admin role that you will use to log in to Business Central In thefollowing command replace ltusernamegt and ltpasswordgt with the user name and passwordof your choice

value=javajbossdatasourcesKieServerDSgt ltproperty name=orgkieserverpersistencedialect value=orghibernatedialectPostgreSQLDialectgtltsystem-propertiesgt

$ add-usersh -a --user ltUSERNAMEgt --password ltPASSWORDgt --role adminrest-all

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

4 Make a note of your user names and passwords

If you installed Business Central and Process Server in the same serverinstance you can create a single user that has both of these roles

You should install Business Central and Process Server on different servers inproduction environments

55 CONFIGURING PROCESS SERVER WITH THE INTEGRATEDPROCESS AUTOMATION MANAGER CONTROLLER

Only make the changes described in this section if Process Server will be managed byBusiness Central and you installed Red Hat Process Automation Manager from the ZIPfiles If you did not install Business Central you can use the headless ProcessAutomation Manager controller to manage Process Server as described in Chapter 7Installing and running the headless Process Automation Manager controller

Process Server can be managed or it can be unmanaged If Process Server is unmanaged you mustmanually create and maintain containers If Process Server is managed the Process AutomationManager controller manages the Process Server configuration and you interact with the controller tocreate and maintain containers

If you installed Red Hat Process Automation Manager from the ZIP files you must edit the standalone-fullxml file in both the Process Server and Business Central installations toconfigure 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 JBossEAP installation (EAP_HOME)

$ add-usersh -a --user ltUSERNAMEgt --password ltPASSWORDgt --role kie-server

$ add-usersh -a --user ltUSERNAMEgt --password ltPASSWORDgt --role adminrest-allkie-server

You should install Business Central and Process Server on different servers inproduction environments However if you install Process Server and BusinessCentral on the same server for example in a development environment makethe changes described in this section in the shared standalone-fullxmlfile

On Business Central server nodes a user with the rest-all role existsFor more information see Section 54 ldquoCreating usersrdquo

Procedure

1 In the Business Central EAP_HOMEstandaloneconfigurationstandalone-fullxmlfile uncomment the following properties in the ltsystem-propertiesgt section and replace ltUSERNAMEgt and ltUSER_PWDgt with the credentials of a user with the kie-server role

2 In the Process Server EAP_HOMEstandaloneconfigurationstandalone-fullxmlfile uncomment the following properties in the ltsystem-propertiesgt section

3 Replace the following values

Replace ltCONTROLLER_USERgt and ltCONTROLLER_PWDgt with the credentials of a userwith the rest-all role

Replace ltKIE_SERVER_IDgt with the ID or name of the Process Server installation forexample rhpam700-process-server-1

Replace ltHOSTgt with the ID or name of the Process Server host for example localhostor 192789

Replace ltPORTgt with the port of the Process Server host for example 8080

The orgkieserverlocation property specifies the location ofProcess Server

Replace ltCONTROLLER_URLgt with the URL of Business Central Process Server connectsto this URL during startup

ltproperty name=orgkieserveruser value=ltUSERNAMEgtgt ltproperty name=orgkieserverpwd value=ltUSER_PWDgtgt

ltproperty name=orgkieservercontrolleruser value=ltCONTROLLER_USERgtgt ltproperty name=orgkieservercontrollerpwd value=ltCONTROLLER_PWDgtgt ltproperty name=orgkieserverid value=ltKIE_SERVER_IDgtgt ltproperty name=orgkieserverlocation value=httpltHOSTgtltPORTgtkie-serverservicesrestservergt ltproperty name=orgkieservercontroller value=ltCONTROLLER_URLgtgt

If you installed Business Central using the installer or Red Hat JBoss EAP zipinstallations ltCONTROLLER_URLgt has this formathttpltHOSTgtltPORTgtbusiness-centralrestcontroller

If you are running Business Central using the standalonejar file ltCONTROLLER_URLgt has this formathttpltHOSTgtltPORTgtrestcontroller

CHAPTER 6 RUNNING RED HAT PROCESS AUTOMATIONMANAGER

Use this procedure to run the Red Hat Process Automation Manager on Red Hat JBoss EAP instandalone mode

Prerequisite

Red Hat Process Automation Manager is installed and configured

Procedure

1 In a terminal application navigate to EAP_HOMEbin

2 Run the standalone configuration

On Linux or UNIX-based systems

On Windows

If you deployed Business Central without Process Server you can startBusiness Central with the standalonesh script without specifying the standalone-fullxml file In this case ensure that you make anyconfiguration changes to the standalonexml file before startingBusiness Central

$ standalonesh

On Windows

3 In a web browser open the URL localhost8080business-central

4 Log in using the credentials of the user that you created for Business Central in Section 54ldquoCreating usersrdquo

$ standalonesh -c standalone-fullxml

standalonebat -c standalone-fullxml

standalonebat

CHAPTER 7 INSTALLING AND RUNNING THE HEADLESSPROCESS AUTOMATION MANAGER CONTROLLER

You can configure Process Server to run in managed or unmanaged mode If Process Server isunmanaged you must manually create and maintain containers If Process Server is managed theProcess Automation Manager controller manages the Process Server configuration and you interactwith the controller to create and maintain containers

The Process Automation Manager controller is integrated with Business Central If you install BusinessCentral use the Execution Server page to create and maintain containers However if you do notinstall Business Central you can install the headless Process Automation Manager controller and usethe REST API or the Process Server Java Client API to interact with it

71 INSTALLING THE HEADLESS PROCESS AUTOMATION MANAGERCONTROLLER

You can install the headless Process Automation Manager controller and use the REST API or theProcess Server Java Client API to interact with it

Prerequisites

Procedure

Version 70

2 Download Red Hat Process Automation Manager 700 Add Ons (the rhpam-700-add-onszip file)

3 Unzip the rhpam-700-add-onszip file The rhpam-70-controller-ee7zip file isin the unzipped directory

4 Extract the rhpam-70-controller-ee7 archive to a temporary directory In the followingexamples this directory is called TEMP_DIR

5 Copy the TEMP_DIRrhpam-70-controller-ee7controllerwar directory to EAP_HOMEstandalonedeployments

WARNING

Ensure that the names of the headless Process Automation Managercontroller deployments you are copying do not conflict with your existingdeployments in the Red Hat JBoss EAP instance

6 Copy the contents of the TEMP_DIRrhpam-70-controller-ee7SecurityPolicydirectory to EAP_HOMEbin When asked to overwrite files select Yes

7 In the EAP_HOMEstandalonedeployments directory create an empty file named controllerwardodeploy This file ensures that the headless Process AutomationManager controller is automatically deployed when the server starts

711 Creating a controller user

Before you can use the headless Process Automation Manager controller you must create a user thathas the kie-server role

Prerequisite

The controller is installed in the base directory of the Red Hat JBoss EAP installation (EAP_HOME)

Procedure

2 Enter the following command and replace ltUSER_NAMEgt and ltPASSWORDgt with the user nameand password of your choice

3 Make a note of your user name and password

712 Configuring Process Server and the headless Process Automation Managercontroller

If Process Server will be managed by the headless Process Automation Manager controller you mustedit the standalone-fullxml file in both the Process Server and headless Process AutomationManager controller installations as described in this section

$ add-usersh -a --user ltUSER_NAMEgt --password ltPASSWORDgt --role kie-server

Prerequisites

Process Server is installed in the base directory of the Red Hat JBoss EAP installation(EAP_HOME) as described in Chapter 5 Installing Red Hat Process Automation Manager from ZIPfiles section

The controller is installed in an EAP_HOME

You should install Process Server and the headless Process AutomationManager controller on different servers in production environments However ifyou install Process Server and the headless Process Automation Managercontroller on the same server for example in a development environment makethese changes in the shared standalone-fullxml file

On Process Server nodes a user with the kie-server role exists

On the controller server nodes a user with the kie-server role existsFor more information see Section 54 ldquoCreating usersrdquo

Procedure

1 In the controller EAP_HOMEstandaloneconfigurationstandalone-fullxml fileadd the following properties to the ltsystem-propertiesgt section and replace ltUSERNAMEgtand ltUSER_PWDgt with the credentials of a user with the kie-server role

2 In the Process Server EAP_HOMEstandaloneconfigurationstandalone-fullxmlfile add the following properties to the ltsystem-propertiesgt section

3 In this file replace the following values

Replace ltCONTROLLER_USERgt and ltCONTROLLER_PWDgt with the credentials of a userwith the kie-server role

Replace ltKIE_SERVER_IDgt with the ID or name of the Process Server installation forexample rhpam-700-process_server-1

Replace ltCONTROLLER_URLgt with the URL of the headless Process Automation Managercontroller

4 Process Server connects to this URL during startup

72 RUNNING THE HEADLESS PROCESS AUTOMATION MANAGERCONTROLLER

After you have installed the headless Process Automation Manager controller on Red Hat JBoss EAPuse this procedure to run the headless Process Automation Manager controller

Prerequisite

The headless Process Automation Manager controller is installed and configured in the base directoryof the Red Hat JBoss EAP installation (EAP_HOME)

Procedure

2 Enter the following command

On Windows

3 To verify that the controller is working on Red Hat JBoss EAP enter the following commandwhere ltCONTROLLERgt and ltCONTROLLER_PWDgt is the user name and password combinationthat you created in Section 711 ldquoCreating a controller userrdquo The output of this commandprovides information about the Process Server instance

curl -X GET httpltHOSTgtltPORTgtcontrollerrestcontrollermanagementservers -H accept applicationxml -u ltCONTROLLERgtltCONTROLLER_PWDgt

Alternatively you can use the Process Server Java API Client to access the headlessProcess Automation Manager controller

$ standalonesh

standalonebat

CHAPTER 8 RUNNING STANDALONE BUSINESS CENTRALYou can use the Business Central standalone JAR file to run Business Central without needing todeploy it to an application server such as Red Hat JBoss EAP

Red Hat supports this installation type only when it is installed on Red Hat EnterpriseLinux

Procedure

Version 70

2 Download Red Hat Process Automation Manager 70 Business Central Standalone (rhpam-700-business-central-standalonejar)

3 Create a directory and move the rhpam-700-business-central-standalonejar fileto this directory

4 In a terminal window navigate to the directory that contains the standalone JAR file

5 Create the application-usersproperties file Include an administrative user and if thisBusiness Central instance will be a controller for Process Server include a controller user forexample

rhpamAdmin=password1controllerUser=controllerUser1234

6 Create the application-rolesproperties file to assign roles to the users that youincluded in the application-usersproperties file for example

rhpamAdmin=admincontrollerUser=kie-server

7 Create the application-configyaml configuration file with the following contents whereltAPPLICATION_USERSgt is the path to the application-usersproperties file and ltAPPLICATION_ROLESgt is the path to the application-rolesproperties file

swarm security security-domains other classic-authentication login-modules myloginmodule code orgkiesecurityjaasKieLoginModule flag optional module deploymentkie-wb-webappwar

CHAPTER 8 RUNNING STANDALONE BUSINESS CENTRAL

management security-realms ApplicationRealm local-authentication default-user local allowed-users local skip-group-loading true properties-authentication path ltAPPLICATION_USERSgt plain-text true properties-authorization path ltAPPLICATION_ROLESgtdatasource management wildfly admin admin

java -jar rhpam-700-business-central-standalonejar -s application-configyaml

In addition you can set any properties supported by Business Central by including the -Dltpropertygt=ltvaluegt parameter in this command for example

java -jar rhpam-700-business-central-standalonejar -s application-configyaml -Dltpropertygt=ltvaluegt -Dltpropertygt=ltvaluegt

See Section 81 ldquoSupported propertiesrdquo for more information

81 SUPPORTED PROPERTIES

When you install standalone Business Central you can use the properties listed in this section in thefollowing command

In this command ltpropertygt is a property from the following list and ltvaluegt is a value that youassign to that property

orguberfireniogitdir Location of the Process Server Git directory

orguberfireniogitdirname Name of the Process Server Git directory Default valueniogit

orguberfireniogitdaemonenabled Enables or disables the Git daemon Defaultvalue true

orguberfireniogitdaemonhost If the Git daemon is enabled it uses this propertyas the local host identifier Default value localhost

orguberfireniogitdaemonport If the Git daemon is enabled it uses this propertyas the port number Default value 9418

orguberfireniogitsshenabled Enables or disables the SSH daemon Default valuetrue

orguberfireniogitsshhost If the SSH daemon enabled it uses this property as thelocal host identifier Default value localhost

orguberfireniogitSSHport If the SSH daemon is enabled it uses this property asthe port number Default value 8001

orguberfireniogitsshcertdir Location of the security directory where localcertificates are stored Default the working directory

orguberfireniogitsshpassphrase Pass phrase used to access the public keystore of your operating system when cloning git repositories with SCP style URLs Example gitgithubcomuserrepositorygit

orguberfireniogitsshalgorithm Algorithm used by SSH Default value DSA

If you plan to use RSA or any algorithm other than DSA make sure you set upyour application server to use the Bouncy Castle JCE library

orguberfiremetadataindexdir Place where the Lucene index directory is storedDefault the working directory

orguberfireldapregexrole_mapper Regex pattern used to map LDAP principalnames to the application role name Note that the variable role must be part of the patternbecause it is substituted by the application role name when matching a principal value to a rolename Default Not used

orguberfiresysrepomonitordisabled Disables the configuration monitor Do notdisable unless you are sure Default value false

orguberfiresecurekey Password used by password encryption Default value orguberfireadmin

orguberfiresecurealg Crypto algorithm used by password encryption Default value PBEWithMD5AndDES

orguberfiredomain Security-domain name used by uberfire Default value ApplicationRealm

orgguvnorm2repodir Place where the Maven repository folder is stored Default value ltworking-directorygtrepositorieskie

orgguvnorprojectgavcheckdisabled Disables group ID artifact ID and version(GAV) checks Default value false

orgkieexample Enables external cloning of a demo application from GitHub

orgkiebuilddisable-project-explorer Disables automatic build of a selectedproject in Project Explorer Default value false

orgkieverificationdisable-dtable-realtime-verification Disables the real-

time validation and verification of decision tables Default value false

orgkieservercontroller URL for connecting with a Kie Server controller forexample wslocalhost8080business-centralwebsocketcontroller

orgkieserveruser User name used to connect with the Process Server nodes from thecontroller This property is only required when using this Business Central installation as acontroller

orgkieserverpwd Password used to connect with the Process Server nodes from thecontroller This property is only required when using this Business Central installation as acontroller

CHAPTER 9 SETTING MAVEN DEPENDENCIES IN YOURPROJECT

You can use an external Maven repository to deploy a project When you create a project BusinessCentral uses the Maven repositories that are configured for Business Central You can use the Mavenglobal or user settings to direct all Red Hat Process Automation Manager projects to retrievedependencies from the public Red Hat Process Automation Manager repository by modifying thefollowing files

The Maven settingsxml file

The Maven project object model (POM) file (pomxml)

For more information see Packaging and deploying a project

91 MODIFY THE MAVEN SETTINGS FILE

You can configure Business Central and Process Server to use an external Maven repository such asNexus instead of the built-in repository In this case when you build projects in Business Central allbuilt project KJAR files are pushed into this external repository You can progress these files throughthe repository as necessary to implement your integration process and deploy the KJAR files usingBusiness Central or the Process Server REST API

Prerequisite

Business Central and Process Server are installed For installation options see Planning a Red HatProcess Automation Manager installation

Procedure

1 Create a Maven settingsxml file with connection and access details for your externalrepository For details about the settingsxml file see the Maven Settings Reference

2 Save the file in a known location for example optcustom-configsettingsxml

3 In your Red Hat Process Automation Manager installation directory navigate to the standalone-fullxml file For example if you use a Red Hat JBoss EAP installation for RedHat Process Automation Manager go to $EAP_HOMEstandaloneconfigurationstandalone-fullxml

4 Open standalone-fullxml and under the ltsystem-propertiesgt tag set the kiemavensettingscustom property to the full path name of the settingsxml fileFor example

5 Start or restart Business Central and Process Server

92 MODIFY THE MAVEN POM FILE

To use the correct Maven dependencies in your Red Hat Process Automation Manager project youmust add relevant bill of materials (BOM) files to the projectrsquos pomxml file When you add the BOM

ltproperty name=kiemavensettingscustom value=optcustom-configsettingsxmlgt

CHAPTER 9 SETTING MAVEN DEPENDENCIES IN YOUR PROJECT

files the correct versions of transitive dependencies from the provided Maven repositories areincluded in the project

For more information see What is the mapping between RHPAM product and maven library version

Procedure

1 Declare the BOM in the pomxml file For example

2 Declare dependencies required for your project in the ltdependenciesgt tag After you importthe product BOM into your project the versions of the user-facing product dependencies aredefined so you do not need to specify the ltversiongt sub-element of these ltdependencygtelements However you must use the ltdependencygt element to declare dependencies whichyou want to use in your project

3 For standalone projects that are not authored in Business Central specify all dependenciesrequired for your projects In projects that you author in Business Central the basic Drools andjBPM engine dependencies are provided automatically by Business Central

For a basic Red Hat Process Automation Manager project declare the followingdependencies depending on the features that you want to use

Embedded jBPM engine dependencies

ltdependencyManagementgt ltdependenciesgt ltdependencygt ltgroupIdgtorgjbossbomltgroupIdgt ltartifactIdgtrhpam-platform-bomltartifactIdgt ltversiongt700-redhat-3ltversiongt lttypegtpomlttypegt ltscopegtimportltscopegt ltdependencygt ltdependenciesgtltdependencyManagementgtltdependenciesgtlt-- Your dependencies --gtltdependenciesgt

lt-- Public KIE API --gtltdependencygt ltgroupIdgtorgkieltgroupIdgt ltartifactIdgtkie-apiltartifactIdgtltdependencygt

lt-- jBPM engine core dependencies --gtltdependencygt ltgroupIdgtorgjbpmltgroupIdgt ltartifactIdgtjbpm-flowltartifactIdgtltdependencygt

ltdependencygt ltartifactIdgtjbpm-flow-builderltartifactIdgtltdependencygt

For a Red Hat Process Automation Manager project that uses CDI you typically declarethe following dependencies

CDI-enabled jBPM engine dependencies

ltdependencygt ltgroupIdgtorgjbpmltgroupIdgt ltartifactIdgtjbpm-bpmn2ltartifactIdgtltdependencygt

ltdependencygt ltgroupIdgtorgjbpmltgroupIdgt ltartifactIdgtjbpm-runtime-managerltartifactIdgtltdependencygt

ltdependencygt ltgroupIdgtorgjbpmltgroupIdgt ltartifactIdgtjbpm-persistence-jpaltartifactIdgtltdependencygt

ltdependencygt ltgroupIdgtorgjbpmltgroupIdgt ltartifactIdgtjbpm-query-jpaltartifactIdgtltdependencygt

ltdependencygt ltgroupIdgtorgjbpmltgroupIdgt ltartifactIdgtjbpm-auditltartifactIdgtltdependencygt

ltdependencygt ltgroupIdgtorgjbpmltgroupIdgt ltartifactIdgtjbpm-kie-servicesltartifactIdgtltdependencygt

lt-- Dependency needed for default WorkItemHandler implementations --gtltdependencygt ltgroupIdgtorgjbpmltgroupIdgt ltartifactIdgtjbpm-workitems-coreltartifactIdgtltdependencygt

lt-- Logging dependency You can use any logging framework compatible with slf4j --gtltdependencygt ltgroupIdgtchqoslogbackltgroupIdgt ltartifactIdgtlogback-classicltartifactIdgt ltversiongt$logbackversionltversiongtltdependencygt

ltdependencygt ltgroupIdgtorgkieltgroupIdgt ltartifactIdgtkie-apiltartifactIdgtltdependencygt

ltdependencygt

For a basic Red Hat Process Automation Manager project declare the followingdependencies

Embedded Drools engine dependencies

To use the Process Server declare the following dependencies

Client application Process Server dependencies

ltgroupIdgtorgjbpmltgroupIdgt ltartifactIdgtjbpm-kie-servicesltartifactIdgtltdependencygt

ltdependencygt ltgroupIdgtorgjbpmltgroupIdgt ltartifactIdgtjbpm-services-cdiltartifactIdgtltdependencygt

ltdependencygt ltgroupIdgtorgdroolsltgroupIdgt ltartifactIdgtdrools-compilerltartifactIdgtltdependencygt

lt-- Dependency for persistence support --gtltdependencygt ltgroupIdgtorgdroolsltgroupIdgt ltartifactIdgtdrools-persistence-jpaltartifactIdgtltdependencygt

lt-- Dependencies for decision tables templates and scorecardsFor other assets declare orgdroolsdrools-workbench-models- dependencies --gtltdependencygt ltgroupIdgtorgdroolsltgroupIdgt ltartifactIdgtdrools-decisiontablesltartifactIdgtltdependencygtltdependencygt ltgroupIdgtorgdroolsltgroupIdgt ltartifactIdgtdrools-templatesltartifactIdgtltdependencygtltdependencygt ltgroupIdgtorgdroolsltgroupIdgt ltartifactIdgtdrools-scorecardsltartifactIdgtltdependencygt

lt-- Dependency for loading KJARs from a Maven repository using KieScanner --gtltdependencygt ltgroupIdgtorgkieltgroupIdgt ltartifactIdgtkie-ciltartifactIdgtltdependencygt

ltdependencygt ltgroupIdgtorgkieserverltgroupIdgt ltartifactIdgtkie-server-clientltartifactIdgt

To create a remote client for Red Hat Process Automation Manager declare the followingdependency

Client dependency

When creating a JAR file that includes assets such as rules and process definitionsspecify the packaging type for your Maven project as kjar and use orgkiekie-maven-plugin to process the kjar packaging type located under the ltprojectgtelement In the following example $kieversion is the Maven library version listed inWhat is the mapping between RHPAM product and maven library version

ltdependencygt

ltdependencygt ltgroupIdgtorguberfireltgroupIdgt ltartifactIdgtuberfire-rest-clientltartifactIdgtltdependencygt

ltpackaginggtkjarltpackaginggtltbuildgt ltpluginsgt ltplugingt ltgroupIdgtorgkieltgroupIdgt ltartifactIdgtkie-maven-pluginltartifactIdgt ltversiongt$kieversionltversiongt ltextensionsgttrueltextensionsgt ltplugingt ltpluginsgtltbuildgt

CHAPTER 10 IMPORTING PROJECTS FROM GITREPOSITORIES

Git is a distributed version control system It implements revisions as commit objects When you saveyour changes to a repository a new commit object in the Git repository is created

Business Central uses Git to store project data including assets such as rules and processes When youcreate a project in Business Central it is added to a Git repository that is connected to BusinessCentral If you have projects in Git repositories you can import those projects into the Business CentralGit repository through Business Central spaces

Prerequisites

Red Hat Process Automation Manager projects exist in an external Git repository

Credentials required for read access to that external Git repository are available

Procedure

1 In Business Central click Menu rarr Design rarr Projects

2 Select or create the space into which you want to import the projects The default space ismySpace

3 Click the three vertical dots on the right side of the screen and select Import Project

4 In the Import Project window enter the URL and credentials for the Git repository thatcontains the projects that you want to import and click Import The projects are added to theBusiness Central Git repository and are available from the current space

CHAPTER 11 VERIFYING THE RED HAT PROCESSAUTOMATION MANAGER INSTALLATION

After you have installed Red Hat Process Automation Manager create an asset to verify that theinstallation is working

Procedure

1 In a terminal window navigate to the EAP_HOMEbin directory and enter the followingcommand to start Red Hat Process Automation Manager

standalonesh -c standalone-fullxml

If you deployed Business Central without Process Server you can start BusinessCentral with the standalonesh script without specifying the standalone-fullxml file In this case ensure that you make any configuration changes tothe standalonexml file before starting Business Central

2 In a web browser enter localhost8080business-central

If Red Hat Process Automation Manager has been configured to run from a domain namereplace localhost with the domain name for examplehttpwwwexamplecom8080business-central

If Red Hat Process Automation Manager has been configured to run in a cluster replace localhost with the IP address of a particular node for examplehttpltnode_IP_addressgt8080business-central

3 Enter the admin user credentials that you created during installation The Business Centralhome page appears

4 Select Menu rarr Design rarr Projects

5 Click Try Samples rarr Mortgages rarr OK The Assets window appears

6 Click Create New Asset rarr Data Object

7 Enter MyDataObject in the Data Object field and click OK

8 Click Spaces rarr myteam rarr Mortgages and confirm that MyDataObject is in the list of assets

9 Delete MyDataObject

CHAPTER 12 CUSTOMIZING BUSINESS CENTRALYou can customize the Business Central login page and application header

121 CUSTOMIZING THE BUSINESS CENTRAL LOGIN PAGE

You can customize the company logo and the project logo on the Business Central login page

Procedure

1 Start Red Hat JBoss EAP and open Business Central in a web browser

2 Copy a PNG format image to the EAP_HOMEstandalonedeploymentsbusiness-centralwarimg directory in your Red Hat Process Automation Manager installation

3 In the EAP_HOMEstandalonedeploymentsbusiness-centralwarimg directoryeither move or rename the existing login-screen-logopng file

4 Rename your PNG file login-screen-logopng

5 To change the project logo that appears above the User name and Password fields replacethe default image RHPAM_Logosvg with a new SVG file

6 Force a full reload of the login page bypassing the cache to view the changes For example inmost Linux and Windows web browsers press Ctrl+F5

122 CUSTOMIZING BUSINESS CENTRAL APPLICATION HEADER

You can customize the Business Central application header

Procedure

1 Start Red Hat JBoss EAP open Business Central in a web browser and log in with your usercredentials

2 Copy your new application header image in the SVG format to the EAP_HOMEstandalonedeploymentsbusiness-centralwarbanner directory inyour Red Hat Process Automation Manager installation

3 Open the EAP_HOMEstandalonedeploymentsbusiness-centralwarbannerbannerhtml file in a text editor

4 Replace logosvg in the ltimggt tag with the file name of your new image

ltimg src=bannerlogosvggt

CHAPTER 13 INTEGRATING LDAP AND SSLWith Red Hat Process Automation Manager you can integrate LDAP and SSL through RH-SSO Formore information see the Red Hat Single Sign-On Server Administration Guide

CHAPTER 14 RELATED INFORMATIONIntegrating Red Hat JBoss Developer Studio with Red Hat Process Automation Manager

CHAPTER 15 NEXT STEPSGetting started with business processes

APPENDIX A VERSIONING INFORMATIONDocumentation last updated on Thursday August 23 2018

Table of Contents

PREFACE



43 USING THE INSTALLER TO CONFIGURE PROCESS SERVER WITH THE PROCESS AUTOMATION MANAGER CONTROLLER





54 CREATING USERS

55 CONFIGURING PROCESS SERVER WITH THE INTEGRATED PROCESS AUTOMATION MANAGER CONTROLLER



71 INSTALLING THE HEADLESS PROCESS AUTOMATION MANAGER CONTROLLER


712 Configuring Process Server and the headless Process Automation Manager controller









CHAPTER 12 CUSTOMIZING BUSINESS CENTRAL







Red Hat Process Automation Manager 70 Installing and configuring Red

Hat Process Automation Manager on Red Hat JBoss EAP 71

Red Hat Customer Content Servicesbrms-docsredhatcom

Legal Notice

Abstract

Table of Contents

PREFACE

1313141416

2121222224

292929

363636

Table of Contents

Prerequisite

PREFACE

Procedure

Version 70

Next steps

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

WARNING

Prerequisites

Procedure

WARNING

Prerequisite

Procedure

For example

54 CREATING USERS

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Legal Notice

Abstract

Table of Contents

PREFACE

1313141416

2121222224

292929

363636

Table of Contents

Prerequisite

PREFACE

Procedure

Version 70

Next steps

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

WARNING

Prerequisites

Procedure

WARNING

Prerequisite

Procedure

For example

54 CREATING USERS

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Table of Contents

PREFACE

1313141416

2121222224

292929

363636

Table of Contents

Prerequisite

PREFACE

Procedure

Version 70

Next steps

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

WARNING

Prerequisites

Procedure

WARNING

Prerequisite

Procedure

For example

54 CREATING USERS

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisite

PREFACE

Procedure

Version 70

Next steps

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

WARNING

Prerequisites

Procedure

WARNING

Prerequisite

Procedure

For example

54 CREATING USERS

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisite

PREFACE

Procedure

Version 70

Next steps

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

WARNING

Prerequisites

Procedure

WARNING

Prerequisite

Procedure

For example

54 CREATING USERS

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Procedure

Version 70

Next steps

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

WARNING

Prerequisites

Procedure

WARNING

Prerequisite

Procedure

For example

54 CREATING USERS

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Procedure

Version 70

Next steps

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

WARNING

Prerequisites

Procedure

WARNING

Prerequisite

Procedure

For example

54 CREATING USERS

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Procedure

Version 70

Next steps

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

WARNING

Prerequisites

Procedure

WARNING

Prerequisite

Procedure

For example

54 CREATING USERS

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Next steps

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

WARNING

Prerequisites

Procedure

WARNING

Prerequisite

Procedure

For example

54 CREATING USERS

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Procedure

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

WARNING

Prerequisites

Procedure

WARNING

Prerequisite

Procedure

For example

54 CREATING USERS

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

WARNING

Prerequisites

Procedure

WARNING

Prerequisite

Procedure

For example

54 CREATING USERS

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisites

Procedure

Prerequisites

Procedure

Prerequisites

Procedure

WARNING

Prerequisites

Procedure

WARNING

Prerequisite

Procedure

For example

54 CREATING USERS

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisites

Procedure

Prerequisites

Procedure

WARNING

Prerequisites

Procedure

WARNING

Prerequisite

Procedure

For example

54 CREATING USERS

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisites

Procedure

WARNING

Prerequisites

Procedure

WARNING

Prerequisite

Procedure

For example

54 CREATING USERS

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisites

Procedure

WARNING

Prerequisites

Procedure

WARNING

Prerequisite

Procedure

For example

54 CREATING USERS

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















WARNING

Prerequisites

Procedure

WARNING

Prerequisite

Procedure

For example

54 CREATING USERS

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisite

Procedure

For example

54 CREATING USERS

Prerequisites

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisites

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisite

Procedure

On Windows

$ standalonesh

On Windows

standalonebat

Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisites

Procedure

Version 70

WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















WARNING

Prerequisite

Procedure

Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisites

Procedure

Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisite

Procedure

On Windows

$ standalonesh

standalonebat

Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Procedure

Version 70

Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisite

Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Procedure

ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















ltdependencygt

Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Client dependency

ltdependencygt

Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Prerequisites

Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Procedure

Table of Contents

PREFACE








54 CREATING USERS






















Table of Contents

PREFACE








54 CREATING USERS






















Table of Contents

PREFACE








54 CREATING USERS






















Table of Contents

PREFACE








54 CREATING USERS






















Table of Contents

PREFACE








54 CREATING USERS






















Documents

Red Hat Process Automation Manager 7.0 Installing …...Installing and configuring Process Server on IBM WebSphere Application Server Installing and configuring Process Server on Oracle