Running with the Mid-Tier Option on Microsoft Windows

To deploy mid-tier components on physical or virtual Microsoft Windows hosts:

Extract the first zip file, FILENAME_1ofn.zip.

It is recommended that you extract into the same directory where you downloaded the zip file, 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.
Open a command prompt window with Run as Administrator.
Change directory to the location where you extracted the first zip file, DPK_INSTALL/setup.
Run the script with the mid-tier option to set up the Application Server, PIA, and web server mid-tier components.
- 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
```
- 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.
```
psft-dpk-setup.bat --dpk_src_dir DPK_INSTALL –-env_type midtier
```
Note:

Running the DPK setup script with the --env_type midtier option deploys all servers. If you want to deploy one of the servers (application server, Process Scheduler server, PIA, or application server and Process Scheduler server) see the command options in “Installing the PeopleSoft Homes,” Reviewing the DPK Setup Script Options.
Wait while the script begins the setup process.

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. The script creates the directory if it is not present.

Note:

When entering the path for the base directory, use forward slashes (/). For example, C:/psft. Enclose any names with special characters in double quotes. Do not use a name for the base directory that begins with a number. Confirm your choice or change it if necessary.
```
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: C:/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.

Note:

A mid-tier setup of a PeopleSoft environment requires about 25 GB of disk 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 a mid-tier deployment.
- BASE_DIR\dpk
  
  The script uses this directory to extract the archives from the PeopleSoft DPKs, and contains the Puppet YAML files for the deployment.
- BASE_DIR\psft_puppet_agent
  
  This script uses this directory to install Puppet software.
- BASE_DIR\pt
  
  The script uses this directory to deploy PeopleSoft components.

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 validates the files found in DPK_INSTALL and extracts the DPK archives.

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

After the script completes the extraction, it deletes the original files. Make a backup copy if you want to keep them.

See Obtaining the PeopleSoft PeopleTools DPKs, for the filename syntax of the DPK zip files

Note:

The messages have been truncated for brevity.
```
Validating the PeopleSoft DPKs in the Windows Host:
[...]
Extracting the PeopleSoft DPK Archives in the Windows Host:
[...]
```
Review the status messages as the script sets up the Puppet file system.

The script sets up Puppet on the host or VM. It then copies the PeopleSoft Puppet modules to the standard location under the base directory (BASE_DIR\dpk) and updates the YAML files to reflect the type of PeopleSoft environment setup.
```
Setting up Puppet on the Windows Host:
Generating eYAML Hiera Backend Encryption Keys:              [  OK  ]
Updating the Puppet Hiera YAML Files in the Windows Host:    [  OK  ]
Updating the Role in Puppet Site File for the Windows Host:  [  OK  ]
```
Specify the installation type.

Confirm your choice or change it if necessary.
```
Enter the PeopleSoft installation [PUM or FRESH] type [PUM]: FRESH
Are you happy with your answer? [y|n]: 
```
Note:

You see this prompt only when PeopleSoft application DPKs that were built on the same PeopleTools release, are present in DPK_INSTALL.
Specify the information for the database that you want to connect to.
1. For the database platform, enter ORACLE or MSSQL (Microsoft SQL Server).
```
Enter the PeopleSoft database platform [ORACLE]:
```
2. Enter y (yes) if the database you are connecting to is a Unicode database, or n (no) for a non-Unicode database.
```
Is the PeopleSoft database unicode? [Y|n]:
```
3. Enter y (yes) if you want to install the files needed for multi-language support.
  
  Note:
  
  You see this prompt only when PeopleSoft application DPKs that were built on the same PeopleTools release, are present in DPK_INSTALL.
```
Do you want Multi Language support in PeopleSoft database? [y|N]:
```
4. Enter the database name.
  
  If the database name includes non-alphanumeric characters such as periods, enclose the name in double quotes. For example, “HCM.92”.
