Migrating PeopleSoft Application Environments to Oracle Compute Cloud Service

Unzip the Oracle Cloud DPK, PT-OCLD-DPK-LNX.zip, into a location, /ds1/pt/ocutils in this example, with enough disk space for the downloaded files. This directory is referred to later in this tutorial as LAS_TOOL_DIR.

unzip PT-OCLD-DPK-LNX_1of1.zip -d /ds1/pt/ocutils

This will create the following four directories:

• las — migration script along with a sample INI file used for the migration of PeopleSoft Application Home (PS_APP_HOME), PeopleSoft Customer Home (PS_CUST_HOME), and the PeopleSoft application database.
• puppet — PeopleSoft-developed Puppet modules used to set up a PeopleSoft environment.
  
• python2.7.9 — Python run-time software, used for executing the utility scripts.
• db — DPK containing Oracle 12c database software, along with run-time scripts to automate the process of plugging a PeopleSoft database PDB (created using the migration tool) into an Oracle 12c container database (CDB).
• scripts — various run-time scripts used to generate PeopleSoft orchestration files and to bootstrap PeopleSoft instances after the orchestration file creates the instances

1. On the file server, change directory to /ds1/pt/ocutils/las.
2. Open the configuration file las_setup.ini  for editing, and modify it for your environment.
   The file includes four sections.
3. Review and modify the [DEFAULT] section, which includes the following attributes:
   
   • tools_patch — specify the version of PeopleSoft PeopleTools used; for example, 8.55.01.
   • app_type — specify the application Pillar name. Valid values are: HR, HCM, FSCM, CRM, ELM, ELS, PS
     Note. Both uppercase and lowercase values are allowed.
   • app_release — specify the PeopleSoft application release; for example, 92
   • env_type — specify the type of PeopleSoft environment that is being migrated. Valid values are: both (if both mid-tier and database are running on the same host); app (if the host is running mid-tier), and db (if the host is running database).

4. Review and modify the [ps_app_home] section.
   Note. This section is not needed when migrating a database only.
   install_location —  specify the full path of the PS_APP_HOME location

5. Review and modify the [ps_cust_home] section.
   Note. This section is not needed when migrating a database only.
   install_location —  specify the full path of the PS_CUST_HOME location

6. Review and modify the [ps_app_database] section.
   Note. This section can be removed or left blank if you are not migrating a database.

   • oracle_user — specify the Oracle system user name
   • cdb_name — specify the name of the CDB
   • db_name — specify the name of the PDB that is being migrated
   • oracle_home — specify the full path for the Oracle home
   • is_db_pdb — if the database already has a pdb, specify YES.

This section assumes that an Oracle CDB and PDB are created using the on-premises database.

1. Copy the las_setup.ini file to a file for the database attributes:
   

   cd /ds1/pt/ocutils/las
   cp las_setup.ini las_setup_db.ini

2. Open the las_setup_db.ini file for editing, and modify it for your database; for example:
   

   [DEFAULT]
   tools_patch = 8.55.01
   app_type = HCM
   app_release = 92
   env_type = db
   
   [ps_app_database]
   oracle_user = oracle
   cdb_name = oowdemo.cdb
   db_name =  oowdemo.pdb
   oracle_home = /ds1/11.2.0.4/DB
   is_db_pdb = yes

3. On the machine containing the database, log in as root, and change directory to LAS_TOOL_DIR.
   

   cd /ds1/pt/ocutils

4. Use this command to create the database DPK:
   Note. The script uses su permissions as oracle_user and SQL*Plus to get the information needed to package the database into a DPK.
   
   

   ./python2.7.9/python las/lift_psft_app.py -f /ds1/pt/ocutils/las_setup_db.ini -o /ds1/pt/cloud_files

To create the Customer Application DPK with PS_APP_HOME (Application Home) and PS_CUST_HOME (Customer Home):

1. Copy the las_setup.ini file to a file for the application attributes:
   

   cd /ds1/pt/ocutils/las
   cp las_setup.ini las_setup_app.ini

