PeopleSoft PeopleTools 8.57 Deployment Packages Installation

PeopleSoft PeopleTools 8.57

Deployment Packages Installation

May 2019

This software and related documentation are provided under a license agreement containing restrictions on use

and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license

agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit,

distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering,

disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you

find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on

behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any

programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are

"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific

supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs,

including any operating system, integrated software, any programs installed on the hardware, and/or

documentation, shall be subject to license terms and license restrictions applicable to the programs. No other

rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is

not developed or intended for use in any inherently dangerous applications, including applications that may create

a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be

responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle

Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in

dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their

respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are

used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the

AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices.

UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and

services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all

warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an

applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any

loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as

set forth in an applicable agreement between you and Oracle.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For

information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Contents

Preface

About this Documentation ..................................................................................................................................... 9

Understanding This Documentation ........................................................................................................................ 9

Audience .................................................................................................................................................................. 9

Typographical Conventions ................................................................................................................................... 10

Products .................................................................................................................................................................. 11

Related Information ............................................................................................................................................... 12

Comments and Suggestions ................................................................................................................................... 12

Chapter 1

Prerequisites ......................................................................................................................................................... 13

Understanding the PeopleSoft PeopleTools Deployment Packages ...................................................................... 13

Reviewing Hardware Requirements ...................................................................................................................... 14

Reviewing Hardware Requirements for Microsoft Windows .......................................................................... 14

Reviewing Hardware Requirements on AIX, HP-UX, Linux, or Solaris ......................................................... 15

Reviewing Software Requirements ........................................................................................................................ 16

Reviewing Software Requirements on Microsoft Windows ............................................................................ 16

Reviewing Software Requirements on Linux ................................................................................................... 17

Reviewing Software Requirements on AIX ..................................................................................................... 17

Reviewing Software Requirements on HP-UX ................................................................................................ 18

Reviewing Software Requirements on Solaris ................................................................................................. 20

Reviewing Requirements for the Puppet Software on Microsoft Windows ..................................................... 20

Reviewing Requirements for the Puppet Software on Linux ........................................................................... 21

Reviewing Requirements for the Puppet Software on AIX .............................................................................. 22

Reviewing Requirements for the Puppet Software on HP-UX ......................................................................... 23

Reviewing Requirements for the Puppet Software on Solaris .......................................................................... 25

Cataloging the Database for DB2 LUW or DB2 z/OS .......................................................................................... 26

Reviewing the System Parameters on Linux, AIX, HP-UX, or Solaris ................................................................. 26

Understanding the System Parameters on Linux, AIX, HP-UX, or Solaris ..................................................... 26

Reviewing the sysctl Parameters ...................................................................................................................... 26

Reviewing the ulimit Parameters ...................................................................................................................... 27

Chapter 2

Deploying the PeopleSoft PeopleTools Deployment Packages ......................................................................... 29

Obtaining the PeopleSoft PeopleTools DPKs ........................................................................................................ 29

Contents

Obtaining the PeopleSoft PeopleTools DPKs from My Oracle Support .......................................................... 29

Obtaining the PeopleSoft PeopleTools DPKs from Oracle Software Delivery Cloud ..................................... 30

Reviewing the PeopleSoft PeopleTools DPKs ................................................................................................. 30

Reviewing the DPK Setup Script Options ............................................................................................................. 31

Using the DPK Setup Script Options ................................................................................................................ 31

Preparing to Run the DPK Setup Script ............................................................................................................ 34

Deploying as a Non-Root User on Linux, AIX, HP-UX, or Solaris ...................................................................... 35

Preparing to Run the DPK Setup Script as a Non-Root User on Linux, AIX, HP-UX, or Solaris ................... 35

Running the DPK Setup Prerequisite for Linux, AIX, HP-UX, or Solaris ....................................................... 36

Running the DPK Setup Script as a Non-Root User on Linux, AIX, HP-UX, or Solaris ................................ 38

Running the DPK Setup Script for Mid-Tier Deployment .................................................................................... 38

Understanding the Mid-Tier Deployment ......................................................................................................... 38

Prerequisites ...................................................................................................................................................... 39

Running with the Mid-Tier Option on Microsoft Windows ............................................................................. 40

Running with the Mid-Tier Option on Linux, AIX, HP-UX, or Solaris as the Root User ............................... 47

Running with the Mid-Tier Option on Linux, AIX, HP-UX, or Solaris as a Non-Root User .......................... 54

Running the DPK Setup Script to Install Mid-Tier Software Only ....................................................................... 60

Understanding the Mid-Tier Software Installation ........................................................................................... 60

Running the DPK Setup Script to Install Mid-Tier Software on Microsoft Windows ..................................... 61

Running the DPK Setup Script as the Root User to Install Mid-tier Software on Linux, AIX, HP-UX, or

Solaris ............................................................................................................................................................... 63

Running the DPK Setup Script as a Non-Root User to Install Mid-Tier Software on Linux, AIX, HP-UX, or

Solaris ............................................................................................................................................................... 65

Running the DPK Setup Script to Deploy an Application Server Domain ............................................................ 67

Understanding the Application Server Domain Deployment ........................................................................... 67

Running the DPK Setup Script for the Application Server Domain Deployment on Microsoft Windows ...... 68

Running the DPK Setup Script for the Application Server Domain Deployment on Linux, AIX, HP-UX, or

Solaris as the Root User .................................................................................................................................... 71

Running the DPK Setup Script for the Application Server Domain Deployment on Linux, AIX, HP-UX, or

Solaris as a Non-Root User ............................................................................................................................... 75

Running the DPK Setup Script to Deploy a Process Scheduler Domain ............................................................... 78

Understanding the Process Scheduler Domain Deployment ............................................................................ 78

Running the DPK Setup Script for the Process Scheduler Domain Deployment on Microsoft Windows ....... 79

Running the DPK Setup Script for the Process Scheduler Domain Deployment on Linux, AIX, HP-UX, or

Solaris as the Root User .................................................................................................................................... 82

Running the DPK Setup Script for the Process Scheduler Domain Deployment on Linux, AIX, HP-UX, or

Solaris as a Non-Root User ............................................................................................................................... 85

Running the DPK Setup Script to Deploy an Application Server and a Process Scheduler Domain .................... 88

Understanding the Application Server and Process Scheduler Domain Deployment ...................................... 89

Running the DPK Setup Script for the Application Server and Process Scheduler Domain Deployment on

Microsoft Windows .......................................................................................................................................... 89

Running the DPK Setup Script for the Application Server and Process Scheduler Domain Deployment on

Linux, AIX, HP-UX, or Solaris as the Root User ............................................................................................. 93

Running the DPK Setup Script for the Application Server and Process Scheduler Domain Deployment on

Contents

Linux, AIX, HP-UX, or Solaris as a Non-Root User ........................................................................................ 96

Running the DPK Setup Script to Deploy a PIA Domain ..................................................................................... 99

Understanding the PIA Domain Deployment ................................................................................................. 100

Prerequisites for the PIA Domain Deployment .............................................................................................. 100

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

Running the DPK Setup Script for the PIA Domain Deployment on Linux, AIX, HP-UX, or Solaris as the

Root User ........................................................................................................................................................ 105

Running the DPK Setup Script for the PIA Domain Deployment on Linux, AIX, HP-UX, or Solaris as a Non-

Root User ........................................................................................................................................................ 109

Running the DPK Setup Script to Install PS_HOME Only ................................................................................. 113

Understanding the PS_HOME Deployment ................................................................................................... 113

Installing PS_HOME Only on Microsoft Windows ....................................................................................... 114

Installing PS_HOME Only on Linux, AIX, HP-UX, or Solaris ..................................................................... 117

Obtaining Operating System Packages Required by Puppet ............................................................................... 121

Deploying the PeopleTools Client DPK .............................................................................................................. 121

Understanding the Standalone Mode Deployment ......................................................................................... 121

Preparing for the PeopleTools Client DPK Deployment ................................................................................ 122

Deploying in Standalone Mode ...................................................................................................................... 122

Chapter 3

Completing the DPK Initialization with Customizations ............................................................................... 127

Understanding PeopleSoft Environment Customizations .................................................................................... 127

Preparing Customization Files for Linux, AIX, HP-UX, or Solaris Users and Groups ...................................... 132

Preparing the Customization File for a Single User and Single Group .......................................................... 132

Preparing the Customization File for a New Single User, New Primary Group, and Existing Secondary Group .

134

Preparing the Customization File for Existing Users and Groups .................................................................. 135

Preparing the Customization File for JDK on AIX .............................................................................................. 137

Preparing the Customization File for JDK on HP-UX ......................................................................................... 138

Preparing the Customization File for PeopleSoft Domain Definitions ................................................................ 139

Preparing the psft_customizations.yaml File .................................................................................................. 139

Reviewing the Domain Definitions in psft_configuration.yaml ..................................................................... 140

Reviewing the Customization File for a Single Application Server Domain ................................................. 144

Reviewing the Customization File for an Application Server Domain with Custom PS_CFG_HOME ........ 145

Reviewing the Customization File for a PIA Domain on a Separate Host ..................................................... 146

Reviewing the Customization File for Multiple Web Sites in a Single Web Domain ................................... 147

Reviewing the Customization File for Multiple Domains .............................................................................. 149

Preparing the Customization File to Create PeopleSoft Domains Without Configuration .................................. 153

Preparing the Customization File for Component Software Locations ............................................................... 154

Preparing the Customization File for Unicode ..................................................................................................... 156

Preparing the Customization File for the PeopleSoft Homes .............................................................................. 157

Preparing the Customization File for the PS_HOME Location ...................................................................... 157

Contents

Preparing the Customization File for the PS_APP_HOME Location ............................................................ 158

Preparing the Customization File for the PS_CFG_HOME Location ............................................................ 159

Preparing the Customization File for Jolt SSL and WSL SSL Ports ................................................................... 160

Preparing the Customization File for Oracle HTTP Server ................................................................................. 162

Preparing the Customization File for Mid-Tier Connection to a Microsoft SQL Server Database ..................... 164

Preparing the Customization File for Mid-Tier Connection to a DB2 z/OS Database ........................................ 165

Preparing the Customization File for Mid-Tier Connection to a DB2 for Linux, UNIX, and Windows Database .

169

Preparing the Customization File to Exclude Oracle Database Client Installation ............................................. 172

Preparing the Customization File for sysctl and ulimit Parameters on Linux, AIX, HP-UX, or Solaris ............. 172

Preparing the Customization File to Change the setup_sysctl Parameter ....................................................... 173

Preparing the Customization File to Overwrite the sysctl Parameters ........................................................... 173

Preparing the Customization File to Overwrite the ulimit Parameters ........................................................... 174

Completing the Customized Deployment ............................................................................................................ 175

Chapter 4

Using and Maintaining the PeopleSoft Environment ..................................................................................... 177

Using the PeopleSoft Installation ......................................................................................................................... 177

Accessing the PeopleSoft Environment .......................................................................................................... 177

Reviewing the Deployment File System ......................................................................................................... 178

Reviewing the DPK-Created Users for Root Deployments on Linux, AIX, HP-UX, and Solaris ................. 180

Working with PeopleSoft Utilities and Programs for Root Deployments on Linux, AIX, HP-UX, and Solaris . 182

Setting Environment Variables for the Non-Root User on Linux, AIX, HP-UX, or Solaris ............................... 182

Sourcing the psft_env.sh Script ..................................................................................................................... 182

Creating a psft_env.sh Script .......................................................................................................................... 183

Removing a Deployed PeopleSoft Environment ................................................................................................. 184

Understanding the Removal Process .............................................................................................................. 185

Using the DPK Setup Script to Remove the PeopleSoft Environment on Microsoft Windows ..................... 185

Using the DPK Setup Script to Remove the PeopleSoft Environment on Linux, AIX, HP-UX, or Solaris .. 185

Using the DPK Setup Script to Remove the PeopleSoft Environment on Linux, AIX, HP-UX, or Solaris as a

Non-Root User ................................................................................................................................................ 186

Using Puppet to Remove the PeopleSoft Environment on Microsoft Windows ............................................ 186

Using Puppet to Remove the PeopleSoft Environment on Linux, AIX, HP-UX, or Solaris .......................... 187

Manually Removing the PeopleSoft Environment on Microsoft Windows ................................................... 188

Manually Removing the PeopleSoft Environment on Linux, AIX, HP-UX, or Solaris ................................. 190

Appendix A

Applying PeopleTools Patches Using DPKs .................................................................................................... 193

Reviewing PeopleTools Patch Application Options ............................................................................................ 193

Using Scenario 1 .................................................................................................................................................. 194

Contents

Understanding Scenario 1 ............................................................................................................................... 195

Stopping and Deleting the Domains on the Initial Environment .................................................................... 195

Stopping the Services for the Domains ........................................................................................................... 195

Updating the site.pp File ................................................................................................................................. 195

Removing the Existing PeopleTools Components ......................................................................................... 196

Downloading and Deploying the PeopleTools Client for the New Release ................................................... 196

Applying the PeopleTools Patch Using Change Assistant ............................................................................. 197

Deploying the New Release in Mid-Tier Mode .............................................................................................. 198

Preparing psft_customizations.yaml and Completing the Deployment .......................................................... 202

Reviewing the Results ..................................................................................................................................... 202

Verifying the Patch Application ..................................................................................................................... 203

Using Scenario 2 .................................................................................................................................................. 204

Understanding Scenario 2 ............................................................................................................................... 204

Stopping and Deleting the Domains on the Initial Environment .................................................................... 204

Stopping the Services for the Domains ........................................................................................................... 204

Downloading and Deploying the PeopleTools Client for the New Release ................................................... 205

