PeopleSoft PeopleTools 8.58 Deployment Packages Installation

PeopleSoft PeopleTools 8.58

Deployment Packages Installation

July 2022

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 embedded, installed or activated on delivered hardware, and modifications of such programs) and

Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are

"commercial computer software" or "commercial computer software documentation" pursuant to the applicable

Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction,

duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i)

Oracle programs (including any operating system, integrated software, any programs embedded, installed or

activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or

iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable

contract. The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable

contract for such services. 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 Inside 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, Epyc, and the

AMD 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.

The business names used in this documentation are fictitious, and are not intended to identify any real companies

currently or previously in existence.

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 ................................................................................................................................... 11

Understanding This Documentation ...................................................................................................................... 11

Audience ................................................................................................................................................................ 11

Typographical Conventions ................................................................................................................................... 12

Products .................................................................................................................................................................. 13

Related Information ............................................................................................................................................... 14

Comments and Suggestions ................................................................................................................................... 15

Chapter 1

Prerequisites ......................................................................................................................................................... 17

Understanding the PeopleSoft PeopleTools Deployment Packages ...................................................................... 17

Reviewing Hardware Requirements ...................................................................................................................... 18

Reviewing Hardware Requirements for Microsoft Windows .......................................................................... 18

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

Reviewing Software Requirements ........................................................................................................................ 20

Reviewing Software Requirements on Microsoft Windows ............................................................................ 20

Reviewing Software Requirements on Linux ................................................................................................... 21

Reviewing Software Requirements on AIX ..................................................................................................... 22

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

Reviewing Software Requirements on Solaris ................................................................................................. 25

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

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

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

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

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

Cataloging the Database for DB2 z/OS ................................................................................................................. 32

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

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

Reviewing the sysctl Parameters ...................................................................................................................... 33

Reviewing the ulimit Parameters ...................................................................................................................... 34

Chapter 2

Deploying the PeopleSoft PeopleTools Deployment Packages ......................................................................... 35

Obtaining the PeopleSoft PeopleTools DPKs ........................................................................................................ 35

Contents

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

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

Reviewing the PeopleSoft PeopleTools DPKs ................................................................................................. 36

Using the PT-INFRA DPK for Additional Component Software ......................................................................... 37

Reviewing the DPK Setup Script Options ............................................................................................................. 38

Using the DPK Setup Script Options ................................................................................................................ 38

Using the DPK Setup Script Option use_alternate_puppet_install ................................................................... 42

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

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

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

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

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

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

Understanding the Mid-Tier Deployment ......................................................................................................... 51

Prerequisites ...................................................................................................................................................... 52

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

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

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

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

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

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

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

Solaris ............................................................................................................................................................... 73

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

Solaris ............................................................................................................................................................... 75

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

Understanding the Application Server Domain Deployment ........................................................................... 77

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

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

Solaris as the Root User .................................................................................................................................... 81

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

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

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

Understanding the Process Scheduler Domain Deployment ............................................................................ 87

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

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

Solaris as the Root User .................................................................................................................................... 91

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

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

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

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

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

Microsoft Windows .......................................................................................................................................... 98

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

Contents

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

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

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

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

Understanding the PIA Domain Deployment ................................................................................................. 107

Prerequisites for the PIA Domain Deployment .............................................................................................. 108

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

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

Root User ........................................................................................................................................................ 112

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

Root User ........................................................................................................................................................ 116

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

Understanding the PS_HOME Deployment ................................................................................................... 120

Installing PS_HOME Only on Microsoft Windows ....................................................................................... 121

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

Deploying the PeopleTools Client DPK .............................................................................................................. 127

Understanding the Standalone Mode Deployment ......................................................................................... 128

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

Deploying in Standalone Mode ...................................................................................................................... 129

Chapter 3

Deploying the PeopleSoft PeopleTools Deployment Packages in Silent Mode ............................................. 135

Understanding Silent Mode Installation ............................................................................................................... 135

Reviewing the Response File Sample for Mid-tier Installation ........................................................................... 137

Reviewing the Response File Sample for Mid-tier Installation on Microsoft Windows ................................ 137

Reviewing the Response File Sample for Mid-tier Installation as the Root User on Linux, AIX, HP-UX, or

Solaris ............................................................................................................................................................. 138

Reviewing the Response File Sample for Mid-tier Installation as a Non-Root User on Linux, AIX, HP-UX, or

Solaris ............................................................................................................................................................. 138

Reviewing the Response File Sample to Deploy an Application Server Domain ............................................... 139

Reviewing the Response File Sample to Deploy an Application Server Domain on Microsoft Windows .... 139

Reviewing the Response File Sample to Deploy an Application Server Domain on Linux, AIX, HP-UX, or

Solaris as the Root User .................................................................................................................................. 140

Reviewing the Response File Sample to Deploy an Application Server Domain on Linux, AIX, HP-UX, or

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

Reviewing the Response File Sample to Deploy a Process Scheduler Domain .................................................. 140

Reviewing the Response File Sample to Deploy a Process Scheduler Domain on Microsoft Windows ....... 141

Reviewing the Response File Sample to Deploy a Process Scheduler Domain on Linux, AIX, HP-UX, or

Solaris as the Root User .................................................................................................................................. 141

Reviewing the Response File Sample to Deploy a Process Scheduler Domain on Linux, AIX, HP-UX, or

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

Reviewing the Response File Sample to Deploy an Application Server and a Process Scheduler Domain ....... 142

Reviewing the Response File Sample to Deploy an Application Server and a Process Scheduler Domain on

Contents

Microsoft Windows ........................................................................................................................................ 142

Reviewing the Response File Sample to Deploy an Application Server and a Process Scheduler Domain on

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

Reviewing the Response File Sample to Deploy an Application Server and a Process Scheduler Domain on

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

Reviewing the Response File Sample to Deploy a PIA Domain ......................................................................... 143

Reviewing the Response File Sample to Deploy a PIA Domain on Microsoft Windows .............................. 144

Reviewing the Response File Sample to Deploy a PIA Domain on Linux, AIX, HP-UX, or Solaris as the Root

User ................................................................................................................................................................. 144

Reviewing the Response File Sample to Deploy a PIA Domain on Linux, AIX, HP-UX, or Solaris as a Non-

Root User ........................................................................................................................................................ 145

Reviewing the Response File Sample to Install PS_HOME Only ....................................................................... 145

Reviewing the Response File Sample to Install PS_HOME Only on Microsoft Windows ........................... 145

Reviewing the Response File Sample to Install PS_HOME Only on Linux, AIX, HP-UX, or Solaris ......... 146

Running the DPK Setup Script in Silent Mode for Default Initialization ............................................................ 146

Running the DPK Setup Script in Silent Mode with Customizations .................................................................. 147

Running the DPK Setup Script in Silent Mode for Default Initialization with use_alternate_puppet_install Option .

147

Running the DPK Setup Script in Silent Mode with Customizations and use_alternate_puppet_install Option . 148

Chapter 4

Completing the DPK Initialization with Customizations ............................................................................... 151

Understanding PeopleSoft Environment Customizations .................................................................................... 151

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

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

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

159

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

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

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

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

Preparing the psft_customizations.yaml File .................................................................................................. 166

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

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

Reviewing the Customization File for a Single Process Scheduler Domain .................................................. 172

Reviewing the Customization File for a Single PIA Domain ......................................................................... 173

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

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

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

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

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

Preparing the Customization File for Unicode ..................................................................................................... 184

Contents

Preparing the Customization Files for the PeopleSoft Homes ............................................................................. 185

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

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

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

Preparing the Customization File for the PS_CUST_HOME Location ......................................................... 188

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

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

Preparing the Customization File for Session Cookie Names ............................................................................. 193

Preparing the Customization File for JVM Heap Sizes ....................................................................................... 194

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

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

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

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

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

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

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

Completing the Customized Deployment ............................................................................................................ 204

Chapter 5

Using and Maintaining the PeopleSoft Environment ..................................................................................... 207

Using the PeopleSoft Installation ......................................................................................................................... 207

Accessing the PeopleSoft Environment .......................................................................................................... 207

Reviewing the Deployment File System ......................................................................................................... 208

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

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

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

Sourcing the psft_env.sh Script ..................................................................................................................... 214

Creating a psft_env.sh Script .......................................................................................................................... 215

Removing a Deployed PeopleSoft Environment ................................................................................................. 216

Understanding the Removal Process .............................................................................................................. 216

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

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

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

Non-Root User ................................................................................................................................................ 218

Using the psft_puppet_apply.cmd Script to Remove the PeopleSoft Environment on Microsoft Windows . 218

Using the psft_puppet_apply.sh Script to Remove the PeopleSoft Environment on Linux, AIX, HP-UX, or

Solaris ............................................................................................................................................................. 219

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

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

Contents

Appendix A

Applying PeopleTools Patches Using DPKs .................................................................................................... 223

Reviewing PeopleTools Patch Application Options ............................................................................................ 223

Using Scenario 1 .................................................................................................................................................. 224

Understanding Scenario 1 ............................................................................................................................... 225

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

Stopping the Services for the Domains ........................................................................................................... 225

Updating the site.pp File ................................................................................................................................. 225

Removing the Existing PeopleTools Components ......................................................................................... 226

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

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

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

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

Reviewing the Results ..................................................................................................................................... 232

Verifying the Patch Application ..................................................................................................................... 232

Using Scenario 2 .................................................................................................................................................. 233

Understanding Scenario 2 ............................................................................................................................... 233

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

Stopping the Services for the Domains ........................................................................................................... 234

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

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

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

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

Reviewing the Results ..................................................................................................................................... 240

Verifying the Patch Application ..................................................................................................................... 240

Using Scenario 3 .................................................................................................................................................. 241

Understanding Scenario 3 ............................................................................................................................... 241

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

Stopping the Services for the Domains ........................................................................................................... 242

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

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

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

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

Reviewing the Results ..................................................................................................................................... 248

Verifying the Patch Application ..................................................................................................................... 248

Appendix B

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

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

Contents

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

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

Appendix C

Installing PeopleSoft Change Assistant ............................................................................................................ 255

Understanding PeopleSoft Change Assistant ....................................................................................................... 255

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

Running the Change Assistant Setup Script with Command-Line Parameters .............................................. 257

Running the Change Assistant Setup Script with a Response File ................................................................. 258

Running the Change Assistant Setup Script Interactively to Install ............................................................... 258

Running the Change Assistant Setup Script Interactively to Upgrade ........................................................... 259

Running the Change Assistant Setup Script Interactively to Uninstall .......................................................... 260

Using Change Assistant on Linux ................................................................................................................... 261

Configuring and Using PeopleSoft Change Assistant ......................................................................................... 261

Verifying the Path Variable ............................................................................................................................ 261

Specifying Options .......................................................................................................................................... 261

Scanning the Workstation ............................................................................................................................... 262

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

Validating Change Assistant Settings .................................................................................................................. 262

Appendix D

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

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

Appendix E

Learning About the PeopleSoft Deployment Process ..................................................................................... 267

Understanding the PeopleSoft Deployment Framework ...................................................................................... 267

Understanding PeopleSoft Components .............................................................................................................. 268

Understanding Puppet and the PeopleSoft Puppet Modules ................................................................................ 269

Understanding Puppet ..................................................................................................................................... 269

Understanding Hiera ....................................................................................................................................... 270

Understanding Puppet Modules ...................................................................................................................... 270

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

Understanding PeopleSoft Puppet Component Modules ................................................................................ 272

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

Understanding Puppet Third-Party Modules .................................................................................................. 273

Understanding the Deployment Packages Uses and Contents ............................................................................. 273

Understanding How Deployment Packages are Used .................................................................................... 273

Defining the Types of Deployment Packages ................................................................................................. 274

Contents

Reviewing the PeopleSoft PeopleTools Patch DPKs ........................................................................................... 275

Reviewing the PeopleTools Client DPK .............................................................................................................. 277

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 page in the Oracle Help Center. You can also find documentation by searching for the product name

on My Oracle Support.

• PeopleSoft on the Oracle Help Center

You can access PeopleSoft Online Help, or download the PeopleBooks PDFs, from the PeopleSoft page in the

Oracle Help Center. Select PeopleTools or your PeopleSoft application from the navigation list on the left. On

the page for the selected product application, select the PeopleTools release or image number at the top and go

to the Online Help and PeopleBooks section.

See Oracle Help Center, https://docs.oracle.com/en/applications/peoplesoft/index.html.

• PeopleTools: Getting Started with PeopleTools for your release.

This documentation provides a high-level introduction to PeopleTools technology and usage.

See PeopleTools on the Oracle Help Center,

https://docs.oracle.com/en/applications/peoplesoft/peopletools/index.html.

•

PeopleSoft Application Fundamentals for your PeopleSoft Application and release

This documentation provides essential information about the setup, design, and implementation of your

PeopleSoft Application.

See Oracle Help Center, https://docs.oracle.com/en/applications/peoplesoft/index.html.

• Installation guides

You can find the installation guides for PeopleSoft PeopleTools and your PeopleSoft application on the

appropriate Oracle Help Center page. Select your release or update image at the top and then go to the Install

and Upgrade section.

• My Oracle Support

This support platform requires a user account to log in. Contact your PeopleSoft representative for

information.

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

You can find several pages which compile documentation, links, and known issues for various PeopleSoft

product areas. For a list of many of the PeopleSoft pages, select the PeopleSoft tab on the Oracle Information

Center Catalog.

See Oracle Information Center Catalog, My Oracle Support, Doc ID 50.2.

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 Oracle Help Center, https://docs.oracle.com/en/.

Preface

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 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

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"

Install updated supporting software, such as Oracle

WebLogic and others, using the PT-INFRA DPK.

"Deploying the PeopleSoft PeopleTools Deployment

Packages," Using the PT-INFRA DPK for Additional

Component Software

Prerequisites Chapter 1

For information about this topic: See this section:

Methods for using the DPKs for patching a PeopleSoft

PeopleTools 8.58 release

"Applying PeopleTools Patches Using DPKs"

How to perform a PeopleTools-only upgrade to PeopleSoft

PeopleTools 8.58.xx, using the PeopleSoft PeopleTools

DPKs.

"Performing a PeopleTools-Only Upgrade Using the

PeopleSoft PeopleTools DPKs"

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

Note. Beginning with PeopleSoft PeopleTools 8.58.20, only the PeopleSoft Relocatable Puppet is used for

deployment on all the supported operating systems and the option --use_alternate_puppet_install is

no longer needed. See the information in the software requirements sections.

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.

Chapter 1 Prerequisites

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

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

•

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.

For full-tier installations on Linux, the minimum version is Oracle Linux 7.6.

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.

Prerequisites Chapter 1

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.

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

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.

Chapter 1 Prerequisites

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:

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

• Python 3.7.4 is included with the DPKs.

• Microsoft Visual C++ Redistributable files

The current PeopleSoft PeopleTools release was developed using Microsoft Visual Studio 2017. PeopleSoft

PeopleTools programs require Microsoft Visual C++ Redistributable for Visual Studio 2017 files to be present

or the programs will not run. The required Visual C++ Redistributable for Visual Studio 2017 packages are

installed by the DPK setup script. After you have completed the PeopleSoft installation, if necessary, you can

install the files from PS_HOME\setup\psvccrt.

•

Specifying PS_APP_HOME

The DPK setup script creates the installation location for the PeopleSoft application files, PS_APP_HOME, in

a default location. If you want to use an existing PS_APP_HOME, or specify a non-default location, follow

the instructions to perform the deployment using the DPK customizations.

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

PeopleSoft Homes.

• Specifying PS_CUST_HOME

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

deployment using the DPK customizations, and specify the PS_CUST_HOME location.

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

PeopleSoft Homes.

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.

• Verify the umask value.

For a default deployment (that is, with no customizations) run by the root user, the DPK setup script uses the

system umask value when it creates users (for example, psadm1, psadm2, and psadm3) and user home

directories. Be sure that the umask value allows the DPK-created users the necessary access to the user home

directories and other directories they need to use.

See Using the PeopleSoft Installation.

• If you are installing the PeopleSoft DPKs on a supported version of Oracle Linux with Unbreakable

Prerequisites Chapter 1

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_APP_HOME

The DPK setup script creates the installation location for the PeopleSoft application files, PS_APP_HOME, in

a default location. If you want to use an existing PS_APP_HOME, or specify a non-default location, follow

the instructions to perform the deployment using the DPK customizations.

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

PeopleSoft Homes.

• Specifying PS_CUST_HOME

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

deployment using the DPK customizations, and specify the PS_CUST_HOME location.

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

PeopleSoft Homes.

• Python 3.7.4 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.

• Verify the umask value.

For a default deployment (that is, with no customizations) run by the root user, the DPK setup script uses the

system umask value when it creates users (for example, psadm1, psadm2, and psadm3) and user home

directories. Be sure that the umask value allows the DPK-created users the necessary access to the user home

directories and other directories they need to use.

See Using the PeopleSoft Installation.

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

Chapter 1 Prerequisites

Note. Beginning with PeopleSoft PeopleTools 8.58.09, only the Relocatable Puppet is used for deployment on

AIX, and it includes OpenSSL. You do not have to do the separate installation.

See the section Reviewing Requirements for the Puppet Software on AIX.

• 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_APP_HOME

The DPK setup script creates the installation location for the PeopleSoft application files,

PS_APP_HOME,

a default location. If you want to use an existing

PS_APP_HOME,

or specify a non-default location, follow

the instructions to perform the deployment using the DPK customizations.

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

PeopleSoft Homes.

•

Specifying PS_CUST_HOME

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

deployment using the DPK customizations, and specify the PS_CUST_HOME location.

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

PeopleSoft Homes.

• Python 3.7.4 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

Prerequisites Chapter 1

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

• Verify the umask value.

For a default deployment (that is, with no customizations) run by the root user, the DPK setup script uses the

system umask value when it creates users (for example, psadm1, psadm2, and psadm3) and user home

directories. Be sure that the umask value allows the DPK-created users the necessary access to the user home

directories and other directories they need to use.

See Using the PeopleSoft Installation.

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

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.

Note. Beginning with PeopleSoft PeopleTools 8.58.20, only the Relocatable Puppet is used for deployment on

HP-UX, and it includes OpenSSL. You do not have to do the separate installation.

See the section Reviewing Requirements for the Puppet Software on HP-UX.

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 8.0 for your HP-UX operating system.

Note. Beginning with PeopleSoft PeopleTools 8.58.06, you can use the latest JDK/JRE 8.0 for HP-UX.

Chapter 1 Prerequisites

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_APP_HOME

The DPK setup script creates the installation location for the PeopleSoft application files, PS_APP_HOME, in

a default location. If you want to use an existing PS_APP_HOME, or specify a non-default location, follow

the instructions to perform the deployment using the DPK customizations.

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

PeopleSoft Homes.

• Specifying PS_CUST_HOME

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

deployment using the DPK customizations, and specify the PS_CUST_HOME location.

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

PeopleSoft Homes.

• Python 3.7.4 is included with the DPKs.

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.

• Verify the umask value.

For a default deployment (that is, with no customizations) run by the root user, the DPK setup script uses the

system umask value when it creates users (for example, psadm1, psadm2, and psadm3) and user home

directories. Be sure that the umask value allows the DPK-created users the necessary access to the user home

directories and other directories they need to use.

See Using the PeopleSoft Installation.

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

Prerequisites Chapter 1

Note. Beginning with PeopleSoft PeopleTools 8.58.20, only the Relocatable Puppet is used for deployment on

Solaris, and it includes OpenSSL. You do not have to do the separate installation.

See the section Reviewing Requirements for the Puppet Software on Solaris.

• Specifying PS_APP_HOME

The DPK setup script creates the installation location for the PeopleSoft application files, PS_APP_HOME, in

a default location. If you want to use an existing PS_APP_HOME, or specify a non-default location, follow

the instructions to perform the deployment using the DPK customizations.

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

PeopleSoft Homes.

• Specifying PS_CUST_HOME

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

deployment using the DPK customizations, and specify the PS_CUST_HOME location.

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

PeopleSoft Homes.

• Python 3.7.4 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.

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

Modules.

•

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.5.14 (open source, and stand-alone architecture)

• Hiera 3.4.6

• Facter 2.5.1

•

Ruby 2.4.6

• The Puppet installation location depends upon the patch level.

Beginning with PeopleSoft PeopleTools 8.58.20, the DPK setup script installs open-source Puppet software

that has been modified for the PeopleSoft installation. This method, referred to as Relocatable Puppet, installs

the Puppet software by default in the location specified by the DPK setup script, BASE_DIR/

psft_puppet_agent.

For PeopleTools 8.58.19 and previous patch releases, the DPK setup script installs Puppet software in

C:\Program Files\Puppet Labs\Puppet by default. The previous patch releases install the open-source version

that is packaged by Puppet.

• Puppet installation location

• You have the option to use a command-line parameter to install to a non-default location, including drives

other than the C: drive.

You can install in any writable local drive, but you cannot install in a network drive.

Chapter 1 Prerequisites

Note. This command is not valid for Microsoft Windows installations on PeopleSoft PeopleTools 8.58.20

and later, which install the Relocatable Puppet for the deployment.

See "Deploying the PeopleSoft PeopleTools Deployment Packages, "Reviewing the DPK Setup Script

Options.

• You can only specify a non-default location by using the command-line location when running the script.

• Whether you accept the default installation location, or specify a different location on the command line,

the Puppet installation location is set in the Microsoft Windows registry.

• Running the DPK setup script with an existing Puppet installation

Note. This does not apply to Microsoft Windows installations on PeopleTools 8.58.20 and later, which install

the Relocatable Puppet for the deployment. The Relocatable Puppet is the only Puppet software shipped with

the DPK.

•

If you run the DPK setup script on a host with an existing Puppet installation, the script gets the Puppet

location from the Microsoft Windows registry.

If the existing Puppet is a lower version than that packaged with the DPKs, the script asks whether to keep

the existing Puppet or install the version packaged with the DPK.

• If you respond that you want to install the version packaged with the DPK, it will install in the default

location, C:\Program Files\Puppet Labs\Puppet.

This is true whether or not you installed Puppet previously to a non-default location using the command-

line option. That is, you cannot specify a different installation location after you start running the script.

• If you answer that you do not want to install the version packaged with the DPK, the script continues

without installing the Puppet that is provided with the DPKs.

Note that Oracle recommends that you use the Puppet version that is packaged with the DPK.

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.

Note. Beginning with PeopleSoft PeopleTools 8.58.19, it is not necessary for the root user to run a prereq step

on Linux. The DPK setup script installs the Relocatable Puppet software in BASE_DIR/psft_puppet_agent by

default.

Prerequisites Chapter 1

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.

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

PeopleSoft DPKs on Linux operating systems:

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

• Hiera 3.4.6

• Facter 2.5.1

• Ruby 2.4.6

• The Puppet installation location depends upon the patch level.

Beginning with PeopleSoft PeopleTools 8.58.19, the DPK setup script installs open-source Puppet software

that has been modified for the PeopleSoft installation. This method, referred to as Relocatable Puppet, installs

the Puppet software by default in the location specified by the DPK setup script, BASE_DIR/

psft_puppet_agent.

For PeopleTools 8.58.18 and previous patch releases, the DPK setup script installs Puppet software in

/opt/oracle/puppetlabs by default. The previous patch releases install the open-source version that is packaged

by Puppet.

• Running the DPK setup script with an existing Puppet installation

Note. This does not apply to Linux installations on PeopleTools 8.58.19 and later, which install the

Relocatable Puppet for the deployment. The Relocatable Puppet is the only Puppet software shipped with the

DPK.

•

If you run the DPK setup script on a host with an existing Puppet installation, the script searches for

Puppet in standard installation locations.

If the existing Puppet is a lower version than that packaged with the DPKs, the script asks whether to keep

the existing Puppet or install the version packaged with the DPK.

• If you respond that you want to install the version packaged with the DPK, it will install in the default

location, /opt/puppetlabs/puppet/bin.

•

If you answer that you do not want to install the version packaged with the DPK, the script continues

without installing the Puppet that is provided with the DPKs.

Note that Oracle recommends that you use the Puppet version that is packaged with the DPK.

See Also

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

Chapter 1 Prerequisites

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.

Note. Beginning with PeopleSoft PeopleTools 8.58.09, it is not necessary for the root user to run a prereq step

on AIX. The DPK setup script installs the Relocatable Puppet software in BASE_DIR/psft_puppet_agent by

default.

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/oracle/puppetlabs/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.

• 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.5.14 (open source, and stand-alone architecture)

• Hiera 3.4.6

•

Facter 2.5.1

•

Ruby 2.4.6

• The Puppet installation location on AIX depends upon the patch level.

Beginning with PeopleSoft PeopleTools 8.58.09, the DPK setup script installs open-source Puppet software

that has been modified for the PeopleSoft installation. This method, referred to as Relocatable Puppet, installs

the Puppet software by default in the location specified by the DPK setup script, BASE_DIR/

psft_puppet_agent.

For PeopleTools 8.58.08 and previous patch releases, the DPK setup script installs Puppet software in

/opt/oracle/puppetlabs by default. The previous patch releases install the open-source version that is packaged

by Puppet.

• Running the DPK setup script with an existing Puppet installation

Note. This does not apply to AIX installations on PeopleTools 8.58.09 and later, which install the Relocatable

Puppet for the deployment. The Relocatable Puppet is the only Puppet software shipped with the DPK.

Prerequisites Chapter 1

• If you run the DPK setup script on a host with an existing Puppet installation, the script searches for

Puppet in a standard installation locations.

If the existing Puppet is a lower version than that packaged with the DPKs, the script asks whether to keep

the existing Puppet or install the version packaged with the DPK.

• If you respond that you want to install the version packaged with the DPK, it will install in the default

location, /opt/oracle/puppetlabs.

• If you answer that you do not want to install the version packaged with the DPK, the script continues

without installing the Puppet that is provided with the DPKs.

Note that Oracle recommends that you use the Puppet version that is packaged with the DPK.

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

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.

Note. Beginning with PeopleSoft PeopleTools 8.58.20, it is not necessary for the root user to run a prereq step

on HP-UX.

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/oracle/puppetlabs/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.

• 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.5.14 (open source, and stand-alone architecture)

• Hiera 3.4.6

• Facter 2.5.1

• Ruby 2.4.6

Chapter 1 Prerequisites

• The Puppet installation location depends upon the patch level.

Beginning with PeopleSoft PeopleTools 8.58.20, the DPK setup script installs open-source Puppet software

that has been modified for the PeopleSoft installation. This method, referred to as Relocatable Puppet, installs

the Puppet software by default in the location specified by the DPK setup script, BASE_DIR/

psft_puppet_agent.

For PeopleTools 8.58.19 and previous patch releases, the DPK setup script installs Puppet software in

/opt/oracle/puppetlabs by default. The previous patch releases install the open-source version that is packaged

by Puppet.

• Running the DPK setup script with an existing Puppet installation

Note. This does not apply to HP-UX installations on PeopleTools 8.58.20 and later, which install the

Relocatable Puppet for the deployment. The Relocatable Puppet is the only Puppet software shipped with the

DPK.

• If you run the DPK setup script on a host with an existing Puppet installation, the script searches for

Puppet in a standard installation locations.

If the existing Puppet is a lower version than that packaged with the DPKs, the script asks whether to keep

the existing Puppet or install the version packaged with the DPK.

• If you respond that you want to install the version packaged with the DPK, it will install in the default

location, /opt/oracle/puppetlabs.

•

If you answer that you do not want to install the version packaged with the DPK, the script continues

without installing the Puppet that is provided with the DPKs.

Note that Oracle recommends that you use the Puppet version that is packaged with the DPK.

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.

Note. Beginning with PeopleTools 8.58.20, it is not necessary for the root user to run a prereq step on Solaris.

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/oracle/puppetlabs/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-

Prerequisites Chapter 1

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.

• 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.5.14 (open source, and stand-alone architecture)

• Hiera 3.4.6

• Facter 2.5.1

• Ruby 2.4.6

• The Puppet installation location on Solaris depends upon the patch level.

Beginning with PeopleSoft PeopleTools 8.58.20, the DPK setup script installs open-source Puppet software

that has been modified for the PeopleSoft installation. This method, referred to as Relocatable Puppet, installs

the Puppet software by default in the location specified by the DPK setup script, BASE_DIR/

psft_puppet_agent.

For PeopleTools 8.58.19 and previous patch releases, the DPK setup script installs Puppet software in

/opt/oracle/puppetlabs by default. The previous patch releases install the open-source version that is packaged

by Puppet.

• Running the DPK setup script with an existing Puppet installation

Note. This does not apply to Solaris installations on PeopleTools 8.58.20 and later, which install the

Relocatable Puppet for the deployment. The Relocatable Puppet is the only Puppet software shipped with the

DPK.

•

If you run the DPK setup script on a host with an existing Puppet installation, the script searches for

Puppet in a standard installation locations.

If the existing Puppet is a lower version than that packaged with the DPKs, the script asks whether to keep

the existing Puppet or install the version packaged with the DPK.

•

If you respond that you want to install the version packaged with the DPK, it will install in the default

location, /opt/oracle/puppetlabs.

•

If you answer that you do not want to install the version packaged with the DPK, the script continues

without installing the Puppet that is provided with the DPKs.

Note that Oracle recommends that you use the Puppet version that is packaged with the DPK.

See Also

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

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

For all installations on DB2 z/OS, you must catalog the database before mid-tier deployment using DPKs. To

catalog the database, see the documentation for DB2 z/OS for information.

Chapter 1 Prerequisites

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

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.

Prerequisites Chapter 1

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

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

•

Using the PT-INFRA DPK for Additional Component Software

•

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

•

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.58 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 the current PeopleSoft PeopleTools release.

3. In the search results, locate the PeopleSoft PeopleTools download package, and click the button to add it to

your cart.

4. Select Checkout.

5. On the Selected Software page, select your operating system from the Platforms/Languages drop-down list.

Select or clear the check boxes if you do not want all the items.

6. Click Continue.

7. Review and accept the terms and conditions.

8. 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

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

Downloaded Zip Files* Embedded Zip Files Description

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

PEOPLETOOLS-<OS>-<Rel.Patch>

_4of4.zip

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

1of1.zip

PeopleTools Client for 8.58

* 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.58.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.58.04.

•

n represents the total number of zip files.

Task 2-2: Using the PT-INFRA DPK for Additional Component

Software

The PT-INFRA DPK contains supporting (third-party) software that is required for a PeopleSoft installation. A

separate PT-INFRA DPK is delivered as needed to provide security updates or other patches for one or more of

the components. You can use this separate PT-INFRA DPK in a new installation to take advantage of up-to-date

Critical Patch Updates (CPUs).

The PT-INFRA DPK includes the following:

• Oracle Tuxedo

• Oracle WebLogic

• Oracle Database Client

• JDK and JRE

See PT-INFRA Deployment Package Installation (PeopleSoft PeopleTools 8.58), Oracle's PeopleSoft PeopleTools

8.58 Home Page, Installation and Upgrade tab, My Oracle Support, Doc ID 2602329.2.

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

Task 2-3: Reviewing the DPK Setup Script Options

This section discusses:

• Using the DPK Setup Script Options

• Using the DPK Setup Script Option use_alternate_puppet_install

• Preparing to Run the DPK Setup Script

Task 2-3-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 a script, psft-dpk-setup, that you use to set up a PeopleSoft environment. 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. This document includes several examples of using the script. In some cases the examples have been

formatted to make them easier to read. It is a good idea to type the script directly into your command or terminal

window. If you copy from this document and paste it, the pasted text may not be correct.

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.

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.

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

Solaris.

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

additional script options.

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

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

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.

Install the Oracle Tuxedo and Oracle WebLogic software.

psft-dpk-setup.<ext>

--env_typemidtier

--domain_typeappserver

Deploy and set up the domain for the Process Scheduler

only.

Install the Oracle Tuxedo and Oracle WebLogic software.

psft-dpk-setup.<ext>

--env_typemidtier

--domain_typeprcs

Deploy and set up the domain for PIA only.

Install the Oracle Tuxedo and Oracle WebLogic software.

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

Deploy and set up the domains for the Application Server

and the Process Scheduler.

Install the Oracle Tuxedo and Oracle WebLogic software.

psft-dpk-setup.<ext>

--env_typemidtier

--domain_typeappbatch

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

Deployment DPK Setup Script Command

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>

Specify the installation location for Puppet software on

Microsoft Windows.

The DPK setup script installs Puppet in C:\Program

Files\Puppet Labs\Puppet by default. Use this option to

install Puppet in a different location, including drives other

than the C: drive. You can install in any writable local drive,

but you cannot install in a network drive. Specify the full

path to the installation location. Use this option with the

desired deployment command.

Note. This command is not valid for Microsoft Windows

installations on PeopleSoft PeopleTools 8.58.20 and later,

which install the Relocatable Puppet for the deployment.

psft-dpk-setup.bat

--env_typemidtier

--puppet_win_install_dir<full_⇒

puppet_path>

Use the option --use_alternate_puppet_install to install

Puppet software under the BASE_DIR that is specified when

running the DPK setup script.

See Using the DPK Setup Script Option

use_alternate_puppet_install

Run the DPK setup script in silent mode for default

initialization.

You perform the deployment in silent mode by providing all

the required information in a response file.

See Running the DPK Setup Script in Silent Mode.

psft-dpk-setup.<ext>

--silent

--response_file=<response_file>

Run the DPK setup script in silent mode with a

customization file.

Use this command to specify a customization YAML file.

psft-dpk-setup.<ext>

--silent

--response_file=<response_file>

--customization_file=<dpk_⇒

customization_file>

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

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

Deployment DPK Setup Script Command

Reduce the size of the log file produced by the DPK setup

script by adding the nodebug option to any of the other

commands in this table.

This option turns off debug messages generated by Puppet.

Be aware that if you contact Oracle support regarding a

deployment problem, Oracle support will request the log file.

If the log file does not include the debugging messages it

may not be helpful in resolving the issue.

The log file produced when you use this option also does not

record the underlying steps performed by the Puppet lookup

with Hiera. This may also affect your debugging.

Combine the option with the other DPK setup script

commands listed in this table. Here are three examples:

psft-dpk-setup.<ext>

--env_typemidtier

--nodebug

psft-dpk-setup.<ext>

--env_typemidtier

--deploy_only

--nodebug

psft-dpk-setup.<ext>

--env_typemidtier

--domain_typeappserver

--nodebug

Specify the location for the installation log file by adding the

log_file option to any of the other commands in this table.

Combine the option with the other DPK setup script

commands listed in this table. Here are three examples:

psft-dpk-setup.<ext>

--env_typemidtier

--log_file<log file>

psft-dpk-setup.<ext>

--env_typemidtier

--deploy_only

--log_file<log file>

psft-dpk-setup.<ext>

--env_typemidtier

--domain_typeappserver

--log_file<log file>

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:

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

• Change directory to BASE_DIR/pt/ps_home8.58.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"

--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.

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

Task 2-3-2: Using the DPK Setup Script Option

use_alternate_puppet_install

Use the DPK setup script option --use_alternate_puppet_install to install Puppet software under the

BASE_DIR that is specified when running the DPK setup script. Using this script option installs the default, open-

source version that has been sufficiently modified to allow it to be installed in this non-default location.

This installation method is referred to as Relocatable Puppet. You can use this DPK setup script option for

PeopleTools patch releases that do not install Relocatable Puppet by default. If the DPK setup script does not

install Relocatable Puppet, the setup script installs the open-source version that is packaged by Puppet in

operating system-specific locations. It also sets environment variables on Linux, AIX, HP-UX, and Solaris, and

creates a registry entry on Microsoft Windows.

For AIX (beginning with PeopleTools 8.58.09), Linux (beginning with PeopleTools 8.58.19), Microsoft

Windows, HP-UX, and Solaris (beginning with PeopleTools 8.58.20) the option --

use_alternate_puppet_install is not needed, because the DPK setup script only uses the Relocatable

Puppet for the deployment.

If you are on earlier PeopleTools patch releases, you can use the --use_alternate_puppet_install

option on Linux and Microsoft Windows beginning with 8.58.01, and on AIX, HP-UX, and Solaris beginning

with 8.58.05.

•

Add this option to the command line for any supported deployment.

For example, you cannot use it to install Puppet in a separate step, followed by running the DPK setup script

for a mid-tier deployment.

•

When you use the DPK setup script to remove an environment that you deployed using

use_alternate_puppet_install

, you must include the same option in the command.

psft-dpk-setup.<ext>--use_alternate_puppet_install--cleanup

The cleanup will remove the Puppet that was installed under BASE_DIR.

• Puppet will be installed in BASE_DIR/psft_puppet_agent.

• You cannot specify a different installation location.

• The Puppet installation is deployment-specific; that is, each setup that is run with this command has its own

Puppet installation.

• The installation does not modify environment variables or the Microsoft Windows registry.

• If you are running as a non-root user Linux, AIX, HP-UX, or Solaris, and you include this option in the DPK

script commands, the root user does not need to run the prerequisite step to install Puppet or install Puppet and

system configuration first.

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

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

Note. Using the --use_alternate_puppet_install option has a different function from using the

command:

psft-dpk-setup.bat --puppet_win_install_dir <full_puppet_path>

That command is only for Microsoft Windows, requires an installation directory as input, and it does modify the

Windows registry. When you run a cleanup with the DPK setup script, the Puppet installation is not removed.

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.

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

Solaris.

Deployment DPK Setup Script Command

Perform the following:

• Install Puppet software in BASE_DIR/

psft_puppet_agent.

• 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

--use_alternate_puppet_install

psft-dpk-setup.<ext>

--env_typemidtier

--domain_typeall

--use_alternate_puppet_install

Perform the following:

• Install Puppet software in BASE_DIR/

psft_puppet_agent.

• 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

--use_alternate_puppet_install

psft-dpk-setup.<ext>

--env_typemidtier

--deploy_only

--deploy_typeall

--use_alternate_puppet_install

Install Puppet software in

BASE_DIR/

psft_puppet_agent.

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

--use_alternate_puppet_install

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

Deployment DPK Setup Script Command

• Install Puppet software in BASE_DIR/

psft_puppet_agent.

• Deploy and set up the domain for the Application Server

only.

• Install the Oracle Tuxedo and Oracle WebLogic

software.

psft-dpk-setup.<ext>

--env_typemidtier

--domain_typeappserver

--use_alternate_puppet_install

• Install Puppet software in BASE_DIR/

psft_puppet_agent.

• Deploy and set up the domain for the Process Scheduler

only.

• Install the Oracle Tuxedo and Oracle WebLogic

software.

psft-dpk-setup.<ext>

--env_typemidtier

--domain_typeprcs

--use_alternate_puppet_install

• Install Puppet software in BASE_DIR/

psft_puppet_agent.

• Deploy and set up the domain for PIA only.

• Install the Oracle Tuxedo and Oracle WebLogic

software.

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

--use_alternate_puppet_install

• Install Puppet software in BASE_DIR/

psft_puppet_agent.

• Deploy and set up the domains for the Application

Server and the Process Scheduler.

• Install the Oracle Tuxedo and Oracle WebLogic

software.

psft-dpk-setup.<ext>

--env_typemidtier

--domain_typeappbatch

--use_alternate_puppet_install

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.

Install Puppet software in

BASE_DIR/

psft_puppet_agent.

psft-dpk-setup.<ext>

--env_typemidtier

--dpk_src_dir<full_DPK_path>

--use_alternate_puppet_install

Run the DPK setup script in silent mode for default

initialization.

You perform the deployment in silent mode by providing all

the required information in a response file.

See Running the DPK Setup Script in Silent Mode.

psft-dpk-setup.<ext>

--silent

--response_file=<response_file>

--use_alternate_puppet_install

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

Deployment DPK Setup Script Command

Run the DPK setup script in silent mode with a

customization file.

Use this command to specify a customization YAML file.

psft-dpk-setup.<ext>

--silent

--response_file=<response_file>

--customization_file=<dpk_⇒

customization_file>

--use_alternate_puppet_install

Remove a deployed environment that was created using the

--use_alternate_puppet_install option.

See "Using and Maintaining the PeopleSoft Environment,"

Removing a Deployed PeopleSoft Environment.

psft-dpk-setup.<ext>

--cleanup

--use_alternate_puppet_install

Reduce the size of the log file produced by the DPK setup

script by adding the nodebug option to any of the other

commands in this table.

This option turns off debug messages generated by Puppet.

Be aware that if you contact Oracle support regarding a

deployment problem, Oracle support will request the log file.

If the log file does not include the debugging messages it

may not be helpful in resolving the issue.

The log file produced when you use this option also does not

record the underlying steps performed by the Puppet lookup

with Hiera. This may also affect your debugging.

Combine the option with the other DPK setup script

commands listed in this table. Here are three examples:

psft-dpk-setup.<ext>

--env_typemidtier

--nodebug

--use_alternate_puppet_install

psft-dpk-setup.<ext>

--env_typemidtier

--deploy_only

--nodebug

--use_alternate_puppet_install

psft-dpk-setup.<ext>

--env_typemidtier

--domain_typeappserver

--nodebug

--use_alternate_puppet_install

* 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.58.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"

--logdest<DPK_INSTALL>/<log_file_name>

For Linux,

PUPPET_DIR

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

PUPPET_DIR

/opt/oracle/puppetlabs/bin.

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

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

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

• Non-root deployment

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

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

• Default or manual configuration

After extracting the DPKs, you are given the option to exit the process, create a customization file, and

complete the configuration manually using the psft_puppet_apply script with a user-written customization file.

Use the manual configuration if you want to change installation locations and so on.

See "Completing the DPK Initialization with Customizations."

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

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

• Unicode or non-Unicode

While running the DPK setup script, you can choose to install a Unicode or non-Unicode environment.

Alternatively, specify Unicode using the customizations and psft_puppet_apply script.

See "Completing the DPK Initialization with Customizations," Preparing the Customization File for Unicode.

• Specifying PS_CUST_HOME

You may wish to set up a PS_CUST_HOME (PeopleSoft Customization Home) directory in your environment

to store your site's customized files, separate from

PS_HOME

and

PS_APP_HOME.

If you wish to use a

PS_CUST_HOME

for your environment, you must perform the deployment using the DPK customizations,

and specify the PS_CUST_HOME location.

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

PeopleSoft Homes.

Task 2-4: 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 Step for Linux, AIX, HP-UX, or Solaris

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

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

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.

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.

After the non-root user completes the deployment:

•

The non-root user owns all of the deployed environment, including PS_HOME and PS_CFG_HOME.

•

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 command ./psft-

dpk-setup.sh --prereq

, the log file is /root/psft_dpk_work/psft_dpk_setup_1234.log.

For example, if the home directory for the non-root user is /home/psft_user, when the non-root user runs

./psft-dpk-setup.sh --midtier, or another deployment command, the log file is

/home/psft_user/psft_dpk_work/psft_dpk_setup_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 step. 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 Reference Comment

1. Obtain DPKs and extract the first zip

file.

Obtaining the PeopleSoft PeopleTools

DPKs

2. Select and run one or more

prerequisite commands.

Running the DPK Setup Prerequisite

Step 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.

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

Step Reference Comment

3. Run the DPK setup script. For

example, to deploy a mid-tier

environment:

./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. If necessary, run the cleanup

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.

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

uses the script option --use_alternate_puppet_install, with a root user performing a prerequisite

step. 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 Reference Comment

1. Obtain DPKs and extract the first zip

file.

Obtaining the PeopleSoft PeopleTools

DPKs

2. Run the prerequisite command.

./psft-dpk-setup.sh

--prereq--create_⇒

central_orainv_only

Running the DPK Setup Prerequisite

Step 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, to deploy a mid-tier

environment:

./psft-dpk-setup.sh

--env_typemidtier

--use_alternate_puppet_⇒

install

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.

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

Step Reference Comment

4. If necessary, run the cleanup

command.

./psft-dpk-setup.sh

--cleanup

--use_alternate_puppet_⇒

install

"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-4-1: Running the DPK Setup Prerequisite Step for Linux, AIX, HP-

UX, or Solaris

This section discusses:

•

Understanding the DPK Setup Prerequisite Step

•

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

•

Running the DPK Setup Prerequisite Step to Install Puppet

Understanding the DPK Setup Prerequisite Step

Before a non-root user can install the PeopleSoft environment, the root user should review this section and

determine what prerequisite steps are needed.

Note. Beginning with PeopleSoft PeopleTools 8.58.09 on AIX, 8.58.19 on Linux, and 8.58.20 on HP-UX or

Solaris, the root user does not need to run the prerequisite step. The DPK setup script installs the Relocatable

Puppet software in BASE_DIR/psft_puppet_agent by default.

This table lists the prerequisite commands:

Note. The commands include line feeds for readability.

Action DPK Setup Script Command

Use this command only on Linux to install the Puppet

software and update the system configuration on the host.

This command installs the required Puppet software to the

default location. It also sets system configuration variables

such as kernel parameters, user and group ulimits.

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

--syscfg

Install only the Puppet software.

Use this command if you do not want to update the system

configuration variables on your host.

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

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

Use these guidelines in deciding which command to use:

1. Determine whether the non-root user used the --use_alternate_puppet_install option for the

deployment.

Running the DPK setup script with --use_alternate_puppet_install installs the Puppet software

under the BASE_DIR. In this case, the Puppet software is owned by the non-root user, and has the appropriate

permissions for the BASE_DIR and all its subdirectories.

See "Deploying the PeopleSoft Application Deployment Packages," Reviewing the DPK Setup Script

Options.

2. If the non-root deployment did not use the --use_alternate_puppet_install option, the root user

must run one of these prerequisite commands to install Puppet to the standard location:

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

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

3. If the non-root deployment used the --use_alternate_puppet_install option, the root user does

not have to run either of the prerequisite commands to install Puppet in step 2.

4. Whether or not the non-root deployment used the --use_alternate_puppet_install option, the

root user should run the command to create a central inventory location for the Oracle 19c Database Server

installation.

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

See "Preparing for Installation," Reviewing the Oracle Central Inventory File Location and Permissions on

Linux.

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

Configuration on Linux

The option --syscfg is supported only for Linux. To run the DPK setup script prerequisite step to install

Puppet and set the 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--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 Step 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.

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

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.

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-4-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-5: 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

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

Note. This is an Oracle 12c Database Client. The client can be used with the Oracle Database releases that are

supported for the current PeopleSoft PeopleTools release. See the Certifications for PeopleSoft PeopleTools

on My Oracle Support.

• 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

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.

If you install as a non-root user, the DPK setup script uses the home directory of the logged-in user as the

default home directory for the user, and for the deployment log files. The non-root deployment includes a

prompt for

PS_CFG_HOME.

If you do the entire installation as root, the DPK setup script creates default users, and includes a prompt for

the home directory for these generated default users. The default is /home. In this case,

PS_CFG_HOME

installed as a subdirectory of the psadm2 default user's home directory.

See "Using and Maintaining the PeopleSoft Environment," Using the PeopleSoft Installation.

•

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 or DB2 z/OS, you must use

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

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, or DB2 z/OS databases.

• For all installations on DB2 z/OS, you must catalog the database before mid-tier deployment using DPKs. To

catalog the database, see the documentation for DB2 z/OS 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:

• RDBMS platform

• Database name, service name, host, and listening port

•

Unicode or non-Unicode database

•

For DB2 z/OS, 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 and password

•

Integration Gateway keystore password

When you run the DPK setup script, the prompts for some of the passwords do not explicitly specify the

restrictions as they did in previous releases.

See E-DPK Password restrictions are not reflected in the DPK setup script prompts, My Oracle Support, Doc ID

2639270.1.

Task 2-5-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_1ofn.zip.

It is recommended that you extract into the same directory where you downloaded the zip file,

DPK_INSTALL. The extraction creates the DPK_INSTALL/setup 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.

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

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

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

(yes) to install the Puppet software and

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.

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.

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

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

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\

The script uses this directory to deploy PeopleSoft components.

• BASE_DIR\

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.

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

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 information for the database that you want to connect to.

a. For the database platform, enter ORACLE, MSSQL (Microsoft SQL Server), or DB2ODBC (DB2 for

z/OS).

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

d. Enter the database service name.

Note. The service name is required for Oracle RDBMS.

For the service name, enter the full name, including the domain, if the database was installed with the

domain. Use forward slashes if necessary. If the service name includes non-alphanumeric characters such

as periods, enclose the name in double quotes. For example, "HCM.92.example.com". Do not enter an IP

address.

EnterthePeopleSoftdatabaseservicename[HCM92]:

e. Enter the name of the host where the database is installed, and the port number:

Use forward slashes if necessary. If the host name includes non-alphanumeric characters such as periods,

enclose the name in double quotes. For example, "host.example.com". Do not enter an IP address.

EnterthePeopleSoftdatabasehostname:

EnterthePeopleSoftdatabaseport[1521]:1521

11. Enter the PeopleSoft Connect ID at the following prompt:

The default is people.

EnterthePeopleSoftdatabaseConnectID[people]:

12. Enter a password for the PeopleSoft Connect ID, and enter again on the next line, at the following prompt.

See E-DPK Password restrictions are not reflected in the DPK setup script prompts, My Oracle Support, Doc

ID 2639270.1.

EnterthePeopleSoftdatabaseConnectID[people]password.

Ensurethatthepasswordmeetsthelengthandcomplexityrequirements

foryourdatabaseplatform:

Re-EnterthePeopleSoftConnectIDpassword:

13. Enter the PeopleSoft Operator ID (user ID) at the next prompt:

EnterthePeopleSoftdatabaseOperatorID[PS]:

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

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

EnteranewPeopleSoftdatabaseOperatorID[PS]password.

Ensurethatthepasswordisbetween1and32charactersinlength.

Youmayincludethesespecialcharacters!@#$%^&:

Re-EnterthePeopleSoftOperatorIDpassword:

15. 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thatthepasswordisbetween8and30charactersinlength:

Youmayincludethesespecialcharacters!@#$%^&:

Re-EntertheApplicationServerDomainconnectionpassword:

16. Enter the password for the PTWEBSERVER web profile user.

EnteranewPeopleSoftWebProfileuser[PTWEBSERVER]password.

Ensurethatthepasswordisbetween8and32charactersinlength.

Youmayincludethesespecialcharacters!@#$%^&:

Re-EnterthePeopleSoftWebProfileuserpassword:

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

The default Oracle WebLogic server administrator is system. The window does not display masking

characters as you type. There is no default password.

EnteranewWebLogicServerAdminuser[system]password.

Ensurethatthepasswordisbetween8and30charactersinlength

withatleastonelowercaseletterandoneuppercaseletter.

Itmustalsocontainonenumberor

oneofthesespecialcharacters!@#$%^&:

Re-EntertheWebLogicServerAdminuserpassword:

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

The default user ID is administrator.

EnterthePeopleSoftIntegrationGatewayuser[administrator]:

EnterthePeopleSoftIntegrationGatewayuser[administrator]password.

Ensurethepasswordisbetween8and30charactersinlength:

Youmayincludethesespecialcharacters!@#$%^&:

Re-EnterthePeopleSoftIntegrationGatewayuserpassword:

18. Enter the Integration Gateway keystore password.

You see this prompt beginning with PeopleSoft PeopleTools 8.58.04.

See the information on using the integrationGateway.properties file and configuring security in the Integration

Broker product documentation.

See

PeopleTools: Integration Broker Administration,

"Configuring Security and General Properties."

EnterthePeopleSoftIntegrationGatewayKeystorepassword.Ensure

thepasswordisbetween8and30charactersinlength.

Youmayincludethesespecialcharacters!@#$%^&:

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

Re-EnterthePeopleSoftIntegrationGatewayKeystorepassword:

19. 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]:

