Preparing to Run the DPK Setup Script
Include the following decisions in preparing to install with the DPK setup script:
-
Non-root deployment
On Linux, you have the option to deploy the PeopleSoft environment as a non-root user.
See Preparing to Run the DPK Setup Script as a Non-Root User on Linux
-
Default or manual configuration
After extracting the DPKs, you are given the option to exit the process, create a customization file, and complete the configuration manually using the psft_puppet_apply script with a user-written customization file. Use the manual configuration if you want to change installation locations and so on.
See "Completing the DPK Initialization with Customizations."
-
User IDs and password
The DPK setup process does not include any default passwords. There are default users in some cases, which are included in the prompts. You must provide user IDs and passwords, as determined by the type of deployment.
The restrictions for special characters are listed in the following article.
See E-DPK - PeopleTools 8.59 and later - DPK setup does not support some special characters for passwords (My Oracle Support, Article ID KB300834).
The DPK setup script prompts for the following user IDs and passwords:
-
Unicode or non-Unicode
While running the DPK setup script, you can choose to install a Unicode or non-Unicode environment.
Alternatively, specify Unicode using the customizations and psft_puppet_apply script.
See "Completing the DPK Initialization with Customizations," Preparing the Customization File for Unicode.
-
Specifying PS_CUST_HOME
You may wish to set up a PS_CUST_HOME (PeopleSoft Customization Home) directory in your environment to store your site's customized files, separate from PS_HOME and PS_APP_HOME. If you wish to use a PS_CUST_HOME for your environment, you must perform the deployment using the DPK customizations, and specify the PS_CUST_HOME location.
See "Completing the DPK Initialization with Customizations," Preparing the Customization File for the PeopleSoft Homes.