Highly available application tier architectures must have enough computing power to support fail-over, as well as a means to allocate new servers to support increased demands for service.
To deploy a highly available production system, two or more physical or virtual machines are needed. These allow for horizontal cluster scale and provide hardware redundancy to maximize efficiency and offer a solution for crash recovery. Each machine can deploy one or more Pega Platform servers.
Organizations can employ vertical cluster scale by adding multiple Pega Platform server instances to support production load. Determine the number of Pega Platform server instances based on capacity planning and by evaluating operational thresholds.
For information on supported application server platform versions, see the Platform Support Guide for your version of Pega Platform. For more information, see Pega Platform Support Guide Resources.
For consistency, the term "Pega Platform server" is used for each web application server instance (JVM) on a physical or virtual machine. The decision to configure multiple Pega Platform servers on physical or virtual machines must be coupled with redundancy at the machine level.
Pega Platform servers must be designed to support redundancy among Pega Platform various components, such as connectors, services, listeners, and search. The exact configuration varies based on the specifics of the applications in the production environment.
Single sign-on for automatic reauthentication
Pega Platform high availability features are secure and require reauthentication in the event of a Pega Platform server crash. The Pega Platform retains operator authorization for redirection of a user during server quiesce. A single sign-on solution, although not required, enables a seamless user experience.
For more information, see Configuring SSO login authentication with a SAML identity provider.