20. 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]

21. If you want to continue running the initialization script using the default configuration, answer y (yes) to the

following prompt, and continue with the next step.

Note. If you select the default initialization process, the PeopleSoft environment is created with one

Application Server domain, one Process Scheduler domain, and one PIA domain.

If you want to customize the PeopleSoft environment, answer n (no) to stop the script. You must use

customizations to complete the mid-tier deployment.

ThebootstrapscriptisreadytodeployandconfigurethePeopleSoft

environmentusingthedefaultconfigurationdefinedinthePuppet

HieraYAMLfiles.Youcanproceedbyanswering'y'atthefollowing

prompt.And,ifyouwanttocustomizetheenvironmentbyoverriding

thedefaultconfiguration,youcananswer'n'.Ifyouanswer'n',you

shouldfollowtheinstructionsinthePeopleSoftInstallationGuide

forcreatingthe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]:

22. Review the status messages as the script runs Puppet profiles to set up the PeopleSoft environment.

A message of [ OK ] indicates that the profile has been applied successfully while a message [FAILED]

indicates that the profile application failed.

The script stops and exits the first time a profile application fails, and displays an error message. This example

shows the error message after the first step failed:

StartingtheDefaultInitializationofPeopleSoftEnvironment:

DeployingPeopleToolsComponents:[FAILED]