2. Open the las_setup_app.ini file for editing, and modify it for your environment; for example:
   

   [DEFAULT]
   tools_patch = 8.55.01
   app_type = HCM
   app_release = 92
   env_type = app
   
   [ps_app_home]
   install_location = /ds1/pt/app_home
   
   [ps_cust_home]
   install_location = /ds1/pt/cust_home
   

3. Change directory to LAS_TOOL_DIR.
   

   cd /ds1/pt/ocutils

4. Create the Customer Application DPK with this command:
   

   ./python2.7.9/python las/lift_psft_app.py -f /ds1/pt/ocutils/las_setup_app.ini -o /ds1/pt/cloud_files

If the attachments are stored in the database this step can be skipped.

Perform this step on a machine that can access the attachments.

tar -czvf /ds1/pt/cloud_files/attach_repo.tgz /ds1/pt/attach_repo 

The PeopleSoft migration files include a python utility, upload_opc.py, for uploading PeopleSoft DPKs to Oracle Cloud Storage.

The script requires the following input:

• Cloud User name – The user who has access to the Oracle Cloud account. This user should also have appropriate permissions to upload to Oracle Cloud Storage
• Cloud User password – The User password. This password is prompted when the upload script is run.
• Container name – This is an optional parameter. The default is ‘compute_images’.
• Domain name – The name of the user’s identity domain.
• Source directory – The local directory where the DPKs are located

Use one of the following formats to run the utility:

LAS_TOOL_DIR/python2.7.9/python upload_opc.py -u <Cloud User name> -d <Domain name> -s <Source directory>

LAS_TOOL_DIR/python2.7.9/python upload_opc.py -u <Cloud User name> -d <Domain name> -s <Source directory> -c <Container name>

Note. The PeopleSoft DPKs are quite large. Depending on the network connectivity between your on-premises network and Oracle Cloud, the upload process will take a very long time – probably many hours. Please account for this delay while planning the whole migration process from the on-premises environment to Oracle Cloud.

Perform these steps from a machine with access to Oracle Cloud and the DPK location:

1. If you are using Oracle SES, merge the downloaded Oracle SES VM portions into one by running the following script:
   

   assemble_ses_images.sh -p OPC_EL5U10_X86_64_SES_11.2.2.2_BP4_PVM

2. Move all the required PeopleSoft DPKs (and the Oracle SES file, if using) into a single directory; for example:
   
   • PT-OCLD-DPK-LNX_1of1.zip (downloaded from My Oracle Support)
   • PEOPLETOOLS-LNX-8.55.02-1of4.zip (downloaded from My Oracle Support)
   • PEOPLETOOLS-LNX-8.55.02-2of4.zip (downloaded from My Oracle Support)
   • PEOPLETOOLS-LNX-8.55.02-3of4.zip (downloaded from My Oracle Support)
   • PEOPLETOOLS-LNX-8.55.02-4of4.zip (downloaded from My Oracle Support)
   • APP-DPK-<Application Name>-LNX-92-8.55.02-1of2.zip (generated as part of this tutorial)
   • APP-DPK-<Application Name>-LNX-92-8.55.02-2of2.zip (generated as part of this tutorial)
   • OPC_EL5U10_X86_64_SES_11.2.2.2_BP4_PVM (downloaded and assembled)
3. Run the upload script.
   Note. The script prompts for the user password twice.
   
   

   cd /ds1/pt/ocutils/scripts
   ../python2.7.9/python upload_opc.py -u a.b@example.com -d psftoowdemo -s /ds1/pt/cloud_files

The Oracle Cloud DPK is delivered with YAML files which should be used as a starting point. To avoid errors, copy and paste the values exactly as given. Modify for your environment, being sure to retain the indentation given here.

The psftconfig.yaml file used in this section has four major sections:

• image_list — List of OS-version images offered by Oracle Cloud on which to install the PeopleSoft system
• sshkey_list — List of ssh keys to identify the users who can access these machines
• identitydomains — List of identity domains where you want to create the VMs
• instance_list — List of the VM types with configurations

1. In LAS_TOOL_DIR/scripts, make a backup copy of psftconfig.yaml; for example:
   

   cp psftconfig.yaml psftconfig_bkup.yaml

