Learn About Oracle Maximum Availability Architecture for PeopleSoft

Oracle’s PeopleSoft application is a comprehensive suite of integrated business applications providing human capital management, financial management, procurement and supplier management, project portfolio management, asset lifecycle management, order and inventory management, and campus solutions. These mission critical functions require protection, to ensure they are available at all times. Whether PeopleSoft is deployed in Oracle Cloud Infrastructure (OCI) or on-premises, planning and implementing strategies for high availability and disaster recovery are paramount.

Oracle Maximum Availability Architecture (Oracle MAA) is Oracle's best practice blueprint for implementing Oracle high availability technologies and recommendations. The goal of Oracle MAA is to achieve the optimal high availability architecture at the lowest cost and complexity.

This reference architecture provides a high-level introduction to Oracle Cloud Infrastructure (OCI) and PeopleSoft Oracle MAA architectures. See Provision and deploy a maximum availability solution for PeopleSoft on Oracle Cloud for the installation, configuration, and operational best practices for an end-to-end MAA implementation of PeopleSoft on OCI.

Before You Begin

If you're new to Oracle Cloud, we highly recommend that you read the following:

• Welcome to Oracle Cloud Infrastructure. There are a variety of tutorials to help you understand the concepts.
• Best practices framework for Oracle Cloud Infrastructure.

Architecture

The following architecture diagrams show PeopleSoft and Oracle Maximum Availability Architecture (Oracle MAA).

PeopleSoft Maximum Availability Architecture is a PeopleSoft high availability architecture layered on top of the Oracle Database and Oracle Fusion Middleware Oracle MAA, including a secondary site to provide business continuity in the event of a primary site failure.

The following shows a full-stack Oracle MAA architecture, including primary and secondary sites. The secondary site is a replica of the primary.

Description of the illustration peoplesoft-maa-arch.png

peoplesoft-maa-arch-oracle.zip

Each site consists of the following:

• An HTTPS load balancer for web-based application services
• Two servers that host the PeopleSoft Pure Internet Architecture (PIA) domain
• Two servers that host both the PeopleSoft Application Server and the Process Scheduler domains
• A shared file system for PeopleSoft application software and report repository
• An Oracle Real Application Clusters (Oracle RAC) database, with two database servers and shared storage
• Oracle Active Data Guard, which allows routing of “mostly read operations” to the standby database while keeping the standby database current with the primary

Both the application tier shared file system and the database are replicated to the secondary site – the application tier using rsync, and the database tier using Oracle Data Guard.

The data at the second site is kept in sync with the primary by using appropriate replication mechanisms.

• For the database itself, Oracle Active Data Guard ensures the standby database is kept in sync and transactionally consistent.
• For file system output generated during the operation of the application, rsync is used to frequently replicate the output to another region. There will be a small gap to resolve by identifying missing file system components and determining the action to take for each.