TheinitializationofPeopleSoftenvironmentsetupfailed.Checkthe

logfile[C:\DPK_INSTALL\setup\psft_dpk_setup.log]fortheerrors.

Aftercorrectingtheerrors,runthefollowingcommandstocontinue

withthesetupofPeopleSoftenvironment.

StartacmdwindowasAdministratorandrunC:\psft\psft_puppet_⇒

apply.cmd

ExitingthePeopleSoftenvironmentsetupprocess.

Upon successful completion, the DPK setup script displays the following message:

StartingtheDefaultInitializationofPeopleSoftEnvironment:

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

DeployingPeopleToolsComponents:[OK]

SettingupPeopleSoftOSUsersEnvironment:[OK]

SettingupPeopleSoftApplicationServerDomain:[OK]

SettingupPeopleSoftProcessSchedulerDomain:[OK]

SettingupPeopleSoftPIADomain:[OK]

ChangingthePasswordsfortheEnvironment:[OK]

ConfiguringPre-BootPeopleSoftEnvironment:[OK]

StartingPeopleSoftDomains:[OK]

ConfiguringPost-BootPeopleSoftEnvironment:[OK]

SettingupSourceDetailsforPeopleToolsClient:[OK]

ThePeopleSoftEnvironmentSetupProcessEnded.

