Chapter 3. Deploying a Red Hat Process Automation Manager environment using the Automation Broker

Procedure

1. In the OpenShift Web UI, select Add to Project Browse Catalog.
2. In the search field, type Red Hat Process Automation Manager.
3. Select the Red Hat Process Automation Manager 7.3 APB catalog entry.
4. Click Next.

5. Select the required architecture elements, as described on the screen, and click the Next button.

   Important

   If you want to deploy an environment with immutable servers and a monitoring infrastructure, you must first install the Immutable Server - Monitor option and then the Immutable Server - KIE Process Server option.

6. Enter the parameters as described on the screen. In most cases, the default values lead to a working deployment; you can modify them as necessary. You must enter the following settings:

   • For the Immutable Server - Monitor option:

     • The Maven repository URL field. You must provide a Maven repository with the same versions of all the artifacts that are deployed on any monitored immutable servers.
     • The Admin password field. You must record the administrative user name and password to configure monitored servers to connect to Business Central Monitoring.

   • For the Immutable Server - KIE Process Server option:

     • The KIE Server Container Deployment, Git Repository URL, and Git Repository Reference fields. These settings determine the source code that the deployment process builds and deploys on the Process Server.

     • If you deployed the Immutable Server - Monitor option and want to connect the server to the monitoring infrastructure:

       • Under Router integration, the service name of the rhpam-immutable-mon-smartrouter service.

       • Under Controller integration, the service name of the rhpam-immutable-mon-rhpamcentrmon service and the admin username and password that you set in the Immutable Server - KIE Process Server option.

         Important

         Avoid each of the following combinations of settings. These combinations produce an invalid environment.

         • Process server>Database type H2 and Process server>Number of replicas exceeding 1.
         • Process server>Database type External and Process server>Sets of Process Servers exceeding 1.
         • Red Hat - Single Sign-On configured and Process server>Sets of Process Servers exceeding 1.

7. If you are using the External database type for the Process Server in the Authoring, Immutable Server - Process Server, or Managed Environment option, set the parameters under the External Database heading. Set the host, port, database name, and database JDBC URL to the correct values for your database server. Use the following values for the other fields:

   • Driver name: The driver for the server, depending on the server type:

     • mysql
     • postgresql
     • mariadb
     • mssql
     • db2
     • oracle
     • sybase

   • Dialect class (KIE_SERVER_EXTERNALDB_DIALECT): The Hibernate dialect for the server, depending on the server type:

     • org.hibernate.dialect.MySQL5Dialect (used for MySQL and MariaDB)
     • org.hibernate.dialect.PostgreSQLDialect
     • org.hibernate.dialect.SQLServer2012Dialect (used for MS SQL)
     • org.hibernate.dialect.DB2Dialect
     • org.hibernate.dialect.Oracle12cDialect
     • org.hibernate.dialect.SybaseASE15Dialect

8. If you created a custom image for using an external database server other than MySQL or PostgreSQL, as described in Section 2.5, “Building a custom Process Server image for an external database”, you must also set the Process Server Image Stream Name parameter (under the Process Server heading) to the following value:

   • For Microsoft SQL Server, rhpam73-kieserver-mssql-openshift
   • For MariaDB, rhpam73-kieserver-mariadb-openshift
   • For IBM DB2, rhpam73-kieserver-db2-openshift
   • For Oracle Database, rhpam73-kieserver-oracle-openshift
   • For Sybase, rhpam73-kieserver-sybase-openshift

9. Click Next to commence deployment.

   After deploying the environment, you can access it using the HTTPS routes displayed in the OpenShift Web console. HTTP requests are redirected to HTTPS.