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.
- Understand the production requirements
- Define the service level agreement for the production system.
- Perform capacity planning to understand the necessary computational requirements to meet the required service level agreement.
- Deploy the physical architecture
- Review the physical architecture of the system.
- Verify hardware requirements.
- Deploy a load balancer.
- Select a shared storage solution.
- Install Pega Platform instances on Pega Platform servers using split schema.
- Configure the Pega Platform
- Build applications or migrate existing applications
- Perform system testing
- Architecting a high availability system
The Pega Platform supports production service level agreements and emphasizes redundancy as a best practice for physical and software-based highly available production architectures.
- Cluster management
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.
- Performing a rolling upgrade
You can upgrade Pega Platform by performing a rolling upgrade (rolling restart) that keeps your system available during the upgrade process. You remove nodes from the load balancer, shut them down, upgrade, and restart each node one by one. When you have upgraded half of the nodes, you add them back to the load balancer.
Previous topic Reporting on passivated requestors Next topic Architecting a high availability system