Applying the PeopleTools Patch Using Change Assistant ............................................................................. 205

Deploying the New Release in Mid-tier Mode ............................................................................................... 206

Preparing psft_customizations.yaml and Completing the Deployment .......................................................... 210

Reviewing the Results ..................................................................................................................................... 211

Verifying the Patch Application ..................................................................................................................... 211

Using Scenario 3 .................................................................................................................................................. 212

Understanding Scenario 3 ............................................................................................................................... 213

Stopping and Deleting the Domains on the Initial Environment .................................................................... 213

Stopping the Services for the Domains ........................................................................................................... 213

Downloading and Deploying the PeopleTools Client for the New Release ................................................... 213

Applying the PeopleTools Patch Using Change Assistant ............................................................................. 214

Deploying the New Release in Mid-tier Mode ............................................................................................... 215

Preparing psft_customizations.yaml and Completing the Deployment .......................................................... 219

Reviewing the Results ..................................................................................................................................... 219

Verifying the Patch Application ..................................................................................................................... 220

Appendix B

Performing a PeopleTools-Only Upgrade Using the PeopleSoft PeopleTools DPKs ................................... 223

Understanding the PeopleTools-Only Upgrade Using the PeopleSoft PeopleTools DPKs ................................. 223

Performing the PeopleTools-Only Upgrade Using DPKs ................................................................................... 224

Reviewing the Results of the PeopleTools-Only Upgrade Using DPKs ............................................................. 226

Appendix C

Installing PeopleSoft Change Assistant ............................................................................................................ 227

Contents

Understanding PeopleSoft Change Assistant ....................................................................................................... 227

Using the Change Assistant Setup Script to Install, Upgrade, or Uninstall ......................................................... 228

Understanding the Change Assistant Setup Script .......................................................................................... 228

Running the Change Assistant Setup Script to Install .................................................................................... 228

Running the Change Assistant Setup Script to Upgrade ................................................................................ 229

Running Change Assistant Setup Script to Uninstall ..................................................................................... 230

Installing, Upgrading, or Removing Change Assistant in Silent Mode ............................................................... 231

Understanding the Change Assistant Silent Mode Script ............................................................................... 231

Using the Change Assistant Silent Mode Script to Install, Upgrade, or Uninstall ......................................... 232

Configuring and Using PeopleSoft Change Assistant ......................................................................................... 233

Verifying the Path Variable ............................................................................................................................ 233

Specifying Options .......................................................................................................................................... 233

Scanning the Workstation ............................................................................................................................... 233

Exporting Jobs to XML, HTML, or Microsoft Excel Format ........................................................................ 234

Validating Change Assistant Settings .................................................................................................................. 234

Appendix D

Encrypting Passwords for Customizations on Linux, AIX, HP-UX, or Solaris ........................................... 237

Encrypting Passwords for Customization Files on Linux, AIX, HP-UX, or Solaris ........................................... 237

Appendix E

Learning About the PeopleSoft Deployment Process ..................................................................................... 239

Understanding the PeopleSoft Deployment Framework ...................................................................................... 239

Understanding PeopleSoft Components .............................................................................................................. 240

Understanding Puppet and the PeopleSoft Puppet Modules ................................................................................ 241

Understanding Puppet ..................................................................................................................................... 241

Understanding Hiera ....................................................................................................................................... 242

Understanding Puppet Modules ...................................................................................................................... 242

Understanding How the PeopleSoft DPKs Use Puppet .................................................................................. 243

Understanding PeopleSoft Puppet Component Modules ................................................................................ 243

Understanding PeopleSoft Puppet Profiles and Roles Modules ..................................................................... 244

Understanding Puppet Third-Party Modules .................................................................................................. 244

Reviewing the Deployment Packages .................................................................................................................. 245

Understanding Deployment Package Types ................................................................................................... 245

Defining the Deployment Packages ................................................................................................................ 246

Reviewing the PeopleSoft PeopleTools Patch DPKs ........................................................................................... 247

Reviewing the PeopleTools Client DPK .............................................................................................................. 249

About this Documentation

This preface discusses:

• Understanding This Documentation

• Audience

• Typographical Conventions

• Products

• Related Information

• Comments and Suggestions

Understanding This Documentation

This documentation is designed to guide you through the deployment of the Oracle's PeopleSoft Deployment

Packages. It is not a substitute for the documentation provided for PeopleSoft PeopleTools or PeopleSoft

applications.

Audience

This documentation is written for the individuals responsible for installing and administering the PeopleSoft

environment. This documentation assumes that you have a basic understanding of the PeopleSoft system. One of

the most important components in the installation and maintenance of your PeopleSoft system is your on-site

expertise.

You should be familiar with your operating environment and RDBMS and have the necessary skills to support

that environment. You should also have a working knowledge of:

•

SQL and SQL command syntax.

• PeopleSoft system navigation.

• PeopleSoft windows, menus, and pages, and how to modify them.

• Microsoft Windows.

Oracle recommends that you complete training, particularly a PeopleSoft Server Administration and Installation

course, before performing an installation.

See Oracle University, http://education.oracle.com.

Preface

Typographical Conventions

To help you locate and understand information easily, the following conventions are used in this documentation:

Convention Description

Monospace

Indicates a PeopleCode program or other code, such as

scripts that you run during the install. Monospace is also

used for messages that you may receive during the install

process.

Italics

Indicates field values, emphasis, and book-length publication

titles. Italics is also used to refer to words as words or letters

as letters, as in the following example:

Enter the letter O.

Italics are also used to indicate user-supplied information.

For example, the term domain is used as a placeholder for

the actual domain name in the user's environment. When two

such placeholders are used together, they may be set apart

with angle brackets. For example, the path

<PS_CFG_HOME>/appserv/<domain> includes two

placeholders that require user-supplied information.

Initial Caps Field names, commands, and processes are represented as

they appear on the window, menu, or page.

lower case File or directory names are represented in lower case, unless

they appear otherwise on the interface.

Menu, Page A comma (,) between menu and page references indicates

that the page exists on the menu. For example, "Select Use,

Process Definitions" indicates that you can select the Process

Definitions page from the Use menu.

Cross-references Cross-references that begin with See refer you to additional

documentation that will help you implement the task at hand.

We highly recommend that you reference this

documentation.

Cross-references under the heading See Also refer you to

additional documentation that has more information

regarding the subject.

⇒ (line-continuation arrow)

A line-continuation arrow inserted at the end of a line of

code indicates that the line of code has been wrapped at the

page margin. The code should be viewed or entered as a

continuous line of code, without the line-continuation arrow.

" " (quotation marks) Indicate chapter titles in cross-references and words that are

used differently from their intended meaning.

Preface

Convention Description

Note. Note text.

Text that begins with Note. indicates information that you

should pay particular attention to as you work with your

PeopleSoft system.

Important! Important note text.

A note that begins with Important! is crucial and includes

information about what you need to do for the system to

function properly.

Warning! Warning text.

A note that begins with Warning! contains critical

configuration information or implementation considerations;

for example, if there is a chance of losing or corrupting data.

Pay close attention to warning messages.

Products

This documentation may refer to these products and product families:

•

Oracle® BPEL Process Manager

•

Oracle® Enterprise Manager

•

Oracle® Tuxedo

•

Oracle® WebLogic Server

•

Oracle's PeopleSoft Application Designer

•

Oracle's PeopleSoft Change Assistant

•

Oracle's PeopleSoft Change Impact Analyzer

•

Oracle's PeopleSoft Data Mover

• Oracle's PeopleSoft Process Scheduler

• Oracle's PeopleSoft Pure Internet Architecture

•

Oracle's PeopleSoft Customer Relationship Management

•

Oracle's PeopleSoft Enterprise Learning Management

•

Oracle's PeopleSoft Enterprise Performance Management

•

Oracle's PeopleSoft Financial Management

•

Oracle's PeopleSoft Human Capital Management

•

Oracle's PeopleSoft Interaction Hub

•

Oracle's PeopleSoft Pay/Bill Management

•

Oracle's PeopleSoft PeopleTools

•

Oracle's PeopleSoft Staffing Front Office

•

Oracle's PeopleSoft Supply Chain Management

See the Products area on the Oracle web site, http://www.oracle.com/us/products/product-list/products-a-

z/index.html.

Preface

Related Information

Oracle provides reference information about PeopleSoft PeopleTools and your particular PeopleSoft Application.

You can access documentation for recent releases of PeopleSoft PeopleTools and PeopleSoft Applications at the

PeopleSoft Hosted Documentation site. You can also find documentation by searching for the product name on

My Oracle Support.

• My Oracle Support. This support platform requires a user account to log in. Contact your PeopleSoft

representative for information.

To locate documentation on My Oracle Support, search for the title and select PeopleSoft Enterprise to refine

the search results.

See My Oracle Support, https://support.oracle.com.

• PeopleTools: Getting Started with PeopleTools for your release. This documentation provides a high-level

introduction to PeopleTools technology and usage.

See Oracle PeopleSoft Online Help, http://www.peoplesoftonlinehelp.com.

•

PeopleSoft Application Fundamentals for your PeopleSoft Application and release. This documentation

provides essential information about the setup, design, and implementation of your PeopleSoft Application.

To install additional component software products for use with PeopleSoft products, including those products that

are packaged with your PeopleSoft products as well as products from other vendors, you should refer to the

documentation provided with those products, as well as this documentation. For those additional components that

are offered by Oracle, such as Oracle Middleware products, see the documentation on the Oracle Help Center.

See Also

Oracle Help Center, https://docs.oracle.com/en/

Comments and Suggestions

Your comments are important to us. We encourage you to tell us what you like, or what you would like changed

about PeopleSoft documentation and other Oracle reference and training materials. Please send your suggestions

to:

[email protected]

While we cannot guarantee to answer every email message, we will pay careful attention to your comments and

suggestions. We are always improving our product communications for you.

Chapter 1

Prerequisites

This chapter discusses:

• Understanding the PeopleSoft PeopleTools Deployment Packages

• Reviewing Hardware Requirements

• Reviewing Software Requirements

• Cataloging the Database for DB2 LUW or DB2 z/OS

• Reviewing the System Parameters on Linux, AIX, HP-UX, or Solaris

Understanding the PeopleSoft PeopleTools Deployment Packages

The PeopleSoft PeopleTools deployment packages (DPKs) enable you to install the PeopleSoft PeopleTools

server and client software, application server, Process Scheduler, and PeopleSoft Pure Internet Architecture (PIA)

domains, as well as required supporting software, for use with an existing PeopleSoft database. For details about

the PeopleTools DPKs, see the following sections in this documentation:

For information about this topic: See this section:

How to obtain the DPKs from My Oracle Support or Oracle

Software Delivery Cloud

"Deploying the PeopleSoft PeopleTools Deployment

Packages," Obtaining the PeopleSoft PeopleTools DPKs

Using the DPKs to install PeopleSoft application server,

Process Scheduler, and PIA domains (referred to as a mid-

tier environment)

"Deploying the PeopleSoft PeopleTools Deployment

Packages," Running the DPK Setup Script for Mid-Tier

Deployment

Using the DPKs to install only the installation directory for

the PeopleSoft PeopleTools server software (PS_HOME)

"Deploying the PeopleSoft PeopleTools Deployment

Packages," Running the DPK Setup Script to Install

PS_HOME Only

Using the DPK to install PeopleTools Client software "Deploying the PeopleSoft PeopleTools Deployment

Packages," Deploying the PeopleTools Client DPK

Methods for using the DPKs for patching a PeopleSoft

PeopleTools 8.57 release

"Applying PeopleTools Patches Using DPKs"

How to customize the DPK installation for your environment

Note. If you are connecting to a database platform other than

Oracle, you must use customizations.

"Completing the DPK Initialization with Customizations"

Prerequisites Chapter 1

For information about this topic: See this section:

Using the DPKs for other selective installations, such as an

application server domain alone.

"Deploying the PeopleSoft PeopleTools Deployment

Packages," Reviewing the DPK Setup Script Options

The terminology used with DPK deployment, and the

contents of the DPKs

"Learning About the PeopleSoft Deployment Process,"

Reviewing the Deployment Packages

The PeopleSoft components installed by the DPK

deployment

"Learning About the PeopleSoft Deployment Process,"

Understanding PeopleSoft Components

The Puppet open-source software used in DPK development "Learning About the PeopleSoft Deployment Process,"

Understanding Puppet and the PeopleSoft Puppet Modules

Task 1-1: Reviewing Hardware Requirements

This section discusses:

• Reviewing Hardware Requirements for Microsoft Windows

• Reviewing Hardware Requirements on AIX, HP-UX, Linux, or Solaris

Task 1-1-1: Reviewing Hardware Requirements for Microsoft Windows

You can install the PeopleSoft Application Image deployment packages (DPKs) or PeopleSoft PeopleTools DPKs

directly on a system running a Microsoft Windows operating system. The PeopleSoft Application Images and

PeopleSoft PeopleTools DPKs are certified to run on those Microsoft Windows operating systems that are

certified for the current PeopleSoft PeopleTools release. The Microsoft Windows system can be a physical

computer (sometimes called "bare-metal") or a virtual machine.

Oracle strongly recommends that you dedicate a Microsoft Windows machine for the PeopleTools client. This

should be a machine that is not used for other PeopleSoft purposes.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Deploying the PeopleTools Client DPK in

Standalone Mode, for information on installing the PeopleTools client utilities.

• Host computer: The PeopleSoft DPKs can be deployed directly on any supported Microsoft Windows host,

bare-metal or virtual.

If you deploy on a virtual host computer, you are responsible for provisioning the virtual machine before

beginning the deployment.

