A typical Pega Platform cluster consists of several physical or virtual machine instances sharing a single database. Machine instances may have multiple web application server instances or Pega Platform servers.
Use the high availability APIs, which can be directly integrated into a custom Pega Platform management console to notify that an upgrade is in process. The Pega API provides RESTAPIs for managing quiesce and other operations. For more information, see Pega API services.
If an organization is not managing multiple clusters, you can use high availability landing pages. Because the Pega Platform cluster management pages use the system pulse to communicate, data is accurate after two pulse cycles, and the latency that is introduced when updating the Pega Platform server run state might not be optimal for large organizations.
- Privileges and roles for high availability management
Various privileges and roles are used for Pega Platform high availability management.
- High availability cluster settings
The HA Cluster Settings page is used to configure crash recovery and accelerated passivation options.
- Managing clusters by using Autonomic Event Services (AES)
To perform cluster management using Autonomic Event Services (AES), use the Quiesce manager.