Setup the PeopleSoft Application and Web Tier

Set up the foundation for your middle tier architecture.

Set Up an OS Group and User

Create the OS group and user on all Oracle Linux middle tier compute instances.

  1. As root, create the oinstall group on all compute instances.
    # groupadd -g 1001 oinstall
  2. As root, create the OS user to be used by the PeopleSoft installation on all compute instances.
    # useradd --uid 1005 -g oinstall psadm2
  3. As root, modify the user to set up its home directory and default shell on all compute instances.
    # usermod -d /home/psadm2 -g oinstall -s /bin/bash psadm2

Configure OCI File Storage Service for Shared Homes

Mount your OCI File Storage file systems on each middle tier server, using the IP address for your file system.

  1. Log in as root, then create the /u01 and /u02 directories.
    # mkdir /u01
    # mkdir /u02
  2. Add entries to /etc/fstab directory using your OCI File Storage IP addresses.
    OCI-File-Storage-IP-Address:/export/psftapp  /u01        nfs        rw,rsize=131072,wsize=131072,bg,hard,timeo=600,nfsvers=3 0 0
    OCI-File-Storage-IP-Address:/export/psftinterface  /u02    nfs        rw,rsize=131072,wsize=131072,bg,hard,timeo=600,nfsvers=3 0 0
    
  3. Mount the file systems.
    # mount /u01
    # df -h /u01
    Filesystem                    Size  Used Avail Use% Mounted on
    10.0.103.224:/export/psftapp  8.0E  0G  8.0E   0% /u01
    # mount /u02
    # df -h /u02
    Filesystem                          Size  Used Avail Use% Mounted on
    10.0.103.224:/export/psftinterface  8.0E   11M  8.0E   1% /u02

Create the PeopleSoft Software Directory Structure

Except for MicroFocus COBOL, all software components are placed in a shared directory on OCI File Storage: /u01/app/psft/pt. PeopleSoft requires that you map several environment variables to this directory structure. In addition, there's one environment variable for custom scripts needed to automate startup, shutdown, and switchover activities.
  • Map the environment variables to the directory structure.
    Environment Variable Set to Purpose
    BASE_DIR /u01/app/psft Location used as the base for all PeopleSoft software install
    PS_HOME /u01/app/psft/pt/ps_home8.57.11 Location of PeooleTools
    PS_APP_HOME /u01/app/psft/pt/hcm_app_home Location of the PeopleSoft HCM application
    PS_CUST_HOME /u01/app/psft/pt/hcm_cust_home Location of customizations of the PeopleSoft application
    PS_CFG_HOME /peoplesoft/local/ps_config Location of node specific configuration and log files for PeopleSoft components such as application and process server domains under Oracle Tuxedo, and Oracle WebLogic log files.
    PS_FILEDIR /u01/app/psft/pt/ps_home8.57.11/file Location of integration and interface files such as XML or other file types.
    ORACLE_HOME /u01/app/psft/pt/oracle-client/19.3.0.0 Location of the Oracle client software installation
    TNS_ADMIN /u01/app/psft/pt/oracle-client/19.3.0.0/network/admin Location of the database client tnsnames.ora file for connecting to the PeopleSoft database.
    JAVA_HOME /u01/app/psft/pt/jdk1.8.0_221 Location of the Java install and Java run-time environment
    TUXDIR /u01/app/psft/pt/bea/tuxedo/tuxedo12.2.2.0.0 Location of the Oracle Tuxedo install.
    WLS_HOME /u01/app/psft/pt/bea/wlserver Location of the Oracle WebLogic server
    COBDIR /opt/MFCobol The installation directory for where MicroFocus (or Visual) Cobol is installed.
    SCRIPT_DIR /u01/app/psft/pt/custom_admin_scripts Location of administrative scripts created to manage the processes in this paper

Create PeopleSoft Directories for Multi-Node Deployments

Create the file system directories to hold the PeopleSoft configuration and infrastructure log files. When designing this implementation, we created local, non-shared file system directories on each middle tier VM to hold the PeopleSoft configuration and infrastructure log files. In each case, set PS_CFG_HOME to the local directory /peoplesoft/local/ps_config.