• Host operating system: The host operating system (OS) must be a 64-bit platform that is certified by Oracle

for PeopleSoft systems.

Note. My Oracle Support Certification notes include information about the PeopleSoft PeopleTools

components that are certified for each operating system. Some OSs are certified only for browsers and clients.

If you want to deploy a full PeopleSoft environment, verify that the OS you want to use is certified for server

installation.

See My Oracle Support, Certifications.

See PeopleSoft PeopleTools Certifications, My Oracle Support, Doc ID 747587.1, for help searching

PeopleSoft Certifications.

Chapter 1 Prerequisites

• RAM (Memory): A minimum of 8 GB RAM is required to run a PeopleSoft environment.

• Disk space: The disk space requirements vary depending upon the type of environment you set up.

See "Preparing to Deploy," Understanding PeopleSoft Components.

• 25–35 GB free disk space for the downloaded zip files

You may remove these files after you have successfully initialized your virtual machine.

• 150 GB free disk space is required to deploy and set up a full tier PeopleSoft environment.

• 75 GB free disk space is required to deploy and set up a db-tier PeopleSoft environment.

• 25 GB free disk space is required to deploy and set up a mid-tier PeopleSoft environment.

See Also

Tech Update - Main Page, My Oracle Support, Doc ID 764222.1

Task 1-1-2: Reviewing Hardware Requirements on AIX, HP-UX, Linux, or

Solaris

You can install the PeopleSoft Application Image deployment packages (DPKs) directly on a system running an

Oracle Linux operating system. You can install the PeopleSoft PeopleTools deployment packages (DPKs) directly

on a system running an IBM AIX, HP-UX, Linux, or Solaris operating system. The PeopleSoft Application

Images and PeopleSoft PeopleTools DPKs are certified to run on those operating systems that are certified for the

current PeopleSoft PeopleTools release. The AIX, HP-UX, Linux, or Solaris system can be a physical computer

(sometimes called "bare-metal") or a virtual machine.

• Host computer: The PeopleSoft DPKs can be deployed on any supported AIX, HP-UX, Linux, or Solaris host,

either a physical computer or virtual machine. The PeopleSoft DPKs can also be deployed on Oracle Exalogic

Elastic Cloud.

If you deploy on a virtual host computer, you are responsible for provisioning the virtual machine before

beginning the deployment.

• Host operating system: The host operating system must be a 64-bit platform that is certified by Oracle for

PeopleSoft systems.

See My Oracle Support, Certifications.

See PeopleSoft PeopleTools Certifications, My Oracle Support, Doc ID 747587.1, for help searching

PeopleSoft Certifications.

• RAM (Memory): A minimum of 8 GB RAM is required to run a PeopleSoft environment.

• Disk space: The disk space requirements vary depending upon the type of environment you set up.

See "Preparing to Deploy," Understanding PeopleSoft Components.

• 25–35 GB free disk space for the downloaded zip files

You may remove these files after you have successfully initialized your virtual machine.

•

150 GB free disk space is required to deploy and set up a full tier PeopleSoft environment.

•

75 GB free disk space is required to deploy and set up a db-tier PeopleSoft environment.

•

25 GB free disk space is required to deploy and set up a mid-tier PeopleSoft environment.

Prerequisites Chapter 1

See Also

My Oracle Support, Certifications.

Tech Update - Main Page, My Oracle Support, Doc ID 764222.1

Task 1-2: Reviewing Software Requirements

This section discusses:

• Reviewing Software Requirements on Microsoft Windows

• Reviewing Software Requirements on Linux

• Reviewing Software Requirements on AIX

• Reviewing Software Requirements on HP-UX

• Reviewing Software Requirements on Solaris

• Reviewing Requirements for the Puppet Software on Microsoft Windows

• Reviewing Requirements for the Puppet Software on Linux

• Reviewing Requirements for the Puppet Software on AIX

• Reviewing Requirements for the Puppet Software on HP-UX

• Reviewing Requirements for the Puppet Software on Solaris

Task 1-2-1: Reviewing Software Requirements on Microsoft Windows

Here are the software requirements for using the PeopleSoft Deployment Packages on a Microsoft Windows

machine:

•

Administrative permission

•

Read, write, and execute permission on the default temporary folder.

The deployment of a PeopleSoft environment by the DPKs installs required supporting software, such as

Oracle WebLogic and Oracle Tuxedo. The DPK process to install this software uses the default temporary

folders, as specified by the environment variable for the operating system. The user running the DPK setup

script must have read/write/execute permission to these default temporary folders for successful DPK

installation, or the deployment steps that install these components will fail.

•

The DPK setup script can be run from any drive, regardless of the drive where the Windows operating system

is installed.

•

Web Browser

You need a version certified for the current PeopleSoft PeopleTools release for end-users.

See PeopleSoft Update Manager (PUM) Home Page, My Oracle Support, Doc ID 1641843.2.

See My Oracle Support, Certifications.

•

Zip utility

You need a utility that is able to extract (unzip) the DPK zip files for your operating system.

•

Verify that the PATHEXT environment variable includes the extension .bat.

This is a requirement for running Puppet. For example:

Chapter 1 Prerequisites

PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC

• Python 3.6.2 is included with the DPKs.

• Specifying PS_CUST_HOME

If you wish to use a PS_CUST_HOME location to store your site's custom files, you must create the directory

manually and set the PS_CUST_HOME environment variable. The DPK setup will use the environment

variable location for setting up the PeopleSoft domains.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Preparing to Run the DPK Setup Script.

Task 1-2-2: Reviewing Software Requirements on Linux

Here are the software requirements for using the PeopleSoft Deployment Packages on a Linux machine:

• You must have root access to deploy the PeopleSoft DPKs.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Deploying as a Non-Root User on Linux,

AIX, HP-UX, or Solaris.

•

Read, write, and execute permission on the default temporary folder.

The deployment of a PeopleSoft environment by the DPKs installs required supporting software, such as

Oracle WebLogic and Oracle Tuxedo. The DPK process to install this software uses the default temporary

folders, as specified by the environment variable for the operating system. The user running the DPK setup

script must have read, write, and execute permission to these default temporary folders for successful DPK

installation, or the deployment steps that install these components will fail.

•

If you are installing the PeopleSoft DPKs on Oracle Linux 6 or 7 with Unbreakable Enterprise Kernel (UEK),

apply the latest UEK kernel from the Oracle YUM repository at http://public-yum.oracle.com/index.html.

• Zip utility

You need a utility that is able to extract (unzip) the DPK zip files for your operating system; for example, tar

or unzip.

• Specifying PS_CUST_HOME

If you wish to use a PS_CUST_HOME location to store your site's custom files, you must create the directory

manually and set the PS_CUST_HOME environment variable. The DPK setup will use the environment

variable location for setting up the PeopleSoft domains.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Preparing to Run the DPK Setup Script.

• Python 3.6.2 is included with the DPKs.

Task 1-2-3: Reviewing Software Requirements on AIX

Here are the software requirements for using the PeopleSoft Deployment Packages on an IBM AIX machine:

•

You must have root access to deploy the PeopleSoft DPKs.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Deploying as a Non-Root User on Linux,

AIX, HP-UX, or Solaris.

• Read, write, and execute permission on the default temporary folder.

The deployment of a PeopleSoft environment by the DPKs installs required supporting software, such as

Oracle WebLogic and Oracle Tuxedo. The DPK process to install this software uses the default temporary

folders, as specified by the environment variable for the operating system. The user running the DPK setup

script must have read, write, and execute permission to these default temporary folders for successful DPK

installation, or the deployment steps that install these components will fail.

Prerequisites Chapter 1

• Utilities for extracting the DPK zip files

You need both the gunzip and unzip utilities for your operating system in order to extract the DPK zip files,

and the PATH for the root user must include the gunzip and unzip locations.

• OpenSSL

Obtain the latest version of OpenSSL for your AIX operating system from your IBM support contact, and

install it on the host.

• JDK 8.0

You must manually install JDK 8.0 from the IBM web site. To obtain 64-bit IBM JDK for IBM AIX:

1. Go to the IBM JDK download and service site.

http://www.ibm.com/developerworks/java/jdk/aix/service.html

Note. You need a user name and password for downloading IBM JDK. If you don't have the required

credentials, contact IBM AIX support.

2. Select the link for Java 8 64-bit under Java SE Version 8.

3. Provide the required information to sign in.

4. Install the JDK on the AIX computer where you will install the PeopleSoft AIX DPK.

5. Make a note of the installation location.

For the AIX DPK installation, you must perform the deployment using the DPK customizations, and

specify the AIX JDK installation location.

See "Completing the DPK Initialization With Customizations," Preparing the Customization File for JDK

on AIX.

•

Specifying PS_CUST_HOME

If you wish to use a PS_CUST_HOME location to store your site's custom files, you must create the directory

manually and set the PS_CUST_HOME environment variable. The DPK setup will use the environment

variable location for setting up the PeopleSoft domains.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Preparing to Run the DPK Setup Script.

• Python 3.6.2 is included with the DPKs.

Task 1-2-4: Reviewing Software Requirements on HP-UX

Here are the software requirement for using the PeopleSoft Deployment Packages on HP-UX Itanium.

• You must have root access to deploy the PeopleSoft DPKs.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Deploying as a Non-Root User on Linux,

AIX, HP-UX, or Solaris.

• Read, write, and execute permission on the default temporary folder.

The deployment of a PeopleSoft environment by the DPKs installs required supporting software, such as

Oracle WebLogic and Oracle Tuxedo. The DPK process to install this software uses the default temporary

folders, as specified by the environment variable for the operating system. The user running the DPK setup

script must have read, write, and execute permission to these default temporary folders for successful DPK

installation, or the deployment steps that install these components will fail.

• Utilities for extracting the DPK zip files

Install tar and zip/unzip utilities from Hewlett Packard and add the locations to your PATH:

1. Go to HP-UX Porting & Archiving Centre, at http://hpux.connect.org.uk.

Chapter 1 Prerequisites

2. Follow the instructions on the HP-UX Porting & Archiving Centre to install tar and its runtime

dependencies, gettext, libiconv, and libunistring.

3. Install zip/unzip from the HP-UX Porting & Archiving Centre, at http://hpux.connect.org.uk.

4. Add the installation locations for tar, zip, and unzip to PATH.

Make sure that the installation location for tar is first in the PATH. For example, if you installed tar to

/usr/local/bin:

exportPATH=/usr/local/bin:$PATH

5. Set LD_LIBRARY_PATH. For example, if your installation location above was in /usr/local:

exportLD_LIBRARY_PATH=/usr/local/lib${LD_LIBRARY_PATH+:$LD_LIBRARY_⇒

PATH}

• OpenSSL

Install the latest version of OpenSSL on the host where you will run the DPK setup script.

1. Go to the HP-UX Porting and Archive Centre web site, at http://hpux.connect.org.uk/hppd/hpux/.

2. Search for openssl, and locate the latest version of OpenSSL in the list of results.

3. Select the link for the latest OpenSSL package, for example openssl-1.0.2p.

4. Download the gzipped binary package for 64-bit Itanium; for this example, this is openssl-1.0.2p-ia64-

11.31.depot.gz.

5. Use the installation documentation on the same page to install the OpenSSL package.

•

JDK 8.0

You must manually install JDK 8.0 from the Hewlett Packard web site. To obtain 64-bit JDK for HP-UX

Itanium:

1. Go to the Hewlett Packard Software Depot.

See Hewlett Packard Software Depot,

https://h20392.www2.hpe.com/portal/swdepot/index.do?lc=EN_US.

2. Locate the link for the latest JDK/JRE for your HP-UX operating system.

Select the link for Version 8.0.14 or higher.

3. Install the JDK on the HP-UX computer where you will install the PeopleSoft HP-UX DPK.

4. Make a note of the installation location.

For the HP-UX DPK installation, you must perform the deployment using the DPK customizations, and

specify the HP-UX JDK installation location.

See "Completing the DPK Initialization With Customizations," Preparing the Customization File for JDK

on HP-UX.

•

Specifying PS_CUST_HOME

If you wish to use a

PS_CUST_HOME

location to store your site's custom files, you must create the directory

manually and set the PS_CUST_HOME environment variable. The DPK setup will use the environment

variable location for setting up the PeopleSoft domains.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Preparing to Run the DPK Setup Script.

•

Python 3.6.2 is included with the DPKs.

Prerequisites Chapter 1

Task 1-2-5: Reviewing Software Requirements on Solaris

Here are the software requirements for using the PeopleSoft Deployment Packages on Solaris:

• You must have root access to deploy the PeopleSoft DPKs.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Deploying as a Non-Root User on Linux,

AIX, HP-UX, or Solaris.

• Read, write, and execute permission on the default temporary folder.

The deployment of a PeopleSoft environment by the DPKs installs required supporting software, such as

Oracle WebLogic and Oracle Tuxedo. The DPK process to install this software uses the default temporary

folders, as specified by the environment variable for the operating system. The user running the DPK setup

script must have read, write, and execute permission to these default temporary folders for successful DPK

installation, or the deployment steps that install these components will fail.

• Zip utility

You need a utility that is able to extract (unzip) the DPK zip files for your operating system; for example, tar

or unzip.

• OpenSSL

Obtain the latest version of OpenSSL for your operating system and install it on the host.

• Specifying PS_CUST_HOME

If you wish to use a PS_CUST_HOME location to store your site's custom files, you must create the directory

manually and set the PS_CUST_HOME environment variable. The DPK setup will use the environment

variable location for setting up the PeopleSoft domains.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Preparing to Run the DPK Setup Script.

• Python 3.6.2 is included with the DPKs.

Task 1-2-6: Reviewing Requirements for the Puppet Software on Microsoft

Windows

