Chapter 2. Preparing to deploy Red Hat Process Automation Manager in your OpenShift environment

Procedure

1. Determine whether Red Hat OpenShift Container Platform was configured with the user name and password for Red Hat registry access. For details about the required configuration, see Configuring a Registry Location. If you are using an OpenShift Online subscription, it is configured for Red Hat registry access.

2. If Red Hat OpenShift Container Platform was configured with the user name and password for Red Hat registry access, run the following commands:

   $ oc get imagestreamtag -n openshift | grep rhpam72-businesscentral
   $ oc get imagestreamtag -n openshift | grep rhpam72-kieserver

   If the outputs of both commands are not empty, the required image streams are available in the openshift namespace and no further action is required.

3. If the output of one or both of the commands is empty or if OpenShift was not configured with the user name and password for Red Hat registry access, complete the following steps:

   1. Log in to OpenShift with the oc command as a user with administrator permissions.
   2. Complete the steps documented in Registry Service Accounts for Shared Environments. You must log on to Red Hat Customer Portal to access the document and to complete the steps to create a registry service account.
   3. Select the OpenShift Secret tab and click the link under Download secret to download the YAML secret file.
   4. View the downloaded file and note the name that is listed in the name: entry.

   5. Run the following commands:

      oc create -f <file_name>.yaml -n openshift
      oc secrets link default <secret_name> --for=pull -n openshift
      oc secrets link builder <secret_name> --for=pull -n openshift

      Where <file_name> is the name of the downloaded file and <secret_name> is the name that is listed in the name: entry of the file.

   6. Download the rhpam-7.2.0-openshift-templates.zip product deliverable file from the Software Downloads page and extract the rhpam72-image-streams.yaml file.

   7. Complete one of the following actions:

      • Run the following command:

        $ oc create -f rhpam72-image-streams.yaml -n openshift

      • Using the OpenShift Web UI, select Add to Project → Import YAML / JSON and then choose the file or paste its contents.

Procedure

1. Generate an SSL keystore with a private and public key for SSL encryption for Process Server. In a production environment, generate a valid signed certificate that matches the expected URL of the Process Server. Save the keystore in a file named keystore.jks. Record the name of the certificate and the password of the keystore file.

   See Generate a SSL Encryption Key and Certificate for more information on how to create a keystore with self-signed or purchased SSL certificates.

2. Use the oc command to generate a secret named kieserver-app-secret from the new keystore file:

   $ oc create secret generic kieserver-app-secret --from-file=keystore.jks

Procedure

1. Generate an SSL keystore with a private and public key for SSL encryption for Business Central. In a production environment, generate a valid signed certificate that matches the expected URL of the Business Central. Save the keystore in a file named keystore.jks. Record the name of the certificate and the password of the keystore file.

   See Generate a SSL Encryption Key and Certificate for more information on how to create a keystore with self-signed or purchased SSL certificates.

2. Use the oc command to generate a secret named businesscentral-app-secret from the new keystore file:

   $ oc create secret generic businesscentral-app-secret --from-file=keystore.jks

Procedure

1. Generate an SSL keystore with a private and public key for SSL encryption for Smart Router. In a production environment, generate a valid signed certificate that matches the expected URL of the Smart Router. Save the keystore in a file named keystore.jks. Record the name of the certificate and the password of the keystore file.

   See Generate a SSL Encryption Key and Certificate for more information on how to create a keystore with self-signed or purchased SSL certificates.

2. Use the oc command to generate a secret named smartrouter-app-secret from the new keystore file:

   $ oc create secret generic smartrouter-app-secret --from-file=keystore.jks

Procedure

1. For IBM DB2, Oracle Database, or Sybase, provide the JDBC driver JAR in a local directory or on an HTTP server. Within the local directory or HTTP server, the following paths are expected:

   • For IBM DB2, <local_path_or_url>/com/ibm/db2/jcc/db2jcc4/10.5/db2jcc4-10.5.jar
   • For Oracle Database, <local_path_or_url>/com/oracle/ojdbc7/12.1.0.1/ojdbc7-12.1.0.1.jar

   • For Sybase, <local_path_or_url>/com/sysbase/jconn4/16.0_PL05/jconn4-16.0_PL05.jar

     Where <local_path_or_url> is the path to the local directory or the URL for the HTTP server where the driver is provided.

2. To install the source code for the custom build, download the rhpam-7.2.0-openshift-templates.zip product deliverable file from the Software Downloads page. Unzip the file and, using the command line, change to the templates/contrib/jdbc directory of the unzipped file.

3. Change to the following subdirectory:

   • For Microsoft SQL Server, mssql-driver-image
   • For MariaDB, mariadb-driver-image
   • For IBM DB2, db2-driver-image
   • For Oracle Database, oracle-driver-image
   • For Sybase, sybase-driver-image

4. Run the following command:

   • For Microsoft SQL Server or MariaDB:

   ../build.sh

   • For IBM DB2, Oracle Database, or Sybase:

   ../build.sh --artifact-repo=<local_path_or_url>

   Where <local_path_or_url> is the path to the local directory or the URL for the HTTP server where the driver is provided. For example:

   ../build.sh --artifact-repo=/home/builder/drivers
   ../build.sh --artifact-repo=http://nexus.example.com/nexus/content/groups/public

   If you want to configure your OpenShift docker registry address in the process, add also the --registry=<registry_name.domain_name:port> parameter to your build command.

   Examples:

   ../build.sh --registry=docker-registry.custom-domain:80
   
   ../build.sh --artifact-repo=/home/builder/drivers --registry=docker-registry.custom-domain:80

Procedure

1. To check whether your environment uses GlusterFS, run the following command:

   oc get storageclass

   In the results, check whether the (default) marker is on the storage class that lists glusterfs. For example, in the following output the default storage class is gluster-container, which does list glusterfs:

   NAME              PROVISIONER                       AGE
   gluster-block     gluster.org/glusterblock          8d
   gluster-container (default) kubernetes.io/glusterfs 8d

   If the result has a default storage class that does not list glusterfs or if the result is empty, you do not need to make any changes. In this case, skip the rest of this procedure.

2. To save the configuration of the default storage class into a YAML file, run the following command:

   oc get storageclass <class-name> -o yaml >storage_config.yaml

   Where class-name is the name of the default storage class. For example:

   oc get storageclass gluster-container -o yaml >storage_config.yaml

3. Edit the storage_config.yaml file:

   1. Remove the lines with the following keys:

      • creationTimestamp
      • resourceVersion
      • selfLink
      • uid

   2. On the line with the volumeoptions key, add the following two options: features.cache-invalidation on, performance.nl-cache on. For example:

      volumeoptions: client.ssl off, server.ssl off, features.cache-invalidation on, performance.nl-cache on

4. To remove the existing default storage class, run the following command:

   oc delete storageclass <class-name>

   Where class-name is the name of the default storage class. For example:

   oc delete storageclass gluster-container

5. To re-create the storage class using the new configuration, run the following command:

   oc create -f storage_config.yaml