Running the DPK Setup Script as a Non-Root User to Install Mid-Tier Software on Linux
To install the mid-tier software as a non-root user:
Note:
Some of the informational script messages have been omitted for brevity.
-
Open a terminal window as a non-root user.
-
Change directory to DPK_INSTALL/setup.
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.
-
Run the script as follows:
-
If you extracted the first zip file into the same directory where you downloaded the zip files, use this command:
./psft-dpk-setup.sh --env_type midtier --deploy_only -
If you extracted the first zip file into a different directory, include the option
dpk_src_dirto specify the location of the downloaded zip files, such as DPK_INSTALL, as follows:./psft-dpk-setup.sh --dpk_src_dir DPK_INSTALL --env_type midtier ⇒ --deploy_only
-
-
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, referred to here as BASE_DIR.
The base directory is used to extract the DPKs as well as for deploying PeopleSoft components. The script creates the base directory if it does not exist.
Use forward slashes only (/) when specifying the base directory; for example, /home/psft. Do not use a base directory name 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: Are you happy with your answer? [Y|n|q]:The script installs Puppet software and 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.
Note:
A mid-tier setup of a PeopleSoft environment requires about 25 GB of disk space.
-
Specify the type of database platform.
Enter MSSQL for Microsoft SQL Server or ORACLE.
Enter the PeopleSoft database platform [ORACLE]: -
Specify whether you want support for a Unicode database.
Is the PeopleSoft database unicode? [Y|n]: -
Enter y to continue with the script.
Are you happy with your answers? [y|n]: y Encrypting the Passwords in the User Data: [ OK ] 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.
Upon successful completion, the DPK setup script displays the following message:
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.