The PeopleSoft DPKs are delivered with the PeopleSoft Puppet modules, which are initialization and

management scripts based upon open-source Puppet software.

• Installation requirements

In most cases, the Puppet software will be installed by the DPKs. In some scenarios it may be necessary for

you to install either Puppet or its dependencies directly. If so, use these guidelines:

•

The DPK deployment requires open-source Puppet software.

See the Puppet Labs Web site at www.puppetlabs.com to download the software.

•

Customer installation of Puppet is supported for Microsoft Windows operating systems.

• These are the minimum requirements for the software versions associated with using Puppet with the

PeopleSoft DPKs on Microsoft Windows operating systems:

•

Puppet Agent 5.3.5 (open source, and stand-alone architecture)

•

Hiera 3.4.2

•

Facter 2.4.4

•

Ruby 2.4.3

•

MCollective 2.11.4

Chapter 1 Prerequisites

• Operating system packages required for Puppet

The Puppet software used for the DPK deployment is dependent on certain OS-level packages, which may not

be present in the delivered DPKs. In this case, you can use the information in the DPK setup log file to

determine which packages are needed. It is the responsibility of the user to obtain and install the required

packages.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Obtaining Operating System Packages

Required for Puppet.

• Installation location

Puppet software is installed in a standard location by the DPKs. The DPK deployment checks for existing

Puppet installations only in that standard location. If Puppet software was installed in a different location, for

example for other business or development requirements, the DPK will not recognize or try to remove that

existing Puppet installation. It will install to the standard location dictated by the DPK requirement, and the

other Puppet installation may subsequently cause problems.

See Also

"Learning About the PeopleSoft Deployment Process," Understanding Puppet and the PeopleSoft Puppet Modules

Task 1-2-7: Reviewing Requirements for the Puppet Software on Linux

The PeopleSoft DPKs are delivered with the PeopleSoft Puppet modules, which are initialization and

management scripts based upon open-source Puppet software.

• You must have root access to deploy the PeopleSoft DPKs.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Deploying as a Non-Root User on Linux,

AIX, HP-UX, or Solaris.

• The Puppet directory and its scripts must have read and execute permissions for all users.

Puppet must be installed by the root user, either by running the DPK setup for any env_type or by running the

prereq step for non-root users. If the root user has a non-default umask, when Puppet is installed by the root

user, the files in the Puppet directory will not have the correct permissions for other users, which would

impact non-root users who subsequently try to run the DPK setup.

For example, if root has umask of 027, the permissions would be set as in the following example:

-rwxr-x---1rootroot126Feb122018/opt/puppetlabs/puppet/bin⇒

/wrapper.sh

In this case, the root user has read, write, and execute permissions for files in this Puppet installation. The

group that root belongs to has read and execute permission, and all other users have no permissions. So a non-

root user will not have read and execute permissions for running the scripts in the Puppet directory

(wrapper.sh in this example). Without the necessary permissions for the Puppet files, when the non-root user

runs the DPK setup, Puppet execution will fail, because that user will not be able to execute any script or

binary from the Puppet directory.

•

Installation requirements

In most cases, the Puppet software will be installed by the DPKs. In some scenarios it may be necessary for

you to install either Puppet or its dependencies directly. If so, use these guidelines:

•

The DPK deployment requires open-source Puppet software.

See the Puppet Labs Web site at www.puppetlabs.com to download the software.

•

Customer installation of Puppet is supported for Linux operating systems.

Prerequisites Chapter 1

• These are the minimum requirements for the software versions associated with using Puppet with the

PeopleSoft DPKs on Linux operating systems:

• Puppet Agent 5.3.5 (open source, and stand-alone architecture)

• Hiera 3.4.2

• Facter 2.4.4

• Ruby 2.4.3

• MCollective 2.11.4

• Operating system packages required for Puppet

The Puppet software used for the DPK deployment is dependent on certain OS-level packages, which may not

be present in the delivered DPKs. In this case, you can use the information in the DPK setup log file to

determine which packages are needed. It is the responsibility of the user to obtain and install the required

packages.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Obtaining Operating System Packages

Required for Puppet.

• Installation location

Puppet software is installed in a standard location by the DPKs. The DPK deployment checks for existing

Puppet installations only in that standard location. If Puppet software was installed in a different location, for

example for other business or development requirements, the DPK will not recognize or try to remove that

existing Puppet installation. It will install to the standard location dictated by the DPK requirement, and the

other Puppet installation may subsequently cause problems.

See Also

"Learning About the PeopleSoft Deployment Process," Understanding Puppet and the PeopleSoft Puppet Modules

Task 1-2-8: Reviewing Requirements for the Puppet Software on AIX

The PeopleSoft DPKs are delivered with the PeopleSoft Puppet modules, which are initialization and

management scripts based upon open-source Puppet software.

• You must have root access to deploy the PeopleSoft DPKs.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Deploying as a Non-Root User on Linux,

AIX, HP-UX, or Solaris.

•

The Puppet directory and its scripts must have read and execute permissions for all users.

Puppet must be installed by the root user, either by running the DPK setup for any env_type or by running the

prereq step for non-root users. If the root user has a non-default umask, when Puppet is installed by the root

user, the files in the Puppet directory will not have the correct permissions for other users, which would

impact non-root users who subsequently try to run the DPK setup.

For example, if root has umask of 027, the permissions would be set as in the following example:

-rwxr-x---1rootroot126Feb122018/opt/puppetlabs/puppet/bin⇒

/wrapper.sh

In this case, the root user has read, write, and execute permissions for files in this Puppet installation. The

group that root belongs to has read and execute permission, and all other users have no permissions. So a non-

root user will not have read and execute permissions for running the scripts in the Puppet directory

(wrapper.sh in this example). Without the necessary permissions for the Puppet files, when the non-root user

runs the DPK setup, Puppet execution will fail, because that user will not be able to execute any script or

Chapter 1 Prerequisites

binary from the Puppet directory.

• Installation requirements

In most cases, the Puppet software will be installed by the DPKs. In some scenarios it may be necessary for

you to install either Puppet or its dependencies directly. If so, use these guidelines:

• The DPK deployment requires open-source Puppet software.

See the Puppet Labs Web site at www.puppetlabs.com to download the software.

• Customer installation of Puppet is not supported for IBM AIX operating systems.

If you are installing the PeopleSoft DPKs for IBM AIX, you must use the Puppet software that is delivered

with the DPKs.

• If you are installing the PeopleSoft DPKs for IBM AIX, check the Puppet web site for Puppet dependencies or

limitations for those operating systems.

• These are the minimum requirements for the software versions associated with using Puppet with the

PeopleSoft DPKs on AIX operating systems:

• Puppet Agent 5.3.5 (open source, and stand-alone architecture)

•

Hiera 3.4.2

•

Facter 2.4.4

•

Ruby 2.4.4

• Operating system packages required for Puppet

The Puppet software used for the DPK deployment is dependent on certain OS-level packages, which may not

be present in the delivered DPKs. In this case, you can use the information in the DPK setup log file to

determine which packages are needed. It is the responsibility of the user to obtain and install the required

packages.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Obtaining Operating System Packages

Required for Puppet.

• Installation location

Puppet software is installed in a standard location by the DPKs. The DPK deployment checks for existing

Puppet installations only in that standard location. If Puppet software was installed in a different location, for

example for other business or development requirements, the DPK will not recognize or try to remove that

existing Puppet installation. It will install to the standard location dictated by the DPK requirement, and the

other Puppet installation may subsequently cause problems.

See Also

"Learning About the PeopleSoft Deployment Process," Understanding Puppet and the PeopleSoft Puppet Modules

Task 1-2-9: Reviewing Requirements for the Puppet Software on HP-UX

The PeopleSoft DPKs are delivered with the PeopleSoft Puppet modules, which are initialization and

management scripts based upon open-source Puppet software.

• You must have root access to deploy the PeopleSoft DPKs.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Deploying as a Non-Root User on Linux,

AIX, HP-UX, or Solaris.

• The Puppet directory and its scripts must have read and execute permissions for all users.

Puppet must be installed by the root user, either by running the DPK setup for any env_type or by running the

Prerequisites Chapter 1

prereq step for non-root users. If the root user has a non-default umask, when Puppet is installed by the root

user, the files in the Puppet directory will not have the correct permissions for other users, which would

impact non-root users who subsequently try to run the DPK setup.

For example, if root has umask of 027, the permissions would be set as in the following example:

-rwxr-x---1rootroot126Feb122018/opt/puppetlabs/puppet/bin⇒

/wrapper.sh

In this case, the root user has read, write, and execute permissions for files in this Puppet installation. The

group that root belongs to has read and execute permission, and all other users have no permissions. So a non-

root user will not have read and execute permissions for running the scripts in the Puppet directory

(wrapper.sh in this example). Without the necessary permissions for the Puppet files, when the non-root user

runs the DPK setup, Puppet execution will fail, because that user will not be able to execute any script or

binary from the Puppet directory.

• Installation requirements

In most cases, the Puppet software will be installed by the DPKs. In some scenarios it may be necessary for

you to install either Puppet or its dependencies directly. If so, use these guidelines:

• The DPK deployment requires open-source Puppet software.

See the Puppet Labs Web site at www.puppetlabs.com to download the software.

• Customer installation of Puppet is not supported for HP-UX operating systems.

If you are installing the PeopleSoft DPKs for HP-UX, you must use the Puppet software that is delivered

with the DPKs.

• If you are installing the PeopleSoft DPKs for HP-UX, check the Puppet web site for Puppet dependencies or

limitations for those operating systems.

• These are the minimum requirements for the software versions associated with using Puppet with the

PeopleSoft DPKs on HP-UX operating systems:

•

Puppet Agent 5.3.5 (open source, and stand-alone architecture)

•

Hiera 3.4.2

•

Facter 2.4.4

•

Ruby 2.4.4

• Operating system packages required for Puppet

The Puppet software used for the DPK deployment is dependent on certain OS-level packages, which may not

be present in the delivered DPKs. In this case, you can use the information in the DPK setup log file to

determine which packages are needed. It is the responsibility of the user to obtain and install the required

packages.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Obtaining Operating System Packages

Required for Puppet.

• Installation location

Puppet software is installed in a standard location by the DPKs. The DPK deployment checks for existing

Puppet installations only in that standard location. If Puppet software was installed in a different location, for

example for other business or development requirements, the DPK will not recognize or try to remove that

existing Puppet installation. It will install to the standard location dictated by the DPK requirement, and the

other Puppet installation may subsequently cause problems.

Chapter 1 Prerequisites

See Also

"Learning About the PeopleSoft Deployment Process," Understanding Puppet and the PeopleSoft Puppet Modules

Task 1-2-10: Reviewing Requirements for the Puppet Software on Solaris

The PeopleSoft DPKs are delivered with the PeopleSoft Puppet modules, which are initialization and

management scripts based upon open-source Puppet software.

• You must have root access to deploy the PeopleSoft DPKs.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Deploying as a Non-Root User on Linux,

AIX, HP-UX, or Solaris.

• The Puppet directory and its scripts must have read and execute permissions for all users.

Puppet must be installed by the root user, either by running the DPK setup for any env_type or by running the

prereq step for non-root users. If the root user has a non-default umask, when Puppet is installed by the root

user, the files in the Puppet directory will not have the correct permissions for other users, which would

impact non-root users who subsequently try to run the DPK setup.

For example, if root has umask of 027, the permissions would be set as in the following example:

-rwxr-x---1rootroot126Feb122018/opt/puppetlabs/puppet/bin⇒

/wrapper.sh

In this case, the root user has read, write, and execute permissions for files in this Puppet installation. The

group that root belongs to has read and execute permission, and all other users have no permissions. So a non-

root user will not have read and execute permissions for running the scripts in the Puppet directory

(wrapper.sh in this example). Without the necessary permissions for the Puppet files, when the non-root user

runs the DPK setup, Puppet execution will fail, because that user will not be able to execute any script or

binary from the Puppet directory.

• Installation requirements

In most cases, the Puppet software will be installed by the DPKs. In some scenarios it may be necessary for

you to install either Puppet or its dependencies directly. If so, use these guidelines:

• The DPK deployment requires open-source Puppet software.

See the Puppet Labs Web site at www.puppetlabs.com to download the software.

• Customer installation of Puppet is not supported for Solaris operating systems.

If you are installing the PeopleSoft DPKs for Solaris, you must use the Puppet software that is delivered

with the DPKs.

•

Before installing the PeopleSoft DPKs for Solaris, check the Puppet web site for Puppet dependencies or

limitations for those operating systems.

•

These are the minimum requirements for the software versions associated with using Puppet with the

PeopleSoft DPKs on Oracle Solaris for SPARC operating systems:

• Puppet Agent 5.3.5 (open source, and stand-alone architecture)

• Hiera 3.4.2

• Facter 2.4.4

• Ruby 2.4.4

• Operating system packages required for Puppet

The Puppet software used for the DPK deployment is dependent on certain OS-level packages, which may not

Prerequisites Chapter 1

be present in the delivered DPKs. In this case, you can use the information in the DPK setup log file to

determine which packages are needed. It is the responsibility of the user to obtain and install the required

packages.

See "Deploying the PeopleSoft PeopleTools Deployment Packages," Obtaining Operating System Packages

Required for Puppet.

• Installation location

Puppet software is installed in a standard location by the DPKs. The DPK deployment checks for existing

Puppet installations only in that standard location. If Puppet software was installed in a different location, for

example for other business or development requirements, the DPK will not recognize or try to remove that

existing Puppet installation. It will install to the standard location dictated by the DPK requirement, and the

other Puppet installation may subsequently cause problems.

See Also

