Secondary Region Site Testing

You can start the full PeopleSoft stack at the standby site on OCI for testing without impacting the primary region, while the production PeopleSoft application is running. You can test patches and various configuration changes for a final validation of core changes before promoting the change to production.

An important prerequisite that should be met prior to conducting any DR site testing is ensuring that the URL used for standby testing is different from that of production. There are several ways to achieve this, but one way is to create an additional host name alias associated with a listener within the load balancer at each region. We recommend that you create a host name that is clearly for testing and associate it with the OCI Load Balancer listener. For example, psfthcm-test. You will also need to upload a signed SSL certificate for the host name you create and associate with the listener. Do this at each region, since either site might serve as the standby for the other.

Note:

Within the PeopleSoft application, there are different page styles that you can select to change the theme and banner information. We recommend that you use this feature when testing PeopleSoft at your standby. This will help anyone logging into the application running at the DR site know that this is not production, and that all their changes will be lost when the site is reverted back to standard standby operation. For more details on changing PeopleSoft themes and downloading themes, go to: psadmin.io Themes in GitHub.