Chapter 1. Installation environment options for Red Hat Process Automation Manager

With Red Hat Process Automation Manager, you can set up a development environment to develop business applications, a runtime environment to run those applications to support decisions, or both.

  • Development environment: Typically consists of one Business Central installation and at least one Process Server installation. You can use Business Central to design decisions and other artifacts, and you can use Process Server to execute and test the artifacts that you created.
  • Runtime environment: Consists of one or more Process Server instances with or without Business Central. Business Central has an embedded Process Automation Manager controller. If you install Business Central, use the MenuDeployExecution servers page to create and maintain containers. If you want to automate Process Server management without Business Central, you can use the headless Process Automation Manager controller.

You can also cluster both development and runtime environments. A clustered development or runtime environment consists of a unified group or "cluster" of two or more servers. The primary benefit of clustering Red Hat Process Automation Manager development environments is high availability and enhanced collaboration, while the primary benefit of clustering Red Hat Process Automation Manager runtime environments is high availability and load balancing. High availability decreases the chance of a loss of data when a single server fails. When a server fails, another server fills the gap by providing a copy of the data that was on the failed server. When the failed server comes online again, it resumes its place in the cluster. Load balancing shares the computing load across the nodes of the cluster to improve the overall performance.

Note

Clustering of the runtime environment is currently supported on Red Hat JBoss EAP 7.2 and Red Hat OpenShift Container Platform only. Clustering of Business Central is currently a Technology Preview feature that is not yet intended for production use. For more information about Red Hat Technology Preview support, see Technology Preview Features Support Scope.