2. Open psftconfig.yaml in a text editor, and modify it for your environment. The major sections of the file to be modified are described in the following sections.

Modify the image_list section with the OS-version images offered by Oracle Cloud on which to install the PeopleSoft system.

image_list:
  image_1:
    os_type:    linux
    image_name:  /oracle/public/oel_6.6_20GB_x11_RD
    image_index: 0

  image_2:
    os_type:    linux
    image_name:  /oracle/public/oel_6.4_5GB_RD
    image_index: 1

  image_3:
    os_type:    windows
    image_name: /Compute-$Domain/$username/win_image
    image_index: 2

In this section:

• os_type is linux or windows
• image_name is the location of the image file location.
  In the sample given here, "/Compute-psftoowdemo/a.b@example.com/ses11222" is an example for a custom image that was uploaded to Oracle Storage Cloud Service.
• image_index is a user-defined number used for later reference.

To see a list of available images, sign in to the Oracle Compute Cloud Service console, and select Create Instance. Access the Image drop-down list, as shown in this example:

Modify the sshkey_list section with a list of ssh keys which identify the users generated in the previous section, Generating SSH Keys, who can access these machines.

sshkey_list:
  ssh_key_0:
    key: /Compute-psftoowdemo/a1.b1@c1.com/ssh-key-1
    sshkey_index: 0
  ssh_key_1:
    key: /Compute-psftoowdemo/a2.b2@c1.com/psft-key-1
    sshkey_index: 1
  ssh_key_2:
    key: /Compute-psftoowdemo/a3.b3@example.com/psft-key-2
    sshkey_index: 2
  ssh_key_3:
    key: /Compute-psftoowdemo/a.b@example.com/psft-key-3
    sshkey_index: 3

In this section:

• key is comprised of the following parts:
  
  • identity domain name, for example Compute-psftoowdemo
  • user name, for example a1.b1@c1.com
  • key name given when importing the public key into Oracle Compute Cloud Service; for example, psft-key-1.
• sshkey_index is a user-defined number used for later reference

Edit the identitydomain section with the list of identity domains where you want to create the VMs.

identitydomains:
    domain_1:
      name: psftoowdemo
      pswd: password
      rest_endpoint: 'https://api-z27.compute.us6.oraclecloud.com'
      user: a.b@example.com 

In this section:

• name is identity domain name, for example psftoowdemo
• pswd is the password for each domain
• rest_endpoint is the API end point URL which can be retrieved from Oracle Compute Cloud Service, as shown below.
• iddomain_index is a user-defined number used for later reference.

To view the API end point URL, sign in to the Oracle Compute Cloud Service console, and select Service Details.  On the Service Details page, the API end point URL is found in the REST Endpoint field. In this example, the REST Endpoint is https://api-z27.compute.us6.oraclecloud.com.

Use the instance_list section to list the VMs, resources for the VMs, along with the components to be deployed on the host, such as application server domain, web server domain, and Process Scheduler domain. This section also includes features to be enabled and configurations that need to be set.

