Running the DPK Setup Script for the PIA Domain Deployment on Microsoft Windows

This procedure to deploy a single PIA domain assumes that you have obtained the four PeopleSoft PeopleTools DPK zip files and saved them in DPK_INSTALL.

Note:

Some of the informational script messages have been omitted for brevity.

Extract the first zip file (FILENAME_1ofn.zip).

Note:

It is a good idea to extract into the same directory where you downloaded the zip files, DPK_INSTALL.

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.

The extraction creates the DPK_INSTALL/setup directory and other files.
Open a command prompt with Run as Administrator.
Change directory to DPK_INSTALL/setup.
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.bat --env_type midtier --domain_type pia
```
- If you extracted the first zip file into a different directory, include the option dpk_src_dir to specify the location of the downloaded zip files, such as DPK_INSTALL, as follows:
```
psft-dpk-setup.bat --dpk_src_dir DPK_INSTALL --env_type midtier ⇒
--domain_type pia
```
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, C:/psft. Do not use a base directory name that begins with a number.
```
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 the 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.
```
Checking if the Base directory has Enough Free Space:         [  OK  ]
```
Specify the type of database platform.

Enter MSSQL for Microsoft SQL Server or ORACLE.
```
Enter the PeopleSoft database platform [ORACLE]: 
```
Specify whether you want a Unicode database.
```
Is the PeopleSoft database unicode? [Y|n]:
```
Enter the database name.
```
Enter the PeopleSoft database name:
```
If your database platform is Oracle, enter the database service name.

The default is the same as the database name. Do not enter an IP address.
```
Enter the PeopleSoft database service name [PSFT92DB]:
```
Enter the name of the host where the database is installed.

Do not enter an IP address.
```
Enter the PeopleSoft database host name:
```
If your database platform is Oracle, enter the database listener port number:
```
Enter the PeopleSoft database port [1521]:
```
If your database platform is Microsoft SQL Server, enter the database server name.
```
Enter the PeopleSoft database server name:
```
If your database platform is Microsoft SQL Server, enter the ODBC driver name.
```
Enter Microsoft SQL Server ODBC Name["ODBC Driver 17 for SQL Server"]:
```
If you want to change to a different version, enter the text without double quotes; for example:
```
Enter Microsoft SQL Server ODBC Name["ODBC Driver 17 for SQL Server"]:ODBC Driver 18 for SQL Server
```
Enter the PeopleSoft Connect ID at the following prompt:

The default is people.
```
Enter the PeopleSoft database Connect ID [people]:
```
Enter a password for the PeopleSoft Connect ID, and enter again on the next line, at the following prompt.

See E-DPK - PeopleTools 8.59 and later - DPK setup does not support some special characters for passwords, My Oracle Support, Article ID KB300834.
```
Enter the PeopleSoft database Connect ID [people] password.
Ensure that the password meets the length and complexity requirements
for your database platform:
Re-Enter the PeopleSoft database Connect ID password:
```
Enter the PeopleSoft user ID (operator ID), such as PS or VP1.
```
Enter the PeopleSoft database Operator ID [VP1]:
```

Enter the password twice for the PeopleSoft operator ID.

Enter the PeopleSoft database Operator ID [VP1] password.
Ensure that the password is between 1 and 32 characters in length.
You may include these special characters !@#$%^& :
Re-Enter the PeopleSoft database Operator ID password:

Enter the Application Server Domain Connection password, following the guidelines in the prompt.

Note:

This is an optional password. If no password is entered, the connection between Web Server and Application Server will not be password protected.

[Optional] Enter a new Application Server Domain connection password.
Ensure that the password is between 8 and 30 characters in length.
You may include these special characters !@#$%^& :
Re-Enter the Application Server Domain connection password:

Enter the password for the PTWEBSERVER web profile user at the following prompt:

Enter a new PeopleSoft WebProfile user [PTWEBSERVER] password. Ensure
the password is between 8 and 32 characters in length.
You may include these special characters !@#$%^& :
Re-Enter the PeopleSoft WebProfile user password:

Enter the Oracle WebLogic Server Admin password, following the guidelines in the prompt.

The default Oracle WebLogic server administrator is system. The window does not display masking characters as you type. There is no default password.

Enter a new WebLogic Server Admin user [system] password. 
Ensure that the password is between 8 and 30 characters in length
with at least one lowercase letter and one uppercase letter. It must also
contain one number or one of these special characters !@#$%^& :

Re-Enter the WebLogic Server Admin user password:

Enter the Integration Gateway user ID and password at the following prompt.

The default user ID is administrator.

Enter the PeopleSoft Integration Gateway user [administrator]:
Enter the PeopleSoft Integration Gateway user [administrator] password. 
Ensure that the password is between 8 and 30 characters in length:.
You may include these special characters !@#$%^& :
Re-Enter the PeopleSoft Integration Gateway user password:

Enter the Integration Gateway keystore password.

Enter the SSL Keystore password, which is required for web servers and Integration Broker gateways in SSL-enabled environments. The password you enter is used for the default keystore. If you need to reset the password, use the pskeymanager utility.

See PeopleTools: System and Server Administration, "Implementing WebLogic SSL Keys and Certificates."

See PeopleTools: Integration Broker Administration, "Configuring Security and General Properties."
```
Enter the PeopleSoft Integration Gateway Keystore password. Ensure
the password is between 8 and 30 characters in length.
You may include these special characters !@#$%^& :
Re-Enter the PeopleSoft Integration Gateway Keystore password:
```
Enter the Application Server Domain Connections string, in the format <Server_name>:<Port>.

To specify the Application Server Domain Connect string, enter the application server name and a colon, followed by the Jolt port that the PIA domain connects to. For example, psftserver:9000.

See PeopleTools: System and Server Administration, "Configuring Jolt Failover and Load Balancing."

See PeopleTools: System and Server Administration, "Configuring SSL for Workstation Listener and Jolt Listener."
```
Enter the Application Server Domain Connections String:
```
Enter the name of the server with the Process Scheduler domain.
```
Enter the Process Scheduler Domain Server Name:
```
When you run the DPK setup script with default initialization, the Process Scheduler domain server name is PRCSxxxx, where xxx is a random number. On a host where Process Scheduler has been deployed, you can find the Process Scheduler domain server name (PrcsServerName) in the Process Scheduler configuration file. Locate it in <PS_CFG_HOME>/appserv/prcs/<Domain name>/psprcs.cfg, under General settings for the Process Scheduler.

For example:
```
;====================================================================
; General settings for the Process Scheduler
;====================================================================
PrcsServerName=PRCS8783
```

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.