The complete setup log is written to the file psft_dpk_setup.log in the same location as the DPK setup script.

Task 2-5-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

(yes) to install the Puppet software and

to abort the PeopleSoft environment setup process. The default

action (if nothing is entered at the prompt) is to install the software.

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

If there is any error during the Puppet software installation, the script aborts the setup process. Review the log

file in DPK_INSTALL/setup.

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

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.

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. Do not end the base directory name with a

forward slash (for example, do not enter /ds1/psft/).

ThebasedirectoryisusedtoextractthePeopleSoftDPKs.Itisalso

usedtodeploythePeopleSoftcomponents.Thisdirectoryshouldbe

accessible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

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

This directory is not used for this deployment.

6. Specify a writable directory for the user home directory at the following prompt.

You see this prompt beginning with PeopleSoft PeopleTools 8.58.04.

The PeopleSoft environment setup using DPKs creates local users on the host. These users deploy the

PeopleSoft components and own the PeopleSoft runtime domains. Enter a new location to be used for creating

the home directories for these local users, or specify the default home directory, /home.

EnteradirectoryontheLinuxVMthatiswritable[/home]:/ds1

Areyouhappywithyouranswer?[y|n|q]:

If the script finds that the location you enter (either a new location or the default) is not writable, it exits with

the following message.