instance_list:
  instance_1:
    label:       "PSFT File Server"
    shape:       oc4
    os_type:     linux
    image_index: 0

    storage_attachments:
      storage_1:
         size:      500G

    hostname:    psft-file-server
    env_type:    fileserver
    features:    nfs
    psft_base:   /u01/app/oracle/product

  instance_2:
    label:       "PSFT HCM Test # Win 1"
    shape:       oc2m
    os_type:     windows
    image_index: 2

    storage_attachments:
      storage_1:
         size: 40G

    hostname:    psfthcmstwin1
    env_type:    psftclient
    app_type: hcm
    psft_base:   /u01/app/oracle/product
    features:    pia,appsrv,batch
    tools_version: 8.55.01
    db_name: HR92P16
    db_service_name: HR92P16
    db_host: psftdblnx1
    db_port: 1521
    connect_id: people
    connect_pwd: people
    domain_boot_user: PS
    domain_boot_user_pwd: **

  instance_3:
    label:       "PSFT HCM DB-Tier Linux 1"
    shape: oc2m
    os_type:     linux
    image_index: 0

    storage_attachments:
      storage_1:
         size: 150G

    hostname: psftdblnx1
    env_type: dbtier
    app_type: hcm
    psft_base: /u01/app/oracle/product
    db_name: HR92P16
    db_port: 1521
    connect_id: people
    connect_pwd: ******

  instance_4:
    label:       "PSFT HCM Mid-Tier Linux 1"
    shape:       oc2m
    os_type:     linux
    image_index: 0

    storage_attachments:
      storage_1:
         size: 150G

    hostname:    psftmtlnx1
    env_type:    midtier
    app_type: hcm
    psft_base:   /u01/app/oracle/product
    features:    pia,appsrv,batch
    tools_version: 8.55.01
    pia_http_port: 8000
    pia_https_port: 8443
    wsl_port: 7000
    jolt_port: 9000
    db_name: HR92P16
    db_service_name: HR92P16
    db_host: psftdblnx1
    db_port: 1521
    connect_id: people
    connect_pwd: ******
    domain_boot_user: PS
    domain_boot_user_pwd: **
    weblogic_admin_user: system
    weblogic_admin_pwd: **********
    webprofile_user_pwd: ***********
    gw_admin_user: administrator
    gw_admin_user_pwd:  ********

instance_5:
    label:       "PSFT HCM Full-Tier Linux 1"
    shape:       oc2m
    os_type:     linux
    image_index: 0

    storage_attachments:
      storage_1:
         size: 200G

    hostname:    psftftlnx1
    env_type:    fulltier
    app_type: hcm
    psft_base:   /u01/app/oracle/product
    tools_version: 8.55.01
    pia_http_port: 8000
    pia_https_port: 8443
    wsl_port: 7000
    jolt_port: 9000
    db_name: HR92P16
    db_service_name: HR92P16
    db_host: psftdblnx1
    db_port: 1521
    connect_id: people
    connect_pwd: ******
    domain_boot_user: PS
    domain_boot_user_pwd: **
    weblogic_admin_user: system
    weblogic_admin_pwd: **********
    webprofile_user_pwd: ***********
    gw_admin_user: administrator
    gw_admin_user_pwd: ********
    setup_ses: false

  instance_6:
    label:       "PSFT SES"
    shape:       oc4
    os_type:     linux
    image_index: 3
    
    hostname:    psftses112225
    env_type:    ses 
    
    storage_attachments:
      storage_1:
         size: 200G
    ses_port: 7777

• label is a name for this VM
• storage_attachments:  storage_1:  size defines the block storage created for this VM.
• hostname is the internal machine name for this VM.
• env_type defines the software that needs to be installed on this machine. Other env_type options are described below.
• features defines the configurations that need to be performed on this VM.
  
• psft_base is the location of the share file system.
• shape can be any shape supported by Oracle Cloud that defines the number of CPUs and memory. To see the list of supported shapes, sign in to the Oracle Compute Cloud Service console, and select Create Instance.
  
  Access the Image drop-down list, as shown in this example:
  

• File server
  In the example, instance_1 (env_type: fileserver) defines the file server for shared storage.
• Windows client
  In the example, instance_2 (env_type: psftclient) defines the Microsoft Windows client.
• Database server
  In the example, instance_3 (env_type: dbtier) defines the database tier. The database tier refers to the Oracle Database server, Oracle Database Client, and PeopleSoft application database.
• Middle tier system
  In the example, instance_4, (env_type: midtier) defines the mid-tier environment. A PeopleSoft mid-tier environment includes the Application Server, Process Scheduler, and web server domains, and the software required to deploy them, such as Oracle Tuxedo and Oracle WebLogic.
  For the env_type midtier additional properties are passed to the PeopleSoft DPK Puppet software to configure this environment. These names are self-explanatory for PeopleSoft administrators. For more information, see the PeopleSoft PeopleTools documentation on PeopleSoft Information Portal.
• Full tier system
  In the example, instance_5 (env_type: fulltier) defines a PeopleSoft full tier environment, which includes the Oracle database server and PeopleSoft application database along with PeopleSoft Application Server, Process Scheduler, and web server.
• SES
  In the example, instance_6 (env_type: ses) defines the Oracle SES configuration.