"Learning About the PeopleSoft Deployment Process," Understanding Puppet and the PeopleSoft Puppet Modules

Task 1-3: Cataloging the Database for DB2 LUW or DB2 z/OS

For all installations on DB2 z/OS or DB2 for Linux, UNIX, or Windows (DB2 LUW), you must catalog the

database before mid-tier deployment using DPKs. To catalog the database, see the documentation for DB2 z/OS

or DB2 LUW for information.

Task 1-4: Reviewing the System Parameters on Linux, AIX, HP-

UX, or Solaris

This section discusses:

•

Understanding the System Parameters on Linux, AIX, HP-UX, or Solaris

• Reviewing the sysctl Parameters

• Reviewing the ulimit Parameters

Understanding the System Parameters on Linux, AIX, HP-UX, or Solaris

The generated YAML file for UNIX operating systems includes settings for certain system parameters. When you

run the DPK setup script on Linux, AIX, HP-UX, or Solaris, the script overwrites existing system-level

parameters that are different from the values in BASE_DIR/dpk/puppet/production/data/psft_unix_system.yaml.

You can perform a customized deployment to make certain changes to the way that the DPK deployment handles

these system parameters, but be aware that the values listed in the psft_unix_system.yaml file are the minimum

requirements for the DPK deployment.

Task 1-4-1: Reviewing the sysctl Parameters

If you do not want the DPK setup script to overwrite the sysctl parameters, you can perform one of these

customized deployments:

• If the existing sysctl settings on your system meet the DPK requirements, you can change the value of the

Chapter 1 Prerequisites

parameter setup_syscfg from true to false.

This change will prevent the DPK setup script from overwriting the parameters.

See "Completing the DPK Initialization with Customizations," Preparing the Customization File to Change

the setup_sysctl Parameter.

• If you want to allow the DPK setup script to change the sysctl settings on your system, retain the parameter

setup_syscfg: true, and specify values for the following sysctl parameters that are greater than those

given in the generated psft_unix_system.yaml file.

sysctl:

kernel.msgmnb:65538

kernel.msgmni:1024

kernel.msgmax:65536

kernel.shmmax:68719476736

kernel.shmall:4294967296

kernel.core_uses_pid:1

net.ipv4.tcp_keepalive_time:90

net.ipv4.tcp_timestamps:1

net.ipv4.tcp_window_scaling:1

net.ipv4.ip_local_port_range:'1000065500'

See "Completing the DPK Initialization with Customizations," Preparing the Customization File to Overwrite

the sysctl Parameters.

Task 1-4-2: Reviewing the ulimit Parameters

The psft_unix_system.yaml file includes the following ulimit parameters. These are the minimum requirements

for the deployment. If you do not want the DPK setup script to overwrite the ulimit parameters, you can perform a

customized deployment and specify values for the ulimit parameters that are greater than those given in the

generated psft_unix_system.yaml file.

ulimit:

group:

hard.nofile:65536

soft.nofile:65536

hard.nproc:65536

soft.nproc:65536

hard.core:unlimited

soft.core:unlimited

hard.memlock:500000

soft.memlock:500000

hard.stack:102400

soft.stack:102400

user:

hard.nofile:131072

soft.nofile:131072

hard.nproc:131072

soft.nproc:131072

hard.core:unlimited

soft.core:unlimited

hard.memlock:500000

soft.memlock:500000

Prerequisites Chapter 1

See "Completing the DPK Initialization with Customizations," Preparing the Customization File to Overwrite the

ulimit Parameters.

Chapter 2

Deploying the PeopleSoft PeopleTools

Deployment Packages

This chapter discusses:

• Obtaining the PeopleSoft PeopleTools DPKs

•

Reviewing the DPK Setup Script Options

•

Deploying as a Non-Root User on Linux, AIX, HP-UX, or Solaris

•

Running the DPK Setup Script for Mid-Tier Deployment

•

Running the DPK Setup Script to Install Mid-Tier Software Only

•

Running the DPK Setup Script to Deploy an Application Server Domain

•

Running the DPK Setup Script to Deploy a Process Scheduler Domain

•

Running the DPK Setup Script to Deploy an Application Server and a Process Scheduler Domain

•

Running the DPK Setup Script to Deploy a PIA Domain

•

Running the DPK Setup Script to Install PS_HOME Only

•

Obtaining Operating System Packages Required by Puppet

•

Deploying the PeopleTools Client DPK

Task 2-1: Obtaining the PeopleSoft PeopleTools DPKs

This section discusses:

•

Obtaining the PeopleSoft PeopleTools DPKs from My Oracle Support

•

Obtaining the PeopleSoft PeopleTools DPKs from Oracle Software Delivery Cloud

• Reviewing the PeopleSoft PeopleTools DPKs

Task 2-1-1: Obtaining the PeopleSoft PeopleTools DPKs from My Oracle

Support

The PeopleSoft PeopleTools patches are available on My Oracle Support. Contact Oracle if you need a user ID

and password for My Oracle Support.

To locate and download the DPKs:

1. Go to the PeopleSoft PeopleTools Patches Home Page, My Oracle Support, Doc ID 2062712.2, to find the

information on locating and downloading the latest PeopleSoft PeopleTools patch.

This page includes documentation and links to the most recent patches. To find earlier PeopleSoft

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

PeopleTools patches:

a. Sign in to My Oracle Support.

b. Select the Patches & Updates tab.

c. Select Product or Family (Advanced), and search for PeopleSoft PeopleTools.

2. Download the DPK zip files into a single directory, referred to in this documentation as DPK_INSTALL.

Be sure that the DPK_INSTALL directory has adequate available space for all the zip files. When you

download, there will probably be multiple zip files. The multiple files are needed due to size limitations.

This documentation typically refers to the downloaded zip files as FILENAME_#ofn.zip. The filename syntax

is described in following section.

Task 2-1-2: Obtaining the PeopleSoft PeopleTools DPKs from Oracle

Software Delivery Cloud

At the general availability date for PeopleSoft PeopleTools 8.57 for on premises installations, you can obtain the

PeopleSoft PeopleTools DPKs from Oracle Software Delivery Cloud. Later patches are available only on My

Oracle Support. To obtain the PeopleSoft PeopleTools DPKs from Oracle Software Delivery Cloud:

1. Sign in to Oracle Software Delivery Cloud.

See Oracle Software Delivery Cloud, https://edelivery.oracle.com.

2. Search for PeopleSoft PeopleTools release.

3. Select your operating system from the Platform list, and click Search.

4. Click Continue twice.

5. Review and accept the terms and conditions.

6. Download the DPK zip files, for example V123456-0#.zip, into a single directory, referred to in this

documentation as DPK_INSTALL.

Be sure that the DPK_INSTALL directory has adequate available space for all the zip files. When you

download, there will probably be multiple zip files. The multiple files are needed due to size limitations.

This documentation typically refers to the downloaded zip files as FILENAME_#ofn.zip. The filename syntax

is described in the next section.

Task 2-1-3: Reviewing the PeopleSoft PeopleTools DPKs

The PeopleSoft PeopleTools DPKs are delivered for each PeopleTools patch on My Oracle Support. The files are

double-zipped. This table describes the downloaded zip files and the embedded zip files. Be sure to review the

instructions in this documentation before unzipping the files.

Downloaded Zip Files* Embedded Zip Files Description

PEOPLETOOLS-

<OS>

<Rel.Patch>

_1of4.zip

The setup folder, including the setup

script and other files.

Setup DPK

PEOPLETOOLS-

<OS>

<Rel.Patch>

_2of4.zip

PT-DPK-

<OS>

<Rel.Patch>

-1of2.zip PeopleTools server, Part 1

PEOPLETOOLS-<OS>-<Rel.Patch>

_3of4.zip

PT-DPK-<OS>-<Rel.Patch>-2of2.zip PeopleTools server, Part 2

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

Downloaded Zip Files* Embedded Zip Files Description

PEOPLETOOLS-<OS>-<Rel.Patch>

_4of4.zip

PTC-DPK-<OS>-<Rel.Patch>-

1of1.zip

PeopleTools Client for 8.57

* This refers to the name of the files downloaded from My Oracle Support.

The zip files have the following format:

PEOPLETOOLS-<OS>-<Rel.Patch>_#ofn.zip

For example:

PEOPLETOOLS-WIN-8.57.04_1of4.zip

The files names are comprised of the following parts:

• <OS> is one of these operating systems:

• AIX for IBM AIX

• HPI for HP-UX

• LNX for Linux

• SOL for Oracle Solaris

• WIN for Microsoft Windows

• <Rel.Patch> is the release and patch number for the product, such as 8.57.04.

• n represents the total number of zip files.

Task 2-2: Reviewing the DPK Setup Script Options

This section discusses:

•

Using the DPK Setup Script Options

•

Preparing to Run the DPK Setup Script

Task 2-2-1: Using the DPK Setup Script Options

The PeopleSoft PeopleTools DPK setup script alleviates the installation process by automating most of the

manual tasks on a virtual or bare-metal host running a supported operating system. By convention, the setup DPK

is the first zip file (FILENAME_1ofn.zip) in the group of PeopleSoft DPK zip files you download from My Oracle

Support.

The DPK setup zip file includes two scripts, a Microsoft Windows script (psft-dpk-setup.bat) and a shell script for

Linux, AIX, HP-UX, or Solaris (psft-dpk-setup.sh). To set up a PeopleSoft environment, run the script pertinent

to the host operating system (OS) platform on which the DPK setup script is invoked. The DPK setup script offers

a variety of options for setting up mid-tier components, PS_HOME folder, and PeopleSoft domains, depending

upon the options you supply. The script is an interactive script that detects the downloaded DPKs and verifies that

they are correct. It also prompts the user for input, and once that information is gathered, will set up a complete

functional PeopleSoft mid-tier environment connecting to an existing PeopleSoft database.

Note. The DPK setup script does not provide any default passwords. It is a good idea to be prepared to supply

passwords such as user ID, PeopleSoft Connect ID, Application Server Domain Connection, and so on.

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

The following table lists the options available for the DPK setup script, psft-dpk-setup.bat for Microsoft Windows

and psft-dpk-setup.sh for Linux, AIX, HP-UX, or Solaris. The suffix <ext> in the table refers to the operating

system specific extension.

See the section Preparing to Deploy with a Non-Root User for additional script options.

Note that the command options require two dashes when running on Microsoft Windows, Linux, AIX, HP-UX, or

Solaris.

Note. The commands in the table include line feeds to improve readability.

Deployment DPK Setup Script Command

Perform the following:

• Install the software required for the mid-tier

components, including Oracle Tuxedo, Oracle

WebLogic, and Oracle database client.

• Deploy and set up the domains for the mid-tier

components (Application Server, web server, Process

Scheduler and Oracle database client).

The deployment sets up one each of Application Server,

web server, and Process Scheduler domains.

• Install the PS_HOME directory.

psft-dpk-setup.<ext>

--env_typemidtier

psft-dpk-setup.<ext>

--env_typemidtier

--domain_typeall

Perform the following:

• Install the software required for the mid-tier

components, including Oracle Tuxedo, Oracle

WebLogic and Oracle database client, without setting up

the mid-tier domains.

• Install the PS_HOME directory.

*There is additional information following this table.

psft-dpk-setup.<ext>

--env_typemidtier

--deploy_only

psft-dpk-setup.<ext>

--env_typemidtier

--deploy_only

--deploy_typeall

Deploy the PS_HOME directory only.

This option does not set up any domains.

*There is additional information following this table.

psft-dpk-setup.<ext>

--env_typemidtier

--deploy_only

--deploy_typetools_home

Deploy and set up the domain for the Application Server

only.

psft-dpk-setup.<ext>

--env_typemidtier

--domain_typeappserver

Deploy and set up the domain for the Process Scheduler

only.

psft-dpk-setup.<ext>

--env_typemidtier

--domain_typeprcs

Deploy and set up the domain for PIA only.

Note. Before beginning the PIA domain deployment, ensure

that application server and Process Scheduler domains are

available.

psft-dpk-setup.<ext>

--env_typemidtier

--domain_typepia

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

Deployment DPK Setup Script Command

Deploy and set up the domains for the Application Server

and the Process Scheduler.

psft-dpk-setup.<ext>

--env_typemidtier

--domain_typeappbatch

Specify the full path of the downloaded DPKs.

The script assumes that the downloaded DPKs are in the

parent directory of the DPK setup script. If the DPKs are

located in a different directory, use this option.

psft-dpk-setup.<ext>

--env_typemidtier

--dpk_src_dir<full_DPK_path>

Remove a deployed environment.

See "Using and Maintaining the PeopleSoft Environment,"

Removing a Deployed PeopleSoft Environment.

psft-dpk-setup.<ext>

--cleanup

List the DPK setup script usage.

psft-dpk-setup.<ext>--help

See the section Preparing to Deploy with a Non-Root User for additional script options.

The following options are also available for the PeopleSoft Application Images. These options require the

presence of PeopleSoft application DPK zip files in the deployment folder. If DPK_INSTALL includes only the

PeopleTools DPK zip files, you cannot use these options.

See PeopleSoft 9.2 Application Installation for your database platform.

Deployment with PeopleSoft Application DPKs Present DPK Setup Script Command

Deploy the PS_APP_HOME directory only.

This option does not set up any domains.

*There is additional information following this table.

psft-dpk-setup.<ext>

--env_typemidtier

--deploy_only

--deploy_typeapp_home

Deploy the PS_HOME and PS_APP_HOME directories

only.

This option does not set up any domains.

*There is additional information following this table.

psft-dpk-setup.<ext>

--env_typemidtier

--deploy_only

--deploy_typeapp_and_tools_home

