PeopleTools 8.55 Installation for Oracle

PeopleTools 8.55 Installation for Oracle

PeopleTools 8.55 Installation for

Oracle

December 2015

PeopleTools 8.55 Installation

for Oracle

SKU itora_December_2015

Copyright © 2015, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

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

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

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

UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

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.

Warranty Disclaimer

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.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS:

Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

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.

Third Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers 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 ................................................................................................................................. 23

Understanding This Documentation ...................................................................................................................... 23

Audience ................................................................................................................................................................ 23

Typographical Conventions ................................................................................................................................... 24

Products .................................................................................................................................................................. 25

Related Information ............................................................................................................................................... 26

Comments and Suggestions ................................................................................................................................... 26

Part I ...................................................................................................................................................................... 27

Mandatory Installation ........................................................................................................................................... 27

Chapter 1

Preparing for Installation .................................................................................................................................... 29

Understanding the PeopleSoft Installation ............................................................................................................. 29

Using Oracle Software Delivery Cloud to Obtain Installation Files ...................................................................... 31

Considering Project Planning ................................................................................................................................. 31

Planning Your Initial Configuration ...................................................................................................................... 31

Understanding Workstations ............................................................................................................................. 32

Understanding PeopleSoft Servers and Clients ................................................................................................ 33

Defining the PeopleTools Client ....................................................................................................................... 33

Defining the File Server .................................................................................................................................... 34

Defining the Database Server ........................................................................................................................... 34

Defining the Application Server ....................................................................................................................... 35

Defining the Batch Server ................................................................................................................................. 35

Defining Installation Locations ......................................................................................................................... 36

Defining the Web Server .................................................................................................................................. 39

Using Oracle Configuration Manager ............................................................................................................... 39

Using Laser Printers .......................................................................................................................................... 40

Planning Database Creation ................................................................................................................................... 40

Understanding Database Creation ..................................................................................................................... 40

Determining Databases and Database Names ................................................................................................... 41

Defining Oracle and PeopleSoft Databases ...................................................................................................... 41

Using Oracle Pluggable Databases ................................................................................................................... 42

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

5

Contents

Planning Multilingual Strategy .............................................................................................................................. 43

Understanding Multilingual Issues ................................................................................................................... 43

Choosing a Base Language ............................................................................................................................... 45

Selecting Additional Languages ....................................................................................................................... 47

Selecting a Database Character Set ................................................................................................................... 47

Preparing for the PeopleTools-Only Upgrade ........................................................................................................ 48

Understanding the PeopleTools Only Upgrade ................................................................................................ 48

Reviewing the Upgrade Documentation ........................................................................................................... 49

Shutting Down Servers ..................................................................................................................................... 49

Reviewing Customized Configuration Files ..................................................................................................... 49

Reviewing Patches and Updates Required at Installation ...................................................................................... 49

Installing Supporting Applications ........................................................................................................................ 51

Installing the Database Engine ............................................................................................................................... 52

Understanding the Database Engine ................................................................................................................. 52

Creating a Seed Database .................................................................................................................................. 52

Installing Oracle Net on the Server ........................................................................................................................ 52

Installing Oracle Net on Your Workstation ........................................................................................................... 54

Testing Oracle Net Connectivity ............................................................................................................................ 54

Performing Backups ............................................................................................................................................... 54

Using PeopleSoft Change Assistant and PeopleSoft Change Impact Analyzer .................................................... 55

Chapter 2

Installing Web Server Products .......................................................................................................................... 57

Installing Oracle WebLogic Server ........................................................................................................................ 57

Understanding the Oracle WebLogic Installation ............................................................................................. 57

Reviewing Troubleshooting Tips ...................................................................................................................... 58

Obtaining Oracle WebLogic Installation Files from Oracle Software Delivery Cloud .................................... 59

Installing JDK for Oracle WebLogic ................................................................................................................ 60

Installing Oracle WebLogic on Microsoft Windows ........................................................................................ 63

Installing Oracle WebLogic on Linux or UNIX in Silent Mode ...................................................................... 72

Configuring JDK for Daylight Savings Time Change ...................................................................................... 75

Removing the Oracle WebLogic Installation on Microsoft Windows ............................................................. 76

Removing the Oracle WebLogic Installation on Linux or UNIX ..................................................................... 79

Installing IBM WebSphere Application Server ..................................................................................................... 80

Understanding IBM WebSphere Installation .................................................................................................... 80

Prerequisites ...................................................................................................................................................... 81

Obtaining IBM WebSphere Installation Files ................................................................................................... 82

Installing IBM WebSphere 8.5.5.0 ND ............................................................................................................ 85

Installing IBM HTTP Server 8.5.5.0 ................................................................................................................ 85

Installing IBM WebSphere Plug-ins 8.5.5.0 ..................................................................................................... 85

6

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Contents

Chapter 3

Installing Additional Components ...................................................................................................................... 87

Reviewing Additional Components ....................................................................................................................... 87

Installing Oracle Tuxedo ........................................................................................................................................ 88

Understanding Oracle Tuxedo .......................................................................................................................... 88

Prerequisites ...................................................................................................................................................... 89

Debugging the Oracle Tuxedo Installer ............................................................................................................ 90

Obtaining the Oracle Tuxedo Installation Files from Oracle Software Delivery Cloud .................................. 90

Obtaining the Oracle Tuxedo Patches from My Oracle Support ...................................................................... 91

Removing Existing Oracle Tuxedo Installations from Microsoft Windows (Optional) ................................... 92

Designating the Application Server Administrator on Microsoft Windows .................................................... 93

Installing Oracle Tuxedo on Microsoft Windows in GUI Mode ...................................................................... 94

Installing the Oracle Tuxedo Patch on Microsoft Windows ........................................................................... 105

Installing Oracle Tuxedo on Microsoft Windows in Silent Mode .................................................................. 106

Uninstalling the Oracle Tuxedo Patch on Microsoft Windows ...................................................................... 108

Uninstalling Oracle Tuxedo in GUI Mode ..................................................................................................... 108

Checking the Windows Service Account ....................................................................................................... 110

Restricting Domain Process Privileges ........................................................................................................... 111

Setting Up the Windows Services for Oracle Tuxedo .................................................................................... 112

Verifying the Server Installation on Microsoft Windows ............................................................................... 114

Removing Existing Oracle Tuxedo Installations from UNIX (Optional) ....................................................... 115

Completing the Preinstallation Checklist on UNIX ........................................................................................ 115

Designating the Oracle Tuxedo Owner on UNIX ........................................................................................... 116

Installing Oracle Tuxedo in Silent Mode on UNIX ........................................................................................ 117

Installing the Oracle Tuxedo Patch on UNIX ................................................................................................. 118

Uninstalling the Oracle Tuxedo Patch from UNIX ........................................................................................ 119

Uninstalling Oracle Tuxedo from UNIX Using Silent Mode ......................................................................... 119

Verifying the Server Installation on UNIX ..................................................................................................... 120

Ensuring that Oracle Tuxedo Coexists with Earlier Versions ........................................................................ 120

Chapter 4

Using the PeopleSoft Installer ........................................................................................................................... 123

Understanding the PeopleSoft Installer ................................................................................................................ 123

Defining the PeopleSoft Installer .................................................................................................................... 123

Defining Supported Server Combinations ...................................................................................................... 124

Obtaining License Codes ................................................................................................................................ 125

Prerequisites ......................................................................................................................................................... 125

Obtaining the PeopleSoft Installation Files from Oracle Software Delivery Cloud ............................................ 126

Running the PeopleSoft Installer ......................................................................................................................... 127

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

7

Contents

Understanding the PeopleSoft Installer .......................................................................................................... 128

Starting the PeopleSoft Installer ..................................................................................................................... 128

Installing PeopleSoft PeopleTools in GUI Mode ........................................................................................... 130

Installing PeopleSoft PeopleTools in Console Mode ..................................................................................... 146

Verifying Necessary Files for Installation on Windows ...................................................................................... 151

Installing PeopleSoft Application Software ......................................................................................................... 152

Installing the Multilanguage Files ........................................................................................................................ 152

Installing the PeopleTools Client Files ................................................................................................................ 153

Installing the PeopleTools Client Files Using the PeopleSoft Installer .......................................................... 153

Installing the PeopleTools Client Files in Silent Mode .................................................................................. 153

Mapping a Drive on the Install Workstation ........................................................................................................ 154

Chapter 5

Setting Up the Install Workstation ................................................................................................................... 157

Understanding the Install Workstation ................................................................................................................. 157

Prerequisites ......................................................................................................................................................... 157

Starting Configuration Manager .......................................................................................................................... 158

Setting Startup Options ........................................................................................................................................ 158

Editing the Default Profile ................................................................................................................................... 159

Running Client Setup ........................................................................................................................................... 161

Chapter 6A

Creating a Database Manually on Windows ................................................................................................... 163

Understanding Database Creation ........................................................................................................................ 164

Preparing for the PeopleSoft Database Installation ............................................................................................. 164

Installing the PeopleSoft Database Server Components on the Database Server ........................................... 165

Installing the Oracle RDBMS Software ......................................................................................................... 165

Identifying the Oracle RDBMS Trace and Alert File Locations .................................................................... 165

Obtaining Windows Administrator Authority ................................................................................................ 166

Creating an INIT<SID>.ORA File ................................................................................................................. 166

Creating an INIT<SID>.ORA File (Multitenant Architecture) ...................................................................... 168

Creating Target Directory Paths ..................................................................................................................... 168

Creating Target Directory Paths (Multitenant Architecture) .......................................................................... 169

Setting the ORACLE_SID Environment Variable ......................................................................................... 169

Creating the Windows Service for the Database Instance ................................................................................... 170

Using SQL Tools .................................................................................................................................................. 171

Editing Database Scripts (non-Multitenant) ......................................................................................................... 171

Understanding Database Scripts ..................................................................................................................... 171

Modifying Database Scripts ............................................................................................................................ 171

Creating an Oracle Instance (non-Multitenant) .................................................................................................... 173

8

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Contents

Creating Catalog Views and Utility Tablespaces (non-Multitenant) ................................................................... 173

Creating PS.PSDBOWNER Table (non-Multitenant) ......................................................................................... 173

Creating Application-Specific Dbspaces and Tablespaces (non-Multitenant) .................................................... 174

Creating PeopleSoft Database Roles (non-Multitenant) ...................................................................................... 174

Creating the PeopleSoft Database Owner ID (non-Multitenant) ......................................................................... 174

Setting Up Connect ID (non-Multitenant) ........................................................................................................... 175

Understanding Connect ID ............................................................................................................................. 175

Understanding Connect ID and the Login Process ......................................................................................... 175

Creating the Connect ID ................................................................................................................................. 176

Editing Database Scripts (Multitenant Architecture) ........................................................................................... 176

Creating an Oracle Instance (Multitenant Architecture) ...................................................................................... 177

Creating a Root Container Database ............................................................................................................... 177

Creating a PDB ............................................................................................................................................... 178

Creating Catalog Views and Utility Tablespaces (Multitenant Architecture) ..................................................... 179

Creating PS.PSDBOWNER Table (Multitenant Architecture) ........................................................................... 179

Creating Application-Specific Dbspaces and Tablespaces (Multitenant Architecture) ....................................... 180

Creating PeopleSoft Database Roles (Multitenant Architecture) ........................................................................ 180

Creating the PeopleSoft Database Owner ID (Multitenant Architecture) ........................................................... 180

Setting Up Connect ID (Multitenant Architecture) .............................................................................................. 181

Understanding Connect ID ............................................................................................................................. 181

Understanding Connect ID and the Login Process ......................................................................................... 182

Creating the Connect ID ................................................................................................................................. 182

Updating Connection Information ....................................................................................................................... 182

Setting NLS_LANG in the Windows Registry .................................................................................................... 183

Creating Data Mover Import Scripts .................................................................................................................... 184

Understanding Data Mover Import Scripts ..................................................................................................... 184

Working with Multilingual Databases ............................................................................................................ 185

Running Database Setup to Create Data Mover Import Scripts ..................................................................... 185

Running Data Mover Import Scripts .................................................................................................................... 193

Understanding Data Mover Import Scripts ..................................................................................................... 193

Populating Tables in the PeopleSoft Database ............................................................................................... 193

Checking the Log Files and Troubleshooting ...................................................................................................... 194

Checking the Log Files ................................................................................................................................... 194

Running Data Mover ....................................................................................................................................... 194

Troubleshooting .............................................................................................................................................. 195

Improving Performance .................................................................................................................................. 196

Changing the Base Language ............................................................................................................................... 197

Chapter 6B

Creating a Database on UNIX .......................................................................................................................... 199

Understanding the Database Configuration Wizard ............................................................................................ 199

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

9

Contents

Fulfilling PeopleSoft Database Configuration Wizard Prerequisites ................................................................... 200

Installing the PeopleSoft Database Server Components on the Database Server ........................................... 200

Installing the Oracle RDBMS Software ......................................................................................................... 201

Identifying the Trace and Alert File Locations ............................................................................................... 201

Creating an INIT<SID>.ORA File ................................................................................................................. 201

Creating an INIT<SID>.ORA File (Multitenant Architecture) ...................................................................... 203

Creating Target Directory Paths ..................................................................................................................... 203

Creating Target Directory Paths (Multitenant Architecture) .......................................................................... 205

Setting Up Target Database Connectivity ....................................................................................................... 205

Running the Shell Script psconfig.sh .............................................................................................................. 205

Running the Database Configuration Wizard ...................................................................................................... 205

Checking the Log Files and Troubleshooting ...................................................................................................... 222

Checking the Log Files ................................................................................................................................... 222

Running Data Mover ....................................................................................................................................... 223

Troubleshooting .............................................................................................................................................. 225

Improving Performance .................................................................................................................................. 227

Chapter 7

Completing the Database Setup ........................................................................................................................ 229

Selecting the Necessary Tasks to Complete the Database Setup ......................................................................... 229

Reviewing Patch Application ............................................................................................................................... 229

Updating Database to Latest PeopleTools Release .............................................................................................. 230

Understanding Database Updates ................................................................................................................... 230

Cleaning Up Data ............................................................................................................................................ 231

Deleting Performance Monitor System Default Data ..................................................................................... 231

Creating New PeopleTools Tablespaces ......................................................................................................... 231

Updating PeopleTools System Tables ............................................................................................................ 232

Updating PeopleTools Database Objects ........................................................................................................ 237

Updating PeopleTools Multilingual Objects .................................................................................................. 240

Deleting Obsolete PeopleTools Database Objects .......................................................................................... 243

Applying Patched PeopleTools Database Objects .......................................................................................... 245

Altering PeopleTools Tables ........................................................................................................................... 246

Migrating Records to New Tablespaces ......................................................................................................... 249

Updating PeopleTools System Data ............................................................................................................... 255

Running PeopleTools Conversions ................................................................................................................. 258

Converting Integration Broker ........................................................................................................................ 263

Running Additional PeopleTools Conversions ............................................................................................... 266

Running Additional Data Mover Scripts .............................................................................................................. 266

Installing a Multilingual PeopleTools System Database ..................................................................................... 266

Understanding the Multilingual Database Project .......................................................................................... 266

Applying the Multilingual Database Project ................................................................................................... 267

10

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Contents

Populating the Translated System Data .......................................................................................................... 267

Running VERSION Application Engine Program ............................................................................................... 267

Running SQR Reports .......................................................................................................................................... 268

Understanding Running SQR Reports ............................................................................................................ 268

Running SQRs on the Client Workstation ...................................................................................................... 268

Creating a Shortcut to Run SQRs ................................................................................................................... 270

Checking the Database ......................................................................................................................................... 271

Running SETSPACE.SQR ................................................................................................................................... 272

Running Alter Audit ............................................................................................................................................. 273

Chapter 8A

Configuring the Application Server on Windows ........................................................................................... 279

Understanding the Application Server ................................................................................................................. 279

Prerequisites ......................................................................................................................................................... 280

Preparing the Application Server File System for a PeopleTools-Only Upgrade ............................................... 281

Setting Up COBOL for Remote Call ................................................................................................................... 281

Verifying Database Connectivity ......................................................................................................................... 281

Creating, Configuring, and Starting an Initial Application Server Domain ........................................................ 281

Creating, Configuring, and Starting the Application Server Domain ............................................................. 282

Testing the Three-Tier Connection ................................................................................................................. 285

Importing an Existing Application Server Domain Configuration ................................................................. 287

Setting Up a Custom Application Server Domain Configuration .................................................................. 289

Troubleshooting Common Errors ................................................................................................................... 292

Chapter 8B

Configuring the Application Server on UNIX ................................................................................................. 293

Understanding the Application Server ................................................................................................................. 293

Understanding the Application Server Domain Processes ................................................................................... 294

Prerequisites ......................................................................................................................................................... 294

Preparing the Application Server File System for a PeopleTools-Only Upgrade ............................................... 295

Setting Environment Variables ............................................................................................................................ 295

Setting Up COBOL for Remote Call ................................................................................................................... 296

Verifying Database Connectivity ......................................................................................................................... 296

Creating, Configuring, and Starting an Initial Application Server Domain ........................................................ 297

Creating, Configuring, and Starting the Application Server Domain ............................................................. 297

Testing the Three-Tier Connection ................................................................................................................. 300

Importing an Existing Application Server Domain Configuration ................................................................. 302

Setting Up a Custom Application Server Domain Configuration .................................................................. 304

Troubleshooting Common Errors ................................................................................................................... 306

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

11

Contents

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode ........................................................... 309

Understanding PeopleSoft Pure Internet Architecture ......................................................................................... 309

Using Authentication Domains in the PeopleSoft Pure Internet Architecture Installation .................................. 311

Preparing the PeopleSoft Pure Internet Architecture File System for a PeopleTools-Only Upgrade ................. 312

Installing the PeopleSoft Pure Internet Architecture on Oracle WebLogic in GUI Mode .................................. 312

Prerequisites .................................................................................................................................................... 313

Installing the PeopleSoft Pure Internet Architecture on a New Oracle WebLogic Domain .......................... 313

Installing the PeopleSoft Pure Internet Architecture on an Existing Oracle WebLogic Domain ................... 328

Uninstalling the PeopleSoft Pure Internet Architecture on Oracle WebLogic ............................................... 346

Installing the PeopleSoft Pure Internet Architecture on IBM WebSphere in GUI Mode .................................... 346

Prerequisites .................................................................................................................................................... 347

Installing the PeopleSoft Pure Internet Architecture on IBM WebSphere ..................................................... 347

Uninstalling the PeopleSoft Pure Internet Architecture from IBM WebSphere ............................................. 365

Testing and Administering the PeopleSoft Pure Internet Architecture Installation ............................................. 366

Verifying the PeopleSoft Pure Internet Architecture Installation ................................................................... 366

Starting and Stopping Oracle WebLogic ........................................................................................................ 367

Starting and Stopping IBM WebSphere Application Servers ......................................................................... 368

Using PSADMIN to Start and Stop Web Servers ........................................................................................... 371

Accessing the PeopleSoft Signon ................................................................................................................... 373

Completing Post-Installation Steps ...................................................................................................................... 376

Using Fluid User Interface .............................................................................................................................. 376

Updating the Installation Table ....................................................................................................................... 379

Setting Options for Multilingual Databases .................................................................................................... 380

Updating PeopleTools Options ....................................................................................................................... 381

Updating Database Information ...................................................................................................................... 381

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode ..................................................... 383

Understanding PeopleSoft Pure Internet Architecture ......................................................................................... 383

Using Authentication Domains in the PeopleSoft Pure Internet Architecture Installation .................................. 385

Preparing the PeopleSoft Pure Internet Architecture File System for a PeopleTools-Only Upgrade ................. 386

Installing the PeopleSoft Pure Internet Architecture on Oracle WebLogic in Console Mode ............................ 386

Prerequisites .................................................................................................................................................... 387

Installing the PeopleSoft Pure Internet Architecture on a New Oracle WebLogic Domain in Console Mode .

387

Installing the PeopleSoft Pure Internet Architecture on an Existing Oracle WebLogic Domain in Console

Mode ............................................................................................................................................................... 392

Uninstalling the PeopleSoft Pure Internet Architecture from Oracle WebLogic ........................................... 398

Installing the PeopleSoft Pure Internet Architecture on IBM WebSphere in Console Mode .............................. 398

12

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Contents

Prerequisites .................................................................................................................................................... 398

Installing the PeopleSoft Pure Internet Architecture on IBM WebSphere Application Server ND ............... 399

Uninstalling the PeopleSoft Pure Internet Architecture from IBM WebSphere ............................................ 403

Installing the PeopleSoft Pure Internet Architecture in Silent Mode ................................................................... 404

Understanding the Silent Installation and the Response File .......................................................................... 404

Editing the Response File ............................................................................................................................... 404

Running the Silent Mode Installation ............................................................................................................. 407

Testing and Administering the PeopleSoft Pure Internet Architecture Installation ............................................. 407

Verifying the PeopleSoft Pure Internet Architecture Installation ................................................................... 407

Starting and Stopping Oracle WebLogic ........................................................................................................ 408

Starting and Stopping IBM WebSphere Application Servers ......................................................................... 408

Using PSADMIN to Start and Stop Web Servers ........................................................................................... 411

Accessing the PeopleSoft Signon ................................................................................................................... 413

Completing Post-Installation Steps ...................................................................................................................... 416

Using Fluid User Interface .............................................................................................................................. 416

Updating the Installation Table ....................................................................................................................... 419

Setting Options for Multilingual Databases .................................................................................................... 420

Updating PeopleTools Options ....................................................................................................................... 421

Updating Database Information ...................................................................................................................... 421

Chapter 10A

Setting Up Process Scheduler on Windows ..................................................................................................... 423

Prerequisites ......................................................................................................................................................... 423

Preparing the Process Scheduler File System for a PeopleTools-Only Upgrade ................................................. 424

Setting Up Process Scheduler Security ................................................................................................................ 424

Understanding Process Scheduler Security .................................................................................................... 424

Changing User Account to Start ORACLE ProcMGR V12.1.3.0.0_VS2012 ................................................ 425

Granting Process Scheduler Administrative Rights ........................................................................................ 427

Setting Up Process Scheduler to Transfer Reports and Logs to the Report Repository ...................................... 428

Understanding Report Distribution ................................................................................................................. 429

Setting Up Single Signon to Navigate from PIA to Report Repository ......................................................... 431

Determining the Transfer Protocol ................................................................................................................. 431

Starting the Distribution Agent ....................................................................................................................... 432

Setting Up the Report Repository ................................................................................................................... 432

Setting Up the Distribution for Your Process Scheduler Server ..................................................................... 449

Setting Up Sending and Receiving of Report Folders in the Report Manager ............................................... 450

Setting Environment Variables ............................................................................................................................ 450

Setting Up Process Scheduler Server Agent ........................................................................................................ 450

Understanding Process Scheduler Server Agent ............................................................................................. 451

Creating and Configuring a Process Scheduler Server ................................................................................... 451

Reconfiguring a Process Scheduler Server ..................................................................................................... 457

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

13

Contents

Verifying the Process Scheduler Server Status ............................................................................................... 458

Starting Process Scheduler as a Windows Service (Optional) ............................................................................. 460

Configuring the Process Scheduler for Microsoft Word (Optional) .................................................................... 463

Configuring Process Scheduler ....................................................................................................................... 463

Executing Winword on Mapped Drive ........................................................................................................... 464

Configuring Setup Manager ................................................................................................................................. 465

Installing Products for PS/nVision ....................................................................................................................... 466

Understanding the PS/nVision Setup .............................................................................................................. 467

Installing Products for PS/nVision in Excel Automation Mode ..................................................................... 467

Installing Microsoft .NET Framework Products for PS/nVision .................................................................... 467

Installing Microsoft Open XML SDK for PS/nVision ................................................................................... 475

Chapter 10B

Setting Up Process Scheduler on UNIX ........................................................................................................... 481

Prerequisites ......................................................................................................................................................... 481

Preparing the Process Scheduler File System for a PeopleTools-Only Upgrade ................................................. 482

Setting Up Process Scheduler Security ................................................................................................................ 482

Understanding Process Scheduler Security .................................................................................................... 482

Granting Process Scheduler Administrative Rights ........................................................................................ 482

Setting Up Process Scheduler to Transfer Reports and Logs to the Report Repository ...................................... 484

Understanding Report Distribution ................................................................................................................. 484

Setting Up Single Signon to Navigate from PIA to Report Repository ......................................................... 486

Determining the Transfer Protocol ................................................................................................................. 486

Starting the Distribution Agent ....................................................................................................................... 487

Setting Up the Report Repository ................................................................................................................... 487

Setting Up the Distribution for Your Process Scheduler Server ..................................................................... 502

Setting Up Sending and Receiving of Report Folders in the Report Manager ............................................... 503

Setting Up Process Scheduler Server Agent ........................................................................................................ 503

Understanding Process Scheduler Server Agent ............................................................................................. 503

Changing the Default Operating System ........................................................................................................ 504

Setting Up Your Environment ........................................................................................................................ 504

Creating and Configuring a Process Scheduler Server ................................................................................... 505

Reconfiguring a Process Scheduler Server ..................................................................................................... 510

Verifying the Process Scheduler Server Status ............................................................................................... 512

Part II .................................................................................................................................................................. 515

Discretionary Installation ..................................................................................................................................... 515

14

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Contents

Chapter 11

Configuring Integration Between PeopleSoft PeopleTools and Oracle SES ................................................ 517

Understanding PeopleSoft PeopleTools and SES Integration ............................................................................. 517

Preparing for the Integration of PeopleSoft PeopleTools and SES ...................................................................... 518

Installing Oracle Secure Enterprise Search ..................................................................................................... 518

Reviewing the PeopleSoft PeopleTools Prerequisites .................................................................................... 518

Configuring SES for the Search Framework ....................................................................................................... 519

Understanding the Oracle SES Configuration ................................................................................................ 519

Creating a Federated Trusted Entity ............................................................................................................... 519

Activating the Identity Plug-in ........................................................................................................................ 520

Configuring SES Authentication Timeout Settings ........................................................................................ 520

Enabling Character Set Detection ................................................................................................................... 521

Activating the Document Service Plugin ........................................................................................................ 521

Using a Proxy with Oracle SES ...................................................................................................................... 521

Setting Up the PeopleSoft Application Server for the Search Framework .......................................................... 522

Setting Up Search Framework User IDs .............................................................................................................. 522

Using the Search Administration Activity Guide ................................................................................................ 523

Understanding the Search Administration Activity Guide ............................................................................. 523

Setting Up the Local Nodes ............................................................................................................................ 523

Specifying the Integration Gateway ................................................................................................................ 528

Verifying the Service Configuration ............................................................................................................... 531

Defining a Search Instance in the PeopleSoft System .................................................................................... 532

Verifying PeopleSoft PeopleTools and SES Connectivity .................................................................................. 536

Chapter 12

Installing the Verity Integration Kit ................................................................................................................ 539

Understanding the Verity Installation .................................................................................................................. 539

Installing the Verity Integration Kit in GUI Mode .............................................................................................. 539

Installing the Verity Integration Kit in Console Mode ........................................................................................ 544

Chapter 13

Creating a Database Manually on UNIX ......................................................................................................... 547

Understanding Database Creation ........................................................................................................................ 547

Preparing for the PeopleSoft Database Installation ............................................................................................. 548

Installing the PeopleSoft Database Sever Components on the Database Server ............................................ 549

Installing the Oracle RDBMS Software ......................................................................................................... 549

Identifying the Trace and Alert File Locations ............................................................................................... 549

Setting Environment Variables for the PeopleSoft Database ......................................................................... 549

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

15

Contents

Creating an INIT<SID>.ORA File ................................................................................................................. 550

Creating an INIT<SID>.ORA FIle (Multitenant Architecture) ...................................................................... 552

Using SQL Tools .................................................................................................................................................. 552

Editing Database Scripts (non-Multitenant) ......................................................................................................... 552

Understanding Database Scripts ..................................................................................................................... 552

Modifying Database Scripts ............................................................................................................................ 552

Setting NLS_LANG in the Windows Registry .................................................................................................... 554

Creating an Oracle Instance (non-Multitenant) .................................................................................................... 555

Creating Catalog Views and Utility Tablespaces (non-Multitenant) ................................................................... 555

Creating PS.PSDBOWNER Table (non-Multitenant) ......................................................................................... 556

Creating Application-Specific Dbspaces and Tablespaces (non-Multitenant) .................................................... 556

Creating PeopleSoft Database Roles (non-Multitenant) ...................................................................................... 556

Creating the PeopleSoft Database Owner ID (non-Multitenant) ......................................................................... 556

Setting Up Connect ID (non-Multitenant) ........................................................................................................... 557

Understanding Connect ID ............................................................................................................................. 557

Understanding Connect ID and the Login Process ......................................................................................... 558

Creating the Connect ID ................................................................................................................................. 558

Editing Database Scripts (Multitenant Architecture) ........................................................................................... 558

Creating an Oracle Instance (Multitenant Architecture) ...................................................................................... 560

Creating a Root Container Database ............................................................................................................... 560

Creating a PDB ............................................................................................................................................... 560

Creating Catalog Views and Utility Tablespaces (Multitenant Architecture) ..................................................... 561

Creating PS.PSDBOWNER Table (Multitenant Architecture) ........................................................................... 562

Creating Application-Specific Dbspaces and Tablespaces (Multitenant Architecture) ....................................... 562

Creating PeopleSoft Database Roles (Multitenant Architecture) ........................................................................ 562

Creating the PeopleSoft Database Owner ID (Multitenant Architecture) ........................................................... 563

Setting Up Connect ID (Multitenant Architecture) .............................................................................................. 563

Understanding Connect ID ............................................................................................................................. 563

Understanding Connect ID and the Login Process ......................................................................................... 564

Creating the Connect ID ................................................................................................................................. 564

Updating Connection Information ....................................................................................................................... 565

Creating Data Mover Import Scripts .................................................................................................................... 565

Understanding Data Mover Import Scripts ..................................................................................................... 565

Working with Multilingual Databases ............................................................................................................ 566

Running Database Setup to Create Data Mover Import Scripts ..................................................................... 566

Running Data Mover Import Scripts .................................................................................................................... 574

Understanding Data Mover Import Scripts ..................................................................................................... 574

Populating Tables in the PeopleSoft Database ............................................................................................... 574

Checking the Log Files and Troubleshooting ...................................................................................................... 575

Checking the Log Files ................................................................................................................................... 575

Running Data Mover ....................................................................................................................................... 575

Troubleshooting .............................................................................................................................................. 577

16

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Contents

Improving Performance .................................................................................................................................. 579

Changing the Base Language ............................................................................................................................... 579

Chapter 14A

Installing and Compiling COBOL on Windows ............................................................................................. 581

Understanding COBOL ........................................................................................................................................ 581

Prerequisites ......................................................................................................................................................... 581

Preparing COBOL for a PeopleTools-only Upgrade ........................................................................................... 582

Installing Micro Focus Net Express on Microsoft Windows ............................................................................... 582

Prerequisites .................................................................................................................................................... 582

Obtaining Installation Files for Micro Focus Net Express from Oracle Software Delivery Cloud ................ 583

Installing Micro Focus Net Express Wrap Pack 6 .......................................................................................... 583

Installing Micro Focus Net Express Wrap Pack 11 ........................................................................................ 595

Managing Micro Focus Net Express Compiler Licenses ..................................................................................... 600

Understanding Micro Focus Net Express Compiler Licenses ........................................................................ 600

Configuring a Full License with the License Server ...................................................................................... 601

Configuring a Timed License with the License Server .................................................................................. 611

Revoking the License Using the License Management System ..................................................................... 618

Revoking the License by Removing the Installation ...................................................................................... 620

Using the Micro Focus COBOL Compiler on Microsoft Windows .................................................................... 622

Understanding COBOL Compilation ............................................................................................................. 623

Compiling COBOL on Microsoft Windows with a PS_HOME Setup ........................................................... 624

Compiling COBOL on Microsoft Windows with a PS_APP_HOME Setup ................................................. 627

Compiling COBOL on Microsoft Windows with a PS_CUST_HOME Setup .............................................. 631

Recompiling COBOL on Microsoft Windows ............................................................................................... 636

Setting Up the Micro Focus Net Express Runtime ......................................................................................... 637

Defining the GNT and INT Files .................................................................................................................... 639

Distributing COBOL Binaries ........................................................................................................................ 639

Chapter 14B

Installing and Compiling COBOL on UNIX ................................................................................................... 641

Understanding COBOL ........................................................................................................................................ 641

Prerequisites ......................................................................................................................................................... 642

Preparing COBOL for a PeopleTools-only Upgrade ........................................................................................... 642

Installing Micro Focus Server Express for UNIX and Linux .............................................................................. 642

Understanding Micro Focus Server Express ................................................................................................... 642

Prerequisites .................................................................................................................................................... 643

Obtaining the Installation Files for Micro Focus Server Express from Oracle Software Delivery Cloud ..... 643

Installing Micro Focus Server Express ........................................................................................................... 644

Using the Micro Focus COBOL Compiler on UNIX .......................................................................................... 649

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

17

Contents

Understanding COBOL Compilation ............................................................................................................. 650

Setting Environment Variables ....................................................................................................................... 651

Modifying the Liblist64 File (IBM AIX) ........................................................................................................ 651

Modifying the Cobopt File (SuSE Linux Enterprise Server Only) ................................................................. 652

Compiling COBOL on UNIX with a PS_HOME Setup ................................................................................. 652

Compiling COBOL on UNIX with a PS_APP_HOME Setup ....................................................................... 653

Compiling COBOL on UNIX with a PS_CUST_HOME Setup .................................................................... 655

Linking COBOL ............................................................................................................................................. 655

Recompiling COBOL on UNIX ..................................................................................................................... 656

Installing IBM COBOL on IBM AIX .................................................................................................................. 657

Understanding the IBM COBOL for AIX Installation ................................................................................... 657

Prerequisites .................................................................................................................................................... 657

Installing IBM COBOL for AIX v4.1.1.1 ....................................................................................................... 658

Using the IBM COBOL Compiler on IBM AIX ................................................................................................. 660

Setting Environment Variables for IBM COBOL .......................................................................................... 660

Compiling COBOL on AIX with a PS_HOME Setup .................................................................................... 661

Compiling COBOL on AIX with a PS_APP_HOME Setup .......................................................................... 662

Compiling COBOL on AIX with a PS_CUST_HOME Setup ....................................................................... 663

Troubleshooting the IBM COBOL Compiler ................................................................................................. 665

Setting Up the IBM COBOL Runtime ............................................................................................................ 668

Removing the IBM COBOL Installation ........................................................................................................ 672

Chapter 15

Installing PeopleSoft Change Assistant ............................................................................................................ 677

Understanding PeopleSoft Change Assistant ....................................................................................................... 677

Removing or Upgrading PeopleSoft Change Assistant Installations ................................................................... 678

Removing PeopleSoft Change Assistant Installations from Previous Releases ............................................. 678

Removing PeopleSoft Change Assistant Instances in the Current Release .................................................... 678

Upgrading PeopleSoft Change Assistant Instances ........................................................................................ 682

Installing PeopleSoft Change Assistant in GUI Mode ......................................................................................... 686

Installing PeopleSoft Change Assistant in Silent Mode ...................................................................................... 692

Understanding Silent Mode for PeopleSoft Change Assistant ....................................................................... 693

Using the Silent Mode Script .......................................................................................................................... 693

Configuring and Using PeopleSoft Change Assistant ......................................................................................... 694

Verifying the Path Variable ............................................................................................................................ 694

Specifying Options .......................................................................................................................................... 694

Scanning the Workstation ............................................................................................................................... 695

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

Validating Change Assistant Settings .................................................................................................................. 695

18

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Contents

Chapter 16

Installing PeopleSoft Change Impact Analyzer .............................................................................................. 699

Prerequisites ......................................................................................................................................................... 699

Removing PeopleSoft Change Impact Analyzer Installations ............................................................................. 699

Installing PeopleSoft Change Impact Analyzer ................................................................................................... 702

Installing and Removing PeopleSoft Change Impact Analyzer in Silent Mode .................................................. 707

Understanding Silent Mode for PeopleSoft Change Impact Analyzer ........................................................... 707

Installing PeopleSoft Change Impact Analyzer in Silent Mode ..................................................................... 708

Removing the PeopleSoft Change Impact Analyzer Installation in Silent Mode ........................................... 709

Removing and Installing PeopleSoft Change Impact Analyzer in Silent Mode ............................................. 709

Chapter 17

Adding New Product Modules .......................................................................................................................... 711

Adding New Modules to PeopleSoft 8.4 Installations ......................................................................................... 711

Chapter 18

Installing PeopleSoft Online Help ..................................................................................................................... 713

Understanding PeopleSoft Online Help (PeopleBooks) ...................................................................................... 713

Using the PeopleSoft Online Help Web Site for Context-Sensitive Help ........................................................... 714

Understanding the PeopleSoft Online Help Web Site .................................................................................... 714

Setting Up Context-Sensitive Help with the PeopleSoft Online Help Web Site ............................................ 714

Setting Up F1 Help with the PeopleSoft Online Help Web Site .................................................................... 717

Installing PeopleSoft Online Help LocalIy .......................................................................................................... 717

Obtaining PeopleSoft Online Help Installation Files from Oracle Software Delivery Cloud ........................ 717

Installing the PeopleSoft Online Help to a Local Machine ............................................................................ 718

Configuring Context-Sensitive Help with Local Installations ............................................................................. 719

Enabling the Help Link from the Application Pages with Local Installations ............................................... 720

Enabling F1 Help with Local Installations ..................................................................................................... 720

Creating the Help Index for Multi-Product Installations ................................................................................ 721

Using Oracle Secure Enterprise Search for Full-Text Searches .......................................................................... 721

Understanding Oracle Secure Enterprise Search and PeopleSoft Online Help .............................................. 721

Prerequisites .................................................................................................................................................... 721

Crawling a Source to Generate Full-Text Search ........................................................................................... 722

Setting Up Oracle Secure Enterprise Search for Multiple Product Line Libraries .............................................. 736

Understanding the Multiple Product Line Setup ............................................................................................ 736

Setting Up the Product Line Libraries ............................................................................................................ 737

Creating Web Sources for the Individual Product Line Libraries .................................................................. 737

Creating a Web Source for the Combined Library ......................................................................................... 737

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

19

Contents

Chapter 19

Installing Software for PS/nVision Drilldowns ............................................................................................... 739

Understanding PS/nVision DrillDown Add-ins ................................................................................................... 739

Installing the DrillToPIA Add-In ......................................................................................................................... 740

Understanding Drilldown with DrillToPIA Add-in ........................................................................................ 740

Installing the DrillToPIA Add-in on the Microsoft Excel Environment ........................................................ 740

Installing the nVisionDrill Add-In ....................................................................................................................... 741

Understanding PS/nVision DrillDown Using Web Services .......................................................................... 741

Understanding Security for DrillDown Using nVisionDrill VSTO Add-in ................................................... 741

Installing the nVisionDrill Add-in for Microsoft Excel ................................................................................. 741

Installing the nVisionDrill Add-Ins for Multi-Language Installations ................................................................ 742

Setting Up PeopleSoft Integration Broker for Using Web Service Capability with nVisionDrill Add-in .......... 742

Chapter 20

Installing Web Application Deployment Tools ................................................................................................ 747

Prerequisites ......................................................................................................................................................... 747

Installing the Web Application Deployment Tool on Oracle WebLogic in GUI Mode ...................................... 748

Installing the Web Application Deployment Tool on IBM WebSphere in GUI Mode ....................................... 761

Installing the Web Application Deployment Tool on Oracle WebLogic in Console Mode ................................ 773

Installing the Web Application Deployment Tool on IBM WebSphere in Console Mode ................................. 777

Installing the Web Application Deployment Tool in Silent Mode ...................................................................... 781

Understanding the Web Application Deployment Tool Silent Mode Installation and the Response File ..... 781

Editing the Web Application Deployment Tool Response File to Deploy DES ............................................ 782

Running the Web Application Deployment Tool Silent Mode Installation to Deploy DES .......................... 783

Testing and Troubleshooting the Web Application Deployment ........................................................................ 784

Appendix A

Describing Debugger Requirements ................................................................................................................. 785

Describing Debugger Requirements for the AIX Operating System ................................................................... 785

Describing Debugger Requirements for the HP-UX Operating System .............................................................. 785

Describing Debugger Requirements for the Linux Operating System ................................................................ 785

Describing Debugger Requirements for the Oracle Solaris Operating System ................................................... 786

Describing Debugger Requirements for the z/OS Operating System .................................................................. 786

Appendix B

Relinking SQR on UNIX ................................................................................................................................... 789

Understanding SQR Relinking ............................................................................................................................. 789

20

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Contents

Relinking SQR on UNIX ..................................................................................................................................... 789

Relinking SQR on Oracle Solaris ........................................................................................................................ 790

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

21

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 direct you through a basic PeopleSoft installation. It is not a substitute for the database administration documentation provided by your relational database management system (RDBMS) vendor, the network administration documentation provided by your network vendor, or the installation and configuration documentation for additional software components that are used with PeopleSoft products.

This documentation is divided into two parts. The chapters in Part 1 include the information that is required to complete a basic PeopleSoft installation. The chapters and appendices in Part 2 include information for less common or optional tasks.

Required updates to this installation documentation are provided in the form of "Required for Install" incidents, which are available on My Oracle Support. In addition, addenda to the recent PeopleTools installation guides are periodically posted in My Oracle Support on the same page as the initial posting.

Instructions for installing Oracle's PeopleSoft PeopleTools are provided in PeopleSoft PeopleTools installation guides. Application-specific installation instructions are provided in a separate document for the PeopleSoft application. For instance, if you are installing Oracle's PeopleSoft Customer Relationship Management (CRM), you need both the PeopleSoft PeopleTools installation guide and the additional instructions provided for installing

PeopleSoft CRM.

To find the installation documentation for PeopleSoft PeopleTools or for your PeopleSoft application, go to My

Oracle Support and search for the installation guide for your product and release.

Note. Before proceeding with your installation, check My Oracle Support to ensure that you have the latest version of this installation guide for the correct release of the PeopleSoft product that you are installing.

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.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

23

Preface

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

Typographical Conventions

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

Convention

Monospace

Description

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

Menu, Page

Cross-references

Field names, commands, and processes are represented as they appear on the window, menu, or page.

File or directory names are represented in lower case, unless they appear otherwise on the interface.

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

24

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Convention

⇒ (line-continuation arrow)

" " (quotation marks)

Note. Note text.

Important! Important note text.

Warning! Warning text.

Products

This documentation may refer to these products and product families:

• Oracle® BPEL Process Manager

• Oracle® Enterprise Manager

• Oracle® Secure Enterprise Search

• 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

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Preface

Description

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.

Indicate chapter titles in cross-references and words that are used differently from their intended meaning.

Text that begins with Note. indicates information that you should pay particular attention to as you work with your

PeopleSoft system.

A note that begins with Important! is crucial and includes information about what you need to do for the system to function properly.

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.

25

Preface

• 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-az/index.html.

Related Information

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

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

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

My Oracle Support.

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

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

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

PeopleTools: Getting Started with PeopleTools for your release. This documentation provides a high-level introduction to PeopleTools technology and usage.

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

• PeopleSoft Application Fundamentals for your PeopleSoft Application and release. This documentation provides essential information about the setup, design, and implementation of your PeopleSoft Application.

To install additional component software products for use with PeopleSoft products, including those products that are packaged with your PeopleSoft products as well as products from other vendors, you should refer to the documentation provided with those products, as well as this documentation. For those additional components that are offered by Oracle, such as Oracle Middleware products, see the documentation on the Oracle Help Center.

See Also

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

Comments and Suggestions

Your comments are important to us. We encourage you to tell us what you like, or what you would like changed about PeopleSoft documentation and other Oracle reference and training materials. Please send your suggestions to:

[email protected]

While we cannot guarantee to answer every email message, we will pay careful attention to your comments and suggestions. We are always improving our product communications for you.

26

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Part I

Mandatory Installation

The chapters in the first part of this installation guide cover only those tasks that are required for a basic

PeopleSoft installation. Everyone carrying out an installation should use the tasks in Part I. After setting up the

Application Server, PeopleSoft Pure Internet Architecture, and Process Scheduler Server, you verify that you can sign into the PeopleSoft installation in a browser.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

27

Chapter 1

Preparing for Installation

This chapter discusses:

• Understanding the PeopleSoft Installation

• Using Oracle Software Delivery Cloud to Obtain Installation Files

• Considering Project Planning

• Planning Your Initial Configuration

• Planning Database Creation

• Planning Multilingual Strategy

• Preparing for the PeopleTools-Only Upgrade

• Reviewing Patches and Updates Required at Installation

• Installing Supporting Applications

• Installing the Database Engine

• Installing Oracle Net on the Server

• Installing Oracle Net on Your Workstation

• Testing Oracle Net Connectivity

• Performing Backups

• Using PeopleSoft Change Assistant and PeopleSoft Change Impact Analyzer

Understanding the PeopleSoft Installation

This chapter will help you plan and prepare for a basic PeopleSoft installation. Before you begin the installation, please note:

• See Getting Started on the PeopleSoft Installation, for an overview of the installation and for information on obtaining the necessary documentation and software.

You can find Getting Started on the PeopleSoft Installation on the same My Oracle Support page as this installation guide.

• Before you begin your PeopleSoft installation, use the PeopleSoft hardware and software requirements information in the My Oracle Support Certifications area to verify that you have the correct hardware and software in place to support a successful installation. In addition to the information in the Certifications area, review the application-specific hardware and software documentation available on My Oracle Support.

See hardware and software requirements for PeopleSoft PeopleTools and your PeopleSoft application on My

Oracle Support.

See My Oracle Support, Certifications.

29

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Preparing for Installation

Chapter 1

Warning! If you are unable to meet any of the criteria outlined in the hardware and software requirements and certification information on My Oracle Support, contact Oracle before going forward with the installation.

Attempting to complete an installation on an unsupported configuration can be a very costly decision, and

Oracle will not provide support for such PeopleSoft installations.

Important! Before installing Oracle's Secure Enterprise Search (SES) we highly recommend that you review our deployment and sizing recommendations provided in "Oracle Secure Enterprise Search Deployment

Considerations for PeopleSoft 9.2" (Document ID: 1684035.1) found on My Oracle Support. This article provides information regarding the essential hardware for SES and information to help ensure capacity for peak concurrent usage of your PeopleSoft 9.2 environment. Failing to follow these recommendations can impact the performance and stability of your PeopleSoft 9.2 environment.

• Use the My Oracle Support Certifications area to determine the latest certified versions of additional components, such as Oracle Tuxedo or IBM WebSphere, which are supported for the PeopleSoft PeopleTools release you are installing.

• If you will be upgrading your current release after you perform this installation, you also need to install

Change Assistant. The page on My Oracle Support containing your upgrade documentation and files includes information on which tool you need.

• For critical issues related to the installation process, see the My Oracle Support web site. Be sure to read the

"Required for Installation or Upgrade" incidents on the Patches and Updates page for the PeopleSoft

PeopleTools version that you are installing.

• For online technical support information, use the My Oracle Support web site. My Oracle Support includes tools for self-directed searches of information including reference documents and problem resolutions, as well as service request management tools.

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

• To download software and documentation, use the Oracle Software Delivery Cloud portal, and the Oracle

Technology Network.

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

See Oracle Technology Network, http://www.oracle.com/technetwork/index.html.

• Be aware that not all application releases are certified and supported to run on all PeopleSoft PeopleTools releases. Please check the PeopleSoft policy information in article ID 1348959.1 on My Oracle Support for further details on the support policy for your particular application. If you are planning to do a PeopleTools-

Only upgrade, do not continue until you have verified that your application is supported on the target

PeopleSoft PeopleTools release.

• This installation guide may refer you to other PeopleSoft documentation resources for more information or instructions. You can access Oracle's PeopleSoft Hosted Documentation online during the installation process.

For PeopleSoft PeopleTools 8.53 and later, you also have the option to install PeopleSoft Online Help documentation, a dynamic, interactive, accessible HTML version of the documentation formerly known as

"PeopleBooks."

• If you are using a Microsoft Windows or Linux operating system, Oracle recommends that you use the

PeopleSoft Cloud Architecture. The PeopleSoft Cloud Architecture consists of several deployment packages

(DPKs) that deliver pre-installed PeopleSoft components, which can be installed on virtualization platforms as well as directly on traditional, non-virtual machines ("bare-metal") with Microsoft Windows or Linux operating systems.

See Getting Started on PeopleSoft Installation, "Reviewing PeopleSoft Cloud Architecture."

30

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 1

Preparing for Installation

See Also

"Installing PeopleSoft Online Help"

Oracle's PeopleSoft Hosted Documentation, http://www.peoplesoftonlinehelp.com

"Installing PeopleSoft Change Assistant"

Task 1-1: Using Oracle Software Delivery Cloud to Obtain

Installation Files

Before beginning the installation, you should have obtained the PeopleSoft installation software by downloading the necessary zip files from the Oracle Software Delivery Cloud portal. Use the information available in the

PeopleSoft documentation and My Oracle Support Certifications to be sure that you obtain all the zip files required for your environment.

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

In case you have not yet obtained the necessary files, this documentation includes sections on obtaining the files at appropriate points during the installation process.

Note. If your PeopleSoft installation uses Oracle SOA Suite, note that the 32-bit versions of the Oracle SOA Suite

10g media components on the Oracle Software Delivery Cloud portal are certified to run on the Linux x86-64 and the Microsoft Windows 64-bit operating system platforms.

Task 1-2: Considering Project Planning

Identify the maintenance schedule for upcoming PeopleSoft PeopleTools and PeopleSoft application releases.

These releases are typically on a regular schedule (for example, quarterly, biannually) and should be included in your project planning and budgeting processes. Maintenance schedules are posted on My Oracle Support. It is important to plan regular maintenance in your overall project plans. For example, for a year-long enterprise upgrade, development, and conversion project, make sure to set aside time for applying the PeopleSoft

PeopleTools minor releases that ship during that time frame. Otherwise, if you fall behind, you may find that you need a fix shipped with one of the minor releases that cannot be backported as a patch.

Search for the term "maintenance schedules" on My Oracle Support. You can find schedules by year and quarter for PeopleSoft PeopleTools and PeopleSoft applications. The schedules include lists of bundles and maintenance packs for individual products.

Task 1-3: Planning Your Initial Configuration

This section discusses:

• Understanding Workstations

• Understanding PeopleSoft Servers and Clients

• Defining the PeopleTools Client

• Defining the File Server

• Defining the Database Server

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

31

Preparing for Installation

Chapter 1

• Defining the Application Server

• Defining the Batch Server

• Defining Installation Locations

• Defining the Web Server

• Using Oracle Configuration Manager

• Using Laser Printers

Note. Oracle supports a number of versions of UNIX and Linux in addition to Microsoft Windows for the

PeopleSoft installation. Throughout this book, there are references to operating systems. Where necessary, this book refers to specific operating systems by name (for example, Oracle Solaris, IBM AIX, or Linux); however, for simplicity the word UNIX is often used to refer to all UNIX-like operating systems, including Linux.

Understanding Workstations

This section discusses:

• Using the PeopleTools Development Environment (Microsoft Windows-Based Clients)

• Using Workstations Equipped with Supported Web Browsers

Note. With the PeopleSoft Pure Internet Architecture, Microsoft Windows-based clients are primarily used as a development environment. End users can use any machine equipped with a supported web browser.

Using the PeopleTools Development Environment (Microsoft Windows-Based Clients)

Microsoft Windows-based clients are referred to as the PeopleTools Development Environment. These clients— which run on supported Microsoft Windows platforms—can connect to the PeopleSoft database directly using client connectivity software (a two-tier connection) or through a PeopleSoft application server (a three-tier connection).

Three-tier connectivity offers great performance advantages over two-tier (especially over a WAN), reduces network traffic, and generally does not require that you install database connectivity on the client. However, any

Microsoft Windows-based clients that will be running Data Mover scripts against the database, or running

COBOL or Structured Query Report (SQR) batch processes on the client, must have database connectivity installed.

Note. COBOL is not needed for PeopleTools or for applications that contain no COBOL programs. Check My

Oracle Support for details about whether your application requires COBOL.

See Installing Supporting Applications.

You need to have the PeopleTools Development Environment set up to create your database. For more information on setting up the PeopleTools Development Environment, refer to the product documentation for

PeopleSoft Configuration Manager.

See the PeopleTools: System and Server Administration product documentation for more information about using

PeopleSoft Configuration Manager.

For installation purposes, you must set up at least one Microsoft Windows-based client for sign-on using a twotier connection to the database, so that it can create and populate the PeopleSoft database. This documentation refers to this client as the install workstation. Depending on your installation plan, you may want to set up more than one install workstation so that you can perform asynchronous installation tasks in parallel.

32

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 1

Preparing for Installation

Note. The Microsoft Windows machine that you use to perform your PeopleSoft PeopleTools installation must be running in 256-color mode or higher when running the PeopleSoft installation and database configuration on

Microsoft Windows. This is not necessary for UNIX or console mode.

Using Workstations Equipped with Supported Web Browsers

To run the PeopleSoft Pure Internet Architecture, the client workstation only needs a web browser that is HTML

4.0 compliant. You may need an additional workstation for demonstration and testing purposes if you plan to use a browser running on a platform other than Microsoft Windows—such as Macintosh or UNIX.

See PeopleTools: Portal Technology.

See My Oracle Support, Certifications.

Understanding PeopleSoft Servers and Clients

You use the PeopleSoft Installer to install PeopleSoft servers and the PeopleTools Client. Here is a summary of the functionality included in each server or client installation:

File Server

All Client executables (such as PeopleSoft Application Designer and Configuration Manager), PS/nVision,

Change Assistant, files and directories necessary to perform upgrade, and Client SQR.

See Defining the File Server

PeopleTools Client

All Client executables (such as PeopleSoft Application Designer and Configuration Manager), PS/nVision,

Change Assistant, Change Impact Analyzer, PeopleSoft Test Framework, PSEM Agent, and Client SQR.

See Defining the PeopleTools Client.

Application Server

PSADMIN and COBOL for remote call

Database Server

Scripts and data directories, files necessary to run Data Mover.

Process Scheduler Server

PSADMIN, COBOL, and SQR.

Web Server

The Web Server contains all the scripts file, Portal Search data files, and PeopleSoft Pure Internet

Architecture (PIA) installation tools that can assist in setting up a web server domain. However, to run the

PeopleSoft Pure Internet Architecture, the client workstation only needs a web browser that is HTML 4.0 compliant.

Task 1-3-1: Defining the PeopleTools Client

The PeopleTools Client is the environment repository for the PeopleSoft PeopleTools Development environment.

The PeopleTools Client provides two-tier and three-tier connectivity to PeopleSoft applications.

The PeopleSoft installer for the PeopleTools Client is included as part of the PeopleSoft PeopleTools installation.

Keep in mind that the PeopleTools Client can be installed only on supported Microsoft Windows operating systems.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

33

Preparing for Installation

Chapter 1

Note. The client may be referred to as the PeopleTools Client, PT Client, or PeopleSoft Microsoft Windows client in this documentation.

See "Using the PeopleSoft Installer," Installing the PeopleTools Client Files.

Task 1-3-2: Defining the File Server

The file server is the environment (or file) repository for the PeopleTools Development Environment, which is needed for the Database Configuration Wizard. The file server is also the repository for the files necessary to perform an upgrade. This includes Change Assistant and all of the executables and scripts that are necessary to perform an upgrade. You will apply patches and updates from My Oracle Support directly to the file server and then copy the updated files to your other servers. In addition, the file server is a source repository for COBOL and

SQR.

Important! Remember, a COBOL compiler is not needed for PeopleSoft PeopleTools unless your application contains COBOL programs. If your application requires COBOL and you are running on Microsoft Windows, we require that you maintain a central repository of your COBOL source code on the Windows file server. See the task Installing Supporting Applications later in this chapter for details on where you should install your COBOL compiler.

If you follow the default procedures recommended in this documentation, the install workstations, Microsoft

Windows batch servers, and Microsoft Windows report servers will access the PeopleSoft files on the file server by pointing to a directory referred to in this documentation as PS_HOME on a shared network drive. You can install SQR on the file server, or install them locally on Microsoft Windows batch servers and on Microsoft

Windows-based clients that will be running these processes locally.

Setting up a file server is part of installations on both UNIX and Microsoft Windows environments. If you are doing an installation only for UNIX computers, you need a Microsoft Windows file server. If you are working only on Microsoft Windows, and you install the file server along with the other servers, you do not need to repeat the file server setup.

If you need to set up the file server on a separate Microsoft Windows machine, you should install PeopleSoft

PeopleTools, any PeopleSoft applications, and the Multilanguage files.

In some cases you may choose to set up local copies of the PeopleSoft executables on the PeopleTools

Development Environment and Windows batch servers, rather than mapping to a shared directory on the file server. You can use the instructions in the chapter "Using the PeopleSoft Installer" to perform such local installations.

Task 1-3-3: Defining the Database Server

The servers that host your PeopleSoft databases need sufficient processing, storage, and networking resources to process the database requests, store the data and transaction logs, and communicate freely to the clients of this data. These databases will include your own PeopleSoft database prototypes as well as any system and demonstration databases delivered directly from Oracle with the PeopleSoft installation media.

See Planning Database Creation.

Database sizes vary depending on the applications that you install. The size of your prototype PeopleSoft database will also depend on the amount of data to be converted from your legacy system. A good rule of thumb for estimating the size of your prototype PeopleSoft database is to estimate the amount of disk space needed for the data to be converted from your legacy system, add to this the size required for the PeopleSoft System database, and then add an additional 50 percent of this combined figure to allow for growth.

34

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 1

Preparing for Installation

Task 1-3-4: Defining the Application Server

The application server is the centerpiece of the PeopleSoft Pure Internet Architecture. It connects to the

PeopleSoft database and handles almost all SQL-intensive interactions with the database server required during online transaction processing. Microsoft Windows-based clients, in three-tier, communicate with the application server using Oracle Tuxedo messages. In the PeopleSoft Pure Internet Architecture, the application server interacts with user workstations through a web server.

The application server also provides functionality required for application messaging and for implementing the

PeopleSoft Pure Internet Architecture. An application server is required in all PeopleSoft installations.

If you are installing on an Oracle for UNIX RDBMS, you can install the application server on the same machine as the database server, a configuration called logical three-tier. You can also install application servers on one or more separate UNIX or Microsoft Windows machines. This configuration is called physical three-tier. (See the

Certification area on My Oracle Support for information on supported operating systems for PeopleSoft

Application Servers.)

If you are installing on an Oracle for Windows RDBMS, you may use a Microsoft Windows application server.

This application server can be installed on the same machine as the Oracle database server, but for Windows installations you will most likely get better results by installing one or more dedicated application servers (that is, a physical three-tier configuration).

All application servers require database connectivity to the database server. Before beginning your installation, make sure that you can connect from the application server machine to the database server using a SQL tool. This topic will be addressed later in this chapter.

See Also

PeopleTools: Portal Technology

Task 1-3-5: Defining the Batch Server

The term batch server is equivalent to the term Process Scheduler server. PeopleSoft batch processes, such as

COBOL and SQR, are scheduled and invoked by a Process Scheduler server. In almost all configurations, batch server SQR and COBOL files are located and executed on the same computer as the database server.

With Oracle Windows databases, a Process Scheduler server running on the batch server may point to and invoke files that are physically located on the file server. With an Oracle UNIX database, the SQR and COBOL files must be installed to the batch server through the PeopleSoft Installer; and COBOL source files must be compiled.

Oracle supports setting up the batch environments on a dedicated server, an application server, or even on the database server.

For Windows-specific batch processes—such as nVision reports, Cube Builder, or Microsoft Word—you need to set up a Windows batch environment on a Microsoft Windows application server or on a dedicated Microsoft

Windows workstation.

Any computer operating as a batch server must have database connectivity installed so that it can make a two-tier connection to the PeopleSoft database.

See Also

PeopleTools: Process Scheduler

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

35

Preparing for Installation

Chapter 1

Task 1-3-6: Defining Installation Locations

This section discusses:

• Understanding Installation Locations

• Defining PS_HOME

• Defining PS_APP_HOME

• Defining PS_CFG_HOME

• Defining PS_CUST_HOME

• Defining PIA_HOME

Understanding Installation Locations

As you proceed through the PeopleSoft PeopleTools installation, you are asked to specify several installation locations. Use the information in this section to choose how to specify the installation locations for the various components in a PeopleSoft installation.

In addition to these installation locations, there are home directories for the various supporting software, such as

Oracle WebLogic, which are described in the appropriate chapters.

Defining PS_HOME

The PS_HOME directory holds the PeopleSoft PeopleTools files. The way that you specify the other installation locations discussed in the following sections will determine whether other files are installed in PS_HOME or elsewhere; for example, whether the PeopleSoft application files are installed into PS_HOME or into

PS_APP_HOME.

See "Using the PeopleSoft Installer."

For information on setting up PS_HOME as a read-only environment, see the PeopleTools: System and Server

Administration product documentation on securing PS_HOME and PS_CFG_HOME.

PS_HOME can be used in the following ways:

• Multiple hosts can access PS_HOME on a shared (Microsoft Windows) or mounted (UNIX) location.

• An administrator can do an installation where all PeopleTools, PeopleSoft application, and customized files reside in the same location. That is, the paths for PS_HOME, PS_APP_HOME, and PS_CUST_HOME are the same. The administrator can then copy and paste PS_HOME to different locations with no requirement to duplicate the original file path. This scenario requires a PS_CFG_HOME location that is separate from

PS_HOME, PS_APP_HOME and PS_CUST_HOME.

• Several Application Server, PIA, and Process Scheduler domains can use the same PS_HOME.

Defining PS_APP_HOME

The PS_APP_HOME location holds the PeopleSoft application files.

Depending upon the PeopleSoft application that you are installing, for PeopleSoft PeopleTools 8.52 and later, the directory where you install the PeopleSoft application files does not have to be the same as the location where you install PeopleSoft PeopleTools, PS_HOME. You can select any writeable location on the file system. The

PS_APP_HOME location is sometimes referred to as "Application Home."

36

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 1

Preparing for Installation

For details about whether this functionality is supported for your PeopleSoft application, and how it is used, see the PeopleSoft application-specific installation guide.

If you choose to install the PeopleSoft application software to a PS_APP_HOME location that is different from the PS_HOME location where you installed PeopleSoft PeopleTools, you will need to define a PS_APP_HOME environmental variable.

For example, on Microsoft Windows:

1. Select Start, Control Panel, System on Microsoft Windows 7.

Click the Start button, then Control Panel, System and Security, System, on Microsoft Windows 8 or 2012 R2.

2. Select Advanced system settings.

3. On the System Properties dialog box, select Advanced, and click Environment Variables.

4. Add or modify the user variable PS_APP_HOME and specify its value. For example:

PS_APP_HOME=C:\HC9.2

On UNIX, specify the environment variable with a command such as this:

PS_APP_HOME=/data1/ora/HC9.2;export PS_APP_HOME

If your environment includes more than one PeopleSoft application, such as FSCM and HCM, you can install into a separate PS_APP_HOME location for each. However, in this case, you must change the value of the

PS_APP_HOME environment variable for any configuration tasks.

For information on setting and working with the PS_APP_HOME environment variable, see the product documentation PeopleTools: System and Server Administration, "Working with PS_APP_HOME."

See the chapters on installing and compiling COBOL in this documentation for further information.

Defining PS_CFG_HOME

The PS_CFG_HOME location holds the configuration files for the application server, batch server and search server domains.

It also holds the configuration files for web server domains if PIA_HOME, defined in the next section, is equal to

PS_CFG_HOME. This location is sometimes referred to as "Config Home."

When you install PeopleSoft PeopleTools and the PeopleSoft application software, the PeopleSoft installer places the required files into the specified PS_HOME directory. When you create an application server, batch server, or search server domain, the configuration files associated with that domain are installed into a directory referred to as PS_CFG_HOME.

By default, the system separates the binary files (executables and libraries) stored in PS_HOME from the ASCII files (configuration and log files) associated with a domain stored in PS_CFG_HOME. This separation applies only to these servers:

• PeopleSoft Application Server

• PeopleSoft Process Scheduler Server

• PeopleSoft Search Server

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

37

Preparing for Installation

Chapter 1

When you use the PSADMIN utility, the system creates the PS_CFG_HOME directory based upon environment variables associated with the current user. This table lists the user environment variable and default directory by operating system:

Operating System

UNIX

User Environment Variable

HOME

PS_CFG_HOME Default Location

$HOME/psft/pt/<peopletools_version>

Microsoft Windows USERPROFILE %USERPROFILE%\psft\pt\

<peopletools_version>

For example, if USERPROFILE is C:\Documents and Settings\asmith and the PeopleTools version is 8.55, by default PS_CFG_HOME would be C:\Documents and Settings\asmith\psft\pt\8.55. The configuration and log files for the application server, process scheduler server, and search server are installed below this directory.

Note. The PS_CFG_HOME directory is associated with the PS_HOME from which it was originally generated.

This server domain configuration allows for a more flexible installation. You also have the opportunity to place different security restrictions on the binary and configuration files. To take advantage of this flexibility, you have the option to specify a different location by setting a PS_CFG_HOME environment variable. Before doing so, however, see the PeopleTools: System and Server Administration product documentation for a more complete explanation of working with PS_CFG_HOME.

Defining PS_CUST_HOME

The PS_CUST_HOME location holds customized file system objects.

Anything that is changed from the file system objects that are delivered with the PeopleSoft application installation should be placed here. The sub-directory structure must mirror the PS_APP_HOME upon which it is based. For example, when you install your PeopleSoft application, the directory structure includes SQR scripts in

PS_APP_HOME/sqr. If you have customized SQR scripts, you would place them in PS_CUST_HOME/sqr.

If a value is not assigned for the PS_CUST_HOME environment variable it assumes the default value of

PS_HOME. This location is sometimes referred to as "Cust Home."

For information on setting up and using PS_CUST_HOME, see the information on working with

PS_CUST_HOME in the product documentation PeopleTools: System and Server Administration.

Defining PIA_HOME

When you install the PeopleSoft Pure Internet Architecture, the files are installed in the PIA_HOME directory.

The PIA_HOME location holds the webserv directory, and the files for the PeopleSoft Pure Internet Architecture installation. The directory where you install PeopleSoft Pure Internet Architecture, PIA_HOME, does not have to be the same as the location where you install PeopleSoft PeopleTools and the PeopleSoft application software,

PS_HOME. You have the option to specify the installation location for the PeopleSoft Pure Internet Architecture by setting the environment variable PS_CFG_HOME.

See "Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode."

See "Setting Up the PeopleSoft Pure Internet Architecture in Console Mode."

38

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 1

Preparing for Installation

The PS_CFG_HOME directory is created the first time that the PSADMIN utility starts. PSADMIN recognizes that PS_CFG_HOME is not present and creates it when necessary. This is done before any domains are created.

When you invoke PeopleSoft Pure Internet Architecture, the installer checks your environment to determine the

PS_CFG_HOME. If the environment variable PS_CFG_HOME is defined, the PS_CFG_HOME location is seen as the directory to which that environment variable points. If PS_CFG_HOME is not defined the default value is used.

See the product documentation for using the %V Meta variable in PeopleTools: System and Server Administration product documentation for more information about setting the PS_CFG_HOME environment variable.

Task 1-3-7: Defining the Web Server

A web server is required to run the PeopleSoft Pure Internet Architecture. The PeopleSoft Pure Internet

Architecture is certified to work with either of the following two J2EE web application servers (also commonly referred to as web servers):

• Oracle WebLogic Server

• IBM WebSphere Server

Refer to the Certifications page on My Oracle Support for supported web server combinations.

To find support information for the HTTP servers that can be used as reverse proxy servers (RPS), see the following:

• For Oracle WebLogic, see the Oracle WebLogic documentation, included with Oracle Fusion Middleware.

• For IBM WebSphere, see the information for PeopleSoft PeopleTools on My Oracle Support, Certifications.

Oracle WebLogic, IBM WebSphere, and the supported reverse proxy servers will provide out-of-the-box SSL support across all supported operating systems. Oracle WebLogic and IBM WebSphere provide demo digital certificates, but for production grade SSL you must purchase digital certificates from a Certificate Authority supported by the web server that you are using (for example, Verisign, Baltimore, Entrust, and so on).

Task 1-3-8: Using Oracle Configuration Manager

When you install PeopleSoft PeopleTools, you can configure the Oracle Configuration Manager. Oracle

Configuration Manager enables you to connect to My Oracle Support to upload your environment information to an Oracle repository. When you enter your configuration information for the Oracle Configuration Manager during the PeopleSoft PeopleTools installation, the installer checks the Internet connection and associates the current environment data with your My Oracle Support account. Oracle Configuration Manager offers the following advantages:

• Facilitates communication with Oracle Software Support

• Improves access to the Oracle knowledge base

• Enables pro-active problem avoidance.

If you choose not to configure the Oracle Configuration Manager during the PeopleSoft PeopleTools installation, you can complete the configuration at a later date. If your system is already configured to use Oracle

Configuration Manager, the PeopleSoft installer does not display the screens for the configuration.

If you are installing on an IBM AIX operating system, and you configure Oracle Configuration Manager during the PeopleSoft PeopleTools installation, the installation will complete with errors. To set up Oracle Configuration

Manager on IBM AIX, download the latest Oracle Configuration Manager version from the Collector page on My

Oracle Support, and follow the instructions in the documentation on that page to install and configure it.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

39

Preparing for Installation

Chapter 1

See Also

Oracle Configuration Manager Documentation on the Oracle Technology Network web site, http://www.oracle.com/technetwork/indexes/documentation/index.html

How to Install Oracle Configuration Manager (OCM) for PeopleTools 8.48 through 8.53, My Oracle Support,

(search for article name)

PeopleTools: Change Assistant and Update Manager, "Integrating with Oracle Configuration Manager"

Task 1-3-9: Using Laser Printers

Along with the printer you will need a Windows printer driver to print the online reports that produce 180character-wide reports using the HP LinePrinter font. Your printer must be configured with sufficient memory

(typically 1.5 MB) to produce graphics images for page printouts.

See Also

My Oracle Support, Certifications

Task 1-4: Planning Database Creation

This section discusses:

• Understanding Database Creation

• Determining Databases and Database Names

• Defining Oracle and PeopleSoft Databases

• Using Oracle Pluggable Databases

Understanding Database Creation

When performing a PeopleSoft installation, you will create these types of PeopleSoft databases:

• System (also called SYS) databases, which contain the PeopleSoft PeopleTools and product-specific metadata required for development of a production database.

• Demo (DMO) databases, which are populated with sample data for study, demonstration, or training purposes.

It is important to note the distinction between an Oracle database and a PeopleSoft database, which is a set of

SQL objects that reside within a single Oracle database and share the same owner ID. Oracle recommends that you install only one PeopleSoft database per Oracle instance. For details, see the section "Defining Oracle and

PeopleSoft Databases" later in this task.

If you are installing PeopleSoft software on an Oracle Real Application Cluster (RAC) database, you must use the manual procedure for database setup, and complete other configuration procedures.

See "Creating a Database Manually (on UNIX or Windows)."

See the information on setting up the PeopleSoft installation with Oracle RAC in the PeopleTools: Data

Management product documentation.

40

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 1

Preparing for Installation

Before installing PeopleSoft software, you should install the Oracle RDBMS software. This documentation does not cover installation of Oracle software. Please refer to the Oracle RDBMS installation documentation that accompanied your Oracle software for information.

You need to install 64-bit server and client Oracle RDBMS software for your PeopleSoft installation. The

PeopleSoft PeopleTools database server, Application Server, and Process Scheduler, as well as the PeopleTools

Client features, require 64-bit connectivity.

Task 1-4-1: Determining Databases and Database Names

Before you begin the installation process, you should determine how many PeopleSoft databases (System or

Demo) of which type you need and how you intend to use them. You should also determine the names of the databases at this point, using database names that:

• Are limited to eight characters, all UPPERCASE.

• Capture information about the PeopleSoft product line and the type of database.

For example, you may want to create two databases with the names PSHRDMO and PSHRSYS, using the two characters HR (for Human Resources) to indicate the product line.

Task 1-4-2: Defining Oracle and PeopleSoft Databases

An Oracle database is a set of SQL objects defined by one system catalog in the SYSTEM tablespace and one

SID (system identifier), using one instance of the Oracle server executables and associated files. The Oracle database is commonly referred to as the Oracle SID.

A PeopleSoft database is a set of SQL objects defined as having the same owner ID. These tables are always contained within a single Oracle database. A PeopleSoft database includes the PeopleSoft objects and application data for one or more products in a PeopleSoft product line.

This owner ID (an Oracle user ID) may also be referred to as an Oracle schema or Oracle logical database. Each

PeopleSoft database needs its own owner. We refer to this as the PeopleSoft owner ID, which is also the

PeopleSoft access ID.

Note. You must limit the owner ID (access ID) to eight characters or less. You must limit the owner password

(access password) to 30 characters or less.

We recommend that you install no more than one PeopleSoft database per Oracle instance. When each PeopleSoft database has its own instance, the system is more robust for the following reasons:

• Your developers can bring down their instance of the Oracle server executables, but the others will remain running.

• You have added security with one PeopleSoft database per Oracle instance.

• It is more efficient to tune each instance to the requirements of its corresponding PeopleSoft application database.

If you are unable to run extra Oracle database instances because of resource limitations, such as memory and system semaphores, you can install multiple PeopleSoft databases in the same Oracle instance. Keep the following points in mind if installing multiple PeopleSoft databases within one Oracle database instance:

• When supporting multiple databases in one Oracle instance, increase maxdatafiles from the default of 32 when you create the database.

Check the limits of maxdatafiles for your operating system and increase the value accordingly.

• You need to increase the size of the tablespaces if you use the same ones for each PeopleSoft database schema.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

41

Preparing for Installation

Chapter 1

Sharing tablespaces is not recommended.

• Each PeopleSoft database should have different operator IDs (also known as user IDs) to avoid problems with passwords.

• Each PeopleSoft database needs its own PeopleSoft database name.

This is the database name users enter during the PeopleSoft logon process. It appears in the following locations:

Location

PeopleSoft logon screen

Reference

Database Name

TNSNAMES.ORA

PS.PSDBOWNER table

The service name defined in TNSNAMES.ORA must be the same as that in PS.PSDBOWNER.

DBNAME column

A single table, PS.PSDBOWNER, is created in the Oracle

SID as part of the database creation procedures.

PS.PSDBOWNER is maintained and acts as directory during the sign-on process to all of the PeopleSoft databases in the

Oracle database/SID. There is a single row in the

PS.PSDBOWNER for each PeopleSoft DB contained in the

SID.

This table includes an example of four PeopleSoft databases, uses, and IDs, in one Oracle database:

Database Use SID

Testing

PeopleSoft Database

Name

Owner ID and Access

ID (Oracle Schema)

Owner/Access

Password

HRTST sysadm sysadm hrdm

Development

Training

Training

HRDVLP

HRTRAIN1

HRTRAIN2 sysadm2 sysadm3 sysadm4 sysadm2 sysadm3 sysadm4 hrdm hrdm hrdm

Note. With Oracle 11gR1 the database user ID is case-sensitive. So, when running the installation, system administrators need to make sure the database user ID, such as SYSADM, with all upper-case letters, is represented consistently, wherever it needs to be supplied in the configuration tools and scripts as well as on any signon screen.

Task 1-4-3: Using Oracle Pluggable Databases

If your RDBMS is Oracle 12c, for PeopleSoft PeopleTools 8.54 and later, you can use the Oracle 12c database multitenant architecture, with pluggable databases. The Pluggable Databases (PDB) functionality is an Oracle 12c

Enterprise Edition database feature that enables an Oracle database to function as a container database. A container database (CDB) is an Oracle database that includes one or more pluggable databases (PDBs). A PDB is a portable collection of schemas, schema objects, and non-schema objects that appears to an Oracle Net client as a non-CDB. For an introduction to the Oracle multitenant architecture, PDBs, and CDBs, see the Oracle database documentation.

42

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 1

Preparing for Installation

Using the Oracle multitenant architecture with pluggable databases, a single database instance can host multiple

PeopleSoft application databases.

The owners of PDBs and CDBs and their relationship to PeopleSoft users can be described as follows:

• CDB Administrator (Common User)

A common user is a database user that has the same identity in the root and in every existing and future PDB.

Every common user can connect to and perform operations within the root, and within any PDB in which it has privileges. every common user is either Oracle-supplied or user-created. Examples of Oracle-supplied common users are SYS and SYSTEM.

In PeopleSoft PeopleTools, the Oracle database user who belongs to the ORA_DBA group acts as a CDB

Administrator.

• PDB Administrator (Local User)

A local user is a database user that is not common and can operate only within a single PDB. The PeopleSoft

PeopleTools Access ID acts as the PDB Administrator.

This documentation includes the instructions for creating CDBs and PDBs with both the Database Configuration

Wizard (on UNIX) and manually (on UNIX or Microsoft Windows).

See Also

Oracle Database Concepts 12c Release 1 (12.1), "Introduction to the Multitenant Architecture," Oracle Database

Documentation Library, http://st-doc.us.oracle.com/12/121/server.121/e17633/toc.htm

PeopleTools: Data Management, "Using Pluggable Databases"

Tech Update - PeopleSoft Supports Oracle 12c Multitenant, My Oracle Support, (search for article title)

Task 1-5: Planning Multilingual Strategy

This section discusses:

• Understanding Multilingual Issues

• Choosing a Base Language

• Selecting Additional Languages

• Selecting a Database Character Set

Understanding Multilingual Issues

Before beginning your installation, you should determine which languages your PeopleSoft system will need to support. If multiple languages are required, determine which language will be used most often. These decisions will affect tasks at various stages of the installation, including file server setup, database creation, and the ability to change the base language of the PeopleSoft database after it is created. Even if you do not plan on running your system in more than one language, you should decide the following information before completing this task:

• Database base language

• Additional languages (if any)

• Database character set (AL32UTF8 recommended)

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

43

ITA

JPN

KOR

NOR

POL

POR

ROM

ESP

FRA

GER

HUN

DAN

DUT

ENG

FIN

Preparing for Installation

Chapter 1

The current languages provided by Oracle and their language codes are listed in the following table, as well as the corresponding database character sets for that language. These are the languages for which Oracle provides pretranslated products. If you plan to provide users access to your applications in these languages, Oracle recommends that you install the translations during your initial installation. This approach will keep you from having to perform an upgrade if you decide to add the Oracle-provided translations at a later date. After installation, you also have the option of performing your own translations, and adding additional languages.

In considering which languages to include, whether for pre-translated objects or for your own application development, keep in mind that certain languages require a Unicode database. Oracle recommends Unicode character sets rather than non-Unicode character sets, including Western European and Japanese Shift-JIS, for all installations and upgrades regardless of the languages used.

See Selecting a Database Character Set.

Language Code

ARA

Language

Arabic

Database Character Set

Unicode only

CFR

CZE

Canadian French

Czech

Unicode recommended

Unicode only

Italian

Japanese

Korean

Norwegian

Polish

Portuguese

Romanian

Danish

Dutch

US English

Finnish

Spanish

French

German

Hungarian

Unicode recommended

Unicode recommended

Unicode recommended

Unicode recommended

Unicode recommended

Unicode recommended

Unicode recommended

Unicode only

Unicode recommended

Unicode recommended

Unicode only

Unicode recommended

Unicode only

Unicode recommended

Unicode only

44

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 1

Language Code

RUS

SVE

THA

TUR

UKE

ZHS

ZHT

Language

Russian

Swedish

Thai

Turkish

United Kingdom English

Simplified Chinese

Traditional Chinese

Preparing for Installation

Database Character Set

Unicode only

Unicode recommended

Unicode only

Unicode only

Unicode recommended

Unicode only

Unicode only

See Also

PeopleTools: Global Technology

Task 1-5-1: Choosing a Base Language

Each PeopleSoft database can have only one base language. PeopleSoft databases ship with English as the default base language. Typically, the base language of your database should match the language most commonly used by your organization, as it affects the performance of PeopleSoft applications.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

45

Preparing for Installation

Chapter 1

When PeopleSoft PeopleTools attempts to open language-sensitive objects (such as pages and menus), it first compares the operator's preferred language to the base language of the database. If the preferred language matches the base language, PeopleSoft PeopleTools immediately loads the required definition from the base language

PeopleSoft PeopleTools tables. However, if the user's preferred language differs from the database's base language, PeopleSoft PeopleTools must first query the related language tables for the object. Should a translation of the object not be found in the operator's preferred language, a query is then performed on the base language tables. The following process flow illustrates the selection of the language used for language-sensitive objects, beginning with the language selected when the user signs in to the PeopleSoft application:

Language selection process using the base language and the preferred language

While these queries typically occur very quickly, they still take up valuable processing time. To optimize performance you can set the base language of your database as the language that is used most often by your users.

Another consideration is that because PeopleSoft databases are shipped with a base language of English, maintenance is simpler if English remains the base language. Both configurations are supported by Oracle.

46

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 1

Preparing for Installation

Task 1-5-2: Selecting Additional Languages

Oracle provides translations of all end-user objects with the Global Multi-Language installation files. It is much easier to install additional languages upon initial database creation than to add them later in your implementation process, so we recommend that you choose which additional languages may be required now. There is no limit to the number of languages that can coexist in a single PeopleSoft database; however, remember that each language will require additional storage space, primarily for PeopleSoft PeopleTools objects.

Task 1-5-3: Selecting a Database Character Set

This section discusses:

• Understanding Character Sets

• Using Unicode Databases

Understanding Character Sets

Oracle recommends Unicode AL32UTF8, but also supports non-Unicode (legacy) character sets, in PeopleSoft databases.

The following table lists a selection of character sets, descriptions, and languages that the PeopleSoft software supports for Oracle databases:

Legacy Character Set

WE8ISO8859P1

Description

Western European ISO 8859-1

Languages Supported

All Western European (English,

French, Spanish, Portuguese, German,

Dutch, and so on)

WE8ISO8859P15

WE8MSWIN1252

US7ASCII

JA16SJIS

Note. The Shift-JIS character set

JA16SJISTILDE is also supported.

Western European ISO 8859-15

Western European MS Windows

CP1252

All Western European (English,

French, Spanish, Portuguese, German,

Dutch, and so on), and includes the euro symbol

All Western European (English,

French, Spanish, Portuguese, German,

Dutch and so on), and includes the euro symbol

English

US 7

–bit ASCII

Japanese Shift-JIS 16-bit

The JA16SJIS and JA16SJISTILDE character sets are essentially the same, except for the way that the wave dash and the tilde are mapped to and from

Unicode.

Japanese, English

See PeopleTools: Global Technology, "Selecting and Configuring Character Sets."

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

47

Preparing for Installation

Chapter 1

Using Unicode Databases

To create an Oracle Unicode database, you must specify the character set as either AL32UTF8 or UTF8 in the

CREATE DATABASE statement. The default value for an Oracle Unicode database is AL32UTF8, although

UTF8 is also supported. The difference between the two is that the newer AL32UTF8 supports Unicode supplementary characters.

In addition, you must specify the init.ora parameter

NLS_LENGTH_SEMANTICS

as

CHAR

or

BYTE

based on the database used, as described in the following sections:

See Creating an INIT<SID>.ORA File in "Creating a Database Manually on Windows" or "Creating a Database on UNIX."

See "Creating a Database Manually on UNIX," Creating an Oracle Instance.

Unicode databases are required if the languages that you selected do not share the same character set. Typically, a single character set can encode all languages written in a single script. For example, English, French, and Spanish all share the same script (Latin), so they can coexist in a non-Unicode database. However, Japanese does not share the same script as French, so if you need to have Japanese and French coexist in a single system, you need a

Unicode database.

Note. The characters required for the English language exist in all Unicode and non-Unicode character sets. For example, Japanese and English can coexist in a single Unicode or non-Unicode database.

If you plan on installing or supporting a combination of languages that do not share the same character set, you should use a Unicode database.

If you decide to use Unicode for your database, you do not need to select a character set.

See Understanding Multilingual Issues.

See Understanding Character Sets.

Task 1-6: Preparing for the PeopleTools-Only Upgrade

This section discusses:

• Understanding the PeopleTools Only Upgrade

• Reviewing the Upgrade Documentation

• Shutting Down Servers

• Reviewing Customized Configuration Files

Understanding the PeopleTools Only Upgrade

As part of a PeopleTools-only upgrade, you will need to use files included in the new PeopleSoft PeopleTools release. For PeopleSoft PeopleTools 8.54 and later, you must install a separate PeopleTools codeline PS_HOME that is different than your old release PS_HOME for use in performing the upgrade. When performing a

PeopleTools-only upgrade, prior to the installation of the new release codeline, you will need to perform the tasks described in this section.

48

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 1

Preparing for Installation

Task 1-6-1: Reviewing the Upgrade Documentation

Review Getting Started on Your PeopleTools Upgrade, located on the PeopleTools Upgrade Home Page for your new PeopleSoft PeopleTools release. The installation of the new PeopleTools codeline is only part of the upgrade process. After installing the PeopleTools codeline, you will apply the PeopleTools upgrade Change Package to complete the database portion of the upgrade.

See Also

PeopleSoft PeopleTools Upgrade Home Page for your new release, My Oracle Support

PeopleTools: Change Assistant and Update Manager

Task 1-6-2: Shutting Down Servers

Shut down any application servers, web servers, and Process Scheduler servers. Make sure that there are no lingering domain processes from any Application Server domains. Such threads can interfere with successfully installing new application server files. If there are any threads remaining after you shut down the domains, you must manually remove them.

Note. For IBM AIX, run the slibclean utility as the root user to remove unused shared libraries from memory.

Task 1-6-3: Reviewing Customized Configuration Files

If you have any customized configuration files (such as psappsrv.cfg, psconfig.sh, pscbl.mak, psrun.mak, and so on), organize and save them in order to have them ready for configuring your new release system. This enables you to preserve any tuned variables. If after finishing the upgrade, you want to install and use a different

PS_HOME than the one used during the upgrade, then make sure that these customized configuration files are available for use in configuring your new release system.

Task 1-7: Reviewing Patches and Updates Required at Installation

Before beginning the installation, check the Patches and Updates page on My Oracle Support to identify any patches, updates, or fixes required at installation that you will need to apply, based on the products, product version, and PeopleSoft PeopleTools version that you are installing. Specific instructions for applying the patches and updates are included in each listed incident.

Make note of all the patches and updates, and plan to apply them at appropriate stages during the installation procedure. For example, a replacement for a PeopleTools executable would be applied after installing the media pack to the appropriate server, and so on.

Note. For any patches and updates that require database changes, be sure to read the section on deciding when to apply patches.

See "Completing the Database Setup," Reviewing Patch Application.

The following procedure describes how to access the Patches & Updates database. Contact Oracle if you don't have a user ID and password for My Oracle Support.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

49

Preparing for Installation

Chapter 1

Note. The My Oracle Support interface is updated periodically. For information on using the Patches & Updates area, select the Help link at the top of the page.

To review patches and updates required at installation:

1. Go to My Oracle Support at https://support.oracle.com.

2. Enter your user name and password to log in.

Note. Be sure to log on, or you will not see all of the menu options.

3. Select Patches & Updates.

4. In the Patch Search section, select the Product or Family (Advanced) link.

The Search page includes several search filters. Click the plus sign to add additional filters.

5. In the Product drop-down list, select PeopleSoft Enterprise PT PeopleTools.

Note. PeopleSoft products begin with the word PeopleSoft.

6. In the Release drop-down list, select the appropriate PeopleSoft PeopleTools release for the patch search.

7. Select Install/Upgrade (PeopleSoft) as a search filter, and select Required at Install from the drop-down list beside it.

Note. This search filter is only available when you select PeopleSoft products.

8. Click the Search button (Patch Search).

9. Note any PeopleTools patches and updates that apply to your installation.

Open the Read Me documentation to view information about the patch that you choose for your installation.

10. Return to the Patch Search page (or click Edit Search on the results page) and search for any PeopleSoft application-related incidents by selecting the appropriate product or product family, release, and language.

It is strongly recommended that you include Language as a search filter for PeopleSoft application patch searches.

Make sure the Required for Install option is selected and click the Search button (Patch Search).

11. Note any PeopleSoft application-specific patches and updates that apply to your installation.

Note. Keep in mind that your installation will require additional software components, including web server, report generation, and search software. Be sure to check for updates and patches for any additional component software you install on your environment. Later chapters cover this topic in detail.

After this installation, you can upgrade your Java Runtime Engine (JRE) to a newer version without upgrading

PeopleTools, as long as the new JRE is certified.

See Also

"Installing Web Server Products"

"Installing Additional Components"

"Configuring Integration Between PeopleSoft PeopleTools and Oracle SES"

PeopleTools Certifications - Suggested Fixes, My Oracle Support, (search for the article title)

Operating System, RDBMS, and Additional Component Patches Required for Installation PeopleTools, My

Oracle Support, (search for the article title)

50

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 1

Preparing for Installation

PeopleSoft Enterprise PeopleTools Certification Table of Contents, My Oracle Support, (search for the article title)

Task 1-8: Installing Supporting Applications

Oracle requires that a number of supporting applications be installed for the PeopleSoft installation on batch servers and on any Windows-based client on which batch processes will be run locally. (Throughout the rest of this section we refer to these Windows-based clients as two-tier clients.) Be sure to check My Oracle Support,

Certifications to ensure that you are installing software versions that are certified by Oracle.

COBOL

• Consult the PeopleSoft information on My Oracle Support to verify whether your application requires

COBOL. Remember that COBOL is not needed for PeopleSoft PeopleTools or for applications that do not contain COBOL programs.

See PeopleSoft Enterprise Frequently Asked Questions about PeopleSoft and COBOL Compilers, My Oracle

Support, (search for the article name).

See PeopleSoft Enterprise Frequently Asked Questions about PeopleSoft and the IBM COBOL Compiler, My

Oracle Support, (search for the article name).

• For PeopleSoft applications written in COBOL, install the appropriate version of the COBOL compiler on the server where you will compile.

See "Installing and Compiling COBOL on Windows."

See "Installing and Compiling COBOL on UNIX."

• For UNIX servers, install Micro Focus Server Express or IBM Compiler for IBM AIX.

• For Microsoft Windows servers, install the appropriate version of Micro Focus Net Express.

• If all your servers are on Microsoft Windows operating systems, Oracle recommends that you install a

COBOL compiler on the file server.

You can install PeopleSoft PeopleTools plus any patches on the file server, compile your COBOL there, and then copy the COBOL binaries to your application and batch servers.

• If your application and batch servers are on UNIX or Linux, we recommend that you designate a single server as the compile server, so that you can compile COBOL from this central location and then distribute it to the rest of your application and batch servers.

If you use this approach, you only need to copy patches or customizations over to the compile server. In this case, you would install a COBOL compiler on the master (or compile) server and either the COBOL compiler or runtime on the rest. You can also copy patches or customizations from the file server to all of your UNIX servers and compile the COBOL on each machine.

• The format of COBOL source file names of patches or customizations on the file server should always be

UPPERCASE.cbl to ensure compatibility with your UNIX servers.

• The PeopleSoft Installer installs COBOL source code from the installation directory to your Microsoft

Windows file server and to all UNIX servers, but not to the rest of your Microsoft Windows servers.

SQR

Note that the compile server must have the same operating system as any destination application or batch servers. For example, if your compile server is an IBM AIX machine, you can only copy COBOL compiled there to other IBM AIX application and batch servers. Oracle recommends this approach. It will help you keep your COBOL source code in sync and only requires that you install COBOL in a single location.

• You must install SQR on any non-Windows batch server.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

51

Preparing for Installation

Chapter 1

• On Microsoft Windows batch servers and two-tier clients, you have the option of installing SQR locally, or mapping to a copy installed on the file server.

• Because SQR does not require any local registry settings, you can execute SQR from any Microsoft Windows batch server or two-tier client once SQR has been installed to a shared directory. Installing SQR locally will result in improved performance; over a slow network connection the improvement will be significant.

Microsoft Office

Install Microsoft Office (Excel and Word) on any Windows batch server or two-tier client that will be running

PS/nVision or Microsoft Word batch processes.

Microsoft Office must be installed locally, because it requires registry settings.

See Also

My Oracle Support, Certifications

Task 1-9: Installing the Database Engine

This section discusses:

• Understanding the Database Engine

• Creating a Seed Database

Understanding the Database Engine

If you have not already done so, install the Oracle database engine on your database server.

When installing the Oracle RDBMS, installation option selection influences the resulting generated Oracle Shared

Library. The PeopleSoft product calls the Oracle Shared library when making calls to the Oracle RDBMS.

Task 1-9-1: Creating a Seed Database

Create the seed database during the installation of your Oracle database engine. This will not be your PeopleSoft database, so keep it small and give it a name that is not related to your application. After successfully installing your Oracle database engine, use the seed database to test Oracle Net connectivity from your application servers, batch servers, and workstations.

Task 1-10: Installing Oracle Net on the Server

You need to carry out this step for the database server, batch server, and application server. You need to load the

Oracle Net listener and the communication protocol adapter you are using, such as TCP/IP, IPX, or NetBIOS.

Additionally you should do the following:

• Configure the listener to start automatically upon booting.

Refer to your Oracle documentation for details on setting up the listener.

• Verify that Oracle Net is loaded on the database server by connecting to a database using SQL*PLUS.

Issue the complete connect string including the TCP/IP address or some other node identifier. For example, if you are on TCP/IP, your logon might resemble the following example:

52

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 1

Preparing for Installation

oracleid/[email protected]:service_name

Note. If you have someone outside your company install Oracle Net, make sure that they install the workstation end as well. Also, make sure they demonstrate connectivity between the workstations and the database server.

• Set required Oracle network configuration file parameters.

Note. PeopleTools 8.44 introduced a new feature called Query Kill. For Query Kill to work successfully, your application server must be using a remote network connection (for example, Oracle Net). In addition, you need to set the SQLNET.EXPIRE_TIME = nn parameter in the SQLNET.ORA network configuration file, as discussed below. If you are using a local connection, Query Kill will not work. However, the

BEQUEATH_DETACH=YES parameter in the SQLNET.ORA network configuration file should also be set to keep UNIX defunct processes from being created on aborted batch server processes.

Oracle requires its PeopleSoft customers to use one of the following two Oracle SQLNET.ORA parameters to force the Oracle database server to terminate "dead" or "defunct" threads: SQLNET.EXPIRE_TIME or

BEQUEATH_DETACH.

• The Dead Connection Detection parameter,

SQLNET.EXPIRE_TIME = nn

, applies only to connections being done through Oracle Net (for example, through tnsnames.ora).

This parameter sets a dead connection time-out value. Oracle Net sends a probe periodically to verify that a client-server connection is still active. (Oracle recommends a value of 10. The time increment is in minutes.)

This ensures that connections are not left open indefinitely, due to an abnormal client termination. (Client in this context can be an application server thread.) If the probe finds a dead connection or a connection that is no longer in use, it returns an error, causing the server process to exit.

Note. Be sure to set this parameter in the SQLNET.ORA on the server side.

Note. This parameter works with all the supported versions of Oracle with PeopleTools 8.51 and higher.

Limitations on using the dead connection detection feature are:

• Dead connection detection is not allowed on bequeathed connections.

• Though very small, a probe packet generates additional traffic that may downgrade network performance.

• The server may need to perform additional processing to distinguish the connection probing event from other events that occur, depending on which operating system is in use.

This may also downgrade network performance.

• The parameter Turn Off Unix Signal Handling,

BEQUEATH_DETACH=YES

, applies only to local connections using the BEQ protocol.

Because the client application spawns a server process internally through the Bequeath protocol as a child process, the client application becomes responsible for cleaning up the child process when it completes. When the server process completes its connection responsibilities, it becomes a defunct process. Signal handlers are responsible for cleaning up these defunct processes. Setting this parameter configures the client profile to pass this process to the UNIX init process by disabling signal handlers.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

53

Preparing for Installation

Chapter 1

Task 1-11: Installing Oracle Net on Your Workstation

You must install Oracle Net on each workstation that will connect to the PeopleSoft database server in a two-tier connection. Workstations making a three-tier connection normally do not need connectivity software. However, bear in mind that batch processes (such as COBOL and SQR) that are executed on the client workstation require that database connectivity software be installed on the client workstation. This is necessary because these batch processes must maintain their own SQL connection to the database server.

Note. You must also install Oracle Net on each application server and batch server that will connect to the

PeopleSoft database server.

Oracle Net works with many communication protocols, so ensure that the listener on your database server is using the same protocol as the workstation. Also, keep in mind that the client workstations need simultaneous access to the database server (through Oracle Net) and to the PeopleSoft PeopleTools software on the file server.

You must use the same version of Oracle Net (either 11g or 12c for PeopleSoft PeopleTools 8.54 and later) on your workstations, applications servers, batch servers, and database servers. PeopleSoft PeopleTools 8.55 requires at a minimum the NET 11g (version 11.2.0.x) functionality. Note as well that you must install the necessary protocol driver for your environment, such as the Oracle TCP/IP Adapter.

Note. Ensure that Oracle Net client connectivity is installed prior to performing a PeopleSoft workstation installation. Always check the most recent version of supported platforms on My Oracle Support for the currently supported Oracle Net versions.

See My Oracle Support, Certifications.

Task 1-12: Testing Oracle Net Connectivity

Once you have installed Oracle Net on the database server, application server, or workstation, test that the connection works using the SQL*PLUS utility provided with Oracle Net.

Connect to a database on your database server as the SYSTEM user, and issue the following SQL statement:

SQL> select * from all_users;

Note. Pinging or using Telnet does not test the Oracle Net connection.

Oracle, or your Oracle vendor, is best equipped to assist you if you have any problems installing any Oracle products or connecting to your Oracle database.

Task 1-13: Performing Backups

Before proceeding, you should back up all servers and workstations that are set up for installation so you can recover to this point if necessary. Do the following:

• Back up any changes you made to the database server in setting up your PeopleSoft system.

• Back up any changes you made to your file server while setting aside space for your PeopleSoft system and setting up access privileges.

• Once you set up your install workstations to access the file server and database server simultaneously, back up the workstations.

54

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 1

Preparing for Installation

Task 1-14: Using PeopleSoft Change Assistant and PeopleSoft

Change Impact Analyzer

After you have completed the tasks in this book to install PeopleSoft PeopleTools, including installing any necessary patches and fixes, you need to install PeopleSoft Change Assistant. PeopleSoft Change Assistant is a standalone application that enables you to assemble and organize all of the steps necessary to apply patches and fixes for maintenance updates.

PeopleSoft Change Assistant gathers all the necessary information for a maintenance update from the

Environment Management Hub and uploads it to My Oracle Support. With the environment data available, My

Oracle Support can determine what updates are applicable to your environment. PeopleSoft Change Assistant carries out the following tasks:

• Coordinates with Environment Management Framework to monitor information specific to your PeopleSoft implementation.

• Finds required updates

• Downloads updates

• Creates change packages

Note. Beginning with PeopleSoft PeopleTools 8.53, use the PeopleSoft Update Manager from PeopleSoft

Change Assistant to use a tailored search to find patches, as well as create and apply change packages.

• Applies all change packages

You can also install PeopleSoft Change Impact Analyzer, either as part of the PeopleSoft Change Assistant installation, or separately from the installation executable provided with PeopleSoft PeopleTools. PeopleSoft

Change Impact Analyzer is a Microsoft Windows-based tool that you can use to evaluate the effect of changes you make on your installation.

See Also

"Installing PeopleSoft Change Assistant"

"Installing PeopleSoft Change Impact Analyzer"

PeopleTools: Change Assistant and Update Manager

PeopleTools: Change Impact Analyzer

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

55

Chapter 2

Installing Web Server Products

This chapter discusses:

• Installing Oracle WebLogic Server

• Installing IBM WebSphere Application Server

Task 2-1: Installing Oracle WebLogic Server

This section discusses:

• Understanding the Oracle WebLogic Installation

• Reviewing Troubleshooting Tips

• Obtaining Oracle WebLogic Installation Files from Oracle Software Delivery Cloud

• Installing JDK for Oracle WebLogic

• Installing Oracle WebLogic on Microsoft Windows

• Installing Oracle WebLogic on Linux or UNIX in Silent Mode

• Configuring JDK for Daylight Savings Time Change

• Removing the Oracle WebLogic Installation on Microsoft Windows

• Removing the Oracle WebLogic Installation on Linux or UNIX

Understanding the Oracle WebLogic Installation

PeopleSoft PeopleTools 8.55 supports Java 7 enabled 64-bit Oracle WebLogic Server 12.1.3. Oracle provides installation files for Oracle WebLogic on the Oracle Software Delivery Cloud portal.

See Obtaining Oracle WebLogic Installation Files from Oracle Software Delivery Cloud.

To familiarize yourself with the most current support information and information about any required Oracle

WebLogic service packs based on operating system platform or PeopleSoft PeopleTools versions, consult the

Certifications area of My Oracle Support.

You must install an operating-system specific Java Developers Kit (JDK) before beginning the Oracle WebLogic installation.

See Installing JDK for Oracle WebLogic.

See Also

Oracle Software Delivery Cloud, http://edelivery.oracle.com

My Oracle Support, Certifications

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

57

Installing Web Server Products

Chapter 2

Clustering and High Availability for PeopleTools, My Oracle Support, (search for the article title)

Operating System, RDBMS, and Additional Component Patches Required for Installation PeopleTools, My

Oracle Support, (search for the article title and release number)

Reviewing Troubleshooting Tips

If you have trouble with the installation, review these tips:

• It can require up to 800 MB space to install Oracle WebLogic. If there is not enough space, the installer displays an error with information about the space limitation. You will need to exit the installation and create some space under your home directory before starting over.

• The Oracle WebLogic installer makes use of the default system temporary space. It will stop and display an error message if the temporary space is not sufficient. Clean up the default system temp space and try again. If you do not have the privilege to clean up that directory and need to proceed, the workaround is to set aside a directory under your Home directory and use it as the temporary space. This can be achieved by setting -

Djava.io.tmpdir

in the command for launching the installer.

The following command is a sample Linux command for silent mode installation, which uses the "temp" directory under your Home directory. RESPONSE_DIR refers to the location of the silent mode response file, and INVENTORY_DIR refers to the location of the Oracle inventory file.

See Installing Oracle WebLogic on Linux or UNIX in Silent Mode.

$JAVA_HOME/bin/java -jar -Djava.io.tmpdir=~/temp ./fmw_12.1.3.0.0_⇒ wls.jar -silent -responseFile RESPONSE_DIR/res.rsp -invPtrLoc INVENTORY_

DIR/oraInst.loc

Note. This workaround may not be applicable on all platforms. If you tried and the installer still errors out due to the amount of temporary space, contact your system administrator to clean up the system temporary space before proceeding.

• If the installation fails, and the Middleware Home directory that you specified for the Oracle WebLogic 12.1.3

installation is one in which other Oracle products have been installed in previous releases, (for example c:\oracle folder in Microsoft Windows), it may indicate corruption in the registry.xml file inside your existing

Middleware Home. Pick a different location for the Oracle WebLogic 12.1.3 installation directory and try the installation again.

• If you are installing onto an UNIX or Linux environment, in case of installation failure, refer to the log file

Wls1213Install.log under the installation logs directory to view the events that occurred.

• If you encounter the following error message while running in console mode on a Microsoft Windows operating system, it means an environment variable _JAVA_OPTIONS has been set in your system. It causes the Java process initiated by the Oracle WebLogic installer to fail.

ERROR: JVMPI, an experimental interface, is no longer supported.

Please use the supported interface: the JVM Tool Interface (JVM TI).

To resolve the problem, remove the environment variable _JAVA_OPTIONS from your system and rerun the installation.

• If you encounter the following error message while installing on an Oracle Solaris operating system, it means there is a problem with access to the temporary directory:

*sys-package-mgr*: can't write cache file

This message appears because the Oracle WebLogic installer creates a temporary directory (for example, on

Oracle Solaris it is /var/tmp/wlstTemp) that is shared by all users, and it is unable to differentiate between

58

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 2

Installing Web Server Products

users. As a result, access to the directory is blocked when the user accessing the directory is not the one who originally created the directory. The workaround for this problem is to remove the installation and install it again after manually adjusting the temporary directory permissions. A user with superuser privileges can use the following command to adjust the permissions: chmod -R 777 /var/tmp/wlstTemp

For more information, search the Oracle documentation for Oracle WebLogic.

Task 2-1-1: Obtaining Oracle WebLogic Installation Files from Oracle

Software Delivery Cloud

At this point you should have already downloaded the necessary files from Oracle Software Delivery Cloud. If not, this section includes additional information on finding and using the files for Oracle WebLogic if necessary.

See "Preparing for Installation," Using Oracle Software Delivery Cloud to Obtain Installation Files.

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

To obtain the files for Oracle WebLogic installation:

1. After logging in to Oracle Software Delivery Cloud, read the information about export restrictions, and then click Accept.

2. Enter Oracle WebLogic in the Product field, and select Oracle Server, Enterprise Edition, from the drop-down list.

Note. The Enterprise Edition includes Oracle WebLogic Server and Oracle Coherence, as well as other items.

3. Click Select Platform, select the operating system you are running on, and click Select.

The following operating systems are supported:

• IBM AIX

• HP-UX Itanium

• Linux

• Microsoft Windows

• Oracle Solaris on SPARC

• Oracle Solaris on x86–64

4. Click Continue.

5. On the page listing the selected product, click Continue.

Note. Click the arrow to view the list of products included.

6. Read the license agreements, and select the check box to acknowledge that you accept the agreement, and then click Continue.

7. On the File Download window, download the zip file for Oracle Fusion Middleware 12c (12.1.3.0.0)

WebLogic Server and Coherence.

Download the files you need by clicking a file name to download an individual file, or click Download All to obtain all of the files listed.

Save the zip files to a temporary directory on your local system. The directory where you save the zip file is referred to in this documentation as WLS_INSTALL. You must extract (unzip) the file on the platform for which it is intended. For example, if you download the zip file for Oracle Solaris, you must unzip it on Oracle

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

59

Installing Web Server Products

Chapter 2

Solaris to avoid problems. If you unzip the file to a staging directory on a Microsoft Windows computer and copy the staging directory to an Oracle Solaris, the stage area files may be corrupt.

8. Extract the files into WLS_INSTALL.

The Oracle WebLogic installer file is fmw_12.1.3.0.0_wls.jar.

Note. If you need to FTP the downloaded file, make sure to FTP it in Binary mode.

Task 2-1-2: Installing JDK for Oracle WebLogic

This section discusses:

• Understanding the JDK Requirement for Oracle WebLogic

• Installing JDK for IBM AIX

• Installing JDK for HP-UX Itanium

• Installing JDK for Linux

• Installing JDK for Microsoft Windows

• Installing JDK for Oracle Solaris on SPARC

• Installing JDK for Oracle Solaris on x86-64

Understanding the JDK Requirement for Oracle WebLogic

Before beginning the Oracle WebLogic installation you must install the 64-bit Java 7 JDK. The specific JDK required depends upon the operating system and vendor, as described in this table:

Operating System

Platforms

IBM AIX

HP-UX Itanium

JDK Version Supported

IBM JDK 1.7.0 SR6+

Hewlett-Packard JDK

7.0.08+

64-bit or Mixed Mode*

64-bit

Mixed mode

Comments

none

Use "-d64" to turn on 64

–bit mode

Linux

Microsoft Windows

Oracle Solaris on SPARC

Oracle Solaris on x86

–64

Oracle JDK 1.7.0_51+

Oracle JDK 1.7.0_51+

Oracle JDK 1.7.0_51+

Oracle JDK 1.7.0_51+

64-bit

64-bit

Mixed mode

Mixed mode none none

Requires two installers.

Use "-d64" to turn on 64-bit mode.

Install the X86 JDK installer first and then the one for

X64.

Use "-d64" to turn on 64 bit mode.

* The mixed mode installers run in 32-bit by default. The parameter -d64 is required to run them in 64-bit mode.

60

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 2

Installing Web Server Products

Installing JDK for IBM AIX

To install 64-bit IBM JDK for IBM AIX:

1. Go to the IBM JDK download 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, your AIX support personnel should be able to help.

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

3. Register and log in to download.

4. Download Java7_64_sdk installer for version 7.1.0.15 or higher.

5. Install the JDK on the AIX computer where you will install the Oracle WebLogic server.

The directory where you install the JDK is referred to in this documentation as JAVA_HOME.

Note. Spaces are not allowed in the JAVA_HOME name.

Installing JDK for HP-UX Itanium

To install Hewlett-Packard JDK for an Oracle WebLogic installation on HP-UX Itanium:

1. Go to the Hewlett-Packard download web site: https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=HPUXJDKJRE70

2. Select the link for Version 7.0.08 or higher.

3. Provide the login credentials.

4. Provide the required information.

5. Click Next and download JDK.

6. Install the JDK on the computer where you will install the Oracle WebLogic server.

The directory where you install the JDK is referred to in this documentation as JAVA_HOME.

Note. Spaces are not allowed in the JAVA_HOME name.

Installing JDK for Linux

To install 64-bit JDK for an Oracle WebLogic installation on Linux:

1. Go to the Oracle JDK download site: http://www.oracle.com/technetwork/java/javase/downloads/index.html

2. Download Oracle Java 7 64-bit JDK version 1.7.0_51 or higher for Linux x86-64.

Refer to the JDK installation instructions at the following link: http://docs.oracle.com/javase/7/docs/webnotes/install/linux/linux-jdk.html

3. Install the JDK on the computer where you will install the Oracle WebLogic server. The directory where you install the JDK is referred to in this documentation as JAVA_HOME.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

61

Installing Web Server Products

Note. Spaces are not allowed in the JAVA_HOME name.

Chapter 2

Installing JDK for Microsoft Windows

To install 64-bit JDK for an Oracle WebLogic installation on Microsoft Windows:

1. Go to the Oracle JDK download site: http://www.oracle.com/technetwork/java/javase/downloads/index.html

2. Download Oracle Java 7 64-bit JDK version 1.7.0_51 or higher for Microsoft Windows x86-64.

Refer to the JDK installation instructions at the following link: http://docs.oracle.com/javase/7/docs/webnotes/install/windows/jdk-installation-windows.html

3. Install the JDK on the computer where you will install the Oracle WebLogic server. The directory where you install the JDK is referred to in this documentation as JAVA_HOME.

Note. Spaces are not allowed in the JAVA_HOME name.

Installing JDK for Oracle Solaris on SPARC

To install JDK for an Oracle WebLogic installation on Oracle Solaris on SPARC (64-bit):

1. Go to the Oracle JDK download site: http://www.oracle.com/technetwork/java/javase/downloads/index.html

2. Download the Oracle Java 7 64-bit JDK version 1.7.0_51 or higher for Solaris SPARC.

Be sure to get both files needed for 64-bit JDK for Solaris. The JDK is mixed mode, and the second installer enables the JDK to be run in 64-bit mode, which is triggered by the "-d64" parameter.

Refer to the installation instructions at the following link: http://docs.oracle.com/javase/7/docs/webnotes/install/solaris/solaris-jdk.html

3. Install the JDK on the computer where you will install the Oracle WebLogic server.

The directory where you install the JDK is referred to in this documentation as JAVA_HOME.

Note. Spaces are not allowed in the JAVA_HOME name.

Installing JDK for Oracle Solaris on x86-64

To install JDK for an Oracle WebLogic installation on Oracle Solaris on x86-64:

1. Go to the Oracle JDK download site: http://www.oracle.com/technetwork/java/javase/downloads/index.html

2. Download the Sun Java 7 64-bit JDK version 1.7.0_51 or higher for both Oracle Solaris x86 and Oracle

Solaris x64.

Oracle Solaris x64 requires users to first install the JDK for Oracle Solaris x86 and then run the JDK installer for Oracle Solaris x64. The JDK is mixed mode, and the second installer enables the JDK to be run in 64-bit mode, which is triggered by the "-d64" parameter.

Refer to the installation instructions at the following link:

62

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 2

Installing Web Server Products

http://docs.oracle.com/javase/7/docs/webnotes/install/solaris/solaris-jdk.html

3. Install the JDK on the computer where you will install the Oracle WebLogic server.

The directory where you install the JDK is referred to in this documentation as JAVA_HOME.

Note. Spaces are not allowed in the JAVA_HOME name.

Task 2-1-3: Installing Oracle WebLogic on Microsoft Windows

The following procedure assumes that you saved the installation file fmw_12.1.3.0.0_wls.jar from Oracle

Software Delivery Cloud in the directory WLS_INSTALL. Installation in GUI mode is normally used for

Microsoft Windows operating systems. You should have installed the appropriate JDK to JAVA_HOME before beginning this installation.

See Installing JDK for Oracle WebLogic.

Note. Previous releases of Oracle WebLogic Server, such as 9.2 MPX, and 10.3.X, can coexist with 12.1.3 on a single machine. The best practice is to install Oracle WebLogic 12.1.3 into an empty directory, or at least one that does not contain other Oracle WebLogic (previously BEA) products.

If you choose, however, to install this version of Oracle WebLogic in an existing WLS_HOME directory (for example, c:\oracle), you must shut down all instances of Oracle WebLogic Server running in that WLS_HOME before performing this installation.

To install Oracle WebLogic Server 12.1.3:

1. Open a command prompt and change directory to WLS_INSTALL.

Note. If you are running on a Microsoft Windows operating system, you must run the command prompt as administrator.

2. Set the environment variable JAVA_HOME to be the location where you installed the Oracle Java JDK 7.

For example, if you installed JDK to D:\jdk1.7.0_51 use this command: set JAVA_HOME=D:\jdk1.7.0_51

3. Use the following command to launch the installer:

%JAVA_HOME%\bin\java -jar fmw_12.1.3.0.0_wls.jar

Note. It may take up to five minutes to extract the installer. You see system check messages. The Welcome window appears when the extraction is complete.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

63

Installing Web Server Products

Chapter 2

4. Click Next on the Welcome window for Oracle Fusion Middleware 12c (12.1.3.0.0) WebLogic Server and

Coherence Installer.

Oracle Fusion Middleware 12c WebLogic Server and Coherence Installation - Step 1 of 7: Welcome window

64

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 2

Installing Web Server Products

5. On the Installation Location window, enter a location for the Oracle Home, or browse to an existing directory.

Do not choose a directory that contains an existing installation of Oracle WebLogic.

If the directory does not exist, the Oracle WebLogic installer creates it. The directory where you install Oracle

WebLogic is referred to as WLS_HOME in this documentation. In this example WLS_HOME is C:\WLS1213.

Click Next to continue.

Oracle Fusion Middleware 12c WebLogic Server and Coherence Installation - Step 2 of 7: Installation

Location window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

65

Installing Web Server Products

Chapter 2

6. Accept the default WebLogic Server installation option on the Installation Type window, for WebLogic

Server Installation, and then click Next.

66

Oracle Fusion Middleware 12c WebLogic Server and Coherence Installation - Step 3 of 8: Installation Type window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 2

Installing Web Server Products

7. Wait while the installer carries out prerequisite checks.

Note. You may see the following message if installing Oracle WebLogic 12.1.3 on Microsoft Windows 2012

R2. You can ignore this warning and proceed with the installation:

"Expected result: One of 6.0,6.1,6.2[[

Actual Result: 6.3

Check complete.

The overall result of this check is: Failed"

In this example the system passed the prerequisite checks.

Oracle Fusion Middleware 12c WebLogic Server and Coherence Installation - Step 4 of 8: Prerequisite

Checks window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

67

Installing Web Server Products

Chapter 2

8. Clear the option I wish to receive security updates via My Oracle Support on the Specify Security Updates window, as shown in this example.

68

Oracle Fusion Middleware 12c WebLogic Server and Coherence Installation - Step 5 of 8: Specify Security

Updates window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 2

Installing Web Server Products

9. A dialog box labelled "My Oracle Support Username/Email Address Not Specified" appears; click Yes to confirm that you wish to remain uninformed of critical security issues in your configuration:

My Oracle Support Username/Email Address Not Specified dialog box

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

69

Installing Web Server Products

Chapter 2

10. Verify your choices in the installation summary, such as the installation location and features to install.

If you want to save a response file to be used in silent installation, click Save Response File and provide a location.

Click Install to begin the installation.

70

Oracle Fusion Middleware 12c WebLogic Server and Coherence Installation - Step 6 of 8: Installation

Summary window

A progress indicator appears. Click Next when the tasks are complete, as shown in this example:

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 2

Installing Web Server Products

Oracle Fusion Middleware 12c WebLogic Server and Coherence Installation - Step 7 of 8: Installation

Progress window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

71

Installing Web Server Products

Chapter 2

11. When the installation has completed successfully, clear the Automatically Launch the Configuration Wizard option, and click Finish.

Oracle Fusion Middleware 12c WebLogic Server and Coherence Installation - Step 8 of 8: Installation

Complete window

Task 2-1-4: Installing Oracle WebLogic on Linux or UNIX in Silent Mode

Use these instructions for silent mode installation for Linux and UNIX operating systems.

Note. Console mode installation is not supported beginning with Oracle WebLogic 12.1.3.

See the information on silent installation for Oracle WebLogic in the Oracle Middleware documentation.

The following procedure assumes that you saved the installation file fmw_12.1.3.0.0_wls.jar from Oracle

Software Delivery Cloud in the directory WLS_INSTALL. You should have installed the appropriate JDK to

JAVA_HOME before beginning this installation.

To run the Oracle WebLogic installation in silent mode:

1. Download the Oracle WebLogic installation file and save it in a local directory, referred to here as

WLS_INSTALL.

If you downloaded the zip file for the Oracle WebLogic installation from Oracle Software Delivery Cloud to a

72

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 2

Installing Web Server Products

Microsoft Windows computer, FTP the zip file in binary mode to your Linux or Oracle Solaris computer before unzipping it into WLS_INSTALL.

2. Change directory to WLS_INSTALL and make the installer file executable using the following command: chmod a+x fmw_12.1.3.0.0_wls.jar

3. In a shell window, change directory to WLS_INSTALL: cd WLS_INSTALL

4. Set JAVA_HOME to be the location where you installed the JDK.

For example, if the JDK is installed under "/home/jdklnk7u51", use the following command: export JAVA_HOME=/home/jdklnk7u51

5. If it does not exist, use a text editor, such as "vi", to create the central inventory location file, named oraInst.loc, in a directory referred to in this documentation as INVENTORY_DIR.

The oraInst.loc file contains only the following two lines: inventory_loc=/home/psftuser/oraInventory inst_group=wlsgrp

The oraInst.loc file contains the following information:

• inventory_loc — Specify the full path to the directory where you want the installer to create the inventory directory. The location in the example is /home/psftuser/oraInventory.

• oui_install_group — Specify the name of the group whose members have write permissions to this directory. The group name in the example is wlsgrp.

6. Copy the following content into a text editor and save it as res.rsp.

This is the silent response file. The directory where you save it is referred to here as RESPONSE_DIR.

[ENGINE]

#DO NOT CHANGE THIS.

Response File Version=1.0.0.0.0

[GENERIC]

#The oracle home location. This can be an existing Oracle Home or a new⇒

 Oracle Home

ORACLE_HOME=

#Set this variable value to the Installation Type selected. e.g. Web⇒

Logic Server, Coherence, Complete with Examples.

INSTALL_TYPE=WebLogic Server

#Provide the My Oracle Support Username. If you wish to ignore Oracle⇒

 Configuration Manager configuration provide empty string for user name.

MYORACLESUPPORT_USERNAME=

#Provide the My Oracle Support Password

MYORACLESUPPORT_PASSWORD=<SECURE VALUE>

#Set this to true if you wish to decline the security updates. Setting⇒

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

73

Installing Web Server Products

Chapter 2

 this to true and providing empty string for My Oracle Support username⇒

 will ignore the Oracle Configuration Manager configuration

DECLINE_SECURITY_UPDATES=true

#Set this to true if My Oracle Support Password is specified

SECURITY_UPDATES_VIA_MYORACLESUPPORT=false

#Provide the Proxy Host

PROXY_HOST=

#Provide the Proxy Port

PROXY_PORT=

#Provide the Proxy Username

PROXY_USER=

#Provide the Proxy Password

PROXY_PWD=<SECURE VALUE>

#Type String (URL format) Indicates the OCM Repeater URL which should⇒

 be of the format [scheme[Http/Https]]://[repeater host]:[repeater port]

COLLECTOR_SUPPORTHUB_URL=

7. Use a text editor to enter the full path for ORACLE_HOME.

Oracle WebLogic will be installed into the ORACLE_HOME directory entered here. This must be a new directory; do not enter a directory that has been used previously.

8. If this is the first time you are installing on your system (meaning there is no pre-existing Oracle inventory location), use the following commands to perform a silent installation.

These commands use res.rsp as the name for the response file.

• For IBM AIX or Linux:

$JAVA_HOME/bin/java -jar ./fmw_12.1.3.0.0_wls.jar -silent -response⇒

File RESPONSE_DIR/res.rsp -invPtrLoc INVENTORY_DIR/oraInst.loc

• For HP-UX Itanium or Oracle Solaris (on SPARC or x86–64):

$JAVA_HOME/bin/java -d64 -jar ./fmw_12.1.3.0.0_wls.jar -silent -⇒ responseFile RESPONSE_DIR/res.rsp -invPtrLoc INVENTORY_DIR/ora⇒

Inst.loc

Note. The JVM parameter "-d64" is required for HP-UX Itanium or Oracle Solaris.

9. If you have previously installed an Oracle product on your system and do not need to specify an Oracle inventory location, use the following commands to perform a silent installation:

• For IBM AIX or Linux:

$JAVA_HOME/bin/java -jar ./fmw_12.1.3.0.0_wls.jar -silent -response⇒

File RESPONSE_DIR/res.rsp

• For HP-UX Itanium or Oracle Solaris (on SPARC or x86–64):

$JAVA_HOME/bin/java -d64 -jar ./fmw_12.1.3.0.0_wls.jar -silent -⇒

74

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 2

Installing Web Server Products

responseFile RESPONSE_DIR/res.rsp

Note. The JVM parameter "-d64" is required for HP-UX Itanium or Oracle Solaris.

10. After you enter the commands in the previous steps, the installer is launched in silent mode, and a progress indicator tracks the installation.

When the installation is complete, you should see a completion message such as "The installation of Oracle

Fusion Middleware 12c WebLogic Server and Coherence 12.1.3.0.0 completed successfully."

Task 2-1-5: Configuring JDK for Daylight Savings Time Change

The version of JDK mentioned in the previous section Installing JDK for Oracle WebLogic includes the Daylight

Saving Time (DST) rules available at the time of packaging. If new rules are implemented after this time, you should use the instructions in this section to update the time zone definition files.

You can skip this section unless a change to the DST rules has happened near or after the general availability date of Oracle WebLogic or PeopleSoft PeopleTools. Consult the information on configuring PeopleSoft time zone definitions in the PeopleTools: Global Technology product documentation.

This section provides an example of how the time zone updater utility (TZUPDATER), which is supplied by the

JDK vendors, can be used to update the time zone definition files contained in the JDK used by Oracle WebLogic server.

1. Identify and shut down any JVM processes that are using the JDK that you will be updating.

2. For future reference or restoration, back up the location where the targeted JDK is located.

The JDK being used for different operating systems is different. For Oracle WebLogic 12.1.3.0.0, refer to the commEnv.cmd (for Microsoft Windows), or commEnv.sh (for UNIX) file under WLS_HOME\ oracle_common\common\bin to determine the setting for JAVA_HOME and the exact name and location for the JDK being used by your Oracle WebLogic server. WLS_HOME is the directory where Oracle WebLogic is installed.

3. Download the appropriate updater utility for your operating system from the JDK vendor.

Each tzupdater provided by the vendor comes with instructions (typically in a readme file) describing how to:

• Locate the correct JDK.

• Apply classes using the tzupdater or provided scripts.

• Check tzupdater versions.

Read the instructions carefully as the steps and instructions are vendor-specific. Keep in mind that these instructions and versions may be updated when the vendor finds it necessary.

Note. After successfully running the TZUPDATER to update a JDK location, the changes will take effect only for newly started Java processes from that location. In the event that you did not identify and stop all Java processes running from this location, it will be necessary to stop and restart these for the changes to take effect.

See Also

Timezone Updater Tool, Oracle Technology Network, http://www.oracle.com/technetwork/java/javase/tzupdaterreadme-136440.html

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

75

Installing Web Server Products

Chapter 2

Task 2-1-6: Removing the Oracle WebLogic Installation on Microsoft

Windows

To remove the Oracle WebLogic installation on Microsoft Windows (GUI mode):

1. Before running the deinstaller, stop all servers and processes associated with the Oracle home you are going to remove.

2. Change directory to the WLS_HOME\oui\bin folder and run the deinstall.cmd script.

WLS_HOME is the location where you installed your Oracle WebLogic 12.1.3.0.0. Click Next on the

Welcome window.

76

Oracle Fusion Middleware Deinstallation - Step 1 of 4: Welcome window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 2

Installing Web Server Products

3. Verify the components that you want to uninstall (by default all components are selected as shown in this example).

Oracle Fusion Middleware Deinstallation - Step 2 of 4: Deinstallation Summary window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

77

Installing Web Server Products

Chapter 2

4. Click the Save Response File button and browse to a location to save the file, which you can use for a silent mode deinstallation.

See Removing the Oracle WebLogic Installation on UNIX or Linux.

Click Deinstall. A progress indicator appears. Click Next when the tasks are complete, as shown in this example.

78

Oracle Fusion Middleware Deinstallation - Step 3 of 4: Deinstallation Progress window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 2

5. Click Finish on the Deinstallation Complete window.

Installing Web Server Products

Oracle Fusion Middleware Deinstallation - Step 4 of 4: Deinstallation Complete window

6. Remove the WLS_HOME directory manually after the deinstallation.

Task 2-1-7: Removing the Oracle WebLogic Installation on Linux or UNIX

To remove the installation on Linux or UNIX, you run in console mode, and use a response file.

Note. The previous section, Removing the Oracle WebLogic Installation on Microsoft Windows, included a step in which you saved a response file. You can edit and use this response file for different operating system platforms.

To remove the Oracle WebLogic installation on UNIX or Linux in silent mode:

1. Before running the deinstaller, stop all servers and processes associated with the Oracle home you are going to remove.

2. If you need to create a response file, copy the following content into a text editor and save it.

This is the silent response file, referred to here as RESPONSE_DIR/response.txt.

[ENGINE]

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

79

Installing Web Server Products

Chapter 2

#DO NOT CHANGE THIS.

Response File Version=1.0.0.0.0

[GENERIC]

#This will be blank when there is nothing to be de-installed in⇒

 distribution level

SELECTED_DISTRIBUTION=WebLogic Server~12.1.3.0.0

#The oracle home location. This can be an existing Oracle Home or a new⇒

 Oracle Home

ORACLE_HOME=

3. Edit the ORACLE_HOME line to add the location where you installed Oracle WebLogic 12.1.3.0.0.

4. Change directory to WLS_HOME/oui/bin and locate the deinstall.sh script.

WLS_HOME is the location where you installed your Oracle WebLogic 12.1.3.0.0.

5. Run the following command.

For INVENTORY_DIR, specify the full directory path containing the Oracle installer inventory file, oraInst.loc.

See Installing Oracle WebLogic on Linux or UNIX in Silent Mode.

./deinstall.sh -silent -response RESPONSE_DIR/response.txt -invPtrLoc ⇒

INVENTORY_DIR/oraInst.loc

6. An indicator shows the progress of the removal process, followed by a completion message such as "The uninstall of Oracle Fusion Middleware 12c WebLogic Server and Coherence 12.1.3.0.0 completed successfully."

7. Remove the WLS_HOME directory manually to complete the deinstallation.

Task 2-2: Installing IBM WebSphere Application Server

This section discusses:

• Understanding IBM WebSphere Installation

• Prerequisites

• Obtaining IBM WebSphere Installation Files

• Installing IBM WebSphere 8.5.5.0 ND

• Installing IBM HTTP Server 8.5.5.0

• Installing IBM WebSphere Plug-ins 8.5.5.0

Understanding IBM WebSphere Installation

Oracle supports 64-bit IBM® WebSphere® Application Server Network Deployment 8.5.5.0 (referred to as IBM

WebSphere ND in this documentation) for PeopleSoft PeopleTools 8.55. The IBM WebSphere ND requires IBM

Runtime Environment, Java Technology Edition 6.0.1 (J9 2.6).

80

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 2

Installing Web Server Products

IBM WebSphere Application Server supports IBM HTTP server (IHS) as a HTTP Reverse Proxy server. IBM

WebSphere Application Server alone cannot act as a proxy server for PeopleSoft PeopleTools REN Server. You must also install PeopleSoft Pure Internet Architecture, as well as installing the IBM HTTP server. Consult My

Oracle Support for information on the versions of IHS certified for use with PeopleSoft PeopleTools.

This section includes guidelines for installing IBM WebSphere ND, the Web server plug-ins for IBM WebSphere

Application Server, and IHS. For detailed installation instructions, see the IBM documentation.

See Also

My Oracle Support, Certifications

Clustering and High Availability for PeopleTools, My Oracle Support, (search for the article name)

IBM WebSphere Application Server Information Center, http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/index.jsp

Prerequisites

IBM WebSphere ND is certified for PeopleSoft PeopleTools 8.55 on the following operating systems:

• IBM AIX

• HP-UX Itanium

• Linux

• Microsoft Windows

• Oracle Solaris

The full lists of prerequisites for IBM WebSphere Application Server Network Deployment 8.5.5.0 are available on the IBM website:

See http://www-01.ibm.com/support/docview.wss?uid=swg24034969

In addition, review the following prerequisites before beginning your installation:

• Both IBM WebSphere ND and PeopleSoft Pure Internet Application (PIA) need to be installed and deployed using the same user ID. Following this requirement avoids security and profile management issues.

• On Microsoft Windows operating systems, if you are not using the built-in administrator account to run the commands, you will need stronger user account privileges to carry out the installation of IBM Installation

Manager.

To set the appropriate privileges, right-click the installer and select Run as administrator. Do the same thing for the installation of IBM Installation Manager.

• On UNIX platforms, the /var file system is used to store all the security logging information for the system.

Therefore it is critical that you maintain free space in /var for these operations.

• When you carry out the GUI mode installation on UNIX, executing the installation wizard launches a GUI window. You must run this command from an X-Windows client window (for example, Reflection-X).

• PeopleSoft PeopleTools 8.55 supports the IBM HTTP Server (IHS) 8.5.5.0 that is bundled with the IBM

WebSphere 8.5.5.0 installation. Use of an external remote proxy server (RPS) is optional.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

81

Installing Web Server Products

Chapter 2

Task 2-2-1: Obtaining IBM WebSphere Installation Files

For PeopleSoft PeopleTools 8.55, the installation files for IBM WebSphere are not packaged with PeopleSoft

PeopleTools on Oracle Software Delivery Cloud. To download the necessary files for the IBM WebSphere installation, contact IBM. The installation of IBM WebSphere 8.5.5.0 requires the download of the following components:

• IBM Installation Manager V1.6.2

• WebSphere Application Server Network Deployment V8.5.5.0 64-bit

• IBM HTTP Server V8.5.5.0 64-bit

• Plug-ins V8.5.5.0 64-bit

• IBM SDK V1.7

The distribution is provided as operating-system-specific zip files. The base binaries of IBM WebSphere 8.5.5.0,

IHS 8.5.5.0, and Plug-in 8.5.5.0 have to be downloaded by providing an IBM partner ID and password.

Download and extract the appropriate zip files for your operating system, listed in the following tables.

IBM AIX

File or Folder Name

QS_FOR_WAS_ND_V8.5.5.0.zip

Description

Quick Start for IBM WebSphere Application Server

Network Deployment V8.5

WAS_ND_V8.5.5_1_OF_3.zip

WAS_ND_V8.5.5_2_OF_3.zip

WAS_ND_V8.5.5_3_OF_3.zip

WS_SDK_JAVA_TEV7.0_1OF3_WAS_8.5.5.zip

WS_SDK_JAVA_TEV7.0_2OF3_WAS_8.5.5.zip

WS_SDK_JAVA_TEV7.0_3OF3_WAS_8.5.5.zip

WAS_V8.5.5_SUPPL_1_OF_3.zip

WAS_V8.5.5_SUPPL_2_OF_3.zip

WAS_V8.5.5_SUPPL_3_OF_3.zip

InstalMgr1.6.2_AIX_PPC_WAS_8.5.5.zip

Binaries for IBM WebSphere Application Server Network

Deployment V8.5.5.0

Binaries for IBM WebSphere SDK Java (TM) Technology

Edition V7.0

Binaries for Application Client, IBM HTTP Server, Web

Server Plug-ins and WebSphere Customization Toolbox

Binaries for IBM Installation Manager v1.6.2 for AIX

HP-UX Itanium

File or Folder Name

QS_FOR_WAS_ND_V8.5.5.0.zip

WAS_ND_V8.5.5_1_OF_3.zip

WAS_ND_V8.5.5_2_OF_3.zip

WAS_ND_V8.5.5_3_OF_3.zip

Description

Quick Start for IBM WebSphere Application Server

Network Deployment V8.5

Binaries for IBM WebSphere Application Server Network

Deployment V8.5.5.0

82

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 2

File or Folder Name

WS_SDK_JAVA_TEV7.0_1OF3_WAS_8.5.5.zip

WS_SDK_JAVA_TEV7.0_2OF3_WAS_8.5.5.zip

WS_SDK_JAVA_TEV7.0_3OF3_WAS_8.5.5.zip

WAS_V8.5.5_SUPPL_1_OF_3.zip

WAS_V8.5.5_SUPPL_2_OF_3.zip

WAS_V8.5.5_SUPPL_3_OF_3.zip

InstalMgr1.6.2_HPUXIA64_WAS_8.5.5.zip

Linux

File or Folder Name

QS_FOR_WAS_ND_V8.5.5.5.zip

WAS_ND_V8.5.5_1_OF_3.zip

WAS_ND_V8.5.5_2_OF_3.zip

WAS_ND_V8.5.5_3_OF_3.zip

WS_SDK_JAVA_TEV7.0_1OF3_WAS_8.5.5.zip

WS_SDK_JAVA_TEV7.0_2OF3_WAS_8.5.5.zip

WS_SDK_JAVA_TEV7.0_3OF3_WAS_8.5.5.zip

WAS_V8.5.5_SUPPL_1_OF_3.zip

WAS_V8.5.5_SUPPL_2_OF_3.zip

WAS_V8.5.5_SUPPL_3_OF_3.zip

InstalMgr1.6.2_LNX_PPC_WAS_8.5.5.zip

InstalMgr1.6.2_LNXS390_WAS_8.5.5.zip

InstalMgr1.6.2_LNX_X86_64_WAS_8.5.5.zip

Microsoft Windows

File or Folder Name

QS_FOR_WAS_ND_V8.5.5.0.zip

Installing Web Server Products

Description

Binaries for IBM WebSphere SDK Java (TM) Technology

Edition V7.0

Binaries for Application Client, IBM HTTP Server, Web

Server Plug-ins and WebSphere Customization Toolbox

Binaries for IBM Installation Manager v1.6.2 for HP-UX

Itanium

Description

Quick Start for IBM WebSphere Application Server

Network Deployment V8.5

Binaries for IBM WebSphere Application Server Network

Deployment V8.5.5.0

Binaries for IBM WebSphere SDK Java (TM) Technology

Edition V7.0

Binaries for Application Client, IBM HTTP Server, Web

Server Plug-ins and WebSphere Customization Toolbox

Binaries for IBM Installation Manager v1.6.2 for Linux

PowerPC

Binaries for IBM Installation Manager v1.6.2 for Linux s390

Binaries for IBM Installation Manager v1.6.2. for Linux x86

64-bit

Description

Quick Start for IBM WebSphere Application Server

Network Deployment V8.5

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

83

Installing Web Server Products

File or Folder Name

WAS_ND_V8.5.5_1_OF_3.zip

WAS_ND_V8.5.5_2_OF_3.zip

WAS_ND_V8.5.5_3_OF_3.zip

WS_SDK_JAVA_TEV7.0_1OF3_WAS8.5.5.zip

WS_SDK_JAVA_TEV7.0_2OF3_WAS8.5.5.zip

WS_SDK_JAVA_TEV7.0_3OF3_WAS8.5.5.zip

WAS_V8.5.5_SUPPL_1_OF_3.zip

WAS_V8.5.5_SUPPL_2_OF_3.zip

WAS_V8.5.5_SUPPL_3_OF_3.zip

InstalMgr1.6.2_WINX86_64_WAS_8.5.5.zip

Oracle Solaris on SPARC

File or Folder Name

QS_FOR_WAS_ND_V8.5.5.0.zip

WAS_ND_V8.5.5_1_OF_3.zip

WAS_ND_V8.5.5_2_OF_3.zip

WAS_ND_V8.5.5_3_OF_3.zip

WS_SDK_JAVA_TEV7.0_1OF3_WAS_8.5.5.zip

WS_SDK_JAVA_TEV7.0_2OF3_WAS_8.5.5.zip

WS_SDK_JAVA_TEV7.0_3OF3_WAS_8.5.5.zip

WAS_V8.5.5_SUPPL_1_OF_3.zip

WAS_V8.5.5_SUPPL_2_OF_3.zip

WAS_V8.5.5_SUPPL_3_OF_3.zip

InstalMgr1.6.2SOLSPARC_WAS_8.5.5.zip

Oracle Solaris on x86_64

File or Folder Name

QS_FOR_WAS_ND_V8.5.5.0.zip

Chapter 2

Description

Binaries for IBM WebSphere Application Server Network

Deployment V8.5.5.0

Binaries for IBM WebSphere SDK Java (TM) Technology

Edition V7.0

Binaries for Application Client, IBM HTTP Server, Web

Server Plug-ins and WebSphere Customization Toolbox

Binaries for IBM Installation Manager v1.6.2 for Microsoft

Windows

Description

Quick Start for IBM WebSphere Application Server

Network Deployment V8.5

Binaries for IBM WebSphere Application Server Network

Deployment V8.5.5.0

Binaries for IBM WebSphere SDK Java (TM) Technology

Edition V7.0

Binaries for Application Client, IBM HTTP Server, Web

Server Plug-ins and WebSphere Customization Toolbox

Binaries for IBM Installation Manager v1.6.2 for Solaris

SPARC

Description

Quick Start for IBM WebSphere Application Server

Network Deployment V8.5

84

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 2

File or Folder Name

WAS_ND_V8.5.5_1_OF_3.zip

WAS_ND_V8.5.5_2_OF_3.zip

WAS_ND_V8.5.5_3_OF_3.zip

WS_SDK_JAVA_TEV7.0_1OF3_WAS_8.5.5.zip

WS_SDK_JAVA_TEV7.0_2OF3_WAS_8.5.5.zip

WS_SDK_JAVA_TEV7.0_3OF3_WAS_8.5.5.zip

WAS_V8.5.5_SUPPL_1_OF_3.zip

WAS_V8.5.5_SUPPL_2_OF_3.zip

WAS_V8.5.5_SUPPL_3_OF_3.zip

InstalMgr1.6.2_SOL_X86_WAS8.5.5.zip

Installing Web Server Products

Description

Binaries for IBM WebSphere Application Server Network

Deployment V8.5.5.0

Binaries for IBM WebSphere SDK Java (TM) Technology

Edition V7.0

Binaries for Application Client, IBM HTTP Server, Web

Server Plug-ins and WebSphere Customization Toolbox

Binaries for IBM Installation Manager v1.6.2 for Solaris x86_64

Task 2-2-2: Installing IBM WebSphere 8.5.5.0 ND

For detailed information on installing IBM WebSphere 8.5.5.0. ND, see the documentation on the IBM web site.

See the previous section, Obtaining IBM WebSphere Installation Files, for the installation file names for your operating system. The installation of IBM WebSphere Application Server Network includes the following steps:

1. Install IBM Installation Manager V1.6.2

2. Install IBM WebSphere 8.5.5.0 64-bit

3. Install IBM WebSphere SDK Java (TM) Technology Edition V7.0

Task 2-2-3: Installing IBM HTTP Server 8.5.5.0

For detailed information on installing IHS 8.5.5.0, see the documentation on the IBM web site. See the previous section, Obtaining IBM WebSphere Installation Files, for the installation file names for your operating system.

To install IHS 8.5.5.0 64-bit, use IBM Installation Manager.

Task 2-2-4: Installing IBM WebSphere Plug-ins 8.5.5.0

For detailed information on installing the Web server plug-ins for IBM WebSphere Application Servers, see the documentation on the IBM web site. See the earlier section, Obtaining IBM WebSphere Installation Files, for the installation file names for your operating system.

To install the IBM Plug-ins 8.5.5.0 64-bit for IBM WebSphere Application Servers, use IBM Installation

Manager.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

85

Chapter 3

Installing Additional Components

This chapter discusses:

• Reviewing Additional Components

• Installing Oracle Tuxedo

Reviewing Additional Components

Depending upon your PeopleSoft installation environment, you may need to install and configure software components that are not included with the PeopleSoft PeopleTools installation files, or which you acquire from vendors other than Oracle. Some of the components that are discussed in this installation guide include:

• Oracle Tuxedo

The installation of Oracle Tuxedo is required for a basic PeopleSoft PeopleTools installation, and is covered in this chapter.

• COBOL

COBOL is not needed for PeopleSoft PeopleTools or for PeopleSoft Applications that contain no COBOL programs. Check My Oracle Support for details about whether your application requires COBOL.

See "PeopleSoft Enterprise Frequently Asked Questions About PeopleSoft and COBOL Compilers," My

Oracle Support (search for article title).

See "PeopleSoft Enterprise Frequently Asked Questions About PeopleSoft and the IBM COBOL Compiler,"

My Oracle Support (search for article title).

The installation and configuration of Micro Focus and IBM COBOL compilers are covered in later chapters.

See "Installing and Configuring COBOL on UNIX."

See "Installing and Configuring COBOL on Windows."

• Oracle Secure Enterprise Search

Oracle Secure Enterprise Search (SES) is the search engine for the PeopleSoft Search Framework. The integration of Oracle SES with PeopleSoft PeopleTools is covered in a later chapter.

See "Configuring Integration Between PeopleSoft PeopleTools and Oracle SES."

Note. Use the My Oracle Support Certifications area to determine the latest certified versions of additional components that are supported for the PeopleSoft PeopleTools release you are installing.

See Also

"Installing the Verity Installation Kit"

87

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Installing Additional Components

Chapter 3

Task 3-1: Installing Oracle Tuxedo

This section discusses:

• Understanding Oracle Tuxedo

• Prerequisites

• Debugging the Oracle Tuxedo Installer

• Obtaining the Oracle Tuxedo Installation Files from Oracle Software Delivery Cloud

• Obtaining the Oracle Tuxedo Patches from My Oracle Support

• Removing Existing Oracle Tuxedo Installations from Microsoft Windows (Optional)

• Designating the Application Server Administrator on Microsoft Windows

• Installing Oracle Tuxedo on Microsoft Windows in GUI Mode

• Installing the Oracle Tuxedo Patch on Microsoft Windows

• Installing Oracle Tuxedo on Microsoft Windows in Silent Mode

• Uninstalling the Oracle Tuxedo Patch on Microsoft Windows

• Uninstalling Oracle Tuxedo in GUI Mode

• Checking the Windows Service Account

• Restricting Domain Process Privileges

• Setting Up the Windows Services for Oracle Tuxedo

• Verifying the Server Installation on Microsoft Windows

• Removing Existing Oracle Tuxedo Installations from UNIX (Optional)

• Completing the Preinstallation Checklist on UNIX

• Designating the Oracle Tuxedo Owner on UNIX

• Installing Oracle Tuxedo in Silent Mode on UNIX

• Installing the Oracle Tuxedo Patch on UNIX

• Uninstalling the Oracle Tuxedo Patch from UNIX

• Uninstalling Oracle Tuxedo from UNIX Using Silent Mode

• Verifying the Server Installation on UNIX

• Ensuring that Oracle Tuxedo Coexists with Earlier Versions

Understanding Oracle Tuxedo

The PeopleSoft application server uses the Oracle® Fusion Middleware product, Oracle Tuxedo, to perform transaction management, messaging, and administration. This task guides you through the installation of Oracle

Tuxedo on your server. It is essential that you install Oracle Tuxedo 64-bit, version 12c Release 2 (12.1.3.0), which is available on Oracle Software Delivery Cloud. You need to install Oracle Tuxedo before you go any further in setting up your application server and your PeopleSoft Pure Internet Architecture. After you perform the installation described here, you will configure the application server environment to incorporate Oracle Tuxedo with the PeopleSoft components.

Oracle supports Oracle Tuxedo 12c Release 2 (64-bit) for Linux or UNIX, and Oracle Tuxedo 12c Release 2 (64bit) with MS Visual Studios 2012 for Microsoft Windows, with PeopleSoft PeopleTools 8.55.

88

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 3

Installing Additional Components

The minimum patch level certified for running Oracle Tuxedo 12c Release 2 with PeopleSoft PeopleTools 8.55 is

RP037. These installation instructions include the installation of the base Oracle Tuxedo 12c Release 2, followed by the patch installation.

Note. Oracle Tuxedo 12c Release 2 for Linux operating systems supports Exalogic optimizations.

For PeopleSoft customers running on Oracle Exalogic Elastic Cloud, we strongly recommend the use of the

Exalogic OVM Template for PeopleSoft.

See Oracle's PeopleSoft Virtualization Products, My Oracle Support, Doc ID 1538142.1.

Note. For the sake of brevity and convenience, this documentation shortens "Oracle Tuxedo 12c Release 2 (64bit)" to "Oracle Tuxedo 12cR2" and "Oracle Tuxedo 12c Release 2 (64-bit) with MS Visual Studios 2012" to

"Oracle Tuxedo 12cR2_VS2012."

If you have a previous version of Oracle Tuxedo installed, you need to install the new version of Oracle Tuxedo, and re-create your application server domains. (You must create your domains using PSADMIN; you cannot migrate existing domains.) You can also use the PSADMIN domain import utility.

You can install Oracle Tuxedo once for each release on a machine, regardless of the number of PeopleSoft applications or databases the server supports. For example, if you installed Oracle Tuxedo 10gR3 for an earlier release of your PeopleSoft application, you may install Oracle Tuxedo 12cR2 on the same machine in a separate directory. For example:

On Windows, you may install into C:\oracle\tuxedo10gR3_VS2008 and C:\oracle\tuxedo12.1.3.0.0_VS2012.

On UNIX, you may install into /home/oracle/tuxedo10gR3 and /home/oracle/tuxedo12cR2.

If more than one PeopleSoft application uses the same Oracle Tuxedo version (that is, the same patch level), then it is recommended that you have a single installation of Oracle Tuxedo to serve all the supported PeopleSoft applications. A single Oracle Tuxedo installation simplifies future maintenance (such as applying patches).

However, if you choose to have more than one Oracle Tuxedo installation (this scenario is possible only on UNIX systems, as Oracle Tuxedo does not allow multiple installations of the same version of Oracle Tuxedo on

Microsoft Windows), you must install and maintain the same Oracle Tuxedo version more than once in different directories.

See Also

Oracle Tuxedo Documentation on Oracle Technology Network, http://www.oracle.com/technetwork/middleware/tuxedo/documentation/index.html

PeopleTools: Portal Technology

PeopleTools: System and Server Administration

Operating System, RDBMS, and Additional Component Patches Required for Installation PeopleTools, My

Oracle Support (search for article name and select the release)

Clustering and High Availability for PeopleTools, My Oracle Support (search for title)

Using OVM Templates for PeopleSoft on Exalogic, My Oracle Support (search for title)

Prerequisites

Before you begin to install Oracle Tuxedo, make sure that you have the following resources in place:

• TCP/IP connectivity (required for PeopleSoft PeopleTools 8.50 or higher) between the client machine and the application server

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

89

Installing Additional Components

Chapter 3

• For UNIX, you must have root access.

• Enough free disk space on the application server to install the product.

The disk space requirements vary by operating system. For free disk space requirements, see the Oracle

Tuxedo documentation.

The Oracle Tuxedo installer uses the default system temporary space. If there is not enough space for installation, it will stop with an error. To specify a different temporary directory on Microsoft Windows, use the following command before starting the installer: set IATEMPDIR=Complete_Path_Temp_Dir

Replace Complete_Path_Temp_Dir with the full path to the temporary directory that you want to use for the installation.

If you are sure you have enough space, but the installer still gives an error about low disk space (this usually happens on Linux), run the following command before starting the installer: unset BLOCKSIZE

Debugging the Oracle Tuxedo Installer

If the Oracle Tuxedo installation fails with no error message, open a command prompt and enter the following command: set LAX_DEBUG=1

After entering this command, start the installer again. If you are using GUI mode on Microsoft Windows, you must start the installer using the same command prompt.

Task 3-1-1: Obtaining the Oracle Tuxedo Installation Files from Oracle

Software Delivery Cloud

You can obtain the files needed to install Oracle Tuxedo 12cR2 or 12cR2_VS2012 from the Oracle Software

Delivery Cloud portal. At this point you should have already downloaded the necessary files. If you have not yet downloaded the files, this section includes additional information on finding and using the files for Oracle Tuxedo if necessary.

See "Preparing for Installation," Using Oracle Software Delivery Cloud to Obtain Installation Files.

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

1. After logging in to Oracle Software Delivery Cloud, read the export restrictions, and then click Accept.

2. Enter Oracle Tuxedo in the Product field, and select Oracle Tuxedo from the drop-down list.

3. Click Select Platform, select the operating system you are running on, and then click Select.

4. Click Continue.

5. Click the arrow to expand the product list, select the check box for Oracle Tuxedo 12.1.3.0.0, and click

Continue.

6. Read the license agreement and select the check box to acknowledge that you accept the agreement.

7. Click Continue.

8. Click one of the filenames to download an individual zip file, or click Download All to obtain all of the files.

Save the zip files to a temporary directory on your local system, referred to in this documentation as

TUX_INSTALL.

90

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 3

Installing Additional Components

9. After you download the installation files from Oracle Software Delivery Cloud, if it is necessary, transfer the files to a UNIX computer using FTP. Unzip the file and change the permissions of the unzipped file to make it an executable, for example using the chmod +x command.

10. Extract the files into TUX_INSTALL.

After you extract, you see a Disk1 folder with two subfolders, install and stage.

Note. For the PeopleTools Client, install Oracle Tuxedo 12cR2_VS2012 for Microsoft Windows (64-bit) to run with PeopleSoft PeopleTools 8.55.

Task 3-1-2: Obtaining the Oracle Tuxedo Patches from My Oracle Support

You can download the latest patch for Oracle Tuxedo 12cR2_VS2012 for Microsoft Windows or Oracle Tuxedo

12cR2 for Linux or UNIX from My Oracle Support. Patches released for Oracle Tuxedo 12cR2 and

12cR2_VS2012 will also be supported.

Note. To obtain older Oracle Tuxedo patches, raise a service request through My Oracle Support.

To obtain the latest Oracle Tuxedo patch:

1. Sign in to My Oracle Support with your account name and password: https://support.oracle.com

2. Select the Patches & Updates tab.

3. Under Patch Search, select Product or Family (Advanced Search).

4. Select Oracle Tuxedo from the product drop-down list.

5. Select Oracle Tuxedo 12.1.3.0.0 from the release drop-down list.

6. Select your platform.

Note. For detailed supported platform information, see the certifications area on My Oracle Support.

The supported platforms are:

• AIX

• HP-UX Itanium

• Linux

• Microsoft Windows

• Oracle Solaris

7. Click Search.

Download the necessary files from the list of results. For installation on Microsoft Windows operating systems, make sure your rolling patch (RP) description has "VS2012" or "Visual Studio 2012" in the description.

Note. To begin a new search, select Edit Search in the top right of the results page.

8. Download the patch file for your operating system platform to a convenient directory, referred to here as

TUX_INSTALL.

9. After you install a patch, use these steps to verify the installation: a. In a command prompt, change directory to TUXDIR\bin (where TUXDIR is the Oracle Tuxedo installation location).

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

91

Installing Additional Components

Chapter 3 b. Execute the following command: tmadmin -v

The command displays the patch level. For example:

INFO: Oracle Tuxedo, Version 12.1.3.0.0_VS2012, 64-bit, Patch Level ⇒

(012)

Task 3-1-3: Removing Existing Oracle Tuxedo Installations from Microsoft

Windows (Optional)

You may already have prior versions of Oracle Tuxedo installed on your system from an earlier version of

PeopleSoft PeopleTools. If you are completely upgrading to PeopleSoft PeopleTools 8.55 from an earlier version of PeopleSoft PeopleTools, then you may uninstall the existing version and patches.

Note. It is not mandatory to uninstall the existing version of PeopleSoft PeopleTools, as Oracle Tuxedo

12cR2_VS2012 can coexist with prior versions on the same machine.

If you wish to use two versions of PeopleSoft PeopleTools that depend on different versions of Oracle Tuxedo, you should read the section "Ensuring that Oracle Tuxedo Coexists with Earlier Versions" before continuing.

You may have to uninstall Oracle Tuxedo for these reasons:

• You are having problems starting Oracle Tuxedo and decide to reinstall.

• You no longer need Oracle Tuxedo on a machine.

To uninstall Oracle Tuxedo from Microsoft Windows:

1. Using PSADMIN, shut down any application server, Process Scheduler, and Search server domains that may be running on the machine.

2. Stop the processes for the Tuxedo Monitor and the Tuxedo Administrative Web Server (wlisten and tuxwsvr), if applicable.

a. Right-click on the task bar and select Task Manager.

b. Highlight wlisten, and click the End Task button.

c. Highlight tuxwsvr and click the End Task button.

d. Exit Task Manager.

3. Stop and set the TListen VERSION service to manual, if applicable.

Replace VERSION with the version number for the existing service. For example, this would be TListen 9.1 or

TListen 10gR3.

a. Select Start, Settings, Control Panel. Double-click Administrative Tools, and double-click the Services icon.

b. Select TListen VERSION and click the Stop button. c. Choose the Startup Type and set to Manual.

4. Stop and set the ORACLE ProcMGR VERSION (or BEA ProcMGR VERSION for earlier releases) service to manual.

a. Select Start, Settings, Control Panel. Double-click Administrative Tools, and double-click the Services icon.

b. Select ORACLE ProcMGR VERSION and click the Stop button.

c. Choose the Startup Type and set to Manual.

92

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 3

Installing Additional Components

5. Reboot your machine.

6. Uninstall Oracle Tuxedo in one of the following ways:

• Using the Oracle Tuxedo VERSION installation CD provided by Oracle for PeopleSoft installations, open a Command Window, navigate to the root of the CD, and enter pstuxinstall rmall

. This will remove Oracle Tuxedo VERSION plus any delivered Oracle Tuxedo patches from your system.

• Using the Add/Remove Programs dialog, in sequence remove: Oracle TuxedoVERSION RP and then

Oracle Tuxedo VERSION.

7. Go to the Control Panel, double-click on the System icon, and then perform the following actions: a. Make sure TUXDIR\bin is deleted from the PATH environment variable definition.

TUXDIR refers to the Oracle Tuxedo installation directory.

b. Delete the environment variable TUXDIR.

c. Make sure you click on Apply and OK to save your changes.

8. Using Explorer, delete the Tuxedo home directory, such as C:\bea\tuxedo8.1.

If you are unable to delete any files, reboot your machine and retry.

Task 3-1-4: Designating the Application Server Administrator on Microsoft

Windows

Before beginning the installation, you need to designate an existing user—or create a new user such as TUXADM or some other account—to be the Application Server Administrator. The Application Server Administrator, not the Windows Administrator, will install Oracle Tuxedo.

The designated user must be a local Microsoft Windows administrator and must have full system privileges. The

Oracle Tuxedo installation program creates a new service for Microsoft Windows—called ORACLE ProcMGR

V12.1.3.0.0_VS2012—for which you need administrator privileges. This service was developed to port Oracle

Tuxedo from UNIX to Microsoft Windows. Administrator rights are required since system registry settings are updated. Once this new service is created, you must reboot to start it.

When you configure your application server domain in a read-only PS_HOME environment, the user ID designated to be the Application Server Administrator must have read-only access to PS_HOME, read and write access to PS_CFG_HOME, and read-only access to the Oracle Tuxedo installation directory, TUXDIR, (for example, C:\oracle\tuxedo12.1.3.0.0_VS2012). Otherwise, in a scenario where <PS_CFG_HOME> =

<PS_HOME>, the Application Server Administrator must have read and write access to PS_HOME and readonly access to TUXDIR.

See "Configuring the Application Server on Windows."

See "Preparing for Installation," Defining Installation Locations.

To designate the Application Server Administrator:

1. Add the user ID by selecting Start, Administrative Tools, Computer Management, Local Users and Groups.

Keep in mind that you can also use an existing account if you do not care to create a new one. You can set this to the system account or an account that is a domain administrator (if there is a need to access files on the domain).

2. Expand Local Users and Groups.

3. If the user ID does not yet exist, highlight the Users folder, and select Action, New User.

4. On the New User dialog box, specify the information for the new account.

Make sure to deselect the User must change password at next logon check box.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

93

Installing Additional Components

5. Expand the Groups folder.

6. Right-click the Administrators group, and select All Tasks, Add to Group, Add.

7. Click Locations to select the local machine or the network domain in which you created the new user.

8. Enter the new user name you created in the object names box.

9. Click OK, and click Apply and OK again to accept the changes.

Chapter 3

Task 3-1-5: Installing Oracle Tuxedo on Microsoft Windows in GUI Mode

The following procedure assumes that you saved and extracted the installation files from Oracle Software

Delivery Cloud in the directory TUX_INSTALL. Installation in GUI mode is normally used for Microsoft

Windows operating systems.

Note. Oracle Tuxedo 12cR2_VS2012 can coexist on a machine with other versions of Oracle Tuxedo.

To install Oracle Tuxedo on Microsoft Windows:

1. Double-click TUX_INSTALL\Disk1\install\setup.exe to begin the installation process.

Click OK on the Welcome window, shown in this example:

94

Oracle Universal Installer: Welcome window for Oracle Tuxedo

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 3

Installing Additional Components

2. Accept the default option, Full Install, on the Select Installation Type window, as shown in this example, and click Next.

Select Installation Type window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

95

Installing Additional Components

Chapter 3

3. Specify a name and the home directory path for the installation.

You can enter a new name, or choose an existing name from the drop-down list. The name that you supply will be used to identify this Oracle Tuxedo installation in the Oracle Universal Installer, when reviewing the

Installed Products list. In this example, the name is tuxedo1213_VS2012.

Specify the full path for the home directory. You can choose an existing path from the drop-down list. The

Path refers to the location where the Oracle Tuxedo will be installed. The default is ORACLE_HOME\ tuxedo12.1.3.0.0_VS2012. In this example, the path is C:\oracle, which is the recommended location, so the software will be installed to C:\oracle\tuxedo12.1.3.0.0_VS2012. The installation directory is referred to in this documentation as TUXDIR.

Note. In previous Oracle Tuxedo and PeopleSoft PeopleTools releases, the installation directory was referred to as BEA_HOME, and the default was C:\bea. You may see installation directories from previous releases displayed here, and if so, you can select one.

96

Specify Home Details window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 3

Installing Additional Components

4. If you select an existing directory that is not empty, you may see a warning message.

The message recommends that you install to an empty directory unless the directory contains Operating

System generated files or subdirectories like lost+found. Click Yes to close the message and continue.

Warning message for a non-empty directory

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

97

Installing Additional Components

Chapter 3

5. If you have other versions of Oracle Tuxedo on your system, you may get a warning that earlier versions were detected, and with a recommendation that you exit and remove the earlier versions.

You can either quit and remove the earlier version, or install to a different directory if you want to maintain more than one version of the software. The message, shown in this example, directs you to the Tuxedo

12.1.3.0.0_VS2012 Installation Guide for instructions for using more than one version of the software. Click

Next to continue.

98

Earlier Version Detected window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 3

Installing Additional Components

6. Select No on the TSAM Plus agent enable choice window, as shown in this example, and then click Next.

This indicates that you do not want to enable Oracle Tuxedo System and Applications Monitor Plus (Oracle

TSAM Plus) agent.

TSAM Plus agent enable choice window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

99

Installing Additional Components

7. Select No on the SSL Installation Choice window, as shown in this example, and then click Next.

This indicates that you do not want to configure LDAP for SSL Support.

Chapter 3

SSL Installation Choice window

100

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 3

Installing Additional Components

8. Select No to indicate that you do not want to install Oracle Tuxedo Samples, as shown in this example, and then click Next.

Oracle Tuxedo Samples Installation Choice window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

101

Installing Additional Components

Chapter 3

9. Select No to indicate that you do not want to configure Oracle Tuxedo tlisten, as shown in this example, and then click Next.

If you want to configure tlisten, you must first apply patch RP037, and then configure tlisten manually after the installation is complete. See the Oracle Tuxedo documentation on performing post-installation tasks for information.

See Oracle Tuxedo Documentation on Oracle Technology Network, http://www.oracle.com/technetwork/middleware/tuxedo/documentation/index.html.

102

Oracle Tuxedo tlisten configuration Choice window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 3

Installing Additional Components

10. Review the summary information, and click Install to continue.

The summary information, shown in this example, includes the product name, install folder, installation type, and disk space information. If you want to change any of your choices, click Back.

Summary window

A progress indicator appears during the installation, as shown in this example.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

103

Installing Additional Components

Chapter 3

Install progress indicator window

104

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 3

Installing Additional Components

11. Click Exit when you see the window indicating the installation is complete, as shown in this example.

End of Installation window

Task 3-1-6: Installing the Oracle Tuxedo Patch on Microsoft Windows

These instructions assume that you have installed the base Oracle Tuxedo 12cR2_VS2012, and have downloaded the platform-specific version of the rolling patch to a directory referred to here as TUX_INSTALL.

To install the patch:

1. Stop all PeopleSoft PeopleTools domains that are running and using your Oracle Tuxedo installation.

2. Verify that the environment variable TUXDIR is set to the Oracle Tuxedo installation location, such as

C:\oracle\tuxedo12.1.3.0.0_VS2012.

3. Verify that the environment variable ORACLE_HOME is set to the ORACLE_HOME location you specified when you installed Oracle Tuxedo, such as C:\oracle.

4. Run the following command to verify the opatch version:

%ORACLE_HOME%\OPatch\opatch.bat version

The version should be 12.1.0.1.1 or later. If the version is lower, you must first update opatch by installing patch 19166960.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

105

Installing Additional Components

Chapter 3

5. Launch the Services window; for example, select Start, Administrative Tools, Services.

6. Select each of the following services, right-click, and select Stop:

• ORACLE ProcMGR V12.1.3.0.0_VS2012

• TListen 12.1.3.0.0_VS2012 (Port: 3050)

Note. The port number is variable.

7. Uninstall any existing patches.

8. Go to the directory where you downloaded the patch zip file from My Oracle Support, TUX_INSTALL, and unzip the file.

This creates a directory 21618163, which includes a zip file with the patch.

9. Set the environment variable for the platform ID; for example: set OPATCH_PLATFORM_ID=233

10. Open a command prompt and go to the TUX_INSTALL/21618163 directory.

11. Run the following command:

%ORACLE_HOME%\OPatch\opatch.bat apply 21618163.zip

Note. The patch installer backs up all files being patched. The backup copy is located in the directory

ORACLE_HOME\.patch_storage\. Do not delete these backup files. They will be used if you need to remove the patch installation.

Task 3-1-7: Installing Oracle Tuxedo on Microsoft Windows in Silent Mode

This section discusses:

• Understanding Silent Installation on Microsoft Windows

• Running the Silent Mode Installation on Microsoft Windows

Understanding Silent Installation on Microsoft Windows

You can carry out a silent installation of Oracle Tuxedo 12cR2_VS2012 by providing all the required settings in a response file. With silent installation there is little or no user interaction.

See Oracle Tuxedo documentation.

Use a text editor to create the response file and specify the values according to your installation requirements.

Here is a sample response file:

#

# .......... Silent Installation Properties file .........

#

RESPONSEFILE_VERSION=2.2.1.0.0

ORACLE_HOME="C:\oracle"

ORACLE_HOME_NAME="tuxedo1213_VS2012"

106

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 3

Installing Additional Components

INSTALL_TYPE="Full Install"

ENABLE_TSAM_AGENT=false

LDAP_SUPPORT_SSL=false

INSTALL_SAMPLES=false

ENCRYPT_CHOICE=0

CONFIG_TLISTEN=false

Most of the entries are similar to those seen in the GUI installation. Note the following definitions:

• ORACLE_HOME: The high level installation directory, for example C:\oracle.

The installer creates the Oracle Tuxedo installation directory, TUXDIR, as

ORACLE_HOME\tuxedo12.1.3.0.0_VS2012.

• ORACLE_HOME_NAME: The name of the current Oracle installation, for example tuxedo1213_VS2012.

This identifies the Oracle Tuxedo installation in the Oracle Universal Installer, when reviewing the Installed

Products list.

Running the Silent Mode Installation on Microsoft Windows

The following procedure assumes that you saved and extracted the installation file from Oracle Software Delivery

Cloud in the directory TUX_INSTALL.

See Obtaining the Oracle Tuxedo Installation Files from Oracle Software Delivery Cloud.

To run the installer:

1. Create a response file as described in the previous section and copy it to TUX_INSTALL.

2. Open a command prompt and change directory to TUX_INSTALL\Disk1\install.

3. Run the installer.

• If you specify an empty directory for ORACLE_HOME, use this command: setup.exe -silent -responseFile response_file

Specify the full path to the response file. For example, if the response file name is response.rsp, and

TUX_INSTALL is D:\Temp, use this command: setup.exe -silent -responseFile D:\Temp\response.rsp

• If you specify an existing directory that is not empty for ORACLE_HOME, you must include the – force option.

When you use the

– force

option with a non-empty ORACLE_HOME, you may see a warning message recommending that you install to an empty directory or one that includes Operating System generated files. You may close the message to continue the installation. setup.exe -silent -responseFile D:\Temp\response.rsp -force

Note. If you do not include the

– force

option with an ORACLE_HOME directory that is not empty, the installer will abort.

4. After you enter the commands in the previous steps, the installer is launched in silent mode, and a progress

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

107

Installing Additional Components

Chapter 3 indicator tracks the installation.

When the installation is complete, you should see a completion message such as "The installation of Oracle

Tuxedo was successful."

Task 3-1-8: Uninstalling the Oracle Tuxedo Patch on Microsoft Windows

To remove an Oracle Tuxedo installation, you must first remove the rolling patch, as follows:

1. Stop all PeopleSoft PeopleTools domains that are running and using your Oracle Tuxedo installation.

2. Verify that the environment variable TUXDIR is set to the Oracle Tuxedo installation location, such as

C:\oracle\tuxedo12.1.3.0.0_VS2012.

3. Verify that the environment variable ORACLE_HOME is set to the ORACLE_HOME location you specified when you installed Oracle Tuxedo, such as C:\oracle.

4. Open a command prompt and run the following command:

%ORACLE_HOME%\OPatch\opatch.bat rollback -id 21618163

Task 3-1-9: Uninstalling Oracle Tuxedo in GUI Mode

To remove the Oracle Tuxedo 12cR2_VS2012 or 12cR2 installation, use Oracle Universal Installer (OUI).

1. Start Oracle Universal Installer (OUI).

The way you start OUI depends upon the Oracle products you have installed. For example:

• On Microsoft Windows 7, select Start, Programs, Oracle 12c, Oracle Installation Products, Universal

Installer.

• On Microsoft Windows 8 or 2012 R2, access the Apps screen. Navigate to Oracle 12c, Oracle Installation

Products, Universal Installer.

• Double-click TUX_INSTALL\Disk1\install\setup.exe.

108

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 3

2. Click Deinstall Products, as shown in this example:

Installing Additional Components

Oracle Universal Installer: Welcome window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

109

Installing Additional Components

Chapter 3

3. On the Contents page, select the name for the Oracle Tuxedo installation, which is tuxedo1213_VS2012 in this example, and then click Remove.

Inventory window: Contents page

4. Open the Microsoft Windows registry, for example by selecting Start, Run, regedit.

Verify that the following key has been removed from the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\TUXEDO\12.1.3.0.0_VS2012

See Oracle Tuxedo, Installing the Oracle Tuxedo System 12c Release 2 (12.1.3), Oracle Technology Network.

Task 3-1-10: Checking the Windows Service Account

Use the information in this section to ensure that the Microsoft Windows services are properly configured. Oracle recommends installing the application server binaries locally on your C drive, for best performance. The procedure to set up the ORACLE ProcMGR V12.1.3.0.0_VS2012 service in the next section includes options for the account type. Use the following guidelines to choose between the Local System account option and the This

Account option. (For the option This Account, you must specify a user ID and password.)

Note. For the sake of brevity and convenience, this documentation sometimes shortens "ORACLE ProcMGR

V12.1.3.0.0_VS2012" to "Oracle ProcMGR."

110

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 3

Installing Additional Components

• If you plan to install the PeopleSoft application server binaries (as in, psappsrv.exe and so on) on a remote file server, you must select the This Account option.

• If the PeopleSoft application server binaries are local, that is, they exist on your local hard drive, you can use either the Local System account or This Account option.

• If you intend to use this Microsoft Windows service to start Process Scheduler, you must always select the

This Account option. Enter the name of your Domain/Windows user name

—not the machine name—and your password.

• If you are running on Microsoft Windows and are configuring a search index that resides on a mapped network drive, you must ensure that the user ID of the Oracle ProcMGR service has access to network drives accessed by the search engine. The search engine stores the search indexes at PS_HOME/data/search.

However, this path can be changed in the application or the Process Scheduler's configuration. If this path is changed in these configurations and it points to a network drive, you must ensure that the user ID that starts the Oracle ProcMGR service has access to these network drives. The application server and the Process

Scheduler are started by the Oracle ProcMGR service and therefore inherit the same permissions as the Oracle

ProcMGR service.

See Also

"Setting Up Process Scheduler on Windows," Setting Up Process Scheduler Security

Task 3-1-11: Restricting Domain Process Privileges

This section discusses:

• Understanding Domain Process Privileges

• Setting TM_CPAU Environment Variable

Understanding Domain Process Privileges

For PeopleSoft systems, the Oracle ProcMGR service (tuxipc.exe) is responsible for starting Oracle Tuxedo domain processes on Microsoft Windows. By default, domain processes run as the same user ID that the service is running as. In a default installation, the service is configured to log on to Microsoft Windows as the Local System user. Microsoft does not support assigning network privileges to the Local System user for security reasons, but the Local System user otherwise has full administrative access to the local system.

In this configuration, PeopleSoft PeopleTools domain processes also run as the Local System user, which presents several potential issues, including:

• PeopleSoft PeopleTools domain processes are unable to access network resources.

• PeopleSoft PeopleTools domain processes run with more privileges than are necessary. A compromised

PeopleSoft PeopleTools process will have full access to the local system and could potentially be used to gain unauthorized access to the local system.

• All PeopleSoft PeopleTools domain processes on the system run as the same user ID.

These problems are not present on UNIX systems where domain processes are always started as the user that runs tmadmin (by way of PSADMIN for PeopleSoft installations) to boot the domain. UNIX systems therefore support multiple domains, each running under different user IDs, with only the desired local privileges, and with no undesirable restrictions to network resources.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

111

Installing Additional Components

Chapter 3

For Microsoft Windows platforms, you can use the Oracle Tuxedo TM_CPAU environment variable to achieve behavior similar to UNIX systems. If TM_CPAU is set to YES before tuxipc is started, tuxipc creates an Oracle

Tuxedo process that belongs to the user who initiated tmboot. If the Oracle ProcMGR service (tuxipc.exe) is started with the TM_CPAU=YES environment variable set, then domain processes will run as the user ID used to run tmadmin (PSADMIN) to boot the domain.

Using the TM_CPAU environment variable enables a variety of configuration options, including:

• The Oracle ProcMGR service can be run as the Local System user, but domain processes can be run using a minimally privileged user. This reduces the chance of a compromised PeopleSoft PeopleTools process being used to gain unauthorized access to the system. Note that the option "Allow services to interact with Desktop" should not be selected.

• The Oracle ProcMGR service can be configured to log on to Microsoft Windows using a minimally privileged user ID and PeopleSoft PeopleTools processes can run as a user with more privileges than the Oracle Tuxedo user ID. For example, the Oracle Tuxedo user ID could have read-only access to PS_CFG_HOME, but the

PeopleSoft PeopleTools user could have read-write access. The Oracle Tuxedo user ID does not actually require read access to PS_HOME. When CreateProcessAsUser runs, access to the executable to start is evaluated using the user ID that the process will run as.

• A single Microsoft Windows system can be used to host multiple PeopleSoft PeopleTools installations that are each administered by a different user. A non-administrative user ID used to boot one domain will have no privileges to processes started with a different user ID.

• Domain processes can be identified and managed in Windows Task Manager by a non-administrative user.

See File Formats, Data Descriptions, MIBs, and System Processes Reference, Oracle Tuxedo Reference Topics, http://docs.oracle.com/cd/E35855_01/tuxedo/docs12c/rf5/rf5.html.

Setting TM_CPAU Environment Variable

This is a recommended step. Perform this step only if Local System account is used in the task Setting Up the

Windows Services for Oracle Tuxedo.

To set the TM_CPAU environment variable:

1. Select Start, Control Panel, System on Microsoft Windows 7.

Click the Start button, then Control Panel, System and Security, System, on Microsoft Windows 8 or 2012 R2.

2. Select Advanced system settings.

3. Select the Advanced tab.

4. Click Environment Variables.

5. In the System variables area, click New to add a new environment variable.

6. Enter TM_CPAU as the variable name, YES as the value, and click OK three times to close the dialog boxes.

7. Restart your machine.

Task 3-1-12: Setting Up the Windows Services for Oracle Tuxedo

To set up the Microsoft Windows services for Oracle Tuxedo:

1. Log on again as the Application Server Administrator, TUXADM, or a designated user ID.

2. Open the Control Panel and double-click Administrative Tools.

3. Select Computer Management and expand Services and Applications.

4. Select Services and locate the service labeled ORACLE ProcMGR V12.1.3.0.0_VS2012.

112

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 3

Installing Additional Components

Double-click ORACLE ProcMGR V12.1.3.0.0_VS2012 to open the properties dialog box.

5. On the General tab, if the Stop button is enabled, click it to stop the current ORACLE ProcMGR

V12.1.3.0.0_VS2012 process.

6. Select Log On.

7. Choose either Local System account or This account.

If you select This account, as shown in this example, be sure to specify a user with the appropriate permissions, and then enter and confirm the password.

See Checking the Windows Service Account.

ORACLE ProcMGR V12.1.3.0.0_VS2012 Properties dialog box: Log On tab

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

113

Installing Additional Components

8. Select General.

Make sure that Startup Type is set to Automatic, as shown in this example.

Chapter 3

ORACLE ProcMGR V12.1.3.0.0_VS2012 Properties dialog box: General tab

9. Click Start.

The status Started appears both on the General tab of the Oracle ProcMGR V12.1.3.0.0_VS2012 Properties dialog box and in the Services dialog box. Click OK to close the dialog box.

10. As mentioned, unless you intend to use the Tuxedo Web Monitor, you should disable the TListen

12.1.3.0.0_VS2012 (Port: PORT) service, where PORT is the port number you entered during the installation.

The default is 3050.

Task 3-1-13: Verifying the Server Installation on Microsoft Windows

At this point, you should verify that the server installation was successful.

To verify the installation:

1. Open a command prompt.

2. Set the TUXDIR environment variable; for example: set TUXDIR=C:\oracle\tuxedo12.1.3.0.0_VS2012

3. Go to the directory where you installed Oracle Tuxedo, TUXDIR, and then to the bin sub-directory. For example:

114

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 3

Installing Additional Components

C:\oracle\tuxedo12.1.3.0.0_VS2012\bin

4. Issue this command: tmadmin -v

The command will return the Oracle Tuxedo version that is installed. For example:

INFO: Oracle Tuxedo, Version 12.1.3.0.0_VS2012, 64-bit, Patch Level⇒

(None)

If you do not see the desired output, review your steps and reinstall Oracle Tuxedo 12cR2_VS2012.

5. Open the Microsoft Windows registry, for example by selecting Start, Run, regedit.

Verify that the following key is created in the Windows registry:

HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\TUXEDO\12.1.3.0.0_VS2012

Task 3-1-14: Removing Existing Oracle Tuxedo Installations from UNIX

(Optional)

You may have older versions of Oracle Tuxedo installed on your system from an earlier version of PeopleSoft

PeopleTools. If you are completely upgrading to PeopleSoft PeopleTools 8.55 from an earlier version of

PeopleSoft PeopleTools and you do not require the older Oracle Tuxedo anymore, then, you may uninstall it.

Note. It is not mandatory to uninstall older Oracle Tuxedo versions from the machine where you are installing

Oracle Tuxedo 12cR2, as older Oracle Tuxedo versions and Oracle Tuxedo 12cR2 can exist on the same machine.

You may have to remove your Oracle Tuxedo installation on UNIX for the following reasons:

• You are having problems starting Oracle Tuxedo and decide to reinstall.

• You no longer need Oracle Tuxedo on a machine.

To remove Oracle Tuxedo from UNIX:

1. Using PSADMIN, shut down any application server, Process Scheduler, and Search server domains that may be running on the machine.

2. Use the UNIX rm

command to directly remove the Oracle Tuxedo installation.

Be sure to remove the directory containing Oracle Tuxedo, referred to here as TUXDIR.

3. Remove the TUXDIR environment variable and any entries containing your platform-specific LIBRARY

PATH and PATH environment variables.

Task 3-1-15: Completing the Preinstallation Checklist on UNIX

We recommend that you complete the following preinstallation checklist before you begin the Oracle Tuxedo installation. The checklist includes various parameters with descriptions and example values. Specify your values in the Real Value column. Completing this information first should save you time during your installation.

Item

ORACLE_HOME

Description Example Value

The high level installation directory. You specify this value in the silent installation file.

/oracle

Real Value

<enter value>

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

115

Installing Additional Components

Chapter 3

Item Description Example Value

ORACLE_HOME_NAME The name of the current

Oracle installation. This identifies the Oracle Tuxedo installation in the Oracle

Universal Installer, when reviewing the Installed

Products list.

tuxedo1213

TUXDIR The full path to the Oracle

Tuxedo installation. The installer creates this as

ORACLE_HOME/tuxedo12.

1.3.0.0

/oracle/tuxedo12.1.3.0.0

Username

UNIX_GROUP_NAME

FROM_LOCATION

Real Value

<enter value>

<enter value>

The UNIX user name of the

Application Server

Administrator (Oracle

Tuxedo owner). See the next section for instructions.

tuxedo <enter value>

The UNIX group name of the

Oracle Tuxedo owner. See the next section for instructions.

tuxedo

The full path to the directory containing the products to be installed.

/home/temp/Disk1/stage/prod ucts.xml

<enter value>

Note. You can select any user name and group name you want; however, you might want to use the "tuxedo" convention for simplicity.

Task 3-1-16: Designating the Oracle Tuxedo Owner on UNIX

A new or existing user must be designated as the Oracle Tuxedo owner.

Note. For Oracle Tuxedo 11gR1 and later releases, the application server can be booted only by the Oracle

Tuxedo owner or the group that the owner is in. The predefined UNIX "other" group does not have read or execute permission. If it is required that members of the "other" group be able to boot and shut down an application server domain, you must manually give read and execute permissions to all files and folders under the

TUXDIR/locale and TUXDIR/udataobj directories.

To designate the Oracle Tuxedo owner:

1. Log in as root.

2. Create the UNIX group and the user name of the individual who will be the owner of Oracle Tuxedo.

Using the values from the preinstallation checklist, create the group and specify the group name. Then create the user who will be the Oracle Tuxedo owner, specifying the user name, group name, and home directory, denoted by TUXDIR from the checklist.

116

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 3

Installing Additional Components

Note. The utility that you use to create the user and group varies, depending on your operating system. For example, HP-UX Itanium uses the "sam" utility, IBM AIX uses the "smit" utility, and so on. For the exact utility, refer to your operating system documentation.

Task 3-1-17: Installing Oracle Tuxedo in Silent Mode on UNIX

This section discusses:

• Understanding the Silent Mode Installation on UNIX

• Running the Silent Mode Installation on UNIX

Understanding the Silent Mode Installation on UNIX

You can carry out a silent installation of Oracle Tuxedo 12cR2 by providing all the required settings in a response file. With silent installation there is little or no user interaction.

See Oracle Tuxedo documentation.

Note. Console mode installation is not supported for Oracle Tuxedo 12cR2.

Use a text editor to modify the values in the response file according to your installation requirements. Here is a sample response file:

#

# .......... Silent Installation Properties file .........

#

RESPONSEFILE_VERSION=2.2.1.0.0

#Unix group to be set for the inventory directory. Valid only in Unix⇒

 platforms.

UNIX_GROUP_NAME="dba"

#Complete path of the Oracle Home.

ORACLE_HOME="/home/psftuser/oracle"

#Oracle Home Name. Used in creating folders and services.

ORACLE_HOME_NAME="tuxedo1213"

DEINSTALL_LIST={"Tuxedo","12.1.3.0.0"}

SELECTED_LANGUAGES={"en"}

COMPONENT_LANGUAGES={"en"}

INSTALL_TYPE="Full Install"

ENABLE_TSAM_AGENT=false

LDAP_SUPPORT_SSL=false

TLISTEN_PORT="3050"

MIN_CRYPT_BITS_CHOOSE=0

MAX_CRYPT_BITS_CHOOSE=256

INSTALL_SAMPLES=true

ENCRYPT_CHOICE=0

CONFIG_TLISTEN=true

TLISTEN_PASSWORD=password

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

117

Installing Additional Components

Chapter 3

Running the Silent Mode Installation on UNIX

The following procedure assumes that you saved and extracted the installation files from Oracle Software

Delivery Cloud in the directory TUX_INSTALL.

To install Oracle Tuxedo on UNIX or Linux:

1. If it does not exist, use a text editor, such as "vi", to create the central inventory location file, named oraInst.loc, in a convenient directory.

If you have previously installed Oracle software on the system, the oraInst.loc file may already exist. The oraInst.loc file contains only the following two lines: inventory_loc=/home/psftuser/oraInventory inst_group=ccpt

The oraInst.loc file contains the following information:

• inventory_loc — Specify the full path to the directory where you want the installer to create the inventory directory. The location in the example is /home/psftuser/oraInventory.

• oui_install_group — Specify the name of the group whose members have write permissions to this directory. The group name in the example is ccpt.

2. Create a response file as described in the previous section and copy it to TUX_INSTALL.

3. Open a command prompt and change directory to TUX_INSTALL/Disk1/install.

4. If this is the first time you are installing on your system (that is, there is no pre-existing Oracle inventory location, and you had to create the oraInst.loc file in the first step), use the following command to perform a silent installation:

./runInstaller -responseFile <complete_filename> -silent -invPtrLoc ⇒

<complete_inventory_filename>

Specify the full path and name for both the response file and the oraInst.loc file. For example:

./runInstaller -responseFile /home/temp/response.rsp -silent -invPtrLoc⇒

 /home/psftuser/oraInventory/oraInst.loc

5. If you have previously installed an Oracle product on your system and do not need to specify an Oracle inventory location, use the following command to perform a silent installation:

./runInstaller -responseFile <complete_filename> -silent

Specify the full path and name for both the response file. For example:

./runInstaller -responseFile /home/temp/response.rsp -silent

6. After you enter the commands in the previous steps, the installer is launched in silent mode, and a progress indicator tracks the installation.

When the installation is complete, you should see a completion message such as "The installation of Oracle

Tuxedo was successful."

Task 3-1-18: Installing the Oracle Tuxedo Patch on UNIX

These instructions assume that you have installed the base Oracle Tuxedo 12cR2, and have downloaded the platform-specific version of the rolling patch to a directory referred to here as TUX_INSTALL.

To install the patch:

118

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 3

Installing Additional Components

1. Stop all PeopleSoft PeopleTools domains that are running and using your Oracle Tuxedo installation.

2. Verify that the environment variable TUXDIR is set to the Oracle Tuxedo installation location, such as

/home/psftuser/oracle/tuxedo12.1.3.0.0.

3. Verify that the environment variable ORACLE_HOME is set to the ORACLE_HOME location you specified when you installed Oracle Tuxedo, such as /home/psftuser/oracle.

4. Go to the directory where you downloaded the patch zip file from My Oracle Support, TUX_INSTALL, and unzip the file.

This creates a directory 21618163, which includes a zip file with the patch.

5. Open a command prompt and go to the TUX_INSTALL/21618163 directory.

6. Run the following command:

$ORACLE_HOME/OPatch/opatch apply 21618163.zip

Note. The patch installer backs up all files being patched. The backup copy is located in the directory

ORACLE_HOME\.patch_storage\. Do not delete these backup files. They will be used if you need to remove the patch installation.

Task 3-1-19: Uninstalling the Oracle Tuxedo Patch from UNIX

To remove an Oracle Tuxedo installation, you must first remove the rolling patch, as follows:

1. Stop all PeopleSoft PeopleTools domains that are running and using your Oracle Tuxedo installation.

2. Verify that the environment variable TUXDIR is set to the Oracle Tuxedo installation location, such as

/home/psftuser/oracle/tuxedo12.1.3.0.0.

3. Verify that the environment variable ORACLE_HOME is set to the ORACLE_HOME location you specified when you installed Oracle Tuxedo, such as /home/psftuser/oracle.

4. Open a command prompt and run the following command:

$ORACLE_HOME/OPatch/opatch rollback -id 21618163

Task 3-1-20: Uninstalling Oracle Tuxedo from UNIX Using Silent Mode

To remove the Oracle Tuxedo 12cR2 installation from UNIX:

1. Open a command prompt and change directory to TUX_INSTALL/Disk1/install.

2. Run the following command, where ORACLE_HOME refers to the high-level installation director, and

REMOVE_HOMES refers to the directory to be removed:

./runInstaller -deinstall -silent ORACLE_HOME=<LOCATION_OF_ORACLE_HOME>

 "REMOVE_HOMES={<LOCATION_OF_ORACLE_HOME_TO_BE_REMOVED>}"

For example:

./runInstaller -deinstall -silent ORACLE_HOME="/home/psftuser/oracle"⇒

 "REMOVE_HOMES={/home/psftuser/oracle}"

See Oracle Tuxedo documentation.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

119

Installing Additional Components

Chapter 3

Task 3-1-21: Verifying the Server Installation on UNIX

At this point, you should verify that the server installation was successful.

To verify the installation:

1. Open a shell.

2. Change directory to TUXDIR/bin. For example:

/home/psftuser/oracle/tuxedo1213/bin

3. Issue the following command: tmadmin -v

The command will return the Oracle Tuxedo version that is installed. For example:

INFO: Oracle Tuxedo, Version 12.1.3.0.0, 64-bit, Patch Level(None)

If you do not see the desired output, review your steps and reinstall Oracle Tuxedo 12cR2.

Task 3-1-22: Ensuring that Oracle Tuxedo Coexists with Earlier Versions

This section discusses:

• Understanding the Use of Multiple Oracle Tuxedo Versions

• Checking Your Environment Variables

• Changing the TListen Port

Understanding the Use of Multiple Oracle Tuxedo Versions

Earlier versions of PeopleSoft PeopleTools rely on earlier versions of Oracle Tuxedo—for example, PeopleSoft

PeopleTools 8.49 uses Oracle Tuxedo 9.1, and releases 8.44 to 8.48 use Oracle Tuxedo 8.1. If you are installing only PeopleSoft PeopleTools 8.55, you can safely skip this section. If you need to run application servers on

PeopleSoft PeopleTools 8.55 and earlier PeopleSoft PeopleTools versions on the same machine, read this section to learn about coexistence issues. Although Oracle Tuxedo 12cR2 coexists with earlier Oracle Tuxedo versions on the same machine, you may need to take a number of manual steps to ensure that these products share the same environment gracefully.

Checking Your Environment Variables

Installing Oracle Tuxedo changes your TUXDIR and PATH environment variables. Although you do not need to change these environment variables to successfully run PeopleSoft PeopleTools 8.55 with Oracle Tuxedo 12cR2, earlier versions of PeopleSoft PeopleTools rely on these environment variables being set.

To change your environment variables manually:

1. Set your TUXDIR environment variable to reflect the installation directory of your earlier Oracle Tuxedo release.

For example, Oracle Tuxedo 8.1 may be installed to C:\tux8.1. This means that TUXDIR=C:\tux8.1 is the correct setting.

2. Your PATH environment variable must contain TUXDIR\bin for the earlier Oracle Tuxedo version before any entries for TUXDIR\bin for Oracle Tuxedo 12cR2.

120

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 3

Installing Additional Components

For example the setting PATH=C:\winnt;C:\oracle\tuxedo12.1.3.0.0_VS2012\bin;C:\tux8.1\bin will cause your pre-8.49 domains to no longer work. You would need to change this to

PATH=C:\winnt;C:\tux8.1\bin;C:\oracle\tuxedo12.1.3.0.0_VS2012\bin to work with pre-PeopleSoft

PeopleTools 8.49 domains.

Note. PeopleSoft PeopleTools 8.44 and later do not use environment variables to discover the installation location of Oracle Tuxedo 8.1 and later. The PSADMIN tool retrieves these values from the Microsoft

Windows registry.

3. Your library path on UNIX (whichever of the environment variables LD_LIBRARY_PATH, LIBPATH, or

SHLIB_PATH is appropriate for your platform) must contain TUXDIR/lib for the earlier Oracle Tuxedo version before any entries for Oracle Tuxedo 12cR2.

For example the setting

LD_LIBRARY_PATH=/lib:/usr/lib:/home/user/Oracle/tuxedo12cR2/lib:/prod/tuxedo/8.1/lib, will cause your pre-8.49 domains to no longer work. You would need to change this to

LD_LIBRARY_PATH=/lib:/usr/lib:/prod/tuxedo/8.1/lib:/home/user/Oracle/tuxedo12cR2/lib for your pre-

8.49 domains to work.

Alternatively, you can set the environment variables for a desired release using these steps:

1. Go to the TUXDIR directory for the release that you want to run and run the command ./tux.env

.

This command sets the environment variables needed to run Oracle Tuxedo.

2. Verify the correct Oracle Tuxedo version by running this command: tmadmin -v

See Verifying the Server Installation on UNIX.

Changing the TListen Port

Installing Oracle Tuxedo 12cR2 and earlier creates a new service known as TListen. In most cases, you can disable this service as it is not required to run PeopleSoft PeopleTools application server domains. However, if you intend to use the Tuxedo Web Monitor you may wish to ensure that there is no port clash with earlier versions. This port is determined at installation and should be changed to a port other than the default 3050 if you intend on using the TListen service for Oracle Tuxedo 12cR2 and earlier Oracle Tuxedo versions concurrently.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

121

Chapter 4

Using the PeopleSoft Installer

This chapter discusses:

• Understanding the PeopleSoft Installer

• Prerequisites

• Obtaining the PeopleSoft Installation Files from Oracle Software Delivery Cloud

• Running the PeopleSoft Installer

• Verifying Necessary Files for Installation on Windows

• Installing PeopleSoft Application Software

• Installing the Multilanguage Files

• Installing the PeopleTools Client Files

• Mapping a Drive on the Install Workstation

Understanding the PeopleSoft Installer

This section discusses:

• Defining the PeopleSoft Installer

• Defining Supported Server Combinations

• Obtaining License Codes

Defining the PeopleSoft Installer

The PeopleSoft Installer is a Java-based tool that delivers software to your servers and to the PeopleTools Client.

You can install the whole range of PeopleSoft servers and client with the PeopleSoft installer. You can install the server and client software separately or together.

Note. You must install the necessary web server products and any additional component software as described in the previous chapters before you run the PeopleSoft Installer.

The PeopleSoft Installer enables you to transfer files directly to various PeopleSoft servers—including application servers, batch servers, web servers, and database servers—without first copying all files to a file server. You can also use the PeopleSoft Installer to install the files for the PeopleTools Client.

123

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Using the PeopleSoft Installer

Chapter 4

You run the PeopleSoft installer to install the necessary products on the target machines. Which files are installed depends on the operating system on the target machine, the database platform, and the selected server option. The

PeopleSoft Installer installs files directly to Microsoft Windows, UNIX, and Linux machines. PeopleSoft

PeopleTools and PeopleSoft applications use the same PeopleSoft installation template. This chapter discusses the installation of PeopleSoft PeopleTools, followed by the installation of PeopleSoft application software and the application-specific Multilanguage files.

All licensed components of the PeopleSoft Architecture must be installed on each server. If you are not able to download and extract the PeopleSoft installation files directly on a UNIX machine, for example, you can download to the Windows file server and then FTP the files to your UNIX system.

You can install multiple logical servers to the same machine. For example, you can have the application server and the batch server on the same machine. But, if you want to install different servers to different machines, you have to run the PeopleSoft Installer once for each server.

Before beginning the installation, be sure to review the information about the various PeopleSoft servers and clients in the chapter "Preparing for Installation."

See Also

"Preparing for Installation," Planning Your Initial Configuration

Defining Supported Server Combinations

The following table lists the supported operating systems for the various PeopleSoft servers for your database platform. For more detailed information, consult the PeopleSoft product certifications area of My Oracle Support.

Supported operating systems for database servers

HP-UX Itanium

IBM AIX on POWER

Systems (64-bit)

IBM: Linux on System z

Linux x86-64

Microsoft Windows x64

(64-bit)

Oracle Solaris on

SPARC (64-bit)

Oracle Solaris x86_64

Supported operating systems for application servers and batch servers

Supported operating systems for file servers

Supported operating systems for web servers

HP-UX Itanium

IBM AIX on POWER

Systems (64-bit)

IBM: Linux on System z

(batch server only; no application server)

Linux x86-64

Microsoft Windows x64

(64-bit)

Oracle Solaris on

SPARC (64-bit)

Oracle Solaris x86_64

Microsoft Windows x64 (64bit)

Linux or UNIX with network file system (NFS) or equivalent support

HP-UX Itanium (64-bit)

IBM AIX on POWER

Systems (64-bit)

Linux x86-64

Microsoft Windows x64

(64-bit)

Oracle Solaris on

SPARC (64-bit)

Oracle Solaris x86_64

See Also

My Oracle Support, Certifications

124

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 4

Using the PeopleSoft Installer

Obtaining License Codes

Refer to the following URL for license codes for Oracle's PeopleSoft line of products: http://licensecodes.oracle.com/ent_keys_by_prod.html.

See Also

My Oracle Support, (search for Licensing Notes for the current release)

"Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode," Completing Post-Installation Steps

"Setting Up the PeopleSoft Pure Internet Architecture in Console Mode," Completing Post-Installation Steps

Prerequisites

Verify that you fulfill the following requirements before beginning the installation:

• The PeopleSoft Installer requires Java Virtual Machine (JVM), which is bundled for all OS platforms. The

PeopleSoft Installer directly uses the bundled JVM, and therefore does not need to search for the JVMs in the directories in which users would typically install JVM. PeopleSoft PeopleTools supports JRE/JDK 1.7 and higher patch level. See My Oracle Support for information on the correct JRE version for your system.

See My Oracle Support, Certifications.

• Before running the PeopleSoft installer, you must verify that you have the correct patches for your JVM level.

Check My Oracle Support and your vendor for required patches.

See Operating System, RDBMS, & Additional Component Patches Required for Installation PeopleTools, My

Oracle Support, (search for the article title).

• Make sure you have at least 4.5 GB of free space to perform your installation.

See Running the PeopleSoft Installer.

• The installation process also requires at least 2.0 GB of free temporary disk space, which is needed only for the duration of the process. The process uses the directory defined by the TEMP environment variable on your installation computer or the directory specified by the -tempdir option when using setup.sh to install.

Oracle strongly recommends that you use the

–tempdir option to install, using the following guidelines:

• Do not use /tmp as the temporary directory.

• Do not specify /tmp as the explicit temporary directory for the -tempdir option.

• Do not specify a directory that is on a shared drive.

• Do not specify a directory that is inside the location where PeopleSoft PeopleTools is being installed; for example, PS_HOME/temp.

• The user who installs PeopleSoft PeopleTools must be root or the owner of PS_HOME.

PS_HOME is used throughout this installation guide to refer to the high-level directory where your PeopleSoft

PeopleTools software is installed. The documentation may also use the notation $PS_HOME or

%PS_HOME% to refer to the PS_HOME environment variable in a code sample.

• You can install the PeopleSoft Application software to PS_HOME, or to another directory outside PS_HOME.

This documentation refers to the directory where you install the PeopleSoft application software as

PS_APP_HOME.

See "Preparing for Installation," Defining Installation Locations.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

125

Using the PeopleSoft Installer

Chapter 4

• You must have admin privileges to install the PeopleSoft web server.

• You can install the PeopleSoft web server to PS_HOME, or to another directory outside PS_HOME. This documentation refers to the directory where you install the PeopleSoft web server as PIA_HOME.

See "Preparing for Installation," Defining Installation Locations.

• If your installation requires any PeopleSoft PeopleTools patches, you can apply the code (that is, the contents of the zip file you downloaded from My Oracle Support) after running the PeopleSoft Installer. Do not apply the database instructions at this time; the database objects will be applied later during the install. Be sure to read and follow the instructions provided with the PeopleSoft PeopleTools patches.

See Also

My Oracle Support, Certifications

Task 4-1: Obtaining the PeopleSoft Installation Files from Oracle

Software Delivery Cloud

You obtain the PeopleSoft PeopleTools, PeopleSoft application, and multi-language software by downloading them as zip files from Oracle Software Delivery Cloud. At this point you should have already downloaded the necessary files. However, if you have not yet downloaded the files, this section includes information on finding and using the installation files.

See "Preparing for Installation," Using Oracle Software Delivery Cloud to Obtain Installation Files.

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

To obtain the installation files for PeopleSoft PeopleTools and PeopleSoft applications from Oracle Software

Delivery Cloud:

1. After logging in to Oracle Software Delivery Cloud read the information about export restrictions, and then click Accept.

2. Enter the name of a specific PeopleSoft application product in the type-ahead Product field.

For example, for PeopleSoft Human Capital Management, enter and select PeopleSoft Enterprise Human

Resources. For PeopleSoft Financials and Supply Chain Management, enter and select PeopleSoft Enterprise

Financials.

Note. The installation files for PeopleSoft PeopleTools are included with the PeopleSoft application installation files. If you want to obtain the files for PeopleSoft PeopleTools only, enter PeopleSoft Enterprise

PeopleTools in the Product field, and select PeopleSoft Enterprise PeopleTools - Enterprise Development from the drop-down list.

3. Click Select Platform, select the operating system you are running on, and then click Select.

Note that you must unzip the zip files on the operating system platform for which they are intended. For example, if you download the files for Oracle Solaris, you must unzip the files on an Oracle Solaris operating system. If you unzip the files on a Microsoft Windows machine into a staging directory, and then move the directory to an Oracle Solaris machine, the staging area files may be corrupted.

4. In the Selected Products section, click the Quick Select link below your PeopleSoft application.

5. In the Quick Select window, select the check boxes for all the products you want to download, and then click

Select.

The products are added to the Selected Products list.

126

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 4

Using the PeopleSoft Installer

6. Click Continue.

7. Click the arrow to view and select from the list of products included.

8. Click Continue.

9. Read the license agreement, select the check box to acknowledge that you accept the agreement, and then click Continue.

10. On the File Download window, click one of the filenames to download an individual zip file, or click

Download All to obtain all of the files

11. For the PeopleSoft PeopleTools installation, when you unzip the files, extract them into a temporary directory, referred to here as PS_INSTALL. The extracted files are loaded into directories Disk1, Disk2, Disk3, and so on.

For the PeopleSoft application, and other files, extract the zip files into a convenient local directory, referred to as PS_INSTALL.

For UNIX only:

After you download the installation files from Oracle Software Delivery Cloud, if it is necessary to transfer the files to a UNIX computer using FTP, you must change the permissions to make them executable, for example using the chmod +x

command. Change the mode to executable for the following files:

PS_INSTALL\Disk1\setup.sh

• Files in PS_INSTALL\Disk1\InstData:

• setup.aix

• setup.hp-ia64

• setup.linux

• setup.solaris

• setup.solaris-x86_64

• setup.zlinux

See Also

Application-specific installation instructions, My Oracle Support, (search for the PeopleSoft application)

Obtaining License Codes

Task 4-2: Running the PeopleSoft Installer

This section discusses:

• Understanding the PeopleSoft Installer

• Starting the PeopleSoft Installer

• Installing PeopleSoft PeopleTools in GUI Mode

• Installing PeopleSoft PeopleTools in Console Mode

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

127

Using the PeopleSoft Installer

Chapter 4

Understanding the PeopleSoft Installer

The PeopleSoft Installer guides you through the process of installing files to your various servers. You must run the PeopleSoft Installer on each machine that you use for one or more PeopleSoft server. The specific options that you see during the installation procedure depend upon the operating system platform, database platform and so on.

Use the PeopleSoft Installer for:

• PeopleSoft PeopleTools

• PeopleSoft applications

• Multilanguage files

• PeopleTools Client files

The directory where the files are installed is referred to in this section as PS_HOME. As described earlier in this documentation, you can configure your environment with separate installation locations for PeopleSoft

PeopleTools and PeopleSoft applications. It is a good idea to use a directory name that indicates the application you are installing and the version number, such as HCM920 for the 9.2 version of PeopleSoft Human Capital

Management.

See "Preparing for Installation," Defining Installation Locations.

You can run the installer in GUI mode, on Microsoft Windows operating systems, or in console (text) mode, on

UNIX or Linux.

Note. The machine that you use to perform your PeopleSoft PeopleTools installation must be running in 256-

color mode or higher when running the PeopleSoft PeopleTools, PeopleSoft application, multilanguage, or

PeopleSoft Pure Internet Architecture installation, and database configuration in Microsoft Windows. This is not necessary for UNIX or console mode.

The PeopleSoft Installer asks whether you want to install supporting features such as Environment Management

Hub. Before you run the PeopleSoft Installer, you may want to consult supporting documentation to help you in choosing these options.

See Also

PeopleTools: Global Technology

PeopleTools: Change Assistant and Update Manager

PeopleTools: System and Server Administration

My Oracle Support, Certifications

Task 4-2-1: Starting the PeopleSoft Installer

After you download and extract the PeopleSoft PeopleTools installation files you can find the installer in

PS_INSTALL/disk1.

To start the PeopleSoft Installer on Microsoft Windows, type:

PS_INSTALL\disk1\setup.bat [command line options]

To start the PeopleSoft Installer on a supported UNIX or Linux operating system, type:

PS_INSTALL/disk1/setup.sh [command line options]

128

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 4

Using the PeopleSoft Installer

The following list includes options that you can use when running setup.bat and setup.sh on the command line, their allowed values, descriptions, and environment variables that must be set before using the options.

Note. Only the command line options listed in this documentation are supported for PeopleSoft installation. Note that the use of a response file for silent installation is not supported for the installer for PeopleSoft PeopleTools

8.55. For some of the installations described elsewhere in this documentation, such as PeopleSoft Pure Internet

Architecture, the same options apply.

• Specify console or GUI mode with the – i

option.

• To run in GUI mode: setup.bat -i GUI

• To run in console mode: setup.sh -i console setup.bat -i console

• Specify the full absolute path to the Java (JRE or JDK) executable.

Use either of the options

– javahome or

LAX_VM to specify the absolute path to the JRE or JDK executable, including the executable name. Use this option if your installation is different than the vendordefined installation path. This is used by the installer as the runtime javahome.

On Microsoft Windows: setup.bat -javahome D:\prod\java7\bin\java.exe

setup.bat -LAX_VM D:\prod\java7\bin\java.exe

On UNIX: setup.sh -javahome /opt/java7/bin/java setup.sh -LAX_VM /opt/java7/bin/java

• Run in debug mode to investigate basic installer features.

1. Set the environment variable LAX_DEBUG; for example:

On Microsoft Windows: set LAX_DEBUG=true

On UNIX: export LAX_DEBUG=true

2. Run the installer; for example:

On Microsoft Windows: setup.bat -DDEBUG=console

On UNIX: setup.sh -DDEBUG=console

• Specify the temporary directory to extract temporary files.

This is recommended if you have less than 2 GB of space in your default temporary directory. See the

Prerequisites section for information on choosing the temporary directory.

• On Microsoft Windows, set the environment variable %TMP%, and then run setup.bat

without an option for the temporary directory; for example:

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

129

Using the PeopleSoft Installer

Chapter 4 set TMP=D:\user\temp setup.bat

• On UNIX, use the – tempdir

option to specify the absolute path to the temporary directory; for example: setup.sh -tempdir /opt/home/user/temp

• To use more than one of the preceding options, you can combine them in any order; for example: setup.bat -i console -javahome D:\prod\java7\bin\java.exe

setup.sh -LAX_VM /opt/java7/bin/java -DDEBUG=console -i console

• To start the debugger in GUI mode:

1. Type the command; for example: setup.bat -DDEBUG=console -i console

2. Press ENTER, and then hold down the CTRL key.

The GUI installer window opens, and a console window also opens with the debugger messages.

Task 4-2-2: Installing PeopleSoft PeopleTools in GUI Mode

To install PeopleSoft PeopleTools with the PeopleSoft Installer in GUI mode:

130

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 4

1. Launch the installer. For example:

PS_INSTALL\disk1\setup.bat

Click Next when you see the Welcome screen for PeopleTools 8.55.

Using the PeopleSoft Installer

PeopleSoft Installer Welcome window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

131

Using the PeopleSoft Installer

2. Click the radio button to accept the license agreement and click Next.

The License Agreement window includes the terms in several languages.

Chapter 4

PeopleSoft Installer License Agreement window

132

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 4

3. Enter your license code and click Next.

See Understanding the PeopleSoft Installer, Obtaining License Codes.

Using the PeopleSoft Installer

PeopleSoft Installer License window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

133

Using the PeopleSoft Installer

Chapter 4

4. Choose a Unicode or non-Unicode database and click Next.

Note. Unicode databases are recommended by Oracle. Some languages in a PeopleSoft installation are only supported in a Unicode database. Unicode databases can require more disk space than non-Unicode databases.

See PeopleTools: Global Technology.

This example shows the option Unicode Database (Recommended) selected.

PeopleSoft Installer Character Set window

134

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 4

Using the PeopleSoft Installer

5. Select the servers you want to install and click Next.

In this example the PeopleSoft Application Server, PeopleSoft Batch Server, PeopleSoft Database Server,

PeopleSoft File Server, and PeopleSoft Web Server are selected.

PeopleSoft Installer Server window

Use the following information to help you make your selection on the Server window:

• You can install multiple servers at the same time, but they will all be installed on the same machine. If you want to install servers on separate machines, you need to run the PeopleSoft Installer on each server machine.

• If you do not have admin privileges, you will not be able to install PeopleSoft web server. You will have to either acquire admin privileges or deselect the Web Server option to continue.

• You must install the PeopleSoft software on your database server in order to run the PeopleSoft Database

Configuration Wizard. (Running the Database Configuration Wizard is discussed in the chapter on creating a database.)

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

135

Using the PeopleSoft Installer

Chapter 4

6. Specify the directory where you want to install PeopleSoft PeopleTools, referred to in this documentation as

PS_HOME, in the Directory Name field, and click Next.

In this example, PS_HOME is C:\PT8.55.

Note. Substitute your network drive and the directory name of your choice for the default selection. The installation directory name cannot contain a space. Note that directory names containing periods or non-US-

ASCII characters may not work with some additional component software.

136

PeopleSoft Installer Choose Install Folder window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 4

Using the PeopleSoft Installer

7. If you selected the PeopleSoft Application Server, PeopleSoft Web Server, or PeopleSoft Batch Server option above, the My Oracle Support window appears.

This window does not appear if the Oracle Configuration Manager is already configured for your environment.

See "Preparing for Installation," Using Oracle Configuration Manager.

PeopleSoft Installer My Oracle Support window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

137

Using the PeopleSoft Installer

Chapter 4

8. If you would prefer not to continue with the setup of Oracle Configuration Manager, do not enter either an email address or a password.

When you click Next, a confirmation dialog box appears asking if you really do not want to receive security updates, as shown in this example. If you click Yes, the PeopleSoft PeopleTools installation continues and

Oracle Configuration Manager is not configured. You can configure Oracle Configuration Manager later from

PS_HOME/ccr using the instructions available at My Oracle Support.

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

Email address not specified dialog box

9. If you want to configure Oracle Configuration Manager in anonymous mode, clear the check box I wish to receive security updates via My Oracle Support, enter an email address, and click Next.

138

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 4

Using the PeopleSoft Installer

10. To configure Oracle Configuration Manager now, enter the email address and password associated with your

My Oracle Support account.

Select or clear the option I wish to receive security updates via My Oracle Support, and click Next.

Oracle Configuration Manager checks for Internet connectivity, and verifies the credentials specified. If there is no direct connectivity to the Internet, the Provide Proxy Information dialog box appears to enable you to define a proxy server.

Provide Proxy Information dialog box

Enter the following information:

• Proxy Server — The host name of the proxy server, for example www-proxy.us.oracle.com.

• Proxy Port — The port for the proxy server, for example, 98.

• Proxy User Name — If the proxy server requires authentication, enter the user name.

• Proxy Password — If the proxy server requires authentication, enter the password.

• Select the option I want to remain uninformed of critical security issues in my configuration check box if you want Oracle Configuration Manager to be installed in disconnected mode.

11. Click OK to confirm connectivity.

If Oracle Configuration Manager cannot validate the entered My Oracle Support account and the proxy information, the Provide Proxy Information dialog box appears. If you attempt the validation three times, an error message appears, and your account is registered as anonymous.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

139

Using the PeopleSoft Installer

Chapter 4

12. Specify the location of your Connectivity Program Directory and click Next.

For Oracle database platforms, specify the path to the 64-bit connectivity software.

The default location for the connectivity software for Oracle 11g is C:\oracle\product\11.2.0\dbhome_1\BIN, as shown in this example.

Note. If you are using Oracle 12c, the default location is C:\oracle\product\12.1.0\dbhome_1\BIN.

PeopleSoft Installer Connectivity Program window

140

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 4

Using the PeopleSoft Installer

13. Depending on the PeopleSoft servers you selected, choose whether to install the PeopleSoft PeopleTools icons and click Next.

PeopleSoft Installer PeopleTools Icons Selection window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

141

Using the PeopleSoft Installer

Chapter 4

14. If you elected to install PeopleSoft PeopleTools icons, choose a valid group folder in which to create them and click Next.

This example shows the default group folder, PeopleTools 8.55.

PeopleSoft Installer PeopleTools Program Group Folder window

142

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 4

Using the PeopleSoft Installer

15. Enter the configuration information for Environment Management, the Environment Management machine name and port number.

Select the machine name of the web server running the Environment Manager Hub. (This will very likely be the machine on which you run the PeopleSoft Pure Internet Architecture). Select the hub port number (the default is 80, as shown in the example). This needs to match the PeopleSoft Pure Internet Architecture port. If you change the port number for the PeopleSoft Pure Internet Architecture configuration, you must also change the web server listener port number for all the agents in the configuration.properties file.

See the information on configuring and running Environment Management Components in the PeopleTools:

Change Assistant and Update Manager product documentation.

PeopleSoft Installer Environment Management Details window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

143

Using the PeopleSoft Installer

Chapter 4

16. The next screen lists the PeopleSoft PeopleTools components (product features). Accept the defaults for the

PeopleSoft PeopleTools features and click Next.

144

PeopleSoft Installer Choose Product Features window

• Select PeopleTools to install PeopleSoft PeopleTools and the PeopleSoft Pure Internet Architecture. This component contains the core PeopleTools files and is required for the proper operation of the PeopleSoft system and the PeopleSoft Pure Internet Architecture.

• Select PeopleTools System Database to allow your developers to create custom PeopleSoft PeopleTools applications outside of the delivered PeopleSoft Application.

• The PeopleTools Language Pack and PeopleTools Language Development Kit contain the translated

PeopleSoft PeopleTools DLLs and the resource files and headers needed to build them.

Note. These options are available only for installations on Windows.

Select PeopleTools Language Pack if you plan on running the Windows components of the installation in languages other than English. This component contains the compiled PeopleSoft translations for the

Windows client. If you are not using multiple languages throughout your implementation, you do not need this component.

Select PeopleTools Language Development Kit if you plan on modifying or creating your own new translations for the PeopleSoft PeopleTools Windows client components. It contains the source and header files required to modify and compile new versions of these translations. Again, you do not need this component if you are not using multiple languages.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 4

Using the PeopleSoft Installer

17. You will see an installation confirmation window. If the information is correct, choose Next. If you need to modify any of the information, choose the Back button and make your changes.

The summary information includes the installation directory, the features, and the PeopleSoft servers:

PeopleSoft Installer Installation Summary window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

145

Using the PeopleSoft Installer

18. After the files have been installed, click Done to complete the setup.

The window displays the installation directory, which is C:\PT8.55 in this example.

Chapter 4

PeopleSoft Installer Install Complete window

Task 4-2-3: Installing PeopleSoft PeopleTools in Console Mode

To install PeopleSoft PeopleTools with the PeopleSoft Installer in console mode:

Note. The console mode installation is typically used on UNIX and Linux platforms, but can also be used on

Microsoft Windows.

1. Launch the PeopleSoft Installer in console mode. For example:

On Unix and Linux

PS_INSTALL/disk1/setup.sh -i console -tempdir /tmp

On Microsoft Windows

PS_INSTALL/disk1/setup.bat -i console

See Starting the PeopleSoft Installer.

2. At the Welcome prompt, press ENTER to continue.

========================================================================⇒

=======

Welcome

146

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 4

Using the PeopleSoft Installer

-------

InstallAnywhere will guide you through the installation of PeopleTools

8.55.

PRESS <ENTER> TO CONTINUE:

3. Accept the license agreement by entering Y. Select 0 when you are finished.

Portions of the agreement text have been omitted from this example for brevity.

========================================================================⇒

=======

License Agreement

-----------------

Installation and Use of PeopleTools Requires Acceptance of the Following

License Agreement:

English

Notice:  This installation program may install products above and⇒

 beyond those that you have licensed.  Please refer to your master license agreement⇒

 for the products you are entitled to use. Installing and/or using software that⇒

 you have not specifically licensed may result in termination of your license agreement with PeopleSoft and entitle PeopleSoft to receive damages.  ⇒

 It may also be an infringement of PeopleSoft's intellectual property rights.

DO YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT? (Y/N): y

4. Enter your license code, and press ENTER to continue.

Do not include spaces when entering the license code.

See Understanding the PeopleSoft Installer, Obtaining License Codes.

   Please enter your PeopleSoft license code []:

5. Enter 1 to select a Unicode Database (Recommended), or 2 to select a non-Unicode database, and then 0 to continue.

Note. Unicode databases are beneficial if you intend to deploy your applications globally. Some languages in a PeopleSoft installation are only supported in a Unicode database. Unicode databases can require more disk space than non-Unicode databases.

See PeopleTools: Global Technology.

Please select the Oracle database character set:

  ->1- Unicode Database (Recommended)

    2- Non-Unicode Database

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

147

Using the PeopleSoft Installer

Chapter 4

To select an item enter its number, or 0 when you are finished [0] : 

6. Select the PeopleSoft servers you want to install.

For Oracle please select the products to install:

  ->1- PeopleSoft Application Server

  ->2- PeopleSoft Batch Server

  ->3- PeopleSoft Database Server

  ->4- PeopleSoft File Server

  ->5- PeopleSoft Web Server

To select an item enter its number, or 0 when you are finished [0] :

By default, all of the servers supported for your database platform are selected.

Note. If you are installing on UNIX, do not use Symbolic Links. Use the actual directory.

7. Enter the installation location, such as /home/pt855, referred to as PS_HOME, and press ENTER to continue.

Note. In console mode, the browse option for specifying a different install directory is unavailable.

Please enter an installation location or press <ENTER> to accept the⇒

 default

   (Default: C:\PT8.55-803-I1):

8. If you selected the PeopleSoft Application Server, PeopleSoft Web Server, or PeopleSoft Batch Server option above, the Oracle Configuration Manager Setup prompt appears.

This prompt does not appear if the Oracle Configuration Manager is already configured for your environment.

See "Preparing for Installation," Using Oracle Configuration Manager.

Email address / User Name [DEFAULT]: 

Provide your My Oracle Support password to receive security updates via⇒

 your My Oracle Support account.

Password (optional):

9. If you would prefer not to continue with the setup of Oracle Configuration Manager, do not enter either an email address or a password.

When you enter Next, a confirmation prompt asks if you really do not want to receive security updates. If you enter Y (Yes), the PeopleSoft PeopleTools installation continues and Oracle Configuration Manager is not configured. You can configure Oracle Configuration Manager later from PS_HOME/ccr using the instructions available on My Oracle Support.

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

You have not provided an email address.

Do you wish to remain uninformed of critical security issues in your⇒

 configuration? (Y/N): Y

10. If you want to configure Oracle Configuration Manager in anonymous mode, enter an email address but no password.

11. To configure Oracle Configuration Manager now, enter the email address and password associated with your

My Oracle Support account, and press ENTER to continue.

Oracle Configuration Manager checks for Internet connectivity, and verifies the credentials specified. If there

148

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 4

Using the PeopleSoft Installer

is no direct connectivity to the Internet, the next prompt asks you to define a proxy server. Provide the information for the proxy server in the following format:

[<proxy-user>@]<proxy-host>[:<proxy-port>]

Enter the following information:

• Proxy User Name — If the proxy server requires authentication, enter the user name.

Note. If you do not specify the proxy-user, (that is, you enter <proxy-host>:<proxy-port>), a proxy server will be used for the connection, but will not be authenticated.

• Proxy Server — The host name of the proxy server, for example www-proxy.us.oracle.com.

• Proxy Port — The port for the proxy server, for example, 98.

12. If you specify Proxy User Name, a prompt appears asking for a Proxy Password.

13. Enter NONE if you do not want to receive security updates through your My Oracle Support account.

If you want to remain uninformed of critical security issues in your⇒

 configuration, enter NONE

Proxy specification (DEFAULT: NONE)

14. Enter Next to confirm connectivity.

If Oracle Configuration Manager cannot validate the entered My Oracle Support account and the proxy information, the Provide Proxy Information prompt appears again. If you attempt the validation three times, an error message appears, and your account is registered as anonymous.

15. Microsoft Windows only: Specify the database connectivity directory.

Please select the location of Connectivity Program Directory [c:\orawin⇒

\bin]

   :

Specify the path to the 64-bit connectivity software.

The default location for the connectivity software for Oracle 11g is: C:\oracle\product\11.2.0\dbhome_1\BIN.

If the database connectivity software was installed to a different directory, enter that path instead.

Note. If you are using Oracle 12c, the default location is C:\oracle\product\12.1.0\dbhome_1\BIN.

16. Microsoft Windows only: Indicate whether you want icons to be created.

Do you want to Install PeopleTools Icons?

  ->1- Yes

    2- No

To select an item enter its number, or 0 when you are finished [0] :

17. If you select the option to create PeopleTools icons, enter the name for the program group.

The default is PeopleTools 8.55.

 Please enter in the program group folder you wish to create the icons⇒

 in

   [PeopleTools 8.55]:

18. Enter the configuration for Environment Management. Select the machine name and port number.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

149

Using the PeopleSoft Installer

Chapter 4

Please enter the hub machine name: [PSEMHUB]:

   Please enter the hub port number: [80]:

Select the machine name of the web server running the Environment Manager Hub. (This will very likely be the machine on which you run the PeopleSoft Pure Internet Architecture). Select the hub port number (the default is 80). This needs to match the PeopleSoft Pure Internet Architecture port. If you change the port number for the PeopleSoft Pure Internet Architecture configuration, you must also change the web server listener port number for all the agents in the configuration.properties file.

See the information on configuring and running Environment Management components in the PeopleTools:

Change Assistant and Update Manager product documentation.

19. Choose the features that you wish to install:

To select/deselect a feature or to view its children, type its number

         -> 1-  PeopleTools

            2-  PeopleTools System Database

            3-  PeopleTools Language Pack

            4-  PeopleTools Language Development Kit

Options 3 and 4 appear only on Microsoft Windows.

20. At this point, you can toggle the install status of each product. Press 0 and then ENTER to continue and the

PeopleSoft Installer will give you a summary of your selection. This summary will depend on your earlier selections.

Pre-Install Summary

Please review the following before continuing:

PeopleTools  will be installed in the following location: /home/PT855 with the following features:

PeopleTools

PeopleTools System Database

The following PeopleSoft Servers were selected by you:

PeopleSoft Application Server

PeopleSoft Batch Server

PeopleSoft Database Server

PeopleSoft File Server

PeopleSoft Web Server

Database Type:

Oracle

Environment Hub Configuration:

Hub machine name: PSEMHUB

Hub port number: 80

Press 1 for Next, 2 for Previous, 3 to Cancel, or 5 to Redisplay [1]

21. Press ENTER to start the installation.

The PeopleSoft Installer displays a text-based progress bar to indicate the progress of the installation.

150

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 4

Using the PeopleSoft Installer

22. Press ENTER to exit.

Note. For UNIX operating systems, if you chose PeopleSoft servers that require a JRE, you see the

"Unpacking JRE" message after the progress bar.

Installation Complete

---------------------

Congratulations. PeopleTools has been successfully installed to:

   /home/PT855

PRESS <ENTER> TO EXIT THE INSTALLER:

23. If you are installing on AIX, go to the PS_HOME/jre directory and ensure that the directory has executable permissions. If not, set the permission using a command such as chmod +x.

Task 4-3: Verifying Necessary Files for Installation on Windows

PeopleSoft PeopleTools 8.50 and later releases are developed using Microsoft Visual C++ 2005 and later.

Microsoft, as part of VC++ 2005, changed the way applications use and ship the required C Run Time (CRT) files

(these files are installed as shared assemblies). PeopleSoft PeopleTools 8.50 and higher programs require these files to be present or the programs will not run.

During your PeopleSoft PeopleTools installation, the install programs will automatically update the Microsoft

Windows machine performing the installation.

The required CRT files are installed by all of the PeopleSoft installers, including:

• PeopleSoft PeopleTools

• PeopleTools Client

• Database Configuration Wizard (DCW)

• PeopleSoft Pure Internet Architecture

• Change Assistant

• Change Impact Analyzer

• Web Application Deployment tool

In some cases it may be necessary for you to carry out a separate installation of the CRT files. For example:

• If the update does not take place during the installation program run, you may not be able to launch

PeopleSoft PeopleTools client or server executables on that machine and may receive error messages.

• If you are accessing PeopleSoft PeopleTools executables from a machine on which the PeopleSoft installer did not run, the executables may not work and you may receive error messages.

If you encounter these errors, you can update the Microsoft Windows machine's CRT files by running the installers manually.

If installing on a server or PeopleTools Client environment:

1. Go to PS_HOME\setup\psvccrt.

2. Run psvccrt_retail.msi.

3. Run psvccrt_retail_x64.msi.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

151

Using the PeopleSoft Installer

Note. For each installer, the installation is completed automatically.

Chapter 4

Task 4-4: Installing PeopleSoft Application Software

After installing PeopleSoft PeopleTools, install the PeopleSoft application software to the same PS_HOME directory, or to PS_APP_HOME. The installation windows may look slightly different depending upon which application you install.

See "Preparing for Installation," Defining Installation Locations.

To install the PeopleSoft application, launch the PeopleSoft Installer from PS_INSTALL/disk1 and follow the procedure in Running the PeopleSoft Installer.

Use the following guidelines when installing:

• If supported by the PeopleSoft Application that you are installing, you can install the PeopleSoft Application software to a PS_APP_HOME location that is not the same as the PS_HOME location where you installed

PeopleSoft PeopleTools. Be sure to review the installation guide for your PeopleSoft Application to determine whether this functionality is supported.

• If you are installing more than one application, it is a good idea to create an application-specific PS_HOME or

PS_APP_HOME and carry out an installation of PeopleSoft PeopleTools for each application. This helps you to maintain your applications more efficiently, since you can easily match each application version to the correct version of PeopleSoft PeopleTools.

• The installation includes all products for your PeopleSoft application and both System Database and Demo

Database files. After you set up the PeopleSoft Pure Internet Architecture, you will complete a step to update the installation table for your licensed products.

See "Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode," Completing Post-Installation Steps.

See "Setting Up the PeopleSoft Pure Internet Architecture in Console Mode," Completing Post-Installation

Steps.

Task 4-5: Installing the Multilanguage Files

If you are licensed for and have chosen to install languages other than English, you need to load the Applicationspecific PeopleSoft Multilanguage files. Each PeopleSoft Application product installation has corresponding

Multilanguage installation software that contains all the non-English translations.

To download the necessary files for a Multilanguage installation from the Oracle Software Delivery Cloud portal, select the Translation Media Pack for your PeopleSoft Application on the Media Pack Search page. The listing for the Translation Media Pack is divided into sets of files for PeopleSoft PeopleTools, the PeopleSoft Application, and the Multilanguage files for the PeopleSoft Application.

Warning! The release numbers for the PeopleSoft Application media pack and the Application Multilanguage media pack must be in sync. For example, if you are installing HCM 9.2 Feature Pack 1, you can only use the

Multilanguage HCM 9.2 Feature Pack 1 ML; you cannot use the HCM 9.2 ML.

Download each media pack into a temporary location, referred to here as PS_INSTALL, launch the PeopleSoft installer from PS_INSTALL/disk1, and follow the procedure in the task Running the PeopleSoft Installer.

To carry out a Multilanguage installation:

• Install the PeopleSoft PeopleTools installation files to PS_HOME.

152

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 4

Using the PeopleSoft Installer

• Install the PeopleSoft Application installation files to PS_APP_HOME.

• Install the PeopleSoft Application Multilanguage installation files to the same PS_APP_HOME as the

PeopleSoft Application installation files.

Keep in mind that the PS_APP_HOME installation location may be the same as or different from the PS_HOME location, as described previously.

See "Preparing for Installation," Planning Your Initial Configuration.

Task 4-6: Installing the PeopleTools Client Files

This section discusses:

• Installing the PeopleTools Client Files Using the PeopleSoft Installer

• Installing the PeopleTools Client Files in Silent Mode

Task 4-6-1: Installing the PeopleTools Client Files Using the PeopleSoft

Installer

To install the files needed for the PeopleTools Client, you must first install PeopleSoft PeopleTools. After you install PeopleSoft PeopleTools, launch the PeopleSoft Installer from PS_HOME\setup\Client\Disk1 and follow the procedure in the section Running the PeopleSoft Installer. Note that the PeopleTools Client installation does not include the Environment Management Setup window.

Note. If you installed PeopleSoft PeopleTools on a UNIX or Linux computer, you can copy the directory

PS_HOME\setup\Client\ to a Microsoft Windows machine to install the client.

Task 4-6-2: Installing the PeopleTools Client Files in Silent Mode

This section discusses:

• Editing the Response File

• Running the Silent Mode Installation for the PeopleTools Client

Editing the Response File

You can carry out a silent installation of the PeopleTools client files by providing all the required settings in a response file. With silent installation there is no user interaction after the installation begins.

You need a response file to start the installer in silent mode. After installing PeopleSoft PeopleTools you can find a response file template (resp_file_client.txt) in the directory PS_HOME\setup\Client\Disk1. Modify the values in the response file according to your installation requirements. Use the information in the section Running the

PeopleSoft installer for guidance in editing the file.

For example, to specify D:/PT8.55_Client as the installation directory, edit the file to include this line:

USER_INSTALL_DIR=D:/PT8.55_Client

Note. Use a forward slash ("/") to specify the directory.

Sample response file:

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

153

Using the PeopleSoft Installer

Chapter 4

# Response file for Client Installation

# Notes:

# 1. Use "/" forward slash in the path (unix style), (for ex, D:/PT8.53-⇒

803-R1-client)

# 2. Replace _DESTDIR_ below with the destination directory path.

# 3. Invoke silent install as "<cddir>\disk1\setup.bat -i silent -DRES_⇒

FILE_PATH=<path_to_response_file>".

# the install directory for (for ex, D:/PT8.53-803-R1-client)

USER_INSTALL_DIR=_DESTDIR_

# Possbile values for database type are "ORA","DBX","MSS","DB2"

DB_TYPE=ORA

# "0" for non-unicode db and  "1" for unicode db

# Applies to daatabase types "ORA","DBX","MSS","DB2"

UNICODE_DB=1

# install shortcuts for Client components in start > programs , allowed⇒

 values- "0" not to create shortcut, "1" to create shortcut.

USER_INPUT_RESULT_0=0

# if you set USER_INPUT_RESULT_0 to 1 (above) then Name your shortcut like⇒

 the way you want to see in Start>programs (default is PeopleTools Client⇒

 8.55)

USER_INPUT_RESULT_14=PeopleTools Client 8.55

Running the Silent Mode Installation for the PeopleTools Client

Use the response file that you modified for your configuration. Substitute the location where you saved the response file for <path_to_response_file> in the following procedures:

To install the PeopleTools client files in silent mode:

1. In a command prompt, go to PS_HOME\setup\Client\Disk1.

2. Run the following command: setup.bat -i silent -DRES_FILE_PATH=<path_to_response_file>

Task 4-7: Mapping a Drive on the Install Workstation

If you need to install to the file server or PeopleTools Client from a networked install workstation, map a drive letter to the top-level PeopleSoft directory (PS_HOME) from the install workstation. The PS_HOME directory must be shared, and you must have write permission from the install workstation to the file server or PeopleSoft

Client.

From the install workstation, create a logical drive that points to the PS_HOME directory.

On a Windows network, use Windows Explorer to map to the drive on the file server or PeopleTools Client to which you are installing; or use the NET USE command, for example:

154

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 4

NET USE N: \\SERVER1\PS_HOME

On a Novell network, use the MAP command:

MAP ROOT N:=SERVER1/SYS:PS_HOME

In this example, SERVER1 is the name of the file server or PeopleTools Client.

See Also

"Setting Up the Install Workstation"

Using the PeopleSoft Installer

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

155

Chapter 5

Setting Up the Install Workstation

This chapter discusses:

• Understanding the Install Workstation

• Prerequisites

• Starting Configuration Manager

• Setting Startup Options

• Editing the Default Profile

• Running Client Setup

Understanding the Install Workstation

This chapter describes how to set up a PeopleSoft Windows-based client for connecting to the database server in two-tier mode, specifically for the purpose of performing install-related tasks from the workstation. You must configure at least one two-tier Windows-based client for running the Data Mover and SQR processes required for setting up the batch server and for creating the PeopleSoft database. For some installations you may wish to set up multiple install workstations, so that you can perform asynchronous tasks at the same time; for example, you could create and populate multiple databases simultaneously. You can quickly configure multiple workstations by exporting a configuration file from one workstation and importing it to another workstation.

See Also

PeopleTools: System and Server Administration

Prerequisites

The following tasks are prerequisites for setting up the install workstation:

• The workstation must have database connectivity software installed.

• You must have planned your database creation strategy. You should know the precise names of the databases that you intend to create.

• Make sure that you have created your connect strategy. You must use a Connect ID. You should know both the Connect ID and Connect password.

For information on PeopleSoft Connect ID and Connect password, consult the PeopleTools: System and

Server Administration product documentation for information on setting Application Server domain parameters.

• The workstation must have a logical drive mapped to PS_HOME on the file server (or, if the file server and

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

157

Setting Up the Install Workstation

Chapter 5 install workstation are one and the same, PS_HOME can be installed on a local drive).

• The person performing the installation must have read access to the PS_HOME directory.

If this is the same workstation on which the PeopleSoft PeopleTools installation was performed, it should have a

PeopleTools 8.5 installation program group, which was created when you loaded the PeopleTools software. This isn't a requirement, but it does make it more convenient to run the PeopleTools install applications.

See Also

"Preparing for Installation"

"Using the PeopleSoft Installer"

Task 5-1: Starting Configuration Manager

Configuration Manager is a utility for configuring workstations being used as the PeopleTools Development

Environment. These are its principal functions:

• Sets up and make changes to PeopleSoft configuration settings.

• Creates a program group containing Microsoft Windows shortcuts to PeopleSoft applications.

• Installs local DLLs.

The first time you run Configuration Manager on the client, it will populate certain fields with default values specified in a configuration file stored on the file server, specifically: PS_HOME\setup\pstools.cfg. This configuration file was set up when you ran the installation. Once you set up and run Configuration Manager, it will populate fields using values that are stored in the Windows system registry.

To start Configuration Manager, do one of the following:

• On Microsoft Windows 7, select Start, Programs, PeopleTools 8.55, Configuration Manager. (This program group will be available if you installed PeopleSoft PeopleTools on this workstation.)

• On Microsoft Windows 8 or 2012 R2, access the Apps screen, navigate to the PeopleTools 8.55 category, and select Configuration Manager.

Note. See the documentation for your operating system for information on accessing the Apps screen.

• If the PeopleTools 8.55 program group was not installed on this workstation, run pscfg.exe directly from the

PS_HOME\bin\client\winx86 directory on the file server.

Task 5-2: Setting Startup Options

The Startup tab of Configuration Manager sets the default options for the PeopleSoft sign-on screen that is used for connecting to a PeopleSoft database. It also contains a setting that specifies the local directory for storing cached PeopleSoft data.

To set Startup options:

1. Confirm that you are viewing the Configuration Manager Startup tab (this tab is what you see if you started

Configuration Manager as described in the previous task).

2. Set the following options:

Database type Verify the type of RDBMS. This should already be set to Oracle.

158

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 5

Setting Up the Install Workstation

Application Server Name This option appears if you select a database type of Application Server. It is where you enter your application server name if you are setting up a three-tier connection.

Database name The name of the default database to connect to. Enter the name of one of the databases that you intend to create.

User ID The name of the default user that will appear in the sign-on screen. This can be any valid user name, although for installation setup it normally matches the name of one of the built-in PeopleSoft users

(typically PS or VP1) that will be installed in the database.

Connect ID and Connect Password Type your connect ID and password into these fields. Connect ID is required for this PeopleSoft release.

Task 5-3: Editing the Default Profile

Begin by editing the default profile for the workstation. Among other things, this will verify that the paths to

PS_HOME and its subdirectories are correctly set, which is required for subsequent tasks.

For more information on using Configuration Manager, see the PeopleTools: System and Server Administration product documentation for configuring user profiles.

To edit the default profile:

1. Select the Profile tab in Configuration Manager.

Only one profile, the Default Profile, has been defined.

2. Select Edit to display the Edit Profile dialog box, and then select the Process Scheduler tab.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

159

Setting Up the Install Workstation

3. In the Process Scheduler tab verify the options listed below the example.

These should have been set correctly by the PeopleSoft installation program.

Chapter 5

160

Edit Profile dialog box: Process Scheduler tab

• Verify that the PeopleSoft Home Directory (PS_HOME) field is set to the path to PS_HOME on the file server.

• Verify that the PeopleSoft Apps Home Directory (PS_APP_HOME) field is set to the path to

PS_APP_HOME on the file server.

The default value is the same as PS_HOME.

• On Microsoft Windows operating systems, set the Database Drivers (DBBIN) field to the path for the 64bit database connectivity files, if necessary.

The example shows the default for Oracle, C:\oracle\product\11.2.0\dbhome_1\bin.

• Set the SQR Executables (SQRBIN) field to the file server directory where SQR for Windows was installed when you ran the PeopleSoft Installer.

• Set the SQR Flags (PSSQRFLAGS) field to -ZIF<PS_HOME>\sqr\pssqr.ini.

• Set the SQR Report Search 1 (PSSQR1) field to PS_HOME\sqr. The remaining SQR Report Search fields can be left blank, because no additional SQR report directories have been created yet.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 5

4. Select the Common tab of the Edit Profile dialog box, shown in this example:

Setting Up the Install Workstation

Edit Profile dialog box: Common tab

The following fields on the Common tab are used to set Data Mover default input, output, and log directories.

• Verify that the Input Directory and Output Directory fields are set to PS_HOME\data. This directory will store the Data Mover scripts required to populate the PeopleSoft database.

• Set the Log Directory to a local workstation directory to store the Data Mover log files. The default is

C:\TEMP.

Data Mover will not create a new directory under PS_APP_HOME or PS_HOME for log files. If you want

Data Mover to write log files into PS_APP_HOME, you must create a new directory named log under

PS_APP_HOME.

5. Select OK to close the Edit Profile dialog box.

Task 5-4: Running Client Setup

The Client Setup tab does the following:

• Installs a PeopleSoft program group on the workstation.

• Installs system DLLs on the workstation.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

161

Setting Up the Install Workstation

Chapter 5

These Client Setup functions are performed when you click OK or Apply from Configuration Manager only if the

Install Workstation option on the Client Setup tab is selected.

Note. Any files installed by Client Setup on the workstation from the file server use the paths specified in the default profile.

To run Client Setup:

1. Select the Client Setup tab in Configuration Manager.

2. In the Group Title text box enter the name of the program group for the icons you want on the client workstation. (A program group name cannot contain any of the following characters: \ / : * ? " < > |)

You can call the program group anything you want, but this documentation uses PeopleTools 8.55.

3. If you do not have a PeopleTools 8.55 program group set up on the workstation, be sure to check the following two options for installing shortcuts to applications essential for installation.

Note. When you run Client Setup, it will uninstall any existing shortcuts in the PeopleTools 8.55 program group, and install shortcuts for the applications you have selected. If you subsequently want to install or uninstall shortcuts, you can always re-run Client Setup.

Data Mover

Configuration Manager

4. Select the option Install Workstation.

This check box determines whether Client Setup runs when you click Apply or OK in Configuration Manager.

If this option is not selected, Client Setup will create or update settings in the registry, but it will not set up the

PeopleTools 8.55 program group or install local DLLs.

5. Click OK to run Client Setup and close Configuration Manager.

162

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6A

Creating a Database Manually on Windows

This chapter discusses:

• Understanding Database Creation

• Preparing for the PeopleSoft Database Installation

• Creating the Windows Service for the Database Instance

• Using SQL Tools

• Editing Database Scripts (non-Multitenant)

• Creating an Oracle Instance (non-Multitenant)

• Creating Catalog Views and Utility Tablespaces (non-Multitenant)

• Creating PS.PSDBOWNER Table (non-Multitenant)

• Creating Application-Specific Dbspaces and Tablespaces (non-Multitenant)

• Creating PeopleSoft Database Roles (non-Multitenant)

• Creating the PeopleSoft Database Owner ID (non-Multitenant)

• Setting Up Connect ID (non-Multitenant)

• Editing Database Scripts (Multitenant Architecture)

• Creating an Oracle Instance (Multitenant Architecture)

• Creating Catalog Views and Utility Tablespaces (Multitenant Architecture)

• Creating PS.PSDBOWNER Table (Multitenant Architecture)

• Creating Application-Specific Dbspaces and Tablespaces (Multitenant Architecture)

• Creating PeopleSoft Database Roles (Multitenant Architecture)

• Creating the PeopleSoft Database Owner ID (Multitenant Architecture)

• Setting Up Connect ID (Multitenant Architecture)

• Updating Connection Information

• Setting NLS_LANG in the Windows Registry

• Creating Data Mover Import Scripts

• Running Data Mover Import Scripts

• Checking the Log Files and Troubleshooting

• Changing the Base Language

163

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Creating a Database Manually on Windows

Chapter 6A

Understanding Database Creation

This section describes the tasks required to create a PeopleSoft product database. During a standard PeopleSoft installation you will execute these tasks to create two distinct types of databases.

System: The System (SYS) database has no company specific data, and can be used to load your data and begin development of your production database.

Demo: The Demo (DMO) database contains data for a sample company, and can be used immediately for demonstration, for testing, and as a development reference.

The requirements for these databases vary, so not all of this section's tasks apply to each database. The instructions will note any distinctions between creating a Demo and a System database.

Remember, you need to have the PeopleTools Development Environment set up to create your database.

This section includes tasks to create pluggable databases and for non-pluggable databases, as well as tasks that apply to both types. The pluggable database tasks create an Oracle Container Database (CDB) and a Pluggable

Database (PDB), and are labelled "(Multitenant Architecture)." The tasks specific to non-pluggable databases are labelled "(non-Multitenant)." Choose which tasks to use according to the RDBMS you installed, as follows:

• If you installed Oracle 12c Enterprise Edition RDBMS, you can choose to create either CDBs or non-CDBs.

• If you installed Oracle 11gR2 RDBMS, you can create only a non-CDB. For installations on Oracle 11gR2, pluggable databases are not supported. In this case, use the non-multitenant sections.

Important! Do not forget that application-specific installation steps are provided in a separate document specific to the application. For instance, if you are performing PeopleSoft CRM installation, you need both this PeopleSoft

PeopleTools installation guide and any additional instructions provided by CRM. Search in My Oracle Support for the installation documentation specific to your application.

Important! If you are installing the PeopleSoft software on an Oracle RAC database, there are additional configuration procedures that you must follow.

See PeopleTools: Data Management, "Setting Up the PeopleSoft Installation with Oracle RAC."

Note. The Database Configuration Wizard cannot be used on a Microsoft Windows operating system. You must use the manual method of creating a database for this configuration.

After you complete the tasks in this chapter, read the chapter "Completing the Database Setup." Depending upon your environment, you may not need to carry out every task in that chapter. However it is important that you evaluate the requirements and perform the necessary tasks.

See Also

"Preparing for Installation," Planning Database Creation

"Setting Up the Install Workstation"

Task 6A-1: Preparing for the PeopleSoft Database Installation

This section discusses:

• Installing the PeopleSoft Database Server Components on the Database Server

164

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6A

• Installing the Oracle RDBMS Software

• Identifying the Oracle RDBMS Trace and Alert File Locations

• Obtaining Windows Administrator Authority

• Creating an INIT<SID>.ORA File

• Creating an INIT<SID>.ORA File (Multitenant Architecture)

• Creating Target Directory Paths

• Creating Target Directory Paths (Multitenant Architecture)

• Setting the ORACLE_SID Environment Variable

Creating a Database Manually on Windows

Task 6A-1-1: Installing the PeopleSoft Database Server Components on the

Database Server

To create a PeopleSoft Database you must have installed the PeopleSoft software on your database server by running the PeopleSoft Installer and choosing the Database Server option, as described in a previous chapter. In addition, you need to install your application software to your database server before loading the database.

See "Using the PeopleSoft Installer."

Note. Remember, you need to have the PeopleTools Development Environment set up to create your database.

See the information on using PeopleSoft Configuration Manager in the PeopleTools: System and Server

Administration product documentation.

Task 6A-1-2: Installing the Oracle RDBMS Software

The rest of this chapter assumes that the Oracle RDBMS software is installed on your database server. If you have not already done so, install the Oracle RDBMS software now. During the database creation process, we refer to an existing Oracle RDBMS installation. Specifically:

ORACLE_HOME and ORACLE_HOME\bin

Note. If you are creating pluggable databases, you must install Oracle 12c Enterprise Edition.

Task 6A-1-3: Identifying the Oracle RDBMS Trace and Alert File Locations

For Oracle 11gR2 and later releases, all diagnostic data, including the alert log, are stored in the Automatic

Diagnostic Repository (ADR), whose location is set by the DIAGNOSTIC_DEST initialization parameter. Due to this change, the initialization parameter settings for background dump (BACKGROUND_DUMP_DEST), core dump (CORE_DUMP_DEST), and user dump (USER_DUMP_DEST) are replaced by the diagnostic destination parameter DIAGNOSTIC_DEST. For information on the DIAGNOSTIC_DEST parameter and the default location for the ADR, see the Oracle RDBMS documentation.

See the information on managing diagnostic data in the Oracle Database Administrator's Guide.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

165

Creating a Database Manually on Windows

Chapter 6A

Task 6A-1-4: Obtaining Windows Administrator Authority

To create a database instance on Microsoft Windows, you must be a Windows administrator of the target server.

This is necessary because creating an instance on Microsoft Windows requires creating a SERVICE using the

Oracle

ORADIM

command to add a Windows service. On UNIX, an Oracle SID is comprised of many different processes. On Microsoft Windows, an Oracle SID is run as a single Windows service and you need to be an administrator to create that service.

Note. You must also be part of the ORA_DBA group.

Task 6A-1-5: Creating an INIT<SID>.ORA File

You must create an init.ora with the naming convention of init<SID>.ora in the ORACLE_HOME\database directory of the Oracle installation. The init<SID>.ora file is referenced in the following places during the database creation process:

• Using the ORADIM command to create the Windows Service

• Executing the CREATEDB.SQL script

Note. PeopleSoft PeopleTools 8.55 supports Oracle 11g and Oracle 12c on Microsoft Windows. The

PeopleSoft scripts are delivered to work across all versions of the Oracle RDBMS that Oracle supports for this release of PeopleSoft PeopleTools. To support these versions the PeopleSoft installation is delivered with the

CREATEDB.SQL script for Oracle 11g or later installations.

Note. If you are creating pluggable databases, see the following section Creating an INIT<SID>.ORA File

(Multitenant Architecture) after completing this section.

Add or modify the following parameters in the init<SID>.ora file:

• DB_NAME = <SID>

• DB_FILES

Specify the maximum allowed for your operating system, typically 1021.

• OPEN_CURSORS = 1000

This is a minimum value. You may choose to set this higher.

• DB_BLOCK_SIZE = 8192

Review the following init<SID>.ora parameters and if necessary modify them for your environment:

DB_BLOCK_SIZE

The default DB_BLOCK_SIZE in the init.ora file is 8192 or 8K. For PeopleSoft ANSI databases this is more than adequate. For PeopleSoft Unicode databases (for example, CHARACTER_SET AL32UTF8), a

DB_BLOCK_SIZE value of 8K is required.

NLS_LENGTH_SEMANTICS

Use these guidelines to set the

NLS_LENGTH_SEMANTICS

init<SID>.ora parameter:

• Set

NLS_LENGTH_SEMANTICS=CHAR

if you are installing a Unicode database with PeopleSoft application

9.0 or higher releases on PeopleTools 8.48 or higher.

• Set

NLS_LENGTH_SEMANTICS=BYTE

if you are installing any non-Unicode database (such as a Western

European or Shift-JIS database).

166

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6A

Creating a Database Manually on Windows

• Set

NLS_LENGTH_SEMANTICS=BYTE

if you are installing a Unicode database with PeopleSoft application prior to release 9.0 on PeopleSoft PeopleTools prior to release 8.48.

If necessary, verify the PeopleSoft PeopleTools release for your PeopleSoft application using this SQL query: select TOOLSREL from PSSTATUS

Unicode databases on PeopleSoft PeopleTools 8.48 and later, with PeopleSoft application 9.0 or later, use character length semantics. When character length semantics is used, a field of VARCHAR2(10) will store 10 characters. Prior to PeopleSoft PeopleTools 8.48 and PeopleSoft applications 9.0, byte length semantics was used, meaning a VARCHAR2(10) stored 10 bytes. If you are upgrading from a release before PeopleSoft PeopleTools

8.48 and PeopleSoft application 9.0 to one after 8.48 and 9.0, a database conversion is necessary for utilizing

CHARACTER LENGTH SEMANTICS. This conversion process is covered in all PeopleSoft application 9.0 or higher upgrade paths.

It is very important that you set this parameter at the correct point during database creation. Database creation consists of running several scripts before loading the database with Data Mover, as follows:

• CREATEDB.SQL

• UTLSPACE.SQL

XXDDL.SQL

• DBOWNER.SQL

• PSROLES.SQL

• PSADMIN.SQL

• CONNECT.SQL

Set the parameter

NLS_LENGTH_SEMANTICS

at the beginning of database creation or right before the Data

Mover load.

To do this, modify the init<SID>.ora to add the

NLS_LENGTH_SEMANTICS

parameter, and then shut down and restart the database instance.

Oracle Password

If you choose to use an Oracle Password file, create one using the ORAPWD utility, as illustrated in this example: set ORACLE_SID=FDMO orapwd file=$ORACLE_HOME\dbs\pwdtemp2.ora password=manager entries=5

If you choose not to use an Oracle Password file, you must make one of the following changes to the init<SID>.ora file before running the CREATEDB.SQL script:

• Remove the line beginning with remote_login_passwordfile

, or add a comment character to the beginning as shown in this example:

#remote_login_passwordfile=EXCLUSIVE

• Set the parameter to NONE, as shown in this example: remote_login_passwordfile=NONE

For more parameters that may be required for the init<SID>.ora file, consult My Oracle Support.

See Operating System, RDBMS & Additional Component Patches Required for Installation PeopleTools, My

Oracle Support (search for the title and select your release).

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

167

Creating a Database Manually on Windows

Chapter 6A

Task 6A-1-6: Creating an INIT<SID>.ORA File (Multitenant Architecture)

If you are creating pluggable databases, set <SID> to the database name for the CDB (root database). This documentation uses PDB_SERVICE_NAME to refer to the PDB.

Create an init<SID>.ora file as described in Creating an INIT<SID>.ORA File, and append the following line in the init<SID>.ora: enable_pluggable_database=true

Note. It is strongly advisable to set the value of the parameter MEMORY_TARGET, otherwise you may get the error "ORA-04031: unable to allocate string bytes of shared memory" (where string represents memory size) while creating the database . For information on the MEMORY_TARGET environment variable, see the Oracle

Database documentation.

Task 6A-1-7: Creating Target Directory Paths

You must create the directory path structure for the target directories referenced in the scripts that are executed by the database creation process. The referenced directories are not created on the fly, so they need to exist when referenced.

Note. If you want to use something other than the delivered directory paths, you need to modify the

CREATEDB.SQL, UTLSPACE.SQL, and XXDDL.SQL scripts in the PS_HOME\scripts directory, replacing the delivered paths with paths that are appropriate for your site installation prior to creating the database.

Here are some examples of directory path structure references.

• The delivered CREATEDB.SQL script makes the following directory path structure references, where

<drive> refers to the Microsoft Windows drive letter: startup nomount pfile=%ORACLE_HOME%\database\init<SID>.ora

DATAFILE       '<drive>:\oradata\<SID>\system01.dbf'   SIZE   400M

LOGFILE       '<drive>:\oradata\<SID>\log01.dbf'         SIZE   70M,

              '<drive>:\oradata\<SID>\log02.dbf'         SIZE   70M;

Note. Portions of the script have been omitted for clarity.

• The init<SID>.ora parameter file that is referenced in the CREATEDB.SQL script makes the following directory path structure references.

Note. Portions of the init<SID>.ora parameter file have been omitted for clarity. These paths are inserted manually by the user creating the init<SID>.ora parameter file.

Control file references:

control_files = ("c:\apps\db\Oracle11g\oradata\ORC1\control01.ctl", "c:⇒

\apps\db⇒

\Oracle11g\oradata\ORC1\control02.ctl", "c:\apps\db\Oracle11g\oradata⇒

\ORC1⇒

\control03.ctl")

• The delivered UTLSPACE.SQL script makes the following directory path structure references:

168

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6A

Creating a Database Manually on Windows

Note. Portions of the script have been omitted for clarity.

CREATE  TEMPORARY TABLESPACE       PSTEMP

TEMPFILE                '<drive>:\oradata\<SID>\pstemp01.dbf'     SIZE⇒

 300M

EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K;

CREATE TABLESPACE       PSDEFAULT

DATAFILE                '<drive>:\oradata\<SID>\psdefault.dbf'     SIZE⇒

 10M

EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

• The delivered XXDDL.SQL scripts make the following directory path structure references:

Note. This is a sample of the first several Create Tablespace SQL statements in the XXDDL.SQL script. The rest of the script has been omitted here for clarity.

CREATE TABLESPACE PSIMAGE DATAFILE '<drive>:\oradata\<SID>\psimage.dbf'⇒

 SIZE 8M

EXTENT MANAGEMENT LOCAL AUTOALLOCATE

/

CREATE TABLESPACE PSINDEX DATAFILE '<drive>:\oradata\<SID>\psindex.dbf'⇒

 SIZE 64M

EXTENT MANAGEMENT LOCAL AUTOALLOCATE

/

CREATE TABLESPACE PTAPP DATAFILE '<drive>:\oradata\<SID>\ptapp.dbf' SIZE⇒

 4M

EXTENT MANAGEMENT LOCAL AUTOALLOCATE

/

Task 6A-1-8: Creating Target Directory Paths (Multitenant Architecture)

In addition to the directory structure discussed in the previous section, if you are creating a PDB, you must add the following target directories, where <SID> refers to the ORACLE_SID for the CDB, and

<PDB_SERVICE_NAME> refers to the PDB database name.

<drive>:\oradata\<SID>\pdbseed

<drive>:\oradata\<SID>\logs

<drive>:\oradata\<SID>\<PDB_SERVICE_NAME>

Task 6A-1-9: Setting the ORACLE_SID Environment Variable

Make sure that you have the ORACLE_SID parameter set in your user or system environment variables.

Note. If you are creating pluggable databases, set ORACLE_SID to <SID> for the CDB (root database).

For example (the navigation may vary depending upon the operating system):

1. Select Start, Control Panel, System and Security, System on Microsoft Windows 7.

Click the Start button, then Control Panel, System and Security, System, on Microsoft Windows 8 or 2012 R2.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

169

Creating a Database Manually on Windows

Chapter 6A

2. Select Advanced system settings.

3. On the System Properties dialog box, select the Advanced tab.

4. Click Environment Variables.

Verify that the ORACLE_SID variable is set correctly.

This example shows the Environment Variables dialog box with the variable ORACLE_SID and value FDMO.

Setting the ORACLE_SID environment variable

Task 6A-2: Creating the Windows Service for the Database

Instance

Before running the CREATEDB.SQL script and all other scripts needed to create a database, you must first create a Microsoft Windows service. This is necessary because creating an instance on Windows requires creating a

SERVICE using the Oracle

ORADIM

command to add a Microsoft Windows service. On UNIX, an Oracle SID is comprised of many different processes. On Microsoft Windows operating systems, an Oracle SID is run as a single Windows service and you need to be an administrator to create that service. You must also be part of the

ORA_DBA group.

To create a Windows service:

1. Log on to your database server using an ID that is both a Server Administrator and part of the ORA_DBA administrative group.

2. To create the Windows service, open up a command prompt window.

3. Set the ORACLE_SID value to the Oracle database SID you are going to create, <SID> in this example:

170

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6A

Creating a Database Manually on Windows

Set ORACLE_SID=<SID>

4. If you choose to use an Oracle Password file, you need to create one using the ORAPWD utility, as illustrated in this example:

Set ORACLE_SID=<SID> orapwd file=%ORACLE_HOME%\database\pwdtemp2.ora password=manager⇒

 entries=5

Note. If you choose not to use an Oracle Password file, don't forget to comment out or remove the following parameter in the init.ora file: remote_login_passwordfile=EXCLUSIVE

5. Use the ORADIM utility as directed in the following example to create the Windows Oracle Service associated with the SID you are creating: oradim -new -sid <SID> -intpwd manager -startmode auto -pfile %ORACLE_HOME%⇒ \database\init<SID>.ora

Task 6A-3: Using SQL Tools

When you execute PeopleSoft SQL scripts, use the appropriate tool included with your version of the RDBMS.

You should use SQL*Plus, which is available with each version of the Oracle RDBMS that is supported by

Oracle for PeopleSoft installations.

There are various ways to connect to the database with SQL*Plus. For information on using SQL*Plus, see the

Oracle database documentation.

Task 6A-4: Editing Database Scripts (non-Multitenant)

This section discusses:

• Understanding Database Scripts

• Modifying Database Scripts

Understanding Database Scripts

The scripts required for creating the database scripts reside in the PS_HOME\scripts\nt directory on the file server. You need to edit a few of these scripts for your environment before you execute them and go on with the following procedures.

Typically, you need to modify the file system locations and the Oracle SID name.

Note. If you are creating a PDB, follow the instructions for modifying the database scripts in the section Editing

Database Scripts for CDBs later in this chapter.

Task 6A-4-1: Modifying Database Scripts

To edit required database scripts:

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

171

Creating a Database Manually on Windows

Chapter 6A

EB

HC

PA

PT

CR

LM

PF

EP

EA

1. Go to the PS_HOME\scripts\nt directory on the file server.

2. Edit the scripts to conform to your environment.

The following list presents the necessary scripts:

• CREATEDB.SQL

Edit CREATEDB.SQL to remove the REMARK from the following line:

REMARK startup nomount pfile=%ORACLE_HOME%\dbs\init<SID>.ora

Note. When editing CREATEDB.SQL, if you are creating a Unicode database, you need to choose an

Oracle character set supported by the PeopleSoft software. Ensure that the CHARACTER SET parameter in the CREATE DATABASE statement is set to either AL32UTF8 or UTF8.

• CONNECT.SQL.

Edit CONNECT.SQL only if you do not wish to use the default CONNECT_ID.

• UTLSPACE.SQL.

XXDDL.SQL, where XX is a two-letter code for your product line or PeopleSoft PeopleTools, as listed in the table below

Code

CS

Description

PeopleSoft Campus Solutions

PeopleSoft Customer Relationship Management

PeopleSoft Enterprise Learning Management

PeopleSoft Enterprise Performance Management

PeopleSoft Financials / Supply Chain Management

PeopleSoft Financials / Supply Chain Management

Argentina

PeopleSoft Financials / Supply Chain Management Brazil

PeopleSoft Human Capital Management

PeopleSoft Portal Solutions

PeopleSoft PeopleTools

Note. This is a complete list of available product lines for PeopleSoft PeopleTools 8.55. Note that not all products go out on all PeopleSoft PeopleTools releases, so you may not see a script corresponding to every product line. In addition, some bolt-on products reference their own scripts within their application installation documentation.

Search My Oracle Support to confirm that the product is supported for a specific release and database platform.

See My Oracle Support, Certifications.

172

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6A

Creating a Database Manually on Windows

Note. Compare the sizes of the PeopleTools tablespaces in XXDDL.SQL with the tablespaces in PTDDL.SQL. If the tablespace sizes in PTDDL.SQL are larger, increase the PeopleTools tablespace sizes in XXDDL.SQL to be at least as large as those in PTDDL.SQL.

Note. For multilanguage installs, you need to increase the size of the PTTBL, PSIMAGE, and PSINDEX tablespaces. Refer to the comments in the DDL scripts for further details regarding the incremental increase for each additional language.

See Also

"Using the PeopleSoft Installer"

Task 6A-5: Creating an Oracle Instance (non-Multitenant)

Run the CREATEDB.SQL script from SQL*Plus to create an Oracle database.

To create an Oracle database:

1. Invoke SQL*PLUS (sqlplus), connecting as sysdba.

sqlplus / as sysdba

2. Run the CREATEDB.SQL script, using the following example as a guide: sqlplus>@<PS_HOME>\scripts\nt\createdb.sql

Note. When editing CREATEDB.SQL, if you are creating a Unicode database, you need to choose an Oracle character set that is supported by Oracle. Ensure that the CHARACTER SET parameter in the CREATE

DATABASE statement is set to AL32UTF8 or UTF8.

Task 6A-6: Creating Catalog Views and Utility Tablespaces (non-

Multitenant)

Run the UTLSPACE.SQL script from SQL*Plus to create catalog views and utility tablespaces, as follows:

1. Invoke SQL*Plus (sqlplus), connecting as sysdba.

2. Run the UTLSPACE.SQL script:

 sqlplus>@<PS_HOME>\scripts\nt\utlspace.sql

Task 6A-7: Creating PS.PSDBOWNER Table (non-Multitenant)

Run the DBOWNER.SQL script from SQL*Plus to create the PS.PSDBOWNER table, as follows:

1. Invoke SQL*Plus (sqlplus), connecting as sysdba.

2. Run the DBOWNER.SQL script, using the following example as a guide: sqlplus>@<PS_HOME>\scripts\nt\dbowner.sql

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

173

Creating a Database Manually on Windows

Chapter 6A

Task 6A-8: Creating Application-Specific Dbspaces and

Tablespaces (non-Multitenant)

To create tablespaces for the product you are installing, run the appropriate XXDDL.SQL scripts, logged on as the system user, where XX stands for your product line or PeopleSoft PeopleTools, as listed in the table in the section

Editing Database Scripts.

To create application-specific tablespaces:

1. Invoke SQL*Plus (sqlplus), connecting as sysdba.

2. Run the appropriate DDL scripts.

For example: sqlplus>@<PS_HOME>\scripts\nt\epddl.sql

Task 6A-9: Creating PeopleSoft Database Roles (non-Multitenant)

Run the PSROLES.SQL script from SQL*Plus to create the PeopleSoft database roles, as follows:

1. Log on to SQL*Plus, connecting as sysdba.

sqlplus / as sysdba

2. Run the PSROLES.SQL script: sqlplus>@<PS_HOME>\scripts\nt\psroles.sql

Task 6A-10: Creating the PeopleSoft Database Owner ID (non-

Multitenant)

This task creates the PeopleSoft database owner ID that will be referenced in future tasks. It grants the roles, created in the previous step, to this owner ID.

Note. You must run the PSADMIN.SQL script for each PeopleSoft database that you are going to create. When prompted for a default tablespace name, select PSDEFAULT if you are using PeopleSoft naming conventions, or your site equivalent if you are not using PeopleSoft naming conventions.

To create the PeopleSoft database owner ID:

1. Log on to SQL*Plus, connecting as the System user.

sqlplus system/manager

2. Run the PSADMIN.SQL script.

SQLPLUS>@<PS_HOME>\scripts\nt\psadmin.sql

3. Supply values for Access ID, Access ID password, and the default tablespace name when prompted.

Note. The password for Access ID must be between 6 and 30 characters.

174

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6A

Creating a Database Manually on Windows

Task 6A-11: Setting Up Connect ID (non-Multitenant)

This section discusses:

• Understanding Connect ID

• Understanding Connect ID and the Login Process

• Creating the Connect ID

Understanding Connect ID

With the current PeopleSoft PeopleTools release, you establish connections to a database simply by using the connect ID, which allows you to associate multiple PeopleSoft operators to the same connect ID. The connect ID has the minimum privileges required to connect to the database—that is, it has only SELECT privileges on specific PeopleTools tables. After connection, PeopleSoft Security uses the operator ID to control access to objects in the database. The PeopleSoft sign-on process validates the connect ID on the server, rather than the operator ID. Connect ID simplifies database security maintenance. You don't have to maintain access for all

PeopleSoft users, just for the connect ID.

The connect ID is granted access using the following script:

Connect.sql: Creates the connect ID and grants CREATE SESSION privilege to the connect ID. Access to the

PeopleSoft database is then granted to the connect ID explicitly via the initial Data Mover load script generated by DBSETUP to include the following grants.

grant select on PSSTATUS to <CONNECT_ID>; grant select on PSOPRDEFN to <CONNECT_ID>; grant select on PSACCESSPRFL to <CONNECT_ID>; grant select on PSACCESSPROFILE to <CONNECT_ID>;

In order to work, the connect ID and connect password must be specified at the client Configuration Manager or the configuration file of any two-tier client accessing the application.

Understanding Connect ID and the Login Process

When logging into a PeopleSoft database in two-tier mode, the user enters a Database Name, User ID, and

Password in the PeopleSoft Signon dialog box. This table lists the steps and related database SQL operations associated with logging in.

Log-in Processing Steps

The access to the PeopleSoft Database is established with the Connect ID not the User ID.

Related Database SQL Operations

Connect=PT84/<ConnectID>/<ConnectIDPassword>

Check PSSTATUS

Validate the User ID and Password

SELECT OWNERID, TOOLSREL,

LASTREFRESHDTTM, LASTCHANGEDTTM FROM

PSSTATUS

SELECT VERSION, OPERPSWD, ENCRYPTED,

SYMBOLICID, ACCTLOCK FROM PSOPRDEFN

WHERE OPRID =:1

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

175

Creating a Database Manually on Windows

Chapter 6A

Log-in Processing Steps

Get the Access ID and Password

Disconnect Connect ID

Login using the Access ID

Related Database SQL Operations

SELECT ACCESSID, ACCESSPSWD, ENCRYPTED

FROM PSACCESSPROFILE WHERE SYMBOLICID =:1

Disconnect

Connect=PT84/ACCESSID/ACCESSPWD

At this point, access is governed by PeopleSoft security, which determines what applications a specific user ID has access to.

Task 6A-11-1: Creating the Connect ID

To create connect ID:

1. Log on to SQL*Plus as the System user.

2. Run the connect.sql script.

sqlplus>@<PS_HOME>\scripts\nt\connect.sql

3. Supply values for the connect ID and connect ID password when prompted.

The connect ID password must be between 6 and 30 characters.

4. The script will then create the connect ID and grant it CREATE Session privileges only.

Task 6A-12: Editing Database Scripts (Multitenant Architecture)

Edit the scripts listed in this section for your environment before you execute them and continue with the procedure to create a database. You can locate the XXDDL.SQL scripts in the PS_HOME\scripts\nt directory on the file server. The remainder of the scripts listed here reside in the PS_HOME\scripts\nt\pdb directory on the file server.

• CONNECT.SQL

No changes are required.

• CREATEDBCDB.SQL

• Replace the <SID> variable with ORACLE_SID, that is, the CDB database name.

• Replace the <drive> variable with the Microsoft Windows drive letter, for example C or D.

Note. When editing CREATEDBCDB.SQL, if you are creating a Unicode database, you need to choose an Oracle character set supported by the PeopleSoft software. Ensure that the CHARACTER SET parameter in the

CREATE DATABASE statement is set to AL32UTF8.

• CREATEPDB.SQL

• Replace the <SID> variable with ORACLE_SID, that is, the CDB database name.

• Replace the <PDB_SERVICE_NAME> variable with the PDB database name.

• Replace the <drive> variable with the Microsoft Windows drive letter, for example C or D.

• DBOWNER.SQL

176

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6A

Creating a Database Manually on Windows

• Replace the <MANAGERPWD> variable with the System user password.

• Replace the <PDB_SERVICE_NAME> variable with the PDB database name.

• PSADMIN.SQL

• Replace the <MANAGERPWD> variable with the System user password.

• Replace the <PDB_SERVICE_NAME> variable with the PDB database name.

• PSROLES.SQL

No changes are required.

• PSROLES2.SQL

Replace the <PDB_SERVICE_NAME> variable with the PDB database name.

• PTDDL.SQL

• Replace the <SID> variable with ORACLE_SID, that is, the CDB database name.

• Replace the <PDB_SERVICE_NAME> variable with the PDB database name.

• Replace the <drive> variable with the Microsoft Windows drive letter, for example C or D.

• Remove the REMARK from the line for Autoextend.

• UTLSPACE.SQL

• Replace the <SID> variable with ORACLE_SID, that is, the CDB database name.

• Replace the <PDB_SERVICE_NAME> variable with the PDB database name.

• Replace the <drive> variable with the Microsoft Windows drive letter, for example C or D.

XXDDL.SQL, where XX is a two-letter code for your PeopleSoft Application product line.

See the section Editing Database Scripts for a table listing the codes with the PeopleSoft product lines.

• Replace <SID> with the combined name <SID>/<PDB_SERVICE_NAME>.

In this combined name, specify ORACLE_SID, that is, the CDB database name, for <SID>, and the PDB database name for <PDB_SERVICE_NAME>.

• Replace the <drive> variable with the Microsoft Windows drive letter, for example C or D.

• Remove the REMARK from all the lines for Autoextend.

After you edit the scripts, continue with the steps in this chapter to run these scripts and to run the Data Mover import.

Task 6A-13: Creating an Oracle Instance (Multitenant

Architecture)

This section discusses:

• Creating a Root Container Database

• Creating a PDB

Task 6A-13-1: Creating a Root Container Database

To create a (root container database) CDB for pluggable databases:

1. Invoke SQL*Plus (sqlplus), connecting as sysdba:

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

177

Creating a Database Manually on Windows

Chapter 6A sqlplus / as sysdba

2. Run the createdbcdb.sql script, using the following example as a guide: sqlplus>@<PS_HOME>\scripts\nt\pdb\createdbcdb.sql

3. Exit from SQL*Plus.

4. Open the script ptperlcat.bat for editing, and make the following changes for PDBs:

• Replace the <SID> variable with ORACLE_SID

• Replace the <drive> variable with the Microsoft Windows drive letter.

5. Run the script ptperlcat.bat.

This scripts runs the scripts catalog.sql and catproc.sql.

6. To verify that the database was created successfully, log in to SQL*Plus again and run the following command select name,cdb from v$database;

If the value of CDB is "YES" in the response, it means that the database with ID <SID> (FSDMO855 in this example) can be used as a pluggable database:

NAME      CDB

--------  ---

FSDMO855  YES

Task 6A-13-2: Creating a PDB

To create a PDB:

1. Invoke SQL*Plus (sqlplus), connecting as sysdba: sqlplus / as sysdba

2. Run the createpdb.sql script, using the following example as a guide: sqlplus>@<PS_HOME>\scripts\nt\pdb\createpdb.sql

You should see a message "Pluggable database created".

3. Execute the following command: sqlplus>select name, open_mode from v$pdbs;

The following response indicates that the PDB is open and is ready to use:

NAME                OPEN_MODE

----------------    ---------

PDB$SEED            READ ONLY

PDB_SERVICE_NAME    READ WRITE

The PDB_SERVICE_NAME is created by the Oracle server for a new PDB.

4. To verify the service name for the PDB, execute the following command: lsnrctl status;

Service "PDB_SERVICE_NAME" has 1 instance(s).

Instance "PDB_SERVICE_NAME", status READY, has 1 handler(s) for this⇒

 service.

178

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6A

Creating a Database Manually on Windows

5. Add an entry for the PDB service name to the tnsnames.ora file.

This example shows a portion of the tnsnames.ora file. Replace <PDB_SERVICE_NAME> with the PDB database name:

<PDB_SERVICE_NAME> =

  (DESCRIPTION =

    (ADDRESS_LIST =

      (ADDRESS = (PROTOCOL = TCP)(HOST = servername.com)(PORT = 1521))

    )

    (CONNECT_DATA =

      (SERVICE_NAME = <PDB_SERVICE_NAME>)

    )

  )

6. Log in to the PDB in SQL*Plus with the following command: sqlplus / as sysdba

SQL> ALTER SESSION SET CONTAINER = <PDB_SERVICE_NAME>

Task 6A-14: Creating Catalog Views and Utility Tablespaces

(Multitenant Architecture)

To create catalog views and utility tablespaces:

1. Invoke SQL*Plus (sqlplus), connecting as sysdba.

sqlplus / as sysdba

2. Run the UTLSPACE.SQL script: sqlplus>@<PS_HOME>\scripts\nt\pdb\utlspace.sql

Task 6A-15: Creating PS.PSDBOWNER Table (Multitenant

Architecture)

Run the DBOWNER.SQL script from SQL*Plus to create the PS.PSDBOWNER table, as follows:

1. Log on to SQL*Plus (sqlplus), connecting as the System user to the PDB.

The PDB name in this example is <PDB_SERVICE_NAME>: sqlplus system/[email protected]<PDB_SERVICE_NAME>

2. Run the DBOWNER.SQL script, using the following example as a guide: sqlplus>@<PS_HOME>\scripts\nt\pdb\dbowner.sql

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

179

Creating a Database Manually on Windows

Chapter 6A

Task 6A-16: Creating Application-Specific Dbspaces and

Tablespaces (Multitenant Architecture)

To create tablespaces for the product you are installing, run the appropriate XXDDL.SQL scripts, logged on as the system user, where XX stands for your product line or PeopleSoft PeopleTools, as listed in the table in the section

Editing Database Scripts (Multitenant Architecture).

To create application-specific tablespaces:

1. Log on to SQL*Plus (sqlplus), connecting as the System user to the PDB.

The PDB name in this example is <PDB_SERVICE_NAME>: sqlplus system/[email protected]<PDB_SERVICE_NAME>

2. Run the appropriate DDL scripts.

For example, for PeopleSoft Financials/Supply Chain Management: sqlplus>@<PS_HOME>\scripts\nt\epddl.sql

Task 6A-17: Creating PeopleSoft Database Roles (Multitenant

Architecture)

To create the roles for your PeopleSoft database:

1. Log on to SQL*Plus, connecting as the System user to the PDB.

The PDB name in this example is <PDB_SERVICE_NAME>: sqlplus system/[email protected]<PDB_SERVICE_NAME>

2. Run the PSROLES.SQL script: sqlplus>@<PS_HOME>\scripts\nt\pdb\psroles.sql

3. Log out of SQL*Plus.

4. Log on to SQL*Plus, connecting as sysdba.

sqlplus / as sysdba

5. Run the PSROLES2.SQL script: sqlplus>@<PS_HOME>\scripts\nt\pdb\psroles2.sql

Task 6A-18: Creating the PeopleSoft Database Owner ID

(Multitenant Architecture)

This task creates the PeopleSoft database owner ID that will be referenced in future tasks. It grants the roles, created in the previous step, to this owner ID.

180

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6A

Creating a Database Manually on Windows

Note. You must run the PSADMIN.SQL script for each pluggable database that you are going to create. When prompted for a default tablespace name, select PSDEFAULT if you are using PeopleSoft naming conventions, or your site equivalent if you are not using PeopleSoft naming conventions.

To create the PeopleSoft database owner ID:

1. Log on to SQL*Plus, connecting as the System user to the PDB.

The PDB name in this example is <PDB_SERVICE_NAME>. sqlplus system/[email protected]<PDB_SERVICE_NAME>

2. Run the PSADMIN.SQL script.

sqlplus>@<PS_HOME>\scripts\nt\pdb\psadmin.sql

3. Supply values for Access ID, Access ID password, and the default tablespace name when prompted.

Note. The password for Access ID must be between 6 and 30 characters.

Task 6A-19: Setting Up Connect ID (Multitenant Architecture)

This section discusses:

• Understanding Connect ID

• Understanding Connect ID and the Login Process

• Creating the Connect ID

Understanding Connect ID

With the current release of PeopleSoft PeopleTools, you establish connections to a database simply by using the connect ID, which allows you to associate multiple PeopleSoft operators to the same connect ID. The connect ID has the minimum privileges required to connect to the database—that is, it has only SELECT privileges on specific PeopleTools tables. After connection, PeopleSoft Security uses the operator ID to control access to objects in the database. The PeopleSoft sign-on process validates the connect ID on the server, rather than the operator ID. Connect ID simplifies database security maintenance. You do not have to maintain access for all

PeopleSoft users, just for the connect ID.

The connect ID is granted access using the Connect.sql script. This script creates the connect ID and grants

CREATE SESSION privilege to the connect ID. Access to the PeopleSoft database is then granted to the connect

ID explicitly through the initial Data Mover load script generated by DBSETUP to include the following grants.

grant select on PSSTATUS to <CONNECT_ID>; grant select on PSOPRDEFN to <CONNECT_ID>; grant select on PSACCESSPRFL to <CONNECT_ID>; grant select on PSACCESSPROFILE to <CONNECT_ID>;

In order to work, the connect ID and connect password must be specified at the client Configuration Manager or the configuration file of any two-tier client accessing the application.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

181

Creating a Database Manually on Windows

Chapter 6A

Understanding Connect ID and the Login Process

When logging into a PeopleSoft database in two-tier mode, the user enters a Database Name, User ID, and

Password in the PeopleSoft Signon dialog box. This table lists the steps and related database SQL operations associated with logging in.

Log-in Processing Steps

The access to the PeopleSoft Database is established with the Connect ID not the User ID.

Related Database SQL Operations

Connect=PT84/<ConnectID>/<ConnectIDPassword>

Check PSSTATUS

Validate the User ID and Password

SELECT OWNERID, TOOLSREL,

LASTREFRESHDTTM, LASTCHANGEDTTM FROM

PSSTATUS

SELECT VERSION, OPERPSWD, ENCRYPTED,

SYMBOLICID, ACCTLOCK FROM PSOPRDEFN

WHERE OPRID =:1

Get the Access ID and Password

Disconnect Connect ID

Login using the Access ID

SELECT ACCESSID, ACCESSPSWD, ENCRYPTED

FROM PSACCESSPROFILE WHERE SYMBOLICID =:1

Disconnect

Connect=PT84/ACCESSID/ACCESSPWD

At this point, access is governed by PeopleSoft security, which determines what applications a specific user ID has access to.

Task 6A-19-1: Creating the Connect ID

To create connect ID:

1. Log on to SQL*Plus as the System user to the PDB.

The PDB name in this example is <PDB_SERVICE_NAME>. sqlplus system/[email protected]<PDB_SERVICE_NAME>

2. Run the connect.sql script.

sqlplus>@<PS_HOME>\scripts\nt\pdb\connect.sql

3. Supply values for the connect ID and connect ID password when prompted.

The connect ID password must be between 6 and 30 characters.

4. The script will then create the connect ID and grant it CREATE Session privileges only.

Task 6A-20: Updating Connection Information

You must update connection information on the client. To do this, update the connection information in

TNSNAMES.ORA on your client to reflect your Database Name, Oracle SID, and Server Name.

182

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6A

Creating a Database Manually on Windows

Note. If you are creating pluggable databases, create an entry for the CDB, using the SID. Create another entry for the PDB, using the PDB_SERVICE_NAME.

Task 6A-21: Setting NLS_LANG in the Windows Registry

You must set the NLS_LANG Oracle registry key to indicate the Oracle language and character set. The

PeopleSoft Application Server and reporting tools run in Unicode regardless of the database character set or the

NLS_LANG character set component. However, the NLS_LANG character set component does affect the transmission of data in non-PeopleTools connections, such as SQL*Plus and direct COBOL. NLS_LANG has three components, a language, a territory, and a character set in the form

LANGUAGE_TERRITORY.CHARACTERSET. For example, for American English, the correct NLS_LANG setting for a PeopleSoft installation would be AMERICAN_AMERICA.AL32UTF8. See the Oracle National

Language Support guide for full details.

The NLS_LANG parameter should be set on each workstation you use to access the PeopleSoft application in two-tier mode, and on your application server machine.

Note. When using SQL*Plus to query data, set NLS_LANG on the client side to match the OS character set rather than the database character set.

To set NLS_LANG in the Windows registry:

1. Open the Windows Registry Editor by selecting Run from the Microsoft Windows Start menu.

2. Type REGEDIT in the Run dialog.

3. Navigate to the key HKEY_LOCAL_MACHINE\Software\Oracle.

Navigating to NLS_LANG

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

183

Creating a Database Manually on Windows

4. Double-click on the NLS_LANG key in the right hand side of the window.

The Edit String dialog box appears as in this example.

Chapter 6A

Entering the Value data

5. Enter <language>_<territory>.AL32UTF8 in the Value Data field, substituting <language> and <territory> for your preferred language and territory settings.

If unsure, use AMERICAN_AMERICA.AL32UTF8.

6. Click OK and close the Registry Editor.

Task 6A-22: Creating Data Mover Import Scripts

This section discusses:

• Understanding Data Mover Import Scripts

• Working with Multilingual Databases

• Running Database Setup to Create Data Mover Import Scripts

Understanding Data Mover Import Scripts

The Data Mover Import scripts are used to populate the PeopleSoft database with data. You use the Database

Setup feature of the PeopleSoft Data Mover utility to create the Data Mover import scripts.

Note. This task and the next one (Running Data Mover Import Scripts) should be executed from a Microsoft

Windows client machine. Before you can load PeopleSoft data from a Microsoft Windows client machine, you need to install PeopleSoft PeopleTools and your PeopleSoft Application to the Microsoft Windows client machine and be sure to select File Server and Database Server.

To complete the database creation procedure you must supply information on various authorization IDs and passwords, including Access ID, Connect ID, Symbolic ID, and User IDs. Before beginning this procedure, review the information in the section Planning Database Creation and make a note of the authorization information for your environment. For PeopleSoft PeopleTools 8.53 and later releases, the user profiles in

PeopleTools demo databases are delivered disabled. During the procedure to create Data Mover import scripts you will choose whether to enable the delivered user profiles, and how to assign passwords for the profiles. In addition, you will supply several passwords that were previously provided as defaults. Be sure to note the passwords that you supply, as they will be needed for subsequent installation procedures.

See the information on administering user profiles in the PeopleTools: Security Administration product documentation.

See "Preparing for Installation," Planning Database Creation.

184

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6A

Creating a Database Manually on Windows

Task 6A-22-1: Working with Multilingual Databases

All PeopleSoft releases are shipped with English as the database's base language. Therefore when selecting components for the Data Mover Import script, you must select the English components in addition to any other languages you have licensed. After the installation is complete, you can change the database's base language to the language that you plan to use most frequently, or leave the base language as English.

Read the section Planning Multilingual Strategy for information on installing multiple languages and changing your base language.

See "Preparing for Installation," Planning Multilingual Strategy.

If you are creating a database and want to load Oracle-provided translations for non-English languages, you must load English (ENG) in addition to the foreign language components.

If you are creating a non-Unicode database, you must ensure that the languages you select are all supported by the character set you used to create your database.

Note. During the database setup process, you have the option to select the database's base language. Select the language that you plan to use most frequently. If the database's base language is different than that set in this database setup process, generate the SWAP_BASE_LANGUAGE command in the Data Mover Import script to swap the language.

See PeopleTools: Global Technology.

Task 6A-22-2: Running Database Setup to Create Data Mover Import Scripts

To create the import scripts using Data Mover:

See PeopleTools: Data Management.

1. Run Configuration Manager by using one of the following methods:

• On Microsoft Windows 7, select Start, Programs, PeopleTools 8.55, Configuration Manager.

• On Microsoft Windows 8 or 2012 R2, access the Apps screen and navigate to PeopleTools 8.55,

Configuration Manager.

• Run PS_HOME\bin\client\winx86\pscfg.exe.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

185

Creating a Database Manually on Windows

Chapter 6A

2. Verify in the Signon Defaults on the Startup page that the Database Type of Oracle is selected, as shown in the example.

Startup tab on the Configuration Manager dialog box

3. Verify that the connect ID is correct.

If you accepted all defaults, the connect ID is people. Enter and confirm a value for the connect ID password.

4. If the PS_APP_HOME location is not the same as PS_HOME, make sure it is set in Configuration Manager, as follows: a. In Configuration Manager, select Profile.

b. Highlight the Default Profile and select Edit.

c. On the Edit Profile dialog box, select the Process Scheduler tab.

d. Verify that the PS_APP_HOME value is correct.

See "Setting Up the Install Workstation," Editing the Default Profile.

5. Run Data Mover by using one of these methods:

• On Microsoft Windows 7, select Start, Programs, PeopleTools 8.55, Data Mover.

186

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6A

Creating a Database Manually on Windows

• On Microsoft Windows 8 or 2012 R2, access the Apps screen and navigate to PeopleTools 8.55, Data

Mover.

• Run PS_HOME\bin\client\winx86\psdmt.exe.

6. Log on using the access ID as the user id to start Data Mover in bootstrap mode; this should be the user that creates the database.

See Checking the Log Files and Troubleshooting, Running Data Mover.

Note. You must limit the access ID to eight characters or less. You must limit the access password to 30 characters or less.

7. Select File, Database Setup.

The Database Setup dialog box appears, as shown in this example:

Selecting target database and character set on the Database Setup dialog box

8. Select your database platform from the Select Target Database drop-down list.

9. Select your database type, Unicode or non-Unicode, and character set.

Choose the Database Type

—Unicode or Non-Unicode—that you selected in the section on multilingual

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

187

Creating a Database Manually on Windows

Chapter 6A strategy. If you choose Non-Unicode, select the character set that you decided upon in that section from the drop-down list.

Note. When you select a non-Unicode character set, only the characters within that character set can be stored in your database. Oracle recommends that you create your database using Unicode.

See "Preparing for Installation," Planning Multilingual Strategy.

The character set you select here must match the character set you used to create your database in the task

Creating an Oracle Database. If you choose to create a Unicode database, you must have created your instance using the AL32UTF8 or UTF8 character set in the step Creating an Oracle Instance.

Note. The database setup does not actually modify the character set of your database. That is done by the

DBA during database creation. The database setup process only creates customized scripts based on your selection.

10. Select the Demo or System radio button, depending on which type of PeopleSoft database you are installing.

Selecting a PeopleSoft application in the Database Setup dialog box

11. Select the Products for which you want to create a Data Mover script from the PeopleSoft Application list box, and move the items you have selected into the Data Mover Scripts to Create list box by clicking on the

Add or Add All button.

If you installed the Multilanguage software, each application will be listed several times, once for each language. If you are installing languages other than English, make sure to select the appropriate language data files for each application you select in English. This will load the translated database objects.

See "Preparing for Installation," Planning Multilingual Strategy.

If you are installing an application in any language other than English, you must also select the English component of the application. For example, if you select PeopleSoft Fin/SCM - French, you must also select

PeopleSoft Fin/SCM Database - US English. This ensures that you install the necessary base-language

188

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6A components.

Creating a Database Manually on Windows

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

189

Creating a Database Manually on Windows

12. Set the database parameters described below and then click Finish.

Chapter 6A

Specifying Database Parameters on the Database Setup dialog box

190

Database Name: Specify the database name that users will enter on the PeopleSoft signon screen. This corresponds to the owner ID. It can be up to eight characters long and must be entered in uppercase.

Symbolic ID: This is used as the key to retrieve ACCESSID and ACCESSPSWD from

PSACCESSPROFILE.

For initial installation set it equal to the Database Name. The symbolic ID cannot be longer than eight characters.

Access ID: Specify the user you used to create the database. Limit this to eight characters or less.

This value is case sensitive. You will use the access ID every time you want to sign on to Data Mover in bootstrap mode. Limit this to eight characters or less.

Access Password: This is the PeopleSoft access ID password defined in the chapter "Preparing for

Installation." Limit this to 30 characters or less.

Connect ID: For Oracle, this is the connect ID that is used for the initial connection to Oracle. This ID is used for connecting to the database. Limit this to eight characters or less.

Application Server ID: The Application Server ID has privileges to start or shut down the Application

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6A

Creating a Database Manually on Windows

Server domain. It is also used during the Application Server configuration. Enter one of the delivered

PeopleSoft user IDs.

Application Server Password: Specify a password for the Application Server ID.

Web Server Password: Specify a password for the Web Server ID.

The default Web Server ID, as displayed in the example, is PTWEBSERVER. The Web Server ID, also referred to in this documentation as Web Profile User ID, is used to access the web profile information from the database through the Application Server Jolt service.

Enable All Profiles: Select this option to leave the User profiles (other than the Application Server profile and the Web Server User profiles) unchanged.

If you do not select this option, all of the User profiles in the database, with the exception of the

Application Server profile and Web Server User profiles, remain disabled as delivered.

Set Global Password: If you enabled all profiles, you can choose to set the same password for all of the profiles.

Note. This option is enabled when the Enable All Profiles option is selected, as shown in the example.

Global Password: Enter the password to be used for all user profiles.

Note. This option is enabled when the Set Global Password option is selected, as shown in the example.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

191

Creating a Database Manually on Windows

Chapter 6A

13. Select your database's base language.

Note. This window appears only if you selected a database for a language other than English. If you see this window it is critical to select the correct base language. When you select a base language other than ENG,

DBSETUP generates the Data Mover import script with the SWAP_BASE_LANGUAGE command to swap the base language.

See "Preparing for Installation," Planning Multilingual Strategy.

See Working with Multilingual Databases.

192

Selecting a base language in the Database Setup dialog box

Use the following information in making your selection:

• If you have not already done so, read the earlier section on multilingual strategy before determining whether to install multiple languages and whether to change your base language.

• If you are creating a database and want to load Oracle-provided translations for non-English languages, you must load English (ENG) in addition to the foreign language components.

• All PeopleSoft releases are shipped with English as the database's base language. Therefore when selecting components for the Data Mover Import script, you must select the English components in addition to any other languages you have licensed. During the Database Setup wizard, you need to select the database's base language that you plan to use most frequently. If your database's base language is different than the Database Setup wizard generate the SWAP_BASE_LANGUAGE command in the Data

Mover Import script to swap the language.

• If you are creating a non-Unicode database, you must ensure that the languages you select are all

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6A

Creating a Database Manually on Windows

supported by the character set you used to create your database.

14. Click Finish.

Note. If the Database Setup - Base Language window does not appear, click Finish after supplying the parameters on the Database Setup - Database Parameters window.

At this point you are in Data Mover, with the DMS script you just created ready to run.

See Also

PeopleTools: Data Management

PeopleTools: Security Administration, "PeopleSoft Authorization IDs"

Task 6A-23: Running Data Mover Import Scripts

This section discusses:

• Understanding Data Mover Import Scripts

• Populating Tables in the PeopleSoft Database

Understanding Data Mover Import Scripts

Now you will run the Data Mover scripts (DMS) that you created in the preceding task to import the data for your

PeopleSoft database. The Data Mover script creates either a system (SYS) or a demo (DMO) database.

When you initially logged onto Data Mover to create the DMS scripts, you logged in with the Access ID and password, using bootstrap mode. You need to use bootstrap mode to run the Data Mover import script, because there are not yet any PeopleSoft security tables in the database.

When you start Data Mover in bootstrap mode, the word "BootStrap" appears in the Data Mover status bar.

See PeopleTools: Data Management.

See Also

Checking the Log Files and Troubleshooting, Running Data Mover

Task 6A-23-1: Populating Tables in the PeopleSoft Database

To populate tables in the PeopleSoft database:

1. The DMS import script for your application will contain hard-coded file names for log files and data files.

Modify the DMS script if you have moved any files from the delivered directories or want to write log files to another location than that specified in the script.

2. Select File, Run to execute the script.

When you run the script, Data Mover typically performs the following actions:

• IMPORT *

Create all the PeopleTools and application tables with their indexes.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

193

Creating a Database Manually on Windows

• ENCRYPT_PASSWORD *

Encrypt security information for the database.

• CREATE_TRIGGER *

Create application required triggers.

• REPLACE_VIEW *

Create PeopleSoft views.

• CREATE_TEMP_TABLE *

Create PeopleSoft temporary tables.

Chapter 6A

Task 6A-24: Checking the Log Files and Troubleshooting

This section discusses:

• Checking the Log Files

• Running Data Mover

• Troubleshooting

• Improving Performance

Task 6A-24-1: Checking the Log Files

After running each Data Mover script, examine the .LOG files to make sure that all the commands were executed successfully. The log files are located in the directory you specified in the Data Mover script.

See "Setting Up the Install Workstation," Editing the Default Profile.

Task 6A-24-2: Running Data Mover

Use one of these methods to run Data Mover.

Microsoft Windows

• On Microsoft Windows 7, select Start, Programs, PeopleTools 8.55, Data Mover, to run a graphical user interface (GUI mode).

• On Microsoft Windows 8 or 2012 R2, access the Apps screen, and navigate to PeopleTools 8.55, Data Mover to run in GUI mode.

• Run PS_HOME\bin\client\winx86\psdmt.exe from the command line.

If you use the access ID that you specified during the database configuration to log on, you log on in "bootstrap mode." When you start Data Mover in bootstrap mode, the word "BootStrap" appears in the Data Mover status bar.

If you use a valid PeopleSoft Operator ID, such as PS for Human Capital Management or VP1 for

Financials/Supply Chain Management, you log on in "user mode." In this mode, no designation appears in the

Data Mover status bar.

See Also

PeopleTools: Data Management

194

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6A

Creating a Database Manually on Windows

Task 6A-24-3: Troubleshooting

If the DMS script has stopped midway (this can happen for a number of reasons) you need to edit the script and start again.

To edit and restart the DMS script:

1. Determine the record that was being imported (that is, which IMPORT command was running) when the script stopped, and use the following guidelines to edit and rerun the DMS scripts.

When building a DMO database or a multilingual database, adding the SET START statement can be tricky because the Data Mover script used to load the database will include more than one IMPORT statement. The key is to view the log files and determine which IMPORT section of the script Data Mover failed on.

• If the failure occurred during the first IMPORT statement, add the SET START statement before the first

IMPORT *; statement.

• If the failure occurred during a subsequent IMPORT statement, comment out all statements preceding the

IMPORT *; statement where the failure occurred and add the SET START statement before the IMPORT

*; statement of the section in which the failure occurred.

This is very important: If you see any "unique index constraint" error messages in the "Building required indexes" section, your IMPORT script failed during a subsequent IMPORT but the SET START statement was added to the first IMPORT. In this situation, you can run the Data Mover script in its originally generated form, with only one modification. In the first IMPORT section, change the statement "IMPORT

*;" to "REPLACE_DATA *;". This will delete all the data in the tables, and re-import it. This process will take some time to run, and you will need to separately create each of the indexes that failed.

2. Run Data Mover as previously described.

See Running Data Mover.

The PeopleSoft Logon dialog box appears.

3. Log on using the Access ID to start Data Mover in bootstrap mode.

Use the Access ID you specified when you created the Data Mover scripts with the Database Setup utility.

The input window should display the DMS import script for the database. The script has the format

<dbname>ora.dms.

4. If necessary, select File, Open, and browse to the PS_HOME/scripts directory to find the appropriate DMS script.

5. Add the following line before the offending IMPORT command (the one being executed when the failure occurred):

SET START <RECORD NAME>;

<RECORD NAME> is the name of the record that failed. Make sure to review the Data Mover log file to see where the script failed and locate the last record that imported successfully. The SET START command will begin the Data Mover import at the specified record name.

Note. It is a good idea to change the name of the log file in the script before each attempt at running it. This ensures that you have a separate log file for each attempt, if you run the import more than once.

For example, if the script stops and the table is partially inserted with a message similar to this one:

Importing  PSPNLFIELD

Rows inserted into PSPNLFIELD

3000

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

195

Creating a Database Manually on Windows

Chapter 6A

First drop the partially inserted table (for example, record) by using the DROP TABLE command, and then restart Data Mover at the record that failed using the SET START command and continue the Data Mover import. This can be done in a single pass.

Add the following lines before the offending IMPORT *; command (the one being executed when the failure occurred):

SET START <RECORD NAME>;

DROP TABLE <RECORD NAME>; where <RECORD NAME> is the name of the record that failed. The SET START statement will begin the

Data Mover import at the specified <RECORD NAME>.

Example of the original script:

REM - PeopleTools System Database - US English

/

SET LOG ptengs.log;

SET INPUT ptengs.db;

SET COMMIT 30000;

SET NO VIEW;

SET NO SPACE;

SET NO TRACE;

SET UNICODE ON;

IMPORT *;

Example of script after modification, with changes in bold font:

REM - PeopleTools System Database - US English

/

SET LOG ptengs2.log;

SET INPUT ptengs.db;

SET COMMIT 30000;

SET NO VIEW;

SET NO SPACE;

SET NO TRACE;

SET UNICODE ON;

SET START PSPNLFIELD;

DROP TABLE PSPNLFIELD;

IMPORT *;

For the DROP statement, for records with a recname without a leading PS, add PS_ to the beginning of the recname; otherwise the table will not be found. For example, PS_<RECNAME>.

6. Restart the script (File, Run Script).

See Also

"Using the PeopleSoft Installer," Verifying Necessary Files for Installation on Windows.

Task 6A-24-4: Improving Performance

The following tips can help you save time when running the Data Mover scripts:

• Run Data Mover from the fastest workstation available.

• Run Data Mover on the database server.

196

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6A

Creating a Database Manually on Windows

• Run only a single instance of Data Mover, and do not have any other applications running during the import.

• In the PeopleSoft Configuration Manager, turn off all trace options.

Tracing during a DMS load will add considerable time to the process.

• Copy the database file over to the workstation so that Data Mover can access it locally instead of over the network.

• Run Data Mover on the database server with the .db or .dat file located locally.

If you are comfortable changing the options available for an Oracle instance, you might consider "tuning" the instance used for the import. Some of these options are appropriate only during the import, so you may not want to keep them in effect after the import is complete.

For best performance during a Data Mover import, set these options as follows:

• Increase the number of database blocks.

• Use an 8K Oracle block size.

• Use very large rollback segments.

• Increase the size of the UNDO tablespace or the number of UNDO Segments.

• Use asynchronous read and write.

• Use multiple db_writers.

Task 6A-25: Changing the Base Language

The information in the earlier task Planning Multilingual Strategy will help you determine whether you should change your base language, and lists the currently supported languages.

See "Preparing for Installation," Planning Multilingual Strategy.

See PeopleTools Certifications — Supported Languages, My Oracle Support (search for article name).

This task applies only if your users will be operating PeopleSoft applications primarily in one particular language other than English. It gives a performance boost to the language you designate as the base language, but requires more administrative overhead than leaving English as the base language. The details are spelled out in the

PeopleTools: Global Technology product documentation.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

197

Chapter 6B

Creating a Database on UNIX

This chapter discusses:

• Understanding the Database Configuration Wizard

• Fulfilling PeopleSoft Database Configuration Wizard Prerequisites

• Running the Database Configuration Wizard

• Checking the Log Files and Troubleshooting

Understanding the Database Configuration Wizard

The Database Configuration Wizard is a tool designed to simplify your PeopleSoft database installation. When you run the Database Configuration Wizard, Data Mover is also running silently.

See PeopleTools: Data Management.

Important! Do not forget that application-specific installation steps are provided in a separate document specific to the application. For instance, if you are performing PeopleSoft CRM installation, you need both this PeopleSoft

PeopleTools installation guide and you also need any additional instructions provided by CRM. My Oracle

Support provides installation guides that are specific to your application.

See My Oracle Support, (search for "installation," the application name, and release).

This section includes information on creating an Oracle Container Database (CDB) and Pluggable Databases

(PDBs). The sections specific to creation of CDBs and PDBs are labelled "(Multitenant Architecture)." Choose whether to create pluggable databases according to the Oracle RDBMS you installed, as follows:

• If you installed the Oracle 12c Enterprise Edition RDBMS, you can choose to create either CDBs or non-

CDBs.

• If you installed Oracle 11gR2 RDBMB, you can create only a non-CDB. For installations on Oracle 11gR2, pluggable databases are not supported.

You also have the option of using a manual process for creating a PeopleSoft database, instead of using the

Database Configuration Wizard. The manual process is mandatory for some configurations.

Important! The Database Configuration Wizard cannot be used for z/Linux. To create a database on that operating system platform, you must use the manual method of creating a database.

Important! The Database Configuration Wizard cannot be used with Oracle RAC. To create a database with this database platform, you must use the manual method of creating a database.

See the information on setting up the PeopleSoft installation with Oracle RAC in the PeopleTools: Data

Management product documentation.

199

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Creating a Database on UNIX

Chapter 6B

Important! The Database Configuration Wizard cannot be used for an Unicode database on an Oracle database version lower than 11g. You must use the manual method of creating a database for this configuration.

See Creating a Database Manually on UNIX.

After you complete the tasks in this chapter, read the chapter "Completing the Database Setup." Depending upon your environment, you may not need to carry out every task in that chapter. However it is important that you evaluate the requirements and perform the necessary tasks.

Task 6B-1: Fulfilling PeopleSoft Database Configuration Wizard

Prerequisites

This section discusses:

• Installing the PeopleSoft Database Server Components on the Database Server

• Installing the Oracle RDBMS Software

• Identifying the Trace and Alert File Locations

• Creating an INIT<SID>.ORA File

• Creating an INIT<SID>.ORA File (Multitenant Architecture)

• Creating Target Directory Paths

• Creating Target Directory Paths (Multitenant Architecture)

• Setting Up Target Database Connectivity

• Running the Shell Script psconfig.sh

Task 6B-1-1: Installing the PeopleSoft Database Server Components on the

Database Server

To run the PeopleSoft Database Configuration Wizard, your setup must fulfill these requirements:

• You must have installed the PeopleSoft PeopleTools software on your database server by running the

PeopleSoft Installer.

• You must have chosen the Database Server option during the PeopleTools software installation.

• You must have installed the Database component of your application installation software to your database server.

• You must have the PeopleTools Development Environment set up to create your database.

• You must have the Oracle Tuxedo software installed before you run the Database Configuration Wizard.

The Database Configuration Wizard invokes the PeopleSoft Data Mover utility. Data Mover on the UNIX platform has a dependency on the Oracle Tuxedo software.

• You must run the Database Configuration Wizard at the database server.

Be sure the UNIX login ID executing the Database Configuration Wizard has sufficient read and write permissions on this server. Ideally the UNIX login ID executing the Database Configuration Wizard is part of the same UNIX group that the Oracle RDBMS owner is part of, usually the DBA group.

See the information on PeopleSoft Configuration Manager in the PeopleTools: System and Server Administration product documentation.

200

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6B

Creating a Database on UNIX

See Also

"Using the PeopleSoft Installer"

"Setting Up the Install Workstation"

Task 6B-1-2: Installing the Oracle RDBMS Software

The Oracle RDBMS software must be installed before you run the Database Configuration Wizard. The following discussion assumes that you are familiar with Oracle administration tasks. During the execution of the Wizard, references are made to an existing Oracle RDBMS installation:

$ORACLE_HOME and $ORACLE_HOME/bin

Note. The PeopleSoft Database Configuration Wizard for the current PeopleSoft PeopleTools release supports

Oracle 11g or Oracle 12c. If you are using the pluggable database functionality, you must install Oracle 12c

Enterprise Edition.

Task 6B-1-3: Identifying the Trace and Alert File Locations

For Oracle 11gR2 and later releases, all diagnostic data, including the alert log, are stored in the Automatic

Diagnostic Repository (ADR), whose location is set by the DIAGNOSTIC_DEST initialization parameter. Due to this change, the initialization parameter settings for background dump (BACKGROUND_DUMP_DEST), core dump (CORE_DUMP_DEST), and user dump (USER_DUMP_DEST) are replaced by the diagnostic destination parameter DIAGNOSTIC_DEST. For information on the DIAGNOSTIC_DEST parameter and the default location for the ADR, see the Oracle RDBMS documentation.

See the information on managing diagnostic data in the Oracle Database Administrator's Guide.

Task 6B-1-4: Creating an INIT<SID>.ORA File

You must create an init.ora with the naming convention of init<SID>.ora in the ORACLE_HOME/dbs directory of your Oracle installation.

Add or modify the following init.ora parameters:

• DB_NAME = <SID>

• DB_FILES

Specify the maximum allowed for your operating system, typically 1021.

• CONTROL_FILES

Specify the control files for your database, such as

/filesystem1/cntrl1<SID>,/filesystem2/cntrl2<SID>

.

• OPEN_CURSORS = 1000

This is a minimum value. You may choose to set this higher.

• DB_BLOCK_SIZE = 8192

PeopleSoft PeopleTools supports Oracle 11g and Oracle 12c. The PeopleSoft scripts are delivered to work across all versions of the Oracle RDBMS that Oracle supports for this release of PeopleSoft PeopleTools.

The Database Configuration Wizard will prompt you for a SID name. This init<SID>.ora will be referenced in the

CREATEDB.SQL script, which is executed by the Database Configuration Wizard.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

201

Creating a Database on UNIX

Chapter 6B

Review the following information and make any necessary edits to these parameters for your environment:

DB_BLOCK_SIZE

For UNIX the default DB_BLOCK_SIZE in the init<SID>.ora file is operating system dependent. On most operating systems the default is 8192 or 8K. For PeopleSoft ANSI databases this is more than adequate. For

PeopleSoft Unicode databases (for example, CHARACTER_SET AL32UTF8), a DB_BLOCK_SIZE value of 8K is required.

NLS_LENGTH_SEMANTICS

Use these guidelines to set the

NLS_LENGTH_SEMANTICS

init<SID>.ora parameter:

• Set

NLS_LENGTH_SEMANTICS=CHAR

if you are installing a Unicode database with PeopleSoft application

9.0 or higher releases on PeopleTools 8.48 or higher.

• Set

NLS_LENGTH_SEMANTICS=BYTE

if you are installing any non-Unicode database (such as a Western

European or Shift-JIS database).

• Set

NLS_LENGTH_SEMANTICS=BYTE

if you are installing a Unicode database with PeopleSoft application prior to release 9.0 on PeopleSoft PeopleTools prior to release 8.48.

If necessary, verify the PeopleTools release for your PeopleSoft application using this SQL query: select TOOLSREL from PSSTATUS

Unicode databases on PeopleSoft PeopleTools 8.48 and later, with PeopleSoft application 9.0 or later use character length semantics. When character length semantics is used, a field of VARCHAR2(10) will store 10 characters. Prior to PeopleSoft PeopleTools 8.48 and PeopleSoft applications 9.0, byte length semantics was used, meaning a VARCHAR2(10) stored 10 bytes. If you are upgrading from a release before PeopleSoft PeopleTools

8.48 and PeopleSoft application 9.0 to one after 8.48 and 9.0, a database conversion is necessary for utilizing

CHARACTER LENGTH SEMANTICS. This conversion process is covered in all PeopleSoft application 9.0 or higher upgrade paths.

It is very important that you set this parameter at the correct point during database creation. Database creation consists of running several scripts before loading the database with Data Mover, as follows:

• CREATEDB.SQL

• UTLSPACE.SQL

XXDDL.SQL

• DBOWNER.SQL

• PSROLES.SQL

• PSADMIN.SQL

• CONNECT.SQL

Set the parameter

NLS_LENGTH_SEMANTICS

at the beginning of database creation or right before the Data

Mover load.

To do this, modify the init<SID>.ora to add the

NLS_LENGTH_SEMANTICS

parameter, and then shut down and restart the database instance.

Oracle password

If you choose to use an Oracle Password file, you must create one using the ORAPWD utility, as illustrated in this example: export ORACLE_SID=FSDMO orapwd file=$ORACLE_HOME/dbs/pwdtemp2.ora password=manager entries=5

202

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6B

Creating a Database on UNIX

If you choose not to use an Oracle Password file, make one of the following changes to the init<SID>.ora file.

This must be done before running the CREATEDB.SQL script.

• Remove the line beginning with remote_login_passwordfile

, or add a comment character at the beginning as shown in this example:

#remote_login_passwordfile=EXCLUSIVE

• Set the parameter to NONE, as in this example: remote_login_passwordfile=NONE

Note. The init<SID>.ora file will reference "target" directories to write control files, log files, and system files, as well as target locations for Oracle Logs, User Trace Files, and so on. These target directory paths must exist or the

Database Configuration Wizard will fail. See the following section, Creating Target Directory Paths, for details.

For more parameters that may be required for the init<SID>.ora file, consult My Oracle Support.

See Operating System, RDBMS & Additional Component Patches Required for Installation PeopleTools, My

Oracle Support, (search for the article name and your release).

Task 6B-1-5: Creating an INIT<SID>.ORA File (Multitenant Architecture)

If you are creating pluggable databases, set ORACLE_SID to the SID for the root container database (CDB); for example: export ORACLE_SID=<SID>

Add the following line to the init<SID>.ora file: enable_pluggable_database=true

Task 6B-1-6: Creating Target Directory Paths

As mentioned, you must create the directory path structure for the target directories referenced in the scripts executed by the Database Configuration Wizard. The Database Configuration Wizard will not create directories on the fly; it expects the directories to exist.

The <SID> variable for which the Database Configuration Wizard prompts you is automatically prepended to the directory path structure referenced in the various database creation scripts executed by the Database Configuration

Wizard.

Note. If you want to use something other than the delivered directory paths, you need to modify the

CREATEDB.SQL, UTLSPACE.SQL, and XXDDL.SQL scripts in the scripts directory under PS_HOME, replacing the delivered paths with paths appropriate for your site installation prior to running the Database

Configuration Wizard.

Note. Compare the content in XXDDL.SQL with PTDDL.SQL, and if PTDDL.SQL has bigger tablespace sizes than XXDDL.SQL, increase the size of the tablespaces to at least as much in PTDDL.SQL.

You are also asked for several mount points. On UNIX you just specify the File System mount point. An example is data1. (Note that no preceding slash is required.)

Here are some examples of directory path structure references:

• The delivered CREATEDB.SQL script makes the following directory path structure references:

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

203

Creating a Database on UNIX

Chapter 6B

Note. Portions of the script have been omitted for clarity.

startup nomount pfile=$ORACLE_HOME/dbs/init<SID>.ora

   datafile

      '/u01/oradata/<SID>/system01.dbf'      size 400M

   logfile

      '/u01/oradata/<SID>/log01.dbf'         size 70M,

      '/u01/oradata/<SID>/log02.dbf'         size 70M,

      '/u01/oradata/<SID>/log03.dbf'         size 70M; 

• The init<SID>.ora parameter file that is referenced in the CREATEDB.SQL script makes the following directory path structure references:

Note. Portions of the init<SID>.ora parameter file have been omitted for clarity. These paths are hardcoded by the user creating the init<SID>.ora parameter file. The Data Configuration Wizard will not make any substitutions for mount point, target directory path, or <SID> in the init<SID>.ora file.

Control file references:

control_files = ("/u01/oradata/test92/control01.ctl", "/u01/oradata⇒

/test92⇒

/control02.ctl", "/u01/oradata/test92/control03.ctl")

• The delivered UTLSPACE.SQL script makes the following directory path structure references:

Note. Portions of the script have been omitted for clarity.

CREATE TEMPORARY TABLESPACE       PSTEMP

TEMPFILE                'u03/oradata/<SID>/pstemp01.dbf'     SIZE 300M

EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K;

CREATE TABLESPACE      PSDEFAULT

DATAFILE               'u03/oradata/<SID>/psdefault.dbf'     SIZE 10M

EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

        INITIAL     100K

        NEXT        100K

        PCTINCREASE   0  );

• The delivered XXDDL.SQL scripts make the following directory path structure references:

Note. This is a sample of the first several Create Tablespace SQL statements in the XXDDL.SQL script. The rest of the script has been omitted here for clarity.

 CREATE TABLESPACE PSIMAGE DATAFILE '/u01/oradata/<SID>/psimage.dbf'⇒

 SIZE 8M

 EXTENT MANAGEMENT LOCAL AUTOALLOCATE

/

CREATE TABLESPACE PSINDEX DATAFILE '/u01/oradata/<SID>/psindex.dbf' SIZE⇒

 64M

EXTENT MANAGEMENT LOCAL AUTOALLOCATE

/

CREATE TABLESPACE PTAPP DATAFILE '/u01/oradata/<SID>/ptapp.dbf' SIZE 4M

204

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6B

EXTENT MANAGEMENT LOCAL AUTOALLOCATE

/

Creating a Database on UNIX

Task 6B-1-7: Creating Target Directory Paths (Multitenant Architecture)

If you are creating a PDB, you must add the following target directories, replacing <SID> with ORACLE_SID for the CDB, and <PDB_SERVICE_NAME> with the PDB database name.

• /mount/oradata/<SID>/pdbseed

• /mount/oradata/<SID>/logs

Note. The PeopleSoft UNIX user ID executing the Database Configuration Wizard should have read and write permissions for the /mount/oradata/<SID>/logs directory.

• /mount/oradata/<SID>/<PDB_SERVICE_NAME>

Task 6B-1-8: Setting Up Target Database Connectivity

You must add a TNS entry to $ORACLE_HOME/network/admin/tnsnames.ora, because during the Data Mover

Load phase, the Database Configuration Wizard will try to connect to the newly created SID by means of a remote connection string—for example:

ACCESSID/[email protected]_ALIAS

Update the connection information in TNSNAMES.ORA on your server to reflect your Database Name, Oracle

SID, and Server Name.

Note. Make sure that you stop and start (or reload) the Oracle Net listener.

If you are creating a PDB, add an entry in tnsnames.ora to the PDB database (for example,

<PDB_SERVICE_NAME>), not to the root (CDB) database.

Task 6B-1-9: Running the Shell Script psconfig.sh

The shell script psconfig.sh sets up the environment for Data Mover to run. The PeopleSoft Data Mover utility is used to load the database.

To run psconfig.sh:

1. Change the directory to PS_HOME.

2. Run psconfig.sh (. ./psconfig.sh)

Note. The PeopleSoft UNIX user ID executing the Database Configuration Wizard has to be part of the

Oracle DBA group or the PeopleSoft UNIX user ID must grant the UNIX Oracle Administration ID write permission to the following directories in PS_HOME: log, modifiedscripts, and scripts.

Task 6B-2: Running the Database Configuration Wizard

When you run the Database Configuration Wizard, Data Mover typically performs the following actions:

1. IMPORT *.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

205

Creating a Database on UNIX

Chapter 6B

Create all the PeopleTools and application tables with their indexes.

2. ENCRYPT_PASSWORD *

Encrypt security information for the database.

3. CREATE_TRIGGER *

Create application-required triggers.

4. REPLACE_VIEW *

Create PeopleSoft views.

5. CREATE_TEMP_TABLE *

Create PeopleSoft temporary tables.

If Data Mover fails at any of the above steps, it will complete the rest of the steps but will not start the next step— instead the Database Configuration Wizard aborts and tells the user what file to review for the detailed error message. If Data Mover fails at step 1 or 2, it is fatal. If Data Mover fails at step 3 or 4, it is not necessarily fatal.

You may continue the next step(s) manually.

To complete the database creation procedure you must supply information on various authorization IDs and passwords, including Access ID, Connect ID, Symbolic ID, and User IDs. Before beginning this procedure, review the information in the section Planning Database Creation and make a note of the authorization information for your environment. Beginning with PeopleSoft PeopleTools 8.53, the user profiles in PeopleTools demo databases are delivered disabled. During the database configuration procedure you will choose whether to enable the delivered user profiles, and how to assign passwords for the profiles. In addition, you will supply several passwords that were previously provided as defaults. Be sure to note the passwords that you supply, as they will be needed for subsequent installation procedures.

See the information on user profiles in the PeopleTools: Security Administration product documentation.

See "Preparing for Installation," Planning Database Creation.

Beginning with PeopleSoft PeopleTools 8.54, you can create an Oracle Container Database (CDB) and Oracle

Pluggable Database (PDB). The Database Configuration Wizard process described in this section includes choices for creating either CDBs or non-CDBs. For pluggable databases, the Database Configuration Wizard runs the script createdbCDB.sql.

See Understanding the Database Configuration Wizard.

Note. During UNIX console mode installation, you can go back to the previous steps whenever you see the instruction:

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1].

Choose 2 for Previous.

To run the Database Configuration Wizard:

1. Go to PS_HOME/setup/PsMpDbInstall.

2. Launch the installation using the command setup.sh

:

See the chapter "Using the PeopleSoft Installer" for additional flags, or for details about running in GUI mode.

See "Using the PeopleSoft Installer," Running the PeopleSoft Installer.

3. You see the following prompt:

Welcome to the PeopleSoft Database Configuration Wizard 8.55

This Wizard will assist you in configuring and loading a PeopleSoft⇒

 database.

PRESS <ENTER> TO CONTINUE:

206

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6B

Creating a Database on UNIX

4. Press ENTER to continue.

5. Specify the location of PS_HOME

—the high-level directory where the PeopleSoft PeopleTools software is installed

—and press ENTER.

Please enter an installation location or press <ENTER> to accept the⇒

 default

(DEFAULT: [/ds1/ora/PT855]) /ds1/certora/PT855

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1]

6. Press ENTER to continue

7. Specify the location of PS_APP_HOME

—the high-level directory where the PeopleSoft Application software is installed

—and press ENTER.

Note: If you have installed PeopleSoft Applications outside PeopleTools⇒

 PS_HOME then choose the PeopleSoft Applications home PS_APP_HOME, else leave⇒

 the default PS_HOME.

Choose the directory where you previously installed PeopleSoft⇒

 Applications, commonly known as PS_APP_HOME.  or press <ENTER> to accept the default ⇒

  

(DEFAULT: /ds1/ora/PT855): /ds1/ora/FSCM92

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1] :

Note. If the PS_APP_HOME is different from the PS_HOME then all the modified scripts will be will be created under PS_APP_HOME\modifiedscripts, and all the DCW logs will be created under PS_APP_HOME\ logs.

8. Select whether you want to create a container or non-container database.

 ->1- Non-Container DB

   2- Container DB

Note: The "Container DB" option applies to Oracle database 12c or⇒

 higher for 

Pluggable database feature.

Select option 1, Non-Container DB, if you are not creating a CDB. Select option 2, Container DB, if you are running on Oracle 12c or higher, and are creating a CDB.

9. Select whether you want to create a Unicode or non-Unicode database, and press ENTER.

For a database platform of 'Oracle', are you installing a:

   1  -  Non-Unicode Database

 ->2  -  Unicode Database

To select an item enter its number, or 0 when you are finished [0]: 0

10. Select the desired character set and press ENTER.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

207

Creating a Database on UNIX

Chapter 6B

This character set selection is substituted and used in the CREATEDB.SQL script. This example shows the

Unicode character set.

Select Character Set:

 ->1  -  AL32UTF8

 

 To select an item enter its number, or 0 when you are finished [0]: 0

11. If you select a non-Unicode database, you see the following prompt.

Specify the number for the desired character set.

Select Character Set:

  ->1- Western European ISO 8859-1

    2- Western European ISO 8859-15 (with Euro sign)

    3- Microsoft Windows Latin-1 CP1252

    4- US 7-bit ASCII

    5- Japanese Shift-JIS

To select an item enter its number, or 0 when you are finished [0]:

12. The Database Configuration Wizard detects which database files are available for loading. Select the appropriate PeopleSoft database type to load and press ENTER to continue.

You will only see the database types that are valid based on the PeopleSoft application modules that you have installed.

Database Create Type:

 ->1  -  Demo

   2  -  System

   3  -  PeopleTools System

To select an item enter its number, or 0 when you are finished [0]: 2

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1]

Note. See the manual database creation chapter for further details about PeopleSoft database types.

13. Select the PeopleSoft application database you want to load, pressing ENTER when you are done. (The available selections will depend upon which application software you have installed.)

Select PeopleSoft Application:

   1  -  PeopleSoft Fin/SCM Database Objects - US English

To select an item enter its number, or 0 when you are finished [0]: 0

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1]

If you installed the Multilanguage software, each application will be listed several times, once for each language. If you are installing languages other than English, make sure to select the appropriate language data files for each application you select in English. This will load the translated database objects.

See "Preparing for Installation," Planning Multilingual Strategy.

If you are installing an application in any language other than English, you must also select the English component of the application. For example, for Financials/Supply Chain Management if you select Fin/SCM -

French, you must also select Fin/SCM - US English. This ensures that you install the necessary base-language

208

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6B

Creating a Database on UNIX

components.

14. When prompted for the location of $ORACLE_HOME/bin and $ORACLE_HOME, modify the locations as necessary.

Specify the directory path for 'sqlplus'

   Please specify a directory name or press Enter

   [/products/oracle/11.2.0/bin] /products/oracle/11.2.0/bin

Specify the location for ORACLE_HOME

   Please specify a directory name or press Enter

   [/products/oracle/11.2.0] /products/oracle/11.2.0

15. You see the following informational prompt:

Note. The modifiedscripts directory is populated based on the PS_APP_HOME path that you entered in an earlier step.

Location of modified scripts:

 /ds1/certora/FSCM92/modifiedscripts

Please press Enter to Continue

16. Choose to either create an Oracle SID and load a PeopleSoft database, or use an existing Oracle SID to load the PeopleSoft database. For a new installation you must create a new Oracle SID.

Note. The available options depend upon the operating system you are running on.

Do you want to create a new SID or use the existing one?

 ->1  -  Create new SID

   2  -  Use existing SID

   To select an item enter its number, or 0 when you are finished [0]: 1

   Please press Enter to Continue

To create a PDB on an existing CDB, choose option 2, Use existing SID. In this case, the Oracle SID will be the root SID. The "Database Name" that you specify in the next step will be the PDB database name (that is,

<PDB_SERVICE_NAME>).

17. The following prompts request Oracle server and SID information. Whichever option you chose in the previous step, the following prompts will remain the same. The Database Configuration Wizard will use just the information it needs to complete the tasks necessary based on whether you chose to create a new SID or use an existing one.

Note. You must use all uppercase text for the Oracle SID and the database name.

Note. No preceding slash is required for the mount points.

Please enter oracle server information

   Oracle SID [PTSYS] TEST920

   Database Name [PTSYS] PT855

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

209

Creating a Database on UNIX

Chapter 6B

Mount Point 1( for SYSTEM and REDO LOGS file in createdb.sql, ex: NT⇒

 'C', UNIX⇒

 'u01') [c] ds1

Mount Point 2 ( for PSTEMP and PSDEFAULT file in utlspace.sql, ex: NT⇒

 'C' , UNIX 'u01') [c]⇒

 ds1

Mount Point 3 ( for all files in xxddl.sql, ex: NT 'C' , UNIX 'u01') ⇒

[c] ds2

Enable AutoExtend for Peoplesoft Tablespaces?

 ->1  -  Yes

   2  -  No

   To select an item enter its number, or 0 when you are finished [0]: 0

   Please press Enter to Continue

18. The following prompts request additional Oracle server information.

Please enter oracle server information

Peoplesoft owner ID (ex: 'sysadm')   [SYSADM]: 

Peoplesoft owner password (ex: 'sysadm') []:

Peoplesoft connect ID [people]:

Peoplesoft connect password []:

Peoplesoft default tablespace  (ex: 'PSDEFAULT') [PSDEFAULT]:

Location of init.ora file complete path

[/ds29/products/oracle/11.2.0/dbs/initTEST920.ora] /products/oracle⇒

/11.2.0/dbs/initTEST920.ora

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1] 

Use the following guidelines to specify the server information:

• You must limit the owner ID (access ID) and connect ID to eight characters or less.

• The passwords for the owner ID (access ID) and connect ID must be between 6 and 30 characters.

• Whatever you type as your password will not be displayed. This is true for the connect ID password.

• The PSADMIN.SQL script is run by the Database Configuration Wizard for every PeopleSoft database that you are going to create. When prompted for a default tablespace name, select PSDEFAULT if you are using PeopleSoft naming conventions, or your site equivalent if you are not using PeopleSoft naming conventions.

• The path in the preceding prompt for init<SID>.ora (initTEST920.ora in the example code) must match the path of the init<SID>.ora file you created under the task "Fulfilling PeopleSoft Database Configuration

Wizard Prerequisites" earlier in this chapter.

210

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6B

Creating a Database on UNIX

19. Specify the Application Server User ID and password.

The Appserver user has privileges to start or shut down the Application Server domain. It is also used during the Application Server configuration. Enter one of the delivered PeopleSoft user IDs.

Please enter the Appserver User and Password for your database.

   Appserver User []: VP1

   Password []: 

   Re-type Password []: 

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1] :

20. Specify the Web server user ID and password.

Please enter the Webserver User and Password for your database.

   Webserver User : PTWEBSERVER

   Password []:

   Re-type Password []: 

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1] : 

The default Web server user in the prompt is PTWEBSERVER. The Web Server user ID, also referred to in this documentation as Web Profile User ID, is used to access the web profile information from the database through the Application Server Jolt service.

21. Choose whether to enable or disable other user profiles in the database.

Choose whether to enable or disable all other user profiles in your⇒

 database.

   1- Disable

-> 2- Enable

To select an item enter its number, or 0 when you are finished [0] :

• Select the Enable option to leave the User profiles (other than the Application Server User Profile and

Web server User profiles specified in the previous steps) unchanged.

• Select the Disable option to disable all the User profiles in the database except the Application Server User

Profile and Web server User profiles specified in the previous steps.

22. Select an option to set User profile passwords.

Choose whether to set the password same as the OPRID (user) or a⇒

 different password (a global password, same for all OPRIDs).

   1- Set the password same as OPRID

-> 2- I would like to set a different password

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

211

Creating a Database on UNIX

Chapter 6B

To select an item enter its number, or 0 when you are finished [0] :

• Select the option "Set the password same as OPRID" to specify a password that is the same as the User ID

(for example, VP1/VP1).

• Select the option "I would like to set a different password" to set a common global password for all the

User profiles in the database in the next step.

23. If you selected the option "I would like to set a different password", specify (and re-enter) a password for all other user profiles except the Application Server User Profile and Web server User profiles specified in the previous steps of this procedure.

Enter a password that you want to set for all other user profiles.

   Password []:

   Re-type Password []:

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1] 

24. Select the base language (the default is US English) and press ENTER.

Select Base Language:

 ->1  -  ENG - US English

To select an item enter its number, or 0 when you are finished [0]: 0

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1]

The Select base language selection is used to determine what primary base language the customer wants to run their PeopleSoft application on. If you choose a language other than English, the base language will be swapped during the database creation script.

See "Preparing for Installation," Planning Multilingual Strategy.

This step applies only if your users will be operating PeopleSoft applications primarily in one particular language other than English. This step gives a performance boost to the language you designate as the base language, but would require more administrative overhead than leaving English as the base language does.

See PeopleTools: Global Technology.

25. You see a confirmation dialog indicating the selected database configuration.

Peoplesoft Database Configuration will be installed in the following⇒

 location:

Install Folder:

   /ds1/certora/PT855

PeopleToolsOraUnixFeature

Apps Install Home:

   /ds1/certora/FSCM92

Database Platform:

   Oracle  -  Non-Unicode

Oracle SID: 

212

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6B

Creating a Database on UNIX

   TEST920

Application:

   PeopleTools System Database - US English

Database Name:

   PT855

Please type 'back' to go to previous panels

PRESS <ENTER> TO CONTINUE:

26. Press ENTER. You see a number of messages indicating the progress of the processes being run.

Installing Peoplesoft Database Configuration... Please wait.

The ORACLE_SID Environment Variable has been updated to "TEST920"

Up to this point the message(s) indicating progress will be identical.

Beyond this point they will differ based on which option you chose⇒

 above,⇒

 Create a New Sid or Use an Existing SID.

Note. It is always a good idea to let the installation run through even if you encounter a problem. If for any reason you manually abort the installation, you will need to delete the file vpd.properties in order for the

Database Configuration Wizard to successfully update SID when you run again. The file vpd.properties is located under your home directory.

27. If you chose to use an existing SID, you see Database Configuration Wizard messages like this:

Note. The messages are displayed on the console to indicate real time progress of the Database Configuration

Wizard. All messages are also written to log files contained in the PS_HOME/log directory.

You see a message for every SQL script the Database Configuration Wizard executes, regardless of which option you have chosen. The messages may vary depending upon your environment.

Installing Peoplesoft Database Configuration... Please wait.

The ORACLE_SID Environment Variable has been updated to 'TEST920'

Executing runCreatedbCDB.sh

Executing ptperlcat.sh

Executing createPDB.sql

Executing runUtlspace.sh

Executing ptddl.sql

Executing dbowner.sql

Executing psroles.sql

Executing psroles2.sql

 

Executing psadmin.sql...

Executing connect.sql......

Note. At this step, DBSetup is invoked via Data Mover to generate the input Data Mover script. This script can be found in the PS_HOME/scripts directory.

 Initializing Data Mover ... please wait

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

213

Creating a Database on UNIX

Chapter 6B

 PeopleTools 8.55 - Data Mover

 Copyright (c) 2012 PeopleSoft, Inc.

 All Rights Reserved

 Started:  Thu Jan  3 19:39:02 2012

 Data Mover Release: 8.55

 Database: PT855

 Creating Database setup script /PT855/scripts/PT855.dms

 Ended: Thu Jan  3 19:39:02 2012

 Successful completion

 Initializing Data Mover ... please wait

Note. At this step, Data Mover is invoked to execute the input Data Mover script.

If Data Mover attempts to run and fails, you can edit and rerun the script and restart Data Mover. This procedure is covered in the next section. If the process fails before Data Mover begins, run the script

DBSetup.dms.

See Checking the Log Files and Troubleshooting.

 PeopleTools 8.55 - Data Mover

 Copyright (c) 2012 PeopleSoft, Inc.

 All Rights Reserved

 Started:  Thu Jan  3 19:39:40 2012

 Data Mover Release: 8.55

 Database: PT855

 Importing  ACCESS_GRP_LANG

 Creating Table  ACCESS_GRP_LANG

 Import  ACCESS_GRP_LANG  0

 Building required indexes for ACCESS_GRP_LANG

 Updating statistics for ACCESS_GRP_LANG

 Records remaining: 1098

 Importing  ACCESS_GRP_TBL

 Creating Table  ACCESS_GRP_TBL

 Import  ACCESS_GRP_TBL  47

 Building required indexes for ACCESS_GRP_TBL

 Updating statistics for ACCESS_GRP_TBL

 Records remaining: 1097

Note. A portion of the messages generated at this step have been omitted for clarity.

 Importing  XMLSERVICEINFO

 Creating Table  XMLSERVICEINFO

 Import  XMLSERVICEINFO  0

 Building required indexes for XMLSERVICEINFO

 Updating statistics for XMLSERVICEINFO

 Records remaining: 1

 Importing  PSSTATUS

 Creating Table  PSSTATUS

 Import  PSSTATUS  1

 Building required indexes for PSSTATUS

 Updating statistics for PSSTATUS

 SQL Spaces: 0  Tables: 1099  Triggers: 0 Indexes: 1399  Views: 0

 SQL Successful -  INSERT INTO PS.PSDBOWNER VALUES('PT855', 'PT855')

214

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6B

Creating a Database on UNIX

 SQL Successful -  UPDATE  PSSTATUS SET OWNERID = 'PT855'

 SQL Successful -  UPDATE  PSOPRDEFN SET SYMBOLICID = 'TEST920',⇒

 OPERPSWD =⇒

 OPRID, ENCRYPTED = 0

 SQL Successful -  UPDATE  PSACCESSPRFL SET ACCESSID = 'PT855',⇒

 SYMBOLICID =⇒

 'TEST920', ACCESSPSWD = 'PT855', VERSION = 0, ENCRYPTED = 0

 SQL Successful -  UPDATE  PSOPTIONS SET LICENSE_CODE =⇒

 'ffffffffffffffffff⇒

 ffffffffffff2', LICENSE_GROUP = '06'

 SQL Successful -  GRANT   SELECT ON PSSTATUS TO people

 SQL Successful -  GRANT   SELECT ON PSOPRDEFN TO people

 SQL Successful -  GRANT   SELECT ON PSACCESSPRFL TO people

 SQL Successful -  CREATE  VIEW SYSKEYS (IXCREATOR, IXNAME, COLNAME,⇒

 COLNO,⇒

 COLSEQ, ORDERING, FUNCTION) AS SELECT A.OWNERID, B.INDEX_

 NAME, B.COLUMN_NAME, B.COLUMN_POSITION, B.COLUMN_POSITION, 'a', ' '⇒

 FROM P⇒

 SSTATUS A, USER_IND_COLUMNS B

 SQL Successful -  CREATE  VIEW SYSINDEXES (TBCREATOR, NAME, TBNAME,⇒

 CREATO R,⇒

 UNIQUERULE, COLCOUNT, IXTYPE, CLUSTERRULE, IXSIZE, PERC

 ENTFREE) AS SELECT TABLE_OWNER, INDEX_NAME, TABLE_NAME, TABLE_OWNER,⇒

 SUBST R⇒

(UNIQUENESS,1,1), 1, 'b', 'n', 1, PCT_FREE FROM USER_INDEXES

 Ended:  Thu Jan  3 20:00:32 2012

 Successful completion

Note. At this step, the Data Mover import is complete and additional Data Mover commands and scripts are being executed. The first of these commands is ENCRYPT PASSWORD*.

 Started:  Thu Jan  3 20:00:32 2012

 Data Mover Release: 8.55

 Database: PT855

 Password hashed for GUEST

 Password hashed for GUEST_IP

 Password hashed for PAPP_ACCOUNTSIGNONADM

 Password hashed for PAPP_ACTIONITEMSADM

 Password hashed for PAPP_AUTHOR

 Password hashed for PAPP_BRANDINGADM

 Password hashed for PAPP_CALENDARSADM

 Password hashed for PAPP_CONTCATGADM

 Password hashed for PAPP_CONTENTADM

 Password hashed for PAPP_CONTENTMGR

 Password hashed for PAPP_CONTENTRATINGSADM

 Password hashed for PAPP_CONTENTUSR

 Password hashed for PAPP_CONTEXTADM

 Password hashed for PAPP_CONTEXTMGR

 Password hashed for PAPP_CUSTOMER

 Password hashed for PAPP_DEMOADM

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

215

Creating a Database on UNIX

 Password hashed for PAPP_DEMOITEMCXTADM

 Password hashed for PAPP_DEMOITEMCXTMGR

 Password hashed for PAPP_DEMOITEMCXTUSR

 Password hashed for PAPP_DEMOPUB

 Password hashed for PAPP_DEMOVWR

 Access Profiles successfully encrypted.

 Ended:  Thu Jan  3 20:00:35 2012

 Successful completion

Note. At this step, Data Mover is executing the CREATE_TRIGGER * command.

 Started:  Thu Jan  3 20:00:35 2012

 Data Mover Release: 8.55

 Database: PT855

 Creating Trigger for CURRENCY_CD_TBL

 Records remaining: 2

 Creating Trigger for PSMPRTPREF

 Records remaining: 1

 Creating Trigger for PSWORKLIST

 SQL Triggers: 3

 Ended:  Thu Jan  3 20:00:41 2012

 Successful completion

Note. At this step, Data Mover is executing the REPLACE_VIEW command.

 Started:  Thu Jan  3 20:00:41 2012

 Data Mover Release: 8.55

 Database: PT855

 View  PRCSOUTTYPE_VW

 Views remaining: 666

 View  PRCSSRVROPSLANG

 Views remaining: 665

 View  PRCSSRVROPSYS

 Views remaining: 664

Note. A portion of the messages generated at this step have been omitted for clarity.

 View  PSTREEFLDDTLVW

 Views remaining: 3

 View  PSTREEFLDNODVW

 Views remaining: 2

 View  PSTREESTRCTDFVW

 Views remaining: 1

 View  PSTREESTRCTNFVW

 SQL Views: 667

 Ended:  Thu Jan  3 20:02:52 2012

 Successful completion

Note. At this step, Data Mover is executing the CREATE_TEMP_TABLE * command.

 Started:  Thu Jan  3 20:02:52 2012

216

Chapter 6B

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6B

Creating a Database on UNIX

 Data Mover Release: 8.55

 Database: PT855

 Creating Table  MENU_LANG_TMP

 Building required indexes for MENU_LANG_TMP

 SQL Tables: 1  Indexes: 1

 Ended: Thu Jan  3 20:02:57 2012

 Successful completion

Note. At this step, the Data Mover steps are complete. If the Database Configuration Wizard executed successfully, you see the message below.

Creating Table  GPFR_DASR_TMP

Creating temp table instances (5)

Building required indexes for GPFR_DASR_TMP

Records remaining: 1

Creating Table  GPFR_DASS_TMP

Creating temp table instances (5)

Building required indexes for GPFR_DASS_TMP

SQL Tables: 832  Temp Tables: 7805 Indexes: 8266

Ended: Thu Oct 16 16:35:16 2012

Successful completion

ExitCode: 0

Error: false

=====================================

Installation Complete

---------------------

Congratulations. Peoplesoft Database Configuration has been⇒

 successfully installed to:

  /ds1/certora/PT855

Note. If the Database Configuration Wizard detected an error, you get a message similar to the one below, depending on the error encountered:

Checking Data Mover log ... please wait

Checking ... ptengs.log

Error Information

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

217

Creating a Database on UNIX

Chapter 6B

The installation failed to load PeopleSoft data with the following⇒

 error: Error in ptengs.log Please look into the log file(s) located under log⇒

 directory for details.

Click next to exit the installation.

   Please press Enter to Exit

28. If you chose to create a new SID, you see Database Configuration Wizard messages like this:

Installing Peoplesoft Database Configuration... Please wait.

The ORACLE_SID Environment Variable has been updated to 'TEST920'

Note. You see a message for every SQL script the Database Configuration Wizard executes, regardless of which option you have chosen.

Executing createdb.sql for Oracle(UNIX).....

Executing utlspace.sql for Oracle(UNIX).....

Executing ptddl.sql for Oracle(UNIX).....

Executing dbowner.sql for Oracle(UNIX).....

Executing psroles.sql for Oracle(UNIX).....

Executing psadmin.sql for Oracle(UNIX).....

Executing connect.sql for Oracle(UNIX).....

Note. At this step, DBSetup is invoked from Data Mover to generate the input Data Mover script. This script can be found in the PS_HOME/scripts directory.

Initializing Data Mover ... please wait

PeopleTools 8.55 - Data Mover

Copyright (c) 2012 PeopleSoft, Inc.

All Rights Reserved

Started:  Fri Jan  4 06:24:55 2012

Data Mover Release: 8.55

Database: PT855

Creating Database setup script /ds1/home/certora/PT855/scripts⇒

/PT855ora.dms

Ended: Fri Jan  4 06:24:55 2012

Successful completion

Note. At this step, Data Mover is invoked to execute the input Data Mover script.

Initializing Data Mover ... please wait

Started:  Fri Jan  4 06:25:27 2012

Data Mover Release: 8.55

Database: PT855

Importing  ACCESS_GRP_LANG

Creating Table  ACCESS_GRP_LANG

Import  ACCESS_GRP_LANG  0

218

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6B

Creating a Database on UNIX

Building required indexes for ACCESS_GRP_LANG

Updating statistics for ACCESS_GRP_LANG

Records remaining: 1098

Importing  ACCESS_GRP_TBL

Note. A portion of the messages generated at this step have been omitted for clarity.

Records remaining: 2

Importing  XMLSERVICEINFO

Creating Table  XMLSERVICEINFO

Import  XMLSERVICEINFO  0

Building required indexes for XMLSERVICEINFO

Updating statistics for XMLSERVICEINFO

Records remaining: 1

Importing  PSSTATUS

Creating Table  PSSTATUS

Import  PSSTATUS  1

Building required indexes for PSSTATUS

Updating statistics for PSSTATUS

SQL Spaces: 0  Tables: 1099  Triggers: 0 Indexes: 1399  Views: 0

SQL Successful -  INSERT INTO PS.PSDBOWNER VALUES('PT855', 'PT855')

SQL Successful -  UPDATE  PSSTATUS SET OWNERID = 'PT855'

SQL Successful -  UPDATE  PSOPRDEFN SET SYMBOLICID = 'prod817',⇒

 OPERPSWD = OPRI0

SQL Successful -  UPDATE  PSACCESSPRFL SET ACCESSID = 'PT855',⇒

 SYMBOLICID = 0

SQL Successful -  UPDATE  PSOPTIONS SET LICENSE_CODE = 'ffffffffffffffff⇒ fffffff'

SQL Successful -  GRANT   SELECT ON PSSTATUS TO people

SQL Successful -  GRANT   SELECT ON PSOPRDEFN TO people

SQL Successful -  GRANT   SELECT ON PSACCESSPRFL TO people

SQL Successful -  CREATE  VIEW SYSKEYS (IXCREATOR, IXNAME, COLNAME,⇒

 COLNO, COLSB

SQL Successful -  CREATE  VIEW SYSINDEXES (TBCREATOR, NAME, TBNAME,⇒

 CREATOR, UNS

Ended:  Fri Jan  4 06:38:10 2012

Successful completion

Note. At this step, the Data Mover import is complete and additional Data Mover commands and scripts are being executed. The first of these commands is ENCRYPT PASSWORD*.

Started:  Fri Jan  4 06:38:11 2012

Data Mover Release: 8.55

Database: PT855

Password encrypted for APPENV

Password encrypted for PSADMIN

Password encrypted for PT8

Password encrypted for PTADMIN

Password encrypted for PTAE

Password encrypted for PTAPPMSG

Password encrypted for PTDMO

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

219

Creating a Database on UNIX

Password encrypted for PTEMPL

Password encrypted for PTEND

Password encrypted for PTGBL

Password encrypted for PTHVAP

Password encrypted for PTIDE

Password encrypted for PTOLAP

Password encrypted for PTOPT

Password encrypted for PTPORTAL

Password encrypted for PTPRD

Password encrypted for PTQETST

Password encrypted for PTRPT

Password encrypted for PTSECADM

Password encrypted for PTSVR

Password encrypted for PTTOOLS

Password encrypted for PTUPG

Password encrypted for PTWEB

Access Profiles successfully encrypted.

Ended:  Fri Jan  4 06:38:13 2012

Successful completion

Note. At this step, Data Mover is executing the CREATE_TRIGGER * command.

Started:  Fri Jan  4 06:38:13 2012

Data Mover Release: 8.55

Database: PT855

Creating Trigger for CURRENCY_CD_TBL

Records remaining: 2

Creating Trigger for PSMPRTPREF

Records remaining: 1

Creating Trigger for PSWORKLIST

SQL Triggers: 3

Ended:  Fri Jan  4 06:38:18 2012

Successful completion

Note. At this step, Data Mover is executing the REPLACE_VIEWS * command.

Started:  Fri Jan  4 06:38:18 2012

Data Mover Release: 8.55

Database: PT855

View  PRCSOUTTYPE_VW

Views remaining: 666

View  PRCSSRVROPSLANG

Views remaining: 665

View  PRCSSRVROPSYS

Note. A portion of the messages generated at this step have been omitted for clarity.

Views remaining: 3

View  PSTREEFLDNODVW

Views remaining: 2

View  PSTREESTRCTDFVW

Views remaining: 1

220

Chapter 6B

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6B

Creating a Database on UNIX

View  PSTREESTRCTNFVW

SQL Views: 667

Ended:  Fri Jan  4 06:40:19 2012

Successful completion

Note. At this step, Data Mover is executing the CREATE_TEMP_TABLE * command.

Started:  Fri Jan  4 06:40:19 2012

Data Mover Release: 8.55

Database: PT855

Creating Table  MENU_LANG_TMP

Building required indexes for MENU_LANG_TMP

SQL Tables: 1  Indexes: 1

Ended: Fri Jan  4 06:40:20 2012

Successful completion

Note. At this point, Data Mover is complete.

Creating Table  GPFR_DASR_TMP

Creating temp table instances (5)

Building required indexes for GPFR_DASR_TMP

Records remaining: 1

Creating Table  GPFR_DASS_TMP

Creating temp table instances (5)

Building required indexes for GPFR_DASS_TMP

SQL Tables: 832  Temp Tables: 7805 Indexes: 8266

Ended: Thu Oct 16 16:35:16 2012

Successful completion

ExitCode: 0

Error: false

29. If the Database Configuration Wizard executed successfully, you see the following message, and you can press ENTER to exit.

=========================================

Installation Complete

---------------------

Congratulations. Peoplesoft Database Configuration has been⇒

 successfully installed to:

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

221

Creating a Database on UNIX

Chapter 6B

 /ds1/certora/PT855

30. If the Database Configuration Wizard detected an error, you get a message similar to the one below, depending on the error encountered:

Checking Data Mover log ... please wait

Checking ... /ds1/home/certora/PT855/log/ptengs.log          Error

Information

The installation failed to load PeopleSoft data with the following⇒

 error: Error in /ds1/home/certora/PT855/log/ptengs.log Please look into the log file⇒

(s) located under log directory for details.

Execute a Unix tail command on the log will show you the last record⇒

 you were⇒

 processing when the error occurred.

Example: pt-sun20:$ tail ptengs.log

Updating statistics for CURRCD_TBL_LANG

Records remaining: 982

Importing  CURRENCY_CD_TBL

Creating Table  CURRENCY_CD_TBL

SQL Error. Error Position: 230 Return: 1722 - ORA-01722: invalid number

INSERT INTO PS_CURRENCY_CD_TBL  (CURRENCY_CD, EFFDT, EFF_STATUS, DESCR,⇒

 DESCRSH)

Error: SQL execute error for CURRENCY_CD_TBL

SQL Spaces: 0  Tables: 118  Triggers: 0 Indexes: 122  Views: 0

Ended: Mon Jan 28 15:59:43 2012

Unsuccessful completion

Task 6B-3: Checking the Log Files and Troubleshooting

This section discusses:

• Checking the Log Files

• Running Data Mover

• Troubleshooting

• Improving Performance

Task 6B-3-1: Checking the Log Files

After the Database Configuration Wizard finishes its execution, look for all log output in the PS_HOME/log directory. Open all the log files. There is a log file for each of the steps that the Database Configuration Wizard carries out—importing, encrypting passwords, creating triggers, replacing views, and creating temp tables. None

should contain error messages.

222

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6B

Creating a Database on UNIX

Task 6B-3-2: Running Data Mover

If the Database Configuration Wizard does not complete successfully, you must run Data Mover manually, using one of the following methods.

On UNIX, run PS_HOME/bin/psdmtx from the command line.

If you use the access ID that you specified during the database configuration to log on, you log on in "bootstrap mode." When you start Data Mover in bootstrap mode, the word "BootStrap" appears in the Data Mover status bar.

If you use a valid PeopleSoft Operator ID, such as PS for Human Capital Management or VP1 for

Financials/Supply Chain Management, you log on in "user mode." In this mode, no designation appears in the

Data Mover status bar.

To run Data Mover on the command line:

Note. You can run psdmtx

by supplying arguments on the command line, or by passing the arguments from a text file. This section describes the text file method.

1. Go to PS_HOME/bin.

cd $PS_HOME/bin

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

223

Creating a Database on UNIX

Chapter 6B

2. Use the following command to view the help for psdmtx

:

$ psdmtx /help

Usage:  psdmtx  [-CT DB2|DB2ODBC|DB2UNIX|MICROSFT|ORACLE]

                [-CS server name]

                [-CD database name]

                [-CO user id]

                [-CP user pswd]

                [-CI connect id]

                [-CW connect id pswd]

                [-I  process instance]

                [-FP filename]

          or

        psdmtx  [parmfile]

To capture the output in a file, use a greater-than symbol ("pipe", >) followed by a filename. For example: psdmtx [arguments] > filename.txt

Use the following list of commands and descriptions for the psdmtx

arguments:

Command Argument

-CT <DB type>

Description

The type of database to connect to: ORACLE.

-CD <DBNAME>

-CO <ACCESSID>

-CP <ACCESSPWD>

-CI <CONN ID>

-CW <CONN PSWD>

-FP <filename>

Your selected Database Name.

Use the <DBNAME> Access ID to run Data Mover in bootstrap mode.

The password for <DBNAME> Access ID.

The ID used to connect to the database server.

The password for the specified connection ID.

The filename for the Data Mover import script (DMS) to run.

3. To set up Data Mover to rerun the Data Mover import script in bootstrap mode, do the following: a. Change directory to PS_HOME/setup.

b. Copy parmfile to parm<DBNAME>. For example, parmPT855. c. Edit parm<DBNAME>.

Use the information in the table above to edit the file for your configuration.

Use ORACLE for <DB type>.

For example:

Before

-CT <DB type> -CD <DBNAME> -CO <ACCESSID> -CP <ACCESSPWD> -CI <CONN⇒

 ID> -CW⇒

 <CONN PSWD> -FP <filename>

224

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6B

Creating a Database on UNIX

After

-CT ORACLE -CD HRDMO -CO HRDMO -CP HRDMO -CI people -CW peop1e -FP⇒

 $PS_HOME⇒

/scripts/pt855ora.dms

4. To launch Data Mover in bootstrap mode, do the following:

• Change directory (cd) to PS_HOME/bin

• Run the psdmtx command with the edited parm<DBNAME> file.

 pt-sun20:$ psdmtx ../setup/parmPT855

You see Data Mover log messages tracking the progress.

See Also

PeopleTools: Data Management

Task 6B-3-3: Troubleshooting

If the Database Configuration Wizard did not complete successfully, read this troubleshooting information. If your script has stopped midway (this can happen for a number of reasons) you need to edit the Data Mover script generated automatically by the Database Configuration Wizard and restart Data Mover manually. The Data

Mover script files have the extension .dms and are sometimes referred to as "DMS scripts."

The generated Data Mover import script is saved in the PS_HOME/scripts directory. The script conforms to the following naming convention:

<dbname>ora.dms

If the Database Configuration Wizard fails while creating views, clear the cache folder, for example,

USER_HOME/PS_CACHE, and repeat the database creation.

See the information on startup settings in PeopleSoft Configuration Manager in the PeopleTools: System and

Server Administration product documentation.

To edit and restart the DMS script:

1. Determine the record that was being imported (that is, which IMPORT command was running) when the script stopped, and use the following guidelines to edit and rerun the DMS scripts.

When building a DMO database or a multilingual database, adding the SET START statement can be tricky because the Data Mover script used to load the database will include more than one IMPORT statement. The key is to view the log files and determine which IMPORT section of the script Data Mover failed on.

• If the failure occurred during the first IMPORT statement, add the SET START statement before the first

IMPORT *; statement.

• If the failure occurred during a subsequent IMPORT statement, comment out all statements preceding the

IMPORT *; statement where the failure occurred and add the SET START statement before the IMPORT

*; statement of the section in which the failure occurred.

This is very important: If you see any "unique index constraint" error messages in the "Building required indexes" section, your IMPORT script failed during a subsequent IMPORT but the SET START statement was added to the first IMPORT. In this situation, you can run the Data Mover script in its originally generated form, with only one modification. In the first IMPORT section, change the statement "IMPORT

*;" to "REPLACE_DATA *;". This will delete all the data in the tables, and re-import it. This process will take some time to run, and you will need to separately create each of the indexes that failed.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

225

Creating a Database on UNIX

Chapter 6B

2. Start Data Mover by running psdmtx on the command line.

See Running Data Mover.

3. Log on using the Access ID to start Data Mover in bootstrap mode.

The input window should display the DMS import script for the database. The script has the format

<dbname>ora.dms.

4. If necessary, select File, Open, and browse to the PS_HOME/scripts directory to find the appropriate DMS script.

5. Add the following line before the offending IMPORT command (the one being executed when the failure occurred):

SET START <RECORD NAME>;

<RECORD NAME> is the name of the record that failed. Make sure to review the Data Mover log file to see where the script failed and locate the last record that imported successfully. The SET START command will begin the Data Mover import at the specified record name.

Note. It is a good idea to change the name of the log file in the script before each attempt at running it. This ensures that you have a separate log file for each attempt, if you run the import more than once.

For example, if the script stops and the table is partially inserted with a message similar to this one:

Importing  PSPNLFIELD

Rows inserted into PSPNLFIELD

3000

First drop the partially inserted table (for example, record) by using the DROP TABLE command, and then restart Data Mover at the record that failed using the SET START command and continue the Data Mover import. This can be done in a single pass.

Add the following lines before the offending IMPORT *; command (the one being executed when the failure occurred):

SET START <RECORD NAME>;

DROP TABLE <RECORD NAME>; where <RECORD NAME> is the name of the record that failed. The SET START statement will begin the

Data Mover import at the specified <RECORD NAME>.

Example of the original script:

REM - PeopleTools System Database - US English

/

SET LOG ptengs.log;

SET INPUT ptengs.db;

SET COMMIT 30000;

SET NO VIEW;

SET NO SPACE;

SET NO TRACE;

SET UNICODE ON;

IMPORT *;

Example of script after modification, with changes in bold font:

REM - PeopleTools System Database - US English

/

226

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 6B

Creating a Database on UNIX

SET LOG ptengs2.log;

SET INPUT ptengs.db;

SET COMMIT 30000;

SET NO VIEW;

SET NO SPACE;

SET NO TRACE;

SET UNICODE ON;

SET START PSPNLFIELD;

DROP TABLE PSPNLFIELD;

IMPORT *;

For the DROP statement, for records with a recname without a leading PS, add PS_ to the beginning of the recname; otherwise the table will not be found. For example, PS_<RECNAME>.

6. To restart the script, use the psdmtx

command to execute Data Mover on the command line.

See Running Data Mover.

Task 6B-3-4: Improving Performance

The following tips can help you save time when running the Data Mover scripts:

• Run Data Mover from the fastest workstation available.

• Run Data Mover on the database server.

• Run only a single instance of Data Mover, and do not have any other applications running during the import.

• In the PeopleSoft Configuration Manager, turn off all trace options.

Tracing during a DMS load will add considerable time to the process.

• Copy the database file over to the workstation so that Data Mover can access it locally instead of over the network.

• Run Data Mover on the database server with the .db or .dat file located locally.

If you are comfortable changing the options available for an Oracle instance, you might consider "tuning" the instance used for the import. Some of these options are appropriate only during the import, so you may not want to keep them in effect after the import is complete.

For best performance during a Data Mover import, set these options as follows:

• Increase the number of database blocks.

• Use an 8K Oracle block size.

• Use very large rollback segments.

• Increase the size of the UNDO tablespace or the number of UNDO Segments.

• Use asynchronous read and write.

• Use multiple db_writers.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

227

Chapter 7

Completing the Database Setup

This chapter discusses:

• Selecting the Necessary Tasks to Complete the Database Setup

• Reviewing Patch Application

• Updating Database to Latest PeopleTools Release

• Running Additional Data Mover Scripts

• Installing a Multilingual PeopleTools System Database

• Running VERSION Application Engine Program

• Running SQR Reports

• Checking the Database

• Running SETSPACE.SQR

• Running Alter Audit

Selecting the Necessary Tasks to Complete the Database Setup

Review each of the tasks in this chapter to determine which are required for your database setup. Depending upon the details of your installation you may not need to complete every task. However, it is important to evaluate the tasks with respect to your specific situation.

Task 7-1: Reviewing Patch Application

The section Reviewing Patches and Updates Required at Installation in the first chapter of this documentation instructed you to search the My Oracle Support Patches & Updates area for Required for Install patches for

PeopleSoft PeopleTools and your PeopleSoft application.

See "Preparing for Installation," Reviewing Patches and Updates Required at Installation.

The patch user documentation, which is included with the files that you download from My Oracle Support, specifies whether the patch includes database changes. The type of patch you are applying may affect how you proceed with the tasks in this chapter.

• If you meet both of the following listed requirements, skip the task Updating Database to Latest PeopleTools

Release, and continue with the task Running Additional Database Mover Scripts:

• You are installing either a PeopleSoft PeopleTools System (SYS) database or a database delivered on

PeopleSoft PeopleTools 8.55.

• You are applying a Required for Install PeopleSoft PeopleTools patch.

Follow the directions in the patch user documentation to apply the database changes.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

229

Completing the Database Setup

Chapter 7

• Complete the task Updating Database to Latest PeopleTools Release, and proceed to review and carry out the tasks following it if:

You are installing a PeopleSoft Application system (SYS) or demo (DMO) database that is not delivered on

PeopleSoft PeopleTools 8.55. The task includes a step to apply the patch database changes.

See Understanding Database Updates for information on determining the delivered version of PeopleSoft

PeopleTools.

Task 7-2: Updating Database to Latest PeopleTools Release

This section discusses:

• Understanding Database Updates

• Cleaning Up Data

• Deleting Performance Monitor System Default Data

• Creating New PeopleTools Tablespaces

• Updating PeopleTools System Tables

• Updating PeopleTools Database Objects

• Updating PeopleTools Multilingual Objects

• Deleting Obsolete PeopleTools Database Objects

• Applying Patched PeopleTools Database Objects

• Altering PeopleTools Tables

• Migrating Records to New Tablespaces

• Updating PeopleTools System Data

• Running PeopleTools Conversions

• Converting Integration Broker

• Running Additional PeopleTools Conversions

Understanding Database Updates

Your PeopleSoft application database may be on a PeopleSoft PeopleTools release prior to the version that you are currently running. For you to be able to sign on to your database after running the Data Mover script to load your database, the PeopleSoft PeopleTools versions for your database and your file server must match. The steps in this task ensure that your PeopleSoft database is in sync with the PeopleSoft PeopleTools version that you are running.

Note. You will use Application Designer for several steps in this portion of the installation. Consult the

Application Designer documentation if you have questions.

See PeopleTools: Application Designer Developer's Guide

Note. If you are installing either a PeopleSoft PeopleTools System Database or a database delivered on

PeopleSoft PeopleTools 8.55, and you are applying a required for install PeopleSoft PeopleTools patch, skip the steps in this task. Instead, follow the directions in the patch user doc to apply the database changes, and then continue with the install at the task Running Additional Data Mover Scripts. If you are installing an application

SYS or DMO database that is not delivered on PeopleSoft PeopleTools 8.55, please proceed with this task.

230

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

Completing the Database Setup

This task must be run for any applications where the PeopleSoft PeopleTools version of the database that was shipped is different than the version of PeopleSoft PeopleTools that you are running. To verify the PeopleSoft

PeopleTools release for your application database, run this SQL query: select TOOLSREL from PSSTATUS

If the PeopleTools version is not 8.55, you must run this task. Otherwise, continue to the task Running Additional

Data Mover Scripts.

Task 7-2-1: Cleaning Up Data

If your database is delivered on PeopleSoft PeopleTools 8.48 or higher, do not run this step, and instead, proceed to Deleting Performance Monitor System Default Data. If your database is delivered on PeopleSoft PeopleTools

8.47 or earlier, perform this step to clean out obsolete message data.

Warning! Performing this task when updating from PeopleSoft PeopleTools 8.48 or later will wipe out current valid data that is needed for your system to function properly.

Message functionality and structure changed as of PeopleSoft PeopleTools 8.48 and the old data is obsolete. Edit

PS_HOME\scripts\ptupgibdel.sql to delete data from the tables that only exist in the old PeopleSoft PeopleTools release. Open the script and make the following modifications, and then run the modified script using your SQL query tool:

1. Search for the string "--- End of PT8.<xx> ---" where <xx> represents the last two digits of the PeopleSoft

PeopleTools release you are upgrading from.

2. Delete the entire portion of the script below this string.

3. Save the script as <PS_HOME>\scripts\ptupgibdel8<xx>.sql where <xx> represents the last two digits of the

PeopleSoft PeopleTools release you are upgrading from, as determined in Step 1.

Important! Be sure to save the script using the naming convention shown above. This will preserve the original script for use in updating other databases at different PeopleSoft PeopleTools releases.

4. Using a SQL query tool, run the ptupgibdel8<xx>.sql script against your PeopleSoft database.

Task 7-2-2: Deleting Performance Monitor System Default Data

If your database is delivered on PeopleSoft PeopleTools 8.54 or higher, do not run this step, and instead, proceed to Creating New PeopleTools Tablespaces. If your database is delivered on PeopleSoft PeopleTools 8.45 through

8.53, perform this task to clean out obsolete message data.

Warning! Performing this task when updating from PeopleSoft PeopleTools 8.54 or later will wipe out current valid data that is needed for your system to function properly.

Truncate the PeopleTools table PSPMSYSDEFAULTS to ensure the successful completion of your installation.

Because a primary key index was added to this table as of PeopleSoft PeopleTools 8.54, the data stored in this table needs to be deleted to ensure that the index can be successfully created later in the installation.

Task 7-2-3: Creating New PeopleTools Tablespaces

Review the XXDDL.SQL tablespace creation script that was run earlier in the install process (XX is a two-letter code for your product line). Compare the contents of the script with the ptddlupg.sql script.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

231

Completing the Database Setup

Chapter 7

Work with your database administrator (DBA) to review, edit, and then run the ptddlupg.sql script to create any missing tablespaces before continuing with the installation.

See Also

"Creating a Database Manually on Windows," Editing Database Scripts

"Creating a Database on UNIX," Fulfilling PeopleSoft Database Configuration Wizard Prerequisites

"Creating a Database Manually on UNIX," Editing Database Scripts

Task 7-2-4: Updating PeopleTools System Tables

Run SQL scripts to update your PeopleSoft PeopleTools system tables to the latest PeopleSoft PeopleTools release (currently 8.55).

Use a query tool, such as Query SQL*Plus, to run SQL scripts while in the PeopleSoft database.

This procedure also includes steps to run Data Mover scripts. Depending upon the step, you run Data Mover in

"bootstrap mode" or in "user mode."

See the section Checking the Log Files and Troubleshooting, Running Data Mover in the chapters on creating a database using the Database Configuration Wizard, or creating a database manually.

To update your PeopleSoft PeopleTools system tables:

232

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

Completing the Database Setup

1. Run the appropriate SQL scripts for your application version.

The following scripts are found in the PS_HOME\scripts directory.

Use the scripts in the following table for non-Unicode databases:

Application Database Version Required Scripts for Non-Unicode Databases

8.40

rel841, rel842, rel843, rel844, rel845, rel846, rel847, rel848, rel849, rel850, rel851, rel852, rel853, rel854, and rel855

8.41

8.42

8.43

8.44

8.45

rel842, rel843, rel844, rel845, rel846, rel847, rel848, rel849, rel850, rel851, rel852, rel853, rel854, and rel855 rel843, rel844, rel845, rel846, rel847, rel848, rel849, rel850, rel851, rel852, rel853, rel854, and rel855 rel844, rel845, rel846, rel847, rel848, rel849, rel850, rel851, rel852, rel853, rel854, and rel855 rel845, rel846, rel847, rel848, rel849, rel850, rel851, rel852, rel853, rel854, and rel855 rel846, rel847, rel848, rel849, rel850, rel851, rel852, rel853, rel854, and rel855

8.46

8.47

rel847, rel848, rel849, rel850, rel851, rel852, rel853, rel854, and rel855 rel848, rel849, rel850, rel851, rel852, rel853, rel854, and rel855

Note. If you are installing ELM 9.0, run rel848n, rel849n, rel850n, rel851n, rel852n, rel853n, rel854n, and rel855n instead.

8.48

8.49

8.50

8.51

rel849, rel850, rel851, rel852, rel853, rel854, and rel855

Note. If you are installing a 9.0 or higher application, run rel849n, rel850n, rel851n, rel852n, rel853n, and rel854n, and rel855n instead.

rel850, rel851, rel852, rel853, rel854, and rel855

Note. If you are installing a 9.0 or higher application, run rel850n, rel851n, rel852n, rel853n, rel854n and rel855n instead.

rel851, rel852, rel853, rel854, and rel855

Note. If you are installing a 9.0 or higher application, run rel851n, rel852n, rel853n, rel854n, and rel855n instead.

rel852, rel853, rel854, and rel855

Note. If you are installing a 9.0 or higher application, run rel852n, rel853n, rel854n, and rel855n instead.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

233

Completing the Database Setup

Chapter 7

Application Database Version Required Scripts for Non-Unicode Databases

8.52

rel853, rel854, and rel855

Note. If you are installing a 9.0 or higher application, run rel853n, rel854n, and rel855n instead.

8.53

8.54

rel854 and rel855

Note. If you are installing a 9.0 or higher application, run rel854n and rel855n instead.

rel855

Note. If you are installing a 9.0 or higher application, run rel855n instead.

8.55

None

Use the scripts in the following table for Unicode databases:

Application Database Version Required Scripts for Unicode Databases

8.40

rel841u, rel842u, rel843u, rel844u, rel845u, rel846u, rel847u, rel848u, rel849u, rel850u, rel851u, rel852u, rel853u, rel854u, and rel855u

8.41

8.42

8.43

8.44

8.45

8.46

8.47

rel842u, rel843u, rel844u, rel845u, rel846u, rel847u, rel848u, rel849u, rel850u, rel851u, rel852u, rel853u, rel854u, and rel855u rel843u, rel844u, rel845u, rel846u, rel847u, rel848u, rel849u, rel850u, rel851u, rel852u, rel853u, rel854u, and rel855u rel844u, rel845u, rel846u, rel847u, rel848u, rel849u, rel850u, rel851u, rel852u, rel853u, rel854u, and rel855u rel845u, rel846u, rel847u, rel848u, rel849u, rel850u, rel851u, rel852u, rel853u, rel854u, and rel855u rel846u, rel847u, rel848u, rel849u, rel850u, rel851u, rel852u, rel853u, rel854u, and rel855u rel847u, rel848u, rel849u, rel850u, rel851u, rel852u, rel853u, rel854u, and rel855u rel848u, rel849u, rel850u, rel851u, rel852u, rel853u, rel854u, and rel855u

Note. If you are installing ELM 9.0, run rel848un, rel849un, rel850un, rel851un, rel852un, rel853un, and rel854un, and rel855un instead.

234

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

Completing the Database Setup

Application Database Version Required Scripts for Unicode Databases

8.48

rel849u, rel850u, rel851u, rel852u, rel853u, rel854u, and rel855u

Note. If you are installing a 9.0 or higher application, run rel849un, rel850un, rel851un, rel852un, rel853un, rel854un, and rel855un instead.

8.49

rel850u, rel851u, rel852u, rel853u, rel854u, and rel855u

Note. If you are installing a 9.0 or higher application, run rel850un, rel851un, rel852un, rel853un, rel854un, and rel855un instead.

8.50

8.51

rel851u, rel852u, rel853u, rel854u, and rel855u

Note. If you are installing a 9.0 or higher application, run rel851un, rel852un, rel853un, rel854un, and rel855un instead.

rel852u, rel853u, rel854u, and rel855u

Note. If you are installing a 9.0 or higher application, run rel852un, rel853un, rel854un, and rel855un instead.

8.52

8.53

8.54

rel853u, rel854u, and rel855u

Note. If you are installing a 9.0 or higher application, run rel853un, rel854un, and rel855un instead.

rel854u and rel855u

Note. If you are installing a 9.0 or higher application, run rel854un and rel855un instead.

rel855u

Note. If you are installing a 9.0 or higher application, run rel855un instead.

8.55

None

2. If the application database version you are installing is either 8.42 or 8.43, run the following SQL command:

DROP TABLE PS_PSMCFQUEUESLANG

Note. PS_PSMCFQUEUESLANG may not exist in some 8.43 application databases. Do not drop the table

PSMCFQUEUESLANG.

3. If the application database you are installing is 8.45 or lower, run the following SQL command:

DROP TABLE PSOPTSTATUS

4. Edit and run the grant.sql script in the PS_HOME\scripts directory. This will grant permissions to the Connect

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

235

Completing the Database Setup

Chapter 7

ID.

5. If the application database you are installing is 8.54 or lower, you are using Oracle 12c or higher, and you are using multitenant architecture, re-run the scripts to create the PeopleSoft database roles.

This will grant additional privileges to enable use of the Oracle in-memory feature in Oracle 12c and restrict certain privileges to the Access ID. a. Open PS_HOME\scripts\nt\pdb\psroles2.sql for editing and replace the variable

<PDB_SERVICE_NAME> with the PDB database name. b. Log on to SQL*Plus, connecting as the System user to the PDB.

The PDB name in this example is <PDB_SERVICE_NAME>: sqlplus system/[email protected]<PDB_SERVICE_NAME> c. Run the PSROLES.SQL script: sqlplus>@PS_HOME\scripts\nt\pdb\psroles.sql

d. Log out of SQL*Plus.

e. Log on to SQL*Plus, connecting as sysdba.

sqlplus / as sysdba f.

Run the PSROLES2.SQL script: sqlplus>@PS_HOME\scripts\nt\pdb\psroles2.sql

g. Run the following SQL command, substituting your access ID: grant PSADMIN to ACCESSID

6. If the application database you are installing is 8.54 or lower, you are using Oracle 12c or higher, and the database is non-multitenant, re-run the script to create the PeopleSoft database roles.

This will grant additional privileges to enable use of the Oracle in-memory feature in Oracle 12c and restrict certain privileges to the Access ID.

a. Log on to SQL*Plus, connecting as the System user. sqlplus system/manager b. Run the PSROLES.SQL script: sqlplus>@PS_HOME\scripts\nt\psroles.sql

c. Run the following SQL command, substituting your access ID: grant PSADMIN to ACCESSID

7. If your database is delivered on PeopleSoft PeopleTools 8.49 or earlier, run the

UPGDBOPTIONS_ENABLETIMESTAMPS.sql script in the PS_HOME\scripts directory.

This enables the usage of the TIMESTAMP data type.

8. If the application database you are installing is 8.54 or lower, invoke Data Mover in bootstrap mode, and run the encrypt.dms Data Mover script in the PS_HOME/scripts directory.

This will encrypt the operator passwords in your database.

9. With Data Mover still in bootstrap mode, run the msgtlsupg.dms Data Mover script in the PS_HOME\scripts directory.

This will update the PeopleSoft PeopleTools messages in your database.

236

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

Completing the Database Setup

10. If you are applying a required for install PeopleSoft PeopleTools patch, invoke Data Mover in user mode and run PS_HOME\scripts\PTPATCH.DMS.

11. With Data Mover still in user mode, run the storeddl.dms Data Mover script in the PS_HOME\scripts directory.

Note. Comment out the other platform-specific scripts according to your platform.

This will update your platform-specific DDL model statements.

Task 7-2-5: Updating PeopleTools Database Objects

To update PeopleSoft PeopleTools database objects to the current release you must be in Application Designer.

The Copy from File functionality lets you update your PeopleSoft PeopleTools database objects from a file. You must perform this step to bring the database objects in sync with the PeopleSoft PeopleTools release. Failure to run this step will introduce problems to your environment.

To update PeopleSoft PeopleTools database objects:

1. Launch Application Designer and sign on to your database with a valid PeopleSoft user ID.

2. Select Tools, Copy Project, From File.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

237

Completing the Database Setup

Chapter 7

3. In the resulting dialog box, change the import directory to PS_HOME\projects, select PPLTLS84CUR from the list of projects and click the Select button.

Note. If the project already exists on the database, a confirmation dialog box appears asking if you want to overwrite the existing project. Select the File radio button and click OK to overwrite the existing project.

238

Selecting Project PPLTLS84CUR in the Copy From File dialog box

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

4. The Copy From File dialog box appears.

Select all object types and then click the Options button.

Completing the Database Setup

The Copy From File dialog box showing that PPLTLS84CUR will be copied

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

239

Completing the Database Setup

5. On the Upgrade Options dialog box, select the General Options tab.

Make sure that the Keep Target Origin option is selected, as shown in this example, and click OK.

Chapter 7

Upgrade Options dialog box: General Options page

6. On the Copy from File dialog box, click the Copy button.

When the progress window disappears, the project has been copied.

If you see the following types of messages in the output window do not worry; they are acceptable because the field label properties were copied with the object definition:

• Definition Name: OPERPSWD.OPERPSWD not copied, entire definition already copied (62,32).

• Definition Name: OPRID.NEW not copied, entire definition already copied (62,32).

Task 7-2-6: Updating PeopleTools Multilingual Objects

If you are currently updating a PeopleSoft Multilingual Database, you must also apply the project

PPLTLS84CURML, which contains the translations of the PeopleSoft PeopleTools Objects.

240

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

Completing the Database Setup

Note. If the application database you are installing is 8.44 or lower and you have licensed and installed French into this database, copy the PPLTLSML project instead of the PPLTLS84CURML project for French only.

Substitute the project name PPLTLSML instead of PPLTLS84CURML in the instructions below. Copy the

PPLTLS84CURML project to update any non-French languages that are installed in the database in addition to the PPLTLSML project for French.

If your application is 8.45 or later, then you only need to copy the PPTL84CURML for all of your licensed and installed languages.

To update PeopleSoft PeopleTools database objects to the current release you must be in Application Designer.

The Copy from File functionality lets you update your PeopleSoft PeopleTools database objects from a file.

To apply the translation project for PeopleSoft PeopleTools 8.55:

1. Bring up the Configuration Manager and select the Display tab.

Ensure that the language matches the base language of your database. Always run upgrade copy as a base language user.

2. Launch Application Designer and sign on to your database with a valid PeopleSoft user ID.

3. Select Tools, Copy Project, From File.

4. In the resulting dialog box, change the import directory to PS_HOME\projects.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

241

Completing the Database Setup

Chapter 7

5. Select PPLTLS84CURML from the list of projects and click the Select button.

Note. If the project already exists on the database, a confirmation dialog box appears asking if you want to overwrite the existing project. Select the File radio button and click OK to overwrite the existing project.

Selecting Project PPLTLS84CURML in the Copy From File dialog box

6. The Copy From File dialog box appears.

Make sure that all object types are selected.

7. Click the Options button, select the Copy Options tab, and ensure that only the non-English languages you have installed are selected.

Please note that English and Common should not be selected.

8. Select the languages that you are currently installing from the Copy Options dialog box.

9. On the Upgrade Options dialog box, select the General Options tab and make sure that the Keep Target Origin option is selected.

Click OK.

242

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

10. On the Copy from File dialog box, click the Copy button.

Completing the Database Setup

The Copy From File dialog box showing that PPLTLS84CURML will be copied

When the progress dialog box disappears, the project has been copied.

Task 7-2-7: Deleting Obsolete PeopleTools Database Objects

This process removes obsolete PeopleSoft PeopleTools objects from your database. To update PeopleSoft

PeopleTools database objects to the current release you must be in Application Designer. You will use the Copy from File functionality to delete the obsolete objects from the database.

The copy process detects whether any deleted fields are in use on other objects, such as records. You may see the following kind of warning during the copy:

Field <FIELDNAME> is in use on at least one record. 

You must clean up any objects that reference the deleted field(s) after the upgrade. While PeopleTools has deleted the field as part of the new release, you may still have objects that reference this deleted field. After fixing any objects that reference this field, delete the field from your system.

To delete obsolete PeopleSoft PeopleTools database objects:

1. Launch Application Designer and sign on to your database with a valid PeopleSoft user ID.

2. Select Tools, Copy Project, From File.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

243

Completing the Database Setup

Chapter 7

3. In the resulting dialog box, change the import directory to PS_HOME\projects, select PPLTLS84CURDEL from the list of projects and click Select.

Note. If the project already exists on the database, a confirmation dialog box appears asking if you want to overwrite the existing project. Select the File radio button and click OK to overwrite the existing project.

244

Selecting Project PPLTLS84CURDEL in the Copy From File dialog box

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

4. The Copy From File dialog box appears.

Select all object types and click the Options button.

Completing the Database Setup

The Copy From File dialog box showing that PPLTLS84CURDEL will be copied

Note. If you have a multilingual database, do not change the languages that are selected by default.

5. On the Upgrade Options dialog box, select the General Options tab and make sure that the Keep Target Origin option is selected.

Click OK.

6. On the Copy from File dialog box, click the Copy button.

When the progress dialog box disappears, the project has been copied.

Task 7-2-8: Applying Patched PeopleTools Database Objects

If you are applying a required for install PeopleSoft PeopleTools patch and if a database project is included as

part of the patch, apply the database project(s) now. Make sure you apply all projects that are appropriate for your environment, including multilingual (ML) projects, if necessary. Make sure to read the patch release notes to find out if database changes are in the patch.

To update patched PeopleSoft PeopleTools database objects to the current release you must be in Application

Designer. The Copy from File functionality lets you update your PeopleSoft PeopleTools database objects from a file. You must perform this step to bring the database objects in sync with the PeopleSoft PeopleTools patch release. Failure to run this step will introduce problems to your environment.

To apply patched PeopleSoft PeopleTools database objects:

1. Launch Application Designer and sign on to your database with a valid PeopleSoft user ID.

2. Select Tools, Copy Project, From File.

3. On the Copy From File dialog box, change the import directory to PS_HOME\projects, select the patch project from the list of projects and click the Select button.

4. Follow the patch instructions to select the correct copy options. Select all object types and then click the

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

245

Completing the Database Setup

Options button.

5. On the Upgrade Options dialog box, select the General Options tab.

6. Select the Keep Target Origin option, and click OK.

7. On the Copy From File dialog box, click Copy.

When the progress window disappears, the project has been copied.

Chapter 7

Task 7-2-9: Altering PeopleTools Tables

Use the ALTER AUDIT process in this step to check whether the PeopleSoft PeopleTools tables are synchronized with the underlying SQL data tables in your database. This step uses a delivered project to compare the data structures of your database tables with the PeopleSoft PeopleTools tables to uncover inconsistencies. The ALTER

AUDIT process then reports its findings. At this point in the installation, we expect to see differences between the database structure and the PeopleSoft PeopleTools tables. You will generate and run a SQL script to synchronize the PeopleSoft PeopleTools table definitions with the underlying tables in your database.

To alter PeopleSoft PeopleTools tables:

1. Launch Application Designer with a valid PeopleSoft user ID and sign on to the installed database.

2. Select File, Open.

The Open Definition dialog box opens.

3. Select Project from the Definition drop-down list, enter PPLTLS84CUR in the name dialog box, and click

OK.

4. Select Build, Project.

The Build dialog box appears:

The Build dialog box with selections for altering tables

5. Select Create Tables and Alter Tables in the Build Options region as shown in the example above (Create

Indexes and Create Trigger will automatically be selected).

246

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

6. Select Build script file in the Build Execute Options region.

7. Click Settings.

The Build Settings dialog box appears:

Completing the Database Setup

Build Settings dialog box: Scripts tab

8. Select the Scripts tab.

9. Select Write Alter comments to script.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

247

Completing the Database Setup

Chapter 7

10. Select the Alter tab and ensure that the Adds, Changes, Renames, and Deletes check boxes are selected in the

Alter Any region.

The check box Drop column if data present should be selected in the Drop Column Options region, and the option Truncate data if field too short should be selected in the Change Column Length Options region.

Make sure that the option Alter by Table Rename is selected in the Alter Table Options region.

Build Settings dialog box: Alter tab

248

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

Completing the Database Setup

11. Select the Create tab and ensure that the options Skip table if it already exists, Recreate view if it already exists, and Recreate index only if modified options are selected.

Build Settings dialog box: Create tab

12. Click OK.

The Build dialog box reappears.

13. Click Build.

14. Click Close when the process is completed.

15. Edit the generated SQL script for the correct tablespace names and sizing parameters if you are not using delivered PeopleSoft Tablespace names.

16. Run the generated SQL script in your platform-specific query tool to bring your database structure in sync with the PeopleSoft PeopleTools tables.

Task 7-2-10: Migrating Records to New Tablespaces

This section discusses:

• Copying the Tablespace Record Project

• Running Alter Tools Tables

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

249

Completing the Database Setup

Chapter 7

Copying the Tablespace Record Project

In every PeopleSoft PeopleTools release, Oracle moves some delivered tables to different tablespaces. You must run this step to move the tables.

To copy the Tablespace Record project:

1. Launch Application Designer and sign on to your database with a valid PeopleSoft user ID.

2. Select Tools, Copy Project, From File.

3. In the resulting dialog box, change the import directory to PS_HOME\projects, select PT84TBLSPC from the list of projects, and click Select.

Note. If the project already exists on the database, a confirmation dialog box appears asking if you want to overwrite the existing project. Select the File radio button and click OK to overwrite the existing project.

250

Selecting Project PT84TBLSPC in the Copy From File dialog box

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

4. The Copy From File dialog box appears.

Select all object types and click the Options button.

Completing the Database Setup

The Copy From File dialog box showing that PT84TBLSPC will be copied

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

251

Completing the Database Setup

Chapter 7

5. On the Upgrade Options dialog box, select the General Options tab and make sure that the Take DDL from

Source and Keep Target Origin options are selected.

Click OK.

Upgrade Options dialog box: General Options tab

6. On the Copy From File dialog box, click the Copy button.

When the progress dialog box disappears, the project has been copied.

Running Alter Tools Tables

To run Alter Tools tables:

1. Launch PeopleSoft PeopleTools and sign on to Installed database.

2. From the Application Designer, select File, Open.

3. Select Project from the Definition drop-down list, enter PT84TBLSPC in the name dialog box, and click OK.

252

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

4. Select Build, Project.

The Build dialog box appears:

Completing the Database Setup

The Build dialog box

5. Select Alter Tables in the Build Options region as shown in the example above (Create Indexes and Create

Trigger will automatically be selected).

6. Select Build script file in the Build Execute Options region.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

253

Completing the Database Setup

7. Click Settings.

The Build Settings dialog box appears:

Chapter 7

Build Settings dialog box: Scripts tab

8. Select the Scripts tab.

9. Select Write Alter comments to script.

254

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

Completing the Database Setup

10. Select the Alter tab and ensure that the Adds, Changes, Renames, and Deletes check boxes are selected in the

Alter Any region, and that the Alter even if no changes check box has been selected.

Drop column if data present should be selected in the Drop Column Options region, and Truncate data if field too short should be selected in the Change Column Length Options region.

Build Settings dialog box: Alter tab

11. Click OK.

The Build dialog box reappears.

12. Click Build.

13. Click Close when the process is completed.

14. Edit the generated SQL script for the correct tablespace names and sizing parameters if you are not using delivered PeopleSoft tablespace names.

15. Run the generated SQL script in your platform-specific query tool move the tables to the correct tablespaces.

Task 7-2-11: Updating PeopleTools System Data

Data Mover scripts that update PeopleSoft PeopleTools system data are run to enable new features and load new messages for the PeopleSoft PeopleTools 8.55 release. Several of the scripts that you need to run are dependent upon the version of the application you are running.

See Understanding Database Updates.

To update PeopleSoft PeopleTools system data:

1. Invoke Data Mover by running PS_HOME\bin\client\winx86\psdmt.exe.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

255

Completing the Database Setup

Chapter 7

The PeopleSoft Logon window appears.

2. Log on using the access ID you specified when you created your Data Mover scripts with the Database Setup program.

This will start Data Mover in bootstrap mode.

256

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

Completing the Database Setup

8.49

8.50

8.51

8.52

8.53

8.54

8.55

3. Run the appropriate Data Mover scripts for your application database version.

The application database version refers to the version before you started this step. Be sure to run the scripts in the order listed. The scripts are found in the PS_HOME\scripts directory:

Application Database Version

8.40

Scripts to Run

pt841tls, pt842tls, pt843tls, pt844tls, pt845tls, pt846tls, pt847tls, pt848tls, pt849tls, pt850tls, pt851tls, pt852tls, pt853tls, pt854tls, and pt855tls

8.41

8.42

8.43

8.44

8.45

8.46

8.47

8.48

pt842tls, pt843tls, pt844tls, pt845tls, pt846tls, pt847tls, pt848tls, pt849tls, pt850tls, pt851tls, pt852tls, pt853tls, pt854tls, and pt855tls pt843tls, pt844tls, pt845tls, pt846tls, pt847tls, pt848tls, pt849tls, pt850tls, pt851tls, pt852tls, pt853tls, pt854tls, and pt855tls pt844tls, pt845tls, pt846tls, pt847tls, pt848tls, pt849tls, pt850tls, pt851tls, pt852tls, pt853tls, pt854tls, and pt855tls pt845tls, pt846tls, pt847tls, pt848tls, pt849tls, pt850tls, pt851tls, pt852tls, pt853tls, pt854tls, and pt855tls pt846tls, pt847tls, pt848tls, pt849tls, pt850tls, pt851tls, pt852tls, pt853tls, pt854tls, and pt855tls pt847tls, pt848tls, pt849tls, pt850tls, pt851tls, pt852tls, pt853tls, pt854tls, and pt855tls pt848tls, pt849tls, pt850tls, pt851tls, pt852tls, pt853tls, pt854tls, and pt855tls pt849tls, pt850tls, pt851tls, pt852tls, pt853tls, pt854tls, and pt855tls pt850tls, pt851tls, pt852tls, pt853tls, pt854tls, and pt855tls pt851tls, pt852tls, pt853tls, pt854tls, and pt855tls pt852tls, pt853tls, pt854tls, and pt855tls pt853tls, pt854tls, and pt855tls pt854tls and pt855tls pt855tls

None

4. Run the pslanguages.dms Data Mover script in the PS_HOME\scripts directory.

This script loads language-specific seed data.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

257

Completing the Database Setup

Chapter 7

5. Run the tlsupgnoncomp.dms Data Mover script in the PS_HOME\scripts directory.

This will import the updated PeopleSoft PeopleTools Trees, Roles, and Access Groups into your database.

6. If you are a Multilingual customer, from the Data Mover script that was created for your PeopleSoft database installation, find the UPDATE to PSLANGUAGES.

The statement should look similar to the following, where xxx is one of the PeopleSoft three-letter language code identifiers, as described earlier:

UPDATE PSLANGUAGES SET INSTALLED=1 WHERE LANGUAGE_CD = 'xxx';

See "Preparing for Installation," Planning Multilingual Strategy.

Run the SQL command identified above using your SQL tool.

7. Open Data Mover using a valid PeopleSoft Operator ID, such as PS for Human Capital Management or VP1 for Financials/Supply Chain Management.

8. If you are a Multilingual customer and have licensed non-English languages, run the pt855tlsxxx.dms scripts in the PS_HOME\scripts directory.

This will update the language-specific PeopleSoft PeopleTools system data in your database.

Note. The portion of the script name xxx is equivalent to the language code (that is, FRA, CFR, GER, JPN, and so on) of the non-English languages you have installed. There will be a Data Mover script for each non-

English language.

9. Run the msgtleng.dms Data Mover Script in the PS_HOME\scripts directory.

Non-English message data was loaded in the pt855tlsxxx.dms scripts. This will update the messages in your database.

10. Run the ptstreng.dms Data Mover script in the PS_HOME\scripts directory.

Non-English system data was loaded in the pt855tlsxxx.dms scripts. This will update the SQR strings in your database.

11. Run the storept.dms Data Mover script in the PS_HOME\src\cbl\base directory.

This will update your PeopleSoft PeopleTools COBOL stored statements.

12. Run the ptdefnsec.dms Data Mover script in the PS_HOME\scripts directory.

This will update the PeopleSoft PeopleTools Definition Security group.

13. If the application database you are installing is PeopleSoft PeopleTools 8.53 or later, you must compile all directive PeopleCode in your database. Execute the following command on your database to run PeopleSoft

Application Designer in quiet mode. From the DOS command line, the syntax is:

<PS_HOME>\bin\client\winx86\pside.exe -CT ORACLE -cD <dbname> -CS⇒

 <database server name> -CO <oprid> -CP <pswd> -SS NO -QUIET -HIDE -⇒

CMPDIRPC -LF <full path of log file>

14. Run the createvw.dms Data Mover script in the PS_HOME\scripts directory.

This will recreate all the views in your database.

Task 7-2-12: Running PeopleTools Conversions

This section discusses:

• Understanding Usage of Application Engine Programs

• Converting Portal Objects

258

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

• Converting Setup Manager

• Converting Navigation Collection and Pagelet Wizard Data

• Converting Additional Pagelet Wizard Data

• Populating the Feed Options Table

• Updating Feeds for Active Data Guard

• Updating Web Profiles

• Updating Chart and Grid Filters

• Populating the Hash Values

• Migrating the Authorization Configuration Data

• Populating BI Publisher Templates with Object Owner ID Values

• Creating the NavBar and Adding Default Tiles

• Populating the DB-Cache Lock Table

Completing the Database Setup

Understanding Usage of Application Engine Programs

You run several Application Engine programs in this section. For information on Application Engine, including how to use and restart Application Engine programs, consult the Application Engine documentation.

See PeopleTools: Application Engine.

Converting Portal Objects

Perform this step if the application database you are installing is PeopleSoft PeopleTools 8.43 or earlier. The

Application Engine program UPG844PORTAL splits PSPRSMDEFN.PORTAL_URLTEXT into segments. This is performed for PeopleSoft Components URLs to extract Menu, Component, and Market information. Record,

Field, Event, and Function Names are extracted from Iscript URLs. This program must be run by a PeopleSoft user with the Portal Administrator or PeopleSoft Administrator role. The following SQL will identify which users have the PeopleSoft Administrator or Portal Administrator roles: select ROLEUSER, ROLENAME from PSROLEUSER where ROLENAME in ('PeopleSoft⇒

 Administrator','Portal Administrator')

Run the UPG844PORTAL Application Engine program on your database. From the DOS command line, the syntax is:

<PS_HOME>\bin\client\winx86\psae -CD <dbname> -CT ORACLE -CO <oprid> -CP⇒

 <pswd> -R INSTALL -AI UPG844PORTAL

Use the values for the database name and user ID that you entered on the startup tab of the Configuration Manager for <dbname> and <oprid>, respectively. However, be aware that <pswd> is not the same as the connect password that you entered on the Configuration Manager startup tab. Enter a value for <pswd> that is the password you want to be associated with the <oprid>.

See "Setting Up the Install Workstation."

You may see some of the following errors when running this Application Engine program:

Not authorized CRef: <Portal Object Name> (95,5032).

This means that you do not have proper privileges to run this conversion. The user ID that you are using to run this conversion needs to have Portal Administrator permissions.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

259

Completing the Database Setup

Chapter 7

Security synchronization failed for Portal Object: <Portal Object Name>

(96,61).

This is not a fatal error. It may be caused by a content reference that contains invalid URL text and indicates that there was an internal error writing to the security table. The invalid URL text may be pointing to a component or script that does not exist in the database. If you receive this error, search the Patches and

Downloads section of My Oracle Support for Required at Install patches for your application and apply the patches after installing your database.

Cref <Portal Object Name> points to Menu: <Menu Name>, Component

<Component Name> which doesn't exist. (96,80).

The content reference is pointing to an invalid Menu/Component combination. If you receive this error, search the Patches and Updates section of My Oracle Support for Required at Install patches for your application and apply the patches after installing your database.

See "Preparing for Installation," Reviewing Patches and Updates Required at Installation.

See PeopleTools: Portal Technology.

Converting Setup Manager

Perform this step if the application database you are installing is PeopleSoft PeopleTools 8.45 or earlier. The application engine program UPGPTSMDAT upgrades Setup Manager Version 1 (shipped with Fin SCM 8.8,

CRM 8.9, and with HCM 8.9) to Setup Manager Version 2 (shipped with PeopleSoft PeopleTools 8.46 and above). The program moves all data from Setup Manager Version 1 tables to Version 2 tables.

The application engine program was designed so that it can be run in any database, and can be rerun in the same database. In either case, it will determine if there is data to convert and run as appropriate. For detailed information, see comments attached to the Steps and Actions in this Application Engine Program within

Application Designer. This program must be run by a PeopleSoft user with PeopleSoft Administrator role.

Run the UPGPTSMDAT Application Engine program on your database. From the DOS command line, the syntax is:

<PS_HOME>\bin\client\winx86\psae -CD <dbname> -CT ORACLE -CO <oprid> -CP⇒

 <pswd> -R INSTALL -AI UPGPTSMDAT

Converting Navigation Collection and Pagelet Wizard Data

Perform this step if the application database you are installing is PeopleSoft PeopleTools 8.45 or earlier. The application engine program UPGPT846PP adds Navigation Collection and Pagelet Wizard data from the

Common Components and PeopleSoft Applications Portal storage tables into PeopleSoft PeopleTools tables.

The application engine program performs the following conversions:

1. Moves data from Common Components tables to PeopleSoft PeopleTools tables.

2. Moves data from PeopleSoft Applications Portal tables to PeopleSoft PeopleTools tables.

3. Updates the registry definitions to enable displaying Navigation pages.

4. Adds, updates, and deletes the Navigation Collections folders and content references in the portal registry to the new structures.

5. Converts Pagelet Wizard definitions to the PeopleSoft PeopleTools Pagelet Wizard version.

6. Renames Navigation Collection and Pagelet Wizard portal registry attributes to the PeopleSoft PeopleTools attribute names.

This program must be run by a PeopleSoft user with the Portal Administrator or PeopleSoft Administrator role.

260

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

Completing the Database Setup

Run the UPGPT846PP Application Engine program on your database. From the DOS command line, the syntax is:

<PS_HOME>\bin\client\winx86\psae -CD <dbname> -CT ORACLE -CO <oprid> -CP⇒

 <pswd> -R INSTALL -AI UPGPT846PP

You may see the following error when running this Application Engine program:

You are not authorized for the <objecttype>...

This means that you do not have proper privileges to run this conversion. The user ID that you are using to run this conversion needs to have Portal Administrator permissions.

You can ignore any other errors encountered on Oracle-delivered objects at this time. Check the Patches and

Downloads section of My Oracle Support for Required at Install patches for your application and apply the patches after installing your database. You can safely rerun UPGPT846PP to check for any remaining errors after applying patches.

Converting Additional Pagelet Wizard Data

Perform this step if the application database you are installing is PeopleSoft PeopleTools 8.47 or earlier. The application engine program UPGPT848PP adds the following Pagelet Wizard data sources from PeopleSoft

Applications Portal to PeopleSoft PeopleTools: IB Connector, Integration Broker, SOAP, and URL. In addition, the application program transforms the WSRP Portlets created in PeopleSoft PeopleTools 8.46 or 8.47 versions of

Pagelet Wizard. The process includes the following:

• Move data from PeopleSoft Applications Portal tables to PeopleSoft PeopleTools tables.

• Convert WSRP Portlets created by Pagelet Wizard to the new version.

This program must be run by a PeopleSoft user with the Portal Administrator or PeopleSoft Administrator role.

Run the UPGPT848PP Application Engine program on your database. From the DOS command line, the syntax is:

<PS_HOME>\bin\client\winx86\psae -CD <dbname> -CT ORACLE -CO <oprid> -CP⇒

 <pswd> -R⇒

 INSTALL -AI UPGPT848PP

You may see the following error when running this Application Engine program:

You are not authorized for the <objecttype>...

This means that you do not have proper privileges to run this conversion. The user ID that you are using to run this conversion needs to have Portal Administrator permissions.

You can ignore any other errors encountered on Oracle-delivered objects at this time. Check the Patches and

Downloads section of My Oracle Support for Required at Install patches for your application and apply the patches after installing your database. You can safely rerun UPGPT848PP to check for any remaining errors after applying patches.

Populating the Feed Options Table

The Application Engine program UPGPT850PTFP populates the feed options table PS_PTFP_OPTIONS if it is empty.

Run the UPGPT850PTFP Application Engine program on your database. From the DOS command line, the syntax is:

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

261

Completing the Database Setup

Chapter 7

<PS_HOME>\bin\client\winx86\psae -CD <dbname> -CT ORACLE -CO <oprid> -CP⇒

 <pswd> -R INSTALL -AI UPGPT850PTFP

Updating Feeds for Active Data Guard

The Application Engine program UPGPT852PTFP updates Service Operations used by Feeds for Active Data

Guard support.

Run the UPGPT852PTFP Application Engine program on your database. From the DOS command line, the syntax is:

<PS_HOME>\bin\client\winx86\psae -CD <dbname> -CT ORACLE -CO <oprid> -CP⇒

 <pswd> -R INSTALL -AI UPGPT852PTFP

Updating Web Profiles

The Application Engine Program UPGPTWBPFNVP migrates the web profile properties from the

PT_PROPVALUE field to the PT_LPROPVALUE field for the PSWEBPROFNVP record.

Run the UPGPTWBPFNVP Application Engine program on your database. From the DOS command line, the syntax is:

<PS_HOME>\bin\client\winx86\psae -CD <dbname> -CT ORACLE -CO <oprid> -CP⇒

 <pswd> -R INSTALL -AI UPGPTWBPFNVP

Updating Chart and Grid Filters

The Application Engine program UPGPTPGFLRS upgrades the Pivot Grid and chart filters from the

PSPGVIEWOPT record into the new long filter fields. The grid filters are updated in the

PTPG_FLRS_GRID_EX field on the PSPGVIEWOPT record and the chart filters are updated in the

PTPG_FLRS_CHART_EX field on the PSPGCHRTFLRSOPT record.

Run the UPGPTPGFLRS Application Engine program on your database. From the DOS command line, the syntax is:

<PS_HOME>\bin\client\winx86\psae -CD <dbname> -CT ORACLE -CO <oprid> -CP⇒

 <pswd> -R INSTALL -AI UPGPTPGFLRS

Populating the Hash Values

The Application Engine program UPGPTHASH populates the hash columns on PSPCMTEXT and PSSQLHASH if they are empty.

Run the UPGPTHASH Application Engine program on your database. From the DOS command line, the syntax is:

<PS_HOME>\bin\client\winx86\psae -CD <dbname> -CT ORACLE -CO <oprid> -CP⇒

 <pswd> -R INSTALL -AI UPGPTHASH

262

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

Completing the Database Setup

Migrating the Authorization Configuration Data

Perform this step if the application database you are installing is PeopleSoft PeopleTools 8.53 or earlier. The

Application Engine program UPGPT854AUTH migrates the authorization configuration data from

PTCAC_AUTHCONF to PTCAC_AUTHORIZE.

Run the UPGPT854AUTH Application Engine program on your database. From the DOS command line, the syntax is:

<PS_HOME>\bin\client\winx86\psae -CD <dbname> -CT ORACLE -CO <oprid> -CP⇒

 <pswd> -R INSTALL -AI UPGPT854AUTH

Populating BI Publisher Templates with Object Owner ID Values

Perform this step if the application database you are installing is PeopleSoft PeopleTools 8.53 or earlier. The

Application Engine program UPGPTXPTMPL populates Oracle Business Intelligence Publisher (BI Publisher) templates with owner ID values.

Run the UPGPTXPTMPL Application Engine program on your database. From the DOS command line, the syntax is:

<PS_HOME>\bin\client\winx86\psae -CD <dbname> -CT ORACLE -CO <oprid> -CP⇒

 <pswd> -R INSTALL -AI UPGPTXPTMPL

Creating the NavBar and Adding Default Tiles

Perform this step if the application database you are installing is PeopleSoft PeopleTools 8.53 or earlier. The

Application Engine program UPGPT855NUI creates the Fluid User Interface navigation bar (NavBar) and adds default tiles if they do not exist.

See PeopleTools: Application User's Guide, "Working with Fluid Homepages."

Run the UPGPT855NUI Application Engine program on your database. From the DOS command line, the syntax is:

<PS_HOME>\bin\client\winx86\psae -CD <dbname> -CT ORACLE -CO <oprid> -CP⇒

 <pswd> -R INSTALL -AI UPGPT855NUI

Populating the DB-Cache Lock Table

The Application Engine program UPGPT851DBC populates the DB Cache lock table PSOBJCACHELOCK.

Run the UPGPT851DBC Application Engine program on your database. From the DOS command line, the syntax is:

<PS_HOME>\bin\client\winx86\psae -CD <dbname> -CT ORACLE -CO <oprid> -CP⇒

 <pswd> -R INSTALL -AI UPGPT851DBC

Task 7-2-13: Converting Integration Broker

This section discusses:

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

263

Completing the Database Setup

Chapter 7

• Updating Integration Broker Defaults

• Creating Integration Broker Objects

• Saving Application Messaging Objects

• Exporting Node Transactions

• Deleting Application Messaging Objects

• Deleting Node Transactions

If your database is delivered with PeopleSoft PeopleTools 8.48 or higher, do not run this task since the database is already delivered with the new Integration Broker objects as of PeopleSoft PeopleTools 8.48. Instead, proceed to

Running Additional PeopleTools Conversions.

Updating Integration Broker Defaults

User-level node security and transactional security have been added as of PeopleSoft PeopleTools 8.48. Service namespace information, a low-level user on the node, and a low-level permission list for service operations, need to be specified. Edit PS_HOME\scripts\ptibupgrade.dms and make the necessary modifications as documented in the script. Consult with your Integration Broker specialist for assistance.

Open Data Mover using a valid PeopleSoft Operator ID and run this script.

Creating Integration Broker Objects

The application engine program UPGPT848IBUG converts Application Package metadata into Integration Broker metadata. It also creates the projects PTUPGIBCLONE and PTUPGIBDELETE, and the script ptupg_trx.dms.

Note. Conversion errors in the Application Engine log file will be resolved by applying application-specific

Required for Install patches.

Run the UPGPT848IBUG Application Engine program on your database. From the DOS command line, the syntax is:

<PS_HOME>\bin\client\winx86\psae -CD <dbname> -CT ORACLE -CO <oprid> -CP⇒

 <pswd> -R⇒

 INSTALL -AI UPGPT848IBUG

Saving Application Messaging Objects

The PTUPGIBCLONE project was created by the UPGPT848IBUG Application Engine program and contains objects that were successfully converted. Copy this project to a directory of your choice where it will not be overwritten. The objects are copied to file as a precautionary measure since you will delete them from the database in a subsequent step.

To save Application Messaging Objects:

1. Launch Application Designer and sign on to your database with a valid PeopleSoft user ID.

2. From the Application Designer, select File, Open.

3. Select Project, enter PTUPGIBCLONE in the name dialog box, and click OK.

4. Select Tools, Copy Project, To File.

5. In the resulting dialog box, change the export directory to one of your choice, and click Copy.

When the progress dialog box disappears, the project has been copied to the specified location.

264

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

Completing the Database Setup

Exporting Node Transactions

Open Data Mover using a valid PeopleSoft Operator ID and run the script PS_HOME\ scripts\ptupg_trx_export.dms to save the old pre-conversion node transaction data.

Deleting Application Messaging Objects

Delete the obsolete pre-conversion object definitions from the database by first copying the PTUPGIBDELETE project to file, and then copying the same project from file. This project was created by the UPGPT848IBUG

Application Engine program and contains the same objects as PTUPGIBCLONE.

To delete Application Messaging Objects:

1. Launch Application Designer and sign on to your database with a valid PeopleSoft user ID.

2. From the Application Designer, select File, Open.

3. Select Project, enter PTUPGIBDELETE in the name dialog box, and click OK.

4. Select Tools, Copy Project, To File.

5. In the resulting dialog box, change the export directory to the same one you used for PTUPGIBCLONE, and click Copy.

When the progress dialog box disappears, the project has been copied to the specified location.

6. Select Tools, Copy Project, From File.

7. In the resulting dialog box, change the import directory to the previously specified directory, select

PTUPGIBDELETE from the list of projects, and click Select.

Note. Because the project already exists on the database, a confirmation dialog box appears asking if you want to overwrite the existing project. Select the File radio button and click OK to overwrite the existing project.

8. Select all object types and click the Copy button.

When the progress dialog box disappears, the project has been copied. The actions in the project are set to

Delete, so this will delete the obsolete pre-conversion object definitions from the database.

Deleting Node Transactions

The script ptupg_trx.dms is generated by the UPGPT848IBUG Application Engine program. This script can be found in the location specified in the OUTPUT variable set in Configuration Manager.

To view the OUTPUT variable:

1. Open Configuration Manager.

2. Select the Profile tab.

3. Click Edit to open the Default profile.

4. Select the Process Scheduler tab.

5. Examine the Output Directory value.

Open Data Mover using a valid PeopleSoft Operator ID and run this script to remove obsolete node transaction data associated with the obsolete objects in the PTUPGIBDELETE project.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

265

Completing the Database Setup

Chapter 7

Task 7-2-14: Running Additional PeopleTools Conversions

The Application Engine program UPGPTSERVOPR converts WSDL and Schema data.

Run the UPGPTSERVOPR Application Engine program on your database. From the DOS command line, the syntax is:

<PS_HOME>\bin\client\winx86\psae -CD <dbname> -CT ORACLE -CO <oprid> -CP⇒

 <pswd> -R⇒

 INSTALL -AI UPGPTSERVOPR

Task 7-3: Running Additional Data Mover Scripts

To import additional data for your specific PeopleSoft database, or to make other required changes, you may need to run additional Data Mover scripts. These script files have the extension .dms and are sometimes referred to as

"DMS scripts." They are located in the PS_HOME\scripts directory of your file server, and need to be run from the file server by means of Data Mover.

For the details on which additional application-specific Data Mover scripts to run, consult your applicationspecific installation instructions.

If you have installed a language other than English, you may need additional instructions on language-specific

Data Mover scripts.

See Installing a Multilingual PeopleTools System Database.

Task 7-4: Installing a Multilingual PeopleTools System Database

This section discusses:

• Understanding the Multilingual Database Project

• Applying the Multilingual Database Project

• Populating the Translated System Data

Understanding the Multilingual Database Project

The information in this section applies if you are installing a multilingual PeopleSoft PeopleTools System database. If not, skip this task and go on to the task "Running VERSION Application Engine Program." If you are installing an application database (for example, HCM, FSCM, EPM, and so on), you do not need to run this task.

If you are adding a new (Oracle-delivered) language to the PTSYS database, you must execute this step for that language. For example, if you want to add Polish to your current multilingual database, you should install Polish from PPLTLSML so you will get all objects. Using the PPLTLS84CURML project to "upgrade" your database will not provide all the necessary objects.

If you are installing a PeopleSoft PeopleTools System database and you want it to be multilingual, you need to perform the steps in the following section after the database has been loaded with Data Mover.

See Applying the Multilingual Database Project.

Note. When you log onto the multilingual database, be sure to select the base language of the database.

266

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

Completing the Database Setup

Task 7-4-1: Applying the Multilingual Database Project

This procedure describes how to apply the multilingual database project that contains translations of the

PeopleSoft PeopleTools objects.

To apply the multilingual database project:

1. Launch Application Designer.

2. Select Tools, Copy Project, From File.

3. In the resulting dialog box, change the import directory to PS_HOME\projects.

4. Select PPLTLSML from the list of projects and click the Open button.

5. In the Upgrade Copy dialog box, make sure that all object types are selected.

6. Click the Options button, select the Copy Options tab, and ensure that only the non-English languages you have installed are selected.

Please note that English and Common should not be selected.

7. Select the languages that you are currently installing from the Copy Options dialog box.

8. Click the Copy button.

(The Reset Done Flags check box will be selected; accept this default.)

Task 7-4-2: Populating the Translated System Data

To populate the translated system data:

Note. You need to run the following script in User mode.

1. Launch Data Mover.

2. Open the pt855tlsxxx.dms script using File, Open.

3. Select File, Run

Note. The portion of the script name xxx is equivalent to the language code (that is, FRA, CFR, GER, JPN, and so on) of the languages you have installed. There will be a Data Mover script for each language.

Task 7-5: Running VERSION Application Engine Program

Run the VERSION Application Engine program on your database. From the command line utility, the syntax is:

<PS_HOME>\bin\client\winx86\psae -CD <dbname>  -CT ORACLE -CO <userid> -CP⇒

 <userpswd> -R RESETVERSIONS  -AI VERSION

Use the values for the database name and user ID that you entered on the startup tab of the Configuration Manager for <dbname> and <userid> respectively. However, be aware that <userpswd> is not the same as the connect password you entered on the Configuration Manager startup tab. Enter a value for <userpswd> that is the password associated with the <userid>.

Note. Do not change the parameter

R RESETVERSIONS

. This value is required for the run control ID for this task.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

267

Completing the Database Setup

See "Setting Up the Install Workstation."

Chapter 7

Task 7-6: Running SQR Reports

This section discusses:

• Understanding Running SQR Reports

• Running SQRs on the Client Workstation

• Creating a Shortcut to Run SQRs

Understanding Running SQR Reports

The instructions in this section describe how to run SQR reports from the client workstation. On the Microsoft

Windows client, you may prefer to create a shortcut to allow you to run the reports repeatedly. You can use these instructions to run SQRs required in the upcoming task Checking the Database.

You can also choose to run SQR reports from the command line in console mode. Before running SQR from the command line on Microsoft Windows operating systems, set PS_HOME from the prompt. For example: set PS_HOME=C:\PT855

See Also

PeopleTools: SQR for PeopleSoft Developers

PeopleTools: SQR Language Reference for PeopleSoft

Task 7-6-1: Running SQRs on the Client Workstation

To run an SQR on the client workstation:

1. Select Start, Run, click Browse, and navigate to PS_HOME\bin\sqr\ORA\binw.

Select sqrw.exe and click Open.

268

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

Completing the Database Setup

2. Add any needed flags at the end of the command line.

Refer to the table that follows. For those flags that require attributes, append the attributes to the flags with no intervening spaces (for example,

–fE:\fsdmo\bin\sqr\pssqr.ini).

Microsoft Windows Run dialog box launching SQRW

The following table summarizes the SQR report arguments used by PeopleSoft software. (For a full listing of report arguments, press the Help button to view the SQR help topic for this dialog box.)

Flag

-I

Description

Specifies the directories that SQR will search for the #INCLUDE files. (A trailing slash is required.)

-f

-ZIF

-keep

-printer:ht

Specifies the directory where the report output will be sent.

If you use the

–keep flag, you must specify the directory with a trailing slash.

If you use the

–printer flag, specify a full pathname with a filename for the HTML file.

Sets the full path and name of the SQR initialization file. The -ZIF flag should point to your PS_HOME\sqr\pssqr.ini file.

Keeps the .SPF file after the program runs. This enables you to view the report with the SQR viewer.

Generates the output file in HTML format. Specify the filename, with path location, with the

–f flag.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

269

Completing the Database Setup

Chapter 7

3. Click OK.

The SQR for PeopleSoft V8.55 dialog box appears, displaying the attributes that you entered in the Run dialog box. The fields on this dialog box are described in the next step:

Note. The report arguments in this example have been arranged for readability.

SQR for PeopleSoft dialog box with DDDAUDIT.SQR

4. Enter the following values:

• Enter the report name.

You must specify the full path.

• Enter the access ID in the Username field.

• Enter the access password in the Password field.

• Enter the database name.

5. Click OK to run the SQR report.

Note. In the Properties dialog box for your SQR icon, make sure that the Start in path points to your Oracle connectivity on the Shortcut tab. If you take the default, you may see a misleading error message about TNS packet writer failure.

Task 7-6-2: Creating a Shortcut to Run SQRs

If you think you may need to run the SQR reports more than once, you may want to create a shortcut on the

Windows client workstation. To save the report arguments:

1. Open Windows Explorer on the machine on which you want to run SQR.

2. Navigate to PS_HOME\bin\sqr\ORA\binw.

3. Right-click sqrw.exe and click Create Shortcut.

4. Right-click the shortcut that you just created and select Properties.

5. On the Shortcut tab, add the same sqr flags that you used in the previous task after sqrw.exe in the Target entry box.

6. Click OK.

270

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

Completing the Database Setup

7. To run the report, double-click the shortcut and specify the following information in the dialog box:

• Report Name: Enter the full path and the name.

• Database name

• Username: Enter the access ID.

• Password: Enter the access password.

• Report arguments: Make any necessary modifications to the saved arguments.

8. Click OK.

Task 7-7: Checking the Database

Run and examine the SQR reports to verify that your database is complete.

See Running SQR Reports.

To verify that the database is complete, run the following SQR reports from the PS_HOME\sqr directory:

• dddaudit.sqr

• sysaudit.sqr

• swpaudit.sqr, if you plan to swap your base language

For further information about these reports, consult PeopleSoft product documentation. This documentation includes specific information on how to interpret the reports and how to fix any errors found there.

It is good practice to run and read the audit reports, which include sysaudit, dddaudit, swpaudit, and alter audit, after making changes such as applying patches, bundles, and upgrades to the database, to make sure that the tables are internally and externally in synch. It is also a good idea to schedule regular maintenance, for example weekly, in which you run and review the reports. You can find information on these audit reports in the PeopleTools:

Data Management product documentation.

See PeopleTools: Global Technology, "Running the Swap Audit Report."

You can greatly improve the performance and run time of the sysaudit.sqr run by making the following configuration changes to the Oracle init.ora for your SID: db_file_multiblock_read_count = 16 db_block_buffers = 2000 or greater log_checkpoint_interval = 9999999 log_buffer = 102400

If you are using rollback segments, you may also want to increase the size of the RBSBIG rollback segment to

500 MB.

Note. If any records show up in the VIEWS-2 or TABLE-3 section of dddaudit and are contained within the

PPLTLS84CURDEL project, you may safely drop these records using the SQL query tool for your platform.

See Also

PeopleTools: Data Management

PeopleTools: System and Server Administration

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

271

Completing the Database Setup

Chapter 7

Task 7-8: Running SETSPACE.SQR

Run the SETSPACE.SQR script to populate or synchronize Tablespace information with the system catalog. To run SETSPACE.SQR:

1. Using the instructions provided earlier, run SETSPACE.SQR from the PS_HOME\SQR directory.

See Running SQR Reports.

Note. Your results will vary depending on the application you are loading. The dialog box example shown here is typical. The report arguments in this example have been arranged for readability.

SQR for PeopleSoft dialog box with setspace.sqr

2. Click OK.

3. As SETSPACE.SQR runs you see a progress indicator similar to the following.

Set Table Space Name in PSRECTBLSPC

 Table PSRECTBLSPC column DDLSPACENAME have been updated

 with the tablespace found in the system catalog table.

 The total number of records updated appears at the bottom of this⇒

 report.

Recname          New DDLSpaceName   Old DDLSpaceName

---------------  ----------------   ----------------

 This phase of SETSPACE will sync up the PSRECTBLSPC and

 PSTBLSPCCAT tables

PSRECTBLSPC Records Updated:     0

PSTBLSPCCAT Records Inserted:    0

Ending SQR.

272

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

Completing the Database Setup

Task 7-9: Running Alter Audit

Use the ALTER AUDIT process to check whether the PeopleSoft PeopleTools tables are synchronized with the underlying SQL data tables in your database. This process compares the data structures of your database tables with the PeopleSoft PeopleTools tables to uncover inconsistencies. The ALTER AUDIT process then reports its findings. At this point of time in the install, we do not expect to see differences between the database structure and the PeopleSoft PeopleTools tables.

Note. If your application database was delivered on the PeopleSoft PeopleTools release you are installing, this task is optional.

Note. Triggers are always dropped and re-created during the alter process and will always show up in the generated Alter Audit script. You can ignore the generated script for triggers.

To alter PeopleSoft PeopleTools tables:

1. Launch Application Designer and sign on to the installed database with a valid PeopleSoft user ID.

2. Select File, New.

3. Select Project and click OK.

4. Select Insert, Definitions into Project.

5. Select Records from the Definition Type drop-down list box.

6. Select Table from the Type drop-down list box.

7. Click Insert, and then click Select All.

8. Click Insert, and then click Close.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

273

Completing the Database Setup

9. Select Build, Project.

The Build dialog box appears:

Chapter 7

The Build dialog box

10. Select Create Tables and Alter Tables in the Build Options region (Create Indexes and Create Trigger will automatically be selected).

11. Select Build script file in the Build Execute Options region.

274

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

12. Click Settings.

The Build Settings dialog box appears:

Completing the Database Setup

Build Settings dialog box: Scripts tab

13. Select the Scripts tab.

14. Select Write Alter comments to script.

15. Enter a unique output file name for each type.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

275

Completing the Database Setup

Chapter 7

16. Select the Alter tab and ensure that the Adds,Changes,Renames, and Deletes check boxes are selected in the

Alter Any region.

Drop column if data present should be selected in the Drop Column Options region, and Truncate data if field too short should be selected in the Change Column Length Options region.

Make sure that Alter by Table Rename is selected in the Alter Table Options region.

Build Settings dialog box: Alter tab

276

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 7

Completing the Database Setup

17. Select the Create tab, and ensure that the options Skip table if it already exists, Recreate view if it already exists, and Recreate index only if modified are selected.

Build Setting dialog box: Create tab

18. Click OK.

The Build dialog box reappears.

19. Click Build.

20. Click Close when the process is completed.

21. Edit the generated SQL script for the correct tablespace names and sizing parameters if you are not using delivered PeopleSoft tablespace names.

22. Run the generated SQL scripts in your platform-specific query tool to bring your database structure in sync with the PeopleTools tables.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

277

Chapter 8A

Configuring the Application Server on

Windows

This chapter discusses:

• Understanding the Application Server

• Prerequisites

• Preparing the Application Server File System for a PeopleTools-Only Upgrade

• Setting Up COBOL for Remote Call

• Verifying Database Connectivity

• Creating, Configuring, and Starting an Initial Application Server Domain

Understanding the Application Server

The information in this chapter is provided to help you configure your PeopleSoft application server.

Note. COBOL is not needed for PeopleSoft PeopleTools or for PeopleSoft Applications that contain no COBOL programs. Check the information on My Oracle Support, and your application-specific documentation, for the details on whether your application requires COBOL.

Oracle supports a Microsoft Windows application server to use with any of our supported databases for the

PeopleSoft installation. For detailed information, consult the certification information on My Oracle Support. The application server support can be found on the certification pages for PeopleSoft systems.

You can install the application server using either a "logical" or "physical" three-tier configuration.

• Installing the application server on the same machine as the database server is known as a logical three-tier configuration. For your initial PeopleSoft installation, Oracle suggests that you install a logical configuration to simplify setup.

• Installing the application server on a machine separate from the database server machine is known as a physical three-tier configuration.

The configuration and log files for application server domains reside in PS_CFG_HOME. If you do not set a

PS_CFG_HOME environment variable before beginning the application server configuration, the system installs it in a default location based on the current user's settings, as follows:

%USERPROFILE%\psft\pt\<peopletools_version>

See "Preparing for Installation," Defining Installation Locations.

Note. You can start application servers as a Windows service, which means that administrators no longer need to manually start each application server that runs on a Windows machine.

279

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Configuring the Application Server on Windows

Chapter 8A

See Also

"Preparing for Installation," Understanding PeopleSoft Servers and Clients

"Setting Up Process Scheduler on Windows," Starting Process Scheduler as a Windows Service

PeopleTools: System and Server Administration, "Using PSADMIN Menus"

PeopleTools: Data Management

My Oracle Support, Certifications

"Setting Up the Install Workstation"

"Installing and Compiling COBOL on Windows"

Prerequisites

Before beginning this procedure, you should have completed the following tasks:

• Installed your application server.

See "Using the PeopleSoft Installer," Planning Your Initial Configuration.

• Installed the supported version of Oracle Tuxedo

See "Installing Additional Components."

• Granted authorization to a PeopleSoft user ID to start the application server.

The database configuration procedure includes a step for setting up the user ID with authorization to start the application server. See the application-specific installation instructions for information on the user IDs for your PeopleSoft application. See the PeopleTools: Security Administration product documentation for information on PeopleSoft PeopleTools delivered user profiles.

See "Creating a Database on UNIX," Running the Database Configuration Wizard.

See "Creating a Database Manually on Windows," Creating Data Mover Import Scripts.

See "Creating a Database Manually on UNIX," Creating Data Mover Import Scripts.

• Run the following SQL statements on your database server to review and if needed, update the

PSCLASSDEFN table:

SELECT CLASSID, STARTAPPSERVER FROM PSCLASSDEFN

WHERE CLASSID IN (SELECT OPRCLASS FROM PSOPRCLS WHERE OPRID='<OPRID>')

UPDATE PSCLASSDEFN SET STARTAPPSERVER=1 WHERE CLASSID='<CLASSID>'

Note. Installers typically use VP1 or PS to test the application server. If these users are deleted or their passwords are changed, the application server will no longer be available. To avoid this problem, you can set up a new operator (called PSADMIN or PSASID, for instance) with privileges to start the application server. If you do this, you can use the new operator for your application servers and you won't need to change the password each time

VP1 or PS is changed.

280

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 8A

Configuring the Application Server on Windows

Task 8A-1: Preparing the Application Server File System for a

PeopleTools-Only Upgrade

When performing the installation of the separate upgrade PS_HOME (which is different than your old release

PS_HOME), you may configure your Application Server at this point in time of the installation. Do not boot your

Application Server until directed to do so within the upgrade. If you are installing into an old PS_HOME or

PS_CFG_HOME after completing a PeopleTools-only upgrade, review your old PS_HOME or PS_CFG_HOME for configuration files that you may want to reuse for the new PeopleSoft PeopleTools release.

See Also

"Preparing for Installation," Preparing for the PeopleTools-Only Upgrade

Task 8A-2: Setting Up COBOL for Remote Call

Remote Call is a PeopleCode feature that launches a COBOL program from an application server, PeopleCode program or a batch Application Engine PeopleCode program and waits for it to complete execution before continuing. The execution of a COBOL program via Remote Call is completely independent of the Process

Scheduler. You need to set up a COBOL runtime environment and COBOL executables on the application server to support Remote Call.

See "Installing and Compiling COBOL on Windows."

Note. If your application does not contain COBOL programs, you do not need to purchase or compile COBOL.

Task 8A-3: Verifying Database Connectivity

Before continuing, it is critical to verify connectivity to the database that the application server domain will use.

To verify connectivity, connect to the database server from the application server using the native SQL tool on the application server.

For Oracle use SQL*Plus.

Task 8A-4: Creating, Configuring, and Starting an Initial

Application Server Domain

This section discusses:

• Creating, Configuring, and Starting the Application Server Domain

• Testing the Three-Tier Connection

• Importing an Existing Application Server Domain Configuration

• Setting Up a Custom Application Server Domain Configuration

• Troubleshooting Common Errors

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

281

Configuring the Application Server on Windows

Chapter 8A

Task 8A-4-1: Creating, Configuring, and Starting the Application Server

Domain

To create, configure, and start the application server domain:

1. Run the psadmin

command.

You see the PeopleSoft Server Administration menu, as in this example:

--------------------------------

PeopleSoft Server Administration

--------------------------------

PS_CFG_HOME:  C:\Users\JSMITH\psft\pt\8.55

PS_HOME:      C:\PT8.55

PS_APP_HOME:  C:\HR92

1) Application Server

2) Process Scheduler

3) Search Server

4) Web (PIA) Server

5) Switch Config Home

6) Service Setup

7) Replicate Config Home

8) Refresh Config Home q) Quit

Command to execute (1-8, q): 1

Note. Make sure you change the directory from the PS_HOME on the file server to the PS_HOME, or highlevel directory, on the application server.

2. Depending on your environment, you may see a message after the initial menu, which indicates that

PSADMIN has modified the PS_CFG_HOME/peopletools.properties file with the current PS_HOME location:

*********************************************************

PS_CFG_HOME/peopletools.properties file has been updated. 

You should use the Config Home Refresh feature in PSAdmin  to ensure that all of your domains are current. 

Alternatively, you may recreate all of your domains. 

Please press any key to continue...

***********************************************************

This indicates that one of these situations exists:

• The PS_CFG_HOME that you are working with was used previously from a different PS_HOME. In this case, you should recreate any existing Application Server, Process Scheduler, Search, or PIA domains in this PS_CFG_HOME.

• You configured your environment such that PS_CFG_HOME is the same as PS_HOME. The first time you use PSADMIN to create a domain, it updates the PS_CFG_HOME/peopletools.properties file.

Continue with the next step.

3. Specify 1 for Application Server and press ENTER.

282

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 8A

Configuring the Application Server on Windows

4. Specify 2 to Create a domain and press ENTER.

--------------------------------------------

PeopleSoft Application Server Administration

--------------------------------------------

  1) Administer a domain

  2) Create a domain

  3) Delete a domain

  4) Import domain configuration

  q) Quit

 Command to execute (1-4, q): 2

5. Specify the domain name.

In this example the database name is HRDMO:

Please enter name of domain to create :HRDMO

Domain names are case sensitive and must be eight US-ASCII characters or less. The domain name is used to create a directory name under the PS_CFG_HOME\appserv directory.

See the information on PS_CFG_HOME and server domain configuration in the PeopleTools: System and

Server Administration product documentation.

6. Specify 4 for small if this is your initial domain installation, press ENTER.

See PeopleTools: System and Server Administration.

7. After the system creates the domain, the PeopleSoft Application Server Administration menu appears with a

Quick-configure menu similar to this:

---------------------------------------------------------

Quick-configure menu -- domain: HRDMO

---------------------------------------------------------

         Features                                 Settings

        ==========                               ==========

  1) Pub/Sub Servers       : No        17) DBNAME         :[HRDMO] 

  2) Quick Server          : No        18) DBTYPE         :[ORACLE]

  3) Query Servers         : No        19) UserId         :[QEDMO]

  4) Jolt                  : Yes       20) UserPswd       :[]

  5) Jolt Relay            : No        21) DomainID       :[TESTSERV]

  6) WSL                   : No        22) AddToPATH      :[c:\oracle⇒

\product\11.2.0\dbhome_1\bin]  

  7) PC Debugger           : No        23) ConnectID      :[people]

  8) Event Notification    : Yes       24) ConnectPswd    :[]

  9) MCF Servers           : No        25) DomainConnectPswd:[]

 10) Perf Collator         : No        26) WSL Port       :[7000]

 11) Analytic Servers      : Yes       27) JSL Port       :[9000]

 12) Domains Gateway       : No        28) JRAD Port      :[9100]

 13) Push Notifications    : No            

                                      

      Actions

     =========

 14) Load config as shown

 15) Custom configuration

 16) Edit environment settings

  h) Help for this menu

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

283

Configuring the Application Server on Windows

Chapter 8A

  q) Return to previous menu

 HINT: Enter 17 to edit DBNAME, then 14 to load

 Enter selection (1-28, h, or q):

Note. If your installation includes more than one application server domain on a given machine, read the troubleshooting section for more information.

See Troubleshooting Common Errors.

8. If you need to modify any of the values for these settings, enter the number next to the parameter name, press

ENTER, then type the new value, and press ENTER again.

If you need to change any of the features, type the number next to the feature name and press ENTER.

9. Configure the WSL to boot by changing option 6 to Yes.

Enter 6, and press ENTER.

10. If you intend to use the PeopleSoft Report Distribution system, you must select Yes for feature 8, Event

Notification.

This enables the REN server, which is used by the "run to window" functionality of the Report Distribution system. The Report Distribution system, MultiChannel Framework, and Optimization Framework use REN

servers. You must also remember to enter an Authentication Token Domain when installing the PeopleSoft

Pure Internet Architecture (PIA).

11. If you are configuring an application server domain to support applications based on the PeopleSoft

MultiChannel Framework (such as PeopleSoft CRM ERMS), select feature 9, MCF Servers.

See the information on configuring REN Servers in the product documentation.

See PeopleTools: MultiChannel Framework.

12. Enter 22 for AddToPATH, and enter the path to the 64-bit connectivity software. For example:

C:\oracle\product\11.2.0\dbhome_1\BIN

13. Enter the values for the 20) UserPswd and 24) ConnectPswd that you specified during the database configuration.

Reenter each password to verify the value. The password is hidden by masking characters as you type and in the Quick-configure menu.

14. If you want to set a Domain Connection password, enter 25 and specify a password of 8 characters or less.

Reenter the password to verify the value. The password is hidden by masking characters as you type and in the Quick-configure menu.

The Domain Connection password is optional. You can specify a value or leave it blank. However, if you do specify a value, you must supply the same value when installing the PeopleSoft Pure Internet Architecture, to ensure the connection to the Application Server.

15. If you are installing a REN server: a. Enter 15 for Custom configuration.

b. Reply y, and press ENTER, at this prompt:

Do you want to change any config values (y/n) [n]?

c. Reply n, and press ENTER, at this prompt:

Do you want to change any values (y/n) [n]?

284

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 8A

Configuring the Application Server on Windows

Continue to enter n, for No, for all sections until you see the PSRENSRV section, and then answer y. (Be aware that there are several sections.) d. Leave the defaults for all settings except for default_auth_token, which you should set to the domain name for your web server.

Note. The default_auth_token setting should be identical to the Authentication Token Domain that you set during PIA installation.

See "Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode." e. Accept the defaults for the next series of questions until asked if you want Event Notification configured.

In this case, answer y. f.

Accept the default for the remaining questions; the configuration will load automatically.

16. If you are not installing a REN server, after you update the settings you can load the configuration by entering

14, for Load config as shown, from the Quick-configure menu.

17. To start the application server (whether you installed a REN server or not), select 1, Boot this domain, from the PeopleSoft Domain administration menu.

18. Select 1, Boot (Serial Boot) or 2, Parallel Boot, from the PeopleSoft Domain Boot Menu.

Note. The messages you see and the number of processes started will depend on the options you chose during configuration.

19. If you plan to continue with PIA installation and testing, do not shut down the application server at this time.

20. If you want to shut down your PeopleSoft application server domain later, follow these simple steps: a. From the PeopleSoft Domain Administration menu, enter 2 for Domain shutdown menu.

b. From the PeopleTools Domain Shutdown Menu, enter 1 for Normal shutdown.

You see messages about the application server processes being shut down. The number of processes stopped will vary depending on the number of processes that started when you booted the domain. c. Enter q to quit the PeopleSoft Domain Administration Menu.

Task 8A-4-2: Testing the Three-Tier Connection

If you get an error message when you try to sign in to the Application Server in Application Designer (that is, three-tier mode), it may be due to an incorrect server name or port number, because the database server is not running, or because the application server was not booted. To test a three-tier connection from the PeopleTools

Development Environment (the Windows-based client):

1. Start Configuration Manager with one of these methods:

• On Microsoft Windows 7, select Start, Programs, PeopleTools 8.55, Configuration Manager.

• On Microsoft Windows 8 or 2012 R2, access the Apps screen and navigate to PeopleTools 8.55,

Configuration Manager.

• Run PS_HOME\bin\client\winx86\pscfg.exe.

2. Select the Profile Tab. Highlight Default and select Edit.

3. On the Edit Profile dialog box, select Application Server as the Connection Type.

4. Enter values for these parameters:

• Application Server Name

• Machine Name or IP Address

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

285

Configuring the Application Server on Windows

Chapter 8A

• Port Number (WSL)

• Domain Connection Password and Domain Connection Password (confirm)

Specify a value for the password, and repeat your entry for confirmation. The password must be 8 characters or less.

This password is optional. If you did not set the Domain Connection Password in Configuration Manager or in the Application Server configuration, leave it blank. If you specify a password, you must supply the same password during the PeopleSoft Pure Internet Architecture installation for a successful connection between the Application Server and PeopleSoft Pure Internet Architecture.

See the PeopleTools: System and Server Administration product documentation for information on using

PeopleSoft Configuration Manager and PSADMIN.

5. Select Set to add the definition to the list and select OK to close the dialog box.

6. On the Configuration Manager dialog box, select the Startup tab.

7. Select Application Server from the Database Type list. Your application server name should be displayed.

8. Enter the values for User ID, Connect ID, and password.

9. Click OK.

Note. Confirm that the application server is running by booting it from PSADMIN. Select 1, Boot this domain, from the PeopleSoft Domain administration menu. Select option 1, Boot (Serial Boot) or 2, Parallel

Boot, from the PeopleSoft Domain Boot menu.

10. Start Application Designer with one of these methods:

• On Microsoft Windows 7, select Start, Programs, PeopleTools 8.55, Application Designer.

• On Microsoft Windows 8 or 2012 R2, access the Apps screen and navigate to PeopleTools 8.55,

Application Designer.

• Run PS_HOME\bin\client\winx86\pside.exe.

11. In the PeopleSoft Signon dialog box:

• Select Application Server as the Connection Type.

• Confirm that the Application Server Name is correct.

• Enter values for User ID and password.

12. Select OK to open Application Designer.

If you see the following error message when you try to sign in to the Application Server in Application Designer:

Network API: "Could not connect to application server 'Application Server⇒

 Name' Make sure the PeopleTools authentication server (PSAUTH) is booted."

This may indicate a problem with the Domain Connection Password. For example, if the password set in the

Application Server configuration file does not match the value in Configuration Manager, you may get this error message when you sign in to Application Designer in three-tier mode. Check the Application Server logs for more information.

286

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 8A

Configuring the Application Server on Windows

Task 8A-4-3: Importing an Existing Application Server Domain

Configuration

If you have an existing application server configuration for a previous PeopleSoft PeopleTools release, you can import it to create a new domain. You can import an existing domain configuration by specifying a file or by specifying the path to an existing domain. To import from a file, you must use the psappsrv.cfg file found inside an existing application server domain folder (you must specify the full path to psappsrv.cfg). This file can be located anywhere in the file system, but must be named psappsrv.cfg. To import from an existing domain configuration that you created in PeopleSoft PeopleTools 8.55, you must specify PS_CFG_HOME and the name of an existing application server domain. (If you are importing a domain from a release before PeopleSoft

PeopleTools 8.50, note that the domains were created in PS_HOME, and that is the path that you should provide.)

To import an existing application server domain configuration:

1. Go to the PS_HOME\appserv directory and run the psadmin

command.

You see the PeopleSoft Server Administration menu, as in this example:

--------------------------------

PeopleSoft Server Administration

--------------------------------

PS_CFG_HOME:  C:\Users\JSMITH\psft\pt\8.55

PS_HOME:      C:\PT8.55

PS_APP_HOME:  C:\HR92

1) Application Server

2) Process Scheduler

3) Search Server

4) Web (PIA) Server

5) Switch Config Home

6) Service Setup

7) Replicate Config Home

8) Refresh Config Home q) Quit

Command to execute (1-8, q): 1

The PS_CONFIG_HOME location, also referred to as Config Home, corresponds to the current working directory. For information on how Config Home is set, see the PeopleTools: System and Server

Administration product documentation.

Note. Make sure you change the directory from the PS_HOME on the file server to the PS_HOME on the application server.

2. Depending on your environment, you may see a message after the initial menu, which indicates that

PSADMIN has modified the PS_CFG_HOME/peopletools.properties file with the current PS_HOME location:

*********************************************************

PS_CFG_HOME/peopletools.properties file has been updated. 

You should use the Config Home Refresh feature in PSAdmin  to ensure that all of your domains are current. 

Alternatively, you may recreate all of your domains. 

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

287

Configuring the Application Server on Windows

Chapter 8A

Please press any key to continue...

***********************************************************

This indicates that one of these situations exists:

• The PS_CFG_HOME that you are working with was used previously from a different PS_HOME. In this case, you should recreate any existing Application Server, Process Scheduler, Search, or PIA domains in this PS_CFG_HOME.

• You configured your environment such that PS_CFG_HOME is the same as PS_HOME. The first time you use PSADMIN to create a domain, it updates the PS_CFG_HOME/peopletools.properties file.

Continue with the next step.

3. Specify 1 for Application Server.

4. Specify 4 for Import domain configuration.

--------------------------------------------

PeopleSoft Application Server Administration

--------------------------------------------

  1) Administer a domain

  2) Create a domain

  3) Delete a domain

  4) Import domain configuration

  q) Quit

 Command to execute (1-4, q): 4

5. Specify 1 for Import regular domain.

--------------------------------------------

PeopleSoft Import Application Server Configuration

--------------------------------------------

  1) Import regular domain

  2) Import IB Master Configuration

  q) Quit

Command to execute (1-2, q) : 1

6. Specify whether to import the domain configuration from a file (option 1) or from an existing application domain configuration (option 2).

--------------------------------------------

PeopleSoft Import Application Server Configuration

--------------------------------------------

  1) Import from file

  2) Import from application domain

  q) Quit

  

Command to execute (1-2, q) :

7. If you selected 1, provide the full path to the file psappsrv.cfg, and then specify the name of the domain you want to create. If you selected 2, go to the next step.

Enter full path to configuration file

  :C:\temp\oldconfig\psappsrv.cfg

288

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 8A

Configuring the Application Server on Windows

Enter domain name to create

  :HRDMO

8. If you selected 2, to Import from application domain, provide the full path to the PS_CFG_HOME of the existing domain.

If importing from PeopleTools 8.49 or earlier, provide PS_HOME for PS_⇒

CFG_HOME.

Enter PS_CFG_HOME of domain you wish to import: C:\Users\JSMITH\psft\pt⇒

\8.55

If applicable, choose among the existing application server domains in the specified PS_CFG_HOME:

Tuxedo domain list:

  1)  HRDBA

  2)  HRDBB

Select domain number to import: 1

Enter a name for new domain:  HRDMO

After you create the domain, continue to the next task to verify that the imported configuration parameters are appropriate for the newly created domain. You may need to change the following values:

• DBName

DBName can be the same or different, depending on which database the application server needs to point to.

• DBType

DBType depends on the database type of DBName.

• UserId and UserPswd

UserId and UserPswd are the user's choice.

• Workstation Listener Port

Workstation Listener Port will need to be modified if the old domain will be up and running in the same machine.

• Jolt Listener Port

Jolt Listener Port will also need a different number if the old domain will be up and running in the same machine.

• Jolt Relay Adapter Listener Port

Jolt Relay Adapter Listener Port will need a different number if the old domain will be up and running in the same machine, and will be using Jolt Relay Adapter.

Task 8A-4-4: Setting Up a Custom Application Server Domain Configuration

The Quick-configure menu is initially displayed when you choose to configure your domain. This menu is intended for the commonly adjusted parameters—those most likely to change from domain to domain. However, there are additional configuration parameters that are not available through the Quick-configure menu. For such configuration parameters, you must use the Custom Configuration option, which you can access from the Quickconfigure menu. Feel free to skip this procedure if you have already created and configured your Application

Server using the Quick-configure menu and want to move forward.

The following steps assume you will be using PSADMIN to specify parameter settings.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

289

Configuring the Application Server on Windows

Chapter 8A

To reconfigure an application server domain:

1. Go to the PS_HOME\appserv directory and run the psadmin

command.

Note. Make sure you change the directory from the PS_HOME on the file server to the PS_HOME on the application server.

2. Depending on your environment, you may see a message after the initial menu, which indicates that

PSADMIN has modified the PS_CFG_HOME/peopletools.properties file with the current PS_HOME location:

*********************************************************

PS_CFG_HOME/peopletools.properties file has been updated. 

You should use the Config Home Refresh feature in PSAdmin  to ensure that all of your domains are current. 

Alternatively, you may recreate all of your domains. 

Please press any key to continue...

***********************************************************

This indicates that one of these situations exists:

• The PS_CFG_HOME that you are working with was used previously from a different PS_HOME. In this case, you should recreate any existing Application Server, Process Scheduler, Search, or PIA domains in this PS_CFG_HOME.

• You configured your environment such that PS_CFG_HOME is the same as PS_HOME. The first time you use PSADMIN to create a domain, it updates the PS_CFG_HOME/peopletools.properties file.

Continue with the next step.

3. Specify 1 for Application Server and press ENTER.

4. Specify 1 for Administer a domain and press ENTER.

5. Select the domain to administer and press ENTER.

6. Specify 4 for Configure this domain and press ENTER.

The option Configure this domain performs the following tasks:

• Shuts down the application server, if it is running. (Shutdown is required since the binary file PSTUXCFG must be deleted and re-created to enable new configuration values. If there are no processes running when shutdown is attempted, an error will be displayed but the script continues on. This is normal.)

• Initiates an interactive dialog, prompting for configuration parameters.

• Updates psappsrv.cfg, generates psappsrv.ubb, and internally invokes Tuxedo's tmloadcf executable to create binary file PSTUXCFG used during the domain boot process.

7. Specify 15 for Custom Configuration and press ENTER.

8. Respond to this prompt:

Do you want to change any config values (y/n):

• Specify y to start an interactive dialog to change or examine parameter values, as described in the next step.

Oracle recommends this option for more experienced users.

• Specify n if you have already edited psappsrv.cfg, skip the next step, and continue with the step to select server process options.

9. Complete the interactive dialog to specify configuration parameters.

Configuration parameters are grouped into sections. For each section, you are asked whether you want to

290

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 8A

Configuring the Application Server on Windows

change any parameters in that section, as in the following example:

Values for config section - Startup

                DBName=

                DBType=

                UserId=

                UserPswd=

                ConnectId=

                ConnectPswd=

                ServerName=

                StandbyDBName=

                StandbyDBType=

                StandbyUserId=

                StandbyUserPswd=

                InMemoryDBName=

                InMemoryDBType=

Do you want to change any values (y/n)? [n]:  y

• Specify y to change any parameter values for the current configuration section displayed.

You are prompted for each parameter value. Either specify a new value, or press ENTER to accept the default if applicable. After pressing ENTER, you are positioned at the next parameter in that section.

When you are done with that section, you are again asked whether you want to re-edit any of the values you changed.

• Enter the user ID and user password that has security to start the application server. All application databases are delivered with one or more application server security users, usually PS or VP1.

The password you enter is hidden by masking characters.

• The parameters StandbyDBName, StandbyDBType, StandbyUserId, and StandbyUserPswd, are used for a standby database in an Oracle environment.

See PeopleTools: Data Management, "Implementing Oracle Active Data Guard."

• The parameters InMemoryDBName and InMemoryDBType are reserved for internal use.

• The WSL, JSL, and JRAD port numbers, which are found in other sections of the configuration parameters, have default values of 7000, 9000, and 9100, respectively. These values must be unique for each application server domain. You may alter the port values if necessary to ensure that they are unique

• If you do not wish to change any values, specify n and you will be prompted for the next configuration section.

Note. When setting up your application server, make a note of the values you use for Database Name,

Application Server Name (the machine name), and JSL Port. You will need to use these same values when installing the PeopleSoft Pure Internet Architecture.

See PeopleTools: System and Server Administration.

10. Select server process options.

At this point, you will be prompted to select server process options. If this is your initial installation, we suggest you accept the defaults. A message similar to this appears:

Setting Log Directory to the default... [PS_SERVDIR\LOGS]

Configuration file successfully created.

Loading new configuration...

The message "Loading new configuration" indicates that PSADMIN is generating a binary file named

PSTUXCFG, which is used to boot the application server. At this point, your application server should be

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

291

Configuring the Application Server on Windows

properly configured.

Chapter 8A

Task 8A-4-5: Troubleshooting Common Errors

For troubleshooting help, you can access a log file through the PSADMIN PeopleSoft Domain Administration menu. The following list includes possible errors and troubleshooting tips.

• Use PSADMIN menu option 6 for Edit configuration/log files menu to check for errors in

<PS_CFG_HOME>\appserv\<domain>\LOGS\APPSRV_mmdd.log and <PS_CFG_HOME>\appserv\

<domain>\LOGS\TUXLOG.mmddyy.

• If a PeopleSoft server such as PSAPPSRV fails, examine your configuration parameters. The failure of the

PSAPPSRV process is often signalled by the message "Assume failed"

—which means the process has failed to start. Check the SIGNON section for misspelled or invalid database name, an invalid or unauthorized

OprId, or ConnectId or ServerName is missing or invalid. Finally, make sure the database connectivity is set correctly.

• If a WSL (or JSL) fails to start, try specifying another port number (it may be in use already by another application server domain process).

• If you are unable to start the BBL, check that your Tuxedo is installed fully and that the directory really exists.

• If the installation includes more than one application server domain on a single machine, before booting the second domain, adjust the REN server configuration to avoid conflict in one of these ways:

• Use PSADMIN to disable Event Notification (option 8 on the Quick-configure menu) for the second and subsequent app server domains.

• Change default_http_port to a value other than 7180.

See Also

PeopleTools: System and Server Administration

PeopleTools: MultiChannel Framework

292

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 8B

Configuring the Application Server on UNIX

This chapter discusses:

• Understanding the Application Server

• Understanding the Application Server Domain Processes

• Prerequisites

• Preparing the Application Server File System for a PeopleTools-Only Upgrade

• Setting Environment Variables

• Setting Up COBOL for Remote Call

• Verifying Database Connectivity

• Creating, Configuring, and Starting an Initial Application Server Domain

Understanding the Application Server

The information in this chapter is provided to help you configure your PeopleSoft application server.

Note. COBOL is not needed for PeopleSoft PeopleTools or for PeopleSoft Applications that contain no COBOL programs. Check the information on My Oracle Support, and your application-specific documentation, for the details on whether your application requires COBOL.

Oracle supports application servers for the PeopleSoft installation on several UNIX and Linux operating system platforms. For detailed information, consult the certification information on My Oracle Support. The application server support can be found on the certification pages for PeopleSoft systems.

You can install the application server using either a "logical" or "physical" three-tier configuration.

• Installing the application server on the same machine as the database server is known as a logical three-tier configuration. For your initial PeopleSoft installation, Oracle suggests that you install a logical configuration to simplify setup.

• Installing the application server on a machine separate from the database server machine is known as a physical three-tier configuration.

The configuration and log files for application server domains reside in PS_CFG_HOME. If you do not set a

PS_CFG_HOME environment variable before beginning the application server configuration, the system installs it in a default location based on the current user's settings, as follows:

$HOME/psft/pt/<peopletools_version>

See "Preparing for Installation," Defining Installation Locations.

293

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Configuring the Application Server on UNIX

Chapter 8B

See Also

"Preparing for Installation," Understanding PeopleSoft Servers and Clients

PeopleTools: System and Server Administration, "Using PSADMIN Menus"

PeopleTools: Data Management

My Oracle Support, Certifications

"Setting Up the Install Workstation"

"Installing and Compiling COBOL on UNIX"

Understanding the Application Server Domain Processes

On most platforms (IBM AIX, Oracle Solaris, Linux, and HP-UX Itanium) no changes are required from the system defaults, in order to allow the "small" and "development" domains that are shipped with PeopleSoft

PeopleTools to boot successfully.

Refer to the performance documentation for guidance in configuring your system to run larger domains. That document describes the suggested minimum kernel settings for running PeopleSoft PeopleTools in a real-world environment.

See PeopleTools Performance Guidelines Red Paper on My Oracle Support (search for the article title).

Permanently changing system-wide parameters generally requires root privileges, and any changes to the kernel configuration of your operating system should be done with care.

If you are installing on HP-UX 11.31 operating systems, be aware that hosts with machine names longer than 8 characters require the HP-UX kernel configuration uname_eoverflow

to be set to 0 (zero).

Prerequisites

Before beginning this procedure, you should have completed the following tasks:

• Installed your application server.

See "Using the PeopleSoft Installer," Planning Your Initial Configuration.

• Installed the supported version of Oracle Tuxedo

See "Installing Additional Components."

• Granted authorization to a PeopleSoft user ID to start the application server.

The database configuration procedure includes a step for setting up the user ID with authorization to start the application server. See the application-specific installation instructions for information on the user IDs for your PeopleSoft application. See the PeopleTools: Security Administration product documentation for information on PeopleSoft PeopleTools delivered user profiles.

See "Creating a Database on UNIX," Running the Database Configuration Wizard.

See "Creating a Database Manually on Windows," Creating Data Mover Import Scripts.

See "Creating a Database Manually on UNIX," Creating Data Mover Import Scripts.

• Run the following SQL statements on your database server to review and if needed, update the

PSCLASSDEFN table:

294

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 8B

Configuring the Application Server on UNIX

SELECT CLASSID, STARTAPPSERVER FROM PSCLASSDEFN

WHERE CLASSID IN (SELECT OPRCLASS FROM PSOPRCLS WHERE OPRID='<OPRID>')

UPDATE PSCLASSDEFN SET STARTAPPSERVER=1 WHERE CLASSID='<CLASSID>'

Note. Installers typically use VP1 or PS to test the application server. If these users are deleted or their passwords are changed, the application server will no longer be available. To avoid this problem, you can set up a new operator (called PSADMIN or PSASID, for instance) with privileges to start the application server. If you do this, you can use the new operator for your application servers and you won't need to change the password each time

VP1 or PS is changed.

Task 8B-1: Preparing the Application Server File System for a

PeopleTools-Only Upgrade

When performing the installation of the separate upgrade PS_HOME (which is different than your old release

PS_HOME), you may configure your Application Server at this point in time of the installation. Do not boot your

Application Server until directed to do so within the upgrade. If you are installing into an old PS_HOME or

PS_CFG_HOME after completing a PeopleTools-only upgrade, review your old PS_HOME or PS_CFG_HOME for configuration files that you may want to reuse for the new PeopleSoft PeopleTools release.

See Also

"Preparing for Installation," Preparing for the PeopleTools-Only Upgrade

Task 8B-2: Setting Environment Variables

Telnet to your UNIX system. Log in and ensure the following environment variables are set appropriately.

Note. The environment variables for Tuxedo must be set explicitly; they are not set by running psconfig.sh. These can be also set using the .profile file in the user's home directory.

• $TUXDIR must be set to the correct Oracle Tuxedo installation directory. For example:

TUXDIR=/home/user/Oracle/tuxedo12cR1; export TUXDIR

• $TUXDIR/lib must be prepended to LD_LIBRARY_PATH, LIBPATH, or SHLIB_PATH, whichever is appropriate for your platform. For example:

LD_LIBRARY_PATH=$TUXDIR/lib:$LD_LIBRARY_PATH; export  LD_LIBRARY_PATH

• $TUXDIR/bin must be prepended to PATH. For example:

PATH=$TUXDIR/bin:$PATH; export PATH

One method to ensure that the following PeopleSoft environment variables are set is to source psconfig.sh. Go to the PS_HOME directory, and enter the following command:

. ./psconfig.sh

Note. After running psconfig.sh, you can invoke the psadmin utility from any location.

Alternatively you can make sure the following environment variables are set in the .profile file in the user's home directory:

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

295

Configuring the Application Server on UNIX

Chapter 8B

• $ORACLE_HOME must point to the correct Oracle installation for example:

ORACLE_HOME=/products/oracle/11.2.0;export ORACLE_HOME

• $ORACLE_HOME/bin must be added to PATH; for example:

PATH=$PATH:$ORACLE_HOME/bin;export PATH

• $ORACLE_HOME/lib must be appended to LD_LIBRARY_PATH, LIBPATH, or SHLIB_PATH, whichever is appropriate for your platform.

• $ORACLE_HOME/lib must be ahead of $ORACLE_HOME/lib32 in the library path.

• $ORACLE_SID must be set to the correct Oracle instance. For example:

ORACLE_SID=hdmo;export ORACLE_SID

• $COBDIR must be set to the Server Express installation directory. For example:

COBDIR=/cobol/prod/svrexp-5.1_wp11-64bit;export COBDIR

Note. If your application does not contain COBOL programs, you do not need to set the $COBDIR environment variables.

• $COBDIR/bin must be appended to the PATH; for example:

PATH=$PATH:$COBDIR/bin;export PATH

• $COBDIR/lib must be appended to LD_LIBRARY_PATH, LIBPATH, or SHLIB_PATH, whichever is appropriate for your platform. For example:

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$COBDIR/lib;export LD_LIBRARY_PATH

LIBPATH=$LIBPATH:$COBDIR/lib;export LIBPATH

SHLIB_PATH=$SHLIB_PATH:$COBDIR/lib;export SHLIB_PATH

Task 8B-3: Setting Up COBOL for Remote Call

Remote Call is a PeopleCode feature that launches a COBOL program from an application server, PeopleCode program or a batch Application Engine PeopleCode program and waits for it to complete execution before continuing. The execution of a COBOL program via Remote Call is completely independent of the Process

Scheduler. You need to set up a COBOL runtime environment and COBOL executables on the application server to support Remote Call.

See "Installing and Compiling COBOL on UNIX."

Note. If your application does not contain COBOL programs, you do not need to purchase or compile COBOL.

Task 8B-4: Verifying Database Connectivity

Before continuing, it is critical to verify connectivity to the database that the application server domain will use.

To verify connectivity, connect to the database server from the application server using the native SQL tool on the application server.

For Oracle use SQL*Plus.

296

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 8B

Configuring the Application Server on UNIX

Task 8B-5: Creating, Configuring, and Starting an Initial

Application Server Domain

This section discusses:

• Creating, Configuring, and Starting the Application Server Domain

• Testing the Three-Tier Connection

• Importing an Existing Application Server Domain Configuration

• Setting Up a Custom Application Server Domain Configuration

• Troubleshooting Common Errors

Task 8B-5-1: Creating, Configuring, and Starting the Application Server

Domain

To create, configure, and start the application server domain:

1. Run the psadmin

command.

You see the PeopleSoft Server Administration menu, as in this example:

--------------------------------

PeopleSoft Server Administration

--------------------------------

PS_CFG_HOME:  /home/JSMITH/peopletools/8.55

PS_HOME:      /home/PT855

PS_APP_HOME:  /home/HR92

1) Application Server

2) Process Scheduler

3) Search Server

4) Web (PIA) Server

5) Switch Config Home

6) Replicate Config Home

7) Refresh Config Home q) Quit

Command to execute (1-7, q): 1

2. Depending on your environment, you may see a message after the initial menu, which indicates that

PSADMIN has modified the PS_CFG_HOME/peopletools.properties file with the current PS_HOME location:

*********************************************************

PS_CFG_HOME/peopletools.properties file has been updated. 

You should use the Config Home Refresh feature in PSAdmin  to ensure that all of your domains are current. 

Alternatively, you may recreate all of your domains. 

Please press any key to continue...

***********************************************************

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

297

Configuring the Application Server on UNIX

Chapter 8B

This indicates that one of these situations exists:

• The PS_CFG_HOME that you are working with was used previously from a different PS_HOME. In this case, you should recreate any existing Application Server, Process Scheduler, Search, or PIA domains in this PS_CFG_HOME.

• You configured your environment such that PS_CFG_HOME is the same as PS_HOME. The first time you use PSADMIN to create a domain, it updates the PS_CFG_HOME/peopletools.properties file.

Continue with the next step.

3. Specify 1 for Application Server and press ENTER.

4. Specify 2 to Create a domain and press ENTER.

--------------------------------------------

PeopleSoft Application Server Administration

--------------------------------------------

  1) Administer a domain

  2) Create a domain

  3) Delete a domain

  4) Import domain configuration

  q) Quit

 Command to execute (1-4, q): 2

5. Specify the domain name.

In this example the database name is HRDMO:

Please enter name of domain to create :HRDMO

Domain names are case sensitive and must be eight characters or less. The domain name is used to create a directory name under the PS_CFG_HOME/appserv directory.

See the information on PS_CFG_HOME and server domain configuration in the PeopleTools: System and

Server Administration product documentation.

6. Specify 4 for small if this is your initial domain installation, press ENTER.

See PeopleTools: System and Server Administration.

7. After the system creates the domain, the PeopleSoft Application Server Administration menu appears with a

Quick-configure menu similar to this:

---------------------------------------------------------

Quick-configure menu -- domain: HRDMO

---------------------------------------------------------

         Features                                 Settings

        ==========                               ==========

  1) Pub/Sub Servers       : No        17) DBNAME         :[HRDMO]

  2) Quick Server          : No        18) DBTYPE         :[ORACLE]

  3) Query Servers         : No        19) UserId         :[VP1]

  4) Jolt                  : Yes       20) UserPswd       :[]

  5) Jolt Relay            : No        21) DomainID       :[TESTSERV]

  6) WSL                   : No        22) AddToPATH      :[.]  

  7) PC Debugger           : No        23) ConnectID      :[people]

  8) Event Notification    : Yes       24) ConnectPswd    :[]

  9) MCF Servers           : No        25) DomainConnectPswd:[]

 10) Perf Collator         : No        26) WSL Port       :[7000]

 11) Analytic Servers      : Yes       27) JSL Port       :[9000]

 12) Domains Gateway       : No        28) JRAD Port      :[9100]

298

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 8B

Configuring the Application Server on UNIX

 13) Push Notifications    : No           

                                      

      Actions

     =========

 14) Load config as shown

 15) Custom configuration

 16) Edit environment settings

  h) Help for this menu

  q) Return to previous menu

 HINT: Enter 17 to edit DBNAME, then 14 to load

 Enter selection (1-28, h, or q):

Note. If your installation includes more than one application server domain on a given machine, read the troubleshooting section for more information.

See Troubleshooting Common Errors.

8. If you need to modify any of the values for these settings, enter the number next to the parameter name, press

ENTER, then type the new value, and press ENTER again.

If you need to change any of the features, type the number next to the feature name and press ENTER.

9. Configure the WSL to boot by changing option 6 to Yes.

Enter 6, and press ENTER.

10. If you intend to use the PeopleSoft Report Distribution system, you must select Yes for feature 8, Event

Notification.

This enables the REN server, which is used by the "run to window" functionality of the Report Distribution system. The Report Distribution system, MultiChannel Framework, and Optimization Framework use REN

servers. You must also remember to enter an Authentication Token Domain when installing the PeopleSoft

Pure Internet Architecture (PIA).

11. If you are configuring an application server domain to support applications based on the PeopleSoft

MultiChannel Framework (such as PeopleSoft CRM ERMS), select feature 9, MCF Servers.

See the information on configuring REN Servers in the product documentation.

See PeopleTools: MultiChannel Framework.

12. Enter the values for the 20) UserPswd and 24) ConnectPswd that you specified during the database configuration.

Reenter each password to verify the value. The password is hidden by masking characters as you type and in the Quick-configure menu.

13. If you want to set a Domain Connection password, enter 25 and specify a password of 8 characters or less.

Reenter the password to verify the value. The password is hidden by masking characters as you type and in the Quick-configure menu.

The Domain Connection password is optional. You can specify a value or leave it blank. However, if you do specify a value, you must supply the same value when installing the PeopleSoft Pure Internet Architecture, to ensure the connection to the Application Server.

14. If you are installing a REN server: a. Enter 15 for Custom configuration.

b. Reply y, and press ENTER, at this prompt:

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

299

Configuring the Application Server on UNIX

Chapter 8B

Do you want to change any config values (y/n) [n]?

c. Reply n, and press ENTER, at this prompt:

Do you want to change any values (y/n) [n]?

Continue to enter n, for No, for all sections until you see the PSRENSRV section, and then answer y. (Be aware that there are several sections.) d. Leave the defaults for all settings except for default_auth_token, which you should set to the domain name for your web server.

Note. The default_auth_token setting should be identical to the Authentication Token Domain that you set during PIA installation.

See "Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode." e. Accept the defaults for the next series of questions until asked if you want Event Notification configured.

In this case, answer y. f.

Accept the default for the remaining questions; the configuration will load automatically.

15. If you are not installing a REN server, after you update the settings you can load the configuration by entering

14, for Load config as shown, from the Quick-configure menu.

16. To start the application server (whether you installed a REN server or not), select 1, Boot this domain, from the PeopleSoft Domain administration menu.

17. Select 1, Boot (Serial Boot) or 2, Parallel Boot, from the PeopleSoft Domain Boot Menu.

Note. The messages you see and the number of processes started will depend on the options you chose during configuration.

18. If you plan to continue with PIA installation and testing, do not shut down the application server at this time.

19. If you want to shut down your PeopleSoft application server domain later, follow these simple steps: a. From the PeopleSoft Domain Administration menu, enter 2 for Domain shutdown menu.

b. From the PeopleTools Domain Shutdown Menu, enter 1 for Normal shutdown.

You see messages about the application server processes being shut down. The number of processes stopped will vary depending on the number of processes that started when you booted the domain. c. Enter q to quit the PeopleSoft Domain Administration Menu.

Task 8B-5-2: Testing the Three-Tier Connection

If you get an error message when you try to sign in to the Application Server in Application Designer (that is, three-tier mode), it may be due to an incorrect server name or port number, because the database server is not running, or because the application server was not booted. To test a three-tier connection from the PeopleTools

Development Environment (the Windows-based client):

1. Start Configuration Manager with one of these methods:

• On Microsoft Windows 7, select Start, Programs, PeopleTools 8.55, Configuration Manager.

• On Microsoft Windows 8 or 2012 R2, access the Apps screen and navigate to PeopleTools 8.55,

Configuration Manager.

• Run PS_HOME\bin\client\winx86\pscfg.exe.

2. Select the Profile Tab. Highlight Default and select Edit.

300

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 8B

Configuring the Application Server on UNIX

3. On the Edit Profile dialog box, select Application Server as the Connection Type.

4. Enter values for these parameters:

• Application Server Name

• Machine Name or IP Address

• Port Number (WSL)

• Domain Connection Password and Domain Connection Password (confirm)

Specify a value for the password, and repeat your entry for confirmation. The password must be 8 characters or less.

This password is optional. If you did not set the Domain Connection Password in Configuration Manager or in the Application Server configuration, leave it blank. If you specify a password, you must supply the same password during the PeopleSoft Pure Internet Architecture installation for a successful connection between the Application Server and PeopleSoft Pure Internet Architecture.

See the PeopleTools: System and Server Administration product documentation for information on using

PeopleSoft Configuration Manager and PSADMIN.

5. Select Set to add the definition to the list and select OK to close the dialog box.

6. On the Configuration Manager dialog box, select the Startup tab.

7. Select Application Server from the Database Type list. Your application server name should be displayed.

8. Enter the values for User ID, Connect ID, and password.

9. Click OK.

Note. Confirm that the application server is running by booting it from PSADMIN. Select 1, Boot this domain, from the PeopleSoft Domain administration menu. Select option 1, Boot (Serial Boot) or 2, Parallel

Boot, from the PeopleSoft Domain Boot menu.

10. Start Application Designer with one of these methods:

• On Microsoft Windows 7, select Start, Programs, PeopleTools 8.55, Application Designer.

• On Microsoft Windows 8 or 2012 R2, access the Apps screen and navigate to PeopleTools 8.55,

Application Designer.

• Run PS_HOME\bin\client\winx86\pside.exe.

11. In the PeopleSoft Signon dialog box:

• Select Application Server as the Connection Type.

• Confirm that the Application Server Name is correct.

• Enter values for User ID and password.

12. Select OK to open Application Designer.

If you see the following error message when you try to sign in to the Application Server in Application Designer:

Network API: "Could not connect to application server 'Application Server⇒

 Name' Make sure the PeopleTools authentication server (PSAUTH) is booted."

This may indicate a problem with the Domain Connection Password. For example, if the password set in the

Application Server configuration file does not match the value in Configuration Manager, you may get this error message when you sign in to Application Designer in three-tier mode. Check the Application Server logs for more information.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

301

Configuring the Application Server on UNIX

Chapter 8B

Task 8B-5-3: Importing an Existing Application Server Domain

Configuration

If you have an existing application server configuration for a previous PeopleSoft PeopleTools release, you can import it to create a new domain. You can import an existing domain configuration by specifying a file or by specifying the path to an existing domain. To import from a file, you must use the psappsrv.cfg file found inside an existing application server domain folder (you must specify the full path to psappsrv.cfg). This file can be located anywhere in the file system, but must be named psappsrv.cfg. To import from an existing domain configuration that you created in PeopleSoft PeopleTools 8.55, you must specify PS_CFG_HOME and the name of an existing application server domain. (If you are importing a domain from a release before PeopleSoft

PeopleTools 8.50, note that the domains were created in PS_HOME, and that is the path that you should provide.)

To import an existing application server domain configuration:

1. Run the psadmin

command.

You see the PeopleSoft Server Administration menu, as in this example:

--------------------------------

PeopleSoft Server Administration

--------------------------------

PS_CFG_HOME:  /home/JSMITH/peopletools/8.55

PS_HOME:      /home/PT855

PS_APP_HOME:  /home/HR92

1) Application Server

2) Process Scheduler

3) Search Server

4) Web (PIA) Server

5) Switch Config Home

6) Replicate Config Home

7) Refresh Config Home q) Quit

Command to execute (1-7, q): 1

The PS_CONFIG_HOME location, also referred to as Config Home, corresponds to the current working directory. For information on how Config Home is set, see the PeopleTools: System and Server

Administration product documentation.

2. Depending on your environment, you may see a message after the initial menu, which indicates that

PSADMIN has modified the PS_CFG_HOME/peopletools.properties file with the current PS_HOME location:

*********************************************************

PS_CFG_HOME/peopletools.properties file has been updated. 

You should use the Config Home Refresh feature in PSAdmin  to ensure that all of your domains are current. 

Alternatively, you may recreate all of your domains. 

Please press any key to continue...

***********************************************************

This indicates that one of these situations exists:

• The PS_CFG_HOME that you are working with was used previously from a different PS_HOME. In this

302

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 8B

Configuring the Application Server on UNIX

case, you should recreate any existing Application Server, Process Scheduler, Search, or PIA domains in this PS_CFG_HOME.

• You configured your environment such that PS_CFG_HOME is the same as PS_HOME. The first time you use PSADMIN to create a domain, it updates the PS_CFG_HOME/peopletools.properties file.

Continue with the next step.

3. Specify 1 for Application Server.

4. Specify 4 for Import domain configuration.

--------------------------------------------

PeopleSoft Application Server Administration

--------------------------------------------

  1) Administer a domain

  2) Create a domain

  3) Delete a domain

  4) Import domain configuration

  q) Quit

 Command to execute (1-4, q): 4

5. Specify 1 for Import regular domain.

--------------------------------------------

PeopleSoft Import Application Server Configuration

--------------------------------------------

  1) Import regular domain

  2) Import IB Master Configuration

  q) Quit

Command to execute (1-2, q) : 1

6. Specify whether to import the domain configuration from a file (option 1) or from an existing application domain configuration (option 2).

--------------------------------------------

PeopleSoft Import Application Server Configuration

--------------------------------------------

  1) Import from file

  2) Import from application domain

  q) Quit

  

Command to execute (1-2, q) :

7. If you selected 1, provide the full path to the file psappsrv.cfg, and then specify the name of the domain you want to create. If you selected 2, go to the next step.

Enter full path to configuration file

:/home/oldconfig/psappsrv.cfg

Enter domain name to create

 :HRDMO

8. If you selected 2, to Import from application domain, provide the full path to the PS_CFG_HOME of the existing domain.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

303

Configuring the Application Server on UNIX

Chapter 8B

If importing from PeopleTools 8.49 or earlier, provide PS_HOME for PS_⇒

CFG_HOME.

Enter PS_CFG_HOME of domain you wish to import: /home/JSMITH⇒

/peopletools/8.55

If applicable, choose among the existing application server domains in the specified PS_CFG_HOME:

Tuxedo domain list:

  1)  HRDBA

  2)  HRDBB

Select domain number to import: 1

Enter a name for new domain:  HRDMO

After you create the domain, continue to the next task to verify that the imported configuration parameters are appropriate for the newly created domain. You may need to change the following values:

• DBName

DBName can be the same or different, depending on which database the application server needs to point to.

• DBType

DBType depends on the database type of DBName.

• UserId and UserPswd

UserId and UserPswd are the user's choice.

• Workstation Listener Port

Workstation Listener Port will need to be modified if the old domain will be up and running in the same machine.

• Jolt Listener Port

Jolt Listener Port will also need a different number if the old domain will be up and running in the same machine.

• Jolt Relay Adapter Listener Port

Jolt Relay Adapter Listener Port will need a different number if the old domain will be up and running in the same machine, and will be using Jolt Relay Adapter.

Task 8B-5-4: Setting Up a Custom Application Server Domain Configuration

The Quick-configure menu is initially displayed when you choose to configure your domain. This menu is intended for the commonly adjusted parameters—those most likely to change from domain to domain. However, there are additional configuration parameters that are not available through the Quick-configure menu. For such configuration parameters, you must use the Custom Configuration option, which you can access from the Quickconfigure menu. Feel free to skip this procedure if you have already created and configured your Application

Server using the Quick-configure menu and want to move forward.

The following steps assume you will be using PSADMIN to specify parameter settings.

To reconfigure an application server domain:

1. Run the psadmin

command.

2. Depending on your environment, you may see a message after the initial menu, which indicates that

PSADMIN has modified the PS_CFG_HOME/peopletools.properties file with the current PS_HOME

304

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 8B

Configuring the Application Server on UNIX

location:

*********************************************************

PS_CFG_HOME/peopletools.properties file has been updated. 

You should use the Config Home Refresh feature in PSAdmin  to ensure that all of your domains are current. 

Alternatively, you may recreate all of your domains. 

Please press any key to continue...

***********************************************************

This indicates that one of these situations exists:

• The PS_CFG_HOME that you are working with was used previously from a different PS_HOME. In this case, you should recreate any existing Application Server, Process Scheduler, Search, or PIA domains in this PS_CFG_HOME.

• You configured your environment such that PS_CFG_HOME is the same as PS_HOME. The first time you use PSADMIN to create a domain, it updates the PS_CFG_HOME/peopletools.properties file.

Continue with the next step.

3. Specify 1 for Application Server and press ENTER.

4. Specify 1 for Administer a domain and press ENTER.

5. Select the domain to administer and press ENTER.

6. Specify 4 for Configure this domain and press ENTER.

The option Configure this domain performs the following tasks:

• Shuts down the application server, if it is running. (Shutdown is required since the binary file PSTUXCFG must be deleted and re-created to enable new configuration values. If there are no processes running when shutdown is attempted, an error will be displayed but the script continues on. This is normal.)

• Initiates an interactive dialog, prompting for configuration parameters.

• Updates psappsrv.cfg, generates psappsrv.ubb, and internally invokes Tuxedo's tmloadcf executable to create binary file PSTUXCFG used during the domain boot process.

7. Specify 15 for Custom Configuration and press ENTER.

8. Respond to this prompt:

Do you want to change any config values (y/n):

• Specify y to start an interactive dialog to change or examine parameter values, as described in the next step.

Oracle recommends this option for more experienced users.

• Specify n if you have already edited psappsrv.cfg, skip the next step, and continue with the step to select server process options.

9. Complete the interactive dialog to specify configuration parameters.

Configuration parameters are grouped into sections. For each section, you are asked whether you want to change any parameters in that section, as in the following example:

Values for config section - Startup

                DBName=

                DBType=

                UserId=

                UserPswd=

                ConnectId=

                ConnectPswd=

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

305

Configuring the Application Server on UNIX

Chapter 8B

                ServerName=

                StandbyDBName=

                StandbyDBType=

                StandbyUserId=

                StandbyUserPswd=

                InMemoryDBName=

                InMemoryDBType=

Do you want to change any values (y/n)? [n]:  y

• Specify y to change any parameter values for the current configuration section displayed.

You are prompted for each parameter value. Either specify a new value, or press ENTER to accept the default if applicable. After pressing ENTER, you are positioned at the next parameter in that section.

When you are done with that section, you are again asked whether you want to re-edit any of the values you changed.

• Enter the user ID and user password that has security to start the application server. All application databases are delivered with one or more application server security users, usually PS or VP1.

The password you enter is hidden by masking characters.

• The parameters StandbyDBName, StandbyDBType, StandbyUserId, and StandbyUserPswd, are used for a standby database in an Oracle environment.

See PeopleTools: Data Management, "Implementing Oracle Active Data Guard."

• The parameters InMemoryDBName and InMemoryDBType are reserved for internal use.

• The WSL, JSL, and JRAD port numbers, which are found in other sections of the configuration parameters, have default values of 7000, 9000, and 9100, respectively. These values must be unique for each application server domain. You may alter the port values if necessary to ensure that they are unique

• If you do not wish to change any values, specify n and you will be prompted for the next configuration section.

Note. When setting up your application server, make a note of the values you use for Database Name,

Application Server Name (the machine name), and JSL Port. You will need to use these same values when installing the PeopleSoft Pure Internet Architecture.

See PeopleTools: System and Server Administration.

10. Select server process options.

At this point, you will be prompted to select server process options. If this is your initial installation, we suggest you accept the defaults. A message similar to this appears:

Setting Log Directory to the default... [PS_SERVDIR/LOGS]

Configuration file successfully created.

Loading new configuration...

The message "Loading new configuration" indicates that PSADMIN is generating a binary file named

PSTUXCFG, which is used to boot the application server. At this point, your application server should be properly configured.

Task 8B-5-5: Troubleshooting Common Errors

For troubleshooting help, you can access a log file through the PSADMIN PeopleSoft Domain Administration menu. The following list includes possible errors and troubleshooting tips.

• Use the PSADMIN PeopleSoft Domain Administration menu option 6 for Edit configuration/log files menu to

306

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 8B

Configuring the Application Server on UNIX

check for errors in <PS_CFG_HOME>/appserv/<domain>/LOGS/APPSRV_mmdd.LOG and

<PS_CFG_HOME>/appserv/<domain>/LOGS/TUXLOG.mmddyy.

• If a PeopleSoft server such as PSAPPSRV fails, examine your configuration parameters. The failure of the

PSAPPSRV process is often signalled by the message "Assume failed"

—which means the process has failed to start. Check the SIGNON section for misspelled or invalid database name, an invalid or unauthorized

OprId, or ConnectId or ServerName is missing or invalid. Finally, make sure the database connectivity is set correctly.

• If a WSL (or JSL) fails to start, try specifying another port number (it may be in use already by another application server domain process).

• If you are unable to start the BBL, check that your Tuxedo is installed fully and that the directory really exists.

• If the installation includes more than one application server domain on a single machine, before booting the second domain, adjust the REN server configuration to avoid conflict in one of these ways:

• Use PSADMIN to disable Event Notification (option 8 on the Quick-configure menu) for the second and subsequent app server domains.

• Change default_http_port to a value other than 7180.

• Check that you do not have older Tuxedo releases prepended in your PATH or runtime library (LIBPATH,

SHLIB_PATH or LD_LIBRARY_PATH, depending on the UNIX operating system).

See Also

PeopleTools: System and Server Administration

PeopleTools: MultiChannel Framework

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

307

Chapter 9A

Setting Up the PeopleSoft Pure Internet

Architecture in GUI Mode

This chapter discusses:

• Understanding PeopleSoft Pure Internet Architecture

• Using Authentication Domains in the PeopleSoft Pure Internet Architecture Installation

• Preparing the PeopleSoft Pure Internet Architecture File System for a PeopleTools-Only Upgrade

• Installing the PeopleSoft Pure Internet Architecture on Oracle WebLogic in GUI Mode

• Installing the PeopleSoft Pure Internet Architecture on IBM WebSphere in GUI Mode

• Testing and Administering the PeopleSoft Pure Internet Architecture Installation

• Completing Post-Installation Steps

Understanding PeopleSoft Pure Internet Architecture

This chapter explains how to install and configure the components of the PeopleSoft Pure Internet Architecture

(PIA) in GUI mode. It includes instructions for installing the PeopleSoft files on Oracle WebLogic and IBM

WebSphere. Only complete the instructions for the web server product that you installed.

Note. See the chapter "Setting Up the PeopleSoft Pure Internet Architecture in Console Mode" for instructions on installing in silent mode on Microsoft Windows.

See "Installing Web Server Products."

The setup program for the PeopleSoft Pure Internet Architecture is installed to the web server machine when you run the PeopleSoft Installer and select the PeopleSoft Web Server option.

See "Using the PeopleSoft Installer."

Oracle only supports customer installations that use web servers that are certified for PeopleSoft PeopleTools.

You must install the web server before you install the PeopleSoft Pure Internet Architecture. Before you install the PeopleSoft Pure Internet Architecture, you must also have configured an application server, as described in the previous chapter.

The location where you install the PeopleSoft Pure Internet Architecture is referred to in this documentation as

PIA_HOME. You can specify different locations for PS_HOME and PIA_HOME. After you complete the

PeopleSoft Pure Internet Architecture installation, you can locate the installation files in the directory

PIA_HOME/webserv.

For PeopleSoft PeopleTools 8.51 and later, if you are setting up the PeopleSoft Pure Internet Architecture on a

Microsoft Windows platform, the directory and path that you specify for PIA_HOME may include spaces.

However, parentheses in the directory name (for example, "C:\Program Files (x86)") are not allowed for

PIA_HOME.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

309

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

See "Preparing for Installation," Defining Installation Locations.

If your web server is on a different machine than your application server, you need to make sure you have JRE installed on your web server to run the PeopleSoft Pure Internet Architecture installation.

The initial PeopleSoft Pure Internet Architecture setup automatically creates the default PeopleSoft site named ps.

In subsequent PeopleSoft Pure Internet Architecture setups, change the site name from ps to a unique value. We recommend using the database name. This is handy for easy identification and ensures that the database web server files are installed in a unique web site.

The URL that you use to invoke the PeopleSoft Pure Internet Architecture must conform to ASN.1 specifications.

That is, it may contain only alphanumeric characters, dots ("."), or dashes ("-"). The URL must not begin or end with a dot or dash, or contain consecutive dots (".."). If the URL includes more than one portion, separated by dots, do not use a number to begin a segment if the other segments contain letters. For example,

"mycompany.second.country.com" is correct, but "mycompany.2nd.country.com" is wrong.

Review the following additional notes before beginning the PeopleSoft Pure Internet Architecture installation:

• If you want to connect between multiple application databases, you need to implement single signon.

• If the PeopleSoft Pure Internet Architecture installation encounters an error, it will indicate which log files to refer to.

See "Installing Web Server Products."

• The machine on which you run the PeopleSoft Pure Internet Architecture install must be running in 256 color

mode. This is not necessary for UNIX or console mode.

• When installing on Microsoft Windows Server 2008, change the font size to the default value.

If you use the installer with a non-default font size, some of the fields on the installer windows may appear with an incorrect length. To change the font size:

1. Right-click the desktop and select Personalize.

2. Click Adjust font size (DPI).

3. Select the default, 96 DPI.

The PeopleSoft Pure Internet Architecture installation includes the following products:

PeopleSoft Pure Internet Architecture. This product is the centerpiece of the PeopleSoft architecture that enables users to work on a machine with only a supported browser installed. This option installs the servlets required for deploying PeopleSoft Applications and for the PeopleSoft portal. The portal packs and PeopleSoft

Portal Solutions have their own installation instructions, which are available on My Oracle Support. For an overview of the various types of portals, consult the PeopleTools: Portal Technology product documentation.

PeopleSoft Report Repository. This product works in conjunction with Process Scheduler to allow report distribution over the web.

PeopleSoft Integration Gateway. This product is the entry and exit point for all messages to and from the

Integration Broker. Its Java-based Connector architecture allows asynchronous and synchronous messages to be sent over a variety of standard protocols, many that are delivered at install, or through custom connectors.

Important! For PeopleSoft PeopleTools 8.50 and later, review the product documentation concerning security properties for Integration Gateway. When setting the properties in the integrationGateways.properties

file, the property secureFileKeystorePasswd must be encrypted, and the secureFileKeystorePath must be set.

See PeopleTools: Integration Broker Administration.

PeopleSoft CTI Console. This product works in conjunction with CTI vendor software to enable call center agents to take advantage of browser-based teleset management and automatic population of application pages with relevant data associated with incoming calls, such as customer or case details.

See PeopleTools: MultiChannel Framework.

310

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Environment Management Hub. The Environment Management hub is a web application that is installed with the PeopleSoft Pure Internet Architecture and portal. It is started along with the rest of the web applications when the user boots the web server. You cannot start the Environment Management Hub on a server that is configured to run HTTPS; in other words, if you plan to run Environment Management, your PIA server needs to be configured in HTTP mode.

See PeopleTools: Change Assistant and Update Manager.

See Also

PeopleTools: Security Administration

PeopleTools: System and Server Administration

"Using the PeopleSoft Installer," Verifying Necessary Files for Installation on Windows

Using Authentication Domains in the PeopleSoft Pure Internet

Architecture Installation

You have the option to specify an authentication domain when you install the PeopleSoft Pure Internet

Architecture on Oracle WebLogic or IBM WebSphere.

Note. The authentication domain was referred to as the Authentication Token Domain in previous releases, and that term is still seen in the software.

When an authentication domain is specified during the PeopleSoft Pure Internet Architecture installation, that value gets used as the Cookie domain in the web server configuration. The main requirements when setting a cookie domain are:

• The host must have a fully qualified domain name (FQDN). The requirement that you must have a domain name does not imply that you must have a DNS, but you do need some type of naming service such as DNS or some managed ..\etc\hosts file that contains a list of the servers with their domain name.

• The cookie domain value being set must begin with a dot (.ps.com is valid, ps.com is NOT valid).

• The cookie domain value being set must contain at least 1 embedded dot (.ps.com is valid, .corp.ps.com is valid, .com is NOT valid).

• The cookie domain value can only be a single domain name. It cannot be a delimiter-separated list of domains.

By default, the browser only sends cookies back to the machine that set the cookie. So if web server crm.yourdomain.com sets a cookie, the browser will only send it back there. You can make the browser send the single signon cookie to all servers at yourdomain.com by typing your domain name in the Authentication Token

Domain list box of web server crm.

Specifying the authentication domain may be necessary in certain cases. For example, if you plan to use the

PeopleSoft portal technology, be sure to read the supporting documentation on configuring the portal environment, to determine whether setting the authentication domain is required for correct operation.

See PeopleTools: Portal Technology.

Specify an authentication domain if you plan to run a REN Server. REN Servers are required for PeopleSoft

MultiChannel Framework, Reporting, and some PeopleSoft CRM applications supported by PeopleSoft

MultiChannel Framework.

See PeopleTools: MultiChannel Framework.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

311

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

If you use the PeopleSoft Mobile Application Platform (MAP), you must specify the same authentication domain during the PeopleSoft Pure Internet Architecture installation, for MAP, and for Integration Broker and integration hubs.

See PeopleTools: Mobile Application Platform.

See PeopleTools: Integration Broker.

Task 9A-1: Preparing the PeopleSoft Pure Internet Architecture

File System for a PeopleTools-Only Upgrade

When performing the installation of the PeopleSoft Pure Internet Architecture system using the separate upgrade

PS_HOME (which is different than your old release PS_HOME), you may install and configure your PeopleSoft

Pure Internet Architecture system at this point in time of the installation, but do not start your PeopleSoft Pure

Internet Architecture system until directed to do so within the upgrade.

If you are installing into an existing PS_HOME or PIA_HOME after completing a PeopleTools-only upgrade, perform the following instructions to remove any obsolete files.

See "Preparing for Installation," Preparing for the PeopleTools-Only Upgrade.

Stop the web server before performing the PeopleSoft Pure Internet Architecture installation or uninstallation.

Depending on your web server platform, complete the following steps to clean up previous PeopleSoft Pure

Internet Architecture sites:

• Oracle WebLogic

Shut down Oracle WebLogic and follow the uninstallation instructions in the old release PeopleSoft

PeopleTools installation guide for your database platform.

Alternatively, delete the contents of one of the following directories:

• For PeopleSoft PeopleTools 8.43.x or earlier: <weblogic_home>\wlserver6.1\config\<domain_name>\*

• For PeopleSoft PeopleTools 8.44.x to 8.49.x: <PS_HOME>\webserv\<domain_name>\*

• For PeopleSoft PeopleTools 8.50.x or later: <PIA_HOME>\webserv\<domain_name>\*

• IBM WebSphere

Shut down IBM WebSphere and follow the uninstallation instructions in the old release PeopleSoft

PeopleTools installation guide for your database platform.

Task 9A-2: Installing the PeopleSoft Pure Internet Architecture on

Oracle WebLogic in GUI Mode

This section discusses:

• Prerequisites

• Installing the PeopleSoft Pure Internet Architecture on a New Oracle WebLogic Domain

• Installing the PeopleSoft Pure Internet Architecture on an Existing Oracle WebLogic Domain

• Uninstalling the PeopleSoft Pure Internet Architecture on Oracle WebLogic

312

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Prerequisites

This section describes how to install the PeopleSoft Pure Internet Architecture on Oracle WebLogic. Before installing the PeopleSoft Pure Internet Architecture (PIA) on Oracle WebLogic, you must have installed the

Oracle WebLogic software. PeopleSoft PeopleTools 8.55 supports Java 7 enabled 64-bit Oracle WebLogic 12.1.3.

See "Installing Web Server Products," Installing Oracle WebLogic.

See the PeopleTools: System and Server Administration product documentation for more information on working with Oracle WebLogic.

Task 9A-2-1: Installing the PeopleSoft Pure Internet Architecture on a New

Oracle WebLogic Domain

Use these instructions to install the PeopleSoft Pure Internet Architecture on a new Oracle WebLogic domain. See the next section to install on an existing Oracle WebLogic domain.

1. Go to PS_HOME\setup\PsMpPIAInstall and run setup.bat

.

See "Using the PeopleSoft Installer," Running the PeopleSoft Installer, for setup command options.

2. Click Next on the Welcome to the InstallAnywhere Wizard for PeopleSoft Internet Architecture window.

The window displays the PeopleSoft PeopleTools version, 8.55 in this example, and includes this note: "If installing onto a Oracle WebLogic Server, make sure to shutdown any running web servers to avoid web server corruption."

PeopleSoft Internet Architecture Welcome window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

313

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

3. Enter the location where you want to install the PeopleSoft Pure Internet Architecture, referred to in this documentation as PIA_HOME.

In this example, the directory is C:\Users\psftuser\psft\pt\8.55. The default location for PIA_HOME is the same as PS_CFG_HOME.

See "Preparing for Installation," Planning Your Initial Configuration.

PeopleSoft Internet Architecture Choose directory window

314

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

4. Select Oracle WebLogic Server as in this example, and then click Next.

PeopleSoft Internet Architecture Choose the installation type that best suits your needs window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

315

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

5. Specify the root directory where Oracle WebLogic is installed, WLS_HOME, and click Next.

In this example, the root directory for Oracle WebLogic 12.1.3.0.0 is C:\WLS1213.

Note. If you enter an incorrect path for Oracle WebLogic, you receive an error message "Detected web server version: no choices available." Check that you have Oracle WebLogic installed, and in the designated directory.

PeopleSoft Internet Architecture Choose directory window for Oracle WebLogic

316

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

6. Enter a domain name or accept the default name on the Domain Type window.

If the PIA installer cannot detect any existing Oracle WebLogic domains, only the option Create New

WebLogic Domain is available as shown in this example. The default name is peoplesoft.

Note. If the PIA installer detects an existing WebLogic domain, you also see the option Existing WebLogic

Domain, which is discussed in the next section. Verify that the option Create New WebLogic Domain is selected for this procedure. The installation process automatically generates a valid domain name in the domain name field, such as peoplesoft1.

See Installing the PeopleSoft Pure Internet Architecture on an Existing Oracle WebLogic Domain.

Click Next to continue.

PeopleSoft Internet Architecture Domain Type window for creating a new domain

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

317

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

7. Enter the administrator login ID, and enter and re-enter the password for the new web server domain to be created.

The default login ID is system as shown in this example. The password must be at least 8 alphanumeric characters with at least one number or special character.

Click Next to continue.

PeopleSoft Internet Architecture Webserver Admin Credentials window

318

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

8. Select the type of domain to create

—single server, multi server, or distributed managed server.

In this example, Single Server Domain is selected.

PeopleSoft Internet Architecture Server Type window

There are three domain configuration options:

Single Server Domain

This domain configuration contains one server named PIA, and the entire PeopleSoft application is deployed to it. This configuration is intended for single user or very small scale, non-production environments. This configuration is very similar to the Oracle WebLogic domain provided in PeopleSoft

PeopleTools 8.40 through 8.44.

Multi Server Domain

This domain configuration contains seven unique server definitions, an Oracle WebLogic cluster, and the

PeopleSoft application split across multiple servers. This configuration is intended for a production environment.

Distributed Managed Server

This option is an extension of the Multi Server Domain selection and installs the necessary files to boot a managed server. This option requires a Multi Server installation to be performed to some other location, which will contain the configuration for this managed server.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

319

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

9. Enter the Integration Gateway User name. Enter and re-enter the password for the Integration Gateway User.

The default Integration Gateway User is administrator as shown in this example. The password must be at least 8 alphanumeric characters.

See PeopleTools: Integration Broker Administration.

PeopleSoft Internet Architecture Integration Gateway Credentials window

320

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

10. Enter the AppServer Domain Connection password (optional).

If you configured your Application Server domain to require a Domain Connection password, enter it here.

Otherwise, leave it blank as shown in this example. This password will be propagated to the Integration

Gateway.

For more information about Application Server domain configuration and setting domain parameters, see the product documentation PeopleTools: System and Server Administration.

PeopleSoft Internet Architecture AppServer Connection Password window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

321

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

11. Enter a PeopleSoft web site name; the default is ps as shown in this example.

Warning! The site name can include underscores ( _ ), but an underscore cannot be followed by a numeric character or the string "newwin" (for example, my_site_3 or my_newwin_site).

PeopleSoft Internet Architecture PeopleSoft Website window

322

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

12. Specify your application server name, its JSL (Jolt Station Listener) port number, its HTTP and HTTPS port numbers, the Authentication Token Domain (optional), and click Next.

PeopleSoft Internet Architecture Server Information window

AppServer name

For the AppServer name setting, enter the name of your application server, MACHINE_NAME in this example.

JSL Port

For the JSL port setting, enter the JSL port number you specified when setting up your application server.

(The default value is 9000 as in this example.)

See "Configuring the Application Server on Windows."

See "Configuring the Application Server on UNIX."

HTTP Port

The default value for the HTTP port is 80, as shown in this example.

HTTPS Port

The default value for the HTTPS port is 443, as shown in this example.

Authentication Token Domain

Note. The value you enter for Authentication Token Domain must match the value you specify when configuring your application server, as described earlier in this book. In addition, certain installation configurations require that you specify an authentication domain.

See Using Authentication Domains in the PeopleSoft Pure Internet Architecture Installation.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

323

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

If you enter a value for Authentication Token Domain, the URL to invoke PeopleSoft Pure Internet

Architecture must include the network domain name in the URL. For example, if you do not enter an authentication domain, the URL to invoke PeopleSoft Pure Internet Architecture is http://MachineName/ps/signon.html. If you do enter a value for the authentication domain (for example,

.myCompany.com), the URL to invoke PeopleSoft Pure Internet Architecture is http://MachineName.myCompany.com/ps/signon.html. In addition, if the web server for the database is using an http port other than the default port of 80, the URL must include the port number, for example http://MachineName:8080/ps/signon.html if there is no authentication domain, or http://MachineName.myCompany.com:8080/ps/signon.html if there is an authentication domain. The

URL must also comply with the naming rules given earlier in this chapter.

See Understanding the PeopleSoft Pure Internet Architecture.

324

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

13. Enter the details for the web profile, PROD, or enter another name.

Enter a Web Profile Name, and enter the password two times. The example below shows the default web profile name, PROD, and default user ID, PTWEBSERVER.

The web profile name will be used to configure this web site. You can specify one of the other predelivered web profiles, DEV, TEST, or KIOSK, or enter a different name. If you intend to use a Web Profile User ID other than the default, PTWEBSERVER, be sure to review the information on web profile configuration and security in the PeopleTools: Portal Technology product documentation.

Note. If the PeopleSoft PeopleTools version of your database is below 8.44, then you will need to add the

PTWEBSERVER User Profile before you upgrade to the current PeopleSoft PeopleTools release. The User

Profile must include the PeopleTools Web Server role, but do not grant any other roles. Enter the password that you set for the User Profile for the User ID password in this step. The password must be at least 8 alphanumeric characters.

See the PeopleTools: Security Administration product documentation for the steps required to add a User

Profile.

PeopleSoft Internet Architecture Web Profile Credentials window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

325

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

14. Specify the root directory for the Report Repository, and click Next.

Make sure that the report repository directory is shared. You must have write access to the Report Repository directory. The default is C:\psreports, as shown in this example.

Note. In setting up the Process Scheduler to transfer reports, if you choose the FTP transfer protocol, use the same directory for the Home Directory as you use here for the report repository.

See PeopleTools: Portal Technology.

See "Setting Up Process Scheduler on Windows," Setting Up Process Scheduler to Transfer Reports and Logs to the Report Repository.

326

PeopleSoft Internet Architecture Report Repository window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

15. Verify all of your selections (click Back if you need to make any changes), and click Install to begin the installation.

The window displays a summary of the installation information, such as web server software, web server root directory, version, and so on.

PeopleSoft Internet Architecture Installation Summary window

An indicator appears showing the progress of your installation.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

327

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

16. Click Finish to complete the installation.

The default installation directory for the PIA domain is <PIA_HOME>\webserv\<domain_name>. The Install

Complete window displays the parent installation directory for the domain. In this example, this is

C:/Users/psftuser/psft/pt/8.55/webserv.

Note. If you are installing into an existing domain, you need to restart that domain.

PeopleSoft Internet Architecture Install Complete window

Task 9A-2-2: Installing the PeopleSoft Pure Internet Architecture on an

Existing Oracle WebLogic Domain

Use these instructions to install the PeopleSoft Pure Internet Architecture on an existing Oracle WebLogic domain. See the previous section to install on a new Oracle WebLogic domain.

1. Go to PS_HOME\setup\PsMpPIAInstall and run setup.bat

.

See "Using the PeopleSoft Installer," Running the PeopleSoft Installer, for setup command options.

328

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

2. Click Next on the Welcome to the InstallAnywhere Wizard for PeopleSoft Internet Architecture window.

The window displays the PeopleSoft PeopleTools version, 8.55 in this example, and includes this note: "If installing onto a Oracle WebLogic Server, make sure to shutdown any running web servers to avoid web server corruption."

PeopleSoft Internet Architecture Welcome window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

329

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

3. Enter the location where you want to install the PeopleSoft Pure Internet Architecture, referred to in this documentation as PIA_HOME.

In this example, the directory is C:\Users\psftuser\psft\pt\8.55. The default location for PIA_HOME is the same as PS_CFG_HOME.

See "Preparing for Installation," Planning Your Initial Configuration.

PeopleSoft Internet Architecture Choose directory window

330

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

4. Select Oracle WebLogic Server as in this example, and then click Next.

PeopleSoft Internet Architecture Choose the installation type that best suits your needs window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

331

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

5. Specify the root directory where Oracle WebLogic is installed, WLS_HOME, and click Next.

In this example, the root directory for Oracle WebLogic 12.1.3.0.0 is C:\WLS1213.

Note. If you enter an incorrect path for Oracle WebLogic, you receive an error message "Detected web server version: no choices available." Check that you have Oracle WebLogic installed, and in the designated directory.

PeopleSoft Internet Architecture Choose directory window for Oracle WebLogic

6. Select Existing WebLogic Domain on the Domain Type window.

332

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

7. Select the domain name from the drop-down list, peoplesoft in this example, and select one of the following options:

PeopleSoft Internet Architecture Domain Type window with options for Existing WebLogic Domain

Install additional PeopleSoft site

This option is relevant only to the PeopleSoft PORTAL web application, and does not modify or revert any other configuration settings. Select this option to install only the necessary files for defining an additional PeopleSoft site onto an existing Oracle WebLogic configuration. The new site will be accessed using its name in the URL. A site named "CRM" would be accessed using a URL similar to http://mywebserver_machine/CRM. To reset or re-create an existing PeopleSoft site, simply enter that site's name as the site to create. On your web server, a PeopleSoft site is comprised of the following directories within the PORTAL web application:

<WEBLOGIC_DOMAIN>\applications\peoplesoft\PORTAL\<site>\*

<WEBLOGIC_DOMAIN>\applications\peoplesoft\PORTAL\WEB-INF\psftdocs\<site>\*

Redeploy PeopleSoft Internet Architecture

This option affects all of the PeopleSoft Pure Internet Architecture web applications installed to the local

Oracle WebLogic domain. Select this option to redeploy all of the web components of the PeopleSoft Pure

Internet Architecture. The redeployment process updates all of the web components of the PeopleSoft Pure

Internet Architecture, without modifying the configuration files or scripts that belong to the Oracle

WebLogic server domain.

Re-create WebLogic domain and redeploy PeopleSoft Internet Architecture

This option affects Oracle WebLogic Server domain configuration and all of the PeopleSoft Pure Internet

Architecture web applications installed to the local Oracle WebLogic domain. Select this option to completely remove an existing Oracle WebLogic domain and deploy the PeopleSoft Pure Internet

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

333

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

Architecture components to create the newly specified PeopleSoft site.

Warning! Re-creating an existing domain will delete everything previously installed into that domain.

See PeopleTools: Portal Technology.

Deploy additional PeopleSoft application extensions

This option is solely for use with PeopleSoft applications. PeopleSoft application extensions are provided with certain PeopleSoft applications, and this option allows you to deploy those extensions. Consult the installation documentation for your PeopleSoft application to see if this option is appropriate. PeopleSoft

PeopleTools does not use application extensions.

8. Enter the Login ID and password that you used when creating the existing domain:

334

PeopleSoft Internet Architecture Webserver Admin Credentials window for an existing domain

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

9. Select the type of domain to create

—single server, multi server, or distributed managed server.

In this example, Single Server Domain is selected.

Note. Depending upon the operation you are carrying out for an existing domain, you may not see this window.

PeopleSoft Internet Architecture Server Type window

There are three domain configuration options:

Single Server Domain

This domain configuration contains one server named PIA, and the entire PeopleSoft application is deployed to it. This configuration is intended for single user or very small scale, non-production environments. This configuration is very similar to the Oracle WebLogic domain provided in PeopleSoft

PeopleTools 8.40 through 8.44.

Multi Server Domain

This domain configuration contains seven unique server definitions, an Oracle WebLogic cluster, and the

PeopleSoft application split across multiple servers. This configuration is intended for a production environment.

Distributed Managed Server

This option is an extension of the Multi Server Domain selection and installs the necessary files to boot a managed server. This option requires a Multi Server installation to be performed to some other location, which will contain the configuration for this managed server.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

335

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

10. Enter the Integration Gateway User name. Enter and re-enter the password for the Integration Gateway User.

The default Integration Gateway User is administrator as shown in this example. The password must be at least 8 alphanumeric characters.

See PeopleTools: Integration Broker Administration.

PeopleSoft Internet Architecture Integration Gateway Credentials window

336

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

11. Enter the AppServer Domain Connection password (optional).

If you configured your Application Server domain to require a Domain Connection password, enter it here.

Otherwise, leave it blank as shown in this example. This password will be propagated to the Integration

Gateway.

For more information about Application Server domain configuration and setting domain parameters, see the product documentation PeopleTools: System and Server Administration.

PeopleSoft Internet Architecture AppServer Connection Password window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

337

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

12. If you selected the option Deploy additional PeopleSoft application extensions on the Domain Type window, enter the location where you installed the PeopleSoft application software, PS_APP_HOME, in this example

C:\FSCM92:

PeopleSoft Internet Architecture Choose Apps Install Home window

338

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

13. For the option Deploy additional PeopleSoft application extensions, select the application packages to deploy,

FIN/SCM PeopleSoft eProcurement in this example:

PeopleSoft Internet Architecture Application Package window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

339

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

14. Enter a PeopleSoft web site name; in this example the name is psone.

Warning! The site name can include underscores ( _ ), but an underscore cannot be followed by a numeric character or the string "newwin" (for example, my_site_3 or my_newwin_site).

PeopleSoft Internet Architecture PeopleSoft Website window

340

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

15. Specify your application server name, its JSL (Jolt Station Listener) port number, its HTTP and HTTPS port numbers, the Authentication Token Domain (optional), and click Next.

Note. The fields that appear on this window may change depending upon the type of operation you are carrying out for an existing domain.

PeopleSoft Internet Architecture Server Information window

AppServer name

For the AppServer name setting, enter the name of your application server, MACHINE_NAME in this example.

JSL Port

For the JSL port setting, enter the JSL port number you specified when setting up your application server.

(The default value is 9000 as in this example.)

See the chapter on configuring the application server in this documentation.

HTTP Port

The default value for the HTTP port is 80, as shown in this example.

HTTPS Port

The default value for the HTTPS port is 443, as shown in this example.

Authentication Token Domain

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

341

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

Note. The value you enter for Authentication Token Domain must match the value you specify when configuring your application server, as described earlier in this book. In addition, certain installation configurations require that you specify an authentication domain.

See Using Authentication Domains in the PeopleSoft Pure Internet Architecture Installation.

If you enter a value for Authentication Token Domain, the URL to invoke PeopleSoft Pure Internet

Architecture must include the network domain name in the URL. For example, if you do not enter an authentication domain, the URL to invoke PeopleSoft Pure Internet Architecture is http://MachineName/ps/signon.html. If you do enter a value for the authentication domain (for example,

.myCompany.com), the URL to invoke PeopleSoft Pure Internet Architecture is http://MachineName.myCompany.com/ps/signon.html. In addition, if the web server for the database is using an http port other than the default port of 80, the URL must include the port number, for example http://MachineName:8080/ps/signon.html if there is no authentication domain, or http://MachineName.myCompany.com:8080/ps/signon.html if there is an authentication domain. The

URL must also comply with the naming rules given earlier in this chapter.

See Understanding the PeopleSoft Pure Internet Architecture.

342

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

16. Enter the details for the web profile, PROD, or enter another name.

Enter a Web Profile Name, and enter the password two times. The example below shows the default web profile name, PROD, and default user ID, PTWEBSERVER.

The web profile name will be used to configure this web site. You can specify one of the other predelivered web profiles, DEV, TEST, or KIOSK, or enter a different name. If you intend to use a Web Profile User ID other than the default, PTWEBSERVER, be sure to review the information on web profile configuration and security in the PeopleTools: Portal Technology product documentation.

Note. If the PeopleSoft PeopleTools version of your database is below 8.44, then you will need to add the

PTWEBSERVER User Profile before you upgrade to the current PeopleSoft PeopleTools release. The User

Profile must include the PeopleTools Web Server role, but do not grant any other roles. Enter the password that you set for the User Profile for the User ID password in this step. The password must be at least 8 alphanumeric characters.

See the PeopleTools: Security Administration product documentation for the steps required to add a User

Profile.

PeopleSoft Internet Architecture Web Profile Credentials window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

343

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

17. Specify the root directory for the Report Repository, and click Next.

Make sure that the report repository directory is shared. You must have write access to the Report Repository directory. The default is C:\psreports, as shown in this example.

Note. In setting up the Process Scheduler to transfer reports, if you choose the FTP transfer protocol, use the same directory for the Home Directory as you use here for the report repository.

See PeopleTools: Portal Technology.

See "Setting Up Process Scheduler on Windows," Setting Up Process Scheduler to Transfer Reports and Logs to the Report Repository.

344

PeopleSoft Internet Architecture Report Repository window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

18. Verify all of your selections (click Back if you need to make any changes), and click Install to begin the installation.

The window displays a summary of the installation information, such as web server software, web server root directory, version, and so on.

PeopleSoft Internet Architecture Installation Summary window

An indicator appears showing the progress of your installation.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

345

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

19. Click Finish to complete the installation.

The default installation directory for the PIA domain is <PIA_HOME>\webserv\<domain_name>. The Install

Complete window displays the parent installation directory for the domain. In this example, this is

C:/Users/psftuser/psft/pt/8.55/webserv.

Note. If you are installing into an existing domain, you need to restart that domain.

PeopleSoft Internet Architecture Install Complete window

Task 9A-2-3: Uninstalling the PeopleSoft Pure Internet Architecture on

Oracle WebLogic

To remove a PIA domain deployed on Oracle WebLogic, delete the folder <PIA_HOME>\webserv\

<domain_name>. If there is more than one domain, delete the domain_name folder for every domain you want to remove.

Task 9A-3: Installing the PeopleSoft Pure Internet Architecture on

IBM WebSphere in GUI Mode

This section discusses:

• Prerequisites

• Installing the PeopleSoft Pure Internet Architecture on IBM WebSphere

346

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

• Uninstalling the PeopleSoft Pure Internet Architecture from IBM WebSphere

Prerequisites

The information in this section applies to the installation of PeopleSoft Pure Internet Architecture (PIA) on an

IBM WebSphere Application Server. PeopleSoft PeopleTools 8.52 and later releases require a 64–bit IBM

WebSphere ND installation. PeopleSoft PeopleTools 8.55 supports 64–bit IBM WebSphere 8.5.5.0. Review the following points before beginning the installation:

• Before installing the PeopleSoft Pure Internet Architecture on IBM WebSphere Application Server Network

Deployment, (referred to here as IBM WebSphere ND) you must have installed the IBM WebSphere ND software.

• Each IBM WebSphere Application Server runs one PeopleSoft Pure Internet Architecture application. If you need to install more than one PeopleSoft Pure Internet Architecture application on your IBM WebSphere

Application Server, you must run the PIA installation again.

• When installing PIA on IBM WebSphere ND, you must work with a local copy of the PIA installation software; you cannot install remotely. If you are doing the installation on a machine other than the one on which you installed PeopleSoft PeopleTools, copy the PS_HOME\setup\PsMpPIAInstall directory to the local machine and keep the same directory structure.

• Both IBM WebSphere Application Server Network Deployment and PeopleSoft Pure Internet Architecture need to be installed and deployed using the same user ID. Following this requirement avoids any security and profile management issues.

See Also

"Installing Web Server Products," Installing IBM WebSphere Application Server

Task 9A-3-1: Installing the PeopleSoft Pure Internet Architecture on IBM

WebSphere

To install PIA on IBM WebSphere ND:

1. Go to PS_HOME\setup\PsMpPIAInstall.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

347

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

2. Double-click on setup.bat

.

See "Using the PeopleSoft Installer," Running the PeopleSoft Installer, for setup command options.

The Welcome window appears with the PeopleSoft PeopleTools version, which is 8.55 in this example.

PeopleSoft Internet Architecture Welcome window

348

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

3. Click Next in the Welcome window, and specify the directory where you want to install the PeopleSoft Pure

Internet Architecture, referred to here as PIA_HOME.

The default path for PIA_HOME is the PS_CFG_HOME path. In this example, the directory is

C:\Users\psftuser\psft\pt\8.55.

PeopleSoft Internet Architecture Choose directory window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

349

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

4. Select the option IBM WebSphere Server as the installation type as shown in this example, and click Next.

PeopleSoft Internet Architecture Choose the installation type that best suits your needs window

350

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

5. Specify the directory where IBM WebSphere ND was installed, referred to as WAS_HOME.

The WebSphere Application Server directory in this example is C:\IBM\WebSphere\AppServer. Click Next.

PeopleSoft Internet Architecture Choose directory window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

351

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

6. Enter an application (domain) name or accept the default name on the Domain Type window. Select the type of configuration from the options Single Server Installation or Multi Server Installation.

If the PIA installer cannot detect any existing IBM WebSphere applications, only the option Create New

WebSphere Application is available. The default name is peoplesoft as shown in this example.

Note. The name you specify here for each application must be unique for each IBM WebSphere node.

352

PeopleSoft Internet Architecture Domain Type window for creating a new WebSphere Application

Single Server Installation

The Single Server Installation option creates one WebSphere Application Server profile to hold all the

PeopleSoft web applications. The installer uses the application name you enter for the new profile's name.

Multi Server Installation

The Multi Server Installation option creates a single profile with the name you enter as the application name on this page. The profile includes two servers, which deploy discrete functionality and are found on different ports, as specified in the following table:

Server Name

server1

Purpose

PORTAL applications

HTTP or HTTPS Port Number

X psemhub PeopleSoft Environment

Management Framework applications (PSEMHUB)

X+1

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

7. If there are existing IBM WebSphere applications on your system, select one of the options Create New

WebSphere Application or Existing WebSphere Application.

If you select Create New WebSphere Application, the installation process automatically generates a valid domain name in the domain name field, such as peoplesoft1.

If you attempt to enter an invalid domain name, you see a prompt asking you to enter a new domain name or choose an existing domain.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

353

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

8. If you select the Existing WebSphere Application option, you can choose from a drop-down list of existing application names, and can select whether to install an additional PeopleSoft site, redeploy PeopleSoft Internet

Architecture, or deploy additional PeopleSoft application extensions.

Note. Make sure the server is up and running before installing an additional PeopleSoft site, redeploying PIA, or deploying additional PeopleSoft application extensions.

354

PeopleSoft Internet Architecture Domain Type window for an existing WebSphere Application

Install additional PeopleSoft site

Select this option to install only the necessary files for defining an additional PeopleSoft site onto the existing

IBM WebSphere ND web server configuration.

Redeploy PeopleSoft Internet Architecture

This selection affects all of the PeopleSoft Pure Internet Architecture web applications installed to the local

IBM WebSphere Application Server profile. The redeployment process updates all of the web components of the PeopleSoft Pure Internet Architecture.

Deploy additional PeopleSoft application extensions

This option is solely for use with PeopleSoft product applications. PeopleSoft application extensions are provided with certain PeopleSoft applications, and this option allows you to deploy those extensions. Consult the installation documentation for your PeopleSoft application to see whether this option is appropriate.

PeopleSoft PeopleTools does not use application extensions.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

9. Enter the IBM WebSphere administrator Login ID, and enter the password two times.

Note. The default administrator login ID is system as shown in this example. The password must be at least 8 alphanumeric characters with one number or special character. Use these criteria to log into the IBM

WebSphere administrative console.

If you selected Create New WebSphere Application in the previous step, the following window appears.

PeopleSoft Internet Architecture Webserver Admin Credentials window

If you selected the Existing WebSphere Application option, and either Install additional PeopleSoft site or

Redeploy PeopleSoft Internet Architecture, the following window appears. Enter the same Login ID and password as you entered for the original IBM WebSphere Application creation. If the Login ID and password do not match the original values, you cannot continue with the PIA installation.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

355

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

PeopleSoft Internet Architecture Webserver Admin Credentials window for existing WebSphere profile

10. If there are PeopleSoft application packages in the archives directory, the PIA installer asks whether you want to deploy them.

If you are using an existing domain, you will only be prompted if you selected Deploy additional PeopleSoft extensions.

356

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

11. Enter the Integration Gateway User and enter the password two times.

The default Integration Gateway User is administrator, as shown in this example.

PeopleSoft Internet Architecture Integration Gateway Credentials window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

357

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

12. Enter the AppServer Domain Connection password two times (optional).

In this example, the password fields are blank.

Chapter 9A

PeopleSoft Internet Architecture AppServer Connection Password window

358

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

13. Enter a PeopleSoft web site name; the default is ps as shown in this example.

Warning! The site name can include underscores ( _ ), but an underscore cannot be followed by a numeric character or the string "newwin" (for example, my_site_3 or my_newwin_site).

PeopleSoft Internet Architecture PeopleSoft Website window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

359

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

14. Specify your application server name, its JSL (Jolt Station Listener) port number, its HTTP and HTTPS port numbers, the authentication token domain, and click Next.

360

PeopleSoft Internet Architecture Server Information window

AppServer name

For AppServer name, enter the name of your application server. The name is MACHINE_NAME in this example.

JSL port

For the JSL port, enter the JSL port number you specified when setting up your application server. (The default value is 9000 as shown in this example.)

See "Configuring the Application Server on Windows."

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

HTTP and HTTPS ports

The default HTTP port is 80, and the default HTTPS port is 443, as shown in this example.

When you enter HTTP and HTTPS port numbers, they will not be recognized until you restart your

WebSphere server.

In the case of Multi Server Installation type, HTTP and HTTPS ports cannot be consecutive numbers. The range for port number will be <Port#>-<Port#>+1 for the two application servers that the install creates.

For example, if you select HTTP Port as 5555 and HTTPS port as 5560 then the ports are assigned as given below.

Server Name

server1

HTTP Port Number

5555

HTTPS Port Number

5560 psemhub 5556 5561

Authentication Token Domain

The value you enter for Authentication Token Domain must match the value you specify for the authentication domain when configuring your application server, as described earlier in this book. In addition, certain installation configurations require that you specify an authentication domain.

See Using Authentication Domains in the PeopleSoft Pure Internet Architecture Installation.

If you enter a value for the Authentication Token Domain, the URL to invoke PIA must include the network domain name in the URL. For example, if you do not enter an authentication domain, the URL to invoke PIA is http://MachineName:port/ps/signon.html. If you do enter a value for the authentication domain (for example, .myCompany.com), the URL to invoke PIA is http://MachineName.myCompany.com:port/ps/signon.html. The URL must also comply with the naming rules given earlier in this chapter.

See Understanding the PeopleSoft Pure Internet Architecture.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

361

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

15. Enter the details for the web profile, PROD, or enter another name.

The following example shows the default web profile name, PROD, and default user ID, PTWEBSERVER.

The web profile name will be used to configure this web site. You can specify one of the other predelivered web profiles, DEV, TEST, or KIOSK, or enter a different name. If you intend to use a Web Profile User ID other than the default, be sure to review the information on web profile configuration and security.

Enter and re-enter the password that you set for the User Profile for the User ID password in this step. The password must be at least 8 alphanumeric characters.

For more information on configuring web profiles, see the PeopleTools: Portal Technology product documentation.

Note. If the PeopleSoft PeopleTools version of your database is below 8.44, then you will need to add the

PTWEBSERVER User Profile before you upgrade to the current PeopleSoft PeopleTools release. The User

Profile must include the PeopleTools Web Server role, but do not grant any other roles. Enter the password that you set for the User Profile for the User ID password in this step, as shown in this example. See the product documentation PeopleTools: Security Administration for the steps required to add a User Profile.

362

PeopleSoft Internet Architecture Web Profile Credentials window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

16. Specify the root directory for the Report Repository (c:\psreports by default as shown in this example), and click Next.

Make sure that the report repository directory is shared, and that you have write access.

Note. In setting up the Process Scheduler to transfer reports, if you choose the FTP protocol, use the same directory for the Home Directory as you use here for the report repository.

See "Setting Up Process Scheduler on Windows," Setting Up Process Scheduler to Transfer Reports and Logs to the Report Repository.

PeopleSoft Internet Architecture Report Repository window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

363

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

17. Verify all your selections on the summary window.

The window lists the installation information, such as the web server type, directory, version, and so on. Click

Back if you need to make any changes and click Next to begin the installation. An indicator shows the progress of your installation.

PeopleSoft Internet Architecture Installation Summary window

364

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

18. Click Done to complete the installation.

The default installation directory for a specific PIA profile is <PIA_HOME>\webserv\<profile_name>. The

Install Complete window displays the parent installation directory for the domain. In this example, this is

C:/Users/psftuser/psft/pt/8.55/webserv.

PeopleSoft Internet Architecture Install Complete window

Task 9A-3-2: Uninstalling the PeopleSoft Pure Internet Architecture from

IBM WebSphere

You cannot uninstall PeopleSoft Pure Internet Architecture simply by deleting <PIA_HOME>\webserv\

<profile_name>, without uninstalling it from IBM WebSphere Administration Console. If you do so, the IBM

WebSphere registry becomes corrupt, and subsequent attempts to install PeopleSoft Pure Internet Architecture will fail. Instead, if necessary, you must uninstall PeopleSoft Pure Internet Architecture on IBM WebSphere as described here.

To uninstall PeopleSoft Pure Internet Architecture on IBM WebSphere:

1. Open the IBM WebSphere Administration Console by entering the following URL in a browser: http://<machine-name>:<administrative_console_port>/ibm/console

To find the value for <administrative_console_port>, refer to <PIA_HOME>\webserv\<profile_name>\ logs\AboutThisProfile.txt.

2. Log in as any user.

3. Choose Applications, Application Types, Websphere enterprise applications.

4. Select the check boxes for the PeopleSoft Pure Internet Architecture applications you want to uninstall, and

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

365

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A click Stop.

5. Select the check boxes for the PeopleSoft Pure Internet Architecture applications you want to uninstall, and click Uninstall.

6. Save your configuration.

7. Log out of the IBM WebSphere Administration Console.

8. Stop WebSphere server using one of the following commands:

On Microsoft Windows:

<PIA_HOME>\webserv\<profile_name>\bin\stopServer.bat server1

On UNIX or Linux:

<PIA_HOME>/webserv/<profile_name>/bin/stopServer.sh server1

9. In addition to uninstalling the application, you need to remove the WebSphere Application Server profile, which was created during PIA install, to complete the PIA uninstallation.

To uninstall the WebSphere Application Server profile, run the following steps: a. Go to <PIA_HOME>\webserv\<profile_name>\bin b. Run one of the following commands, where <profile_name> indicates the application name that you have selected during the PIA install.

On Microsoft Windows: manageprofiles.bat -delete -profileName <profile_name>

On UNIX or Linux: manageprofiles.sh -delete -profileName <profile_name> c. Delete the directory <PIA_HOME>\webserv\<profile_name>

Task 9A-4: Testing and Administering the PeopleSoft Pure

Internet Architecture Installation

This section discusses:

• Verifying the PeopleSoft Pure Internet Architecture Installation

• Starting and Stopping Oracle WebLogic

• Starting and Stopping IBM WebSphere Application Servers

• Using PSADMIN to Start and Stop Web Servers

• Accessing the PeopleSoft Signon

Verifying the PeopleSoft Pure Internet Architecture Installation

After installing the PeopleSoft Pure Internet Architecture, you should make sure that your configuration is functional. You can test this by signing on to PeopleSoft, navigating within the menu structure, and accessing pages. (Make sure the application server is configured and booted.) This section includes procedures to start and stop the Oracle WebLogic or IBM WebSphere web servers whenever necessary.

366

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Task 9A-4-1: Starting and Stopping Oracle WebLogic

If you are using the Oracle WebLogic web server, you need to sign on to Oracle WebLogic before using these commands. If you are using IBM WebSphere instead, go on to the next section. Use the following commands in the Oracle WebLogic domain directory.

Note. Starting from Oracle WebLogic 9.2 and later releases, all the Life-cycle management scripts and other batch scripts for the PIA server on Oracle WebLogic are located in <PIA_HOME>\webserv\<domain_name>\bin folder.

• To start Oracle WebLogic Server as a Windows service, use the following command:

Single Server: installNTservicePIA.cmd

Multiple Servers or Distributed Servers: installNTservice.cmd ServerName

The resulting Windows service name will be WebLogicDomain-WebLogicServer. For example, to install a server named PIA as a Windows service in a domain named peoplesoft, run installNTservice.cmd

PIA

and you will see "peoplesoft-PIA" as a service.

• To remove an Oracle WebLogic server Windows service, use the following command: uninstallNTservicePIA.cmd Server Name

Note. If you modify setenv.cmd, then you must uninstall the service using uninstallNTServicePIA.cmd ServerName

, and then re-run installNTServicePIA.cmd

ServerName

.

• To start Oracle WebLogic Server as a foreground process on a single server, use the following commands: startPIA.cmd (on Windows) startPIA.sh (on UNIX)

• To start Oracle WebLogic Server as a foreground process on multiple-servers or distributed servers, use the following commands:

1. Execute: startWebLogicAdmin.cmd (on Windows) startWebLogicAdmin.sh (on UNIX)

2. Then execute: startManagedWebLogic.cmd ManagedServerName (on Windows) startManagedWebLogic.sh ManagedServerName (on UNIX)

• To stop the server, use the following commands:

• Single Server: stopPIA.cmd (on Windows) stopPIA.sh (on UNIX)

• Multiple Servers or Distributed Servers: stopWebLogic.cmd ManagedServerName (on Windows)

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

367

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A stopWebLogic.sh ManagedServerName (on UNIX)

For more information on working with Oracle WebLogic multiple servers or distributed servers, see the

PeopleTools: System and Server Administration product documentation.

Note. For more information on working with Oracle WebLogic multiple or distributed servers, search My Oracle

Support.

Task 9A-4-2: Starting and Stopping IBM WebSphere Application Servers

This section discusses:

• Starting and Stopping IBM WebSphere Application Servers on Windows

• Starting and Stopping IBM WebSphere Application Servers on UNIX or Linux

• Verifying the IBM WebSphere Installation

Starting and Stopping IBM WebSphere Application Servers on Windows

To start and stop the WebSphere Application Server Network Deployment 8.5.5.0 (WebSphere ND), use the

WebSphere First Steps utility:

368

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

1. On Microsoft Windows 7, select Start, Programs, IBM WebSphere, IBM WebSphere Application Server

V8.5, Profiles, profile_name, First steps.

On Microsoft Windows 8 or 2012 R2, access the Apps screen and locate the First steps utility in the IBM

WebSphere category.

The following example shows the First steps window for the profile peoplesoftWAS:

WebSphere Application Server First Steps window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

369

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

2. Select the link Start the server.

If the server starts properly, a verification window appears with several messages about the initialization process, as in this example:

First steps output - Installation verification window

3. To verify whether the server was installed and can start properly, click the link Installation Verification on the

First Step window.

Starting and Stopping IBM WebSphere Application Servers on UNIX or Linux

To start WebSphere ND on UNIX or Linux, use the following command:

<PIA_HOME>/webserv/<profile_name>/bin/startServer.sh <server_name>

For example:

/home/pt855/webserver/peoplesoft/bin/startServer.sh server1

To stop WebSphere ND, use the following command:

<PIA_HOME>/webserv/<profile_name>/bin/stopServer.sh <server_name>

Verifying the IBM WebSphere Installation

Use this method to verify the WebSphere ND and PIA installation for both Microsoft Windows and UNIX.

370

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

To verify the WebSphere ND and PIA installation, copy the following URL into a browser address bar, substituting your machine name and the http port number: http://<machine_name>:<http_port>/ivt/ivtservlet

You should see the text "IVT Servlet" in the browser, as in this example:

IVT Servlet window

You should also sign into the PeopleSoft application, as described in a later section, to verify the installation.

See Accessing the PeopleSoft Signon.

Task 9A-4-3: Using PSADMIN to Start and Stop Web Servers

In addition to the methods given in the previous sections for starting and stopping Oracle WebLogic and IBM

WebSphere web servers, in PeopleSoft PeopleTools 8.52 and later releases you can use PSADMIN to administer a web server domain.

See PeopleTools: System and Server Administration.

To start and stop web servers:

1. Go to the PS_HOME/appserv directory and run the command psadmin

.

2. Specify 4 for Web (PIA) Server.

--------------------------------

PeopleSoft Server Administration

--------------------------------

  PS_HOME:   :  C:\pt855

  PS_CFG_HOME:  C:\psft_AppServ

  1) Application Server

  2) Process Scheduler

  3) Search Server

  4) Web (PIA) Server

  5) Switch Config Home

  6) Service Setup

  7) Replicate Config Home

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

371

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

  q) Quit

Command to execute (1-7, q): 4

The location of Config Home is the current working directory. The PSADMIN utility determines the Config

Home directory by checking for the PS_CFG_HOME environment variable. If that is not set, it checks for the presence of domains in the default PS_CFG_HOME location. If none exists, it uses the PS_HOME location from which it was launched.

See "Preparing for Installation," Defining Installation Locations.

3. Select 1 for Administer a domain.

-----------------------------

PeopleSoft PIA Administration

-----------------------------

  PIA Home:   C:\psft_WebServ

  1) Administer a domain

  2) Create a domain

  3) Delete a domain

  q) Quit

Command to execute: 1

The PSADMIN utility determines the PIA Home location displayed here by first checking for a PIA_HOME environment variable. If none is set, it checks for the PS_CFG_HOME environment variable. If neither is set, it uses the default PS_CFG_HOME directory.

4. Select the domain you want to administer by entering the appropriate number.

------------------------------------------------------

PeopleSoft PIA Domain Administration - Choose a Domain

------------------------------------------------------

1) psftTST  

2) peoplesoft q) Quit

Command to execute: 2

5. To start a web server domain, enter 1, Boot this domain.

------------------------------------

PeopleSoft PIA Domain Administration

------------------------------------

  PIA Home:      C:\psft_WebServ

  PIA Domain:    peoplesoft

  Domain Status: stopped

  1) Boot this domain

  2) Shutdown this domain

  3) Get the status of this domain

  4) Configure this domain

372

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

  5) Edit configuration files

  6) View log files

  7) Administer a site

  8) Delete a site

  9) Windows Service Setup

  q) Quit

Command to execute: 1

The boot command invokes the startPIA.cmd script, and you see the progress and a status message on the console window.

Starting the domain..................

...

Verifying domain status..

The domain has started.

6. To stop a web server domain, select 2, Shutdown this domain.

The shutdown command invokes the stopPIA.cmd script, and you see the progress and a status message on the console window.

Stopping the domain.....

.....

Verifying domain status..........

The domain has stopped.

7. To set up a Windows service, select 9, Windows Service Setup.

8. Select 1 to install a service, or 2 to remove it.

This command invokes the installNTservice script, and creates a service named WebLogicDomain-

WebLogicServer.

---------------------

Windows Service Setup

---------------------

  PIA Home:      C:\psft_websrv

  PIA Domain:    peoplesoft

  Domain status: started

  1) Install Service

  2) Uninstall Service

  q) Quit

Command to execute:

Task 9A-4-4: Accessing the PeopleSoft Signon

To access the PeopleSoft signon:

1. Open your web browser.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

373

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A

2. Enter the name of the site you want to access

—for example (the default value for <site_name> is ps): http://<machine_name>:<http_port>/<site_name>/signon.html

Note. PeopleSoft Pure Internet Architecture installed on IBM WebSphere server listens at the HTTP/HTTPS ports specified during the PeopleSoft Pure Internet Architecture install. Invoke PeopleSoft Pure Internet

Architecture through a browser by using the specified HTTP or HTTPS ports—that is, http://

<WebSphere_machine_name>:<server_port>/<site_name>/signon.html (if AuthTokenDomain is not specified ) or http://<WebSphere_machine_name.mycompany.com>:<server_port>/<site_name>/ signon.html (if you specified .mycompany.com as the AuthTokenDomain). You can find the HTTP and

HTTPS ports in the file <PIA_HOME>/webserv/<domain_name>/logs/AboutThisProfile.txt.

This will take you to the sign-in window corresponding to your browser's language preference, as shown in this example:

374

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Oracle PeopleSoft Enterprise Sign in window

Note. If you do not see the signon screen, check that you supplied all the correct variables and that your application server and the database server are running.

3. Sign in to the PeopleSoft system by entering a valid user ID and password.

The user ID and password are case sensitive.

Note. The user ID and password were set during the database configuration and also used to boot the application server.

The PeopleSoft PeopleTools and PeopleSoft applications include various default user IDs. For information on using the user IDs delivered with your PeopleSoft application demo database, see the application-specific

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

375

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Chapter 9A installation instructions. For information on using and securing PeopleSoft PeopleTools default user IDs, see the information on administering user profiles in the PeopleTools: Security Administration product documentation.

Task 9A-5: Completing Post-Installation Steps

This section discusses:

• Using Fluid User Interface

• Updating the Installation Table

• Setting Options for Multilingual Databases

• Updating PeopleTools Options

• Updating Database Information

Task 9A-5-1: Using Fluid User Interface

When you sign in to your PeopleSoft application, you may see the PeopleSoft Fluid User Interface by default. To access the menu items, as seen in the classic user interface, from the PeopleSoft Fluid User Interface:

376

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

1. On the PeopleSoft Fluid User Interface, shown in this example, select (press) the NavBar button at the top right (diamond inside a circle).

PeopleSoft Fluid User Interface home page

The Navigation bar (NavBar) side page appears.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

377

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

2. Select (press) Navigator.

Chapter 9A

NavBar side page

The menu structure appears.

378

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

3. Navigate to the desired item, such as Set Up HCM or PeopleTools.

Navigator side page with PeopleSoft menu items

See Also

PeopleTools: Applications User's Guide, "Working With Fluid Homepages"

PeopleTools: Fluid User Interface Developer's Guide

Task 9A-5-2: Updating the Installation Table

After you complete the installation process, creating the database, installing the Application Server, and installing the PeopleSoft Pure Internet Architecture, you must complete this additional step. The license codes from the

Oracle license code site mentioned earlier install all products available in the installation package. This postinstallation step ensures that only the products for which you are licensed are active in the installation. The location of the installation table in the PeopleSoft system varies depending upon the PeopleSoft application that you installed.

To update the installation table:

1. Sign on to the PeopleSoft system.

2. Select Set Up Application_name (where Application_name is the PeopleSoft application you installed),

Install, Installation Table.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

379

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Select the Products tab.

3. Clear the check boxes for the products for which you have not obtained a license.

See Also

"Using the PeopleSoft Installer," Obtaining License Codes

Accessing the PeopleSoft Signon

Task 9A-5-3: Setting Options for Multilingual Databases

Chapter 9A

Setting the Data Field Length Checking Option

The value to specify data field length checking must be set correctly in order for PeopleSoft applications to perform correctly in a browser. Use one of these methods to set the data field length checking option:

• Select PeopleTools, Utilities, Administration, PeopleTools Options, and select the Data Field Length

Checking option from the drop-down list.

• Alternatively, use the SQL tool for your database platform to modify the DBLENGTHTYPE parameter in the

PSOPTIONS table.

See PeopleTools: Global Technology, "Setting Data Field Length Checking."

See PeopleTools: Global Technology, "Selecting Character Sets."

Use the guidelines in this table to select the correct option for your environment:

Environment

Unicode-encoded database or a non-

Unicode SBCS database

PeopleTools Option Page Selection

Others

PSOPTIONS.DBLENGTHTYPE Value

N

Japanese database on DB2 LUW DB2 MBCS

Non-Unicode Japanese database MBCS

Note. If your installation uses the Shift-

JIS character set for Japanese, you must use this option.

Note. The MBCS option is not supported for DB2 z/OS.

D

M

Setting the Unicode Enabled Option

If you are running a Unicode database, verify that the UNICODE_ENABLED parameter in the PSSTATUS table is set correctly. For example:

• For non-Unicode databases, including those using the Shift-JIS character set for Japanese, set

UNICODE_ENABLED=0.

• For Unicode databases, set UNICODE_ENABLED=1.

See the information on converting to Unicode in the PeopleTools: Global Technology product documentation.

380

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9A

Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode

Task 9A-5-4: Updating PeopleTools Options

You can set the following options on the PeopleTools Options page:

• Multi-Currency — Select this check box if you plan to use currency conversion.

See PeopleTools: Global Technology, "Using System-Wide Multicurrency Settings."

• Base Time Zone — Enter a value for the base time zone for your PeopleTools database.

See PeopleTools: Global Technology, "Setting the Base Time Zone."

• Sort Order Option — If you specified a non-binary sort order for your database, choose the Sort Order Option that most closely approximates your database sort order.

See PeopleTools: Global Technology, "Setting the Sort Order."

Task 9A-5-5: Updating Database Information

The database information updated in this procedure is used by the PeopleSoft software update tools to identify your PeopleSoft database when searching for updates. These steps should be followed for all additional databases that you create to enable the accurate identification of your databases.

1. Sign on to your PeopleSoft database.

2. Navigate to PeopleTools, Utilities, Administration, PeopleTools Options.

3. Specify long and short names for your environment. For example:

• Environment Long Name — Customer HR Demo Database

• Environment Short Name — HR Demo DB

4. Select a system type from the drop-down list. For example, Demo Database.

5. Save your changes.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

381

Chapter 9B

Setting Up the PeopleSoft Pure Internet

Architecture in Console Mode

This chapter discusses:

• Understanding PeopleSoft Pure Internet Architecture

• Using Authentication Domains in the PeopleSoft Pure Internet Architecture Installation

• Preparing the PeopleSoft Pure Internet Architecture File System for a PeopleTools-Only Upgrade

• Installing the PeopleSoft Pure Internet Architecture on Oracle WebLogic in Console Mode

• Installing the PeopleSoft Pure Internet Architecture on IBM WebSphere in Console Mode

• Installing the PeopleSoft Pure Internet Architecture in Silent Mode

• Testing and Administering the PeopleSoft Pure Internet Architecture Installation

• Completing Post-Installation Steps

Understanding PeopleSoft Pure Internet Architecture

This chapter explains how to install and configure the components of the PeopleSoft Pure Internet Architecture in console mode and in silent mode. It includes instructions for installing the PeopleSoft files on Oracle WebLogic and IBM WebSphere. Only complete the instructions for the web server product that you installed.

Note. The console mode installation is typically used on UNIX platforms.

See "Installing Web Server Products."

The setup program for the PeopleSoft Pure Internet Architecture is installed to the web server machine when you run the PeopleSoft Installer and select the PeopleSoft Web Server option.

See "Using the PeopleSoft Installer."

Oracle only supports customer installations that use web servers that are certified for PeopleSoft PeopleTools.

You must install the web server before you install the PeopleSoft Pure Internet Architecture. Before you install the PeopleSoft Pure Internet Architecture, you must also have configured an application server, as described in the previous chapter.

The location where you install the PeopleSoft Pure Internet Architecture is referred to in this documentation as

PIA_HOME. You can specify different locations for PS_HOME and PIA_HOME. After you complete the

PeopleSoft Pure Internet Architecture installation, you can locate the installation files in the directory

PIA_HOME/webserv.

For PeopleSoft PeopleTools 8.51 and later, if you are setting up the PeopleSoft Pure Internet Architecture on a

Microsoft Windows platform, the directory and path that you specify for PIA_HOME may include spaces.

However, parentheses in the directory name (for example, "C:\Program Files (x86)") are not allowed for

PIA_HOME.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

383

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Chapter 9B

See "Preparing for Installation," Defining Installation Locations.

Before performing the steps in this chapter, verify that Sun's international version of JRE version 7 or higher is properly installed on the system and its path is in the system's environment variable PATH.

If your web server is on a different machine than your application server, you need to make sure you have JRE installed on your web server to run the PeopleSoft Pure Internet Architecture installation.

Note. If you encounter the error message "No Matching JVM," you need to specify the absolute path to the Java

Runtime Environment (JRE) executable (including the executable file name) using the –javahome command line parameter; for example:

<PS_HOME>/setup/PsMpPIAInstall/setup.sh -tempdir

<temporary_directory> -javahome <jredir>/bin/java

.

The initial PeopleSoft Pure Internet Architecture setup automatically creates the default PeopleSoft site named ps.

In subsequent PeopleSoft Pure Internet Architecture setups, change the site name from ps to a unique value. We recommend using the database name. This is handy for easy identification and ensures that the database web server files are installed in a unique web site.

The URL that you use to invoke the PeopleSoft Pure Internet Architecture must conform to ASN.1 specifications.

That is, it may contain only alphanumeric characters, dots ("."), or dashes ("-"). The URL must not begin or end with a dot or dash, or contain consecutive dots (".."). If the URL includes more than one portion, separated by dots, do not use a number to begin a segment if the other segments contain letters. For example,

"mycompany.second.country.com" is correct, but "mycompany.2nd.country.com" is wrong.

Review the following additional notes before beginning the PeopleSoft Pure Internet Architecture installation:

• If you want to connect between multiple application databases, you need to implement single signon.

• If the PeopleSoft Pure Internet Architecture installation encounters an error, it will indicate which log files to refer to.

See "Installing Web Server Products."

• The machine on which you run the PeopleSoft Pure Internet Architecture install must be running in 256 color

mode. This is not necessary for UNIX or console mode.

The PeopleSoft Pure Internet Architecture installation includes the following products:

PeopleSoft Pure Internet Architecture. This product is the centerpiece of the PeopleSoft architecture that enables users to work on a machine with only a supported browser installed. This option installs the servlets required for deploying PeopleSoft Applications and for the PeopleSoft portal. The portal packs and PeopleSoft

Portal Solutions have their own installation instructions, which are available on My Oracle Support. For an overview of the various types of portals, consult the PeopleTools: Portal Technology product documentation.

PeopleSoft Report Repository. This product works in conjunction with Process Scheduler to allow report distribution over the web.

PeopleSoft Integration Gateway. This product is the entry and exit point for all messages to and from the

Integration Broker. Its Java-based Connector architecture allows asynchronous and synchronous messages to be sent over a variety of standard protocols, many that are delivered at install, or through custom connectors.

Important! For PeopleSoft PeopleTools 8.50 and later, review the product documentation concerning security properties for Integration Gateway. When setting the properties in the integrationGateways.properties

file, the property secureFileKeystorePasswd must be encrypted, and the secureFileKeystorePath must be set.

See PeopleTools: Integration Broker Administration.

PeopleSoft CTI Console. This product works in conjunction with CTI vendor software to enable call center agents to take advantage of browser-based teleset management and automatic population of application pages with relevant data associated with incoming calls, such as customer or case details.

See PeopleTools: MultiChannel Framework.

384

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Environment Management Hub. The Environment Management hub is a web application that is installed with the PeopleSoft Pure Internet Architecture and portal. It is started along with the rest of the web applications when the user boots the web server. You cannot start the Environment Management Hub on a server that is configured to run HTTPS; in other words, if you plan to run Environment Management, your PIA server needs to be configured in HTTP mode.

See PeopleTools: Change Assistant and Update Manager.

See Also

PeopleTools: Security Administration

PeopleTools: System and Server Administration

Using Authentication Domains in the PeopleSoft Pure Internet

Architecture Installation

You have the option to specify an authentication domain when you install the PeopleSoft Pure Internet

Architecture on Oracle WebLogic or IBM WebSphere.

Note. The authentication domain was referred to as the Authentication Token Domain in previous releases, and that term is still seen in the software.

When an authentication domain is specified during the PeopleSoft Pure Internet Architecture installation, that value gets used as the Cookie domain in the web server configuration. The main requirements when setting a cookie domain are:

• The host must have a fully qualified domain name (FQDN). The requirement that you must have a domain name does not imply that you must have a DNS, but you do need some type of naming service such as DNS or some managed ../etc/hosts file that contains a list of the servers with their domain name.

• The cookie domain value being set must begin with a dot (.ps.com is valid, ps.com is NOT valid).

• The cookie domain value being set must contain at least 1 embedded dot (.ps.com is valid, .corp.ps.com is valid, .com is NOT valid).

• The cookie domain value can only be a single domain name. It cannot be a delimiter-separated list of domains.

By default, the browser only sends cookies back to the machine that set the cookie. So if web server crm.yourdomain.com sets a cookie, the browser will only send it back there. You can make the browser send the single signon cookie to all servers at yourdomain.com by typing your domain name in the Authentication Token

Domain list box of web server crm.

Specifying the authentication domain may be necessary in certain cases. For example, if you plan to use the

PeopleSoft portal technology, be sure to read the supporting documentation on configuring the portal environment, to determine whether setting the authentication domain is required for correct operation.

See PeopleTools: Portal Technology.

Specify an authentication domain if you plan to run a REN Server. REN Servers are required for PeopleSoft

MultiChannel Framework, Reporting, and some PeopleSoft CRM applications supported by PeopleSoft

MultiChannel Framework.

See PeopleTools: MultiChannel Framework.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

385

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Chapter 9B

If you use the PeopleSoft Mobile Application Platform (MAP), you must specify the same authentication domain during the PeopleSoft Pure Internet Architecture installation, for MAP, and for Integration Broker and integration hubs.

See PeopleTools: Mobile Application Platform.

See PeopleTools: Integration Broker.

Task 9B-1: Preparing the PeopleSoft Pure Internet Architecture

File System for a PeopleTools-Only Upgrade

When performing the installation of the PeopleSoft Pure Internet Architecture system using the separate upgrade

PS_HOME (which is different than your old release PS_HOME), you may install and configure your PeopleSoft

Pure Internet Architecture system at this point in time of the installation, but do not start your PeopleSoft Pure

Internet Architecture system until directed to do so within the upgrade.

If you are installing into an existing PS_HOME or PIA_HOME after completing a PeopleTools-only upgrade, perform the following instructions to remove any obsolete files.

See "Preparing for Installation," Preparing for the PeopleTools-Only Upgrade.

Stop the web server before performing the PeopleSoft Pure Internet Architecture installation or uninstallation.

Depending on your web server platform, complete the following steps to clean up previous PeopleSoft Pure

Internet Architecture sites:

• Oracle WebLogic

Shut down Oracle WebLogic and follow the uninstallation instructions in the old release PeopleSoft

PeopleTools installation guide for your database platform. Alternatively, delete the contents of one of the following directories:

• For PeopleSoft PeopleTools 8.43.x or earlier: <weblogic_home>\wlserver6.1\config\<domain_name>\*

• For PeopleSoft PeopleTools 8.44.x to 8.49.x: <PS_HOME>\webserv\<domain_name>\*

• For PeopleSoft PeopleTools 8.50.x or later: <PIA_HOME>\webserv\<domain_name>\*

• IBM WebSphere

Shut down IBM WebSphere and follow the uninstallation instructions in the old release PeopleSoft

PeopleTools installation guide for your database platform.

Task 9B-2: Installing the PeopleSoft Pure Internet Architecture on

Oracle WebLogic in Console Mode

This section discusses:

• Prerequisites

• Installing the PeopleSoft Pure Internet Architecture on a New Oracle WebLogic Domain in Console Mode

• Installing the PeopleSoft Pure Internet Architecture on an Existing Oracle WebLogic Domain in Console

Mode

• Uninstalling the PeopleSoft Pure Internet Architecture from Oracle WebLogic

386

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Task 9B-2-1: Prerequisites

This section describes how to install the PeopleSoft Pure Internet Architecture on Oracle WebLogic. Before you install the PeopleSoft Pure Internet Architecture (PIA) on Oracle WebLogic, you must have installed the Oracle

WebLogic software. PeopleSoft PeopleTools 8.55 supports Java 7 enabled 64-bit Oracle WebLogic 12.1.3.0.

See "Installing Web Server Products," Installing Oracle WebLogic Server.

See the information on working with Oracle WebLogic in the PeopleTools: System and Server Administration product documentation.

Task 9B-2-2: Installing the PeopleSoft Pure Internet Architecture on a New

Oracle WebLogic Domain in Console Mode

To install the PeopleSoft Pure Internet Architecture on Oracle WebLogic:

1. Change directory to PS_HOME/setup/PsMpPIAInstall and run one of these commands: setup.sh -tempdir <temporary_directory>

See "Using the PeopleSoft Installer," Running the PeopleSoft Installer, for setup command options.

See "Using the PeopleSoft Installer," Prerequisites.

A welcome message appears.

2. Press ENTER at the Welcome prompt to continue.

Welcome to the InstallShield Wizard for PeopleSoft Internet⇒

 Architecture.

Using the InstallShield Wizard you will install PeopleSoft Internet⇒

 Architecture on your computer.

Version: 8.55

Note: If installing onto an Oracle WebLogic Server, make sure to⇒

 shutdown any running⇒

 webservers to avoid web server configuration.

Press 1 for Next, 3 to Cancel, or 5 to Redisplay [1]:

3. Enter the directory where you want to install the PeopleSoft Pure Internet Architecture, referred to here as

PIA_HOME.

Choose the directory where you wish to deploy the PeopleSoft Pure⇒

 Internet Architecture:

  Please specify a directory name or press Enter

[/home/PT855]: 

4. Enter 1 to select the Oracle WebLogic Server.

Choose the installation type that best suits your needs

  ->1- Oracle WebLogic Server

    2- IBM WebSphere Server

To select an item enter its number, or 0 when you are finished [0]:

5. Enter the top-level directory where Oracle WebLogic is installed.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

387

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Chapter 9B

Select the web server root directory [/opt/oracle]: /data4/WLS_HOME

Detected web server version: WebLogic 12.1.3

Note. You will get an error message if you specify a directory that does not contain Oracle WebLogic, or that contains an incorrect Oracle WebLogic version.

6. Select 1, Create New WebLogic Domain, at the following prompt:

->1- Create New WebLogic Domain

  2- Existing WebLogic Domain

Note. If the PIA installer cannot detect any existing Oracle WebLogic domains, only the option Create New

WebLogic Domain is available. The installation on an existing domain is described in the following section.

See Installing the PeopleSoft Pure Internet Architecture on an Existing Oracle WebLogic Domain in Console

Mode.

7. The installation process automatically generates a valid domain name, which is peoplesoft in the following sample prompt.

If you attempt to enter an invalid domain name, you see a prompt asking you to enter a new domain name or choose an existing domain.

Enter domain name or click Next to select default [peoplesoft]:

8. Enter the administrator login, or accept the default value. Enter and re-enter the password for your Oracle

WebLogic domain.

Press ENTER to continue.

The default login ID is system. The password must be at least 8 alphanumeric characters with at least one number or special character.

Please enter the administrator login and password for WebLogic domain.

Login ID [system]:

Password []:

Re-type Password []:

9. Select the type of domain to create

—single server, multi server, or distributed managed server.

Please select the configuration to install.

  ->1- Single Server Domain

    2- Multi Server Domain

    3- Distributed Managed Server

There are three domain configuration options:

Single Server Domain

This domain configuration contains one server, named PeopleSoft Pure Internet Architecture and the entire PeopleSoft application is deployed to it. This configuration is intended for single user or very small scale, non-production environments. This configuration is very similar to the Oracle WebLogic domain provided in PeopleSoft PeopleTools 8.40 through 8.44.

Multi Server Domain

This domain configuration is contains seven unique server definitions, a Oracle WebLogic cluster, and the

PeopleSoft Application split across multiple servers. This configuration is the intended for a production

388

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

environment.

Distributed Managed Server

This option is an extension of the Multi Server Domain selection and installs the necessary files to boot a managed server. This option requires a Multi Server installation to be performed to some other location, which will contain the configuration for this managed server.

10. Enter the Integration Gateway User and password.

The password must be at least 8 alphanumeric characters.

See PeopleTools: Integration Broker Administration.

Please enter the Integration Gateway User and Password.

   Integration Gateway User [administrator]:

   Password []: 

   Re-type Password []: 

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1] :

11. Enter the AppServer Domain Connection password (optional).

If you configured your Application Server domain to require a Domain Connection password, enter it here.

Otherwise, leave it blank. This password will be propagated to the Integration Gateway.

See the information on setting Application Server domain parameters in the PeopleTools: System and Server

Administration product documentation.

Please enter the AppServer Domain Connection Password.

   Password []:

   Re-type Password []:

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1] :

12. Enter a PeopleSoft web site name; the default is ps.

Warning! The site name can include underscores ( _ ), but an underscore cannot be followed by a numeric character or the string "newwin" (for example, my_site_3 or my_newwin_site).

Please specify a name for the PeopleSoft web site:

Website name [ps]:

13. Specify your application server name, its JSL (Jolt Station Listener) port number, its HTTP and HTTPS port numbers, the Authentication Token Domain (optional).

Enter port numbers and summaries.

AppServer name [APPSRVNAME]: 

JSL Port [9000]: 

HTTP Port [80]:

HTTPS Port [443]:

Authentication Token Domain (optional) []:

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

389

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Chapter 9B

AppServer name

For the AppServer name setting, enter the name of your application server.

See "Configuring the Application Server on UNIX."

See "Configuring the Application Server on Windows."

See Understanding the PeopleSoft Pure Internet Architecture.

JSL Port

For the JSL port setting, enter the JSL port number you specified when setting up your application server.

(The default value is 9000.)

HTTP and HTTPS Port

The values for the HTTP and HTTPS ports should be greater than 1024. Any port number less than 1024 is reserved and only Root has access to it.

Authentication Token Domain

The value you enter for the Authentication Token Domain must match the value you specify when configuring your application server, as described earlier in this book. In addition, certain installation configurations require that you specify an authentication domain.

See Using Authentication Domains in the PeopleSoft Pure Internet Architecture Installation.

If you enter a value for the Authentication Token Domain, the URL to invoke PeopleSoft Pure Internet

Architecture must include the network domain name in the URL. For example, if you do not enter an authentication domain, the URL to invoke PeopleSoft Pure Internet Architecture is http://MachineName/ps/signon.html. If you do enter a value for authentication domain (for example,

.myCompany.com), the URL to invoke PeopleSoft Pure Internet Architecture is http://MachineName.myCompany.com/ps/signon.html. In addition, if the web server for the database is using an http port other than the default port of 80, the URL must include the port number, for example http://MachineName:8080/ps/signon.html if there is no authentication domain, or http://MachineName.myCompany.com:8080/ps/signon.html if there is an authentication domain. The

URL must also comply with the naming rules given earlier in this chapter.

14. Enter the details for the web profile, PROD, or enter another name.

The example below shows the default web profile name, PROD, and default user ID, PTWEBSERVER. The web profile name will be used to configure this web site. You can specify one of the other predelivered web profiles, DEV, TEST, or KIOSK, or enter a different name. If you intend to use a Web Profile User ID other than the default, be sure to review the information on web profile configuration and security in the

PeopleTools: Portal Technology product documentation.

Please enter the Name of the Web Profile used to configure the web⇒

 server. The user id and password will be used to retrieve the web⇒

 profile from the database. (NOTE: Other available preset web profile⇒

 names are "TEST", "DEV", and "KIOSK".)

Web Profile Name [PROD]: 

User ID [PTWEBSERVER]:

Password []:

Re-type Password []:

390

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Note. If the PeopleSoft PeopleTools version of your database is below 8.44, then you will need to add the

PTWEBSERVER User Profile before you upgrade to the current PeopleSoft PeopleTools release. The User

Profile must include the PeopleTools Web Server role, but do not grant any other roles. Enter the password that you set for the User Profile for the User ID password in this step, as shown in this example. The password must be at least 8 alphanumeric characters.

See the PeopleTools: Security Administration product documentation for the steps required to add a User

Profile.

15. Specify the root directory for the Report Repository.

The default directory is <user_home>/PeopleSoft Internet Architecture/psreports, where <user_home> is the home directory for the current user.

You must have write access to the specified directory.

Note. In setting up the Process Scheduler to transfer reports, if you choose the FTP protocol, use the same directory for the Home Directory as you use here for the report repository.

See "Setting Up Process Scheduler," Setting Up Process Scheduler to Transfer Reports and Logs to the Report

Repository.

Select the Report Repository location:

Please specify a directory name or press Enter [/ds1/home/PeopleSoft⇒

 Internet Architecture/psreports]:

16. Verify all of your selections and press Enter to begin the installation.

Setup Type : weblogic

Web server root directory : /data4/WLS1213

Web server version : 12.1

Web server domain : peoplesoft

Internet Architecture app name : PORTAL

Integration Gateway app name : PSIGW

PeopleSoft Business Interlink app name : PSINTERLINKS

Environment Management Hub : PSEMHUB

Portlet Container app name : pspc

Site name : ps

Authentication Token Domain :

Application server name : APPSRVNAME

JSL port : 9000

Report repository directory : /ds1/home/PeopleSoft Internet⇒

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

391

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Chapter 9B

 Architecture/psreports

PIA webserver directory : /home/psftuser/psft/pt/8.55/webserv

You see a progress indicator showing the progress of your installation.

17. When the installation is complete, exit from the console window.

The default installation directory is for the PIA domain <PIA_HOME>/webserv/<domain_name>/, where

<domain> is the web server domain (peoplesoft by default).

Task 9B-2-3: Installing the PeopleSoft Pure Internet Architecture on an

Existing Oracle WebLogic Domain in Console Mode

To install the PeopleSoft Pure Internet Architecture on Oracle WebLogic:

1. Change directory to PS_HOME/setup/PsMpPIAInstall and run one of these commands: setup.sh -tempdir <temporary_directory>

See "Using the PeopleSoft Installer," Running the PeopleSoft Installer, for setup command options.

See "Using the PeopleSoft Installer," Prerequisites.

A welcome message appears.

2. Press ENTER at the Welcome prompt to continue.

Welcome to the InstallShield Wizard for PeopleSoft Internet⇒

 Architecture.

Using the InstallShield Wizard you will install PeopleSoft Internet⇒

 Architecture on your computer.

Version: 8.55

If installing onto an Oracle WebLogic Server, make sure to shutdown any⇒

 running⇒

 webservers to avoid web server configuration.

Press 1 for Next, 3 to Cancel, or 5 to Redisplay [1]:

3. Enter the directory where you want to install the PeopleSoft Pure Internet Architecture, referred to here as

PIA_HOME.

Choose the directory where you wish to deploy the PeopleSoft Pure⇒

 Internet Architecture:

  Please specify a directory name or press Enter

[/home/PT855]: 

4. Enter 1 to select the Oracle WebLogic Server.

Choose the installation type that best suits your needs

  ->1- Oracle WebLogic Server

    2- IBM WebSphere Server

To select an item enter its number, or 0 when you are finished [0]:

5. Enter the top-level directory where Oracle WebLogic is installed.

Select the web server root directory [/opt/oracle]: /data4/WLS_HOME

392

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Detected web server version: WebLogic 12.1.3

Note. You will get an error message if you specify a directory that does not contain Oracle WebLogic, or that contains an incorrect Oracle WebLogic version.

6. Select 2, Existing WebLogic Domain, at the following prompt:

Note. You only see the option Existing WebLogic Domain if there is already a domain in PIA_HOME.

  1- Create New WebLogic Domain

 ->2- Existing WebLogic Domain

7. Select the domain name from the list:

Select application name from list:

->1- ptwls

  2- ptwls2

8. Select one of these options for operations to run at the following prompt:

Select application name from list:

  ->1- Install additional PeopleSoft site

    2- Redeploy PeopleSoft Internet Architecture

    3- Re-create WebLogic domain and redeploy PeopleSoft Internet⇒

 Architecture

    4- Deploy additional PeopleSoft application extensions

To select an item enter its number, or 0 when you are finished [0] : 1

Install additional PeopleSoft site

This option is relevant only to the PeopleSoft PORTAL web application, and does not modify or revert any other configuration settings. Select this option to install only the necessary files for defining an additional PeopleSoft site onto an existing Oracle WebLogic configuration. The new site will be accessed using its name in the URL. A site named "CRM" would be accessed using a URL similar to http://<mywebserver_machine>/CRM. To reset or re-create an existing PeopleSoft site, simply enter that site's name as the site to create. On your web server, a PeopleSoft site is comprised of the following directories within the PORTAL web application:

<WEBLOGIC_DOMAIN>/applications/peoplesoft/PORTAL/<site>/*

<WEBLOGIC_DOMAIN>/applications/peoplesoft/PORTAL/WEB-INF/psftdocs/<site>/*

Redeploy PeopleSoft Internet Architecture

This option affects all of the PeopleSoft Pure Internet Architecture web applications installed to the local

Oracle WebLogic domain. Select this option to redeploy all of the web components of the PeopleSoft Pure

Internet Architecture. The redeployment process updates all of the web components of the PeopleSoft Pure

Internet Architecture, without modifying the configuration files or scripts that belong to the Oracle

WebLogic server domain.

Re-create WebLogic domain and redeploy PeopleSoft Internet Architecture

This option affects Oracle WebLogic Server domain configuration and all of the PeopleSoft Pure Internet

Architecture web applications installed to the local Oracle WebLogic domain. Select this option to completely remove an existing Oracle WebLogic domain and deploy the PeopleSoft Pure Internet

Architecture components to create the newly specified PeopleSoft site.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

393

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Chapter 9B

Warning! Re-creating an existing domain will delete everything previously installed into that domain.

See PeopleTools: Portal Technology.

Deploy additional PeopleSoft application extensions

This option is solely for use with PeopleSoft applications. PeopleSoft application extensions are provided with certain PeopleSoft applications, and this option allows you to deploy those extensions. Consult the installation documentation for your PeopleSoft application to see if this option is appropriate. PeopleSoft

PeopleTools does not use application extensions.

9. If there are application packages in the archives directory, select whether you want to deploy them. (If you are using an existing domain, you see a prompt for this only if you elected to Deploy Additional PeopleSoft

Extensions.)

10. Enter the administrator login and password that you specified for the existing Oracle WebLogic domain. Press

ENTER to continue.

The default login ID is system. The password must be at least 8 alphanumeric characters with at least one number or special character.

Please enter the administrator login and password for WebLogic domain.

Login ID [system]:

Password []:

11. Select the type of domain to create

—single server, multi server, or distributed managed server.

Note. Depending upon the operation you are carrying out for an existing domain, you may not see this prompt.

Please select the configuration to install.

  ->1- Single Server Domain

    2- Multi Server Domain

    3- Distributed Managed Server

There are three domain configuration options:

Single Server Domain

This domain configuration contains one server, named PeopleSoft Pure Internet Architecture and the entire PeopleSoft application is deployed to it. This configuration is intended for single user or very small scale, non-production environments. This configuration is very similar to the Oracle WebLogic domain provided in PeopleSoft PeopleTools 8.40 through 8.44.

Multi Server Domain

This domain configuration is contains seven unique server definitions, a Oracle WebLogic cluster, and the

PeopleSoft Application split across multiple servers. This configuration is the intended for a production environment.

Distributed Managed Server

This option is an extension of the Multi Server Domain selection and installs the necessary files to boot a managed server. This option requires a Multi Server installation to be performed to some other location, which will contain the configuration for this managed server.

12. Enter the Integration Gateway User and password.

The password must be at least 8 alphanumeric characters.

See PeopleTools: Integration Broker Administration.

394

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Please enter the Integration Gateway User and Password.

   Integration Gateway User [administrator]:

   Password []: 

   Re-type Password []: 

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1] :

13. Enter the AppServer Domain Connection password (optional).

If you configured your Application Server domain to require a Domain Connection password, enter it here.

Otherwise, leave it blank. This password will be propagated to the Integration Gateway.

See the information on setting Application Server domain parameters in the PeopleTools: System and Server

Administration product documentation.

Please enter the AppServer Domain Connection Password.

   Password []:

   Re-type Password []:

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1] :

14. If you selected Deploy additional PeopleSoft application extensions, enter the location where you installed the

PeopleSoft application software, PS_APP_HOME.

Choose the directory where you previously installed PeopleSoft⇒

 Applications, commonly known as "PS_APP_HOME".

Note: If you have installed PeopleSoft Applications outside PeopleTools⇒

 PS_HOME then choose the PeopleSoft Applications home "PS_APP_HOME",⇒

 else leave the default PS_HOME.

Please specify a directory name or press Enter [/home/FSCM92]

15. For the option Deploy additional PeopleSoft application extensions, select the application packages to deploy,

EL PeopleSoft Enterprise Learning Mgmt in this sample prompt:

Please select the application package to deploy:

  ->1- EL PeopleSoft Enterprise Learning Mgmt

    2- FIN-SCM PeopleSoft eProcurement

16. Enter a PeopleSoft web site name; the default is ps.

Warning! The site name can include underscores ( _ ), but an underscore cannot be followed by a numeric character or the string "newwin" (for example, my_site_3 or my_newwin_site).

Please specify a name for the PeopleSoft web site:

Website name [ps]:

17. Specify your application server name, its JSL (Jolt Station Listener) port number, its HTTP and HTTPS port numbers, the Authentication Token Domain (optional).

Note. This prompt may differ depending upon the type of operation you are carrying out for an existing domain.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

395

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Chapter 9B

Enter port numbers and summaries.

AppServer name [APPSRVNAME]: 

JSL Port [9000]: 

HTTP Port [80]:

HTTPS Port [443]:

Authentication Token Domain (optional) []:

AppServer name

For the AppServer name setting, enter the name of your application server.

See "Configuring the Application Server on UNIX."

See "Configuring the Application Server on Windows."

See Understanding the PeopleSoft Pure Internet Architecture.

JSL Port

For the JSL port setting, enter the JSL port number you specified when setting up your application server.

(The default value is 9000.)

HTTP and HTTPS Port

The values for the HTTP and HTTPS ports should be greater than 1024. Any port number less than 1024 is reserved and only Root has access to it.

Authentication Token Domain

The value you enter for the Authentication Token Domain must match the value you specify when configuring your application server, as described earlier in this book. In addition, certain installation configurations require that you specify an authentication domain.

See Using Authentication Domains in the PeopleSoft Pure Internet Architecture Installation.

If you enter a value for the Authentication Token Domain, the URL to invoke PeopleSoft Pure Internet

Architecture must include the network domain name in the URL. For example, if you do not enter an authentication domain, the URL to invoke PeopleSoft Pure Internet Architecture is http://MachineName/ps/signon.html. If you do enter a value for authentication domain (for example,

.myCompany.com), the URL to invoke PeopleSoft Pure Internet Architecture is http://MachineName.myCompany.com/ps/signon.html. In addition, if the web server for the database is using an http port other than the default port of 80, the URL must include the port number, for example http://MachineName:8080/ps/signon.html if there is no authentication domain, or http://MachineName.myCompany.com:8080/ps/signon.html if there is an authentication domain. The

URL must also comply with the naming rules given earlier in this chapter.

18. Enter the details for the web profile, PROD, or enter another name.

The example below shows the default web profile name, PROD, and default user ID, PTWEBSERVER. The web profile name will be used to configure this web site. You can specify one of the other predelivered web profiles, DEV, TEST, or KIOSK, or enter a different name. If you intend to use a Web Profile User ID other than the default, be sure to review the information on web profile configuration and security in the

PeopleTools: Portal Technology product documentation.

Please enter the Name of the Web Profile used to configure the web⇒

 server. The user id and password will be used to retrieve the web⇒

 profile from the database. (NOTE: Other available preset web profile⇒

396

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

 names are "TEST", "DEV", and "KIOSK".)

Web Profile Name [PROD]: 

User ID [PTWEBSERVER]:

Password []:

Re-type Password []:

Note. If the PeopleSoft PeopleTools version of your database is below 8.44, then you will need to add the

PTWEBSERVER User Profile before you upgrade to the current PeopleSoft PeopleTools release. The User

Profile must include the PeopleTools Web Server role, but do not grant any other roles. Enter the password that you set for the User Profile for the User ID password in this step, as shown in this example. The password must be at least 8 alphanumeric characters.

See the PeopleTools: Security Administration product documentation for the steps required to add a User

Profile.

19. Specify the root directory for the Report Repository.

The default directory is <user_home>/PeopleSoft Internet Architecture/psreports, where <user_home> is the home directory for the current user.

You must have write access to the specified directory.

Note. In setting up the Process Scheduler to transfer reports, if you choose the FTP protocol, use the same directory for the Home Directory as you use here for the report repository.

See "Setting Up Process Scheduler," Setting Up the Process Scheduler to Transfer Reports and Logs to Report

Repository.

Select the Report Repository location:

Please specify a directory name or press Enter [/ds1/home/PeopleSoft⇒

 Internet Architecture/psreports]:

20. Verify all of your selections and press Enter to begin the installation.

Setup Type : weblogic

Web server root directory : /data4/WLS1213

Web server version : 12.1

Web server domain : peoplesoft

Internet Architecture app name : PORTAL

Integration Gateway app name : PSIGW

PeopleSoft Business Interlink app name : PSINTERLINKS

Environment Management Hub : PSEMHUB

Portlet Container app name : pspc

Site name : ps

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

397

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Chapter 9B

Authentication Token Domain :

Application server name : APPSRVNAME

JSL port : 9000

Report repository directory : /ds1/home/PeopleSoft Internet⇒

 Architecture/psreports

PIA webserver directory : /home/psftuser/psft/pt/8.55/webserv

You see a progress indicator showing the progress of your installation.

21. When the installation is complete, exit from the console window.

The default installation directory is for the PIA domain <PIA_HOME>/webserv/<domain_name>/, where

<domain> is the web server domain (peoplesoft by default).

Task 9B-2-4: Uninstalling the PeopleSoft Pure Internet Architecture from

Oracle WebLogic

To remove a PIA domain deployed on Oracle WebLogic, delete the <PIA_HOME>/webserv/<domain_name> directory. If there is more than one PIA domain, delete the domain_name directory for every domain you want to remove.

Task 9B-3: Installing the PeopleSoft Pure Internet Architecture on

IBM WebSphere in Console Mode

This section discusses:

• Prerequisites

• Installing the PeopleSoft Pure Internet Architecture on IBM WebSphere Application Server ND

• Uninstalling the PeopleSoft Pure Internet Architecture from IBM WebSphere

Prerequisites

The information in this section applies to the installation of PeopleSoft Pure Internet Architecture (PIA) on an

IBM WebSphere Application Server. PeopleSoft PeopleTools 8.55 requires a 64-bit IBM WebSphere 8.5.5.0 installation. Review these points before you begin the installation:

• Before installing the PeopleSoft Pure Internet Architecture on IBM WebSphere Application Server, you must have installed the IBM WebSphere ND software.

See "Installing Web Server Products," Installing IBM WebSphere Application Server.

• Each IBM WebSphere Application Server runs one PeopleSoft Pure Internet Architecture application. If you need to install more than one PeopleSoft Pure Internet Architecture application on your WebSphere

Application Server, you must run the PIA installation again.

• When installing PIA on IBM WebSphere ND, you must work with a local copy of the PIA installation software; you cannot install remotely. If you are doing the installation on a machine other than the one on which you installed PeopleSoft PeopleTools, copy the PS_HOME/setup/PsMpPIAInstall directory to the local machine.

398

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

• Both IBM WebSphere Application Server Network Deployment and PeopleSoft Pure Internet Architecture must be installed and deployed using the same user id. Following this restriction avoids any security and profile management issues.

See Also

"Installing Web Server Products," Installing IBM WebSphere Application Server

Task 9B-3-1: Installing the PeopleSoft Pure Internet Architecture on IBM

WebSphere Application Server ND

To install the PeopleSoft Pure Internet Architecture on IBM WebSphere ND:

1. Change directory to PS_HOME/setup/PsMpPIAInstall and run this command: setup.sh

A welcome message appears.

See "Using the PeopleSoft Installer," Running the PeopleSoft Installer, for setup command options.

2. Select Enter to continue.

3. Choose the directory where you want to install the PeopleSoft Pure Internet Architecture, referred to in this documentation as PIA_HOME.

4. Enter 2, to select the IBM WebSphere Application Server:

->1- Oracle WebLogic Server

  2- IBM WebSphere Server

5. Enter the directory where you installed IBM WebSphere ND, or press ENTER to accept the default:

Select the WebSphere Application Server directory:

Directory Name: [/opt/IBM/WebSphere/AppServer] 

6. Choose whether to create a new application, or use an existing application:

->1- Create New WebSphere Application

  2- Existing WebSphere Application

7. If you specify 1, Create New WebSphere Application, enter an application name for this web server.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

399

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Chapter 9B

8. Select the type of server you want to install, and press ENTER to continue:

Select the server install type:

 ->1- Single Server Installation

   2- Multi Server Installation

The Single Server Installation option creates one IBM WebSphere Application Server profile to hold all the

PeopleSoft web applications. The installer uses the Application Name you enter for the new profile's name.

The Multi Server Installation option creates a single profile with the name you entered above,

application_name. The application_name profile includes two servers, which deploy discrete functionality and are found on different ports, as specified in the following table:

Server Name

server1

Purpose

PORTAL applications

HTTP or HTTPS Port Number

X psemhub PeopleSoft Environment Management

Framework applications (PSEMHUB)

X+1

See the information on working with IBM WebSphere in the PeopleTools: System and Server Administration product documentation.

9. If you specify 2, Existing WebSphere Application, select a domain name from the list:

Select domain name from list

->1- AppSrv01

  2- ptwas

  3- peoplesoftA

  4- hcdmo

10. After specifying an existing domain, select one of the options below and press ENTER to continue.

The PeopleSoft application "peoplesoftA" already exists.

Select from the following:

 ->1- Install additional PeopleSoft site

   2- Redeploy PeopleSoft Internet Architecture

   3- Deploy additional PeopleSoft application extensions

Note. Make sure the server is up and running before choosing any of these options.

Install additional PeopleSoft site

Select this option to install only the necessary files for defining an additional PeopleSoft site onto the existing IBM WebSphere web server configuration.

Redeploy PeopleSoft Internet Architecture

This selection affects all of the PeopleSoft Pure Internet Architecture web applications installed to the local IBM WebSphere Application Server profile. The redeployment process updates all of the web components of the PeopleSoft Pure Internet Architecture.

Deploy additional PeopleSoft application extensions

This option is solely for use with PeopleSoft product applications. PeopleSoft application extensions are provided with certain PeopleSoft applications, and this option allows you to deploy those extensions.

Consult the installation documentation for your PeopleSoft application to see whether this option is appropriate. PeopleSoft PeopleTools does not use application extensions.

400

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

11. Enter the administrator login and password for the IBM WebSphere Application profile, or accept the default values.

The default login ID is system. The password must be at least 8 alphanumeric characters with at least one number or special character.

Please enter the administrator login ID and password for WebSphere⇒

 profile.

Login ID [system]: 

Password []:

Retype Password []: 

If you selected the option Existing WebSphere Application, enter the same Login ID and password as you entered for the original IBM WebSphere profile creation. If the Login ID and password do not match the original values, you will not be able to continue with the PIA installation.

12. If you select the option Deploy additional PeopleSoft application extension, select the application packages you want to deploy:

->1- EMP PeopleSoft Activity Based Mgmt

13. Enter the Integration Gateway User and Password.

The password must be at least 8 alphanumeric characters .

Please enter the Integration Gateway User and Password.

   Integration Gateway User [administrator]:

   Password []: 

   Re-type Password []: 

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1] :

14. Enter the AppServer Domain Connection Password (optional).

If you configured your Application Server domain to require a Domain Connection password, enter it here.

Otherwise, leave it blank. This password will be propagated to the Integration Gateway.

See "Configuring the Application Server on UNIX," Creating, Configuring, and Starting an Initial Application

Server Domain.

See the information on setting Application Server domain parameters in the PeopleTools: System and Server

Administration product documentation.

Please enter the AppServer Domain Connection Password.

   Password []:

   Re-type Password []:

Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay [1] :

15. Enter a web site name; the default is ps.

Warning! The site name can include underscores ( _ ), but an underscore cannot be followed by a numeric character or the string "newwin" (for example, my_site_3 or my_newwin_site).

16. Specify your application server name, its JSL (Jolt Station Listener) port number, its HTTP and HTTPS port numbers, the authentication token domain (optional).

Enter port numbers and summaries.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

401

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Chapter 9B

AppServer name:

    [<App Server Machine Name>]

JSL Port:

    [9000]

HTTP Port:

    [80]

HTTPS Port:

    [443]

Authentication Token Domain:(optional) []

• For the AppServer name setting, enter the name of your application server. For the JSL port setting, enter the JSL port number you specified when setting up your application server. (The default value is 9000.)

See "Configuring the Application Server on UNIX."

• The HTTP/HTTPS port numbers are reset to those that you just specified when you restart your IBM

WebSphere server.

• The value you enter for the Authentication Token Domain must match the value you specify when configuring your application server, as described earlier in this book. In addition, certain installation configurations require that you specify an authentication domain. See Using Authentication Domains in the PeopleSoft Pure Internet Architecture Installation.

• If you enter a value for the Authentication Token Domain, the URL to invoke PeopleSoft Pure Internet

Architecture must include the network domain name in the URL. For example, if you do not enter an authentication domain, the URL to invoke PeopleSoft Pure Internet Architecture is http://MachineName/ps/signon.html. If you do enter a value for the authentication domain (for example,

.myCompany.com), the URL to invoke PeopleSoft Pure Internet Architecture is http://MachineName.myCompany.com/ps/signon.html. In addition, if the web server for the database is using an HTTP port other than the default port of 9080, the URL must include the port number, for example http://MachineName:8080/ps/signon.html if there is no authentication domain, or http://MachineName.myCompany.com:8080/ps/signon.html if there is an authentication domain. The

URL must also comply with the naming rules given earlier in this chapter.

See Understanding PeopleSoft Pure Internet Architecture.

17. Enter the details for the web profile, PROD, or enter another name.

The sample prompt shows the default web profile name, PROD, and default User ID, PTWEBSERVER. The web profile name will be used to configure this web site. You can specify one of the other predelivered web profiles, DEV, TEST, or KIOSK, or enter a different name. If you intend to use a Web Profile User ID other than the default, be sure to review the information on web profile configuration and security in the

PeopleTools: Portal Technology product documentation.

Please enter the Name of the Web Profile used to configure the web⇒

 server. The user id and password will be used to retrieve the web⇒

 profile from the database. (NOTE: Other available preset web profile⇒

 names are "TEST", "DEV", and "KIOSK".)

   Web Profile Name [PROD]:

402

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

   User ID : PTWEBSERVER

   Password []: 

   Re-type Password []

Note. If the PeopleSoft PeopleTools version of your database is below 8.44, then you will need to add the

PTWEBSERVER User Profile before you upgrade to the current PeopleSoft PeopleTools release. The User

Profile must include the PeopleTools Web Server role, but do not grant any other roles. Enter the password that you set for the User Profile for the User ID password in this step. The password must be at least 8 alphanumeric characters. See the PeopleTools: Security Administration product documentation for the steps required to add a User Profile.

18. Specify the root directory for the Report Repository.

You can install to any location, but the directory must have write access. The default directory is user_home/

PeopleSoft Internet Architecture/psreports, where user_home is the home directory for the current user.

Note. In setting up the Process Scheduler to transfer reports, if you choose the FTP protocol, use the same directory for the Home Directory as you use here for the report repository.

See "Setting Up Process Scheduler on UNIX," Setting Up Process Scheduler to Transfer Reports and Logs to the Report Repository.

19. Verify your selections and press Enter to start the installation. You see an indicator showing the progress of your installation.

20. When the installation is complete, exit from the console window.

The default installation directory for a specific PIA profile is <PIA_HOME>/webserv/<profile_name>.

Task 9B-3-2: Uninstalling the PeopleSoft Pure Internet Architecture from

IBM WebSphere

You cannot uninstall PeopleSoft Pure Internet Architecture simply by deleting the directory <PIA_HOME>/ webserv/<profile_name>, without uninstalling it from IBM WebSphere Administration Console. If you do so, the

IBM WebSphere registry becomes corrupt, and subsequent attempts to install PeopleSoft Pure Internet

Architecture will fail. Instead, if necessary, you must uninstall PeopleSoft Pure Internet Architecture on IBM

WebSphere ND as described here:

To uninstall PeopleSoft Pure Internet Architecture on IBM WebSphere:

1. Open the IBM WebSphere Administration Console by entering the following URL in a browser: http://<machine-name>:<administrative_console_port>/ibm/console

To find the value for <administrative_console_port>, refer to <PIA_HOME>\webserv\<profile_name>\ logs\AboutThisProfile.txt.

2. Log in as any user.

3. Choose Applications, Application Types, Websphere enterprise applications.

4. Select the check boxes for the PeopleSoft Pure Internet Architecture applications you want to uninstall, and click Stop.

5. Select the check boxes for the PeopleSoft Pure Internet Architecture applications you want to uninstall, and click Uninstall.

6. Save your configuration.

7. Log out of the IBM WebSphere Administration Console.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

403

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Chapter 9B

8. Stop IBM WebSphere server using one of the following commands:

On Microsoft Windows:

<PIA_HOME>\webserv\<profile_name>\bin\stopServer.bat server1

On UNIX or Linux:

<PIA_HOME>/webserv/<profile_name>/bin/stopServer.sh server1

9. In addition to uninstalling the application, you need to remove the IBM WebSphere Application Server profile

(that was created during PIA install) to complete the PIA uninstallation.

To uninstall profile run the following steps: a. Go to <PIA_HOME>/webserv/<profile_name>/bin b. Run one of the following commands, where profile_name indicates the application name that you have selected during the PIA install.

On Microsoft Windows: manageprofiles.bat -delete -profileName profile_name

On UNIX or Linux: manageprofiles.sh -delete -profileName profile_name c. Delete the directory <PIA_HOME>/webserv/<profile_name>

Task 9B-4: Installing the PeopleSoft Pure Internet Architecture in

Silent Mode

This section discusses:

• Understanding the Silent Installation and the Response File

• Editing the Response File

• Running the Silent Mode Installation

Understanding the Silent Installation and the Response File

You can carry out a silent installation of the PeopleSoft Pure Internet Architecture by providing all the required settings in a response file. With silent installation there is no user interaction. Silent mode installation of

PeopleSoft Pure Internet Architecture is supported for both Microsoft Windows and UNIX operating systems platforms, and for both Oracle WebLogic and IBM WebSphere web servers.

Task 9B-4-1: Editing the Response File

You need a response file to start the installer in silent mode. The PeopleSoft Pure Internet Architecture installer comes with a response file template (resp_file.txt) that can be found under PS_HOME\ setup\PsMpPIAInstall\scripts. Modify the values in the response file according to your installation requirements.

For information on the parameters, see the previous sections that discuss the installation in GUI and console mode.

For information on the optional PSSERVER parameter, see the information on configuring Jolt failover and load balancing in the PeopleTools: System and Server Administration production documentation.

404

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

The response file should contain all the input parameters that are needed for deploying PeopleSoft Pure Internet

Architecture, such as PS_CFG_HOME, DOMAIN_NAME, SERVER_TYPE, and so on. For example:

• Specify

SERVER_TYPE=weblogic

to deploy on Oracle WebLogic.

• Specify

SERVER_TYPE=websphere

to deploy on IBM WebSphere.

Note. When specifying paths on Microsoft Windows operating systems, use forward slashes ( / ), as shown in the examples in the response file.

Sample Response file template:

#Following inputs are required in response file for silent installation

# Location of PIA_HOME directory.  For windows path should have front⇒

 slash '/' instead of back slash '\'

# Set the below variable to the location where you want to install PIA. 

# PLEASE NOTE this variable could be ANY DIRECTORY on your machine. It⇒

 includes but is definitely not limited to PeopleTools Home.

PS_CFG_HOME=C:/PT8.50

# Name of the PIA domain

DOMAIN_NAME=peoplesoft

# Web server type. Possible values are "weblogic", "websphere"

SERVER_TYPE=weblogic

# WebLogic home, the location where Oracle WebLogic is installed (for Web⇒

Logic deployment only)

BEA_HOME=c:/bea

# WebSphere Home, the location where IBM WebSphere is installed (for Web⇒

Sphere deployment only)

WS_HOME=C:/IBM/WebSphere/AppServer

# admin console user id/password for securing WebLogic/WebSphere admin⇒

 console credential

USER_ID=system

USER_PWD=

USER_PWD_RETYPE=

# Install action to specify the core task that installer should perform.

# For creating new PIA domain - CREATE_NEW_DOMAIN.

# For redeploying PIA - REDEPLOY_PSAPP.

# For recreating PIA domain - REBUILD_DOMAIN.

# For installing additional PSFT site - ADD_SITE

# For installing Extensions - ADD_PSAPP_EXT

INSTALL_ACTION=CREATE_NEW_DOMAIN

# Domain type to specify whether to create new domain or modify existing⇒

 domain. Possible values are "NEW_DOMAIN", "EXISTING_DOMAIN".

DOMAIN_TYPE=NEW_DOMAIN

# App home is required only when you are installaing extensions from a⇒

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

405

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Chapter 9B

 decoupled Apps home, please leave it commented otherwise.

# Silent installer can detect the deployable application extensions from⇒

 the PS_APP_HOME

# PS_APP_HOME=D:/CR9.2

# Install type to specify whether the installation is a single server or⇒

 multi server deployment. Possible values are "SINGLE_SERVER_⇒

INSTALLATION", "MULTI_SERVER_INSTALLATION"

INSTALL_TYPE=SINGLE_SERVER_INSTALLATION

# WebSite Name

WEBSITE_NAME=ps

# To enable jolt failover and load balancing, provide a list of⇒

 application server domains in the format of;  PSSERVER=AppSrvr:JSLport,...

# For example:  PSSERVER=SERVER1:9000,SERVER2:9010,SERVER3:9020

# PSSERVER is optional, but if set will have precedence over APPSERVER_⇒

NAME & JSL_PORT.

PSSERVER=

# AppServer Name

APPSERVER_NAME=

# Appserver JSL Port

JSL_PORT=

# HTTP Port

HTTP_PORT=80

# HTTPS Port

HTTPS_PORT=443

# Authentication Domain (optional)

AUTH_DOMAIN=

# Web Profile Name Possible Values are "DEV","TEST","PROD","KIOSK"

WEB_PROF_NAME=PROD

# Web Profile password for User "PTWEBSERVER"

WEB_PROF_PWD=

WEB_PROF_PWD_RETYPE=

# Integration Gateway user profile.

IGW_USERID=administrator

IGW_PWD=

IGW_PWD_RETYPE=

# AppServer connection user profile

APPSRVR_CONN_PWD=

APPSRVR_CONN_PWD_RETYPE=

# Directory path for reports

406

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

REPORTS_DIR=

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Task 9B-4-2: Running the Silent Mode Installation

Use the response file that you modified for your configuration. Substitute the location where you saved the response file for <path_to_response_file> in the following procedures:

To install the PeopleSoft Pure Internet Architecture in silent mode on Microsoft Windows:

1. In a command prompt, go to PS_HOME\setup\PsMpPIAInstall.

2. Run the following command, using forward slashes (/) to specify the path: setup.bat -i silent -DRES_FILE_PATH=<path_to_response_file>

For example: setup.bat -i silent -DRES_FILE_PATH=D:/PT8.55

To install the PeopleSoft Pure Internet Architecture in silent mode on UNIX or Linux:

1. Go to PS_HOME/setup/PsMpPIAInstall.

2. Run the following command, using forward slashes (/) to specify the path: setup.sh -i silent -DRES_FILE_PATH=<path_to_response_file>

For example: setup.bat -i silent -DRES_FILE_PATH=/home/PT855

Task 9B-5: Testing and Administering the PeopleSoft Pure

Internet Architecture Installation

This section discusses:

• Verifying the PeopleSoft Pure Internet Architecture Installation

• Starting and Stopping Oracle WebLogic

• Starting and Stopping IBM WebSphere Application Servers

• Using PSADMIN to Start and Stop Web Servers

• Accessing the PeopleSoft Signon

Verifying the PeopleSoft Pure Internet Architecture Installation

After installing the PeopleSoft Pure Internet Architecture, you should make sure that your configuration is functional. You can test this by signing on to PeopleSoft, navigating within the menu structure, and accessing pages. (Make sure the application server is configured and booted.) This section includes procedures to start and stop the Oracle WebLogic or IBM WebSphere web servers whenever necessary.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

407

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Chapter 9B

Task 9B-5-1: Starting and Stopping Oracle WebLogic

If you are using the Oracle WebLogic web server, you need to sign on to Oracle WebLogic before using these commands. If you are using IBM WebSphere instead, go on to the next section. Use the following commands in the Oracle WebLogic domain directory.

Note. Starting from Oracle WebLogic 9.2 and later releases, all the Life-cycle management scripts and other batch scripts for the PIA server on Oracle WebLogic are located in <PIA_HOME>\webserv\<domain_name>\bin folder.

• To start Oracle WebLogic Server as a foreground process on a single server, use the following commands: startPIA.cmd (on Windows) startPIA.sh (on UNIX)

• To start Oracle WebLogic Server as a foreground process on multiple-servers or distributed servers, use the following commands:

1. Execute: startWebLogicAdmin.cmd (on Windows) startWebLogicAdmin.sh (on UNIX)

2. Then execute: startManagedWebLogic.cmd ManagedServerName (on Windows) startManagedWebLogic.sh ManagedServerName (on UNIX)

• To stop the server, use the following commands:

• Single Server: stopPIA.cmd (on Windows) stopPIA.sh (on UNIX)

• Multiple Servers or Distributed Servers: stopWebLogic.cmd ManagedServerName (on Windows) stopWebLogic.sh ManagedServerName (on UNIX)

For more information on working with Oracle WebLogic multiple servers or distributed servers, see the

PeopleTools: System and Server Administration product documentation.

Note. For more information on working with Oracle WebLogic multiple or distributed servers, search My Oracle

Support.

Task 9B-5-2: Starting and Stopping IBM WebSphere Application Servers

This section discusses:

• Starting and Stopping IBM WebSphere Application Servers on Windows

• Starting and Stopping IBM WebSphere Application Servers on UNIX or Linux

• Verifying the IBM WebSphere Installation

408

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Starting and Stopping IBM WebSphere Application Servers on Windows

To start and stop the WebSphere Application Server Network Deployment 8.5.5.0 (WebSphere ND), use the

WebSphere First Steps utility:

1. On Microsoft Windows 7, select Start, Programs, IBM WebSphere, IBM WebSphere Application Server

V8.5, Profiles, profile_name, First steps.

On Microsoft Windows 8 or 2012 R2, access the Apps screen and locate the First steps utility in the IBM

WebSphere category.

The following example shows the First steps window for the profile peoplesoftWAS:

WebSphere Application Server First Steps window

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

409

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Chapter 9B

2. Select the link Start the server.

If the server starts properly, a verification window appears with several messages about the initialization process, as in this example:

First steps output - Installation verification window

3. To verify whether the server was installed and can start properly, click the link Installation Verification on the

First Step window.

Starting and Stopping IBM WebSphere Application Servers on UNIX or Linux

To start WebSphere ND on UNIX or Linux, use the following command:

<PIA_HOME>/webserv/<profile_name>/bin/startServer.sh <server_name>

For example:

/home/pt855/webserver/peoplesoft/bin/startServer.sh server1

To stop WebSphere ND, use the following command:

<PIA_HOME>/webserv/<profile_name>/bin/stopServer.sh <server_name>

Verifying the IBM WebSphere Installation

Use this method to verify the WebSphere ND and PIA installation for both Microsoft Windows and UNIX.

410

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

To verify the WebSphere ND and PIA installation, copy the following URL into a browser address bar, substituting your machine name and the http port number: http://<machine_name>:<http_port>/ivt/ivtservlet

You should see the text "IVT Servlet" in the browser, as in this example:

IVT Servlet window

You should also sign into the PeopleSoft application, as described in a later section, to verify the installation.

See Accessing the PeopleSoft Signon.

Task 9B-5-3: Using PSADMIN to Start and Stop Web Servers

In addition to the methods given in the previous sections for starting and stopping Oracle WebLogic and IBM

WebSphere web servers, in PeopleSoft PeopleTools 8.52 and later releases you can use PSADMIN to administer a web server domain.

See PeopleTools: System and Server Administration.

To start and stop web servers:

1. Run the psadmin

command.

2. Specify 4 for Web (PIA) Server.

--------------------------------

PeopleSoft Server Administration

--------------------------------

  PS_HOME:      /home/pt855

  PS_CFG_HOME:  /home/psft_AppServ

  1) Application Server

  2) Process Scheduler

  3) Search Server

  4) Web (PIA) Server

  5) Switch Config Home

  6) Replicate Config Home

  q) Quit

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

411

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Chapter 9B

Command to execute (1-6, q): 4

The location of Config Home is the current working directory. The PSADMIN utility determines the Config

Home directory by checking for the PS_CFG_HOME environment variable. If that is not set, it checks for the presence of domains in the default PS_CFG_HOME location. If none exists, it uses the PS_HOME location from which it was launched.

See "Preparing for Installation," Defining Installation Locations.

3. Select 1 for Administer a domain.

-----------------------------

PeopleSoft PIA Administration

-----------------------------

  PIA Home:   /home/psft_WebServ

  1) Administer a domain

  2) Create a domain

  3) Delete a domain

  q) Quit

Command to execute: 1

The PSADMIN utility determines the PIA Home location displayed here by first checking for a PIA_HOME environment variable. If none is set, it checks for the PS_CFG_HOME environment variable. If neither is set, it uses the default PS_CFG_HOME directory.

4. Select the domain you want to administer by entering the appropriate number.

------------------------------------------------------

PeopleSoft PIA Domain Administration - Choose a Domain

------------------------------------------------------

1) psftTST  

2) peoplesoft q) Quit

Command to execute: 2

5. To start a web server domain, enter 1, Boot this domain.

------------------------------------

PeopleSoft PIA Domain Administration

------------------------------------

  PIA Home:      /home/psft_websrv

  PIA Domain:    peoplesoft

  Domain Status: stopped

  1) Boot this domain

  2) Shutdown this domain

  3) Get the status of this domain

  4) Configure this domain

  5) Edit configuration files

  6) View log files

412

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

  7) Administer a site

  8) Delete a site

 

  q) Quit

Command to execute: 1

The boot command invokes the startPIA.sh script, and you see the progress and a status message on the console window.

Starting the domain..................

...

Verifying domain status..

The domain has started.

6. To stop a web server domain, select 2, Shutdown this domain.

The shutdown command invokes the stopPIA.sh script, and you see the progress and a status message on the console window.

Stopping the domain.....

.....

Verifying domain status..........

The domain has stopped.

7. Select 1 to install a service, or 2 to remove it.

This command invokes the installNTservice script, and creates a service named WebLogicDomain-

WebLogicServer.

---------------------

Windows Service Setup

---------------------

  PIA Home:      C:\psft_websrv

  PIA Domain:    peoplesoft

  Domain status: started

  1) Install Service

  2) Uninstall Service

  q) Quit

Command to execute:

Task 9B-5-4: Accessing the PeopleSoft Signon

To access the PeopleSoft signon:

1. Open your web browser.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

413

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Chapter 9B

2. Enter the name of the site you want to access

—for example (the default value for <site_name> is ps): http://<machine_name>:<http_port>/<site_name>/signon.html

Note. PeopleSoft Pure Internet Architecture installed on IBM WebSphere server listens at the HTTP/HTTPS ports specified during the PeopleSoft Pure Internet Architecture install. Invoke PeopleSoft Pure Internet

Architecture through a browser by using the specified HTTP or HTTPS ports—that is, http://

<WebSphere_machine_name>:<server_port>/<site_name>/signon.html (if AuthTokenDomain is not specified ) or http://<WebSphere_machine_name.mycompany.com>:<server_port>/<site_name>/ signon.html (if you specified .mycompany.com as the AuthTokenDomain). You can find the HTTP and

HTTPS ports in the file <PIA_HOME>/webserv/<domain_name>/logs/AboutThisProfile.txt.

This will take you to the sign-in window corresponding to your browser's language preference, as shown in this example:

414

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Oracle PeopleSoft Enterprise Sign in window

Note. If you do not see the signon screen, check that you supplied all the correct variables and that your application server and the database server are running.

3. Sign in to the PeopleSoft system by entering a valid user ID and password.

The user ID and password are case sensitive.

Note. The user ID and password were set during the database configuration and also used to boot the application server.

The PeopleSoft PeopleTools and PeopleSoft applications include various default user IDs. For information on using the user IDs delivered with your PeopleSoft application demo database, see the application-specific

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

415

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Chapter 9B installation instructions. For information on using and securing PeopleSoft PeopleTools default user IDs, see the information on administering user profiles in the PeopleTools: Security Administration product documentation.

Task 9B-6: Completing Post-Installation Steps

This section discusses:

• Using Fluid User Interface

• Updating the Installation Table

• Setting Options for Multilingual Databases

• Updating PeopleTools Options

• Updating Database Information

Task 9B-6-1: Using Fluid User Interface

When you sign in to your PeopleSoft application, you may see the PeopleSoft Fluid User Interface by default. To access the menu items, as seen in the classic user interface, from the PeopleSoft Fluid User Interface:

416

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

1. On the PeopleSoft Fluid User Interface, shown in this example, select (press) the NavBar button at the top right (diamond inside a circle).

PeopleSoft Fluid User Interface home page

The Navigation bar (NavBar) side page appears.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

417

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

2. Select (press) Navigator.

Chapter 9B

NavBar side page

The menu structure appears.

418

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

3. Navigate to the desired item, such as Set Up HCM or PeopleTools.

Navigator side page with PeopleSoft menu items

See Also

PeopleTools: Applications User's Guide, "Working With Fluid Homepages"

PeopleTools: Fluid User Interface Developer's Guide

Task 9B-6-2: Updating the Installation Table

After you complete the installation process, creating the database, installing the Application Server, and installing the PeopleSoft Pure Internet Architecture, you must complete this additional step. The license codes from the

Oracle license code site mentioned earlier install all products available in the installation package. This postinstallation step ensures that only the products for which you are licensed are active in the installation. The location of the installation table in the PeopleSoft system varies depending upon the PeopleSoft application that you installed.

To update the installation table:

1. Sign on to the PeopleSoft system.

2. Select Set Up Application_name (where Application_name is the PeopleSoft application you installed),

Install, Installation Table.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

419

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Select the Products tab.

3. Clear the check boxes for the products for which you have not obtained a license.

See Also

"Using the PeopleSoft Installer," Obtaining License Codes

Accessing the PeopleSoft Signon

Task 9B-6-3: Setting Options for Multilingual Databases

Chapter 9B

Setting the Data Field Length Checking Option

The value to specify data field length checking must be set correctly in order for PeopleSoft applications to perform correctly in a browser. Use one of these methods to set the data field length checking option:

• Select PeopleTools, Utilities, Administration, PeopleTools Options, and select the Data Field Length

Checking option from the drop-down list.

• Alternatively, use the SQL tool for your database platform to modify the DBLENGTHTYPE parameter in the

PSOPTIONS table.

See PeopleTools: Global Technology, "Setting Data Field Length Checking."

See PeopleTools: Global Technology, "Selecting Character Sets."

Use the guidelines in this table to select the correct option for your environment:

Environment

Unicode-encoded database or a non-

Unicode SBCS database

PeopleTools Option Page Selection

Others

PSOPTIONS.DBLENGTHTYPE Value

N

Japanese database on DB2 LUW DB2 MBCS

Non-Unicode Japanese database MBCS

Note. If your installation uses the Shift-

JIS character set for Japanese, you must use this option.

Note. The MBCS option is not supported for DB2 z/OS.

D

M

Setting the Unicode Enabled Option

If you are running a Unicode database, verify that the UNICODE_ENABLED parameter in the PSSTATUS table is set correctly. For example:

• For non-Unicode databases, including those using the Shift-JIS character set for Japanese, set

UNICODE_ENABLED=0.

• For Unicode databases, set UNICODE_ENABLED=1.

See the information on converting to Unicode in the PeopleTools: Global Technology product documentation.

420

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 9B

Setting Up the PeopleSoft Pure Internet Architecture in Console Mode

Task 9B-6-4: Updating PeopleTools Options

You can set the following options on the PeopleTools Options page:

• Multi-Currency — Select this check box if you plan to use currency conversion.

See PeopleTools: Global Technology, "Using System-Wide Multicurrency Settings."

• Base Time Zone — Enter a value for the base time zone for your PeopleTools database.

See PeopleTools: Global Technology, "Setting the Base Time Zone."

• Sort Order Option — If you specified a non-binary sort order for your database, choose the Sort Order Option that most closely approximates your database sort order.

See PeopleTools: Global Technology, "Setting the Sort Order."

Task 9B-6-5: Updating Database Information

The database information updated in this procedure is used by the PeopleSoft software update tools to identify your PeopleSoft database when searching for updates. These steps should be followed for all additional databases that you create to enable the accurate identification of your databases.

1. Sign on to your PeopleSoft database.

2. Navigate to PeopleTools, Utilities, Administration, PeopleTools Options.

3. Specify long and short names for your environment. For example:

• Environment Long Name — Customer HR Demo Database

• Environment Short Name — HR Demo DB

4. Select a system type from the drop-down list. For example, Demo Database.

5. Save your changes.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

421

Chapter 10A

Setting Up Process Scheduler on Windows

This chapter discusses:

• Prerequisites

• Preparing the Process Scheduler File System for a PeopleTools-Only Upgrade

• Setting Up Process Scheduler Security

• Setting Up Process Scheduler to Transfer Reports and Logs to the Report Repository

• Setting Environment Variables

• Setting Up Process Scheduler Server Agent

• Starting Process Scheduler as a Windows Service (Optional)

• Configuring the Process Scheduler for Microsoft Word (Optional)

• Configuring Setup Manager

• Installing Products for PS/nVision

Prerequisites

Before setting up your Process Scheduler, you must:

• Install Tuxedo (except for z/Linux).

See "Installing Additional Components."

• Install database connectivity to be able to communicate with your database server (Process Scheduler requires a direct connection to the database).

See "Preparing for Installation."

• Set up the web server with the PeopleSoft Pure Internet Architecture, as described in the previous chapter.

This is required to set up the Process Scheduler to transfer reports or log files to the Report Repository.

• Set up your COBOL batch environment if you need to run COBOL processes through Process Scheduler. If the PeopleSoft modules purchased do not contain any COBOL modules, the COBOL run time libraries are not required. Also, COBOL is not required for applications that contain no COBOL programs. Consult My Oracle

Support for the details on whether your application requires COBOL.

See "Preparing for Installation," Planning Your Initial Configuration.

• Install the Microsoft Office products Microsoft Word and Microsoft Excel.

• Have both your application server and the PeopleSoft Pure Internet Architecture started. In this chapter, you must modify security options of the designated PeopleSoft user ID that will be used to boot up Process

Scheduler. This requires that the user ID's profile be modified through the User Security component. Please refer to earlier chapters for the details on starting the application server and the PeopleSoft Pure Internet

Architecture.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

423

Setting Up Process Scheduler on Windows

Chapter 10A

In PeopleSoft PeopleTools 8.50 and later, the configuration and log files for Process Scheduler server domains reside in PS_CFG_HOME. If you do not set a PS_CFG_HOME environment variable before beginning the application server configuration, the system installs it in a default location based on the current user's settings, as follows:

%USERPROFILE%\psft\pt\<peopletools_version>

See "Preparing for Installation," Defining Installation Locations.

See the product documentation PeopleTools: System and Server Administration for more information on the

PS_CFG_HOME environment variable and working with server domain configuration.

See Also

PeopleTools: Process Scheduler

My Oracle Support, Certifications

Task 10A-1: Preparing the Process Scheduler File System for a

PeopleTools-Only Upgrade

When performing the installation of the separate upgrade PS_HOME or PS_CFG_HOME (which is different than your old release PS_HOME), you may configure your Process Scheduler at this point in time of the installation, but do not boot your Process Scheduler until directed to do so within the upgrade.

If you are installing into an existing PS_HOME or PS_CFG_HOME after completing a PeopleTools-only upgrade, review your old PS_HOME or PS_CFG_HOME for configuration files that you may want to reuse for the new PeopleSoft PeopleTools release. While you may configure your Process Scheduler at this point in time of the installation, do not boot your Process Scheduler until directed to do so within the upgrade.

See "Preparing for Installation," Preparing for the PeopleTools-Only Upgrade.

Task 10A-2: Setting Up Process Scheduler Security

This section discusses:

• Understanding Process Scheduler Security

• Changing User Account to Start ORACLE ProcMGR V12.1.3.0.0_VS2012

• Granting Process Scheduler Administrative Rights

Understanding Process Scheduler Security

This task—in which you set up the PeopleSoft User ID that will be used to boot Process Scheduler server so it has administrative rights to both Process Scheduler and Report Manager—guarantees that security is set up properly both in Microsoft Windows and within your PeopleSoft database.

You must carry out this task to start Process Scheduler successfully.

424

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Setting Up Process Scheduler on Windows

In the next section you set up ORACLE ProcMGR V12.1.3.0.0_VS2012 with a network user ID. When you install Oracle Tuxedo, the ORACLE ProcMGR V12.1.3.0.0_VS2012 service is set up by default to be started by local system account—a user account that does not have access to the Windows network. If the Process Scheduler server or processes initiated through Process Scheduler will be using a network printer, accessing files from a network drive, or using Microsoft Windows utilities such as XCOPY that may access UNC paths, you need to change the user account used to start ORACLE ProcMGR V12.1.3.0.0_VS2012 with a network user account.

Task 10A-2-1: Changing User Account to Start ORACLE ProcMGR

V12.1.3.0.0_VS2012

To change User Account to start ORACLE ProcMGR V12.1.3.0.0_VS2012:

1. Launch the Services dialog box; for example, on Microsoft Windows 7, select Start, All Programs,

Administrative Tools, Services.

On Microsoft Windows 8 or 2012 R2, click the Start button, and then click Administrative Tools, Services.

In the Services dialog box, find the service labeled ORACLE ProcMGR V12.1.3.0.0_VS2012. This service is installed automatically when you install Tuxedo, and is highlighted in this example.

Microsoft Windows Services dialog box with ORACLE ProcMGR service highlighted

2. If the Stop button is enabled, click it to stop the current ORACLE ProcMGR V12.1.3.0.0_VS2012 process. a. Click Yes when a message informs you of the status change.

b. Double-click ORACLE ProcMGR V12.1.3.0.0_VS2012.

The Properties dialog box appears.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

425

Setting Up Process Scheduler on Windows

3. Select the option This account on the Log On tab.

Enter an account name and password. In this example, the account name is CORP\USER1.

Chapter 10A

426

ORACLE ProcMGR V12.1.3.0.0_VS2012 Properties dialog box: Log On tab

Note. When you configure your Oracle Tuxedo server as outlined in the chapter, "Configuring the Application

Server on Windows," the user ID designated to be the Application Server Administrator must have read/write permissions to the PeopleSoft file directory and read permission to the %TUXDIR% directory, such as

C:\oracle\tuxedo1.2.1.3.0.0_VS2012.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Setting Up Process Scheduler on Windows

4. Select the General tab.

Make sure that Startup Type is set to Automatic, as shown in this example, and click OK.

ORACLE ProcMGR V12.1.3.0.0_VS2012 Properties dialog box: General tab

5. Click Start.

A message in the Properties dialog box will indicate the "Started" status. You also see the status in the

Services dialog box. Click OK to close the dialog box.

Task 10A-2-2: Granting Process Scheduler Administrative Rights

To grant Process Scheduler administrative rights:

1. Log onto your PeopleSoft database through the PeopleSoft Pure Internet Architecture.

2. Select PeopleTools, Security, User Profiles.

3. Select the User Profiles component. Use the Search dialog to select the PeopleSoft User ID you plan to use to boot the Process Scheduler server.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

427

Setting Up Process Scheduler on Windows

Chapter 10A

4. Click the Roles tab, click the plus icon to insert a new row, and there enter the ProcessSchedulerAdmin role to grant the user ID with administrative rights in the Process Scheduler components.

Process Scheduler window: Roles tab

5. Repeat the instructions in step 4 to add the role ReportDistAdmin.

This will grant the user ID administrative rights to the Report Manager component. Carry out this step only if the same user is also responsible for maintaining the content of Report Manager.

6. Click Save to save your changes.

7. Select the General tab and jot down the Permission List name assigned to the Process Profile field.

8. From the Portal menu, choose PeopleTools, Security, Permissions & Roles, Permission Lists.

9. In the Search dialog, enter the Permission List you noted in step 7.

10. Select the Can Start Application Server check box.

11. Click Save to save your changes.

Task 10A-3: Setting Up Process Scheduler to Transfer Reports and Logs to the Report Repository

This section discusses:

• Understanding Report Distribution

428

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

• Setting Up Single Signon to Navigate from PIA to Report Repository

• Determining the Transfer Protocol

• Starting the Distribution Agent

• Setting Up the Report Repository

• Setting Up the Distribution for Your Process Scheduler Server

• Setting Up Sending and Receiving of Report Folders in the Report Manager

Setting Up Process Scheduler on Windows

Understanding Report Distribution

The PeopleSoft PeopleTools Report Distribution lets you access reports and log files generated from process requests run by a Process Scheduler Server Agent. Using the PeopleSoft Pure Internet Architecture, you can view reports and log files from the web browser through the Report Manager or Process Monitor Detail page. Report

Distribution enables you to restrict access to these reports to authorized users based either on user ID or role ID.

This product also includes the Distribution Agent component, which runs on the same server as the Process

Scheduler Server Agent. The Distribution Agent, a process that runs concurrently with the Process Scheduler

Server Agent, transfers to the Report Repository files generated by process requests initiated by the Process

Scheduler Server Agent.

The Distribution Agent transfers files to the Report Repository when one of these criteria is true:

• The Process Scheduler Server Agent is set up in the Server Definition to transfer all log files to the Report

Repository.

• The process request output destination type is Web/Window.

In either case, the Process Scheduler Server Agent inserts a row in the Report List table (PS_CDM_LIST). The server agent then updates the distribution status for a process request to Posting upon completion of the program associated with the process request. The distribution status of Posting signals that the files for the process request are ready for transfer to the Report Repository. The Distribution Agent is notified by Process Scheduler for any process requests that are ready for transferring. As part of the process to transfer files to the Report Repository, the Distribution Agent performs the following steps:

Transfer files to the Report Repository. All the report and log files are transferred to the Report Repository.

For each process request transferred, a directory is created in the Report Repository using the following format: \<database name\<date yyyymmdd>\<report id>. All the files for a process request are stored in this directory.

Delete the directory from the Process Scheduler Agent's Log/Output directory. When the output destination type specified for a process request is Web/Window, all the files and directory associated with the process request are deleted from the Process Scheduler Log/Output directory after the files are transferred to the

Report Repository.

The following diagram illustrates the Process Scheduler and Report Repository architecture. The diagram includes the following items:

• The web browser gives access to the Process Request dialog and the Report or Log Viewer.

• The Report Repository is part of the PeopleSoft Pure Internet Architecture.

Note. The PeopleSoft Pure Internet Architecture must be installed for Process Scheduler to be able to transfer reports to the Report Repository.

• The Process Scheduler Server includes the Process Scheduler Server Agent and the Distribution Agent.

• The transfer protocol between Process Scheduler and the Report Repository may be FTP/FTPS, XCOPY,

HTTP/HTTPS, or SFTP.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

429

Setting Up Process Scheduler on Windows

Chapter 10A

Process Scheduler and Report Repository Architecture

Before users can view a report, they are authenticated against the PeopleSoft database.

You should set up single signon if you do not want users to have to log on an additional time to view reports in the Report Repository. For the details on setting up single signon, consult the security documentation.

See PeopleTools: Security Administration.

430

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Setting Up Process Scheduler on Windows

Task 10A-3-1: Setting Up Single Signon to Navigate from PIA to Report

Repository

To view reports (log files or system files) from Report Repository, you need to pass the authentication. Report

Repository should be treated as a separate PeopleSoft application. To navigate from PeopleSoft Pure Internet

Architecture (PIA) to Report Repository, you need to set up single signon to avoid getting a prompt for a second signon. This section includes some considerations for setting up single signon to navigate from PIA to Report

Repository.

If Report Repository resides on the same web server as PIA, make sure your Local Message Node is set up to be a

"trusted" node for single signon for your system.

If Report Repository resides on a different web server than PIA, do the following:

• Make sure your Local Message Node is set up to be a "trusted" node for single signon for your system.

• Use a fully qualified domain name when addressing the web server for both PIA and Report Repository. For example, enter http://<machineName>.peoplesoft.com/<site_name>/signon.html instead of http://

<machineName>/<site_name>/signon.html.

• Specify the Authentication Domain for your application during installation. If you have multiple applications, and you want them to employ single signon, it is important to specify the same Authentication Domain for all applications.

See the information on implementing single signon in the PeopleTools: Security Administration product documentation.

• Set up single signon with a password, like this:

• Choose PeopleTools, Integration Broker, Integration Setup, Nodes.

• Click Search and then select the node marked as Default Local Node.

• Select Password for the Authentication Option.

• Enter a password of your choice.

• Enter the password again in the Confirm Password field.

• Enter the user ID for which you are setting up single signon in the Default User ID field.

• Save the Node Definition.

• Sign out from the PeopleSoft application.

• Reboot your application server.

See Also

PeopleTools: Security Administration

Task 10A-3-2: Determining the Transfer Protocol

We recommend using HTTP as your transfer protocol.

Before transferring the files to the Report Repository, you need to determine which transfer protocol to use. If you have a Microsoft Windows Process Scheduler and a Microsoft Windows web server, you can use either an

XCOPY, FTP/FTPS, SFTP, or HTTP/HTTPS protocol. (If FTP information is not specified, Process Scheduler will perform an XCOPY.) If you have a PeopleSoft Process Scheduler on Microsoft Windows and a UNIX web server, you can use FTP/FTPS, SFTP, or HTTP/HTTPS.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

431

Setting Up Process Scheduler on Windows

Note. If you are using FTP/FTPS or SFTP, the corresponding service must be set up in your web server.

Note. JRE is installed automatically on your Process Scheduler server.

Chapter 10A

Task 10A-3-3: Starting the Distribution Agent

The Distribution Agent is automatically started as another Oracle Tuxedo server when a Process Scheduler Server is booted. If a Process Scheduler Server was set up without specifying a Distribution Node in the Server

Definition page, the Process Scheduler server will have a status in Process Monitor of "Running with No Report

Node." After a node is defined for the Process Scheduler server, in the next cycle the Process Scheduler server checks the state of the system, and the Distribution Agent dynamically sets up its environment.

Task 10A-3-4: Setting Up the Report Repository

This section discusses:

• Defining ReportRepositoryPath

• Defining the Report Node to Use HTTP/HTTPS

• Defining the Report Node to Use XCOPY

• Defining the Report Node to Use FTP

• Defining the Report Node to Use FTPS

• Defining the Report Node to Use SFTP

Defining ReportRepositoryPath

The ReportRepositoryPath specifies the location of a directory for the Report Repository. You can specify the location for the Report Repository Path on the General page of the Web Profile during installation. If you do not set the location in the Web Profile, the location given by ReportRepositoryPath in the configuration.properties file is used for the default location. Note that the value entered for Report Repository Path in the Web Profile overrides any entry in the configuration.properties file.

See PeopleTools: Portal Technology, "Configuring Web Profiles."

Use the following formats to enter the name for the directory that you want to use for the ReportRepositoryPath.

The examples below give the default values. Note that you must use a forward slash ('/') in both cases:

Microsoft Windows: ReportRepositoryPath=c:/psreports

UNIX: ReportRepositoryPath=<user_home>/PeopleSoft Internet Architecture/psreports

For <user_home> substitute the home directory for the current user.

Defining the Report Node to Use HTTP/HTTPS

To define the report node to use HTTP/HTTPS:

1. Select PeopleTools, Process Scheduler, Report Nodes.

2. Select the Add a New Value link and enter the Report node name.

432

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Setting Up Process Scheduler on Windows

3. On the Report Node Definition page, select HTTP or HTTPS from the Protocol drop-down list.

Select the HTTP option if you are not using SSL. Select the HTTPS option if you are using SSL. The pages for HTTP and HTTPS have the same fields. These examples show HTTP.

Note that if you are using SSL you need to have Client Certificates installed on your web server.

Report Node Definition page for the HTTP protocol

4. Enter the following information in the Distribution Node Details area:

URLID: Enter the URL of the web server using the following format: http://<machine_name>:<port_number>/psreports/<site_name>

Replace <machine_name> with the name of your machine. Use the fully qualified host name for your web server. If you are using an HTTP or HTTPS port other than the defaults, you need to specify the port number.

Note. If you specify the Authentication Token Domain name during the PIA installation, you must include a fully qualified domain name for the URL instead of the IP address.

Description: Enter a description of the server (optional).

Operating System: Select the web server operating system, Windows or UNIX.

5. Enter the following information in the Login Details area:

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

433

Setting Up Process Scheduler on Windows

Chapter 10A

Login ID: Enter the Login ID. This is not required, unless basic authentication has been set up on the web server by the Web Administrator.

Password and Confirm Password: Enter the password, and confirm it, for the user ID specified in the

Login ID field. This is not required, unless basic authentication has been set up on the web server by the

Web Administrator.

Note. The setup of authentication is optional, but is recommended for security of the Report Repository when using the HTTP to transfer files. For information on setting up authentication on the web server where the Report Repository resides, refer to the PeopleTools: Security Administration product documentation.

6. Enter the following information in the URI Details area:

URI Host: Enter the machine name for the report repository.

Note. In a basic setup, the machine name for the report repository will match the machine name of the web server URL. However, under certain circumstances—for example, if you are using a reverse proxy server—the URL and URI Host may have different machine names.

URI Port: Enter the port number, which must match the port number of your web server (defaults are

HTTP = 80, HTTPS = 443). If you change a port number you will lose the default values for both protocols.

URI Resource: Enter SchedulerTransfer/<site name>.

7. Click Save to save your entries.

8. Click Validate to confirm that your entries are complete and correct.

The validation confirms that the necessary parameters are present and correct, and simulates a file transfer with the entered information. You either see a message that confirms the success of the validation, or a message that displays an error for missing parameters or an unsuccessful transfer simulation.

9. To add additional report nodes, click Add to return to the Search page.

Defining the Report Node to Use XCOPY

Both the Process Scheduler machine and the Report Repository machine must be Microsoft Windows machines for XCOPY to be used.

To define the report node to use XCOPY:

1. Select PeopleTools, Process Scheduler, Report Nodes.

2. Select Add a New Value, enter the Report node name, and click Add.

434

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Setting Up Process Scheduler on Windows

3. On the Report Node Definition page, select XCOPY from the Protocol drop-down list.

Report Node Definition page for the XCOPY protocol

4. Enter the following information in the Distribution Node Details area:

URLID: Enter the URL of the web server using this format: http://<machine_name>:<port_number>/psreports/<site_name>

Replace <machine name> with the name of your web server. Replace <site name> with the directory where you installed the PIA files.

If you installed the web server software with the default TCP port of 80, you do not need to specify the port number in the URL path. However, if you installed the web server to some other port, you must specify the port number in the URL path.

Description: Enter an optional description for the node.

Network Path: Enter the path that points to your Report Repository share, using this format (where

<machine_name> refers to the web server machine):

\\<machine_name>\psreports

Make sure that this directory is shared with the login accounts used to start Process Scheduler. Use UNC format instead of mapped drive format.

5. Select Save to save your entries.

6. Click Validate to confirm that your entries are correct.

The validation confirms that the necessary parameters are present and correct, and simulates a file transfer with the entered information. You either see a message that confirms the success of the validation, or a message that displays an error for missing parameters or an unsuccessful transfer simulation.

7. To add additional report nodes, select Add to return to the Search page.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

435

Setting Up Process Scheduler on Windows

Chapter 10A

Defining the Report Node to Use FTP

If you use the FTP report node protocol, note that:

• If your FTP server is a Microsoft Windows server, you may have to set up the FTP service.

• The Distribution Agent will perform a validation after FTP has transferred files into the Report Repository by sending a query request to the web server. For this task to be completed, it is critical that the value entered in the URL is accurate. Verify that the machine name, port number, and site number that you specify are correct.

If this setup is not completed, the process request will get a status of NOT POSTED in the Process Monitor

Detail page and will log the message "Unable to verify files posted."

To define the report node to use FTP:

1. Select PeopleTools, Process Scheduler, Report Nodes.

2. Select Add a New Value, enter the Report node name, and click Add.

436

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Setting Up Process Scheduler on Windows

3. On the Report Node Definition page, select FTP from the Protocol drop-down list.

Report Node Definition page for the FTP protocol

4. In the Distribution Node Details area, enter the following information:

URLID: Enter the URL of the web server using this format: http://<machine_name>:<port_number>/psreports/<site_name>

Replace <machine name> with the name of your web server. If you are using an HTTP port other than 80, you need to specify the port number. The variable <site name> refers to the directory where you installed the PIA files; this will default to ps for the first installation.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

437

Setting Up Process Scheduler on Windows

Chapter 10A

Note. If you specify the Authentication Token Domain name during the PIA installation, you must include a fully qualified domain name for the URL instead of the IP address.

Note. If you installed the web server software with the default TCP port of 80, you do not need to specify the port number in the URL path. However, if you installed the web server to some other port, you must specify the port number in the URL path.

Description: Enter a description of the server (optional).

Operating System: Select the operating system of the Report Repository, Windows or UNIX.

Network Path: This information is not required for the FTP protocol

5. In the Login Details area, enter the following information:

Login ID: Enter the FTP User ID.

Password and Confirm Password: Enter the password, and enter it a second time, for the FTP User ID specified in the Login ID field.

6. In the File Transfer Details area, enter the following information:

Home Directory: Enter the directory specified during the PIA installation as the Report Repository. The

FTP User ID must have write access to this directory. Note that this is not a required field for FTP transfer, as the system uses the Report Repository directory specified at install time or the current directory assigned to ReportRepositoryPath in configuration.properties. Note that the value you enter for the Report Repository Path in the Web Profile at install time overrides any entry for ReportRepositoryPath in configuration.properties.

For Microsoft Windows operating systems, the directory needs to match the Report Repository path. Make sure that you do not include any drive information

—as in c:\psreports\—because you are using the FTP protocol to interpret this parameter.

FTP Address: Enter the machine name or the IP address of the Report Repository. If the name of the machine is used, it must be included on a DNS server.

438

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Setting Up Process Scheduler on Windows

7. If you need to specify additional properties, use the Connection Properties area. Specifying the Connection

Properties is optional.

Click the lookup button (magnifying glass) and select one of the properties in the following table. Click the plus sign to add another connection property.

Property Name

ACTIVEMODE

Property Value

To enable active mode, add the ACTIVEMODE property to the URL and set it to Y.

The default FTP connection mode is extended passive mode.

ACTIVEPORTOPTION

ENABLEEPRT

EXTENDEDPASSIVEMODE

This property can be used along with ACTIVEMODE.

When active mode is enabled, you can use

ACTIVEPORTOPTION to specify the IP address and port on which the FTP server can be accessed. This is useful when the server is behind a firewall. By default,

ACTIVEPORTOPTION uses the default IP address of your system. If you want to use a particular IP address, set the ACTIVEPORTOPTION value to either the full IP address, a host name to resolve to an IP address, or a local network interface name.

You can also specify a port range. For example:

10.176.147.111:10000-13000

This option can be used only with Active Mode. If Active

Mode is enabled and ENABLEEPRT is set to N, then the system will use a PORT (IPv4) Active Mode connection.

By default, ENABLEEPRT is Y, if Active Mode is set to

Y.

0: Disable EPSV

1: Enable EPSV

This property enables you to control whether extended passive mode (EPSV) will be used by FTP.

EPSV is used by default. That is, by default, this value is considered to be 1.

If the client fails to connect to the server with EPSV, then the system will try passive mode (PASV). To use PASV only, add EXTENDEDPASSIVEMODE to the URL

Properties and set it to 0.

JKSPASSWORD

JKSPATH

Specify the Java keystore (JKS) password.

Specify the Java keystore (JKS) path.

PASSWORD

USER

Specify the password associated with the USER property, which identifies the FTP User ID.

Specify the FTP User ID used for authentication when accessing the FTP site.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

439

Setting Up Process Scheduler on Windows

Chapter 10A

8. If you need to specify an encrypted password in any of the property fields, use the Password Encryption area to generate the encrypted password, as follows: a. In the Password field, enter a password.

b. In the Confirm Password field, enter the password again.

c. Click Encrypt.

The encrypted password is displayed in the Encrypted Password field.

d. From the Encrypted Password field, cut the encrypted password and then copy the encrypted value to the appropriate location.

9. Select Save to save your entries.

10. Click Validate to confirm that your entries are correct.

The validation confirms that the necessary parameters are present and correct, and simulates a file transfer with the entered information. You either see a message that confirms the success of the validation, or a message that displays an error for missing parameters or an unsuccessful transfer simulation.

11. To add additional report nodes, click Add to return to the Search page.

Defining the Report Node to Use FTPS

To define the report node to use FTPS:

1. Select PeopleTools, Process Scheduler, Report Nodes.

2. Select Add a New Value, enter the Report node name, and click Add.

440

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Setting Up Process Scheduler on Windows

3. On the Report Node Definition page, select FTPS from the Protocol drop-down list.

Report Node Definition page for the FTPS protocol

4. In the Distribution Node Details area, enter the following information:

URLID: Enter the URL of the web server using this format: http://<machine_name>:<port_number>/psreports/<site_name>

Replace <machine name> with the name of your web server. If you are using an HTTP port other than 80, you need to specify the port number. The variable <site name> refers to the directory where you installed the PIA files; this will default to ps for the first installation.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

441

Setting Up Process Scheduler on Windows

Chapter 10A

Note. If you specify the Authentication Token Domain name during the PIA installation, you must include a fully qualified domain name for the URL instead of the IP address.

Note. If you installed the web server software with the default TCP port of 80, you do not need to specify the port number in the URL path. However, if you installed the web server to some other port, you must specify the port number in the URL path.

Description: Enter a description of the server (optional).

Operating System: Select the operating system of the Report Repository, Windows or UNIX.

Network Path: This information is not required for the FTPS protocol.

5. In the Login Details area, enter the following information:

Login ID: Enter the FTP User ID.

Password and Confirm Password: Enter the password, and enter it a second time, for the user ID specified in the Login ID field.

6. In the File Transfer Details area, enter the following information:

Home Directory: Enter the directory specified during the PIA installation as the Report Repository. The

FTP User ID must have write access to this directory. Note that this is not a required field for FTP transfer, as the system uses the Report Repository directory specified at install time or the current directory assigned to ReportRepositoryPath in configuration.properties. Note that the value you enter for the Report Repository Path in the Web Profile at install time overrides any entry for ReportRepositoryPath in configuration.properties.

For Microsoft Windows operating systems, the directory needs to match the Report Repository path. Make sure that you do not include any drive information

—as in c:\psreports\—because you are using the FTP protocol to interpret this parameter.

FTP Address: Enter the machine name or the IP address of the Report Repository. If the name of the machine is used, it must be included on a DNS server.

SSL Mode: Select Explicit or Implicit from the drop-down list.

These are two separate methods developed to invoke the client security for use with FTP clients. With the explicit mode, FTPS-aware clients can invoke security with an FTPS-aware server without breaking overall FTP functionality with non-FTPS-aware clients. The implicit method requires that all clients of the

FTPS server be aware that SSL is to be used on the session, and thus is incompatible with non-FTPSaware clients.

442

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Setting Up Process Scheduler on Windows

7. In the Connection Properties area, click the lookup button (magnifying glass) and select one of the properties in the following table:

Click the plus sign to add another connection property.

Property Name

ACTIVEMODE

Property Value

To enable active mode, add the ACTIVEMODE property to the URL and set it to Y.

The default FTPS connection mode is extended passive mode.

ACTIVEPORTOPTION This property can be used along with ACTIVEMODE.

When active mode is enabled, you can use

ACTIVEPORTOPTION to specify the IP address and port on which the FTP server can be accessed. This is useful when the server is behind a firewall. By default,

ACTIVEPORTOPTION uses the default IP address of your system. If you want to use a particular IP address, set the ACTIVEPORTOPTION value to either the full IP address, a host name to resolve to an IP address, or a local network interface name.

You can also specify a port range. For example:

10.176.147.111:10000-13000

CERTALIAS Certificate Alias: The Certificate Alias must be an alias name of a certificate stored in the database (using the

PeopleSoft PeopleTools Digital Certificates page).

Note. Currently, only PEM certificates are supported for

FTPS.

ENABLEEPRT

EXTENDEDPASSIVEMODE

JKSPASSWORD

JKSPATH

This option can be used only with Active Mode. If Active

Mode is enabled and ENABLEEPRT is set to N, then the system will use a PORT (IPv4) Active Mode connection.

By default, ENABLEEPRT is Y, if Active Mode is set to

Y.

0: Disable EPSV

1: Enable EPSV

This property enables you to control whether extended passive mode (EPSV) will be used by FTP.

EPSV is used by default. That is, by default, this value is considered to be 1.

If the client fails to connect to the server with EPSV, then the system will try passive mode (PASV). To use PASV only, add EXTENDEDPASSIVEMODE to the URL

Properties and set it to 0.

Specify the Java keystore (JKS) password.

Specify the Java keystore (JKS) user.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

443

Setting Up Process Scheduler on Windows

Chapter 10A

Property Name

KEYSTOREPASSWORD

PASSWORD

SSLUAGELEVEL

USER

VERIFYHOST

VERIFYPEER

Property Value

This property is required for FTPS and HTTPS repositories. For attachments transferred from the

PeopleSoft system to the FTPS or HTTPS repository, the system retrieves the key pair for the client certificate from the digital certificate store and writes the pair to a file in

PKCS12 format with password protection. The value of this property will be used as the password for the PKCS12 file.

The PKCS12 file enables connection and file transfer, and it exists only temporarily in

<PS_SERVDIR>\files\<CERT ALIAS NAME> for the duration of the file transfer. The system deletes the file after the file transfer transaction.

Note. If the system fails to delete the certificate alias file, a message will be written to the application server log. The maximum number of files that can exist at any time is equal to the total number of FTPS and HTTPS URL identifiers defined in the system.

For information on setting the PS_SERVDIR environment variable, see the PeopleTools: Integration Broker product documentation.

Specify the password associated with the USER property, which identifies the FTP User ID.

0 - No SSL: No SSL will be used.

1 - Try SSL: Try using SSL, but proceed as normal otherwise.

2 - Control: Require SSL for the control connection.

3 - SSL Only: (Default) Require SSL for all communication.

Specify the FTP User ID used for authentication when accessing the FTP site.

0: Do not verify the server for host name.

1: Check if there exists any value in the common name field in the server certificate. This check does not verify if it matches with what the client specifies.

2: (Default) Check for a match with the host name in the URL with the common name or Subject Alternate field in the server certificate.

False: Do not verify the peer.

True: (Default) Verify the peer by authenticating the certificate sent by the server.

8. If you need to specify an encrypted password in any of the property fields, use the Password Encryption area to generate the encrypted password, as follows:

444

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Setting Up Process Scheduler on Windows

a. In the Password field, enter a password.

b. In the Confirm Password field, enter the password again.

c. Click Encrypt.

The encrypted password is displayed in the Encrypted Password field.

d. From the Encrypted Password field, cut the encrypted password and then copy the encrypted value to the appropriate location.

9. Select Save to save your entries.

10. Click Validate to confirm that your entries are correct.

The validation confirms that the necessary parameters are present and correct, and simulates a file transfer with the entered information. You either see a message that confirms the success of the validation, or a message that displays an error for missing parameters or an unsuccessful transfer simulation.

11. To add additional report nodes, click Add to return to the Search page.

Defining the Report Node to Use SFTP

To define the report node to use SFTP:

1. Select PeopleTools, Process Scheduler, Report Nodes.

2. Select Add a New Value, enter the Report node name, and click Add.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

445

Setting Up Process Scheduler on Windows

3. On the Report Node Definition page, select SFTP from the Protocol drop-down list.

Chapter 10A

Report Node Definition page for the SFTP protocol

4. In the Distribution Node Details area, enter the following information:

URLID: Enter the URL of the web server using this format: http://<machine_name>:<port_number>/psreports/<site_name>

Replace <machine name> with the name of your web server. If you are using an HTTP port other than 80, you need to specify the port number. The variable <site name> refers to the directory where you installed the PIA files; this will default to ps for the first installation.

446

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Setting Up Process Scheduler on Windows

Note. If you specify the Authentication Token Domain name during the PIA installation, you must include a fully qualified domain name for the URL instead of the IP address.

Note. If you installed the web server software with the default TCP port of 80, you do not need to specify the port number in the URL path. However, if you installed the web server to some other port, you must specify the port number in the URL path.

Description: Enter a description of the server (optional).

Operating System: Select the operating system of the Report Repository, Windows or UNIX.

Network Path: This information is not required for the SFTP protocol.

5. In the Login Details area, enter the following information:

Login ID: Enter the FTP User ID.

Password and Confirm Password: Enter the password, and enter it a second time, for the user ID specified in the Login ID field.

6. In the File Transfer Details area, enter the following information:

Home Directory: Enter the directory specified during the PIA installation as the Report Repository. The

FTP User ID must have write access to this directory. Note that this is not a required field for FTP transfer, as the system uses the Report Repository directory specified at install time or the current directory assigned to ReportRepositoryPath in configuration.properties. Note that the value you enter for the Report Repository Path in the Web Profile at install time overrides any entry for ReportRepositoryPath in configuration.properties.

For Microsoft Windows operating systems, the directory needs to match the Report Repository path. Make sure that you do not include any drive information

—as in c:\psreports\—because you are using the FTP protocol to interpret this parameter.

FTP Address: Enter the machine name or the IP address of the Report Repository. If the name of the machine is used, it must be included on a DNS server.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

447

Setting Up Process Scheduler on Windows

Chapter 10A

7. In the Connection Properties area, click the lookup button (magnifying glass) and select one of the properties in the following table.

Click the plus sign to add additional connection properties.

Property Name

AUTHTYPE

PASSWORD

Property Value

Select one of the following the authentication types:

PUBLICKEY

PASSWORD

ANY

Specify the user password. You can enter the password in the Password Encryption box, click Encrypt, and then copy the encrypted value to the Password property.

PASSWORDKEY

PRIVATEKEY

PUBLICKEY

Enter the password for the private key.

Select the private key.

Select the public key.

SSHKEYALIAS

USER

Select the SSH certificate saved to the database using the

PeopleTools Security, Digital Certificates page (select

PeopleTools, Security, Security Objects, Digital

Certificates). The SSH certificate added through the

Digital Certificates page contains both the public and private key data, identified by the Alias column value on the Digital Certificates page.

If using the SSHKEYALIAS URL property, the Property

Value prompt displays only the list of SSH certificates that have been added to the Digital Certificates page. If you have added the SSH certificate using the Digital

Certificates page, and you have assigned an SSH certificate to the SSHKEYALIAS URL property, the system ignores the PUBLICKEY and PRIVATEKEY properties, regardless of whether they refer to valid key files in the file system.

If you provided a password (or passphrase) when generating your SSH certificate, specify that value using the PASSWORDKEY URL property.

See PeopleTools: Security Administration, "Configuring

Digital Certificates."

Specify the user ID to be authenticated.

8. If you need to specify an encrypted password in any of the property fields, use the Password Encryption area to generate the encrypted password, as follows: a. In the Password field, enter a password.

b. In the Confirm Password field, enter the password again.

c. Click Encrypt.

448

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Setting Up Process Scheduler on Windows

The encrypted password is displayed in the Encrypted Password field.

d. From the Encrypted Password field, cut the encrypted password and then copy the encrypted value to the appropriate location.

9. Select Save to save your entries.

10. Click Validate to confirm that your entries are correct.

The validation confirms that the necessary parameters are present and correct, and simulates a file transfer with the entered information. You either see a message that confirms the success of the validation, or a message that displays an error for missing parameters or an unsuccessful transfer simulation.

11. To add additional report nodes, click Add to return to the Search page.

Task 10A-3-5: Setting Up the Distribution for Your Process Scheduler

Server

To set up the Distribution Settings for your Process Scheduler Server:

1. Select PeopleTools, Process Scheduler, Servers.

2. Enter the Server Name (such as PSNT). The Server Definition page appears.

3. Select the Distribution tab.

Server Definition page for PSNT: Distribution tab

4. Click the lookup button for Distribution Node Name to display the report node names and select the name of the required report node.

5. Enter a number for the Maximum Transfer Retries. This is the maximum number of times the server can try to send a report before it errors out.

6. Enter the number of seconds for the Interval for Transfer Attempt field. This is the interval between attempts to send the report.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

449

Setting Up Process Scheduler on Windows

Chapter 10A

7. Select the check box Transfer Log Files to Report Repository if you want to transfer all log and trace files from processes that do not generate reports.

8. Click Save to save your entries.

9. If Process Scheduler is running, you must reboot for any new settings to take effect.

To view reports (log files or system files) from Report Repository, you need to pass the authentication. Report

Repository should be treated as a separate PeopleSoft application. To navigate from PIA to Report Repository, you need to set up single signon in order to avoid getting a prompt for a second signon.

Task 10A-3-6: Setting Up Sending and Receiving of Report Folders in the

Report Manager

To be able to view reports in the Report Manager Explorer and List pages, you need to set up the sending and receiving of report folders in the Report Manager by activating the domain on which a sending and receiving server resides. Consult the documentation covering the PeopleSoft Integration Broker to learn how to activate the sending and receiving server domain.

See PeopleTools: Integration Broker.

See PeopleTools: Integration Broker Service Operations Monitor.

Task 10A-4: Setting Environment Variables

To set the appropriate Tuxedo environment variables, carry out these steps. (If you have already set these variables on the machine you are using as your Process Scheduler Server, you can skip this task.)

See "Installing Additional Components," Installing Oracle Tuxedo on Microsoft Windows.

To set the variables:

1. Choose Start, Settings, Control Panel.

2. Double-click the System icon.

3. Make sure that the NLSPATH environment variable is set.

NLSPATH does not need to be explicitly set since Oracle Tuxedo sets NLSPATH in its own registry tree.

This value can be displayed using Control Panel, Tuxedo, on the Environment tab. However, the installation of certain products, such as IBM DB2 connectivity (DB2 for z/OS and DB2 for Linux, UNIX, and Windows) sets NLSPATH to a value that causes Oracle Tuxedo to fail. The solution is to either set

NLSPATH=c:\tuxedo\locale\c, or to delete it entirely and let Oracle Tuxedo pick up the value from its registry tree. If you are running DB2 for Linux, UNIX, and Windows, the solution instead is to append the c:\tuxedo\locale\c directory in the NLSPATH directory.

Search the Oracle Tuxedo documentation for additional information on NLSPATH.

Task 10A-5: Setting Up Process Scheduler Server Agent

This section discusses:

• Understanding Process Scheduler Server Agent

• Creating and Configuring a Process Scheduler Server

• Reconfiguring a Process Scheduler Server

450

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

• Verifying the Process Scheduler Server Status

Setting Up Process Scheduler on Windows

Understanding Process Scheduler Server Agent

For installation purposes, you can use predefined server names and other definitions. The predefined name that you might use is as follows:

Server Name

PSNT

Operating System

Microsoft Windows

To test this, use processes already defined in your PeopleSoft database. To set up a new server definition in your

PeopleSoft database, refer to the PeopleTools: Process Scheduler product documentation.

Note. When creating multiple Process Scheduler Servers for the same database, each server must have a unique server name. For example, two Process Scheduler Servers, both named PSNT, cannot run against the same database.

Task 10A-5-1: Creating and Configuring a Process Scheduler Server

This section describes how to create and configure a Process Scheduler server.

You can set Process Scheduler configuration parameters either by using PSADMIN, which provides an interactive dialog, or by editing the configuration file psprcs.cfg located in the PS_CFG_HOME\appserv\prcs\database name directory. The following steps assume you are using PSADMIN to specify parameter settings.

Note. For Cube Builder users, if Essbase Server is installed on a different machine than the Process Scheduler, you must install Essbase Client 11.1.2.1 on the process scheduler server machine. You must also ensure that the

%ESSBASEPATH% and %ARBORPATH% environmental variables are properly set in the Process Scheduler.

Note. If you use the configuration file psprcs.cfg, be aware that in the PeopleSoft PeopleTools 8.49 release and later, the section [Output Dest Exceptions] has been modified to trap metastring exceptions not only in the output destination but in other process parameters as well. In this section the entry

OUTDEST_EXCEPT01=%ANYMETASTRING%

has been changed to

PARAMETER_EXCEPT01=%ANYMETASTRING%

.

To create and configure a Process Scheduler Server:

1. From PS_HOME\appserv on the batch server, type psadmin

.

You see the PeopleSoft Server Administration menu, as in this example:

----------------------------------------------

PeopleSoft Server Administration

---------------------------------

PS_CONFIG_HOME       C:\User\JSMITH\psft\pt\8.55

PS_HOME              C:\PT8.55

PS_APP_HOME          C:\HC9.2

1) Application Server

2) Process Scheduler

3) Search Server

4) Web (PIA) Server

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

451

Setting Up Process Scheduler on Windows

Chapter 10A

5) Switch Config Home

6) Service Setup

7) Replicate Config Home

8) Refresh Config Home q) Quit

Command to execute (1-8 q): 

2. Depending on your environment, you may see a message after the menu selection, which indicates that

PSADMIN has modified the PS_CFG_HOME/peopletools.properties file with the current PS_HOME location:

************************************************************

PS_CFG_HOME/peopletools.properties file has been updated.

You should use the Config Home Refresh feature in PSAdmin  to ensure that all of your domains are current.

Alternatively, you may recreate all of your domains.

Please press any key to continue...

*************************************************************

This indicates that one of these situations exists:

• The PS_CFG_HOME that you are working with was used previously from a different PS_HOME. In this case, you should recreate any existing Application Server, Process Scheduler, Search, or PIA domains in this PS_CFG_HOME.

• You configured your environment such that PS_CFG_HOME is the same as PS_HOME. The first time you use PSADMIN to create a domain, it updates the PS_CFG_HOME/peopletools.properties file.

Continue with the next step.

3. Select 2 to access the Process Scheduler submenus.

4. Select 2 for Create a domain from the PeopleSoft Process Scheduler Administration menu.

-------------------------------------------

PeopleSoft Process Scheduler Administration

-------------------------------------------

1) Administer a domain

2) Create a domain

3) Delete a domain

4) Import domain configuration q) Quit

Command to execute (1-4, q) : 2

5. When prompted for the name of the database that your server will access, enter the name of the database, such as HRDMO in this example, and press ENTER:

Please enter name of Database that server will access : HRDMO

6. After the system creates the domain, the Quick-configure menu appears:

------------------------------------------------------------

Quick-configure menu -- domain: HRDMO

------------------------------------------------------------

     Features                      Settings

    ==========                    ==========

  1) App Engine        : Yes    9) DBNAME     :[HRDMO]   

452

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Setting Up Process Scheduler on Windows

  2) Master Scheduler  : Yes   10) DBTYPE     :[ORACLE]  

  3) Perf Collator     : No    11) PrcsServer :[PSNT]

  4) Domains Gateway   : No    12) UserId     :[PS]

  5) Push Notifications: No    13) UserPswd   :[]

                               14) ConnectID  :[people]

                               15) ConnectPswd:[]    

                               16) Log/Output Dir:[%PS_SERVDIR%\log_⇒ output]

                               17) SQRBIN     :[%PS_HOME%\bin\sqr\ORA⇒

\binw]   

                               18) AddToPATH  :[%WINDIR%;%WINDIR%⇒

\SYSTEM32]

                               19) DBBIN      :[C:\<connectivity⇒

 directory>]

                               20) DomainConnectPswd:[]

     Actions

    =========

  6) Load config as shown

  7) Custom configuration

  8) Edit environment settings

  h) Help for this menu

  q) Return to previous menu

HINT: Enter 9 to edit DBNAME, then 6 to load

Enter selection (1-20, h, or q):

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

453

Setting Up Process Scheduler on Windows

Chapter 10A

7. If you need to modify any of these settings, enter the number next to the parameter name, type the new value, and press ENTER. This table lists the parameters and gives brief descriptions.

Parameter

Master Scheduler

App Engine

Perf Collator

Domain Gateways

Push Notifications

Load config as shown

Description

Select this option to enable the Master Scheduler Server

(PSMSTPRC). The default is to enable the server.

See PeopleTools: Process Scheduler.

Select this option to initiate Application Engine programs through the AE Tuxedo Server (PSAESRV). The default is set to run AE using PSAESRV.

See PeopleTools: Process Scheduler.

Select this option to enable the PSPPMSRV server process.

See PeopleTools: Performance Monitor, "Enabling the

Required Elements on the Monitoring System."

Select this option to enables inter domain communication, for example between Application Server and Process

Scheduler domains.

See PeopleTools: Fluid User Interface Developer's Guide,

"Setting Up Push Notification Configurations."

Select this option to enables pushing server events from

PeopleSoft PeopleTools server runtime, such as

Application Server and Process Scheduler, to browser clients and other PeopleSoft PeopleTools server runtime components.

See PeopleTools: Fluid User Interface Developer's Guide,

"Setting Up Push Notification Configurations."

Load the selections you made in the Quick Configure menu.

Custom configuration

Edit environment settings

DBNAME

DBTYPE

PrcsServer

Make custom selections in PSADMIN, using options that are not available in the Quick Configure menu.

Edit, add, remove, comment out, and review domain-level environment variables.

Specify the database name that is associated with a

PeopleSoft Process Scheduler Server Agent, such as

HRDMO, FSDMO, SADMO, and so on.

Specify the database type: ORACLE.

Specify the process server name. This must match the name defined in the Server Definition table, such as PSNT or PSUNX.

454

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Parameter

UserId

UserPswd

ConnectID

ConnectPswd

Log/Output Dir

SQRBIN

AddToPATH

DBBIN

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Setting Up Process Scheduler on Windows

Description

Enter the user ID, such as VP1 or PS.

Enter the password for the user ID, as you specified during the database configuration.

The password is hidden by masking characters as you type, in the Quick-configure menu after entry.

Enter the connect ID. This value is required.

Enter the connect password, as you specified during the database configuration. This value is required.

The password is hidden by masking characters as you type, in the Quick-configure menu after entry.

Specify the directory in which files that are generated by the program are written. When PeopleSoft Process

Scheduler initiates a process request, it creates a subdirectory in the format <Process Type ID>_<Program

Name>_<Process Instance> that contains the generated files. For instance, the SQR program XRFWIN that ran with process instance 20 has all reports, trace, and log files in the subdirectory SQR_XRFWIN_20. It is also the optional directory used with the Output Destination field when scheduling a request. This variable

(%%OutputDirectory%%) can be used in the File/Printer field of the Process Scheduler Request dialog box.

Enter the path to the SQR executables.

(Optional for Tuxedo) Specify an additional directory that is appended to the PATH environment variable.

Add the paths to the 64-bit connectivity software. For example:

C:\oracle\product\11.2.0\dbhome_1\BIN.

Note. If the PATH environment variable contains the path for the 64-bit connectivity software, then you do not need to change the setting for AddToPATH.

Enter the path to the database drivers; that is, your connectivity software.

For an Oracle installation, this should indicate the 64-bit connectivity software, for example

C:\oracle\product\11.2.0\dbhome_1\BIN.

455

Setting Up Process Scheduler on Windows

Chapter 10A

Parameter

DomainConnectPswd

Description

If you configured your Application Server domain to require a Domain Connection password, enter it here.

Otherwise, leave it blank.

The password is hidden by masking characters as you type, and in the Quick-configure menu after entry.

See the information on setting Application Server Domain

Parameters in the PeopleTools: System and Server

Administration product documentation.

For descriptions of the PSADMIN options that do not appear in the Quick-configure menu, see the information on using PSADMIN in the PeopleTools: Process Scheduler product documentation. For a basic installation, in most cases you can accept the defaults.

8. When you have updated the settings as needed, choose 5, Load config as shown, from the Quick-Configure menu to save your settings to the Process Scheduler configuration file, pstuxcfg.

9. To start Process Scheduler, choose 1, for Administer Domain.

10. On the PeopleSoft Process Scheduler Administration menu, choose 1 for Boot this domain.

--------------------------------

PeopleSoft Process Scheduler Administration

---------------------------------

Domain Name: HRDMO

1) Boot this domain

2) Domain shutdown menu

3) Domain status menu

4) Configure this domain

5) TUXEDO command line (tmadmin)

6) Edit configuration/log files menu

7) Clean IPC resources of this domain q) Quit

Command to execute (1-7, q) :

11. Choose 1, Boot (Serial Boot), or 2, Parallel Boot, from the PeopleSoft Domain Boot Menu.

Note. The messages you see and the number of processes started will depend on the options you chose during configuration.

12. If you want to stop Process Scheduler Server, from the PeopleSoft Domain Administration menu, choose 2, for Domain Shutdown menu, and then enter the number corresponding to the name of the appropriate database.

456

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Setting Up Process Scheduler on Windows

Note. If you see the following message, then the server is already down:

Command to execute (1-2, q) [q]: 1 Loading command line administration utility ... tmadmin - Copyright (c) 2007-2008, Oracle. Portions *

Copyright 1986-1997 RSA Data Security, Inc. All Rights Reserved.

Distributed under license by Oracle. Tuxedo is a registered trademark. No bulletin board exists. Entering boot mode. > TMADMIN_CAT:111: ERROR: No such command.

Task 10A-5-2: Reconfiguring a Process Scheduler Server

If you create and then immediately configure a Process Scheduler server, you can use the Quick-configure menu.

Alternatively, you can use PSADMIN as described in this section. Feel free to skip this procedure if you have already created and configured your Process Scheduler Server using the Quick-configure menu and want to move forward with your installation.

Note. If you want to configure the Process Scheduler Server while it is running, you need to stop and restart the server to load the new settings.

To reconfigure a Process Scheduler Server:

1. Go to PS_HOME\appserv and enter: psadmin

2. Depending on your environment, you may see a message after the initial menu, which indicates that

PSADMIN has modified the PS_CFG_HOME/peopletools.properties file with the current PS_HOME location:

************************************************************

PS_CFG_HOME/peopletools.properties file has been updated.

You should use the Config Home Refresh feature in PSAdmin  to ensure that all of your domains are current.

Alternatively, you may recreate all of your domains.

Please press any key to continue...

*************************************************************

This indicates that one of these situations exists:

• The PS_CFG_HOME that you are working with was used previously from a different PS_HOME. In this case, you should recreate any existing Application Server, Process Scheduler, Search, or PIA domains in this PS_CFG_HOME.

• You configured your environment such that PS_CFG_HOME is the same as PS_HOME. The first time you use PSADMIN to create a domain, it updates the PS_CFG_HOME/peopletools.properties file.

Continue with the next step.

3. Select 2 for Process Scheduler in the PeopleSoft Server Administration menu.

4. In the PeopleSoft Process Scheduler Administration menu, select 1 for Administer a domain.

5. Select the database for which the Process Scheduler needs to be configured.

6. You see the following prompt:

Do you want to change any config values (y/n)? [n]:

Specify y to start an interactive dialog that lets you examine or change parameter values.

7. Specify the configuration parameters one by one.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

457

Setting Up Process Scheduler on Windows

Chapter 10A

Configuration parameters are grouped into sections. At each section, you are asked whether to change any parameters

—for example:

Values for config section - Startup

  DBName=

  DBType=

  UserId=

  UserPswd=

  ConnectId=

  ConnectPswd=

  ServerName=

  StandbyDBName=

  StandbyDBType=

  StandbyUserId=

  StandbyUserPswd=

  InMemoryDBName=

  InMemoryDBType=

Do you want to change any values (y/n)? [n]:

• Specify y to change any parameter values for the current section. You are prompted for each parameter value. Either specify a new value or press ENTER to accept the default. After you press ENTER, you are positioned at the next parameter in that section. When you are done with that section, you are again asked whether you want to re-edit any of the values you changed.

• The parameters StandbyDBName, StandbyDBType, StandbyUserID, and StandbyUserPswd are used for a standby database in an Oracle database environment.

See the information on implementing Oracle Active Data Guard in the PeopleTools: Data Management, product documentation.

• The parameters InMemoryDBName and InMemoryDBType are reserved for internal use.

• If you do not want to change any values, specify n and you are prompted for the next configuration section.

8. After you have selected all your parameters, you see this message:

You will need to shut down and start up the server to read the new⇒

 settings.

For descriptions of the Process Scheduler options in the PSADMIN, see the PeopleTools: Process Scheduler product documentation. In most cases you can accept the defaults.

Task 10A-5-3: Verifying the Process Scheduler Server Status

At this stage it is a good idea to verify the Process Scheduler Server status.

To verify the Process Scheduler Server status:

1. From the PeopleSoft Process Scheduler Administration menu, choose option 3, for Domain status menu.

--------------------------------

PeopleSoft Process Scheduler Administration

--------------------------------

Domain Name: HRDMO

1) Boot this domain

458

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Setting Up Process Scheduler on Windows

2) Domain shutdown menu

3) Domain status menu

4) Configure this domain

5) TUXEDO command line (tmadmin)

6) Edit configuration/log files menu

7) Clean IPC resources of this domain q) Quit

Command to execute (1-7, q) : 3

2. To verify the status of the Process Scheduler Server for a specific database, type the number corresponding to the appropriate database.

For example:

Database list:

  1)  HRDMO

Select item number to start: 1

Loading command line administration utility ...

tmadmin - Copyright (c) 2007-2008 Oracle.

Portions * Copyright 1986-1997 RSA Data Security, Inc.

All Rights Reserved.

Distributed under license by Oracle.

Tuxedo is a registered trademark.

> Prog Name      Queue Name  Grp Name      ID RqDone Load Done Current⇒

 Service

---------      ----------  --------      -- ------ --------- -----------⇒

----

BBL.exe        46845       PSSERVER+      0      9       450 (  IDLE )

PSMONITORSRV.e MONITOR     MONITOR        1      0         0 (  IDLE )

PSAESRV.exe    00101.00001 AESRV          1      0         0 (  IDLE )

PSAESRV.exe    00101.00002 AESRV          2      0         0 (  IDLE )

PSAESRV.exe    00101.00003 AESRV          3      0         0 (  IDLE )

PSPRCSRV.exe   SCHEDQ      BASE         101      0         0 (  IDLE )

PSMSTPRC.exe   MSTRSCHQ    BASE         102      0         0 (  IDLE )

PSDSTSRV.exe   DSTQ        BASE         103      0         0 (  IDLE )

>

You can also verify the status of the Process Scheduler Server from Process Monitor in PeopleSoft Pure Internet

Architecture. To verify the Process Scheduler Server status from the Process Monitor page, go to PeopleTools,

Process Scheduler, Process Monitor, and select Server List.

If the user has the process security rights to update the server status, the Refresh button can be used to refresh the screen, too.

See Setting Up Process Scheduler Security.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

459

Setting Up Process Scheduler on Windows

Chapter 10A

This example of the Server List page shows two Process Scheduler servers with status Down, and one with status

Running.

Process Monitor page: Server List tab

Task 10A-6: Starting Process Scheduler as a Windows Service

(Optional)

You can start the Process Scheduler server as a Windows service. This means that administrators do not need to manually boot each Process Scheduler server that runs on a Microsoft Windows machine. Instead, each time you boot the Microsoft Windows server where the Process Scheduler server resides, the Process Scheduler Server will boot automatically. You can also still manually boot Process Scheduler Servers on your Microsoft Windows server.

Note. If you have set up TUXDIR and TEMP as new SYSTEM variables, you need to reboot your machine before any Windows services will pick up the value of these environment variables.

Note. You can also set up application servers and search servers as a Windows service using the instructions provided here.

The following directions assume that the Process Scheduler is already configured on the Microsoft Windows server.

To set up the Windows Service for a Process Scheduler Server:

1. Open the System utility within the Control Panel, and set the variables, listed with a brief explanation in the following table, in the System Variables section of the Environment tab.

Note. Even if the following variables are in the User Variables section, they must also be in the System

Variables section because the Windows service will be started under the System Account.

Variable

TEMP

TUXDIR

Value

Specify the location of the TEMP directory on the

Windows server, as in C:\TEMP.

Specify the location of the Tuxedo directory on the

Windows server, as in C:\tuxedo.

2. Reboot the Windows computer if any changes or additions were made for the system variables.

3. Run the PeopleSoft PSADMIN utility (psadmin.exe in the PS_HOME\appserv directory), and press ENTER.

460

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Setting Up Process Scheduler on Windows

4. Select 6 for Service Setup from the PeopleSoft Server Administration menu.

 --------------------------------

PeopleSoft Server Administration

 --------------------------------

  PS_CFG_HOME             C:\Users\JSMITH\psftuser\psft\pt\8.55

  PS_HOME                 C:\PT8.55

  PS_APP_HOME             C:\HC9.2

  1) Application Server

  2) Process Scheduler

  3) Search Server

  4) Web (PIA) Server

  5) Switch Config Home

  6) Service Setup

  7) Replicate Config Home

  8) Refresh Config Home

  q) Quit

Command to execute (1-8, q): 6

5. Select 1 from the PeopleSoft Services Administration menu.

-------------------------------------------

PeopleSoft Services Administration

-------------------------------------------

 1) Configure Windows Service

 2) Install Windows Service

 3) Delete Windows Service

 4) Edit Service Configuration File

 q) Quit

Command to execute (1-4, q) : 1

When asked if you want to change configuration values, enter y.

6. Enter the name of the Process Scheduler databases that you intend to include as part of the Windows service.

Values for config section - NT Services

  Service Start Delay=60

  Application Server Domains=HRDMO

  Process Scheduler Databases=HRDMO

  Search Server Domains=HRDMO

Do you want to change any values (y/n)? [n]:

If you specify more than one Process Scheduler database, separate each entry with a comma.

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

461

Setting Up Process Scheduler on Windows

Chapter 10A

Note. You can use PSADMIN to set up Process Scheduler Servers, application servers, or search servers as a

Windows service. The Windows Service psntsrv.exe automatically starts application servers, Process

Scheduler servers, and search servers that reside on the same Microsoft Windows machine. Occasionally, psntsrv.exe would attempt to initiate a connection between an application server, Process Scheduler server, or search server and a database on the same machine that was not ready to receive requests. As a result the connection would fail. When you set up these servers as a Windows Service, you can specify a Service Start

Delay, in seconds, that elapses before a service attempts to start any application server domains, Process

Scheduler servers, or search servers. This allows the RDBMS to boot and become available to accept requests.

The default setting for the Service Start Delay parameter is 60 seconds.

Note. The NT Services section of the PSADMIN modifies the psntsrv.cfg file located in the PS_CFG_HOME\ appserv directory. You can edit this file manually by selecting 4, Edit Service Configuration File from the

PeopleSoft Services Administration menu. If you edit it, you need to delete and then install the service again.

7. Select option 2 from the PeopleSoft Services Administration menu.

 -------------------------------------------

PeopleSoft Services Administration

 -------------------------------------------

   1) Configure Windows Service

   2) Install Windows Service

   3) Delete Windows Service

   4) Edit Service Configuration File

   q) Quit

Command to execute (1-4, q) : 2

8. Return to the Control Panel, choose Administrative Tools, and launch the Services utility.

9. On the Services dialog, scroll to find the entry that adheres to the following naming convention, and select it:

PeopleSoft <PS_CFG_HOME>

For example:

PeopleSoft C:\Users\JSMITH\psftuser\psft\pt\8.55

Note. The default Startup mode is Manual.

10. Click Startup.

11. On the Service dialog in the Startup Type group, select Automatic, and in the Log On As group, select Local

System Account. Then click OK.

Note. The Log On As setting needs to reflect that which you set for your ORACLE ProcMGR

V12.1.3.0.0_VS2012 and Tlisten processes. Oracle recommends that you set these services to Local System

Account when you install Tuxedo. The Log On As value only affects the application server because Process

Scheduler runs independently from Tuxedo. See the chapter "Installing Additional Components" for more information on installing Tuxedo, and refer to the chapter "Configuring the Application Server on Windows" for the details on configuring the application server.

12. On the Services dialog, make sure the PeopleSoft service is selected, and click Start.

13. Use the Process Monitor to verify that the Process Scheduler Server is running. You can also use Task

Manager to verify that the executables involved with the service are running.

462

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Setting Up Process Scheduler on Windows

For the Process Scheduler, make sure that the psprcsrv.exe is running. If you have customized the name of psprcsrv.exe, make sure the appropriate executable is running.

Task 10A-7: Configuring the Process Scheduler for Microsoft

Word (Optional)

This section discusses:

• Configuring Process Scheduler

• Executing Winword on Mapped Drive

Task 10A-7-1: Configuring Process Scheduler

Some applications process documents using Microsoft Word. Here is how to configure Microsoft Word to work with the Process Scheduler.

Note. Microsoft Word must already be installed on the server; it is not included with the PeopleSoft PeopleTools install.

To configure Process Scheduler for Microsoft Word:

1. Log in to the PeopleSoft application in a browser and select PeopleTools, Process Scheduler, Processes.

2. Search for Process Type Winword and select a process.

3. On the Process Definition page, select Override Options, as shown in this example.

Process Definition page: Override Options

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

463

Setting Up Process Scheduler on Windows

Chapter 10A

4. In the Parameter List field, enter %%PS_HOME%%\WINWORD\WORDSAMP.DOCX/mWORDSAMP and save.

5. Locate the Process Scheduler configuration file psprcs.cfg in PS_CFG_HOME\appserv\prcs\

<database_name> directory and open it for editing.

6. In the [Process Scheduler] section, edit the WINWORD entry so that it points to the directory where winword.exe is installed

—for example, "WINWORD=C:\Program Files\Microsoft Office\OFFICE 12"

(include the quotes in the entry).

7. If spaces exist in the WINWORD path in the Process Scheduler configuration file (psprcs.cfg), Microsoft

Word reports will fail. You will need to modify the Process Type Definition and add quotes around the entry in the Command Line field, for example " %%WINWORD%%\winword.exe".

8. Change the Microsoft Word macro security to allow macros to be run.

Start Microsoft Word and select Tools, Macro, Security. Select the Low security setting and click OK.

9. If you are running on Microsoft Windows 2008, modify your macros to include the following line:

Application.AutomationSecurity=msoAutomationSecurityLow

You can see an example by viewing the macros in PS_HOME\winword\Wordsamp.doc.

10. Make sure that all the servers (that is, Application Server and Process Scheduler servers) are running in the context of the logged-in user, as WinWord is executed in the same context.

Task 10A-7-2: Executing Winword on Mapped Drive

If you encounter a problem in executing the WinWord process on a mapped drive, there are a couple of solutions to try. If the first solution does not work, try the second one. Try the following workaround suggestions in the order given.

To perform the first workaround:

1. Copy the file WORDSAMP.dotm from PS_HOME\WINWORD\.

2. Locate the WinWord templates folder and place the file WORDSAMP.dotm there.

In general, you can find the templates folder under the logged-in user's directory. For example, for user psftuser, this would be:

C:\Users\psftuser\Microsoft\Templates

3. Open the WinWord.docx file under PS_HOME\WINWORD folder and verify macro is present.

4. Sign in to the PeopleSoft application to execute the WinWord process and verify its status in Process Monitor.

To perform the second workaround:

1. In Microsoft Word, click the Microsoft Office button, and click Word Options.

2. Select Trust Center, and then click Trust Center Settings, Trusted Locations.

3. Select the check box for Allow Trusted Locations on my network, and clear the check box Disable all Trusted

Locations.

464

Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.

Chapter 10A

Setting Up Process Scheduler on Windows

4. Create a new trusted location with path pointing to the PS_HOME\WINWORD folder on your mapped drive.

In this example, the trusted location is \\server1\pt854\WINWORD:

Microsoft Word Trusted Locations window

Task 10A-8: Configuring Setup Manager

Before you can use Setup Manager, you must fulfill these requirements:

• To use the Excel to CI template-generation feature of Setup manager, the Process Scheduler must be PSNT.

That is, Process Scheduler must be installed on a Microsoft Windows machine.

• Process Scheduler must be running.

• Any Process Scheduler environment variables (especia