Preparing to Run the DPK Setup Script as a Non-Root User on Linux

Review the information in this section before deploying on Linux. You have the option of downloading the DPK zip files and deploying the PeopleSoft environment as a non-root user.

To run the DPK setup script as a non-root user, fulfill the following requirements:

  • You can use an existing non-root user account. It is not necessary to create a new user.

  • The deployment supports only a single non-root user who deploys into a single BASE_DIR.

  • The non-root user’s home directory must be writable.

  • The non-root user must be configured to use the Bash, Bourne, or Korn shell.

  • The non-root user must have permission to read and execute the DPK_INSTALL folder and its contents, including the downloaded zip files, and DPK_INSTALL/setup.

    If the root user downloads the DPK zip files and saves them in DPK_INSTALL, the root user must ensure that the necessary permissions are granted to allow the non-root user to read and execute the files.

  • The non-root user must be a member of the oinstall group, and oinstall must be the primary group for the user.

    See Database Installation Guide for Linux, Identifying an Oracle Software Owner User Account, https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/identifying-an-oracle-software-owner-user-account.html.

  • Before a non-root user deploys the PeopleSoft environment, the root user must perform a prerequisite task.

  • For a full-tier or mid-tier deployment, the root user must run the DPK setup script with the --prereq option to check the contents and permissions for the Oracle central inventory file and perform any actions required for the Oracle 19c Database Server and Database Client installation.

    See "Preparing for Installation," Reviewing the Oracle Central Inventory File Location and Permissions on Linux.

After the non-root user completes the deployment:

  • The non-root user owns all of the deployed environment, including PS_HOME and PS_CFG_HOME.

  • The log files for the non-root deployment are saved in <USER_HOME>/psft_dpk_work/psft_dpk_setup_<PID>.log, where <USER_HOME> is the home directory for the user running the script, and <PID> is a process ID.

    For example, if the home directory for the root user is /root, when the root user runs the command ./psft-dpk-setup.sh --prereq, the log file is /root/psft_dpk_work/psft_dpk_setup_1234.log.

    For example, if the home directory for the non-root user is /home/psft_user, when the non-root user runs ./psft-dpk-setup.sh --midtier, or another deployment command, the log file is /home/psft_user/psft_dpk_work/psft_dpk_setup_5678.log.

  • If a non-root user reboots the Linux system after a mid-tier or full-tier deployment, the PeopleSoft domains (Application Server, Process Scheduler, web server) will not be restarted. This is because there are no Linux systemd services installed for a non-root user. The systemd services require root access.

The following table lists the high-level steps required to deploy a PeopleSoft environment by a non-root user, with a root user performing a prerequisite step. The table uses a mid-tier deployment as an example, but the process also applies to other deployments, such as deploying full-tier, or deploying PeopleSoft domains only, and so on.

Note:

The commands in the table include line feeds to improve readability.

Step Reference Comment

1. Obtain DPKs and extract the first zip file.

Obtaining the PeopleSoft PeopleTools DPKs

NA

2. Select and run one or more prerequisite commands.

Running the DPK Setup Prerequisite Step for Linux

Important: This step must be run by the root user.

This action is required once for each host.

3. Run the DPK setup script. For example, to deploy a mid-tier environment:

./psft-dpk-setup.sh 
--env_type midtier

Running the DPK Setup Script as a Non-Root User on Linux

For other deployment options, see the table in the section Using the DPK Setup Script Options.

4. Run the post-configuration command.

./psft-dpk-setup.sh
--postcfg 
--psft_base_dir 
BASE_DIR

Running the DPK Setup Script as a Non-Root User on Linux

Important: This step must be run by the root user.

5. If necessary, run the cleanup command.

./psft-dpk-setup.sh 
--cleanup

“Using and Maintaining the PeopleSoft Environment,” Using the DPK Setup Script to Remove the PeopleSoft Environment on Linux as a Non-Root User

Run cleanup of the environment (optional).

6. Source the script to set environment variables:

source BASE_DIR/pt/psft_env.sh

“Using and Maintaining the PeopleSoft Environment,” Setting Environment Variables for the Non-Root User on Linux

Before using PeopleSoft utilities and programs, source the script to set the required environment variables.