Description of the Illustration psft_multi_region_withCallouts.png

This image is an architecture diagram of the deployment of PeopleSoft application across two regions while ensuring high availability and disaster recovery.

The architecture consists of an Oracle Cloud Infrastructure primary region and an Oracle Cloud Infrastructure disaster recovery region.

The Primary Region

The primary region contains a virtual cloud network (VCN) and is connected to the Internet, the customer's existing network, and a web client. Within the primary region VCN are two virtually identical availability domains, Availability Domain 1 and Availability Domain 2. The VCN is linked to the region via a NAT gateway, an Internet gateway, and a dynamic routing gateway, which ensures the connectivity of the availability domains. Each availability domain contains a bastion and load balancer. The application tier within each availability domain contains servers for the Web and for ElasticSeach. The tiers also contain subnets comprising process scheduler servers and application servers. Each availability domain also contains a PeopleTools server and a database tier, which communicates with Oracle Cloud Infrastructure object storage through a service gateway. The database tier for Availability Domain 2 is disabled in this illustration.

The Disaster Revovery Region

Unlike the Primary Region, the disaster recovery region is not connected directly to the Internet, the customer's existing network, or a web client. Instead, it's connected via rsync to Primary Region's Availability Domain 2 such that it can leverage that domain's external connections. Otherwise, it is identical to the other availability domains. The database tier in the Disaster Recovery region are sync'd by Oracle Active Data Guard and the parallel Oracle Cloud Infrastructure object storage components are sync'd by Cross-Region Object Storage.

There are six numbered callouts on the illustration:
  1. Active-Active Components across ADs
  2. Active-Passive Components across Regions
  3. Regional Subnets across ADs
  4. Load Balancing across ADs
  5. Storage Synchronization across ADs
  6. Database DR across ADs
Each callout is described in the surrounding text.

The bastion host receives requests through the dynamic routing gateway (DRG) and internet gateway. The DRG is the gateway that connects your on-premises network to your cloud network. To enable communication between the DRG and the customer-premises equipment, use IPSec VPN or Oracle Cloud Infrastructure FastConnect. To access your bastion host from the internet, set up an internet gateway (IGW). An IGW is a software-defined router that provides a path for network traffic from your VCN to the internet.

The load balancer instances receive requests over port 8000 or 8443, and then send it to the web servers in the application tier in Availability Domain 1 or 2. The application tier consists of two web server instances in subnet, ElasticSearch servers in another subnet, two application servers and two process scheduler servers in a third subnet. To ensure high availability, redundant instances are deployed in the application tier and all instances are active. The web servers receive application requests from the web environment, the internet and the intranet, through the load balancer. It forwards the requests to the application server. The application servers submit the SQL to database servers in Availability Domain 1 over port 1521. The ElasticSearch servers interacts with PeopleSoft web servers and process scheduler servers. PeopleTools client is placed in a separate subnet and it interacts with the PeopleSoft database over port 1521.