Skip to main content


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

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 Roles

Updated on September 10, 2021

High Availability features enable you to 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.​

High Availability features are relevant to many roles within an IT organization. Whether you are a PRPC System Architect, System Administrator, or Developer, a Network Operations staff member, or a Database Administrator, your responsibilities may be different.

This matrix matches the high availability features that are most relevant to your role. Click a topic or an ‘X’ to jump to the section in the High Availability Administration guide PDF.

TopicPRPC System ArchitectsPRPC System AdministratorsNetwork OperationsDatabase Administrators
ArchitectureX X 
RequirementsXXXX
ConfigurationXXXX
System maintenance: QuiesceXXX 
Crash recoveryXXX 
Split schemaXX X
Managing Pega 7 in production XX 
Developing highly available applicationsX   
Configuring PRPC services for high availabilityXXX 
High availability extensionsXX  
Scenario: Performing a rolling restart XX 
Scenario: Operational use of quiesce XX 
Scenario: F5 load balancer setup XX 
Definition of Roles

The following are definitions of the roles listed above.

PRPC System Architect

A system architect is an application developer team member who contributes object-oriented design and technical implementation skills. Typically, a system architect works with rules in the Data Model, Technical, and Integration categories. Developers holding this role may need skills in integration technologies, XML, debugging, and some familiarity with Java.

See the high availability features most relevant to this role.

PRPC System Administrator

A system administrator is the person who controls security and access to your system, defines the organization structure, and monitors its use. While certain administrative tasks are routine, others may be easy to perform but require careful planning. Generally, an administrator works with rules and data objects in the Integration, SysAdmin, Security, and Organization categories.

See the high availability features most relevant to this role.

Network Operations Center Staff Member

A network operations center (NOC) staff member is a person responsible for monitoring networking environments that require little to no downtime. NOC staff are responsible for insuring that environments remain highly available or do not go down for an extended amount of time. Typically they work in a center with multiple computer stations and monitors to enable real-time network monitoring.

See the high availability features most relevant to this role. 

Database Administrator

A database administrator (DBA) is a person responsible for the installation, configuration, upgrade, administration, security, monitoring, and maintenance of databases in an organization. DBAs can also develop and design database schemas and plan for future expansion.

See the high availability features most relevant to this role.

Related Content

High Availability: What's new in Pega 7

Checklist for rolling out High Availability

High Availability Administration Guide

Tags

Pega Platform 7.1.1 - 8.3.1 System Architect Lead System Architect Pega Delivery Leader System/Cloud Ops Administrator System Administration

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us