* When you use the --deploy_only options on Linux, AIX, HP-UX, or Solaris operating systems, the

deployment does not set environment variables needed for subsequent tasks. After the deployment is complete,

you can set the environment variables using one of these methods:

• Change directory to

BASE_DIR/

pt/ps_home8.57.xx and run

../psconfig.sh

• Run the following command.

<PUPPET_DIR>/puppetapply--confdir=<BASE_DIR>/dpk/puppet

-e"include::pt_profile::pt_psft_environment"--debug--trace

--detailed-exitcodes

--logdest<DPK_INSTALL>/<log_file_name>

For Linux, PUPPET_DIR is /opt/puppetlabs/bin. For AIX, HP-UX or Solaris, PUPPET_DIR is

/opt/oracle/puppetlabs/bin.

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

Note. The command text given here includes line feeds for readability.

Task 2-2-2: Preparing to Run the DPK Setup Script

Include the following decisions in preparing to install with the DPK setup script:

• On Linux, AIX, HP-UX, or Solaris, 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, AIX, HP-UX, or Solaris

• FRESH or PUM installation type

For this documentation, select a FRESH, or new installation, which enables you to make selections for

RDBMS, Unicode, and multi-language support.

The PUM installation type is used with the PeopleSoft Update Image DPKs to create and set up a PeopleSoft

environment to be used as the source for the PeopleSoft Update Manager. If you select the PUM installation

type, the DPK setup script installs an Oracle DEMO multi-lingual database without presenting you with other

options.

See the documentation on the PeopleSoft Update Manager (PUM) Home Page, My Oracle Support, Doc ID

1641843.2.

Note. If you are using the PeopleSoft Upgrade Source DPKs to set up an environment for the Upgrade Source

database, you do not see the prompt for FRESH or PUM installation type.

• 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 Puppet apply command 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."

The following installation scenarios require manual configuration using the customizations:

•

Installing on an AIX operating system

See Reviewing the Software Requirements on AIX

See Preparing the Customization File for JDK on AIX.

• Installing on HP-UX operating system.

See Reviewing the Software Requirements on HP-UX.

See Preparing the Customization File for JDK on HP-UX.

• Connecting to a non-Oracle RDBMS platform

See Preparing the Customization File for Mid-Tier Connection to a Microsoft SQL Server Database

See Preparing the Customization File for Mid-Tier Connection to a DB2 z/OS Database

See Preparing the Customization File for Mid-Tier Connection to a DB2 for Linux, UNIX, and Windows

Database

• User IDs and password

The DPK setup script does not provide any default passwords. It is a good idea to be prepared to supply

passwords such as user ID, PeopleSoft Connect ID, Application Server Domain Connection, and so on.

• Multi-language support

You are given the option to use the DPK setup script to deploy translated files to

PS_APP_HOME

for a multi-

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

language installation.

• 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 Puppet apply command.

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, use the following steps:

1. Before running the DPK setup script, manually create the directory structure to use as PS_CUST_HOME.

See PeopleTools: System and Server Administration, "Working with PS_CUST_HOME."

2. Set the PS_CUST_HOME environment variable.

3. When you run the DPK setup script, the setup process uses the PS_CUST_HOME environment variable

for setting up the PeopleSoft domains.

Task 2-3: Deploying as a Non-Root User on Linux, AIX, HP-UX, or

Solaris

This section discusses:

• Preparing to Run the DPK Setup Script as a Non-Root User on Linux, AIX, HP-UX, or Solaris

• Running the DPK Setup Prerequisite for Linux, AIX, HP-UX, or Solaris

• Running the DPK Setup Script as a Non-Root User on Linux, AIX, HP-UX, or Solaris

Preparing to Run the DPK Setup Script as a Non-Root User on Linux, AIX,

HP-UX, or Solaris

Review the information in this section before deploying on Linux, AIX, HP-UX, or Solaris. You have the option

of downloading the DPK zip files and deploying the PeopleSoft environment as a non-root user. The non-root

user owns all of the deployed environment, including PS_HOME and PS_CFG_HOME.

To run the DPK setup script as a non-root user, fulfill the following requirements:

•

You can use an existing non-root user account. It is not necessary to create a new user.

•

The deployment supports only a single non-root user who deploys into a single

BASE_DIR.

•

The non-root user's home directory must be writable.

•

The non-root user must be configured to use the Bash, Bourne, or Korn shell.

•

The non-root user must have permission to read and execute the

DPK_INSTALL

folder and its contents,

including the downloaded zip files, and

DPK_INSTALL/

setup.

If the root user downloads the DPK zip files and saves them in

DPK_INSTALL,

the root user must ensure that

the necessary permissions are granted to allow the non-root user to read and execute the files.

•

Before a non-root user deploys the PeopleSoft environment, the root user must perform a prerequisite task.

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

Note. The log files for the non-root deployment are saved in <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. For example, if the home directory for the root user is /root, when the root user runs the step ./psft-dpk-

setup.sh -–prereq the log file is saved in /root/psft_dpk_work/psft_dpk_setup_1234.log. If the home

directory for the non-root user is /home/psft_user, the log file when the non-root user runs ./psft-dpk-

setup.sh -–midtier is /home/psft_user/psft_dpk_work_5678.log.

The following table lists the high-level steps required to deploy a PeopleSoft environment by a non-root user,

with a root user performing a prerequisite. The table uses a mid-tier deployment as an example, but the process

also applies to other deployments, such as deploying full-tier, or deploying PeopleSoft domains only, and so on.

Note. The commands in the table include line feeds to improve readability.

Step Number Reference Comment

1. Obtain DPKs and extract the first zip

file.

Obtaining the PeopleSoft PeopleTools

DPKs

2. Select one of these commands to run.

• To install Puppet only:

./psft-dpk-setup.sh

--prereq

• To install Puppet and set system

configuration parameters:

./psft-dpk-setup.sh

--prereq

--syscfg

Running the DPK Setup Prerequisite

for Linux, AIX, HP-UX, or Solaris

Important! This step must be run by

the root user.

This action is required once for each

host.

3. Run the DPK setup script; for

example:

./psft-dpk-setup.sh

--env_typemidtier

Running the DPK Setup Script as a

Non-Root User on Linux, AIX, HP-

UX, or Solaris

For other deployment options, see the

table in the section Using the DPK

Setup Script Options.

4. Run the command:

./psft-dpk-setup.sh

--cleanup

"Using and Maintaining the PeopleSoft

Environment," Using the DPK Setup

Script to Remove the PeopleSoft

Environment on Linux, AIX, HP-UX,

or Solaris as a Non-Root User

Run cleanup of the environment

(optional).

5. Source the script to set environment

variables:

sourceBASE_DIR/pt⇒

/psft_env.sh

"Using and Maintaining the PeopleSoft

Environment," Setting Environment

Variables for the Non-Root User on

Linux, AIX, HP-UX, or Solaris

Before using PeopleSoft utilities and

programs, source the script to set the

required environment variables.

Task 2-3-1: Running the DPK Setup Prerequisite for Linux, AIX, HP-UX, or

Solaris

This section discusses:

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

• Understanding the DPK Setup Prerequisite

• Running the DPK Setup Prerequisite to Install Puppet and Set the System Configuration

• Running the DPK Setup Prerequisite to Install Puppet

Understanding the DPK Setup Prerequisite

Before a non-root user can install the PeopleSoft environment, the root user must first run the DPK setup script to

install the Puppet software to the standard location required by the DPK setup, and optionally perform system

configuration. This prerequisite step is required only once for each host.

• To install the Puppet software and update the system configuration on the host, use the DPK setup script

command ./psft-dpk-setup.sh --prereq --syscfg.

This command installs the required Puppet software to the standard location. It also sets system configuration

variables such as kernel parameters, user and group ulimits.

• To install only the Puppet software, use the DPK setup script command ./psft-dpk-setup.sh --

prereq.

Use this command if you do not want to update the system configuration variables on your host.

Running the DPK Setup Prerequisite to Install Puppet and Set the System Configuration

To run the DPK setup script prerequisite step:

1. Open a terminal window as a user with root access, and extract the first zip file (FILENAME_1ofn.zip).

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

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

2. Change directory to DPK_INSTALL/setup.

3. Run the script as follows:

./psft-dpk-setup.sh--prereq--syscfg

4. After the script completes the Puppet software installation, log out and log in as a non-root user to deploy the

PeopleSoft environment.

Running the DPK Setup Prerequisite to Install Puppet

To install Puppet without performing system configuration:

1. Open a terminal window as a user with root access, and extract the first zip file

(FILENAME

_1ofn.zip).

The extraction creates the

DPK_INSTALL/

setup folder and other files.

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

2. Change directory to

DPK_INSTALL/

setup.

3. Run the script as follows:

./psft-dpk-setup.sh--prereq

The DPK setup log is written to the file <ROOT_HOME>/psft_dpk_work/psft_dpk_setup_<PID>.log, where

<ROOT_HOME> is the home directory for the root user running the script, and <PID> is a process ID.

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

4. After the script completes the Puppet software installation, log out and log in as a non-root user to deploy the

PeopleSoft environment.

Task 2-3-2: Running the DPK Setup Script as a Non-Root User on Linux,

AIX, HP-UX, or Solaris

After the root user completes the prerequisite, start a terminal session as a non-root user and run the DPK setup

script with the appropriate options. The following items are specific to the process when run by a non-root user.

See Reviewing the DPK Setup Script Options.

• The DPK setup script includes a prompt for PS_CFG_HOME.

The script validates whether the specified PS_CFG_HOME location is writable and has 10 GB free space.

• More than one non-root user can run the DPK setup script from the same DPK_INSTALL/setup.

• The non-root user must have permission to read and execute the DPK_INSTALL folder and its contents,

including the downloaded zip files, and DPK_INSTALL/setup.

If the root user downloads the DPK zip files and saves them in DPK_INSTALL, the root user must ensure that

the necessary permissions are granted to allow the non-root user to read and execute the files.

• The DPK 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.

Task 2-4: Running the DPK Setup Script for Mid-Tier Deployment

This section discusses:

• Understanding the Mid-Tier Deployment

• Prerequisites

• Running with the Mid-Tier Option on Microsoft Windows

• Running with the Mid-Tier Option on Linux, AIX, HP-UX, or Solaris as the Root User

• Running with the Mid-Tier Option on Linux, AIX, HP-UX, or Solaris as a Non-Root User

Understanding the Mid-Tier Deployment

Use this procedure to install the PeopleSoft mid-tier components The deployment includes the following:

• PS_HOME

installed to the default location under the DPK base directory

•

Oracle Tuxedo installed to the default location under the DPK base directory

•

Oracle WebLogic installed to the default location under the DPK base directory

•

Oracle database client installed to the default location under the DPK base directory

•

Deployed and set up PeopleSoft domains. There is a single Application Server domain, single Process

Scheduler domain, and single PIA domain.

• The Microsoft Windows DPKs include Microsoft Visual C++ Redistributable Packages for Visual Studio,

which include required Microsoft C++ runtime libraries

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

Prerequisites

Before performing the mid-tier deployment, be sure that you have fulfilled the following requirements:

• You have downloaded all of the required PeopleSoft PeopleTools DPKs, and saved them in a location

accessible to the Microsoft Windows, Linux, AIX, HP-UX, or Solaris host, referred to here as

DPK_INSTALL.

See Obtaining the PeopleSoft PeopleTools DPKs.

Note. After the DPK setup script extracts the downloaded zip files, it will delete the original zip files in

DPK_INSTALL. If you want to save the original zip files, make a backup copy in a different folder.

• Remove any previous installations of the same version of Oracle Tuxedo.

• The user running the script must have administrative permission on Microsoft Windows.

Note. Restarting services for the deployed PeopleSoft environment, such as those for Oracle Tuxedo, must be

performed by the same user (with administrative permission) who carried out the installation.

• You must have root access to deploy the PeopleSoft DPKs on Linux, AIX, HP-UX, or Solaris.

For information on non-root deployment, see the section Deploying as a Non-Root User on Linux, AIX, HP-

UX, or Solaris.

•

For deployment on Linux, AIX, HP-UX, or Solaris, there is a writable directory available for the home for the

users that own the PeopleSoft environment. The default is /home.

If you install as a non-root user, the DPK setup script uses the home directory of the logged-in user. If you do

the entire installation as root, the DPK setup script includes a prompt for the default users' home directories.

•

There is enough space on the host for the PeopleSoft environment.

See "Prerequisites," Reviewing Hardware Requirements on Microsoft Windows.

•

For deployment with the AIX or HP-UX DPK, you have installed JDK required for the operating system.

See Reviewing Software Requirements.

•

You have installed database connectivity software for the database that you want to access on the machine on

which you deploy the mid-tier components.

See "Completing the DPK Initialization with Customizations."

When installing mid-tier components for environments on Microsoft SQL Server, DB2 z/OS, or DB2 LUW,

you must use customizations to complete the installation. The delivered YAML files may not include the

necessary RDBMS client information for your environment. Create a psft_customizations.yaml file, and

include the correct client information.

See the chapter "Completing the DPK Initialization with Customizations" for information on setting up a mid-

tier connection to Microsoft SQL Server, DB2 z/OS or DB2 LUW databases.

• For all installations on DB2 z/OS or DB2 for Linux, UNIX, or Windows (DB2 LUW), you must catalog the

database before mid-tier deployment using DPKs. To catalog the database, see the documentation for DB2

z/OS or DB2 LUW for information.

• The mid-tier deployment constructs a tnsnames.ora entry for use by the PeopleSoft mid-tier components (that

is, application server and Process Scheduler) to connect to a database using SERVICE_NAME. If you plan to

connect to an Oracle database, ensure that your database can be accessed using SERVICE_NAME in the