Everything else is shared and is copied over from the on-premises system. To do this, create the head of the installation directory path for the PeopleSoft software install on shared disk, then create the child psft_reports directory. The other child directories are created when we copy over the contents. You'll refresh the contents of all child directories when you do a final switchover to this environment from the on-premises systems.

  1. Log in as root user on one compute instance.
  2. Move to the /u01 directory.
    # cd /u01
  3. Create the directories.
    # mkdir -p app/psft/pt
  4. Create the directory for the report repository.
    # mkdir -p /u01/app/psft/pt/psft_reports/out
  5. Change ownership of the psft directories.
    # cd app
    # chown -R psadm2:oinstall psft

Setup the Host Environment on OCI Compute Instances

Before configuring the application server, process scheduler, and PeopleSoft Internet Architecture (PIA) web server domains, you must create an environment file for the user psadm2.

While most of the values are the same on each environment, you must set the ORACLE_HOSTNAME correctly for each server.

Note:

We have added a directory to hold new administrative scripts required by this project, and have created an export directive for the new directory as well as adding it to our path. We assume these scripts are in place and in the path when we describe actions later in this document.

The following is the environment file (psft.env) from one of our compute instances:

export ORACLE_HOSTNAME=iad-psft-hcm-app01
export BASE_DIR=/u01/app/psft
export PS_HOME=$BASE_DIR/pt/ps_home8.57.11
export PS_CFG_HOME=/peoplesoft/local/ps_config
export PS_APP_HOME=$BASE_DIR/pt/hcm_app_home
export PS_FILEDIR=$PS_HOME/file
export ORACLE_BASE=/u01/app/psft
export ORACLE_HOME=/u01/app/psft/pt/oracle-client/19.3.0.0
export COBDIR=/opt/MFCobol
export CLASSPATH=$CLASSPATH:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib
export TNS_ADMIN=$ORACLE_HOME/network/admin
export JAVA_HOME=/u01/app/psft/pt/jdk1.8.0_221
export TUXDIR=$BASE_DIR/pt/bea/tuxedo/tuxedo12.2.2.0.0
export NLSPATH=$TUXDIR/locale/C
export LD_LIBRARY_PATH=$TUXDIR/lib:$PS_HOME/bin:$ORACLE_HOME/lib:$COBDIR/lib:$LD_LIBRARY_PATH
export LIBPATH=$COBDIR/lib
export SHLIB_PATH=$SHLIB_PATH:$COBDIR/lib
export PATH=$ORACLE_HOME/bin:$TUXDIR/bin:$PS_HOME/jre/bin:$PS_HOME/bin:$JAVA_HOME/bin:$PATH
export PATH=$PATH:$COBDIR/bin
export PS_SERVER_CFG=$PS_HOME/appserv/prcs/HR92U033/psprcs.cfg
export WLS_HOME=$BASE_DIR/pt/bea/wlserver

# Add directory for custom scripts
export SCRIPT_DIR=$BASE_DIR/pt/custom_admin_scripts
export PATH=$PATH:$SCRIPT_DIR

# You must be in PS_HOME to execute the psconfig.sh script
cd $PS_HOME
./psconfig.sh
cd
  1. Place the environment script in psadm2’s home directory on each compute instance, making sure the ORACLE_HOSTNAME is set to that compute instance’s host name.
  2. Add execute permission to the file as the psadm2 user:
    $ chmod u+x psft.env
  3. Source the environment with the following command:
    $ . ./psft.env
  4. Modify psadm2’s .bash_profile script to call psft.env, to set up the environment automatically.
    This best practice is a requirement if you import the middle tiers into the PeopleSoft Cloud Manager.
Now that all OCI infrastructure and setup components are in place, you can migrate the PeopleSoft application to OCI.

Install MicroFocus COBOL

MicroFocus COBOL (Visual COBOL for later released versions) is a separately licensed software package that contains the COBOL compiler and run-time environment plus the run-time license manager. All compute instances that host the process scheduler (PRCS) must have the MicroFocus COBOL compiler, run-time environment, and license manager installed.

  1. Install MicroFocus COBOL compiler, run-time environment, and license manager on local file system on a compute instance.
    It is best practice to install them on local file system. These components are owned by the root user, and are often installed in either /usr/local/microfocus or /opt/microfocus. The instructions for installing these components are found in the MicroFocus COBOL README file.
  2. During the installation of the License Manager (mflman) and its database, answer Y when prompted “Should the License Manager be started on reboot” to ensure it is running every time the server is booted.
    The MicroFocus License Manager must be running for PeopleSoft COBOL programs to be compiled, linked, and allowed to run under the process scheduler.
  3. Repeat these steps for each compute instance that will host the process scheduler.