TheUserdoesnothavewritepermissiontocreatetheuser'shome

directoryunder[<user input>]ontheLinuxVM.

ExitingthePeopleSoftenvironmentsetupprocess.

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 the information for the database that you want to connect to.

a. For the database platform, enter ORACLE 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 the database name.

EnterthePeopleSoftdatabasename:

d. Enter the database service name.

Deploying the PeopleSoft PeopleTools Deployment Packages Chapter 2

Note. The service name is required for Oracle RDBMS.

For the service name, enter the full name, including the domain, if the database was installed with the

domain. Use forward slashes if necessary. If the service name includes non-alphanumeric characters such

as periods, enclose the name in double quotes. For example, "HCM.92.example.com". Do not enter an IP

address.

EnterthePeopleSoftdatabaseservicename[HCM92]:

e. Enter the name of the host where the database is installed, and the port number:

Use forward slashes if necessary. If the host name includes non-alphanumeric characters such as periods,

enclose the name in double quotes. For example, "host.example.com". Do not enter an IP address.

EnterthePeopleSoftdatabasehostname:

EnterthePeopleSoftdatabaseport[1521]:1521

10. Enter the PeopleSoft Connect ID at the following prompt:

The default is people.

EnteranewPeopleSoftdatabaseConnectID[people]:

11. Enter a password for the PeopleSoft Connect ID, and enter again on the next line, at the following prompt.

See E-DPK - Password restrictions are not reflected in the DPK setup script prompts, My Oracle Support, Doc

ID 2639270.1

EnteranewPeopleSoftdatabaseConnectID[people]password.

Ensurethatthepasswordmeetsthelengthandcomplexityrequirements

foryourdatabaseplatform:

Re-EnterthePeopleSoftConnectIDpassword:

12. Enter the PeopleSoft Operator ID (user ID):

EnterthePeopleSoftdatabaseOperatorID[PS]:

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

EnteranewPeopleSoftdatabaseOperatorID[PS]password.

Ensurethatthepasswordisbetween1and32charactersinlength.

Youmayincludethesespecialcharacters!@#$%^&:

Re-EnterthePeopleSoftOperatorIDpassword:

14. 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isbetween8and30charactersinlength.

Youmayincludethesespecialcharacters!@#$%^&:

Re-EntertheApplicationServerDomainconnectionpassword.

15. Enter the password twice for the PTWEBSERVER web profile user.

EnteranewPeopleSoftWebProfileuser[PTWEBSERVER]password.

Ensurethatthepasswordisbetween8and32charactersinlength.

Chapter 2 Deploying the PeopleSoft PeopleTools Deployment Packages

