Skip to main content

Table of Contents

Configuring high availability deployments


Only available versions of this content are shown in the dropdown

Highly available systems are accessible with minimal or no downtime, despite hardware failure, process crashes due to insufficient resources, memory leaks, maintenance, application upgrade activities, or natural disasters. Pega Platform provides tools to meet high level production service level agreements for mission critical applications with high availability features.

High availability features include:

  • Application server maintenance
    • Operations staff can initiate application tier maintenance that is transparent to users.
    • Pega Platform web application servers that require maintenance can be quiesced.
    • Users on a server that has been quiesced are redirected to other servers in a cluster.
    • Rolling server restarts can be used to upgrade Java Virtual Machine (JVM) settings, physical server maintenance, or Pega Platform upgrades.
  • Application development guidelines
    • System Architects and developers have guidelines to assist them in developing and maintaining highly available Pega Platform applications and strategic applications.
    • Pega Platform System Administrators can control how rules are introduced into the production environment by locking rulesets.
  • Pega Platform updates and upgrades
    • Operations staff can upgrade the Pega Platform without taking production systems offline.
    • Split schema enables administrators to move users on the old rule base to the new rule base with a rolling restart.
  • Network Operation Center integration
    • Operations staff can use the Pega API to integrate high availability features into their operation centers.
  • Crash recovery
    • Operations staff can rely on application tier crash recovery to recover the user’s work when they log in to other Pega Platform servers in the cluster after a crash.
    • Administrators can optionally notify users that their session has been recovered.
    • Seamless recovery in the event of a browser crash is provided.
  • Understanding high availability configuration

    Pega Platform high availability can be configured to run on Java Platform, Enterprise Edition (Java EE) application servers, such as those provided by WebSphere, Weblogic, or JBoss. These enterprise offerings provide services and packaged components that can add other aspects of high availability when properly configured. The primary advantage is that enterprise application servers typically support redundant message queues and buses, which can allow Pega Platform services and listeners to continue during initiated and uninitiated outages.

  • Understanding high availability for developer environments

    Pega Platform developer environments can take partial advantage of high availability features.

  • Configuring your system for passivation and activation

    Passivation and activation help with system performance and high availability. Passivation allows a requestor, service, or clipboard page to be saved into storage and reactivated later, helping to free up JVM memory.

  • Configuring nodes for high availability

    The following list outlines the process that project managers should follow when creating a new highly available system using a Pega Platform installation.

Did you find this content helpful?

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us