Installing PS_HOME Only on Linux

This procedure assumes you have obtained the four PeopleSoft PeopleTools DPK zip files and saved them in DPK_INSTALL.

If you are installing the PeopleSoft environment as a non-root user, ensure that you fulfill the prerequisites in the section Deploying as a Non-Root User on Linux.

To use the DPK setup script to install PS_HOME only:

Extract the first zip file (FILENAME_1of4.zip) in the same directory, DPK_INSTALL.

The extraction creates the DPK_INSTALL/setup directory and other files.

Note:

It is important that you retain the DPK_INSTALL/setup directory, even after deploying, because it holds the DPK setup script, which must be used for both deploying an environment and cleanup of deployed environment.

See Obtaining the PeopleSoft PeopleTools DPKs for the DPK file name syntax.
Open a terminal window and change directory to DPK_INSTALL/setup.
As a user with root access, run the script with the options for mid-tier and deployment only.
```
psft-dpk-setup.sh –-env_type midtier --deploy_only --deploy_type tools_home
```
Wait while the script locates the valid PeopleSoft zip files and extracts them.

The system displays messages indicating the steps in the setup process. The success or failure of each step is indicated by [ OK ] or [FAILED].
```
Starting the PeopleSoft Environment Setup Process:
Validating User Arguments:                                   [  OK  ]
Validating PeopleSoft Supported Platform:                    [  OK  ]
```
At the following prompt, enter the full path to a location that is accessible to the host to be used as the PeopleSoft base directory.

The base directory is used to extract the PeopleSoft DPKs as well as for deploying PeopleSoft components.

Note:

When entering the path for the base directory, use forward slashes (/). For example, /cs1/psft. Do not use a name for the base directory that begins with a number. Do not end the base directory name with a forward slash (for example, do not enter /ds1/psft/).
```
The base directory is used to extract the PeopleSoft DPKs. It is also
used to deploy the PeopleSoft components. This directory should be
accessible, must have write permission and should have enough 
free space.

Enter the full path for the PeopleSoft Base Directory [/opt/oracle/psft]: 
Are you happy with your answer? [Y|n|q]:     
```
The script validates if there is enough free space available under the specified base directory for the PeopleSoft environment. The PeopleSoft environment setup is aborted if there is not enough free space.

The script creates the following sub-directories under the user provided base directory, BASE_DIR:
- BASE_DIR/db
  
  This directory is not used for this deployment.
- BASE_DIR/dpk
  
  The script uses this directory to extract the archives from the PeopleSoft DPKs.
- BASE_DIR/psft_puppet_agent
  
  The script uses this directory to install Puppet software.
- BASE_DIR/pt
  
  The script uses this directory to deploy PeopleSoft PeopleTools.
Review the status messages as the script validates the files found in DPK_INSTALL and extracts the archives from the DPKs.

The script carries out validations for the mid-tier deployment. If any of the validations fail, the PeopleSoft environment setup is aborted.

Note:

The messages have been truncated for brevity.
```
Validating the PeopleSoft DPKs in the directory:
[...]
Extracting the DPK Archives in the VM:
[...]
```

Review the status messages.

The script installs Puppet software, verifies if the DPKs are available in DPK_INSTALL, and checks for available space. It aborts with the message [FAILED] in case of errors.

Installing PSFT Relocatable Puppet Software in the base directory:
[  OK  ]
Installing eYAML Hiera Backend on this host:                [  OK  ]
Checking if PeopleSoft DPKs are Present:                    [  OK  ]
Checking if the Base Directory has Enough Free Space:       [  OK  ]

Review the status messages as the script sets up the Puppet file system.

The script sets up Puppet on the host. It then copies the PeopleSoft Puppet modules to the standard location (BASE_DIR/dpk) and updates the YAML files to reflect the type of PeopleSoft environment setup.
```
Setting up Puppet on the VM:
Generating eYAML Hiera Backend Encryption Keys:             [  OK  ]
Updating the Puppet Hiera YAML Files in the Linux VM:       [  OK  ]
Updating the Role in Puppet Site File for the Linux VM:     [  OK  ]
```
Specify the information for your database platform.
1. For the database platform, enter ORACLE. or just press ENTER.
```
Enter the PeopleSoft database platform [ORACLE]:
```
2. Enter y (yes) to indicate that the database you are connecting to is a Unicode database.
  
  Note:
  
  All PeopleSoft Update Image databases are required to be Unicode.
```
Is the PeopleSoft database unicode? [Y|n]: y
```

Enter y to continue with the script.

Are you happy with your answers? [y|n]: y
Updating the Puppet Hiera YAML Files with User Data:      [  OK  ]

If you want to continue running the initialization script using the default configuration, answer y (yes) to the following prompt, and continue with the next step.

If you want to customize the PeopleSoft environment using the Puppet YAML files, answer n (no) to stop the script.

The bootstrap script is ready to deploy and configure the PeopleSoft
environment using the default configuration defined in the Puppet
Hiera YAML files. You can proceed by answering 'y' at the following
prompt. And, if you want to customize the environment by overriding
the default configuration, you can answer 'n'. If you answer 'n', you
should follow the instructions in the PeopleSoft Installation Guide
for creating the Hiera YAML file 'psft_customizations.yaml' 
and running the psft_puppet_apply script to continue with 
the setup of the PeopleSoft environment.

Do you want to continue with the default initialization process? [y|n]:

Review the status messages as the script runs Puppet profiles to set up the PeopleSoft environment.

A message of [ OK ] indicates that the profile has been applied successfully while a message [FAILED] indicates that the profile application failed.

The script stops and exits the first time a profile application fails, and displays an error message. This example shows the error message after the first step failed:
```
Starting the Default Initialization of PeopleSoft Environment:

Deploying PeopleTools Components:                           [FAILED]
The initialization of PeopleSoft environment setup failed. Check the
log file [/opt/DPK_INSTALL/setup/psft_dpk_setup.log] for the errors.
After correcting the errors, run the following commands to continue
with the setup of PeopleSoft environment.

From the shell, run /opt/oracle/psft/psft_puppet_apply.sh

Exiting the PeopleSoft environment setup process.
```
See "Completing the DPK Initialization with Customizations."

Upon successful completion, the DPK setup script displays the following message:
```
Starting the Default Initialization of PeopleSoft Environment:

Deploying PeopleTools Components:                           [  OK  ]
Setting up PeopleSoft OS Users Environment:                 [  OK  ]

The PeopleSoft Environment Setup Process Ended.
```
The complete setup log is written to the file psft_dpk_setup.log in the same location as the DPK setup script.

If you are running as a non-root user, the setup.log is written to the file <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