Preface

Prerequisites

• Red Hat OpenShift Container Platform version 3.11 is deployed.
• At least four gigabytes of memory are available in the OpenShift cluster/namespace.

• For a high-availability deployment, the following resources are available on the OpenShift cluster:

  • For the Business Central replicated pod, 8 gigabytes of memory and 2 CPU cores are required for each replica. Two replicas are created by default.
  • For the KIE Server replicated pod, 1 gigabyte of memory and 1 CPU core are required for each replica. Two replicas are created by default.
  • For the Red Hat Data Grid replicated pod, 2 gigabytes of memory and 1 CPU core are required for each replica. Two replicas are created by default.
  • The Red Hat AMQ replicated pod uses the default resource limits configured on your cluster.
  • The MySQL replicated pod uses the default resource limits configured on your cluster.

• The OpenShift project for the deployment is created.
• You are logged in to the project using the oc command. For more information about the oc command-line tool, see the OpenShift CLI Reference. If you want to use the OpenShift Web console to deploy templates, you must also be logged on using the Web console.

• Dynamic persistent volume (PV) provisioning is enabled. Alternatively, if dynamic PV provisioning is not enabled, enough persistent volumes must be available. By default, the deployed components require the following PV sizes:

  • The replicated set of KIE Server pods requires one 1Gi PV for the database by default. You can change the database PV size in the template parameters. This requirement does not apply if you use an external database server.
  • Business Central requires one 1Gi PV by default. You can change the PV size for Business Central persistent storage in the template parameters.
• If you intend to deploy a high-availability authoring environment, which includes high-availability Business Central, your OpenShift environment supports persistent volumes with ReadWriteMany mode. If your environment does not support this mode, you can use NFS to provision the volumes. However, for best performance and reliability, use GlusterFS to provision persistent volumes for a high-availability authoring environment. For information about access mode support in OpenShift public and dedicated clouds, see Access Modes.