• Additional instances
  Include additional instances as needed, Process Scheduler, additional web servers, and so on.

This section uses scp and ssh file transfer commands.  The scp command is used to transfer files between systems. The ssh command is used to connect to a system or execute a command and return.

The scp and ssh commands given here assume that the private key is located under the on-premises user’s $HOME/.ssh directory and the public SSH keys are set up on the target machine. For this tutorial, the public key was added as part of the VM creation.

Note. If the private key is not in $HOME/.ssh the location can be specified using the option -i <identity_file>, where <identity_file> is the path to the file in which the SSH key pair was saved in the section Generating an SSH Key Pair on UNIX or UNIX-Like Systems Using ssh-keygen.

Use one of these formats for the scp command:

scp <file_to_upload> opc@<instance_ip_address>:/home/opc/<file_to_upload>
scp <file_to_upload> -i <identity_file> opc@<instance_ip_address>:/home/opc/<file_to_upload>

Use one of these formats for the ssh command:

ssh –t opc@<instance_ip_address>
ssh –t opc@<instance_ip_address> sudo sh <script_to_run>
ssh -i <identity_file> –t opc@<instance_ip_address>
ssh -i <identity_file> –t opc@<instance_ip_address> sudo sh <script_to_run>

To find the value for the instance IP address:

1. Log in to the Oracle Compute Cloud Service Console.
2. Select the Overview tab and then the Instances tile.
3. From the list of instances, identify the instance and click the instance name.
4. Note the Public IP address, which is 192.51.100.120 in this example.
   

1. Upload the psft_opc_setup.sh and download_opc.sh scripts to the Oracle Cloud VM with the scp command.
   

   /ds1/pt/cloud_files
   scp psft_opc_setup.sh opc@:192.51.100.120::/home/opc/psft_opc_setup.sh
   scp download_opc.sh opc@:192.51.100.120::/home/opc/download_opc.sh

2. Connect to the Oracle Cloud instance and provision the file server with the ssh command.
   

   ssh –t opc@192.51.100.120 sudo sh /home/opc/psft_opc_setup.sh

1. Use the ssh command to connect to the Oracle Cloud instance, using the IP address you noted in the section Understanding File Transfer Commands.
   

   ssh –t opc@192.51.100.120

2. Run the psft_opc_setup.sh utility.
   

   sudo sh /home/opc/psft_opc_setup.sh

3. Download the DPKs with the download_opc.sh utility.
   Note. The -l option refers to a space-separated list of files.
   

   cd /u01/app/oracle/product
   /home/opc/download_opc.sh –u a.b@example.com -d psftoowdemo -l "PT-DPK-LNX-8.55.01-1of2.zip PT-DPK-LNX-855.01-2of2.zip APP-DPK-HCM-LNX-92-8.55.01-1of2.zip APP-DPK-HCM-LNX-8.55-01-2of2.zip ODS-DPK-LNX-12.1.0.2-1of1.zip attach_repo.tgz" 

4. To verify that the files were downloaded correctly, after the downloading is complete, go to the directory where the DPKs are downloaded and compare the DPK sizes with the sizes of the DPKs from the Linux host.

COBOL is not required for PeopleSoft PeopleTools. For information on whether your PeopleSoft application requires COBOL, see PeopleSoft Enterprise Frequently Asked Questions about PeopleSoft and COBOL Compilers, My Oracle Support, Doc ID 747059.1.

See the tutorial Compiling PeopleSoft COBOL Programs on an Oracle Compute Cloud Service Instance.

The file server can act as an sftp server where the sftp users can be defined in the Oracle Compute Cloud Server. 

1. Run the following command to extract the attachments on the file server, which were created in the section Creating the Attachment Repository DPK (Optional), and uploaded in the section Uploading DPKs to Oracle Cloud Storage.
   

   tar -xvfz attach_repo.tgz

2. Identify the URL which needs to be changed using this SQL query:
   

   SELECT URL_ID,URL from PSURLDEFN

3. Log in to the PeopleSoft application.
4. Select PeopleTools, Administration, URLs.
5. Modify the identified URLs.