```
Enter a new PeopleSoft database name. Ensure that the database
name start with a letter and contains only uppercase letters and
numbers and is no more than 8 characters in length [HCM92]:
```
5. For a Microsoft SQL Server database, enter the database server name, for example, server.example.com\sql2022.
```
Enter the PeopleSoft database server name: server.example.com\sql2022
```
6. For a Microsoft SQL Server database, 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
```
7. Enter the database service name.
  
  Note:
  
  The service name is required for Oracle RDBMS.
  
  For the service name, enter the full name, including the domain, if the database was installed with the domain. Use forward slashes if necessary. If the service name includes non-alphanumeric characters such as periods, enclose the name in double quotes. For example, “HCM.92.example.com”. Do not enter an IP address.
```
Enter the PeopleSoft database service name [HCM92]:
```
8. Enter the name of the host where the database is installed, and the port number:
  
  Use forward slashes if necessary. If the host name includes non-alphanumeric characters such as periods, enclose the name in double quotes. For example, “host.example.com”. Do not enter an IP address.
```
Enter the PeopleSoft database host name:
Enter the PeopleSoft database port [1521]: 
```
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 Connect ID password:
```
Enter the PeopleSoft Operator ID (user ID) at the next prompt:
```
Enter the PeopleSoft database Operator ID [PS]: 
```

Enter the password twice for the PeopleSoft operator ID, such as PS or VP1.

Enter a new PeopleSoft database Operator ID [PS] password. 
Ensure that the password is between 1 and 32 characters in length.
You may include these special characters !@#$%^& : 
Re-Enter the PeopleSoft 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.

Enter a new PeopleSoft Web Profile user [PTWEBSERVER] password. 
Ensure that the password is between 8 and 32 characters in length.
You may include these special characters !@#$%^& :
Re-Enter the PeopleSoft Web Profile 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 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.

This is 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:
```
If you want to change any of the answers to the previous questions, enter n (no) at the following prompt, or enter y (yes) to continue:
```
Are you happy with your answers? [y|n]:
```

Review the status messages as the script updates the Puppet YAML files with the user input.

Encrypting the Passwords in the User Data:                  [  OK  ]
Updating the Puppet Hiera YAML Files with User Data:        [  OK  ]

Answer n (no) to indicate that you do not want to continue running the initialization script using the default configuration.

The script stops. Follow the instructions for using customizations for mid-tier connectivity to complete the mid-tier deployment.

See "Completing the DPK Initialization with Customizations."

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]: n

You have decided not to continue with the default PeopleSoft environment
setup process. Any customizations to the PeopleSoft environment 
should be done in the Hiera YAML file 'psft_customizations.yaml' 
and place it under [c:\psft\dpk\puppet\production\data] directory. 
After making the necessary customizations, run the following 
script to continue with the setup of PeopleSoft environment.

Start a cmd window as Administrator and run C:\psft\psft_puppet_apply.cmd

Exiting the PeopleSoft environment setup process.

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.

Note:

If you select the default initialization process, the PeopleSoft environment is created with one Application Server domain, one Process Scheduler domain, and one PIA domain.

If you want to customize the PeopleSoft environment, answer n (no) to stop the script. You must use customizations to complete the mid-tier deployment.

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 [C:\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.

Start a cmd window as Administrator and run C:\psft\psft_puppet_apply.cmd

Exiting the PeopleSoft environment setup process.

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  ]
Setting up PeopleSoft Application Server Domain:            [  OK  ]
Setting up PeopleSoft Process Scheduler Domain:             [  OK  ]
Setting up PeopleSoft PIA Domain:                           [  OK  ]
Changing the Passwords for the Environment:                 [  OK  ]
Configuring Pre-Boot PeopleSoft Environment:                [  OK  ]
Starting PeopleSoft Domains:                                [  OK  ]
Configuring Post-Boot PeopleSoft Environment:               [  OK  ]
Setting up Source Details for PeopleTools Client:           [  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.