tnsnames.ora entry.

• You have the information for the database to connect to, including:

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

• RDBMS platform

• Database name, service name, host, and listening port

• Unicode or non-Unicode database

• For DB2 z/OS or DB2 LUW, database catalog information

• You have the information for the user IDs and passwords needed for the deployment, including the following:

• PeopleSoft Connect ID and password

• PeopleSoft operator ID (such as PS or VP1) and password

• Application Server Domain Connection password (optional)

• PTWEBSERVER web profile user password

• Oracle WebLogic server administrator password

• Integration Gateway administrator

Task 2-4-1: Running with the Mid-Tier Option on Microsoft Windows

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

1. Extract the first zip file,

FILENAME

_1of

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 folder and other files.

2. Open a command prompt window with Run as Administrator.

3. Change directory to the location where you extracted the first zip file,

DPK_INSTALL/

setup.

4. Run the script with the mid-tier option to set up the Application Server, PIA, and web server mid-tier

components.

Note. If you see an error message similar to "The application has failed to start because its side-by-side

configuration is incorrect," it indicates that your machine does not include the necessary Microsoft C++

runtime libraries. Go to the Microsoft Web site, locate the Microsoft Visual C++ redistributable package for

your system, and install as directed.

•

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.

5. Wait while the script locates the valid PeopleSoft DPK 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 ].

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

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

them.

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

StartingthePeopleSoftEnvironmentSetupProcess:

ValidatingUserArguments:[OK]

ValidatingPeopleSoftSupportedPlatform:[OK]

6. Specify whether to install the Puppet software if necessary at the next prompt.

The script verifies if Puppet software is installed in the default location specified by the DPKs. If not, answer

y (yes) to install the Puppet software and n to abort the PeopleSoft environment setup process. The default

action (if nothing is entered at the prompt) is to install the software.

If there is any error during the Puppet software installation, the script aborts the setup process. Review the log

file in DPK_INSTALL/setup. If there are missing operating system packages, you will need to carry out

additional steps.

See Obtaining Operating System Packages Required for Puppet.

VerifyingifPuppetSoftwareisInstalled:[OK]

PuppetSoftwareisnotinstalledontheHost.IfthisHostis

usedtosetupaPeopleSoftenvironment,PuppetSoftwareshould

beInstalled.

DoyouwanttoInstallPuppetSoftwareonthisHost?[Y|n]:y

InstallingPuppetSoftwareontheHost:[OK]

The script verifies the eYAML software.

VerifyingifeYAMLHieraBackendisInstalled:[OK]

The script verifies if the DPKs are available in DPK_INSTALL, and aborts with the message [FAILED] if they

are not.

PreparingtheWindows2012ServerVMforPeopleSoftEnvironment:

CheckingifPeopleSoftDPKsarePresent:[OK]

7. At the following prompt, enter a location that is accessible to the host to be used as the PeopleSoft base

directory.

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

script creates the folder if it is not present.

Note. When entering the path for the base folder, use forward slashes (/). For example, C:/psft. Enclose

any names with special characters in double quotes. Do not use a name for the base folder that begins with a

number.

ThebasefolderisusedtoextractthePeopleSoftDPKs.Itisalso

usedtodeploythePeopleSoftcomponents.Thisfoldershouldbe

accessibleontheWindowsVM,musthavewritepermissionsandshould

haveenoughfreespace.

EnterthePeopleSoftBaseFolder:C:/psft

Areyouhappywithyouranswer?[Y|n|q]:

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

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.

CheckingiftheBaseFolderhasEnoughFreeSpace:[OK]

The script creates the following three sub-directories under the user provided base directory, BASE_DIR:

• 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\pt

The script uses this directory to deploy PeopleSoft components.

• BASE_DIR\db

This directory is not used for a mid-tier deployment.

8. 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.

Note. The messages have been truncated for brevity.

ValidatingthePeopleSoftDPKsintheWindowsVM:

[...]

ExtractingthePeopleSoftDPKArchivesintheWindowsVM:

[...]

9. 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 folder (BASE_DIR\dpk) and updates the YAML files to reflect the type of PeopleSoft

environment setup.

SettingupPuppetontheWindowsVM:

GeneratingeYAMLHieraBackendEncryptionKeys:[OK]

UpdatingthePuppetHieraYAMLFilesintheWindowsVM:[OK]

UpdatingtheRoleinPuppetSiteFilefortheWindowsVM:[OK]

10. Specify the installation type.

EnterthePeopleSoftinstallation[PUMorFRESH]type[PUM]:FRESH

Note. You see this prompt only when PeopleSoft application DPKs that were built on the same PeopleTools

release, are present in DPK_INSTALL.

Note. If you are using the PeopleSoft Upgrade Source Image to set up an environment for the Upgrade Source

database, you do not see this prompt.

11. Specify the information for the database that you want to connect to.

a. For the database platform, enter ORACLE, MSSQL (Microsoft SQL Server), DB2UNIX (DB2 for Linux,

UNIX, and Windows), or DB2ODBC (DB2 for z/OS).

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

EnterthePeopleSoftdatabaseplatform[ORACLE]:

b. 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]:

c. 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]:

d. Enter the database name.

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

e. 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".

EnterthePeopleSoftdatabaseservicename[HCM92]:

f. 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".

EnterthePeopleSoftdatabasehostname:

EnterthePeopleSoftdatabaseport[1521]:1521

12. Enter the PeopleSoft Connect ID at the following prompt:

The default is people.

EnteranewPeopleSoftdatabaseConnectID.EnsurethattheID

containsonlyalphanumericcharactersandisatmost8characters

inlength[people]:

13. Enter a password for the PeopleSoft Connect ID, and enter again on the next line, at the following prompt.

EnterthePeopleSoftdatabaseConnectID[people]password:Ensure

thepasswordcontainsonlyalphanumericcharactersandisbetween6

and30charactersinlength:

Re-EnterthePeopleSoftdatabaseConnectIDpassword:

14. Enter y (yes) if you want the DPK setup script to update user passwords, as described in the prompt.

Note. You see this prompt only if you specified Oracle as the PeopleSoft database platform in a previous

prompt.

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

Note:IfthePeopleSoftenvironmentissetupusingDPKsinadistributed

topologywithdbtierononehostandmidtieronanother,thePeopleSoft

applicationusers[AccessID,OperatorID,WebProfileUser]passwords

needtoberesetfromamidtierafterDBprovision.Ifthisisthefirst

midtierinstanceaccessingthedatabase,wecanautomatetheprocessof

updatingthesepasswords.

DoyouwanttoupdatetheuserpasswordsinPeopleSoftdatabase?[y|N]:N

15. Enter the password twice for the database administrator:

EnterthePeopleSoftdatabaseAdminIDpassword:

Re-EnterthePeopleSoftdatabaseAdminIDpassword:

Note. You see this prompt if you answered yes to the previous prompt for updating the user passwords, and if

you specified Oracle as the database platform.

16. Enter the PeopleSoft Operator ID (user ID) at the next prompt:

EnterthePeopleSoftdatabaseOperatorID[PS]:

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

EnteranewPeopleSoftdatabaseOperatorID[PS]password.Ensure

thepasswordcontainsonlyalphanumericcharactersandisbetween1

and32charactersinlength:

Re-EnterthePeopleSoftOperatorIDpassword:

18. Enter the password for the Access ID for the database:

EnteranewPeopleSoftdatabaseAccessID[SYSADM]password.Ensure

thepasswordcontainsonlyalphanumericcharactersandisbetween6

and30charactersinlength:

Re-EnterthePeopleSoftAccessIDpassword:

Note. You see this prompt if you answered yes to the previous prompt for updating the user passwords, and if

you specified Oracle as the database platform.

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

The window does not display masking characters as you type. There is no default password.

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thepasswordcontainsonlyalphanumericcharactersandis

between8and30charactersinlength:

Re-EntertheApplicationServerDomainconnectionpassword:

20. Enter the password for the PTWEBSERVER web profile user.

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

Note. The guideline in the prompt for the PTWEBSERVER user password does not allow special characters.

However, the PeopleSoft system does allow special characters for the PTWEBSERVER password. If you

want to change the password to include special characters, you have the option to do so in the PeopleSoft Pure

Internet Architecture (PIA) after you complete the installation and domain creation.

See PeopleTools: Security Administration, "Working with Passwords."

EnteranewPeopleSoftWebProfileuser[PTWEBSERVER]password.Ensure

thatthepasswordcontainsonlyalphanumericcharactersandisbetween

8and32charactersinlength:

Re-EnterthePeopleSoftWebProfileuserpassword:

21. 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,oneuppercaseletterandonenumber

oronespecialcharacter(!@#$%^&):

Re-EntertheWebLogicServerAdminuserpassword:

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

The default user ID is administrator.

Note. The guideline in the prompt for the Integration Gateway user ID password does not allow special

characters. However, the PeopleSoft system does allow special characters for the Integration Gateway user ID

password. If you want to change the password to include special characters, you have the option to do so in

the PeopleSoft Pure Internet Architecture (PIA) after you complete the installation and domain creation.

See PeopleTools: Security Administration, "Working with Passwords."

EnterthePeopleSoftIntegrationGatewayuser[administrator]:

EnterthePeopleSoftIntegrationGatewayuser[administrator]password.

Ensurethepasswordcontainsonlyalphanumericcharactersandis

between8and30charactersinlength:

Re-EnterthePeopleSoftIntegrationGatewayuserpassword:

23. 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]:

24. 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]

25. 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

(no) to stop the script. You must use

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

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customizationHieraYAMLfileandrunningthePuppet

'apply'commanddirectlytocontinuewiththesetupofthePeopleSoft

environment.

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

26. 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.

1.cd/dC:\psft\dpk\puppet\production\manifests

2."C:\ProgramFiles\PuppetLabs\Puppet\bin\puppet.bat"apply

--confdir=C:\psft\dpk\puppetsite.pp

--debug--trace--detailed-exitcodes

--logdest/some_valid_path/to/log/psft_dpk_setup.log

ExitingthePeopleSoftenvironmentsetupprocess.

Note. To run step 2, the puppet apply step, it is a good idea to use a log name other than psft_dpk_setup.log,

to differentiate the log from that for the DPK initialization.

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]

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

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.

Task 2-4-2: Running with the Mid-Tier Option on Linux, AIX, HP-UX, or

Solaris as the Root User

If you are installing the PeopleSoft environment as a non-root user, see the following section, Running with the

Mid-Tier Option on Linux, AIX, HP-UX, or Solaris as a Non-Root User.

To deploy mid-tier components on Linux, AIX, HP-UX, or Solaris hosts as the root user:

1. Open a terminal window and change directory to DPK_INSTALL/setup.

2. 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

• 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.sh--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 the section Reviewing the DPK Setup Script Options.

3. Wait while the script locates the valid PeopleSoft DPK 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].

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

them.

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

StartingthePeopleSoftEnvironmentSetupProcess:

ValidatingUserArguments:[OK]

ValidatingPeopleSoftSupportedPlatform:[OK]

4. Specify whether to install the Puppet software if necessary at the next prompt.

The script verifies if Puppet software is installed in the default location specified by the DPKs. If not, answer

y (yes) to install the Puppet software and n to abort the PeopleSoft environment setup process. The default

action (if nothing is entered at the prompt) is to install the software.

If there is any error during the Puppet software installation, the script aborts the setup process. Review the log

file in DPK_INSTALL/setup. If there are missing operating system packages, you will need to carry out

additional steps.

See Obtaining Operating System Packages Required for Puppet.

VerifyingifPuppetSoftwareisInstalled:[OK]

PuppetSoftwareisnotinstalledontheHost.IfthisHostis

usedtosetupaPeopleSoftenvironment,PuppetSoftwareshould

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

beInstalled.

DoyouwanttoInstallPuppetSoftwareonthisHost?[Y|n]:

InstallingPuppetSoftwareontheHost:[OK]

The script verifies the eYAML software.

VerifyingifeYAMLHieraBackendisInstalled:[OK]

The script verifies if the DPKs are available in DPK_INSTALL, and aborts with the message [FAILED] if they

are not.

PreparingtheLinuxVMforPeopleSoftEnvironment:

CheckingifPeopleSoftDPKsarePresent:[OK]

5. At the following prompt, enter 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 directory /cs1/psft is used in this example:

Note. When entering the path for the base directory, use forward slashes (/). For example, /cs1/psft. If the

name includes any non-alphanumeric characters such as periods, enclose the name in double quotes. Do not

use a name for the base directory 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ontheLinuxVM,musthavewritepermissionsandshould

haveenoughfreespace.

EnterthePeopleSoftBaseDirectory:/cs1/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 takes about 25 GB of disk space.

CheckingiftheBaseDirectoryhasEnoughFreeSpace:[OK]

The script creates the following three sub-directories under the user provided base directory, BASE_DIR:

• BASE_DIR/dpk

The script uses this directory to extract the archives from the PeopleSoft PeopleTools DPKs, and contains

the Puppet YAML files for the deployment.

• BASE_DIR/pt

The script uses this directory to deploy PeopleSoft components.

• BASE_DIR/db

This directory is not used for this deployment.

6. Specify a writable home directory for the user home directory.

The DPK setup creates local users on the host. These users deploy the PeopleSoft components and own the

PeopleSoft runtime domains. The script checks whether the default home directory for the PeopleSoft users

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

(/home) is writable. If not, it will prompt the user to enter a new location to be used for creating the home

directories for these local users.

CheckingifDefaultUserHomeDirectory/homeisWritable:[WARNING]

ThePeopleSoftenvironmentsetupcreateslocalusersontheLinuxVM.

ThedefaultHomedirectory[/home]donot

