Configure the Middle-Tier in OCI

There are multiple ways to migrate the mid-tier to OCI, such as using a tar ball backup, provision new mid-tier using PUM images or the PeopleSoft Cloud Manager. In this playbook, the mid-tier is rewired with Oracle Autonomous Database on Dedicated Exadata Infrastructure on OCI.

Configure with Mid Tier at OCI

1. Install the Oracle Database Client packages you downloaded earlier in the Download Software Packages section. Run the following packages as root in the given order:

   [root@hr9246 ~]# yum install -y oracle-instantclient19.20-basic-19.20.0.0.0-1.x86_64.rpm
   [root@hr9246 ~]# yum install -y oracle-instantclient19.20-sqlplus-19.20.0.0.0-1.x86_64.rpm
   [root@hr9246 ~]# yum install -y oracle-instantclient19.20-tools-19.20.0.0.0-1.x86_64.rpm

2. Update the following environment variables for PeopleSoft and Oracle Database users for this environment such as oracle2, psadm1, psadm2 and psadm3.
   You must update the environment variables to point to the right version of Oracle Client to establish the connectivity to Oracle Autonomous Database.
   The environment variables resemble:

   echo "PATH=/usr/lib/oracle/19.20/client64/bin:$PATH; export PATH" >> ~/.bashrc
   echo "LD_LIBRARY_PATH=/usr/lib/oracle/19.20/client64/lib:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH" >> ~/.bashrc

3. To connect with Oracle Autonomous Database we need to download and configure the Oracle Autonomous Database.
   1. Navigate to the OCI console, to the Oracle Autonomous Database details page.
   2. Click Database connection.
   3. Click Download Wallet.
   4. Provide a wallet password, and click Download to save the client security credentials ZIP file.
   5. Update the sqlnet.ora file and ensure TNS_ADMIN environment variable is pointing correctly to the location where the wallet is extracted.
      PeopleSoft Applications and tools connect to Oracle Autonomous Database using Oracle Net Services (also known as SQL*Net). Oracle Net Services enables a network session from the client application to an Oracle database server through the network defined by the dedicated infrastructure hosting the database. Oracle Net Services support a variety of connection types to Oracle Autonomous Database, including Oracle Call Interface. Wallet files, along with the database user ID and password provide access to data in Oracle Autonomous Database. Store wallet files in a secure location.
4. For the tnsnames.ora file, copy the connect string of service names database_name_low or database_name_tp and make another service name with 8 characters or less.
   This is a PeopleSoft app server requirement.
5. Validate tnsnames.ora file as the psadm2 user and test the connectivity.

Configure PeopleSoft Server

Your PeopleSoft server components need to be configured.

Update the password for the SYSADM user, configure the app server, process scheduler, web server, and PeopleSoft components.

1. Update password for the SYSADM user.
   PeopleSoft users, PS, PEOPLE and SYSADM, have been created in Oracle Autonomous Database on Dedicated Exadata Infrastructure. The password in the PeopleSoft application needs to be changed. See 'Create Tablespace, Roles and PeopleSoft Users' for details.
   To update the password for SYSADM:
   1. Run the update statement for PSACCESSPROFILE with the SYSADM password.
   2. Encrypt the password using the Data Mover utility.
2. Configure an application server domain with the new password and start it.
3. Similarly, configure a process scheduler domain with the new password and start it.
4. Configure a new web server domain and start it.
5. Configure IB, nodes, report repository, printers, and so on, as part of the post configuration of the PeopleSoft application.