Chapter 13. Using the Red Hat Process Automation Manager installer This section describes how to install Business Central and KIE Server using the installer JAR file. The JAR file is an executable file that installs Red Hat Process Automation Manager in an existing Red Hat JBoss EAP 7.4 server installation. You can run the installer in interactive or command line interface (CLI) mode. Note The Red Hat Process Automation Manager JAR file installer does not support the Red Hat JBoss EAP distribution installed by yum or RPM Package Manager. If you want to install Red Hat Process Automation Manager in this type of Red Hat JBoss EAP installation, download the Red Hat Process Automation Manager 7.13 Deployable for Red Hat JBoss EAP 7.4 file and follow the steps in Chapter 14, Installing Red Hat Process Automation Manager from ZIP files . Note Because IBM JDK cannot use keystores generated on other JDKs, you cannot install Red Hat Process Automation Manager into an existing Red Hat JBoss EAP installation running on IBM JDK with a keystore generated on another JDK. steps: Follow the instructions in one of the following sections: Section 13.1, "Using the installer in interactive mode" Section 13.2, "Using the installer in CLI mode" Section 13.3, "Using the installer to configure KIE Server with the Process Automation Manager controller" 13.1. Using the installer in interactive mode The installer for Red Hat Process Automation Manager is an executable JAR file. You can use it to install Red Hat Process Automation Manager in an existing Red Hat JBoss EAP 7.4 server installation. Note For security reasons, you should run the installer as a non-root user. Prerequisites The Red Hat Process Automation Manager 7.13.5 Installer has been downloaded. For instructions, see Chapter 12, Downloading the Red Hat Process Automation Manager installation files . A supported JDK is installed. For a list of supported JDKs, see Red Hat Process Automation Manager 7 Supported Configurations . A backed-up Red Hat JBoss EAP 7.4 server installation is available. Sufficient user permissions to complete the installation are granted. The JAR binary is included in USDPATH environment variable. On Red Hat Enterprise Linux, it is included in the java-USD JAVA_VERSION -openjdk-devel package. Note Red Hat Process Automation Manager is designed to work with UTF-8 encoding. If a different encoding system is used by the underlying JVM, unexpected errors might occur. To ensure UTF-8 is used by the JVM, use the "-Dfile.encoding=UTF-8" system property. For a list of system properties, see Appendix A, Business Central system properties . Procedure In a terminal window, navigate to the directory where you downloaded the installer JAR file and enter the following command: Note When running the installer on Windows, you may be prompted to provide administrator credentials during the installation. To prevent this requirement, add the izpack.mode=privileged option to the installation command: Furthermore, when running the installer on a 32-bit Java virtual machine, you might encounter memory limitations. To prevent this issue, run this command: The graphical installer displays a splash screen and a license agreement page. Click I accept the terms of this license agreement and click . Specify the Red Hat JBoss EAP 7.4 server home where you want to install Red Hat Process Automation Manager and click . Select the components that you want to install and click . Note You can install Business Central and KIE Server on the same server. However, you should install Business Central and KIE Server on different servers in production environments. To do this, run the installer twice. Create a user and click . By default, if you install both Business Central and KIE Server in the same container the new user is given the admin , kie-server , and rest-all roles. If you install only KIE Server, the user is given the kie-server role. To select another role, deselect admin . For information about roles, see Chapter 11, Red Hat Process Automation Manager roles and users . Note Make 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). Make a note of the user name and password. You will need them to access Business Central and KIE Server. On the Installation Overview page, review the components that you will install and click to start the installation. When the installation has completed, click . If KIE Server is installed, the Configure Runtime step appears under Component Installation . On the Configure Runtime Environment page, choose to perform the default installation or perform an advanced configuration. If you choose Perform advanced configuration , you can choose to configure database settings or customize certain KIE Server options. If you selected Customize database settings , on the JDBC Drive Configuration page specify a data source JDBC driver vendor, select one or more driver JAR files, and click . 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 KIE Server to ensure correct data exchange between the servers and the designated database. If you selected Customize KIE Server properties , on the KIE Server Properties Configuration page change any of the following properties: Change the value of KIE Server ID to change the name of the KIE Server property. Change the value of Controller URL to change the URL of the headless Process Automation Manager controller. Deselect any KIE Server functions that you want to disable. Click to configure the runtime environment. When Processing finished appears at the top of the screen, click to complete the installation. Optional: Click Generate Installation Script and Properties File to save the installation data in XML files, and then click Done . The installer generates two files. The auto.xml file automates future installations and the auto.xml.variables file stores user passwords and other sensitive variables. Use the auto.xml file to repeat the Red Hat Process Automation Manager installation on multiple systems with the same type of server and the same configuration as the original installation. If necessary, update the installpath parameter in the auto.xml file. To perform an installation using the XML file, enter the following command: You have successfully installed Red Hat Process Automation Manager using the installer. If you installed only Business Central, repeat these steps to install KIE Server on a separate server. Note If you use Microsoft SQL Server, make sure you have configured applicable transaction isolation for your database. If you do not, you may experience deadlocks. The recommended configuration is to turn on ALLOW_SNAPSHOT_ISOLATION and READ_COMMITTED_SNAPSHOT by entering the following statements: 13.2. Using the installer in CLI mode You can use the command-line interface (CLI) to run the Red Hat Process Automation Manager installer. Note For security reasons, you should run the installer as a non-root user. Prerequisites The Red Hat Process Automation Manager 7.13.5 Installer has been downloaded. For instructions, see Chapter 12, Downloading the Red Hat Process Automation Manager installation files . A supported JDK is installed. For a list of supported JDKs, see Red Hat Process Automation Manager 7 Supported Configurations . A backed-up Red Hat JBoss EAP 7.4 server installation is available. Sufficient user permissions to complete the installation are granted. The JAR binary is included in the USDPATH environment variable. On Red Hat Enterprise Linux, it is included in the java-USD JAVA_VERSION -openjdk-devel package. Note Red Hat Process Automation Manager is designed to work with UTF-8 encoding. If a different encoding system is used by the underlying JVM, unexpected errors might occur. To ensure UTF-8 is used by the JVM, use the "-Dfile.encoding=UTF-8" system property. For a list of system properties, see Appendix A, Business Central system properties . Procedure In a terminal window, navigate to the directory where you downloaded the installer file and enter the following command: The command-line interactive process will start and display the End-User License Agreement. Read the license agreement, enter 1 , and press Enter to continue: Enter the parent directory of an existing Red Hat JBoss EAP 7.4 installation. The installer will verify the location of the installation at the location provided. Enter 1 to confirm and continue. Note You can install Business Central and KIE Server on the same server. However, you should install Business Central and KIE Server on different servers in production environments. Follow the instructions in the installer to complete the installation. Note When you create the user name and password, make sure that the specified user name does not conflict with any known title of a role or a group. For example, if there 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 one number and one non-alphanumeric character ( not including the character & ). Make a note of the user name and password. You will need them to access Business Central and KIE Server. When the installation has completed, you will see this message: Enter y to create XML files that contain the installation data, or n to complete the installation. If you enter y , you are prompted to specify a path for the XML files. Enter a path or press the Enter key to accept the suggested path. The installer generates two files. The auto.xml file automates future installations and the auto.xml.variables file stores user passwords and other sensitive variables. Use the auto.xml file on multiple systems to easily repeat a Red Hat Process Automation Manager installation on the same type of server with the same configuration as the original installation. If necessary, update the installpath parameter in the auto.xml file. To perform an installation using the XML file, enter the following command: If you installed only Business Central, repeat these steps to install KIE Server on a separate server. Note If you use Microsoft SQL Server, make sure you have configured applicable transaction isolation for your database. If you do not, you may experience deadlocks. The recommended configuration is to turn on ALLOW_SNAPSHOT_ISOLATION and READ_COMMITTED_SNAPSHOT by entering the following statements: 13.3. Using the installer to configure KIE Server with the Process Automation Manager controller KIE Server can be managed by the Process Automation Manager controller or it can be unmanaged. If KIE Server is unmanaged, you must manually create and maintain KIE containers (deployment units). If KIE Server is managed, the Process Automation Manager controller manages the KIE 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. You can use the installer in interactive or CLI mode to install Business Central and KIE Server, and then configure KIE Server with the Process Automation Manager controller. Prerequisites Two computers with backed-up Red Hat JBoss EAP 7.4 server installations are available. Sufficient user permissions to complete the installation are granted. Procedure On the first computer, run the installer in interactive mode or CLI mode. See one of the following sections for more information: Section 13.1, "Using the installer in interactive mode" Section 13.2, "Using the installer in CLI mode" On the Component Selection page, clear the KIE Server box. Complete the Business Central installation. On the second computer, run the installer in interactive mode or CLI mode. On the Component Selection page, clear the Business Central box. On the Configure Runtime Environment page, select Perform Advanced Configuration . Select Customize KIE Server properties and click . Enter the controller URL for Business Central and configure additional properties for KIE Server. The controller URL has the following form where <HOST:PORT> is the address of Business Central on the second computer: Complete the installation. To verify that the Process Automation Manager controller is now integrated with Business Central, go to the Execution Servers page in Business Central and confirm that the KIE Server that you configured appears under REMOTE SERVERS .

Commands:
java -jar rhpam-installer-7.13.5.jar
java -Dizpack.mode=privileged -jar rhpam-installer-7.13.5.jar
java -XX:MaxHeapSize=4g -jar rhpam-installer-7.13.5.jar
java -jar rhpam-installer-7.13.5.jar <path-to-auto.xml-file>
ALTER DATABASE <DBNAME> SET ALLOW_SNAPSHOT_ISOLATION ON ALTER DATABASE <DBNAME> SET READ_COMMITTED_SNAPSHOT ON
java -jar rhpam-installer-7.13.5.jar -console
press 1 to continue, 2 to quit, 3 to redisplay.
Specify the home directory of one of the following servers: Red Hat JBoss EAP 7 or Red Hat JBoss Web Server 5. For more information, see https://access.redhat.com/articles/3405381[Red Hat Process Automation Manager 7 Supported Configurations].
Would you like to generate an automatic installation script and properties file?
java -jar rhpam-installer-7.13.5.jar <path-to-auto.xml-file>
ALTER DATABASE <DBNAME> SET ALLOW_SNAPSHOT_ISOLATION ON ALTER DATABASE <DBNAME> SET READ_COMMITTED_SNAPSHOT ON
<HOST:PORT>/business-central/rest/controller