havewritepermissiontocreatetheuser'shomedirectory.Please

ensurethisdirectoryiswritableorprovideanewdirectoryonthe

LinuxVMthatiswritable.

EnteradirectoryontheLinuxVMthatiswritable[/home]:/ds1

Areyouhappywithyouranswer?[y|n|q]:

If the /home directory is writable, no response is required.

CheckingifDefaultUserHomeDirectory/homeisWritable:[OK]

7. 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.

Note. The messages have been truncated for brevity.

ValidatingthePeopleSoftDPKsintheLinuxVM:

[...]

ExtractingthePeopleSoftDPKArchivesintheLinuxVM:

[...]

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

The script sets up Puppet on the host or VM. As part of this setup, if the EYAML files are installed, it will

generate the encryption keys. 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Linux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]

9. Specify FRESH for the installation type.

EnterthePeopleSoftinstallation[PUMorFRESH]type[PUM]:FRESH

Note. You see this prompt only when PeopleSoft application DPKs that were built on the same PeopleTools

release, are present in DPK_INSTALL.

Note. If you are using the PeopleSoft Upgrade Source Image to set up an environment for the Upgrade Source

database, you do not see this prompt.

10. Specify the information for the database that you want to connect to.

a. For the database platform, enter ORACLE, DB2UNIX (DB2 for Linux, UNIX, and Windows), or

DB2ODBC (DB2 for z/OS).

EnterthePeopleSoftdatabaseplatform[ORACLE]:

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

b. 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]:

c. 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]:

d. Enter the database name.

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

e. 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".

EnterthePeopleSoftdatabaseservicename[HCM92]:

f. 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".

EnterthePeopleSoftdatabasehostname:

EnterthePeopleSoftdatabaseport[1521]:1521

11. Enter the PeopleSoft Connect ID at the following prompt:

The default is people.

EnteranewPeopleSoftdatabaseConnectID.EnsurethattheID

containsonlyalphanumericcharactersandisatmost8characters

inlength[people]:

12. Enter a password for the PeopleSoft Connect ID, and enter again on the next line, at the following prompt.

EnteranewPeopleSoftdatabaseConnectID[people]password.Ensure

thepasswordcontainsonlyalphanumericcharactersandisbetween6

and30charactersinlength:

Re-EnterthePeopleSoftdatabaseConnectIDpassword:

13. Enter

(yes) if you want the DPK setup script to update user passwords, as described in the prompt:

Note. You see this prompt only if you specified Oracle as the PeopleSoft database platform in a previous

prompt.

Note:IfthePeopleSoftenvironmentissetupusingDPKsinadistributed

topologywithdbtierononehostandmidtieronanother,thePeopleSoft

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

applicationusers[AccessID,OperatorID,WebProfileUser]passwords

needtoberesetfromamidtierafterDBprovision.Ifthisisthefirst

midtierinstanceaccessingthedatabase,wecanautomatetheprocessof

updatingthesepasswords.

DoyouwanttoupdatetheuserpasswordsinPeopleSoftdatabase?[y|N]:N

14. Enter the password twice for the database administrator:

EnterthePeopleSoftdatabaseAdminIDpassword:

Re-EnterthePeopleSoftdatabaseAdminIDpassword:

Note. You see this prompt if you answered yes to the previous prompt for updating the user passwords and if

you specified Oracle as the database platform.

15. Enter the PeopleSoft Operator ID (user ID):

EnterthePeopleSoftdatabaseOperatorID[PS]:

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

EnteranewPeopleSoftdatabaseOperatorID[PS]password.Ensure

thepasswordcontainsonlyalphanumericcharactersandisbetween1

and32charactersinlength

Re-EnterthePeopleSoftOperatorIDpassword:

17. Enter the password twice for the Access ID for the database:

EnteranewPeopleSoftdatabaseAccessID[SYSADM]password.Ensure

thepasswordcontainsonlyalphanumericcharactersandisbetween6

and30charactersinlength:

Re-EntertheAccessIDpassword:

Note. You see this prompt if you answered yes to the previous prompt for updating the user passwords and if

you specified Oracle as the database platform.

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

The window does not display masking characters as you type. There is no default password.

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thepasswordcontainsonlyalphanumericcharactersandis

between8and30charactersinlength:

Re-EntertheApplicationServerDomainconnectionpassword.

19. Enter the password twice for the PTWEBSERVER web profile user.

Note. The guideline in the prompt for the PTWEBSERVER user password does not allow special characters.

However, the PeopleSoft system does allow special characters for the PTWEBSERVER password. If you

want to change the password to include special characters, you have the option to do so in the PeopleSoft Pure

Internet Architecture (PIA) after you complete the installation and domain creation.

See PeopleTools: Security Administration, "Working with Passwords."

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

EnteranewPeopleSoftWebProfileuser[PTWEBSERVER]password.Ensure

thepasswordcontainsonlyalphanumericcharactersandisbetween

8and32charactersinlength:

Re-EnterthePeopleSoftWebProfileuserpassword:

20. 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,oneuppercaseletter,onenumberor

onespecialcharacter(!@#$%^&):

Re-EntertheWebLogicServerAdminuserpassword:

21. Enter the Integration Gateway user ID and password.

The default user ID is administrator.

Note. The guideline in the prompt for the Integration Gateway user ID password does not allow special

characters. However, the PeopleSoft system does allow special characters for the Integration Gateway

password. If you want to change the password to include special characters, you have the option to do so in

the PeopleSoft Pure Internet Architecture (PIA) after you complete the installation and domain creation.

See PeopleTools: Security Administration, "Working with Passwords."

EnterthePeopleSoftIntegrationGatewayuser[administrator]:

EnterthePeopleSoftIntegrationGatewayuser[administrator]password.

Ensurethepasswordcontainsonlyalphanumericcharactersandis

between8and30charactersinlength:

Re-EnterthePeopleSoftIntegrationGatewayuserpassword:

22. 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]:

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

If EYAML files are installed, the passwords are encrypted and updated in the YAML file.

EncryptingthePasswordsintheUserData:[OK]

UpdatingthePuppetHieraYAMLFileswithUserData:[OK]

24. If you want to continue running the initialization script using the default configuration, answer

(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

(no) to stop the script. You must use

customizations 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

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

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customizationHieraYAMLfileandrunningthePuppet

'apply'commanddirectlytocontinuewiththesetupofthePeopleSoft

environment.

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

25. 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:

SettingUpSystemSettings:[FAILED]

TheinitializationofPeopleSoftenvironmentsetupfailed.Checkthe

logfile[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.

1.cd/cs1/psft/dpk/puppet/production/manifests

2.PUPPET_DIR/puppetapply

--confdir=/cs1/psft/dpk/puppetsite.pp

--debug--trace--detailed-exitcodes

--logdest/some_valid_path/to/log/psft_dpk_setup.log

ExitingthePeopleSoftenvironmentsetupprocess.

ThePeopleSoftEnvironmentSetupProcessEnded.

Note. For Linux, PUPPET_DIR is /opt/puppetlabs/bin. For AIX, HP-UX or Solaris, PUPPET_DIR is

/opt/oracle/puppetlabs/bin.

Note. To run step 2, the puppet apply step, it is a good idea to use a log name other than psft_dpk_setup.log,

to differentiate the log from that for the DPK initialization.

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:

SettingUpSystemSettings:[OK]

DeployingPeopleToolsComponents:[OK]

DSetting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]

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

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.

Task 2-4-3: Running with the Mid-Tier Option on Linux, AIX, HP-UX, or

Solaris as a Non-Root User

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, AIX, HP-UX, or Solaris.

To deploy mid-tier components on Linux, AIX, HP-UX, or Solaris hosts as a non-root user

1. Open a terminal window and change directory to DPK_INSTALL/setup.

2. 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

•

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.sh--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 the section Reviewing the DPK Setup Script Options.

3. Answer y (yes) at the following prompt:

YouarerunningDPKsetupwithoutroot/administratoraccess.

Thisisfineaslongasthesystemadministratorhasperformed

allnecessarytasksandallprerequisiteshavebeenmet.

Pleaseseethedocumentationtodeterminetheprerequitetasks

thatneedtobeperformedtosuccessfullyrunDPKsetup

withoutroot/administratorprivilege.

Wouldyouliketoproceedwiththesetupasanon-rootuser?[y/n]:y

4. Wait while the script verifies that the necessary PeopleSoft DPK zip files are available and that the Puppet

software is installed.

The system displays messages indicating the steps in the setup process. The success or failure of each step is

indicated by [ OK ] or [FAILED].

ValidatingUserArguments:[OK]

ValidatingPeopleSoftSupportedPlatform:[OK]

VerifyingifPuppetSoftwareisinstalled:[OK]

VerifyingifeYAMLHieraBackendisInstalled:[OK]

PreparingtheRedhatLinuxVMforPeopleSoftEnvironment:

CheckingifPeopleSoftDPKsarePresent:[OK]

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

5. At the following prompt, enter 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 directory /cs1/psft is used in this example:

Note. When entering the path for the base directory, use forward slashes (/). For example, /cs1/psft. If the

name includes any non-alphanumeric characters such as periods, enclose the name in double quotes. Do not

use a name for the base directory 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ontheLinuxVM,musthavewritepermissionsandshould

haveenoughfreespace.

EnterthePeopleSoftBaseDirectory:/cs1/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 takes about 25 GB of disk space.

CheckingiftheBaseDirectoryhasEnoughFreeSpace:[OK]

The script creates the following three sub-directories under the user provided base directory,

BASE_DIR

• BASE_DIR/dpk

The script uses this directory to extract the archives from the PeopleSoft PeopleTools DPKs, and contains

the Puppet YAML files for the deployment.

• BASE_DIR/pt

The script uses this directory to deploy PeopleSoft components.

• BASE_DIR/db

This directory is not used for this deployment.

6. Enter a writable directory with at least 10 GB available space for

PS_CFG_HOME.

The default is USER_HOME/psft/pt/8.57, where USER_HOME is the home directory for the logged-in user.

The PS_CFG_HOME directory holds the configuration and log files for the PeopleSoft Application Server,

Process Scheduler, and PIA domains.

Enterawritableps_config_homedirectoryforPeopleSoftdomains

withatleast10.0GBspace[/home/psftuser/psft/pt/8.57]:

Areyouhappywithyouranswer?[Y|n|q]:y

7. 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.

Note. The messages have been truncated for brevity.

ValidatingthePeopleSoftDPKsintheLinuxVM:

[...]

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

ExtractingthePeopleSoftDPKArchivesintheLinuxVM:

[...]

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

The script sets up Puppet on the host or VM. As part of this setup, if the EYAML files are installed, it will

generate the encryption keys. 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Linux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]

9. Specify FRESH for the installation type.

EnterthePeopleSoftinstallation[PUMorFRESH]type[PUM]:FRESH

Note. You see this prompt only when PeopleSoft application DPKs that were built on the same PeopleTools

release, are present in DPK_INSTALL.

Note. If you are using the PeopleSoft Upgrade Source Image to set up an environment for the Upgrade Source

database, you do not see this prompt.

10. Specify the information for the database that you want to connect to.

a. For the database platform, enter ORACLE, DB2UNIX (DB2 for Linux, UNIX, and Windows), or

DB2ODBC (DB2 for z/OS).

EnterthePeopleSoftdatabaseplatform[ORACLE]:

b. Enter

(yes) if the database you are connecting to is a Unicode database, or

(no) for a non-Unicode

database.

IsthePeopleSoftdatabaseunicode?[Y|n]:

c. 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]:

d. Enter the database name.

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

e. 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".

EnterthePeopleSoftdatabaseservicename[HCM92]:

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

f. 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".

EnterthePeopleSoftdatabasehostname:

EnterthePeopleSoftdatabaseport[1521]:1521

11. Enter the PeopleSoft Connect ID at the following prompt:

The default is people.

EnteranewPeopleSoftdatabaseConnectID.EnsurethattheID

containsonlyalphanumericcharactersandisatmost8characters

inlength[people]:

12. Enter a password for the PeopleSoft Connect ID, and enter again on the next line, at the following prompt.

EnteranewPeopleSoftdatabaseConnectID[people]password.Ensure

thepasswordcontainsonlyalphanumericcharactersandisbetween6

and30charactersinlength:

Re-EnterthePeopleSoftdatabaseConnectIDpassword:

13. Enter

(yes) if you want the DPK setup script to update user passwords, as described in the prompt.

Note. You see this prompt only if you specified Oracle as the PeopleSoft database platform in a previous

prompt.

Note:IfthePeopleSoftenvironmentissetupusingDPKsinadistributed

topologywithdbtierononehostandmidtieronanother,thePeopleSoft

applicationusers[AccessID,OperatorID,WebProfileUser]passwords

needtoberesetfromamidtierafterDBprovision.Ifthisisthefirst

midtierinstanceaccessingthedatabase,wecanautomatetheprocessof

updatingthesepasswords.

DoyouwanttoupdatetheuserpasswordsinPeopleSoftdatabase?[y|N]:N

14. Enter the password twice for the database administrator:

EnterthePeopleSoftdatabaseAdminIDpassword:

Re-EnterthePeopleSoftdatabaseAdminIDpassword:

Note. You see this prompt if you answered yes to the previous prompt for updating the user passwords and if

you specified Oracle as the database platform.

15. Enter the PeopleSoft Operator ID (user ID):

EnterthePeopleSoftdatabaseOperatorID[PS]:

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

EnteranewPeopleSoftdatabaseOperatorID[PS]password.Ensure

thepasswordcontainsonlyalphanumericcharactersandisbetween1

and32charactersinlength

Re-EnterthePeopleSoftOperatorIDpassword:

17. Enter the password twice for the Access ID for the database: