Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

High Availability: What’s New in Pega 7

Suggest edit Updated on February 17, 2016
high-availability

Provide better production service level agreements for mission critical applications. High Availability supports application server maintenance and crash recovery that is transparent to users. Leveraging resilient architectures, these features combine with flexible schema management to upgrade Pega production systems with reduced system downtime.​

Perform application server maintenance transparent to users.

Architect for continuous availability

System architects can design for redundancy across all tiers of the hardware and deployment architecture of PRPC to ensure continuous system availability using a redundant three-tier architecture in private hosting or cloud environments. Pega 7 provides guidelines for load balancers, application servers, shared storage, and databases.

Image-1
 
Image-1

Perform application server maintenance

Businesses can choose a variety of  ways to integrate PRPC high availability into Network Operation Centers (NOCs). System administrators can perform application-tier maintenance that is transparent to users.

Provide continuous user experience during crash recovery.

Recover user experience for application-tier crashes

PRPC provides server-side crash recovery, which is handled transparently with load balancers that provide application monitoring. Single sign-on ensures a continuous user experience. and Operators can manage nodes without affecting the end user experience.

Image-1
Image-1

Monitor and maintain nodes

Use your Network Operating Center to monitor node status and transparently manage crash recovery. Operators have the option of sending crash event messages to end users.

 

Upgrade PRPC and develop highly available applications.

Upgrade production PRPC

PRPC now has a split schema database architecture that separates work and data. Database administrators can create split schemas to enable users on the old rulebase to migrate to the new rulebase with a rolling restart of the application servers.

Image-1
Image-1

Develop highly available applications

PRPC developers and System Architects can take advantage of high availability features and Project Managers can accelerate the deployment of a highly available system by following the guidelines and best practices suggested in the High Availability Administration Guide.

Additional information

High Availability roles

Checklist for rolling out High Availability

High Availability Administration Guide

Did you find this content helpful? YesNo

100% found this useful

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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us