Performing Application Lift

Application Lift means lifting the middle tier which consists of the Application Server, Web Server and Process Scheduler of PeopleSoft Application.

1. Use only the PeopleSoft Admin user (for example, psadm2) to perform Application Lift.

2. Make sure to have sufficient free disk space for Application Lift (based on PS_APP_HOME and PS_CUST_HOME size). A minimum disk space of 10GB is required.

3. Ensure PS_APP_HOME and PS_CUST_HOME directories are available.

4. Ensure that the user running the Lift utility has the permission to create files or directories at the user's home directory, Lift utility directories, and the destination directory where the DPKs are saved, /tmp, PS_APP_HOME, and PS_CUST_HOME directories.

To perform the one-step Lift automation procedure for the application:

1. Download the Lift utility from the Lift and Shift page. For this, perform the following:

   1. Navigate to the Lift and Shift tile.

   2. Copy the “LIFT_UTILITY.zip” utility to the target machine to perform lift.

   Note: If you have recently updated Cloud Manager with any PRPs that has fixes to the lift utility, then SSH to the Cloud Manager instance and delete the stale zip file from /tmp/LIFT_UTILITY.ZIP.

2. Navigate to the below folder after extracting the LIFT_UTILITY.zip and set permissions:

   chmod -R 777 <LIFT_UTILITY_PATH>
   cd <LIFT_UTILITY_PATH>/setup

3. For Linux, run the sh psft-osl.sh command to perform lift.

4. Select 1 at the prompt to select the type of environment to lift.

   This example illustrates the prompt to lift the Application Environment.

   

5. To create the PeopleSoft App Server DPK, you need to provide the database name (or PDB name in case of supported Oracle multitenant databases) and destination directory.

   Note: If the utility is unable to fetch the data from the environment (for example, app_type/oracle_home), it will prompt the user to input the same.

6. Choose any one of the below options:

   1. Create and Save DPK in APP/DB Environment.

   2. Create, Save DPK in APP/DB Environment and Upload the DPK to Oracle Cloud Infrastructure (Object Storage).

7. If you select option 1. Create and Save DPK in APP/DB Environment, you will need to manually upload the DPK to Object Storage. See Uploading the DPK Manually to Oracle Cloud Infrastructure.

8. If option 2 to upload the DPK to Oracle Object Storage is selected, then the script prompts the user to input the Oracle Cloud tenancy credentials as mentioned below in order to upload the DPK once created:

   See Locating OCI Credentials

   – Oracle Cloud Infrastructure Region Name

   – Oracle Cloud Infrastructure Tenancy Name

   – Oracle Cloud Infrastructure Tenancy ID

   – Oracle Cloud Infrastructure User ID

   – Private Key Location, indicates the API signing private key that was created during CM configuration and must be copied to the instance where lift utility will be run. This input refers to the full path to the file.

   – Passphrase, refers to the passphrase that was used to encrypt the API signing keys.

   Note: You need to manually copy the key file or copy the key file contents and save locally in the machine where you perform the lift. This is the corresponding Private Key to the Public Key that was set in the API Keys of the user setting.

9. After Application Lift is complete, the following Application DPK will be created based on the PeopleTools version on the application instance.

   APP-DPK-<platform>-<app_type>-<db_name>-1of3.zip.

   Note: The APP-DPK*-3of3.zip will not be created as part of the Lift utility, however the APP-DPK*- 3of3.zip DPK will be available from the PeopleTools DPK when the shift is triggered from Cloud Manager.

The Lifted DPKs created are available in the destination directory. If you had chosen to create and upload DPK to Oracle Object Storage, then the uploaded DPKs are available in Oracle Object Storage and listed in the Lift and Shift page of Cloud Manager.