Preface

As a system engineer, you can deploy a Red Hat Process Automation Manager fixed managed server environment on Red Hat OpenShift Container Platform to provide an infrastructure to execute services, process applications, and other business assets. This environment includes a fixed number of Process Servers in a single deployment; you cannot add or remove servers at a later point. You can use Business Central Monitoring to manage and update the processes running on Process Servers in this environment.

Prerequisites

  • Red Hat OpenShift Container Platform version 3.11 is deployed.
  • At least four gigabytes of memory are available in the OpenShift cluster/namespace.
  • The OpenShift project for the deployment has been 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 following sizes are required:

    • Each deployed replicated set of Process Server pods requires, by default, one 1Gi PV for the database. 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 Monitoring requires one 64Mi PV.
    • Smart Router requires one 64Mi PV.
  • Your OpenShift environment supports persistent volumes with ReadWriteMany mode. For information about access mode support in OpenShift Online volume plug-ins, see Access Modes.

    Important

    ReadWriteMany mode is not supported on OpenShift Online and OpenShift Dedicated.

Note

Since Red Hat Process Automation Manager version 7.5, support for Red Hat OpenShift Container Platform 3.x is deprecated, including installation using all templates and using the Automation Broker (Ansible Playbook). New features might not be added, and this functionality will be removed in a future release.