Skip to main content

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

Cluster management

Updated on May 11, 2022

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.

Diagram of a typical Pega Platform cluster
Diagram of a typical Pega Platform cluster

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.

Note: If you use this process, you must manually move rules created at run time on the old rule schema to the new schema.

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.

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