Youmayincludethesespecialcharacters!@#$%^&:

Re-EnterthePeopleSoftWebProfileuserpassword:

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

The default Oracle WebLogic server administrator is system. The window does not display masking

characters as you type. There is no default password.

EnteranewWebLogicServerAdminuser[system]password.

Ensurethatthepasswordisbetween8and30charactersinlength

withatleastonelowercaseletterandoneuppercaseletter.

Itmustalsocontainonenumberor

oneofthesespecialcharacters!@#$%^&:

Re-EntertheWebLogicServerAdminuserpassword:

17. Enter the Integration Gateway user ID and password.

The default user ID is administrator.

EnterthePeopleSoftIntegrationGatewayuser[administrator]:

EnterthePeopleSoftIntegrationGatewayuser[administrator]password.

Ensurethepasswordisbetween8and30charactersinlength.

Youmayincludethesespecialcharacters!@#$%^&:

Re-EnterthePeopleSoftIntegrationGatewayuserpassword:

18. Enter the Integration Gateway keystore password.

You see this prompt beginning with PeopleSoft PeopleTools 8.58.04.

See the information on using the integrationGateway.properties file and configuring security in the Integration

Broker product documentation.

See

PeopleTools: Integration Broker Administration,

"Configuring Security and General Properties."

EnterthePeopleSoftIntegrationGatewayKeystorepassword.Ensure

thepasswordisbetween8and30charactersinlength.

Youmayincludethesespecialcharacters!@#$%^&:

Re-EnterthePeopleSoftIntegrationGatewayKeystorepassword:

19. 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]:

20. 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]

21. 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 n (no) to stop the script. You must use

customizations to complete the mid-tier deployment.

See "Completing the DPK Initialization with Customizations."