Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Setting up the components of highly available environments

Updated on July 8, 2022

Creating a highly available system typically requires coordination across multiple groups in an organization. Individuals or groups responsible for deploying highly available systems must collectively understand and agree on how to configure the Pega Platform for their organization.

The smallest environment for basic configuration testing requires the following:

Additionally, as a part of planning for future server maintenance, you must decide whether to use the default immeditate drain method or configure your system to instead use the slow drain method when you perform the quiesce process on a node. For more information, see Quiescing high availability nodes.

  1. Understanding system settings for high availability environments

    There are multiple ways to set and manage Pega Platform settings. Following are recommended methods listed in terms of precedence:

  2. Setting up load balancers

    User and service requests are passed through a load balancer to the Pega Platform servers. The Pega Platform server in turn makes requests to a database.

  3. Configuring session affinity for slow drain

    Session affinity is configured with the load balancer. Session affinity ensures that all requests from a user are handled by the same Pega Platform server.

  4. Configuring application tier architecture for redundancy

    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.

  • Previous topic Architecting a high availability system
  • Next topic Understanding system settings for high availability environments

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us