PeopleTools 8.55 Installation for DB2 for z/OS

PeopleTools 8.55 Installation for DB2
for z/OS
December 2015
PeopleTools 8.55 Installation for DB2 for z/OS
SKU itdb2zOS_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 .................................................................................................................................
Understanding This Documentation ......................................................................................................................
Audience ................................................................................................................................................................
Typographical Conventions ...................................................................................................................................
Products ..................................................................................................................................................................
Related Information ...............................................................................................................................................
Comments and Suggestions ...................................................................................................................................
23
23
23
24
25
26
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 .................................................................................................................................. 38
Using Laser Printers .......................................................................................................................................... 38
Planning Database Creation ................................................................................................................................... 38
Understanding Database Creation ..................................................................................................................... 39
Using Multiple Databases ................................................................................................................................. 39
Determining Databases and Database Names ................................................................................................... 39
Using Standard Database Names ...................................................................................................................... 40
Choosing Owner ID Processing Option ............................................................................................................ 40
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
5
Contents
Planning Multilingual Strategy .............................................................................................................................. 42
Understanding Multilingual Issues ................................................................................................................... 43
Choosing a Base Language ............................................................................................................................... 44
Selecting Additional Languages ....................................................................................................................... 46
Selecting a Database Character Set ................................................................................................................... 46
Preparing for the PeopleTools-Only Upgrade ........................................................................................................ 47
Understanding the PeopleTools Only Upgrade ................................................................................................ 47
Reviewing the Upgrade Documentation ........................................................................................................... 47
Shutting Down Servers ..................................................................................................................................... 47
Reviewing Customized Configuration Files ..................................................................................................... 48
Reviewing Patches and Updates Required at Installation ...................................................................................... 48
Verifying Database Server Sizing .......................................................................................................................... 49
Defining DB2 for z/OS Subsystem Configuration ................................................................................................. 49
Understanding DB2 Configuration Requirements ............................................................................................ 50
Defining EDM Pool Considerations ................................................................................................................. 50
Defining Decimal Arithmetic ........................................................................................................................... 50
Using DSMAX .................................................................................................................................................. 51
Using CMTSTAT/IDTHTOIN ......................................................................................................................... 51
Using CCSID and DB2 z/OS Database Storage Encoding Schemes ............................................................... 51
Using DECIMAL .............................................................................................................................................. 51
Installing Supporting Applications ........................................................................................................................ 52
Setting Up Database Connectivity ......................................................................................................................... 53
Using Connect ID ................................................................................................................................................... 54
Understanding Connect ID ............................................................................................................................... 54
Using Connect ID ............................................................................................................................................. 54
Setting Up z/OS User IDs ...................................................................................................................................... 56
Understanding User ID Setup ........................................................................................................................... 56
Creating PeopleSoft User IDs ........................................................................................................................... 56
Performing Backups ............................................................................................................................................... 59
Using PeopleSoft Change Assistant and PeopleSoft Change Impact Analyzer .................................................... 59
Chapter 2
Installing Web Server Products .......................................................................................................................... 61
Installing Oracle WebLogic Server ........................................................................................................................ 61
Understanding the Oracle WebLogic Installation ............................................................................................. 61
Reviewing Troubleshooting Tips ...................................................................................................................... 62
Obtaining Oracle WebLogic Installation Files from Oracle Software Delivery Cloud .................................... 63
Installing JDK for Oracle WebLogic ................................................................................................................ 64
Installing Oracle WebLogic on Microsoft Windows ........................................................................................ 67
Installing Oracle WebLogic on Linux or UNIX in Silent Mode ...................................................................... 76
Configuring JDK for Daylight Savings Time Change ...................................................................................... 79
6
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Contents
Removing the Oracle WebLogic Installation on Microsoft Windows ............................................................. 80
Removing the Oracle WebLogic Installation on Linux or UNIX ..................................................................... 83
Installing IBM WebSphere Application Server ..................................................................................................... 84
Understanding IBM WebSphere Installation .................................................................................................... 84
Prerequisites ...................................................................................................................................................... 85
Obtaining IBM WebSphere Installation Files ................................................................................................... 86
Installing IBM WebSphere 8.5.5.0 ND ............................................................................................................ 89
Installing IBM HTTP Server 8.5.5.0 ................................................................................................................ 89
Installing IBM WebSphere Plug-ins 8.5.5.0 ..................................................................................................... 89
Chapter 3
Installing Additional Components ...................................................................................................................... 91
Reviewing Additional Components ....................................................................................................................... 91
Installing Oracle Tuxedo ........................................................................................................................................ 92
Understanding Oracle Tuxedo .......................................................................................................................... 92
Prerequisites ...................................................................................................................................................... 93
Debugging the Oracle Tuxedo Installer ............................................................................................................ 94
Obtaining the Oracle Tuxedo Installation Files from Oracle Software Delivery Cloud .................................. 94
Obtaining the Oracle Tuxedo Patches from My Oracle Support ...................................................................... 95
Removing Existing Oracle Tuxedo Installations from Microsoft Windows (Optional) ................................... 96
Designating the Application Server Administrator on Microsoft Windows .................................................... 97
Installing Oracle Tuxedo on Microsoft Windows in GUI Mode ...................................................................... 98
Installing the Oracle Tuxedo Patch on Microsoft Windows ........................................................................... 109
Installing Oracle Tuxedo on Microsoft Windows in Silent Mode .................................................................. 110
Uninstalling the Oracle Tuxedo Patch on Microsoft Windows ...................................................................... 112
Uninstalling Oracle Tuxedo in GUI Mode ..................................................................................................... 112
Checking the Windows Service Account ....................................................................................................... 114
Restricting Domain Process Privileges ........................................................................................................... 115
Setting Up the Windows Services for Oracle Tuxedo .................................................................................... 116
Verifying the Server Installation on Microsoft Windows ............................................................................... 118
Removing Existing Oracle Tuxedo Installations from UNIX (Optional) ....................................................... 119
Completing the Preinstallation Checklist on UNIX ........................................................................................ 119
Designating the Oracle Tuxedo Owner on UNIX ........................................................................................... 120
Installing Oracle Tuxedo in Silent Mode on UNIX ........................................................................................ 121
Installing the Oracle Tuxedo Patch on UNIX ................................................................................................. 122
Uninstalling the Oracle Tuxedo Patch from UNIX ........................................................................................ 123
Uninstalling Oracle Tuxedo from UNIX Using Silent Mode ......................................................................... 123
Verifying the Server Installation on UNIX ..................................................................................................... 124
Ensuring that Oracle Tuxedo Coexists with Earlier Versions ........................................................................ 124
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
7
Contents
Chapter 4
Using the PeopleSoft Installer ........................................................................................................................... 127
Understanding the PeopleSoft Installer ................................................................................................................ 127
Defining the PeopleSoft Installer .................................................................................................................... 127
Defining Supported Server Combinations ...................................................................................................... 128
Obtaining License Codes ................................................................................................................................ 129
Prerequisites ......................................................................................................................................................... 129
Obtaining the PeopleSoft Installation Files from Oracle Software Delivery Cloud ............................................ 130
Running the PeopleSoft Installer ......................................................................................................................... 131
Understanding the PeopleSoft Installer .......................................................................................................... 132
Starting the PeopleSoft Installer ..................................................................................................................... 132
Installing PeopleSoft PeopleTools in GUI Mode ........................................................................................... 134
Installing PeopleSoft PeopleTools in Console Mode ..................................................................................... 147
Verifying Necessary Files for Installation on Windows ...................................................................................... 151
Installing PeopleSoft Application Software ......................................................................................................... 152
Installing the Multilanguage Files ........................................................................................................................ 152
Installing the PeopleTools Client Files ................................................................................................................ 152
Installing the PeopleTools Client Files Using the PeopleSoft Installer .......................................................... 153
Installing the PeopleTools Client Files in Silent Mode .................................................................................. 153
Binding Windows "SQR for PeopleSoft" DB2 Connect Packages ...................................................................... 154
Mapping a Drive on the Install Workstation ........................................................................................................ 155
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 6
Setting Up the Batch Environment on z/OS .................................................................................................... 163
Understanding COBOL and the Batch Environment ........................................................................................... 163
Setting Up Your Batch Environment ................................................................................................................... 164
Completing the Preinstallation Worksheet ........................................................................................................... 164
Allocating z/OS Partitioned Datasets ................................................................................................................... 171
Using PeopleSoft Server Transfer ........................................................................................................................ 171
8
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Contents
Understanding PeopleSoft Server Transfer .................................................................................................... 172
Running the PeopleSoft Server Transfer Program .......................................................................................... 172
Transferring Files to Host Manually ............................................................................................................... 175
Mapping PeopleSoft Installation Directories to z/OS ..................................................................................... 175
Setting up the USS Environment Variables and Granting Access to USS Files ................................................. 177
Installing SQR for z/OS ....................................................................................................................................... 177
Binding the SQR DB2 Plan .................................................................................................................................. 178
Assembling PeopleTools Programs ..................................................................................................................... 178
Compiling and Link-Editing DB2 COBOL ......................................................................................................... 178
Compiling and Link-Editing COBOL .................................................................................................................. 179
Changing the IBM Enterprise COBOL Compiler Version .................................................................................. 179
Chapter 7
Creating a Database ........................................................................................................................................... 181
Understanding Database Creation ........................................................................................................................ 182
Planning Your Installation ................................................................................................................................... 182
Using %UpdateStats ....................................................................................................................................... 182
Using Temporary Tables ................................................................................................................................. 183
Transferring DDL Scripts to z/OS ....................................................................................................................... 184
Creating PS.PSDBOWNER Table ....................................................................................................................... 185
Granting Privileges on PS.PSDBOWNER .......................................................................................................... 186
Granting Privileges to Owner ID ........................................................................................................................ 186
Creating DB2 Databases, Storage Groups, and Tablespaces ............................................................................... 186
Understanding DB2 Databases, Storage Groups, and Tablespaces ................................................................ 186
Customizing the Database Name .................................................................................................................... 187
Working with Tablespaces .............................................................................................................................. 189
Creating Tables .................................................................................................................................................... 192
Configuring the DB2 Connect Gateway .............................................................................................................. 193
Creating Data Mover Import Scripts .................................................................................................................... 193
Understanding Data Mover Import Scripts ..................................................................................................... 193
Working with Multilingual Databases ............................................................................................................ 194
Running Database Setup to Create Data Mover Import Scripts ..................................................................... 194
Running Data Mover Import Scripts .................................................................................................................... 201
Understanding Data Mover Import Scripts ..................................................................................................... 201
Populating Tables in the PeopleSoft Database ............................................................................................... 202
Checking the Log Files and Troubleshooting ...................................................................................................... 202
Checking the Log Files ................................................................................................................................... 203
Running Data Mover ....................................................................................................................................... 203
Troubleshooting .............................................................................................................................................. 203
Improving Performance .................................................................................................................................. 205
Improving Execution ...................................................................................................................................... 205
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
9
Contents
Creating Indexes ................................................................................................................................................... 206
Reviewing Patch Application ............................................................................................................................... 207
Updating Database to Latest PeopleTools Release .............................................................................................. 207
Understanding Database Updates ................................................................................................................... 208
Cleaning Up Data ............................................................................................................................................ 208
Deleting Performance Monitor System Default Data ..................................................................................... 209
Creating New PeopleTools Tablespaces ......................................................................................................... 209
Updating PeopleTools System Tables ............................................................................................................ 209
Updating PeopleTools Database Objects ........................................................................................................ 212
Updating PeopleTools Multilingual Objects .................................................................................................. 215
Deleting Obsolete PeopleTools Database Objects .......................................................................................... 218
Applying Patched PeopleTools Database Objects .......................................................................................... 220
Altering PeopleTools Tables ........................................................................................................................... 221
Migrating Records to New Tablespaces ......................................................................................................... 224
Updating PeopleTools System Data ............................................................................................................... 230
Running PeopleTools Conversions ................................................................................................................. 233
Converting Integration Broker ........................................................................................................................ 238
Running Additional PeopleTools Conversions ............................................................................................... 241
Running the DB2 RUNSTATS Utility ................................................................................................................ 241
Creating PeopleSoft Views .................................................................................................................................. 241
Understanding PeopleSoft Views ................................................................................................................... 241
Creating Views in Data Mover ....................................................................................................................... 241
Creating Views in Application Designer ........................................................................................................ 242
Building Temporary Tables ................................................................................................................................. 244
Understanding Temporary Tables ................................................................................................................... 245
Running SQR SETSPACE.SQR ..................................................................................................................... 245
Correcting Invalid Database/Tablespace Combinations ................................................................................. 246
Setting the Number of Temporary Tables ...................................................................................................... 247
Using the Volatile Table Attribute .................................................................................................................. 247
Building the Temporary Tables and Their Indexes ........................................................................................ 248
Creating PeopleSoft Triggers ............................................................................................................................... 251
Understanding PeopleSoft Triggers ................................................................................................................ 251
Creating Triggers in Data Mover .................................................................................................................... 251
Creating Triggers in Application Designer ..................................................................................................... 251
Running Additional Data Mover Scripts .............................................................................................................. 254
Installing a Multilingual PeopleTools System Database ..................................................................................... 255
Understanding the Multilingual Database Project .......................................................................................... 255
Applying the Multilingual Database Project ................................................................................................... 255
Populating the Translated System Data .......................................................................................................... 255
Running SQR Reports .......................................................................................................................................... 256
Understanding Running SQR Reports ............................................................................................................ 256
Binding the dbcalls.bnd .................................................................................................................................. 256
10
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Contents
Running SQRs on the Client Workstation ...................................................................................................... 257
Creating a Shortcut to Run SQRs ................................................................................................................... 259
Updating PeopleSoft System Tables .................................................................................................................... 260
Understanding PeopleSoft System Tables ...................................................................................................... 260
Updating PeopleSoft System Tables ............................................................................................................... 260
Binding DB2 Plans ............................................................................................................................................... 260
Running VERSION Application Engine Program ............................................................................................... 261
Changing the Base Language ............................................................................................................................... 261
Checking the Database ......................................................................................................................................... 261
Running Alter Audit ............................................................................................................................................. 262
Disabling %UpdateStats ....................................................................................................................................... 267
Chapter 8A
Configuring the Application Server on Windows ........................................................................................... 269
Understanding the Application Server ................................................................................................................. 269
Prerequisites ......................................................................................................................................................... 270
Preparing the Application Server File System for a PeopleTools-Only Upgrade ............................................... 271
Setting Up COBOL for Remote Call ................................................................................................................... 271
Verifying Database Connectivity ......................................................................................................................... 271
Creating, Configuring, and Starting an Initial Application Server Domain ........................................................ 271
Creating, Configuring, and Starting the Application Server Domain ............................................................. 272
Testing the Three-Tier Connection ................................................................................................................. 275
Importing an Existing Application Server Domain Configuration ................................................................. 277
Setting Up a Custom Application Server Domain Configuration .................................................................. 279
Troubleshooting Common Errors ................................................................................................................... 282
Chapter 8B
Configuring the Application Server on UNIX ................................................................................................. 283
Understanding the Application Server ................................................................................................................. 283
Understanding the Application Server Domain Processes ................................................................................... 284
Prerequisites ......................................................................................................................................................... 284
Preparing the Application Server File System for a PeopleTools-Only Upgrade ............................................... 285
Setting Environment Variables ............................................................................................................................ 285
Setting Up COBOL for Remote Call ................................................................................................................... 286
Verifying Database Connectivity ......................................................................................................................... 286
Creating, Configuring, and Starting an Initial Application Server Domain ........................................................ 286
Creating, Configuring, and Starting the Application Server Domain ............................................................. 286
Testing the Three-Tier Connection ................................................................................................................. 290
Importing an Existing Application Server Domain Configuration ................................................................. 291
Setting Up a Custom Application Server Domain Configuration .................................................................. 294
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
11
Contents
Troubleshooting Common Errors ................................................................................................................... 296
Chapter 9A
Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode ........................................................... 297
Understanding PeopleSoft Pure Internet Architecture ......................................................................................... 297
Using Authentication Domains in the PeopleSoft Pure Internet Architecture Installation .................................. 299
Preparing the PeopleSoft Pure Internet Architecture File System for a PeopleTools-Only Upgrade ................. 300
Installing the PeopleSoft Pure Internet Architecture on Oracle WebLogic in GUI Mode .................................. 300
Prerequisites .................................................................................................................................................... 301
Installing the PeopleSoft Pure Internet Architecture on a New Oracle WebLogic Domain .......................... 301
Installing the PeopleSoft Pure Internet Architecture on an Existing Oracle WebLogic Domain ................... 316
Uninstalling the PeopleSoft Pure Internet Architecture on Oracle WebLogic ............................................... 334
Installing the PeopleSoft Pure Internet Architecture on IBM WebSphere in GUI Mode .................................... 334
Prerequisites .................................................................................................................................................... 335
Installing the PeopleSoft Pure Internet Architecture on IBM WebSphere ..................................................... 335
Uninstalling the PeopleSoft Pure Internet Architecture from IBM WebSphere ............................................. 353
Testing and Administering the PeopleSoft Pure Internet Architecture Installation ............................................. 354
Verifying the PeopleSoft Pure Internet Architecture Installation ................................................................... 354
Starting and Stopping Oracle WebLogic ........................................................................................................ 355
Starting and Stopping IBM WebSphere Application Servers ......................................................................... 356
Using PSADMIN to Start and Stop Web Servers ........................................................................................... 359
Accessing the PeopleSoft Signon ................................................................................................................... 361
Completing Post-Installation Steps ...................................................................................................................... 364
Using Fluid User Interface .............................................................................................................................. 364
Updating the Installation Table ....................................................................................................................... 367
Setting Options for Multilingual Databases .................................................................................................... 368
Updating PeopleTools Options ....................................................................................................................... 369
Updating Database Information ...................................................................................................................... 369
Chapter 9B
Setting Up the PeopleSoft Pure Internet Architecture in Console Mode ..................................................... 371
Understanding PeopleSoft Pure Internet Architecture ......................................................................................... 371
Using Authentication Domains in the PeopleSoft Pure Internet Architecture Installation .................................. 373
Preparing the PeopleSoft Pure Internet Architecture File System for a PeopleTools-Only Upgrade ................. 374
Installing the PeopleSoft Pure Internet Architecture on Oracle WebLogic in Console Mode ............................ 374
Prerequisites .................................................................................................................................................... 375
Installing the PeopleSoft Pure Internet Architecture on a New Oracle WebLogic Domain in Console Mode .
375
Installing the PeopleSoft Pure Internet Architecture on an Existing Oracle WebLogic Domain in Console
Mode ............................................................................................................................................................... 380
Uninstalling the PeopleSoft Pure Internet Architecture from Oracle WebLogic ........................................... 386
12
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Contents
Installing the PeopleSoft Pure Internet Architecture on IBM WebSphere in Console Mode .............................. 386
Prerequisites .................................................................................................................................................... 386
Installing the PeopleSoft Pure Internet Architecture on IBM WebSphere Application Server ND ............... 387
Uninstalling the PeopleSoft Pure Internet Architecture from IBM WebSphere ............................................ 391
Installing the PeopleSoft Pure Internet Architecture in Silent Mode ................................................................... 392
Understanding the Silent Installation and the Response File .......................................................................... 392
Editing the Response File ............................................................................................................................... 392
Running the Silent Mode Installation ............................................................................................................. 395
Testing and Administering the PeopleSoft Pure Internet Architecture Installation ............................................. 395
Verifying the PeopleSoft Pure Internet Architecture Installation ................................................................... 395
Starting and Stopping Oracle WebLogic ........................................................................................................ 396
Starting and Stopping IBM WebSphere Application Servers ......................................................................... 396
Using PSADMIN to Start and Stop Web Servers ........................................................................................... 399
Accessing the PeopleSoft Signon ................................................................................................................... 401
Completing Post-Installation Steps ...................................................................................................................... 404
Using Fluid User Interface .............................................................................................................................. 404
Updating the Installation Table ....................................................................................................................... 407
Setting Options for Multilingual Databases .................................................................................................... 408
Updating PeopleTools Options ....................................................................................................................... 409
Updating Database Information ...................................................................................................................... 409
Chapter 10A
Setting Up Process Scheduler on Windows ..................................................................................................... 411
Prerequisites ......................................................................................................................................................... 411
Preparing the Process Scheduler File System for a PeopleTools-Only Upgrade ................................................. 412
Setting Up Process Scheduler Security ................................................................................................................ 412
Understanding Process Scheduler Security .................................................................................................... 412
Changing User Account to Start ORACLE ProcMGR V12.1.3.0.0_VS2012 ................................................ 413
Granting Process Scheduler Administrative Rights ........................................................................................ 415
Setting Up Process Scheduler to Transfer Reports and Logs to the Report Repository ...................................... 416
Understanding Report Distribution ................................................................................................................. 417
Setting Up Single Signon to Navigate from PIA to Report Repository ......................................................... 419
Determining the Transfer Protocol ................................................................................................................. 419
Starting the Distribution Agent ....................................................................................................................... 420
Setting Up the Report Repository ................................................................................................................... 420
Setting Up the Distribution for Your Process Scheduler Server ..................................................................... 437
Setting Up Sending and Receiving of Report Folders in the Report Manager ............................................... 438
Setting Environment Variables ............................................................................................................................ 438
Setting Up Process Scheduler Server Agent ........................................................................................................ 438
Understanding Process Scheduler Server Agent ............................................................................................. 439
Creating and Configuring a Process Scheduler Server ................................................................................... 439
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
13
Contents
Reconfiguring a Process Scheduler Server ..................................................................................................... 444
Verifying the Process Scheduler Server Status ............................................................................................... 446
Starting Process Scheduler as a Windows Service (Optional) ............................................................................. 447
Configuring the Process Scheduler for Microsoft Word (Optional) .................................................................... 450
Configuring Process Scheduler ....................................................................................................................... 450
Executing Winword on Mapped Drive ........................................................................................................... 452
Configuring Setup Manager ................................................................................................................................. 453
Installing Products for PS/nVision ....................................................................................................................... 454
Understanding the PS/nVision Setup .............................................................................................................. 455
Installing Products for PS/nVision in Excel Automation Mode ..................................................................... 455
Installing Microsoft .NET Framework Products for PS/nVision .................................................................... 455
Installing Microsoft Open XML SDK for PS/nVision ................................................................................... 463
Chapter 10B
Setting Up Process Scheduler on UNIX ........................................................................................................... 469
Prerequisites ......................................................................................................................................................... 469
Preparing the Process Scheduler File System for a PeopleTools-Only Upgrade ................................................. 470
Setting Up Process Scheduler Security ................................................................................................................ 470
Understanding Process Scheduler Security .................................................................................................... 470
Granting Process Scheduler Administrative Rights ........................................................................................ 470
Setting Up Process Scheduler to Transfer Reports and Logs to the Report Repository ...................................... 471
Understanding Report Distribution ................................................................................................................. 472
Setting Up Single Signon to Navigate from PIA to Report Repository ......................................................... 474
Determining the Transfer Protocol ................................................................................................................. 474
Starting the Distribution Agent ....................................................................................................................... 475
Setting Up the Report Repository ................................................................................................................... 475
Setting Up the Distribution for Your Process Scheduler Server ..................................................................... 490
Setting Up Sending and Receiving of Report Folders in the Report Manager ............................................... 491
Setting Up Process Scheduler Server Agent ........................................................................................................ 491
Understanding Process Scheduler Server Agent ............................................................................................. 491
Changing the Default Operating System ........................................................................................................ 492
Creating and Configuring a Process Scheduler Server ................................................................................... 492
Reconfiguring a Process Scheduler Server ..................................................................................................... 497
Verifying the Process Scheduler Server Status ............................................................................................... 499
Chapter 10C
Setting Up Process Scheduler on z/OS ............................................................................................................. 501
Prerequisites ......................................................................................................................................................... 501
Preparing the Process Scheduler File System for a PeopleTools-Only Upgrade ................................................. 502
Granting Required Authorization in DB2 and UNIX System Services ............................................................... 502
14
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Contents
Setting UNIX System Services Authorization ................................................................................................ 503
Setting DB2 Authorization ............................................................................................................................. 504
Setting Up Process Scheduler Security ................................................................................................................ 505
Understanding Process Scheduler Security .................................................................................................... 505
Granting Process Scheduler Administrative Rights ........................................................................................ 505
Setting Up Process Scheduler to Transfer Reports and Logs to the Report Repository ...................................... 506
Understanding Report Distribution ................................................................................................................. 507
Setting Up Single Signon to Navigate from PIA to Report Repository ......................................................... 509
Determining the Transfer Protocol ................................................................................................................. 509
Starting the Distribution Agent ....................................................................................................................... 510
Setting Up the Report Repository ................................................................................................................... 510
Setting Up the Distribution for Your Process Scheduler Server ..................................................................... 520
Setting Up Sending and Receiving of Report Folders in the Report Manager ............................................... 521
Setting Up Process Scheduler Server Agent ........................................................................................................ 521
Understanding Process Scheduler Server Agent ............................................................................................. 522
Changing the Default Operating System ........................................................................................................ 522
Setting Up Your Environment ........................................................................................................................ 522
Validating and Editing the ODBC Initialization File ..................................................................................... 523
Creating a Process Scheduler Server .............................................................................................................. 523
Configuring Process Scheduler Server ........................................................................................................... 524
Working with Shell JCL Templates ................................................................................................................ 529
Starting a Process Scheduler Server ............................................................................................................... 535
Verifying the Process Scheduler Server Status ............................................................................................... 536
Stopping the Process Scheduler Server ........................................................................................................... 536
Part II .................................................................................................................................................................. 539
Discretionary Installation ..................................................................................................................................... 539
Chapter 11
Configuring Integration Between PeopleSoft PeopleTools and Oracle SES ................................................ 541
Understanding PeopleSoft PeopleTools and SES Integration ............................................................................. 541
Preparing for the Integration of PeopleSoft PeopleTools and SES ...................................................................... 542
Installing Oracle Secure Enterprise Search ..................................................................................................... 542
Reviewing the PeopleSoft PeopleTools Prerequisites .................................................................................... 542
Configuring SES for the Search Framework ....................................................................................................... 543
Understanding the Oracle SES Configuration ................................................................................................ 543
Creating a Federated Trusted Entity ............................................................................................................... 543
Activating the Identity Plug-in ........................................................................................................................ 544
Configuring SES Authentication Timeout Settings ........................................................................................ 544
Enabling Character Set Detection ................................................................................................................... 545
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
15
Contents
Activating the Document Service Plugin ........................................................................................................ 545
Using a Proxy with Oracle SES ...................................................................................................................... 545
Setting Up the PeopleSoft Application Server for the Search Framework .......................................................... 546
Setting Up Search Framework User IDs .............................................................................................................. 546
Using the Search Administration Activity Guide ................................................................................................ 547
Understanding the Search Administration Activity Guide ............................................................................. 547
Setting Up the Local Nodes ............................................................................................................................ 547
Specifying the Integration Gateway ................................................................................................................ 552
Verifying the Service Configuration ............................................................................................................... 555
Defining a Search Instance in the PeopleSoft System .................................................................................... 556
Verifying PeopleSoft PeopleTools and SES Connectivity .................................................................................. 560
Chapter 12
Installing the Verity Integration Kit ................................................................................................................
Understanding the Verity Installation ..................................................................................................................
Installing the Verity Integration Kit in GUI Mode ..............................................................................................
Installing the Verity Integration Kit in Console Mode ........................................................................................
563
563
563
568
Chapter 13A
Installing and Compiling COBOL on Windows ............................................................................................. 571
Understanding COBOL ........................................................................................................................................ 571
Prerequisites ......................................................................................................................................................... 572
Preparing COBOL for a PeopleTools-only Upgrade ........................................................................................... 572
Installing Micro Focus Net Express on Microsoft Windows ............................................................................... 572
Prerequisites .................................................................................................................................................... 572
Obtaining Installation Files for Micro Focus Net Express from Oracle Software Delivery Cloud ................ 573
Installing Micro Focus Net Express Wrap Pack 6 .......................................................................................... 573
Installing Micro Focus Net Express Wrap Pack 11 ........................................................................................ 585
Managing Micro Focus Net Express Compiler Licenses ..................................................................................... 590
Understanding Micro Focus Net Express Compiler Licenses ........................................................................ 590
Configuring a Full License with the License Server ...................................................................................... 591
Configuring a Timed License with the License Server .................................................................................. 601
Revoking the License Using the License Management System ..................................................................... 608
Revoking the License by Removing the Installation ...................................................................................... 610
Using the Micro Focus COBOL Compiler on Microsoft Windows .................................................................... 612
Understanding COBOL Compilation ............................................................................................................. 613
Compiling COBOL on Microsoft Windows with a PS_HOME Setup ........................................................... 613
Compiling COBOL on Microsoft Windows with a PS_CUST_HOME Setup .............................................. 617
Recompiling COBOL on Microsoft Windows ............................................................................................... 622
Setting Up the Micro Focus Net Express Runtime ......................................................................................... 622
16
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Contents
Defining the GNT and INT Files .................................................................................................................... 624
Distributing COBOL Binaries ........................................................................................................................ 625
Chapter 13B
Installing and Compiling COBOL on UNIX ................................................................................................... 627
Understanding COBOL ........................................................................................................................................ 627
Prerequisites ......................................................................................................................................................... 628
Preparing COBOL for a PeopleTools-only Upgrade ........................................................................................... 628
Installing Micro Focus Server Express for UNIX and Linux .............................................................................. 628
Understanding Micro Focus Server Express ................................................................................................... 628
Prerequisites .................................................................................................................................................... 629
Obtaining the Installation Files for Micro Focus Server Express from Oracle Software Delivery Cloud ..... 629
Installing Micro Focus Server Express ........................................................................................................... 630
Using the Micro Focus COBOL Compiler on UNIX .......................................................................................... 635
Understanding COBOL Compilation ............................................................................................................. 636
Modifying the Liblist64 File (IBM AIX) ........................................................................................................ 636
Modifying the Cobopt File (SuSE Linux Enterprise Server Only) ................................................................. 637
Compiling COBOL on UNIX with a PS_HOME Setup ................................................................................. 637
Compiling COBOL on UNIX with a PS_CUST_HOME Setup .................................................................... 638
Linking COBOL ............................................................................................................................................. 639
Recompiling COBOL on UNIX ..................................................................................................................... 640
Installing IBM COBOL on IBM AIX .................................................................................................................. 640
Understanding the IBM COBOL for AIX Installation ................................................................................... 640
Prerequisites .................................................................................................................................................... 641
Installing IBM COBOL for AIX v4.1.1.1 ....................................................................................................... 641
Using the IBM COBOL Compiler on IBM AIX ................................................................................................. 643
Setting Environment Variables for IBM COBOL .......................................................................................... 643
Compiling COBOL on AIX with a PS_HOME Setup .................................................................................... 644
Troubleshooting the IBM COBOL Compiler ................................................................................................. 645
Setting Up the IBM COBOL Runtime ............................................................................................................ 649
Removing the IBM COBOL Installation ........................................................................................................ 653
Chapter 14
Installing PeopleSoft Change Assistant ............................................................................................................ 657
Understanding PeopleSoft Change Assistant ....................................................................................................... 657
Removing or Upgrading PeopleSoft Change Assistant Installations ................................................................... 658
Removing PeopleSoft Change Assistant Installations from Previous Releases ............................................. 658
Removing PeopleSoft Change Assistant Instances in the Current Release .................................................... 658
Upgrading PeopleSoft Change Assistant Instances ........................................................................................ 662
Installing PeopleSoft Change Assistant in GUI Mode ......................................................................................... 666
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
17
Contents
Installing PeopleSoft Change Assistant in Silent Mode ...................................................................................... 672
Understanding Silent Mode for PeopleSoft Change Assistant ....................................................................... 673
Using the Silent Mode Script .......................................................................................................................... 673
Configuring and Using PeopleSoft Change Assistant ......................................................................................... 674
Verifying the Path Variable ............................................................................................................................ 674
Specifying Options .......................................................................................................................................... 674
Scanning the Workstation ............................................................................................................................... 675
Exporting Jobs to XML, HTML, or Microsoft Excel Format ........................................................................ 675
Validating Change Assistant Settings .................................................................................................................. 675
Chapter 15
Installing PeopleSoft Change Impact Analyzer .............................................................................................. 679
Prerequisites ......................................................................................................................................................... 679
Removing PeopleSoft Change Impact Analyzer Installations ............................................................................. 679
Installing PeopleSoft Change Impact Analyzer ................................................................................................... 682
Installing and Removing PeopleSoft Change Impact Analyzer in Silent Mode .................................................. 688
Understanding Silent Mode for PeopleSoft Change Impact Analyzer ........................................................... 688
Installing PeopleSoft Change Impact Analyzer in Silent Mode ..................................................................... 689
Removing the PeopleSoft Change Impact Analyzer Installation in Silent Mode ........................................... 690
Removing and Installing PeopleSoft Change Impact Analyzer in Silent Mode ............................................. 690
Chapter 16
Adding New Product Modules .......................................................................................................................... 693
Adding New Modules to PeopleSoft 8.4 Installations ......................................................................................... 693
Chapter 17
Installing and Configuring DB2 Connect ........................................................................................................ 695
Understanding DB2 Connect ............................................................................................................................... 695
Verifying Supported Versions .............................................................................................................................. 696
Defining DB2 Connect Architecture .................................................................................................................... 696
Understanding DB2 Connect Architecture ..................................................................................................... 696
Using DB2 Connect Enterprise Edition .......................................................................................................... 697
Using DB2 Connect Personal Edition ............................................................................................................. 698
Defining PeopleSoft Three-Tier Configuration with DB2 Connect ............................................................... 698
Setting Up DDF on the Mainframe ...................................................................................................................... 699
Configuring TCP/IP on the Client ........................................................................................................................ 700
Configuring the DB2 Connect Gateway on Windows ......................................................................................... 701
Configuring Database Connectivity on Clients with DB2 Connect Version 9.x or Earlier ........................... 702
Configuring Database Connectivity on Clients with DB2 Connect Version 10.x or Later ............................ 712
18
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Contents
Configuring an ODBC Data Source for Connectivity on Microsoft Windows (Optional) ............................ 713
Binding DB2 Connect Packages for an EBCDIC Installation ............................................................................. 714
Binding DB2 Connect Packages for a Unicode Installation ................................................................................ 718
Binding DB2 Connect Packages for DB2 Connect Version 10 or later .............................................................. 727
Setting DB2CodePage for a Unicode Database ................................................................................................... 727
Setting Up the DB2 Connect Gateway on UNIX ................................................................................................. 728
Confirming DB2 Connect/ODBC Settings .......................................................................................................... 728
Setting CLI/ODBC Trace with the Client Configuration Assistant ..................................................................... 730
Chapter 18
Installing PeopleSoft Online Help ..................................................................................................................... 733
Understanding PeopleSoft Online Help (PeopleBooks) ...................................................................................... 733
Using the PeopleSoft Online Help Web Site for Context-Sensitive Help ........................................................... 734
Understanding the PeopleSoft Online Help Web Site .................................................................................... 734
Setting Up Context-Sensitive Help with the PeopleSoft Online Help Web Site ............................................ 734
Setting Up F1 Help with the PeopleSoft Online Help Web Site .................................................................... 737
Installing PeopleSoft Online Help LocalIy .......................................................................................................... 737
Obtaining PeopleSoft Online Help Installation Files from Oracle Software Delivery Cloud ........................ 737
Installing the PeopleSoft Online Help to a Local Machine ............................................................................ 738
Configuring Context-Sensitive Help with Local Installations ............................................................................. 739
Enabling the Help Link from the Application Pages with Local Installations ............................................... 740
Enabling F1 Help with Local Installations ..................................................................................................... 740
Creating the Help Index for Multi-Product Installations ................................................................................ 741
Using Oracle Secure Enterprise Search for Full-Text Searches .......................................................................... 741
Understanding Oracle Secure Enterprise Search and PeopleSoft Online Help .............................................. 741
Prerequisites .................................................................................................................................................... 741
Crawling a Source to Generate Full-Text Search ........................................................................................... 742
Setting Up Oracle Secure Enterprise Search for Multiple Product Line Libraries .............................................. 756
Understanding the Multiple Product Line Setup ............................................................................................ 756
Setting Up the Product Line Libraries ............................................................................................................ 757
Creating Web Sources for the Individual Product Line Libraries .................................................................. 757
Creating a Web Source for the Combined Library ......................................................................................... 757
Chapter 19
Installing Software for PS/nVision Drilldowns ............................................................................................... 759
Understanding PS/nVision DrillDown Add-ins ................................................................................................... 759
Installing the DrillToPIA Add-In ......................................................................................................................... 760
Understanding Drilldown with DrillToPIA Add-in ........................................................................................ 760
Installing the DrillToPIA Add-in on the Microsoft Excel Environment ........................................................ 760
Installing the nVisionDrill Add-In ....................................................................................................................... 761
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
19
Contents
Understanding PS/nVision DrillDown Using Web Services ..........................................................................
Understanding Security for DrillDown Using nVisionDrill VSTO Add-in ...................................................
Installing the nVisionDrill Add-in for Microsoft Excel .................................................................................
Installing the nVisionDrill Add-Ins for Multi-Language Installations ................................................................
Setting Up PeopleSoft Integration Broker for Using Web Service Capability with nVisionDrill Add-in ..........
761
761
761
762
762
Chapter 20
Installing Web Application Deployment Tools ................................................................................................ 767
Prerequisites ......................................................................................................................................................... 767
Installing the Web Application Deployment Tool on Oracle WebLogic in GUI Mode ...................................... 768
Installing the Web Application Deployment Tool on IBM WebSphere in GUI Mode ....................................... 781
Installing the Web Application Deployment Tool on Oracle WebLogic in Console Mode ................................ 793
Installing the Web Application Deployment Tool on IBM WebSphere in Console Mode ................................. 797
Installing the Web Application Deployment Tool in Silent Mode ...................................................................... 801
Understanding the Web Application Deployment Tool Silent Mode Installation and the Response File ..... 801
Editing the Web Application Deployment Tool Response File to Deploy DES ............................................ 802
Running the Web Application Deployment Tool Silent Mode Installation to Deploy DES .......................... 803
Testing and Troubleshooting the Web Application Deployment ........................................................................ 804
Chapter 21
Setting Up a Unicode Database ......................................................................................................................... 805
Prerequisites ......................................................................................................................................................... 805
Defining Conversion Pages for Unicode Conversion Services ............................................................................ 805
Fulfilling Connectivity Requirements .................................................................................................................. 806
Appendix A
Extracting DDL for PTSYS Database .............................................................................................................. 807
Understanding the PTGENDDL.DMS Script ...................................................................................................... 807
Using the PTGENDDL.DMS Script .................................................................................................................... 807
Appendix B
Using the PeopleSoft Tablespace DDL Automation Assistance Tool ............................................................ 817
Understanding the PeopleSoft Tablespace DDL Automation Assistance Tool ................................................... 817
Understanding PSTAAT Workstation Requirements .......................................................................................... 818
Understanding the PSTAAT Graphical User Interface ........................................................................................ 818
Understanding the Various PSTAAT Input and Output Files ............................................................................. 829
Using PSTAAT to Create TBDDL and IXDDL .................................................................................................. 833
Using PSTAAT to Customize DDL ..................................................................................................................... 838
20
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Contents
Understanding How PSTAAT Assigns an Object Naming Convention ........................................................ 838
Choosing a Primary Database Prefix and Maximum Number of Tables per Tablespace and Tablespaces per
Database .......................................................................................................................................................... 838
Using the New Name Parameter to Override Tablespace Name .................................................................... 839
Customizing DDL Scripts ............................................................................................................................... 840
Recalculating Primary and Secondary Space Allocations and Setting a Minimum Secondary Space Allocation
With PSTAAT ................................................................................................................................................ 841
Using PSTAAT to Override the Default Bufferpool Assignment .................................................................. 843
Using PSTAAT to Override the Default Segment Size .................................................................................. 844
Validating Input .............................................................................................................................................. 845
Using PSTAAT to Reassign Temporary Tables to Additional Tablespaces ....................................................... 847
Using PSTAAT to Isolate Other Tables to Individual Tablespaces .................................................................... 851
Using PSTAAT to Convert EBCDIC DDL to Unicode DDL ............................................................................. 852
Understanding the EBCDIC DDL to Unicode DDL Conversion ................................................................... 852
Creating Database, Tablespace, and Table Shell DDL for an EBCDIC to Unicode Database Conversion ... 853
Using PSTAAT to Install PeopleSoft Databases ................................................................................................. 857
Appendix C
Describing Debugger Requirements ................................................................................................................. 859
Describing Debugger Requirements for the AIX Operating System ................................................................... 859
Describing Debugger Requirements for the HP-UX Operating System .............................................................. 859
Describing Debugger Requirements for the Linux Operating System ................................................................ 859
Describing Debugger Requirements for the Oracle Solaris Operating System ................................................... 860
Describing Debugger Requirements for the z/OS Operating System .................................................................. 860
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
Description
Monospace
Indicates a PeopleCode program or other code, such as
scripts that you run during the install. Monospace is also
used for messages that you may receive during the install
process.
Italics
Indicates field values, emphasis, and book-length publication
titles. Italics is also used to refer to words as words or letters
as letters, as in the following example:
Enter the letter O.
Italics are also used to indicate user-supplied information.
For example, the term domain is used as a placeholder for
the actual domain name in the user's environment. When two
such placeholders are used together, they may be set apart
with angle brackets. For example, the path
<PS_CFG_HOME>/appserv/<domain> includes two
placeholders that require user-supplied information.
Initial Caps
Field names, commands, and processes are represented as
they appear on the window, menu, or page.
lower case
File or directory names are represented in lower case, unless
they appear otherwise on the interface.
Menu, Page
A comma (,) between menu and page references indicates
that the page exists on the menu. For example, "Select Use,
Process Definitions" indicates that you can select the Process
Definitions page from the Use menu.
Cross-references
Cross-references that begin with See refer you to additional
documentation that will help you implement the task at hand.
We highly recommend that you reference this
documentation.
Cross-references under the heading See Also refer you to
additional documentation that has more information
regarding the subject.
24
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Preface
Convention
Description
⇒ (line-continuation arrow)
A line-continuation arrow inserted at the end of a line of
code indicates that the line of code has been wrapped at the
page margin. The code should be viewed or entered as a
continuous line of code, without the line-continuation arrow.
" " (quotation marks)
Indicate chapter titles in cross-references and words that are
used differently from their intended meaning.
Note. Note text.
Text that begins with Note. indicates information that you
should pay particular attention to as you work with your
PeopleSoft system.
Important! Important note text.
A note that begins with Important! is crucial and includes
information about what you need to do for the system to
function properly.
Warning! Warning text.
A note that begins with Warning! contains critical
configuration information or implementation considerations;
for example, if there is a chance of losing or corrupting data.
Pay close attention to warning messages.
Products
This documentation may refer to these products and product families:
•
Oracle® BPEL Process Manager
•
Oracle® Enterprise Manager
•
Oracle® 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.
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:
PSOFT-Infodev_US@oracle.com
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
•
Verifying Database Server Sizing
•
Defining DB2 for z/OS Subsystem Configuration
•
Installing Supporting Applications
•
Setting Up Database Connectivity
•
Using Connect ID
•
Setting Up z/OS User IDs
•
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
29
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 PeopleToolsOnly 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
•
Defining the Application Server
•
Defining the Batch Server
•
Defining Installation Locations
•
Defining the Web Server
•
Using Laser Printers
Chapter 1
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.
For DB2 z/OS, the file server is used as a staging location to FTP files to the z/OS batch server only. If you are
installing a file server on DB2 z/OS, when running the PeopleSoft Installer, you need to select all PeopleSoft
Servers. This will ensure that all of the files needed by Server Transfer are installed to the PeopleSoft File Server.
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.
34
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 1
Preparing for Installation
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.
Note. If possible, you may want to separate your PeopleSoft applications into their own subsystem away from
other applications. Most sites have separate subsystems for production, development, and testing.
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.
When installing the PeopleSoft software on the z/OS mainframe, you must install one or more dedicated UNIX or
Windows application servers. You should plan to connect the application server to the database using the highest
bandwidth connection available.
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.
For the DB2 z/OS batch server on the mainframe, the SQR and COBOL files must be transferred from the file
server, 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_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.
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_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.
36
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 1
Preparing for Installation
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
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
User Environment Variable
PS_CFG_HOME Default Location
UNIX
HOME
$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_HOME upon which it is based.
For example, when you install your PeopleSoft application, the directory structure includes SQR scripts in
PS_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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
37
Preparing for Installation
Chapter 1
See "Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode."
See "Setting Up the PeopleSoft Pure Internet Architecture in Console Mode."
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 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
•
Using Multiple Databases
•
Determining Databases and Database Names
38
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 1
•
Using Standard Database Names
•
Choosing Owner ID Processing Option
Preparing for Installation
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.
The System and Demo PeopleSoft databases are installed using a multiple-database strategy, where the "logical"
PeopleSoft database actually comprises multiple "physical" databases that share a common DB2 owner ID. This is
explained in more detail in the following section.
Task 1-4-1: Using Multiple Databases
To facilitate optimal performance and minimal use of shared mainframe resources, Oracle employs a multipledatabase strategy on DB2 z/OS. Oracle uses multiple DB2 databases for installing both Demo and System
PeopleSoft databases.
This multiple-database strategy provides the following benefits:
•
Reducing database descriptor (DBD) size improves performance by easing virtual storage constraints.
•
Avoids exceeding the DB2 restriction limiting DBD size to no more than 25 percent of environmental
descriptor manager (EDM) pool size.
•
Improves DDL concurrency in certain PeopleSoft operations.
For instance, when Process Scheduler is invoked, it holds share locks on the DBD of the database where the
Process Scheduler tables are located. Isolating these tables to their own database avoids potential lockouts of
other processes running concurrently with Process Scheduler.
The installation process creates all of the DB2 objects with the same DB2 owner ID. The PeopleSoft reference to
this owner ID equates to the CREATOR field found in the SYSIBM SYSTABLES Catalog table. A PeopleSoft
database is a logical concept that includes all of the PeopleSoft objects and application data belonging to a single
PeopleSoft product line sharing the same owner ID, distributed across multiple physical DB2 databases. The
owner ID common to all of these objects is stored in the PeopleSoft PeopleTools tables PS.PSDBOWNER and
PSSTATUS. The DB2 owner ID and its use in the PeopleSoft system is discussed in the section Choosing Owner
ID Processing Options.
Oracle defines a standard set of DB2 databases for each product line in a DDL script that you will be instructed to
edit and run in the "Creating a Database" chapter.
Task 1-4-2: 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 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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
39
Preparing for Installation
Chapter 1
The PeopleSoft System and Demo databases are delivered with a seven-character database name that serves two
functions. It serves as:
•
The name of the PeopleSoft logical database (which, for the System and Demo databases is actually composed
of multiple DB2 databases).
•
The seven-character name of the "root" physical DB2 database, from which the names of the additional
physical DB2 databases that comprise the single PeopleSoft logical database are derived.
The DB2 database naming convention is explained in more detail in the following section, Using Standard
Database Names.
Task 1-4-3: Using Standard Database Names
The PeopleSoft database naming convention for DB2 z/OS uses one seven-character DB2 database name for a
database containing all of the PeopleSoft system tables except for tables used by Process Scheduler. We refer to
this database as the root database. A second database name with an eighth character of T is reserved just for
Process Scheduler due to persistent share locks. The remaining DB2 database names have an eighth character,
appended to the root database name, identifying a specific application group within a PeopleSoft product line.
Later in this guide, you will run a Data Mover Import script that requires you to select a database name to identify
this PeopleSoft database. This database name is actually nothing more than a label that serves two purposes. It
enables the DB2 Connect connectivity software to identify the appropriate configuration to connect to your DB2
subsystem, and it is the high-level key on the table PS.PSDBOWNER from which the owner ID of the objects in
the PeopleSoft database is derived during the sign-on process. When users sign on to a PeopleSoft database from
a client workstation, they enter this database name in the PeopleSoft sign-on panel. The database name must be
catalogued in the IBM DB2 Connect connectivity software in order to complete the database connection.
See "Creating a Database."
Task 1-4-4: Choosing Owner ID Processing Option
This section discusses:
•
Understanding Owner ID Processing
•
Using Primary Authorization ID Processing
•
Using Secondary Authorization ID Processing
Understanding Owner ID Processing
This section summarizes the relationship between the PeopleSoft access ID and the DB2 owner ID. Other
PeopleSoft IDs, such as the connect ID, are discussed later in this chapter. For more information on the various
PeopleSoft authorization IDs, see the PeopleTools: Security Administration product documentation. The owner
ID is a DB2 z/OS concept and owns the DB2 tables and views. For information on DB2 z/OS security, see the
IBM DB2 documentation.
Each PeopleSoft database that you create must have a valid DB2 owner ID. All of the objects in a PeopleSoft
database will share the same owner ID. Besides being found in the CREATOR field of the SYSIBM system
catalog tables, such as SYSIBM.SYSTABLES, this value is stored in the OwnerID field of the PS.PSDBOWNER
and PSSTATUS PeopleSoft PeopleTools tables.
Oracle recommends that you not use an owner ID used by a non-PeopleSoft application, because this can create
problems when auditing your database.
There are two security-related processing options to choose from when establishing the owner ID:
40
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 1
•
Preparing for Installation
Primary authorization ID processing
• Secondary authorization ID processing
The PeopleSoft installation uses various authorization IDs and passwords to control user access, including user
ID, access ID, and connect ID. The PeopleSoft access ID is directly linked to the decision to use primary or
secondary authorization ID processing. Functionally, this is the ID that has the DB2 access and authorities to
perform the bulk of the SQL processing within the PeopleSoft database. Individual PeopleSoft user IDs would not
be granted the level of DB2 authority that the access ID possesses. There will either be a direct relationship
between the name of the PeopleSoft access ID and the DB2 owner ID, or an indirect one, depending on which
authorization method is chosen.
Using Primary Authorization ID Processing
The primary authorization ID is the simplest implementation of table ownership. The primary authorization ID
and the DB2 owner ID of the PeopleSoft database objects are the same ID. In this option, the owner ID defined in
DB2 will be the same name as the PeopleSoft access ID defined in the PeopleSoft PeopleTools tables. The
PeopleSoft access ID is the DB2 owner ID.
The following table summarizes the roles and authorities of the DB2 owner ID, primary and secondary
authorization IDs and the access IDs for primary authorization ID processing:
Roles and Authorities
Primary Authorization ID
Secondary Authorization ID
Same ID as DB2 Object Owner ID
(CREATOR)
Yes
NA
Database Log On Access
Yes
NA
DB2 Object Access
Yes
NA
Same ID as PeopleSoft Access ID
Yes
NA
SET CURRENT SQLID statement
required?
No
NA
Using Secondary Authorization ID Processing
Most PeopleSoft customers use secondary authorization ID processing to establish an owner ID.
The DB2 owner ID of the PeopleSoft database objects is established as an external security system group, referred
to as a "secondary authorization ID," rather than a primary authorization ID. A secondary authorization ID is not
given direct logon access to the database, but because it is the DB2 owner ID, it has direct access to the
PeopleSoft database objects. Logon access is generally granted to a primary authorization ID, but with secondary
authorization ID processing, the primary authorization ID has no direct access to the PeopleSoft database objects.
A primary authorization ID can "transform" itself into the secondary authorization ID by issuing the following
SQL command:
SET CURRENT SQLID = <secondary authorization ID>
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
41
Preparing for Installation
Chapter 1
Running this command enables the primary authorization ID to acquire all of the database object permissions
owned by the secondary authorization ID. The mainframe security maintenance package (for example, RACF,
Top Secret, or ACFII) keeps track and monitors what secondary authorization IDs can be used by a primary
authorization ID.
When setting up a PeopleSoft application using secondary authorization ID processing, the access ID is
established as a primary authorization ID that has the authority to issue a SET CURRENT SQLID statement
setting itself equal to the secondary authorization ID.
The following table summarizes the roles and authorities of the DB2 owner ID, primary and secondary
authorization IDs and the access IDs for secondary authorization ID processing:
Roles and Authorities
Primary Authorization ID
Secondary Authorization ID
Same ID as DB2 Object Owner ID
(CREATOR)
No
Yes
Database Log On Access
Yes
No
DB2 Object Access
No
Yes
Same ID as PeopleSoft Access ID
Yes
No
SET CURRENT SQLID statement
required?
Yes
NA
In secondary authorization ID processing, at sign on, PeopleSoft PeopleTools, under authorization of the access
ID, issues the SET CURRENT SQLID statement to the DB2 owner ID. This also occurs when you run COBOL
on either the client or the host, or when you run SQR on the client or host.
Note. The access ID does not need SYSADM authority to the DB2 subsystem.
With SYSADM authority, the access ID may issue a SET CURRENT SQLID statement to any authorization ID.
If you do not have SYSADM authority, you may issue SET CURRENT SQLID only to your valid authorization
IDs. Your DB2 owner ID has a certain profile in the mainframe security maintenance package (RACF or its
equivalent) and that profile contains all your assigned secondary authorization groups, which are used as valid
authorization IDs. You can issue SET CURRENT SQLID only to the authorization IDs assigned to you.
The PeopleSoft installation is delivered with secondary authorization groups that are equal to the owner of the
tables. The access ID is added to this secondary authorization group, and thus the access ID can issue a SET
CURRENT SQLID statement only to the owner of the tables (remember owner = RACF group). Using this
approach, it is not necessary to grant SYSADM authority to the access ID. The bottom line is that the access ID
must have proper security to issue SET CURRENT SQLID to the owner of the PeopleSoft tables but this does not
require SYSADM authority to the DB2 subsystem.
See E-DB2: Mainframe Security and PeopleSoft, My Oracle Support, Doc ID 1060956.1.
Task 1-5: Planning Multilingual Strategy
This section discusses:
•
Understanding Multilingual Issues
•
Choosing a Base Language
42
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 1
•
Selecting Additional Languages
•
Selecting a Database Character Set
Preparing for Installation
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 (Unicode recommended)
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
Language
Database Character Set
ARA
Arabic
Unicode only
CFR
Canadian French
Unicode recommended
CZE
Czech
Unicode only
DAN
Danish
Unicode recommended
DUT
Dutch
Unicode recommended
ENG
US English
Unicode recommended
FIN
Finnish
Unicode recommended
ESP
Spanish
Unicode recommended
FRA
French
Unicode recommended
GER
German
Unicode recommended
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
43
Preparing for Installation
Chapter 1
Language Code
Language
Database Character Set
HUN
Hungarian
Unicode only
ITA
Italian
Unicode recommended
JPN
Japanese
Unicode only
KOR
Korean
Unicode only
NOR
Norwegian
Unicode recommended
POL
Polish
Unicode only
POR
Portuguese
Unicode recommended
ROM
Romanian
Unicode only
RUS
Russian
Unicode only
SVE
Swedish
Unicode recommended
THA
Thai
Unicode only
TUR
Turkish
Unicode only
UKE
United Kingdom English
Unicode recommended
ZHS
Simplified Chinese
Unicode only
ZHT
Traditional Chinese
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.
44
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 1
Preparing for Installation
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
45
Preparing for Installation
Chapter 1
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, but also supports non-Unicode (legacy) code sets, in PeopleSoft databases.
Please refer to the discussion of CCSID later in this chapter for further information regarding character sets.
See Defining DB2 for z/OS Subsystem Configuration.
The following table lists a selection of the CCSIDs and languages that the PeopleSoft software supports for DB2
for z/OS:
CCSIDs
Languages Supported
CCSID 37
EBCDIC English
CCSID 500
EBCDIC International
CCSID UNICODE
Unicode
See PeopleTools: Global Technology, "Selecting and Configuring Character Sets."
Using Unicode Databases
In addition to supporting several legacy character sets, the PeopleSoft software supports creating Unicode
databases using DB2 for z/OS New Function Mode. Unicode enables you to maintain data in virtually any
modern language in a single database. Prior to Unicode, many languages could not coexist in one database, as
they did not share a common character set.
See "Setting Up a Unicode Database."
To create a DB2 for z/OS Unicode database, you must specify the CCSID UNICODE option of the CREATE
DATABASE statement.
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.
46
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 1
Preparing for Installation
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.
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
47
Preparing for Installation
Chapter 1
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 "Creating a Database," 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.
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).
48
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 1
Preparing for Installation
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)
PeopleSoft Enterprise PeopleTools Certification Table of Contents, My Oracle Support, (search for the article
title)
Task 1-8: Verifying Database Server Sizing
On your database server, the direct access storage device (DASD) volume(s) making up your storage group(s)
should have sufficient space for the demo database. If you plan to substantially increase the size of tables in your
demo database, ensure that these volumes have plenty of space, or add additional volumes, so that your file
systems have ample space to accommodate growth. You must also alter the primary and secondary quantities of
the tablespaces and indexes that you expect to expand. In addition to space requirements, the Database
Administrator should verify that ample VTOC directory space is available to avoid problems during installation.
Note. Because many PeopleSoft tables are delivered empty, they take up no physical space in the tablespace,
whereas indexes, even those created on an empty table, require a minimum of one track each.
Task 1-9: Defining DB2 for z/OS Subsystem Configuration
This section discusses:
•
Understanding DB2 Configuration Requirements
•
Defining EDM Pool Considerations
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
49
Preparing for Installation
Chapter 1
•
Defining Decimal Arithmetic
•
Using DSMAX
•
Using CMTSTAT/IDTHTOIN
•
Using CCSID and DB2 z/OS Database Storage Encoding Schemes
•
Using DECIMAL
Understanding DB2 Configuration Requirements
The following information provides recommendations for the configuration of the DB2 subsystem that will house
the PeopleSoft database. We recommend dedicating a DB2 subsystem to your PeopleSoft application. This will
allow you to customize the DB2 ZPARM settings for the subsystem without having an impact on your existing
applications.
Task 1-9-1: Defining EDM Pool Considerations
The PeopleSoft installation procedure places all tables for the product you are installing into multiple physical
databases using a shared tablespace methodology. Depending on the applications you are installing, the DB2
subsystem could have a minimum EDM Pool Size of 10 to 30 MB.
If the pool size is too small, the database administrator should either increase it or manually edit the DDL scripts
provided to create additional databases. If you use DB2 Dynamic SQL Cache, you will need to increase the EDM
pool size. It is difficult to recommend an optimum size for the EDM pool. Like buffer pools, there is a tradeoff
between performance and memory usage. It also depends very heavily on the mix of transactions versus batch
processes executing at a point in time. Customers traditionally allocate between 50 and 100 MB when Dynamic
SQL Cache is enabled.
Place the DB2 Dynamic SQL Cache in a Data Space. This will allow for separating the cache from the EDM
pool, which and results in less competition for EDM space. It also allows for a larger Dynamic SQL Cache (up to
2 GB).
Task 1-9-2: Defining Decimal Arithmetic
Arithmetic operations involving decimal numbers in the PeopleSoft system require a greater decimal precision
than earlier versions of PeopleSoft software. DEC31 rules allow a maximum precision of 31 digits in a result
rather than only 15. This allows for a greater number of digits in the scale (digits to the right of the decimal),
resulting in more accurate calculations, particularly when the "unrestricted" result contains many digits to the
right of the decimal. DB2 truncates any digits beyond the calculated scale of the result, without rounding. For
example, the number 1.45697, the result of multiplying or dividing another number by 1.456 (assume a scale of 3)
will be significantly different from 1.4569 (assume a scale of 4). In addition, in further support of greater accuracy
in decimal operations, the PeopleSoft system is utilizing new functionality that permits calculation of a minimum
scale of 6 digits in decimal division operations. In prior releases, 3 digits was the maximum, minimum scale.
In past releases, the PeopleSoft system had specific requirements for the DB2 zparms DECARTH, DECDIV3 and
MINDVSCL. Through a joint development effort with IBM, functionality has been enhanced to enable control of
the functionality provided by these zparms at the DB2 connection level, without impact to other applications
running within the same DB2 subsystem.
PeopleSoft code executes the statement SET CURRENT PRECISION = "D31,6" for each connection into the
database, which will have the effect of running the application in a DB2 subsystem with zparm settings of
DECARTH=31 and MINDVSCL=6, overriding what the actual zparm settings may be. DECDIV3 is overridden
by MINDVSCL so whether DECDIV3 is YES or NO has no impact on the PeopleSoft application.
50
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 1
Preparing for Installation
Task 1-9-3: Using DSMAX
To reduce the open and close activity of data sets, it is important to set DSMAX correctly. DSMAX should be
larger than the maximum number of data sets that are open and in use at one time. For best performance, leave
enough margin in your specification of DSMAX that frequently used CLOSE YES data sets can remain open after
they are no longer referenced. If data sets are opened and closed frequently, such as every few seconds, you can
improve performance by increasing DSMAX. The maximum value for DSMAX is 100000.
See Important PTFs for PeopleSoft on DB2 for z/OS, My Oracle Support, (search for the article title).
Task 1-9-4: Using CMTSTAT/IDTHTOIN
We recommend setting the CMTSTAT parameter to INACTIVE and setting the IDTHTOIN parameter to 0 (i.e.
the IDTHTOIN zparm is ignored when CMTSTAT=INACTIVE). PeopleSoft two-tier and three-tier environments
will function properly regardless of the values of CMTSTAT and IDTHTOIN. CMTSTAT is set in DSNTIPR and
it specifies whether to make a thread active or inactive after it successfully commits or rolls back and holds no
database locks or cursors. ACTIVE threads use memory resources as well as contributing to the MAXDBAT
limit.
Task 1-9-5: Using CCSID and DB2 z/OS Database Storage Encoding
Schemes
PeopleSoft PeopleTools supports only EBCDIC and Unicode data storage encoding schemes (not ASCII) on the
z/OS database server. Be careful to set the default system encoding scheme (SCCSID as specified in
DSNHDECP) in your subsystem for valid EBCDIC translation. PeopleTools Unicode installations will override
the SCCSID value by explicitly specifying Unicode as the CCSID when creating the individual databases that will
compose a Unicode installation. Consult the DB2 zOS Installation and SQL Reference guides for assistance in
setting the default CCSID for your subsystem.
Note that unexpected results may occur when a binary sort is deployed from, or when the collating sequence on a
remote machine is different from the host—such as when running COBOL from a Windows or UNIX based
platform, and accessing DB2 for z/OS. In house, PeopleSoft has tested with CCSIDs of 37 and 500. For more
information, and especially if you use a CCSID other than 37, consult the PeopleTools: Global Technology and
PeopleTools: System and Server Administration product documentation for more details about the use of
%BINARYSORT and PSOPTIONS.
Also, never change the CCSID in your subsystem without first consulting IBM technical support. Corruption and
loss of data could result.
Task 1-9-6: Using DECIMAL
PeopleSoft PeopleTools supports zparm settings of both DECIMAL=PERIOD and DECIMAL=COMMA. The
PeopleTools API is able to identify the zparm value on your particular subsystem. For those subsystems with
zparm DECIMAL=PERIOD, no additional logic is invoked. For those subsystems with DECIMAL=COMMA, a
parsing routine is invoked to "reformat" any necessary SQL statements to avoid confusion by the DB2 parser in
distinguishing a decimal point from a comma. For COBOL programs running on the mainframe, a message is
displayed in the job log indicating whether the parsing routine has been activated. Customers running with zparm
DECIMAL=COMMA should verify that the parsing function has indeed been activated. Customers running with
zparm DECIMAL=PERIOD, should verify that the parsing function is not activated, as it is unnecessary and
could have negative performance implications.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
51
Preparing for Installation
Chapter 1
While PeopleSoft PeopleTools fully supports either setting for zparm DECIMAL, not all product lines support
both settings. SQR does not go through the PeopleTools API interface, and therefore each program must be
inspected for compliance. Product lines that do not use SQR would support both zparm DECIMAL settings by
default (for example, CRM). Product lines that only support one setting will support DECIMAL=PERIOD. Refer
to the product line specific Installation addenda for information on whether your product line supports zparm
DECIMAL=COMMA.
Task 1-10: 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.
• For z/OS servers, install the appropriate version of IBM Enterprise COBOL for z/OS and OS/390.
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.
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.
•
52
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 1
Preparing for Installation
•
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
•
You must install SQR on any non-Windows batch server.
•
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.
JRE
•
z/OS customers should install the appropriate IBM z/OS Java to support JDK/JRE requirements for
PeopleSoft software.
• The minimum support level required for PeopleSoft PeopleTools 8.55 is JRE 7.
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-11: Setting Up Database Connectivity
As part of preparation, you may wish to set up database connectivity components on the mainframe, set up
TCP/IP on database clients (including application servers and any dedicated batch servers), and install software
for the DB2 Connect Gateway.
However, it makes sense to wait until after the PeopleSoft database has been created before configuring the DB2
Connect Gateway—using either Client Configuration Assistant (Microsoft Windows) or the Command Line
Processor (UNIX)—so that the connection to the database can be tested.
Note. The LDAP client (FMID HRSL180) is required for PSAE on z/OS. On z/OS, the LDAP client resides as a
DLL named GLDCLDAP in /usr/lib. Note that /usr/lib must be part of the LIBPATH environment variable.
Note. Before you can run the Process Scheduler from z/OS UNIX System Services, the DB2 systems programmer
must have installed DB2 ODBC.
See Also
"Creating a Database"
"Installing and Configuring DB2 Connect"
IBM DB2 Connect documentation
IBM DB2 Installation Guide (for DB2 ODBC)
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
53
Preparing for Installation
Chapter 1
Task 1-12: Using Connect ID
This section discusses:
•
Understanding Connect ID
•
Using Connect ID
Understanding Connect ID
All two-tier connections use the PeopleSoft PeopleTools connect ID feature.
Two-tier connections include both client workstations and application servers. The connect ID feature allows
customers to associate multiple PeopleSoft operators with the same connect ID. The connect ID is granted 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 PeopleSoft user ID to control access to objects
in the database. The PeopleSoft sign-on process validates the connect ID on the database server, rather than the
user ID. Connect ID simplifies database security maintenance. It is not necessary to define and maintain
individual user IDs within the database server security. For DB2 z/OS implementations, only the connect ID must
be defined in the z/OS security management software (for example, RACF, ACF2, TopSecret), with logon
capabilities. The connect ID option eliminates the need to set up each user ID as a valid z/OS ID. One z/OS ID
can be created and then many PeopleSoft operators can use this ID as the connect ID to sign on to the PeopleSoft
system. This arrangement may be an appropriate choice at customer sites where the PeopleSoft user's only
required access to the mainframe is to use the PeopleSoft applications.
The connect ID is granted access using the following steps:
•
Define the connect ID as an ID with logon capabilities to the z/OS server in the z/OS security management
software.
•
Execute script Grant.sql against the database, after the table objects have been created. Grant.sql grants
SELECT access to the PeopleTools tables PS.PSDBOWNER, PSSTATUS, PSACCESSPRFL,
PSACCESSPROFILE, and PSOPRDEFN.
In addition, the connect ID and connect ID password must be defined in either the Configuration Manager setting
to allow a two-tier connection from the client workstation, or in the application server configuration setting, to
allow connection to the database from the application server.
See Also
PeopleTools: System and Server Administration, "Using PeopleSoft Configuration Manager"
Task 1-12-1: Using Connect ID
As an example, when logging into a PeopleSoft database in two-tier mode, the user enters a database name,
PeopleSoft user (operator) ID, and password in the PeopleSoft Signon dialog box.
After making the initial connection to the database, the sign-on process performs SELECT statements against a
series of PeopleTools tables to obtain data required for sign-on and security. The PeopleSoft user ID and
password are validated against the PSOPRDEFN table, regardless of the sign-on option. The access ID and
password, which are encrypted, are obtained from the PSACCESSPROFILE table.
54
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 1
Preparing for Installation
The sign-on process disconnects, and then connects again as the access ID, which has all Data Manipulation
Language (DML) authorities and certain DDL authorities on the PeopleSoft database. If you are using the
Secondary Authorization ID option, the sign-on process then sets the current SQLID equal to the DB2 owner ID
obtained from the PS.PSDBOWNER table.
The example below details the logon and connection process to the PeopleSoft database on z/OS. This example
uses the following parameter values:
•
Database Name: PT84
•
User ID/Pswd: PSUSER1/PSUSER1
•
Connect ID/Pswd: PSCONCT/PSCONCT
•
Access ID/Pswd: PSACCES1/PSACCESS1
•
Object Owner ID: PSDBOWNR
Activity
Parameter Value and/or Underlying Statements
User initiates logon by entering the database name, user ID
and password.
PT84/PSUSER1/PSUSER1
The connection is established to DB2 z/OS using the
database name, the connect ID (not the user ID), and the
password.
Connect to PT84 user PSCONCT using PSCONCT
Get PeopleSoft Database owner ID.
SELECT OWNERID FROM PS.PSDBOWNER⇒
WHERE DBNAME = :1 :1 = PT84, value returned for OWNERID = PSDBOWNR
Check PSSTATUS.
SELECT OWNERID, TOOLSREL,⇒
LASTREFRESHDTTM, LASTCHANGEDTTM⇒
FROM PSDBOWNR.PSSTATUS
Validate the user ID and password.
SELECT VERSION, OPERPSWD,⇒
ENCRYPTED, SYMBOLICID, ACCTLOCK⇒
FROM PSDBOWNR.PSOPRDEFN WHERE⇒
OPRID = :1
:1 = PSUSER1. The OPERPSWD retrieved is validated
against the value entered when the user initiated the log on.
Get the access ID and password.
SELECT ACCESSID, ACCESSPSWD,⇒
ENCRYPTED FROM PSDBOWNR.PSACCESSPRO⇒
FILE WHERE SYMBOLICID = :1
The ACCESSID and ACCESSPSWD retrieved into the
buffer are PSACCES1/PSACCES1
The current connection with the connect ID is disconnected.
Disconnect
A new connection is established, logging on with the access
ID.
Connect to PT84 USER PSACCES1 USING PSACCES1
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
55
Preparing for Installation
Chapter 1
Activity
Parameter Value and/or Underlying Statements
The "Set Current SQLID" statement is issued to permit
access to the PeopleSoft tables via the access ID without
requiring explicit qualification of the SQL statements with
the Object Owner ID (PSDBOWNR).
Set CURRENT SQLID = :1
:1 = PSDBOWNR
At this point, access within the PeopleSoft application is governed by PeopleSoft security, based on the
permissions defined in the PeopleTools security tables for the user ID that was entered when the logon was
initiated (PSUSER1).
Task 1-13: Setting Up z/OS User IDs
This section discusses:
•
Understanding User ID Setup
•
Creating PeopleSoft User IDs
Understanding User ID Setup
Once you have determined your sign-on strategy, as described in the preceding task, you are ready to create a set
of z/OS user IDs required for the PeopleSoft PeopleTools sign-on process and database table access.
Note. All IDs that you create must be in UPPERCASE.
Task 1-13-1: Creating PeopleSoft User IDs
Use this procedure to create new user IDs for the application. To create PeopleSoft user IDs:
1. Create a mainframe user ID for connecting to the PeopleSoft database. This mainframe user ID needs to
match the PeopleSoft connect ID.
Note. Once your PeopleSoft connect ID is created, you can specify the ID in either the Configuration Manager
Startup tab for Windows client connections or the Startup section in the application server configuration file
for application server connections. This is done so the client or the application server pass the correct ID to
connect to the database.
Note. The connect ID password must be 30 characters or less.
You must explicitly grant SELECT authority to this mainframe user ID on specific PeopleSoft PeopleTools
tables, before attempting to connect to the PeopleSoft database.
2. Create a second mainframe user ID to be used as the PeopleSoft access ID.
The access ID, which is stored in encrypted form in the PeopleSoft database, should either be granted all
DML authorities and certain DDL authorities on the PeopleSoft database if using Primary Authorization ID
access, or associated with a Secondary Authorization ID with this access, if using Secondary Authorization ID
access (the next step). The access ID and access password must be tightly controlled. Both are encrypted in
the PeopleSoft database.
56
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 1
Preparing for Installation
Note. The access ID password must be 30 characters or less.
Oracle recommends that you set up the access ID in z/OS with a non-expiring password. If company standards
mandate that you periodically change the access ID's password, or if the access ID is set up in the z/OS
security system with a password that will expire, special processing will be necessary. You must ensure that
PeopleSoft databases are updated with the access ID's new password before the password changes in the z/OS
security system. The PeopleSoft Security Administrator provides the functionality to change the access ID's
password stored in the security tables.
If the mainframe password for the access ID has expired or has been changed before the PeopleSoft database
has been updated with the new password, no one will be able to access the PeopleSoft online system.
3. If you are using the Secondary Authorization ID option, set up an external security system group as the owner
ID. Make the access ID a member of this group, with authority to SET CURRENT SQLID = <Owner ID>.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
57
Preparing for Installation
Chapter 1
4. Grant SELECT authority to owner ID on SYSIBM DB2 catalog tables.
There are certain PeopleSoft processes that perform queries against the SYSIBM DB2 catalog tables. For this
reason you must grant SELECT authority on these catalog tables to the owner ID that you choose for the
PeopleSoft database. The following table lists DB2 catalog tables used by the PeopleSoft system, with
corresponding PeopleSoft processes or utilities.
Table
PeopleSoft Process or Utility
SYSIBM.SYSTABLES
Application Designer
DDDAUDIT.SQR
SETDBNAM.SQR
SETSPACE.SQR
SETTMPIN.SQR
%UpdateStats MetaSQL function
SYSIBM.SYSTABLESPACE
SETSPACE.SQR
SETDBNAM.SQR
SYSIBM.SYSTRIGGERS
Application Designer
DDDAUDIT.SQR
SYSIBM.SYSCOLUMNS
Application Designer
SYSIBM.SYSINDEXES
Application Designer
DDDAUDIT.SQR
SETBUFF.SQR
SYSIBM.SYSKEYS
Application Designer
SYSIBM.SYSINDEXPART
SETINDEX.SQR
SYSIBM.SYSDATABASE
NA
SYSIBM.SYSVIEWS
NA
If the Owner ID does not have proper authority to the SYSIBM tables, 551 SQL codes will result and it will
mostly occur when you are attempting to SQL Create or Alter a table using Application Designer. If you are
running the listed SQRs outside the PeopleSoft environment, the ID used to run the SQR will need SELECT
access to the listed tables.
See Also
"Creating a Database"
PeopleTools: Portal Technology
PeopleTools: Data Management
58
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 1
Preparing for Installation
Task 1-14: 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.
Task 1-15: 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.
59
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.
61
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
62
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.
63
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
JDK Version Supported
64-bit or Mixed Mode*
Comments
IBM AIX
IBM JDK 1.7.0 SR6+
64-bit
none
HP-UX Itanium
Hewlett-Packard JDK
7.0.08+
Mixed mode
Use "-d64" to turn on 64–bit
mode
Linux
Oracle JDK 1.7.0_51+
64-bit
none
Microsoft Windows
Oracle JDK 1.7.0_51+
64-bit
none
Oracle Solaris on SPARC
Oracle JDK 1.7.0_51+
Mixed mode
Requires two installers.
Use "-d64" to turn on 64-bit
mode.
Oracle Solaris on x86–64
Oracle JDK 1.7.0_51+
Mixed 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.
64
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.
65
Installing Web Server Products
Chapter 2
Note. Spaces are not allowed in the JAVA_HOME name.
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:
66
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.
67
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
68
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.
69
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.
Oracle Fusion Middleware 12c WebLogic Server and Coherence Installation - Step 3 of 8: Installation Type
window
70
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.
71
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.
Oracle Fusion Middleware 12c WebLogic Server and Coherence Installation - Step 5 of 8: Specify Security
Updates window
72
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.
73
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.
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:
74
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.
75
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
76
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.
77
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 -⇒
78
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.
79
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.
Oracle Fusion Middleware Deinstallation - Step 1 of 4: Welcome window
80
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.
81
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.
Oracle Fusion Middleware Deinstallation - Step 3 of 4: Deinstallation Progress window
82
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 2
Installing Web Server Products
5. Click Finish on the Deinstallation Complete window.
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.
83
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).
84
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.
85
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
Description
QS_FOR_WAS_ND_V8.5.5.0.zip
Quick Start for IBM WebSphere Application Server
Network Deployment V8.5
•
•
•
WAS_ND_V8.5.5_1_OF_3.zip
Binaries for IBM WebSphere Application Server Network
Deployment V8.5.5.0
•
•
•
WS_SDK_JAVA_TEV7.0_1OF3_WAS_8.5.5.zip
•
•
•
WAS_V8.5.5_SUPPL_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_2OF3_WAS_8.5.5.zip
Binaries for IBM WebSphere SDK Java (TM) Technology
Edition V7.0
WS_SDK_JAVA_TEV7.0_3OF3_WAS_8.5.5.zip
WAS_V8.5.5_SUPPL_2_OF_3.zip
Binaries for Application Client, IBM HTTP Server, Web
Server Plug-ins and WebSphere Customization Toolbox
WAS_V8.5.5_SUPPL_3_OF_3.zip
InstalMgr1.6.2_AIX_PPC_WAS_8.5.5.zip
Binaries for IBM Installation Manager v1.6.2 for AIX
HP-UX Itanium
File or Folder Name
Description
QS_FOR_WAS_ND_V8.5.5.0.zip
Quick Start for IBM WebSphere Application Server
Network Deployment V8.5
•
•
•
Binaries for IBM WebSphere Application Server Network
Deployment V8.5.5.0
86
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
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 2
Installing Web Server Products
File or Folder Name
Description
•
•
•
WS_SDK_JAVA_TEV7.0_1OF3_WAS_8.5.5.zip
Binaries for IBM WebSphere SDK Java (TM) Technology
Edition V7.0
•
•
•
WAS_V8.5.5_SUPPL_1_OF_3.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_2_OF_3.zip
Binaries for Application Client, IBM HTTP Server, Web
Server Plug-ins and WebSphere Customization Toolbox
WAS_V8.5.5_SUPPL_3_OF_3.zip
InstalMgr1.6.2_HPUXIA64_WAS_8.5.5.zip
Binaries for IBM Installation Manager v1.6.2 for HP-UX
Itanium
Linux
File or Folder Name
Description
QS_FOR_WAS_ND_V8.5.5.5.zip
Quick Start for IBM WebSphere Application Server
Network Deployment V8.5
•
•
•
WAS_ND_V8.5.5_1_OF_3.zip
Binaries for IBM WebSphere Application Server Network
Deployment V8.5.5.0
•
•
•
WS_SDK_JAVA_TEV7.0_1OF3_WAS_8.5.5.zip
•
•
•
WAS_V8.5.5_SUPPL_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_2OF3_WAS_8.5.5.zip
Binaries for IBM WebSphere SDK Java (TM) Technology
Edition V7.0
WS_SDK_JAVA_TEV7.0_3OF3_WAS_8.5.5.zip
WAS_V8.5.5_SUPPL_2_OF_3.zip
Binaries for Application Client, IBM HTTP Server, Web
Server Plug-ins and WebSphere Customization Toolbox
WAS_V8.5.5_SUPPL_3_OF_3.zip
InstalMgr1.6.2_LNX_PPC_WAS_8.5.5.zip
Binaries for IBM Installation Manager v1.6.2 for Linux
PowerPC
InstalMgr1.6.2_LNXS390_WAS_8.5.5.zip
Binaries for IBM Installation Manager v1.6.2 for Linux s390
InstalMgr1.6.2_LNX_X86_64_WAS_8.5.5.zip
Binaries for IBM Installation Manager v1.6.2. for Linux x86
64-bit
Microsoft Windows
File or Folder Name
Description
QS_FOR_WAS_ND_V8.5.5.0.zip
Quick Start for IBM WebSphere Application Server
Network Deployment V8.5
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
87
Installing Web Server Products
Chapter 2
File or Folder Name
Description
•
•
•
WAS_ND_V8.5.5_1_OF_3.zip
Binaries for IBM WebSphere Application Server Network
Deployment V8.5.5.0
•
•
•
WS_SDK_JAVA_TEV7.0_1OF3_WAS8.5.5.zip
•
•
•
WAS_V8.5.5_SUPPL_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_2OF3_WAS8.5.5.zip
Binaries for IBM WebSphere SDK Java (TM) Technology
Edition V7.0
WS_SDK_JAVA_TEV7.0_3OF3_WAS8.5.5.zip
WAS_V8.5.5_SUPPL_2_OF_3.zip
Binaries for Application Client, IBM HTTP Server, Web
Server Plug-ins and WebSphere Customization Toolbox
WAS_V8.5.5_SUPPL_3_OF_3.zip
InstalMgr1.6.2_WINX86_64_WAS_8.5.5.zip
Binaries for IBM Installation Manager v1.6.2 for Microsoft
Windows
Oracle Solaris on SPARC
File or Folder Name
Description
QS_FOR_WAS_ND_V8.5.5.0.zip
Quick Start for IBM WebSphere Application Server
Network Deployment V8.5
•
•
•
WAS_ND_V8.5.5_1_OF_3.zip
Binaries for IBM WebSphere Application Server Network
Deployment V8.5.5.0
•
•
•
WS_SDK_JAVA_TEV7.0_1OF3_WAS_8.5.5.zip
•
•
•
WAS_V8.5.5_SUPPL_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_2OF3_WAS_8.5.5.zip
Binaries for IBM WebSphere SDK Java (TM) Technology
Edition V7.0
WS_SDK_JAVA_TEV7.0_3OF3_WAS_8.5.5.zip
WAS_V8.5.5_SUPPL_2_OF_3.zip
Binaries for Application Client, IBM HTTP Server, Web
Server Plug-ins and WebSphere Customization Toolbox
WAS_V8.5.5_SUPPL_3_OF_3.zip
InstalMgr1.6.2SOLSPARC_WAS_8.5.5.zip
Binaries for IBM Installation Manager v1.6.2 for Solaris
SPARC
Oracle Solaris on x86_64
File or Folder Name
Description
QS_FOR_WAS_ND_V8.5.5.0.zip
Quick Start for IBM WebSphere Application Server
Network Deployment V8.5
88
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 2
Installing Web Server Products
File or Folder Name
Description
•
•
•
WAS_ND_V8.5.5_1_OF_3.zip
Binaries for IBM WebSphere Application Server Network
Deployment V8.5.5.0
•
•
•
WS_SDK_JAVA_TEV7.0_1OF3_WAS_8.5.5.zip
•
•
•
WAS_V8.5.5_SUPPL_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_2OF3_WAS_8.5.5.zip
Binaries for IBM WebSphere SDK Java (TM) Technology
Edition V7.0
WS_SDK_JAVA_TEV7.0_3OF3_WAS_8.5.5.zip
WAS_V8.5.5_SUPPL_2_OF_3.zip
Binaries for Application Client, IBM HTTP Server, Web
Server Plug-ins and WebSphere Customization Toolbox
WAS_V8.5.5_SUPPL_3_OF_3.zip
InstalMgr1.6.2_SOL_X86_WAS8.5.5.zip
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.
89
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"
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
91
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.
92
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.
93
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.
94
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.
95
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.
96
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.
97
Installing Additional Components
Chapter 3
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.
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:
Oracle Universal Installer: Welcome window for Oracle Tuxedo
98
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.
99
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.
Specify Home Details window
100
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.
101
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.
Earlier Version Detected window
102
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.
103
Installing Additional Components
Chapter 3
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.
SSL Installation Choice window
104
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.
105
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.
Oracle Tuxedo tlisten configuration Choice window
106
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.
107
Installing Additional Components
Chapter 3
Install progress indicator window
108
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.
109
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"
110
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.
111
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.
112
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 3
Installing Additional Components
2. Click Deinstall Products, as shown in this example:
Oracle Universal Installer: Welcome window
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
113
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."
114
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.
115
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.
116
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.
Note. The option used—Local System account or This account—must be consistent with your ODBC catalog
definition, due to registry operations. For example, if you use the Local System Account option, you must also
catalog your ODBC data source using System DSN.
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.
117
Installing Additional Components
Chapter 3
8. Select General.
Make sure that Startup Type is set to Automatic, as shown in this example.
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:
118
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
Description
ORACLE_HOME
The high level installation
/oracle
directory. You specify this
value in the silent installation
file.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Example Value
Real Value
<enter value>
119
Installing Additional Components
Chapter 3
Item
Description
Example Value
Real 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
<enter value>
TUXDIR
The full path to the Oracle
/oracle/tuxedo12.1.3.0.0
Tuxedo installation. The
installer creates this as
ORACLE_HOME/tuxedo12.
1.3.0.0
<enter value>
Username
The UNIX user name of the
Application Server
Administrator (Oracle
Tuxedo owner). See the next
section for instructions.
tuxedo
<enter value>
UNIX_GROUP_NAME
The UNIX group name of the tuxedo
Oracle Tuxedo owner. See
the next section for
instructions.
<enter value>
FROM_LOCATION
The full path to the directory /home/temp/Disk1/stage/prod
containing the products to be ucts.xml
installed.
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.
120
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.
121
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:
122
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.
123
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.
124
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 pre8.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.
125
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
•
Binding Windows "SQR for PeopleSoft" DB2 Connect Packages
•
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 needed for various PeopleSoft servers—including
application servers, batch servers, web servers, and database servers, and for the PeopleTools Client.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
127
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
Supported operating
systems for application
servers and batch servers
IBM z/OS on System z
•
IBM AIX on POWER
Systems (64-bit)
•
IBM: Linux on System z Linux or UNIX with network
file system (NFS) or
(batch server only; no
•
equivalent support
application server)
•
IBM z/OS on System z
(batch server only; no
application server)
•
•
Linux x86-64
•
Oracle Solaris on
SPARC (64-bit)
•
Oracle Solaris x86_64
Microsoft Windows x64
(64-bit)
Supported operating
systems for file servers
Supported operating
systems for web servers
Microsoft Windows x64 (64- •
bit)
•
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
128
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.
129
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.
For installations on DB2 z/OS, download the Microsoft Windows version of the zip file. When you install,
enter the license code for DB2 for z/OS as the database platform, and then use the PeopleSoft Server Transfer
to copy the files from the Microsoft Windows machine to your DB2 z/OS machine.
See "Setting Up the Batch Environment on z/OS," Using PeopleSoft Server Transfer.
130
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 4
Using the PeopleSoft Installer
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.
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.
131
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 256color 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]
132
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 4
Using the PeopleSoft Installer
To run the PeopleSoft Installer for an installation on DB2 for z/OS, use PS_INSTALL\disk1\setup.bat to
install on Microsoft Windows, and then use Server Transfer. This is the procedure that was used in PeopleSoft
PeopleTools 8.1x releases.
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
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
133
Using the PeopleSoft Installer
Chapter 4
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:
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:
134
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 4
Using the PeopleSoft Installer
1. Launch the installer. For example:
PS_INSTALL\disk1\setup.bat
Click Next when you see the Welcome screen for PeopleTools 8.55.
PeopleSoft Installer Welcome window
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
135
Using the PeopleSoft Installer
Chapter 4
2. Click the radio button to accept the license agreement and click Next.
The License Agreement window includes the terms in several languages.
PeopleSoft Installer License Agreement window
136
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 4
Using the PeopleSoft Installer
3. Enter your license code and click Next.
See Understanding the PeopleSoft Installer, Obtaining License Codes.
PeopleSoft Installer License window
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
137
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
138
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.
Warning! If you are installing for DB2 for z/OS, you need to select all PeopleSoft Servers. This will ensure
that all of the files needed by Server Transfer are installed to the PeopleSoft file server.
In this example the PeopleSoft Application Server, PeopleSoft Batch 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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
139
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-USASCII characters may not work with some additional component software.
PeopleSoft Installer Choose Install Folder window
140
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 4
Using the PeopleSoft Installer
7. Specify the location of your Connectivity Program Directory and click Next.
The default location for the connectivity software for DB2 for z/OS (as set by the vendor) is: C:\sqllib\bin. If
the database connectivity software was installed to a different directory, enter that path instead.
PeopleSoft Installer Connectivity Program window
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
141
Using the PeopleSoft Installer
Chapter 4
8. Depending on the PeopleSoft servers you selected, choose whether to install the PeopleSoft PeopleTools icons
and click Next.
PeopleSoft Installer PeopleTools Icons Selection window
142
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 4
Using the PeopleSoft Installer
9. 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
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
143
Using the PeopleSoft Installer
Chapter 4
10. 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
144
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 4
Using the PeopleSoft Installer
11. The next screen lists the PeopleSoft PeopleTools components (product features). Accept the defaults for the
PeopleSoft PeopleTools features and click Next.
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.
145
Using the PeopleSoft Installer
Chapter 4
12. 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
146
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 4
Using the PeopleSoft Installer
13. 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.
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
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
147
Using the PeopleSoft Installer
Chapter 4
------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
148
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 4
Using the PeopleSoft Installer
To select an item enter its number, or 0 when you are finished [0] : 6. Select the PeopleSoft servers you want to install.
For DB2 for zOS 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.
Note. If you are installing on DB2 z/OS, you must select all servers when running the installer on Microsoft
Windows. This is because there are additional steps using Server Transfer to upload the files. Also, to install a
Unicode database, DB2 z/OS customers must select the Unicode Database (Recommended) option.
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. Microsoft Windows only: Specify the database connectivity directory.
Please select the location of Connectivity Program Directory [c:\sqllib⇒
\bin]
:
The default location for the connectivity software for DB2 for z/OS (as set by the vendor) is: C:\sqllib\bin.
If the database connectivity software was installed to a different directory, enter that path instead.
9. 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] :
10. 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]:
11. 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.
12. 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.
13. 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:
DB2 for zOS
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]
14. 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
15. 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:
16. 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
Chapter 4
Note. For each installer, the installation is completed automatically.
Task 4-4: Installing PeopleSoft Application Software
After installing PeopleSoft PeopleTools, install the PeopleSoft application software to the same PS_HOME
directory. 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 you are installing more than one application, it is a good idea to create an application-specific PS_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.
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
152
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 4
Using the PeopleSoft Installer
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:
# 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
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
153
Using the PeopleSoft Installer
Chapter 4
# 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: Binding Windows "SQR for PeopleSoft" DB2 Connect
Packages
This task applies to Microsoft Windows file or report servers.
To bind Windows "SQR for PeopleSoft" DB2 Connect packages:
1. Using an ID with mainframe logon and BINDADD privileges, log on to DB2 Connect Command Line
Processor:
db2 => CONNECT TO <database name> USER <mainframe User Id>
Note. Enter your current password for "mainframe User Id": <mainframe User Id password>.
Database Connection Information:
Database server = DB2 OS/390 9.5.0
SQL authorization ID = <mainframe User Id>
Local database alias = <database name>
2. The Windows SQR bind executable is located in the File or Report Server directory (for example, PS_HOME\
bin\sqr\db2\BINW\dbcalls.bnd).
For an EBCDIC installation, issue the following bind command:
db2 => bind <ps_home>\bin\sqr\db2\BINW\dbcalls.bnd blocking all grant⇒
public⇒
sqlerror continue
154
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 4
Using the PeopleSoft Installer
For a Unicode installation, issue the following command to bind the Windows SQR executable with encoding
Unicode:
db2 -> bind <ps_home>\bin\sqr\db2\BINW\dbcalls.bnd encoding unicode⇒
blocking⇒
all grant public sqlerror continue
Collection id (COLLID) of SQR will be added to SYSPACKAGE catalog table and package execute authority
to PUBLIC in SYSPACKAUTH catalog table.
Note. This bind needs to be executed for each new version of SQR for PeopleSoft on every DB2 subsystem or
database.
Task 4-8: 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:
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"
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 Server Transfer, 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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
157
Setting Up the Install Workstation
•
Chapter 5
The workstation must have a logical drive mapped to PS_HOME on the file server (or, if the file server and
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:
158
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 5
Setting Up the Install Workstation
•
Database type — Verify the type of RDBMS. This should already be set to DB2 UDB for OS/390.
•
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.
If you have decided to modify the PeopleSoft database directly and use a user ID other than a user ID
delivered by PeopleSoft, type your user ID into this field.
•
Connect ID and Connect Password — Type your connect ID and password into these fields. Connect ID
is required for this PeopleSoft release. The connect ID and password must match the z/OS ID that you set
up in the chapter "Preparing for Installation."
See Also
"Preparing for Installation," Using Connect ID
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
Chapter 5
3. In the Process Scheduler tab verify the options listed below the example.
These should have been set correctly by the PeopleSoft installation program.
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.
•
On Microsoft Windows operating systems, set the Database Drivers (DBBIN) field to the location of the
database connectivity files on the workstation.
The example shows the default for DB2 z/OS, c:\sqllib\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.
160
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 5
Setting Up the Install Workstation
4. Select the Common tab of the Edit Profile dialog box, shown in this example:
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 6
Setting Up the Batch Environment on z/OS
This chapter discusses:
•
Understanding COBOL and the Batch Environment
•
Setting Up Your Batch Environment
•
Completing the Preinstallation Worksheet
•
Allocating z/OS Partitioned Datasets
•
Using PeopleSoft Server Transfer
•
Setting up the USS Environment Variables and Granting Access to USS Files
•
Installing SQR for z/OS
•
Binding the SQR DB2 Plan
•
Assembling PeopleTools Programs
•
Compiling and Link-Editing DB2 COBOL
•
Compiling and Link-Editing COBOL
•
Changing the IBM Enterprise COBOL Compiler Version
Understanding COBOL and the Batch Environment
This chapter describes how to compile and link PeopleSoft ASSEMBLER and COBOL batch programs, if
necessary. Note that COBOL is no longer needed for PeopleTools because the Process Scheduler is written in
C++. In addition, COBOL is not required for applications that contain no COBOL programs.
Note. We require that you maintain a "central repository" of your COBOL source code on the file server. The
multiplatform installer will place all the needed COBOL source code on your Microsoft Windows and UNIX
servers during the initial install. However, if you download any COBOL patches or make any customizations, you
should apply them to your file server. From there you can transfer the updated COBOL source code out to any
relevant application or batch servers. This approach will help you keep your COBOL source code in sync, even if
it resides on multiple machines. For Microsoft Windows operating systems, COBOL stored SQL statements are
only installed on the file server as well.
Carry out the procedures in this chapter to set up COBOL if your batch (Process Scheduler) server is on a
supported z/OS operating system. See the My Oracle Support, Certifications area for the supported COBOL
compilers for PeopleSoft PeopleTools 8.55.
If you are using IBM Enterprise COBOL for z/OS V5.1, follow the instructions in the section Using IBM
Enterprise COBOL for z/OS V5.1. If you are using IBM Enterprise COBOL for z/OS V4.2 follow the instructions
in this chapter, but skip the section Using IBM Enterprise COBOL for z/OS V5.1. Otherwise, to compile COBOL
on Microsoft Windows and UNIX operating systems, see the chapters "Installing and Compiling COBOL on
Windows" and "Installing and Compiling COBOL on UNIX."
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
163
Setting Up the Batch Environment on z/OS
Chapter 6
See Also
PeopleTools: Global Technology
My Oracle Support, Certifications
Setting Up Your Batch Environment
This chapter describes how to set up your batch environment on a z/OS database server. This process involves
compiling and linking PeopleSoft COBOL batch programs that you will use for such PeopleSoft products as
PeopleSoft Human Capital Management's Payroll or PeopleSoft Financial Management's General Ledger. The
PeopleSoft Server Transfer program creates a script that your FTP program will use to transfer files from the file
server to the database or batch server. It also creates scripts to configure the batch environment.
Note. Remember, COBOL is not required for applications that contain no COBOL programs.
The batch environment components reside in two locations: the z/OS server and UNIX System Services. COBOL,
SQR and other installation-related components reside on the z/OS server; Process Scheduler and Application
Engine components reside in UNIX System Services.
The Server Transfer process must be executed using an ID that has the authority to access both the z/OS Server
and UNIX System Services (USS). PDS and PDSE members will be created on the z/OS server, and directories
and files will be created in UNIX System Services. UNIX System Services security requires that any IDs or
USER values deployed in subsequent batch processes must belong to the same GROUP as the User ID that
initially created the libraries and files on USS. During batch execution, both permanent and temporary files are
written to UNIX Systems Services, and the ID creating these files must have the proper authority to create
directories and files. Oracle recommends that this be administered at the UNIX security GROUP level.
After you compile your COBOL components in the following steps you will only need to re-compile COBOL in
the following situations:
•
Any COBOL programs change
•
The supported COBOL compiler changes
•
You change the version of your RDBMS
•
You change your version of your operating system
•
You apply a patch or a fix
See Also
My Oracle Support, Certifications
My Oracle Support, Patches & Updates
Task 6-1: Completing the Preinstallation Worksheet
Use the preinstallation worksheet below to record site-specific information to expedite editing and transferring
COBOL and SQR files to z/OS. Try to complete it before going on to the next step. Typically, z/OS and DB2
systems administrators should be able to supply the required information.
164
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 6
Setting Up the Batch Environment on z/OS
Parameter values will be blank the first time you run the PeopleSoft Server Transfer program. You must specify
your own site-specific values. The sample values, where provided, are only suggestions. In subsequent executions
of the Server Transfer program, the program will use the values stored in %TEMP%\PSXFR.CFG, built during
the initial run. Note that %TEMP% is a system or environment variable.
Transfer Parameters
Site-Specific Value
Sample Value
1. z/OS Dataset High Level Qualifier
<enter value>
PS.HR840
<enter value>
N:\HR840
The high-level qualifier used for
PeopleSoft COBOL and SQR datasets.
Suggested Default: HLQ.ppvvv
where ppvvv is the PeopleSoft product
and release (such as HR840).
2. PeopleSoft File Server High Level
Directory
Set to PS_HOME, the directory to
which you installed the PeopleSoft
software, such as N:\HR840.
3. Target Directory for Generated Files <enter value>
N:\HR840\STAGE
The workstation directory that will
contain a variety of files generated
when you run the PeopleSoft Server
Transfer program, including file
transfers, COBOL compile JCL, and
translated SQRs (for example [ and ]
translated to \).
Suggested Default: PS_HOME\STAGE
4. File Transfer Method
<enter value>
Microsoft File Transfer Protocol (FTP)
<enter value>
Server IP name
Indicates which file transfer protocol
will be used.
Suggested Default: Microsoft FTP
5. Database Server Host/Node Name
FTP Only: Symbolic IP Name For z/OS
System
Suggested Default: IP Name of Server
If you do not use FTP, specify any
alphanumeric character in this field.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
165
Setting Up the Batch Environment on z/OS
Chapter 6
Transfer Parameters
Site-Specific Value
Sample Value
6. Database Server Login ID
<enter value>
USER1
<enter value>
//PSHR840 JOB
(PSOFT),'J',CLASS=A,MSGCLASS=
A
<enter value>
//REGION=OM,MSGLEVEL=(1,1),US
ER=BATCHID1,PASSWORD=BPSW
D1
<enter value>
// NOTIFY=&SYSUID
FTP Only: z/OS user ID used to
connect to z/OS server and create files
and directories on USS.
Note: This ID MUST be in the same
UNIX GROUP as any IDs under which
subsequent batch processing will be
executed.
Suggested Default: LOGONID
If you do not use FTP, specify any
alphanumeric character in this field.
7. Job Card Line 1
This is the first line of a job card that
will be inserted into JCL files by the
PeopleSoft Server Transfer program.
Enter // in first two positions followed
by job card information such as job
name, keyword JOB, account
information, and so on. If the job card
extends to two lines, end the first line
with a comma and complete Job Card
Line 2.
Note: Any USER= parm coded MUST
be in the same UNIX GROUP as the
Database Server Logon ID noted in
Parameter 6 above.
8. Job Card Line 2
This is the second line of a job card that
will be inserted into JCL files by the
PeopleSoft Server Transfer program.
Enter // in first two positions followed
by at least one space before continuing
to add job card information.
Suggested Default: //*
9. Job Card Line 3
This is the third line of a job card that
will be inserted into JCL files by the
PeopleSoft Server Transfer program.
Enter // in first two positions followed
by at least one space before continuing
to add job card information.
Suggested Default: //*
166
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 6
Setting Up the Batch Environment on z/OS
Transfer Parameters
Site-Specific Value
Sample Value
10. OS390z/OS/DB2 Operator ID
<enter value>
OPRID
<enter value>
PS001
<enter value>
DSNT
<enter value>
DSNn10.SDSNLOAD
This parameter is for PeopleSoft
internal use. Let it default to OPRID.
11. OS390z/OS/DB2 Table Owner ID
This is the PeopleSoft table owner ID—
the high-level qualifier for DB2 tables.
(also known as "CREATOR" in the
IBM SYS Catalog tables). If you are
using secondary authorization, this will
be your secondary authorization ID,
otherwise it will be your primary
authorization ID.
Suggested Default: PSOWNER
12. DB2 Subsystem Name
This is the DB2 Subsystem used for the
PeopleSoft application you are
currently installing (DMO or SYS).
Suggested Default: DDDD
13. DB2 System Dataset Containing
DSN Member
(n is an alphanumeric variable)
This is the DB2 system dataset that
contains member DSN.
Suggested Default:
SYS1.DB2.DDDD.DSNLOAD
14. DB2 System Dataset Containing
DSN3@ATH Member
<enter value>
DSNn10.SDSNEXIT
(n is an alphanumeric variable)
This is the DB2 system dataset that
contains member DSN3@ATH.
DSN3@ATH is a sample authorization
exit. By implementing the sample
authorization exits you can provide
group names as secondary authorization
IDs.
Suggested Default:
SYS1.DB2.DDDD.EXIT
15. DB2 System Dataset Containing
DSNTEP2 Member
<enter value>
DSNn10.RUNLIB.LOAD
(n is an alphanumeric variable)
This is the DB2 runtime system dataset
containing member DSNTEP2.
Suggested Default:
SYS1.DB2.DDDD.RUNLIB.LOAD
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
167
Setting Up the Batch Environment on z/OS
Chapter 6
Transfer Parameters
Site-Specific Value
Sample Value
16. PeopleSoft Database Name
<enter value>
PSHR840
Suggested Default: DB
17. Plan Name for PTPSQLRT via TSO <enter value>
Attach Facility
PTPSQLRT
This is DB2 Plan used by PTPSQLRT
(the COBOL/DB2 API used by
COBOL batch and process scheduler
jobs).
Suggested Default: PTPSQLRT
18. Plan Name for PTPSQLRT via Call <enter value>
Attach facility (for USS)
PTPSQLRA
Suggested Default: PTPSQLRA
19. Language Environment runtime
library (that is, CEE.SCEERUN)
<enter value>
We recommend that you ensure the LE
runtime libraries are present on the
system:
Check with System Administrator for
installation LE library name.
For example:
SYS1.CEE.SCEERUN
xxx.SCEERUNxxx.SCEERUN2
Suggested Default: CEE.SCEERUN
20. Language Environment linkedit
library (that is, CEE.SCEELKED)
<enter value>
CEE.SCEELKED
Note that in SQR in 8.44 and later uses
PM Binder CEE.SCEEBIND
Suggested Default: CEE.SCEELKED
168
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 6
Setting Up the Batch Environment on z/OS
Transfer Parameters
Site-Specific Value
Sample Value
21. COBOL System Dataset Name
Containing IGY* Members
<enter value>
Check with the System Administrator
for the installation of IBM Enterprise
COBOL V4.2.
This is the COBOL load library
containing modules used by COBOL
compiler. Its members include
IGYCASM1, IGYCINIT, and so on.
For example:
IGY.V4R2M0.SIGYCOMP
Suggested Defaults:
IGY.V4R2M0.SIGYCOMP or
IGY.V4R2M0.SIGYCOMP for ANSI
Database (EBCDIC)
IGY.V4R2M0.SIGYCOMP for
Unicode Database
Note. For PeopleSoft PeopleTools 8.54
and later, IBM Enterprise COBOL V5.1
(Version 5 Release 1) is also supported.
See Changing the IBM Enterprise
COBOL Compiler Version
22. COBOL Compiler
<enter value>
IGY51
<enter value>
SYSTEMP
Select the COBOL compiler version
from the drop-down list:
•
IGY51
IBM Enterprise COBOL V5.1
(Version 5 Release 1)
•
IGY42
IBM Enterprise COBOL V4.2
(Version 4 Release 2)
See Changing the IBM Enterprise
COBOL Compiler Version
23. System Storage Name for
Temporary Datasets
This is the storage device name used for
temporary datasets—used in sorting,
passing temporary datasets, and so
forth—that are deleted after the job
completes.
Suggested Default: SYSTEMP
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
169
Setting Up the Batch Environment on z/OS
Chapter 6
Transfer Parameters
Site-Specific Value
Sample Value
24. System Storage Name for
Permanent Datasets
<enter value>
SYSPERM
25. Assembler System Dataset
Containing STIMER
<enter value>
SYS1.MACLIB
26. Assembler Program Name
<enter value>
ASMA90
27. SQR High Level Qualifier
<enter value>
PS.HR8453.SQR
<enter value>
SQR
<enter value>
SQR840
30. Target Server Hardware Platform
<enter value>
UNIX System Services (OS390z/OS)
31. PeopleSoft Unix System Services
Home Directory
<enter value>
/u/data001/PSHR800
32. Library for DB2 CLI Load Module
(that is, DSNAOCLI)
<enter value>
DSNn10.SDSNLOAD
33. Plan Name for CLI Packages (that
is, DSNACLI)
<enter value>
DSNACLI
<enter value>
RRSAF (Resource Recovery Services
Attachment Facility)
This is the storage device name used for
permanent datasets used in dataset
allocation, such as those used to store
COBOL and SQR files.
Suggested Default: SYSPERM
This is the high-level qualifier used for
SQR datasets.
Suggested Default: PS.HR840.SQR
28. SQR Program Name Found in SQR
Load Library
This is the name of the SQR program
contained in the SQR Load Library.
Suggested Default: SQR
29. SQR Plan Name
This is the DB2 Plan name assigned for
SQR.
Suggested Default: DBCALLS
Suggested Default: /u/data001/dbname
(n is an alphanumeric variable)
Suggested Default: DSNACLI
34. Attachment Type for ODBC to
Connect to DB2
Suggested Default: RRSAF
170
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 6
Setting Up the Batch Environment on z/OS
Transfer Parameters
Site-Specific Value
Sample Value
35. HFS path to top level of JDK
product
<enter value>
/usr/lpp/java/J1.7
This will provide the value for the
JDK_HOME environment variable in
the psconfig.sh file.
Suggested Default: /usr/lpp/java/J1.7
Task 6-2: Allocating z/OS Partitioned Datasets
Allocate a z/OS partitioned dataset as HLQ.PSvvv.CNTL, where HLQ is any high-level dataset qualifier, PS is a
constant, and vvv is the current release of your PeopleSoft software (such as 853).
File attributes are: FB, LRECL=80,BLKSIZE=6160, Dir Blks 5, SPACE (Primary 15 Tracks, Secondary 5
Tracks). This dataset will be used to transfer allocation JCL.
To complete allocating the datasets:
1. Transfer PS_HOME\SRC\CBL\MVS\PSLIBCBL.JCL to HLQ.PSvvv.CNTL(PSLIBCBL).
2. Transfer PS_HOME\SRC\CBL\MVS\PSLIBSQR.JCL to HLQ.PSvvv.CNTL(PSLIBSQR).
3. Log on to z/OS and edit PSLIBCBL and PSLIBSQR to reflect the appropriate values for your site as follows:
a. Add a job card.
b. Change all occurrences of $PSHLQ$ to the z/OS Dataset High Level Qualifier determined in the
preinstallation worksheet.
c. Change all occurrences of $SYSPERM$ to the System Storage Name for Permanent Datasets value
determined in the preinstallation worksheet.
d. Change all occurrences of $SQRHLQ$ to the z/OS Dataset High Level Qualifier determined in the
preinstallation worksheet.
See Completing the Preinstallation Worksheet.
4. Submit (PSLIBCBL) and (PSLIBSQR) to allocate files.
Task 6-3: Using PeopleSoft Server Transfer
This section discusses:
•
Understanding PeopleSoft Server Transfer
•
Running the PeopleSoft Server Transfer Program
•
Transferring Files to Host Manually
•
Mapping PeopleSoft Installation Directories to z/OS
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
171
Setting Up the Batch Environment on z/OS
Chapter 6
Understanding PeopleSoft Server Transfer
The PeopleSoft Server Transfer program simplifies editing and transferring COBOL and SQR files to z/OS. Precompile, Compile, Linkedit, binds, and Process Scheduler-initiated COBOL and SQR jobs are ready to submit
following the file transfer, assuming the worksheet values you enter are correct.
Note. Remember, before you can run the Server Transfer program to set up a batch server on z/OS, you need to
have run the PeopleSoft Installer, as described in the chapter "Using the PeopleSoft Installer." Run it on a
Microsoft Windows machine, making sure to select all of the PeopleSoft servers. This Microsoft Windows
machine will then function as your file server, from which you can run Server Transfer.
The PeopleSoft Server Transfer program performs the following functions:
•
Generates a file containing transfer commands to transfer files to z/OS and UNIX System Services (USS).
This file is named PSFTXFR.TXT for transferring files to z/OS using FTP.
•
Generates COBOL compile JCL — program preparation JCL.
•
Edits various JCL and PRC files to site-specific standards using values from the transfer parameters specified
in the PeopleSoft Server Transfer program.
•
Translates [ and ] characters to a \ (backslash) to correct an ASCII-to-EBCDIC translation problem that occurs
during the transfer of SQR files.
Later in this chapter you will learn how workstation file directories relate to z/OS partitioned datasets.
See Mapping PeopleSoft Installation Directories to z/OS.
Before running the PeopleSoft Server Transfer program, ensure that an environment variable (%TMP%) is set to a
"temporary" directory to which you have write access. Oracle recommends using C:\temp for this use.
The transfer program writes the following two files to the %TMP% directory:
•
PSXFR.LOG — a log file that summarizes the program's execution.
•
PSXFR.CFG — a configuration file that stores the parameters you selected.
Note. The PeopleSoft Server Transfer program writes the above files to the %TMP% directory, or to the
%TEMP% directory if the %TMP% environment variable is undefined.
See "Using the PeopleSoft Installer."
Note. In PeopleTools 8.4 and above, the Server Transfer program is used only to transfer files to your batch
server. On UNIX or Windows, to install files to your application server, file server, web server, and so on, you
should use the PeopleSoft Installer.
Task 6-3-1: Running the PeopleSoft Server Transfer Program
To run the PeopleSoft Server Transfer program:
172
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 6
Setting Up the Batch Environment on z/OS
1. Start PeopleSoft Server Transfer.
Enter the following path into the Run dialog box:
PS_HOME\BIN\CLIENT\WINX86\pstrans.exe
Alternatively, select the Server Transfer shortcut, if you elected to create a Program Group during the
PeopleSoft PeopleTools installation.
The PeopleSoft Server Transfer screen appears, as shown in this example, which contains all of the
parameters whose values you should have determined while filling out the preinstallation worksheet.
Entering transfer parameters in the PeopleSoft Server Transfer dialog box
2. Enter the appropriate value for each parameter.
Using the preinstallation worksheet you completed earlier, enter the parameters values describing how you
want to install the PeopleSoft batch environment on your database server. Some of the parameter values may
already exist either as default values or as values from a previous execution of the Server Transfer program.
To select an individual row, just click it. To enter or change a particular parameter value, either select from
predefined values in a drop-down list or enter the values manually if there is no drop-down list.
Note. You must specify a value for each edit field. If you are not sure what value to use, type in the default
suggested by Oracle for PeopleSoft software (see the preinstallation worksheet for a list of defaults) and edit
the parameter value following the file transfer on z/OS.
For parameters that require a directory path, you may enter it directly. If you don't know the exact location,
click Browse to select the directory from the Select Directory dialog box. The Browse button is available
when you click in a field that requires a directory path.
3. Enter the appropriate value for Host/Node Login ID Password. This value should be the password for the
Host/Node Name specified as parameter number 5 in the Server Transfer panel.
This password is mandatory regardless of your database platform or site specifications. Microsoft's FTP
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
173
Setting Up the Batch Environment on z/OS
Chapter 6
software requires a password.
4. Once you enter all the correct parameter values for your site, click OK. (If instead you want to clear all of
your entries and start over, press Reset. To close this instance of the PeopleSoft Server Transfer, press
Cancel.)
The PeopleSoft Server Transfer prepares the files for transfer, which can take from a few seconds to a few
minutes, depending on the number of files and the type of processing required.
The PeopleSoft Server Transfer program will generate a number of files that will be located in the Target
Directory for Generated Files that you specified previously.
5. In the PeopleSoft Server Transfer Output window, if you want to verify that the Transfer program created all
the proper files, click the Display Log button.
The Display Log button calls the PSXFR.LOG in your %TMP% directory (or %TEMP% directory if
%TMP% is undefined) and displays it in Microsoft Notepad. PSXFR.LOG provides summary information
about the transfer program's execution that can be helpful for identifying potential errors and inconsistencies.
It contains the following sections:
•
SELECTED PARAMETERS: Shows the parameters you selected from the PeopleSoft Server Transfer
main window.
•
SUMMARY OF SELECTED FILES: Shows which files—and how many of them—will be transferred. It
also shows which directory they were copied from and their new location.
•
FILE TRANSFER NOTES: Shows important details regarding your transfer process, such as the command
line option and where log files are located.
Note. Only click Close if you want to dismiss the PeopleSoft Server Transfer Output window and transfer
the files manually from the command line.
6. Click the Transfer Now button to begin the transfer process. This button will launch the file transfer method
that you selected on the server transfer main screen.
Note. The Transfer Now button assumes that the destination partitioned datasets exist. See "Allocating z/OS
Partitioned Datasets."
7. When the transfer has completed, the FTPOUT.LOG will display in Notepad. You should review this file for
any errors that may have occurred during the transfer. The file is located in the Target Directory for Generated
Files that you specified previously.
8. Close Notepad and press the CLOSE button on the PeopleSoft Server Transfer Output Panel.
Note. If your transfer is unsuccessful or you would rather transfer the files manually, read the following
section.
The following table summarizes the files generated during the use of the PeopleSoft Server Transfer utility, in the
order in which they are generated, along with their locations and a description.
File Name
Location
Contents
PSXFR.CFG
%TMP%
Configuration file generated by the
PeopleSoft Server Transfer Utility. It
contains the parameters entered in a
somewhat cryptic format.
174
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 6
Setting Up the Batch Environment on z/OS
File Name
Location
Contents
PSXFR.LOG
%TMP%
Summary file generated by the
PeopleSoft Server Transfer Utility. It
contains a summary of the parameters
entered, the files that will be
transferred, and instructions on how to
manually transfer the files, if you
choose to do so later.
PSFTXFR.TXT
The Target Directory for Generated
Files that you specified previously.
A Microsoft FTP command file that
contains the FTP statements to be
executed to transfer the files. This file
is only generated if you selected the
Microsoft FTP file transfer protocol
option.
FTPEXEC.BAT
The Target Directory for Generated
Files that you specified previously.
The .bat file that calls either the
Microsoft FTP command file, from
which the FTP process is initiated. The
PeopleSoft Server Transfer Utility will
initiate this batch file if you select the
Transfer Now option.
FTPOUT.LOG
The Target Directory for Generated
Files that you specified previously.
This is the FTP log file generated by
the FTP utility that details the transfer
results for each file processed.
Task 6-3-2: Transferring Files to Host Manually
From a command line utility (DOS shell) in Microsoft Windows, transfer application files to z/OS using the
transfer/send file generated by the PeopleSoft Server Transfer program. For the Microsoft FTP file transfer
protocol, the file containing transfer commands is in PS_HOME\STAGE and is called PSFTXFR.TXT.
You can initiate either Server Transfer by executing the FTPEXEC.BAT file in PS_HOME\STAGE. Allow at
least 45 minutes to complete the file transfer. If the transfer fails:
•
Make sure the z/OS datasets to which the files are transferred have been allocated.
•
Check whether a z/OS dataset is underallocated or allocated on a volume with insufficient space.
•
Verify that the Database Server Login ID specified in Parameter 6 has write access to z/OS and UNIX System
Services.
Task 6-3-3: Mapping PeopleSoft Installation Directories to z/OS
The following tables shows the mapping between workstation files and the suggested z/OS target datasets. The
root directory is assumed to be PPVVV, which denotes the high-level PeopleSoft directory, such as \HR840. Each
table lists the files, datasets, and descriptions for a subdirectory of PPVVV.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
175
Setting Up the Batch Environment on z/OS
Chapter 6
Mapping in subdirectory \SRC\CBL\BASE:
Files
z/OS Dataset
Description
??P*.CBL
HLQ.PSVVV.SRCLIB
COBOL programs
??C*.CBL
HLQ.PSVVV.COPYLIB
COBOL copy members
Mapping in subdirectory \SRC\CBL\MVS:
Files
z/OS Dataset
Description
??P*.CBL
HLQ.PSVVV.SRCLIB
z/OS specific programs
??C*.CBL
HLQ.PSVVV.COPYLIB
z/OS COBOL copy members
*.ASM
HLQ.PSVVV.SRCLIB
Assembler programs
*.JCL
HLQ.PSVVV.JCLLIB
Compile, bind, Process Scheduler jobs
*.PRC
HLQ.PSVVV.PROCLIB
Procs for compile, bind, assemble
*.JCT
/u/datax/psvvv/appserv/prcs/shelljcl
JCL Shells for COBOL and SQR
Processes
Files
z/OS Dataset
Description
*.SQR
HLQ.PSVVV.SQRSRC
Application SQRs
*.SQC
HLQ.PSVVV.SQRINC
Application SQR include members
SQRPARMS.PAR
HLQ.PSVVV.PARMLIB
SQR parameter file
SQRSAMP.JCL
HLQ.PSVVV.JCLLIB
Sample SQR JCL
SQRPROC.PRC
HLQ.PSVVV.PROCLIB
SQR cataloged procedures
Files
z/OS Dataset
Description
??DDL.SQL
HLQ.PSVVV.DDLLIB
DDL script files used to build
PeopleSoft database in the chapter
Creating a Database
??DDLU.SQL
HLQ.PSVVV.DDLLIB
Script files for Unicode databases
Mapping in \SQR subdirectory:
Mapping in \SCRIPTS subdirectory:
176
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 6
Setting Up the Batch Environment on z/OS
Mapping in \APPSERV\PRCS subdirectory:
Files
z/OS Dataset
Description
*.IN
/u/datax/psvvv/appserv
PSADMIN program utility files
psprcsunix.val
/u/datax/psvvv/appserv/prcs
Process Scheduler value Validation file
Mapping in \BIN\SERVER subdirectory:
Files
z/OS Dataset
Description
*.*
/u/datax/psvvv/bin
Process Scheduler executables for USS
Note. The \SRC\CBL\MVS directory contains files specifically for the DB2 for z/OS platform. Certain files will
appear in both the \SRC\CBL\BASE and \SRC\CBL\MVS directories. The *.CBL files in the \SRC\CBL\BASE
directory will be transferred first, followed by the *.CBL files in the \SRC\CBL\MVS directory. As a result, the
z/OS-specific files will overwrite the generic files. In other words, the order in which files are FTPed to the server
does matter. The PeopleSoft Server Transfer program FTPs the files to the server in the correct order.
Task 6-4: Setting up the USS Environment Variables and Granting
Access to USS Files
Before installing SQR for z/OS, you need to set up USS environment variables by executing the psconfig.sh shell
script, and grant access to specific libraries in UNIX System Services by executing the psmv.sh shell script.
To execute the psconfig.sh and psmv.sh shell scripts:
1. Locate the files psconfig.sh and psmv.sh in USS Home directory /u/datax/ppvvv.
This is the same directory specified in the preinstallation worksheet, parameter 30. Make this directory your
current working directory.
2. Grant execute authority to the file by entering the following at the prompt:
chmod 755 psmv.sh
3. Execute the scripts by entering psconfig.sh and psmv.sh at the prompt.
Task 6-5: Installing SQR for z/OS
To install SQR in the designated partitioned dataset, you need to run the INSTALLSQR.SH shell script. The shell
script performs the following tasks:
•
Copies all SQR installation binary files from the HFS directory PS_HOME/bin/sqr into the designated SQR
sequential data sets.
•
Submits HLQ.PPVVV.JCLLIB (RECVSQR) that will use IBM's RECV utility to migrate all the binaries from
the sequential data set to the designated SQR partitioned dataset.
To execute the installsqr.sh shell script:
1. Change directory to the USS Home directory /u/datax/ppvvv. This is the same directory specified in the
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
177
Setting Up the Batch Environment on z/OS
Chapter 6
preinstallation worksheet (item 30).
2. Enter installsqr.sh at the prompt.
When the shell script submits the JCL to unpack all the SQR binaries from the installation sequential data set,
review the status of the JCL from TSO to verify that all steps using the RECV utility have successfully
completed with return code of 0.
Task 6-6: Binding the SQR DB2 Plan
Once SQR is installed, you have to run the DSN subcommand BIND to build an application plan for SQR. All
DB2 programs require an application plan to allocate resources and to support SQL requests made during
execution. The keywords and parameters you should use when exercising the DSN BIND commands follow.
Refer to the IBM DB2 Command and Utility Reference Manual for further information on BIND.
To create the DB2 Plan for SQR, submit the following JCL job:
HLQ.PSVVV.JCLLIB(PSBNDSQR)
Note. To execute an XPLINK program, the SCEERUN2 as well as the SCEERUN data set must be in the z/OS
program search order (see the {_PLIB_PREFIX} environment variable). The following data sets are also used:
The data sets {_PLIB_PREFIX}.SCEERUN and {_PLIB_PREFIX}.SCEERUN2 contains the runtime library
programs. These data sets are listed here for information only, to assist in identifying the correct data sets to be
added to the z/OS program search order. The default value is "CEE".
Task 6-7: Assembling PeopleTools Programs
You need to assemble the PeopleSoft program PTPSQLTM. PTPSQLTM, called by PTPSQLRT, collects timeinterval data to produce the statistics report.
In z/OS, submit the following job:
HLQ.PPVVV.JCLLIB (PSASM)
On job output, the expected return code is 0 or 4.
Note. In the catalogued procedure PSASM, the ASM step EXEC statement contains the assembler program
specified during the PeopleSoft Server Transfer program. $ASMLIB$ is replaced by the "Assembler Program
Name" transfer parameter. The expected assembler program name is ASMA90. However, IEV90 may also be
used, but the SYSLIN DD statement in the ASM step must be commented first to be assembled successfully.
Task 6-8: Compiling and Link-Editing DB2 COBOL
Precompile, compile, and link-edit PTPSQLRT (PeopleSoft's COBOL/DB2 API) as follows:
•
Submit HLQ.PPVVV.JCLLIB(PSCOB*). Acceptable return codes are 0 and 4 for pre-compiles and compiles,
and 0 for the link-edit step.
•
PSCOBDA: for DB2 precompile, compile and linkedit of program PTPSQLRT for Native CAF for USS.
•
PSCOBDE: for DB2 precompile, compile and linkedit of program PTPSQLRT for TSO CAF.
•
PSCOBNET: for compile and linkedit COBOL program PTPNETRT for Native CAF for USS.
178
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 6
Setting Up the Batch Environment on z/OS
Common compile errors include:
•
Users inadvertently introducing tab characters into source code while viewing it using workstation editors
before file transfer. Check to see if you have X'05' (or other odd hex values) in the z/OS source.
•
Failure to transfer all the BASE and z/OS copy members from the file server, or perhaps overwriting the z/OS
versions with the BASE versions. Check PSFTXFR.TXT to see the order in which the files were transferred.
•
Failure in LINKEDIT of PSCOBNET with error message "Attempt to get file status for an HFS file failed..."
usually results when the User ID under which the PSCOBNET job is running does not have read access to the
necessary USS file.
Note. Oracle delivers procedure library members PSCOBD, PSCOBDA, and PSCOBDE, which set the DB2
precompiler options DATE(ISO) and TIME(ISO). Do not change these settings, because PeopleSoft
applications rely on the ISO format for date and time processing.
Task 6-9: Compiling and Link-Editing COBOL
Submit HLQ.PPVVV.JCLLIB(PSCOB*) to compile COBOL programs.
Note. Previous versions of PSCOB had to be manually divided into multiple jobs if they contained more than 125
COBOL programs to compile. This step is now done by the Server Transfer process, which will create the
PSCOB* members.
Next, serialize compile jobs to avoid problems associated with concurrent PDS updating, and submit the PSCOB
job(s). Acceptable return codes are 0 or 4 for pre-compiles and compiles, and 0 for the link-edit step.
Common compile errors include:
•
Users inadvertently introducing tab characters to source code while viewing them using workstation editors
before file transfer. Check to see if you have X'05' (or other odd hex values) in the z/OS source.
•
Failure to transfer all the BASE and z/OS copy members from the file server, or perhaps overlaying the z/OS
versions with the BASE versions. Check PSFTXFR.TXT to see the order in which the files were transferred.
Task 6-10: Changing the IBM Enterprise COBOL Compiler Version
After you have run the PeopleSoft Server Transfer program, pstrans.exe, use this procedure if you want to change
the version of the IBM Enterprise COBOL compiler manually.
1. Locate the following procs in the COBOL PROCLIB (that is, HLQ.PPVVV.PROCLIB):
•
For IBM Enterprise COBOL for z/OS V5.1, PSSTCCN5 and PSOPTCN5
• For IBM Enterprise COBOL for z/OS V4.2, PSSTCCN4 and PSOPTCN4.
2. Make backup copies of PSSTCCOB and PSOPTCOB.
3. To use IBM Enterprise COBOL for z/OS V5.1, perform these steps on TSO:
a. Copy PSSTCCN5 to PSSTCCOB, overwriting the proc PSSTCCOB with PSSTCCN5.
b. Copy PSOPTCN5 to PSOPTCOB, overwriting the proc PSOPTCOB with PSOPTCN5.
4. To use IBM Enterprise COBOL for z/OS V4.2, perform these steps on TSO:
a. Copy PSSTCCN4 to PSSTCCOB, overwriting the proc PSSTCCOB with PSSTCCN4.
b. Copy PSOPTCN4 to PSOPTCOB, overwriting the proc PSOPTCOB with PSOPTCN4.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
179
Setting Up the Batch Environment on z/OS
Chapter 6
5. Compile COBOL programs as done previously; that is, run PSCOBDA.JCL, PSCOBDE.JCL, and
PSCOBNET.JCL.
6. To confirm the COBOL compiler version, review the JCL output.
The COBOL compiler version 4.2 or 5.1 is included in the JOB output.
180
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
This chapter discusses:
•
Understanding Database Creation
•
Planning Your Installation
•
Transferring DDL Scripts to z/OS
•
Creating PS.PSDBOWNER Table
•
Granting Privileges on PS.PSDBOWNER
•
Granting Privileges to Owner ID
•
Creating DB2 Databases, Storage Groups, and Tablespaces
•
Creating Tables
•
Configuring the DB2 Connect Gateway
•
Creating Data Mover Import Scripts
•
Running Data Mover Import Scripts
•
Checking the Log Files and Troubleshooting
•
Creating Indexes
•
Reviewing Patch Application
•
Updating Database to Latest PeopleTools Release
•
Running the DB2 RUNSTATS Utility
•
Creating PeopleSoft Views
•
Building Temporary Tables
•
Creating PeopleSoft Triggers
•
Running Additional Data Mover Scripts
•
Installing a Multilingual PeopleTools System Database
•
Running SQR Reports
•
Updating PeopleSoft System Tables
•
Binding DB2 Plans
•
Running VERSION Application Engine Program
•
Changing the Base Language
•
Checking the Database
•
Running Alter Audit
•
Disabling %UpdateStats
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
181
Creating a Database
Chapter 7
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.
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.
See Also
"Preparing for Installation," Planning Database Creation
"Setting Up the Install Workstation"
Planning Your Installation
This section discusses:
•
Using %UpdateStats
•
Using Temporary Tables
Note. Two features that impact how you install your PeopleSoft database are the %UpdateStats MetaSQL
function, and the Application Designer Object Type of "Temporary Table."
Using %UpdateStats
%UpdateStats is an optional feature that lets you invoke the DB2 Utility RUNSTATS from within an Application
Engine or COBOL process. Consider the following if you plan to use %UpdateStats:
•
You can initiate RUNSTATS dynamically via the IBM stored procedure DSNUTILS. Before you can use
%UpdateStats, the stored procedure DSNUTILS must be configured in the DB2 subsystem in which you run
the PeopleSoft applications. If %UpdateStats is enabled but DSNUTILS is not in place, a processing error will
result. Please refer to your IBM Systems documentation for instructions on enabling and configuring the
DSNUTILS stored procedure.
•
Using %UpdateStats with COBOL requires modifications to some delivered PeopleSoft code. These
modifications are described in the PeopleTools: Data Management product documentation.
•
%UpdateStats can be enabled or disabled based on the DBFLAGS Process Scheduler configuration parameter.
182
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
Disabling %UpdateStats will cause the functionality to be bypassed, without causing any processing errors.
Note that the default setting for DBFLAGS for UNIX and Windows Process Schedulers is ON
(DBFLAGS=0). The default setting for USS is DBFLAGS=0 (Enable Second DB Connection).
•
The %UpdateStats MetaSql targets a table, whereas the DB2 z/OS RUNSTATS utility processes at the
tablespace level. This can present a performance issue with the default PeopleSoft database installation
strategy, which combines multiple tables into a single tablespace. To alleviate this issue and assist you in
installing your database to optimally utilize the %UpdateStats feature, consider using the PeopleSoft
Tablespace DDL Automation Tool (PSTAAT). PSTAAT can be used to better optimize the mapping of tables
among tablespaces and databases.
See Appendix: "Using The PeopleSoft Tablespace DDL Automation Assistance Tool" for more details.
The scripts that are required for PeopleSoft products are listed in the section "Transferring DDL Scripts to z/OS".
Using Temporary Tables
Temporary tables are an object type defined in Application Designer to support Application Engine concurrent
processing. For PeopleSoft installations, we refer to these objects as temporary tables, but to the DB2 z/OS
database they will be defined as "permanent" SQL tables. Each temporary table defines a base table from which
additional instances or copies of the base table are scripted and physically created on your DB2 z/OS PeopleSoft
database. Only the definition of the base table is stored in Application Designer. The actual number of instances is
governed by a global value for Online concurrent processes, and a value defined either at a Global level (for
EPM) or at the Application Engine Process Level for batch processes.
See PeopleTools: Application Engine.
In an attempt to limit the number of potentially unused objects created on your database, we have reduced the
number of temporary table instances to a minimum setting. Depending on the actual products you are installing,
your processing characteristics and workloads, you may need to modify the number of temporary table instances
to improve performance. This will become evident if you have a number of processes queuing to use a limited
number of temporary table instances. The actual scripting and creation of the temporary tables are performed as a
separate step in the installation process, so you may intervene during this process to increase the number of
temporary table instances if you feel you have substantial batch processing workloads and/or a large volume of
online transaction processing. Temporary tables can be regenerated at any time in the life of your database, so you
don't need to determine the exact number of instances that will be right for your environment at installation time.
When the number of instances of the temporary tables within the PeopleSoft application is changed, all temporary
tables should be regenerated. The same values in the PeopleTools tables that are used to determine how many
temporary tables instances should be created, are also used to determine how many should be available to an
Application Engine process. The expectation is that the number of instances defined within the PeopleTools tables
actually exists on the database. A later task in this chapter describes how to create the temporary tables.
Lastly, since each instance of a base temporary table is not defined within the PeopleTools tables, database and
tablespace information is not stored for these instances. When the DDL is generated to create the base temporary
table and its instances, each instance is put in the same database and tablespace as the base temporary table. To
avoid concurrency issues and obtain optimal performance, each temporary table instance should also be assigned
to its own unique tablespace, particularly when the temporary table is also the object of the %UpdateStats
functionality, described earlier. Use the PeopleSoft Tablespace DDL Automation Assistance Tool (PSTAAT) to
put the base temporary table and each of its instances in separate tablespaces. See the appendix "Using the
PeopleSoft Tablespace DDL Automation Assistance Tool" for more details.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
183
Creating a Database
Chapter 7
Task 7-1: Transferring DDL Scripts to z/OS
If you have set up your batch environment on the z/OS mainframe following the instructions in the chapter
"Setting Up the Batch Environment on z/OS," these files have already been transferred and you can skip this step.
All DDL script files to create the DB2 objects for the PeopleSoft database reside in the PS_HOME\SCRIPTS
directory of your file server (where PS_HOME is the root directory where PeopleSoft software has been installed
in your file server). This task requires that you manually transfer these files to z/OS. Each of these files must be
customized with site-specific values and standards before you submit them either through SPUFI or DSNTEP2.
To transfer DDL scripts:
1. Allocate a partitioned dataset named HLQ.PSvvv.DDLLIB on z/OS, where HLQ is any high-level dataset
qualifier, PS is a constant, and vvv is the current release of your PeopleSoft software (such as 800).
File attributes are: FB, LRECL=80, Dir Blks 10, SPACE (Primary 800 Tracks, Secondary 300 Tracks). For
example, DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160) SPACE=(TRK,(800,300,10)).
184
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
2. Transfer the following files from the PS_HOME\SCRIPTS directory, as a member of the
HLQ.PSvvv.DDLLIB PDS library using Microsoft File Transfer Protocol (FTP).
This table lists and gives a brief description for each script, and defines the naming convention.
Files in the SCRIPTS subdirectory
Description
XXDDL.SQL†
This script contains all the DDL statements to create database,
storage groups, and table spaces
XXDDLU.SQL†
This script contains all the DDL statements to create database,
storage groups, and table spaces for a UNICODE database.
PSDDL.SQL
This script contains the DDL statements to create the
PS.PSDBOWNER table.
TBDDL.SQL
This script contains all the CREATE TABLE statements for the
product line.
TBDDLU.SQL
This script contains all the CREATE TABLE statements for the
product line for a UNICODE database.
IXDDL.SQL
This script contains all the CREATE INDEX statements for the
product line.
† Substitute these product line values for XX:
•
Use CS for PeopleSoft Campus Solutions.
•
Use CR for PeopleSoft Customer Relationship Management.
•
Use LM for PeopleSoft Enterprise Learning Management.
•
Use PF for PeopleSoft Enterprise Performance Management.
•
Use EP for PeopleSoft Financials/Supply Chain Management.
•
Use EA for PeopleSoft Financials/Supply Chain Management Argentina.
•
Use EB for PeopleSoft Financials/Supply Chain Management Brazil.
•
Use HC for PeopleSoft Human Capital Management.
•
Use PA for PeopleSoft Portal Solutions.
Task 7-2: Creating PS.PSDBOWNER Table
You can skip this step if a PS.PSDBOWNER table already exists in the same DB2 subsystem as your new
database. This would be the case if you already have an existing PeopleSoft database in the target DB2
subsystem. You will have one PS.PSDBOWNER table per subsystem.
Edit and execute HLQ.PSvvv.DDLLIB(PSDDL) using SPUFI or DSNTEP2. The PS.PSDBOWNER must exist in
each DB2 subsystem where PeopleSoft databases will be installed and it is the only table that Oracle provides for
PeopleSoft software where an OWNERID cannot be customized. PeopleSoft PeopleTools applications select from
this table to obtain the Owner ID and Database Name information during the PeopleSoft Sign-on process.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
185
Creating a Database
Chapter 7
Note. For UNICODE databases, it is not necessary to use the CCSID=UNICODE option of the Create Database
statement when creating the PSOWNRDB (this contains the PS.PSDBOWNER table). IBM supports the use of
Unicode, EBCDIC, and ASCII tables in the same subsystem, and the ability to join data using any of these
encoding schemes in DB2 for z/OS New Function Mode.
Task 7-3: Granting Privileges on PS.PSDBOWNER
Grant the ALL authority to the table owner ID used for the PeopleSoft database:
GRANT ALL ON TABLE PS.PSDBOWNER TO <Owner_ID> WITH GRANT OPTION;
Task 7-4: Granting Privileges to Owner ID
Before creating your DB2 databases, make sure the owner ID has authorization to use the following DB2
resources:
Grant use of bufferpool to the Owner ID:
GRANT USE OF BUFFERPOOL BP1 TO <Owner_ID>;
GRANT USE OF BUFFERPOOL BP2 TO <Owner_ID>;
GRANT USE OF BUFFERPOOL BP3 TO <Owner_ID>;
GRANT USE OF BUFFERPOOL BP32K TO <Owner_ID>;
Task 7-5: Creating DB2 Databases, Storage Groups, and
Tablespaces
This section discusses:
•
Understanding DB2 Databases, Storage Groups, and Tablespaces
•
Customizing the Database Name
•
Working with Tablespaces
Understanding DB2 Databases, Storage Groups, and Tablespaces
Oracle delivers a generic script to create the DB2 for z/OS storage groups, database shells and tablespaces. Unless
you are installing the System (SYS) or Demo (DMO) database using the generic defaults in the script, you need to
edit various parameters to comply with the standard at the customer site. These parameters include:
•
Storage group names and volumes (if you have already created stogroups, you may comment out the
statements in the script to create them)
•
Database names
•
Tablespace names
•
Bufferpool names
•
Owner_ID
186
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
Note. There is a SET CURRENT SQLID = 'OWNER#ID' statement in the script. It is recommended that the
Current SQLID be set to the ID that will be used to "own" all the database tables (even though no tables are
being created in this step). This will either be the Secondary Authorization ID, if using Secondary
Authorization ID processing, or the Primary Authorization ID, if not. (In the scripts to create the tables found
in the next step, this value is referred to as OBJ#OWNER). The "CREATOR" field in the
SYSIBM.SYSTABLESPACE catalog table will be the same value as the "CREATOR" field in the
SYSIBM.SYSTABLES catalog table. Having these two fields being the same value will facilitate running the
optional SQR SETDBNAM and creating the temporary tables, mentioned later in the chapter.
The following instructions detail where to make these edits as necessary.
Using SPUFI, DSNTEP2, or an equivalent product, create your DB2 objects (that is, databases, storage groups,
and tablespaces) using the HLQ.PSvvv.DDLLIB(XXDDL/XXDDLU) file.
Use the XXDDL version for the non-Unicode installation, and the XXDDLU version for Unicode installation.
The following table shows a few examples of the product identifiers in HLQ.PSvvv.DDLLIB(XXDDL/XXDDLU):
Product
Identifier
PeopleSoft Customer Relationship Management
CR
PeopleSoft Enterprise Performance Management
PF
PeopleSoft Financials/Supply Chain Management
EP
PeopleSoft Human Capital Management
HC
Task 7-5-1: Customizing the Database Name
This section discusses:
•
Understanding Database Name Customization
•
Editing the XXDDL.SQL or XXDDLU.SQL Script
Understanding Database Name Customization
You can customize the database name found in the CREATE DATABASE statements to your organization
standards. However, make note of the database names you change because you will have to make corresponding
changes to the DDL scripts for creating the tables.
Because of the large number of objects delivered in the database, and to facilitate performance, multiple physical
databases are deployed to contain the single, logical PeopleSoft database. The objects in the physical databases
are unified into one logical database by sharing the same Owner ID (the CREATOR field in
SYSIBM.SYSTABLES). For consistency, and to facilitate editing, the physical database names all share a
common root value of seven characters. A unique eighth character is appended to the root name, resulting in a
distinct database name.
As an example, the Human Capital Management product is delivered with a "root" value of PSHRDMO for the
database name. The actual physical database names include PSHRDMO, PSHRDMOB, PSHRDMOH,
PSHRDMOP, PSHRDMOT, PSHRDMO1 and PSHRDMO2.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
187
Creating a Database
Chapter 7
The PeopleSoft applications contain a substantial number of DB2 objects, and we do not recommend putting all
these objects into a single database. Doing so will require an inordinately large EDM pool size, and will produce
undesirable results in your DB2 system. Note also that the PTPRC tablespace is assigned to its own database
PSxxDMOT. This tablespace contains all the tables used by Process Scheduler. Combining these tables in one of
the other databases could potentially cause the lockout of other processes, such as DB2 utilities running
concurrently with Process Scheduler.
Beginning with PeopleSoft PeopleTools 8.53, the tablespace PSIMAGE2 is delivered and is assigned to its own
database PSXXDMOX, where XX refers to application-specific product identifiers. This tablespace contains
tables with PeopleSoft Long data types.
See PeopleTools 8.53 Release Notes, My Oracle Support.
See the information on creating field definitions in the PeopleTools: Application Designer Developer's Guide
product documentation.
Finally, note that several tablespaces specify LOCKSIZE ROW. If any tables we deliver within these tablespaces
are moved, they should only be moved to a tablespace that was defined with row-level locking.
Note. Use the PeopleSoft Tablespace DDL Automation Assistance Tool (PSTAAT) to customize the physical
database names that constitute your logical PeopleSoft database. See the appendix "Using the PeopleSoft
Tablespace DDL Automation Assistance Tool" for more details.
Editing the XXDDL.SQL or XXDDLU.SQL Script
To edit the XXDDL.SQL (or XXDDLU.SQL for Unicode) script, edit the CREATE STOGROUP statements to
site-specific values. Storage group name defaults are PSSGTSxx and PSSGIXxx for tablespaces and index spaces,
respectively, but you can change them to comply with your organization's standards. You may also comment out
the CREATE STOGROUP statements if you have already established Stogroups on your DB2 subsystem, but you
will still need to edit the CREATE TABLESPACE statements with your site-specific Stogroup value.
Verify that your XXDDL.SQL or XXDDLU.SQL script includes the following statements:
Note. You can also copy these statements from the PTDDL.SQL (EBCDIC) or PTDDLU.SQL (Unicode) scripts.
•
To create the PSXXDMOX database for EBCDIC databases:
CREATE DATABASE PSXXDMOX STOGROUP PSSGTSPT ;
COMMIT;
To create the PSXXDMOX database for Unicode databases:
CREATE DATABASE PSXXDMOX STOGROUP PSSGTSPT CCSID UNICODE;
COMMIT;
•
To grant permissions to the PSXXDMOX database, for EBCDIC or Unicode databases:
GRANT DBADM ON DATABASE PSXXDMOX TO OBJOWNER;
COMMIT;
SET CURRENT SQLID='OBJOWNER';
COMMIT;
•
To create the PSIMAGE2 tablespace, for EBCDIC or Unicode databases:
CREATE TABLESPACE PSIMAGE2 IN PSXXDMOX
USING STOGROUP PSSGTSPT PRIQTY 172800 SECQTY 8640
FREEPAGE 0 PCTFREE 10
188
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
SEGSIZE 32 BUFFERPOOL BP32K LOCKSIZE ANY CLOSE NO ;
COMMIT;
We highly recommend that you use standard PeopleSoft tablespace names when installing the demonstration
database to simplify the installation process.
The script contains the GRANT DBADM commands for each DB2 database you plan to create for your
PeopleSoft database. This is the easiest way to grant the required privileges to the owner ID. This enables the
owner ID to perform other tasks, such as starting and stopping the PeopleSoft database, and running DB2 utilities
such as RUNSTATS.
Note. References to owner ID in this document, and in the accompanying scripts, refer to the DB2 Secondary
Authorization ID if using Secondary Authorization ID processing, or to the DB2 Primary Authorization ID, if not.
The options are to grant DBADM to the Owner ID or to issue individual grants for the following:
•
Grant bind capability to the Owner ID:
GRANT BINDADD TO <Owner_ID>;
•
Grant create tablespace capabilities to the Owner ID:
GRANT CREATETS ON DATABASE <database_name> TO <Owner_ID>;
•
Grant create table capability to the Owner ID:
GRANT CREATETAB ON DATABASE <database_name> TO <Owner_ID>;
Note. You may use the PeopleSoft Tablespace DDL Automation Assistance Tool (PSTAAT) to customize
tablespace DDL. See the appendix "Using the PeopleSoft Tablespace DDL Automation Assistance Tool" for
more details.
Task 7-5-2: Working with Tablespaces
This section discusses:
•
Using Tablespaces
•
Following the Standard Tablespace Name Formats
•
Naming Tablespace Defaults
•
Parsing Tablespaces
Using Tablespaces
For tablespaces in your PeopleSoft installation, Oracle provides a strategy for Demo and System databases aimed
at identifying high growth and frequently updated tables. This limits the number of tables the DBA must monitor
and analyze, and simplifies capacity planning and database tuning activities. In addition, with PeopleSoft Release
8 and higher, a new type of table was introduced referred to as a temporary table. A temporary table is
permanently created in the database, but its usage, by Application Engine programs, is temporary. The tables are
delivered empty, but because of the potential for a volatile increase and decrease in the number of rows
populating the table during the execution of a process, the temporary tables are also segregated into their own
tablespaces, buffer pool, and databases. This segregation seeks to facilitate administration of these tables and
tablespaces separate from the tablespaces in which the core application tables reside.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
189
Creating a Database
Chapter 7
For customers that elect to use the %UpdateStats functionality, use the PeopleSoft Tablespace DDL Automation
Assistance Tool (PSTAAT) to place each table that is the target of the %UpdateStats function in its own
tablespace. See the appendix "Using the PeopleSoft Tablespace DDL Automation Assistance Tool" for more
details.
Note. For multilingual installs, the PTTBL, PTTLRG and PSIMAGE tablespaces may need to be increased in
size.
Following the Standard Tablespace Name Formats
The standard tablespace names that Oracle delivers categorize tables as follows:
•
High growth and frequently updated tables for Applications are grouped together into tablespaces named
XXLARGE, where XX is a PeopleSoft application identifier. Similarly, the PeopleTools tables identified as
large tables or frequently updated tables are grouped in the PTTLRG tablespace. Depending on customerspecific requirements and environment, it may be advisable to move those tables containing the largest
amount of data from this shared tablespace into their own segmented or partitioned tablespaces. This should
be done for performance and concurrency reasons.
•
Tables with static or relatively minimal growth are grouped into tablespaces named XXAPP, where XX is a
PeopleSoft application identifier. These tablespaces are defined with a moderate free space specification.
•
Tables that are classified by record type as Temporary tables are grouped into tablespaces named XXWORK,
where XX is a PeopleSoft application identifier.
•
Tables with rows exceeding 4K in length are placed in the PSIMAGE tablespace, which is created using a
32K buffer pool.
•
Tables that benefit from row-level locking exist in the following tablespaces:
•
PTPRC — Tables used by the Process Scheduler
•
PTPRJWK — Tools Project Work Table
•
PTAUDIT — Table used by PeopleTools Audit functionality
•
PTAMSG — Tables used by Application Messaging
•
PTLOCK — PSLOCK and PSVERSION tables are stored in this tablespace. These tables consist of
multiple rows and are used for concurrency and version control respectively.
•
PTRPTS — Tables used by Report Repository processes
•
PSIMGR — Tables that benefit from row level locking that also require use of a 32K bufferpool.
•
Other tablespaces exist to group tables in PeopleSoft PeopleTools by functionality (that is, PTTREE for tree
tables, and PTAPPE for Application Engine tables).
Simple or partitioned tablespaces (one table per tablespace) are not supported for the initial installation, but may
be implemented for demonstration and production databases using the PeopleTools Application Designer.
190
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
Naming Tablespace Defaults
The following tables lists and describes common tablespaces:
Tablespaces
Comments
PTAPP, PTTBL
Contain moderate sized PeopleTools tables with little
expected growth.
PTTLRG
Contains larger PeopleTools tables that have the potential to
grow large.
PTAUDIT
Contains table PSAUDIT used by PeopleTools audit
functionality. Row level locking is specified for this
tablespace.
PSIMAGE
Contains PeopleSoft Application and PeopleSoft
PeopleTools tables that contain LONG field types which
require a 32KB page size.
PSIMAGE2
Contains PeopleSoft Application and PeopleSoft
PeopleTools tables that contain LONG field types which
require a 32KB page size.
PSIMGR
Contains tables requiring a 32K bufferpool size that also
benefit from row level locking. Row level locking is
specified for this tablespace.
PTAMSG
Tables used by Application Messaging. Row level locking is
used for this tablespace.
PTAPPE
Tables used for Application Engine. Please note that other
AE tables exist in PSIMAGE because they require 32K
bufferpool.
PTLOCK
Contains PSLOCK and PSVERSION. Row level locking is
used for this tablespace.
PTTREE
Contains tables specific to PeopleTools trees.
PTPRC
All tables used by Process Scheduler. Row level locking is
used for this tablespace.
PTPRJWK
Contains table PSPROJECTWRK. Row level locking is
used for this tablespace.
PTRPTS
Contains tables associated with Report Repository
functionality. Row level locking is used for this tablespace.
XXWORK
Contain PeopleSoft PeopleTools and PeopleSoft Application
"temporary" tables.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
191
Creating a Database
Chapter 7
Tablespaces
Comments
XXLRG
Application tablespaces containing tables identified as high
growth and high update, where the xx corresponds to the
two-character application identifier (FS, PC, AF, and so on).
XXAPP
Application tablespaces identified as static or with the
potential for relatively minimal growth, where the xx
corresponds to the two-character application identifier (FS,
PC, AF, and so on).
XXIMAGE
Contain Application tables requiring 32K buffer pool size.
Parsing Tablespaces
In this multiple database strategy, the tablespaces are distributed to different databases based on the key
application group within the product line. This parsing strategy serves as a good starting point to build a
PeopleSoft database in your development environment. We recommend that you install the Demonstration
database with the delivered strategy to expedite the database creation. You may consider tailoring the delivered
DDL script files to implement your own strategy to build your System PeopleSoft database.
Below are some guidelines that were used in determining a parsing strategy:
•
PeopleSoft PeopleTools tablespaces are created in a "root" database, with one exception ("root" being the
seven-character database name without addition of the eighth character).
•
Tablespace PTPRC (also a PeopleSoft PeopleTools tablespace) is placed in its own database, with an added
eighth character of T, to avoid contention between Process Scheduler and any other processes that may be
running.
•
Tablespace PSIMAGE2 (shared between PeopleSoft Application and PeopleSoft PeopleTools tablespaces) is
assigned to its own database PSXXDMOX.
Refer to the summary found in the specific XXDDL.SQL script, for the exact database or tablespace parsing
strategy for the Product Line.
Note. You can further improve performance by remapping tables to additional tablespaces, and tablespaces to
additional databases with the PeopleSoft Tablespace DDL Automation Assistance Tool (PSTAAT). Consult the
appendix "Using the PeopleSoft Tablespace DDL Automation Assistance Tool" to help you plan a strategy for
implementing production PeopleSoft databases.
See PeopleTools: Data Management.
Task 7-6: Creating Tables
The CREATE TABLE statements to build the tables for the application group are in Partitioned Data Set HLQ.PS
vvv.DDLLIB. To create the tables, use TBDDL for non-Unicode databases, and TBDDLU for Unicode databases.
If any changes were made to the names of the databases or tablespaces in the HLQ.PSvvv.DDLLIB(XXDDL) or
HLQ.PSvvv.DDLLIB(XXDDLU) script, you must make the same parameter changes to the file you will use to
create the tables. The key values you need to modify are:
•
Owner#ID — This value equates to the "CREATOR" field in the SYSIBM.SYSTABLES catalog table and is
offered to facilitate Secondary Authorization ID processing.
192
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
•
OBJ#OWNER — This value should equate to the CREATOR field in the SYSIBM.SYSTABLES catalog
table.
•
Database names
•
Tablespace names — Only if you changed the default names specified in the HLQ.PSvvv.DDLLIB(XXDDL)
or HLQ.PSvvv.DDLLIB(XXDDLU) script.
After reviewing all your changes, submit this file, preferably through DSNTEP2, since this task will take between
one and two hours.
Warning! By default DSNTEP2 allows 10 errors, failing on the 11th error. Allowing 10 errors before the script
stops could leave your database in an inconsistent state. It is important that your script stop at the first error so you
can assess the problem, fix it and resubmit the job. You may want to change the default for DSNTEP2 to fail on
the first error or use SPUFI to submit the TBDDL.
Note. You may use the PeopleSoft Tablespace DDL Automation Assistance Tool (PSTAAT) to optimize the
default installation DDL scripts (XXDDL, XXDDLU, TBDDL) for a production environment. See the appendix
"Using the PeopleSoft Tablespace DDL Automation Assistance Tool" for more details.
Task 7-7: Configuring the DB2 Connect Gateway
Because subsequent installation tasks require connectivity to the remote database, you now need to configure the
DB2 Connect Gateway, cataloging an alias for the PeopleSoft database. You also need to perform any additional
tasks required for connectivity that you didn't already complete during preparation. For instructions on performing
these tasks, see the appendix "Installing and Configuring DB2 Connect." For details on DB2 Connect
configuration, refer to your IBM DB2 Connect documentation.
Task 7-8: 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.
You must perform this procedure for each type of database that you create (System and Demo databases). Also, if
your database supports Unicode, you must decide whether to use an Unicode or EBCDIC database before
carrying out this procedure.
See PeopleTools: Global Technology.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
193
Creating a Database
Chapter 7
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.
Task 7-8-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.
Task 7-8-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.
194
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
2. Verify in the Signon Defaults on the Startup page that the Database Type of DB2 UDB for OS/390 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. Run Data Mover by using one of these methods:
•
On Microsoft Windows 7, select Start, Programs, PeopleTools 8.55, Data Mover.
•
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.
5. Log on using the Access ID and password you defined in your mainframe security software application; this
will start Data Mover in bootstrap mode.
See Checking the Log Files and Troubleshooting, Running Data Mover.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
195
Creating a Database
Chapter 7
Note. You must limit the Access ID to eight characters or less. You must limit the Access password to 30
characters or less.
See "Preparing for Installation," Planning Database Creation.
6. 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
7. Select your database platform from the Select Target Database drop-down list.
8. Select your database type, Unicode or non-Unicode, and character set.
Note. The database setup does not actually modify the encoding scheme of your database. That is
accomplished during creation. The database setup process only creates customized scripts based on your
selection.
196
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
9. 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
10. 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
components.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
197
Creating a Database
Chapter 7
11. Set the database parameters described below and then click Finish.
Specifying Database Parameters on the Database Setup dialog box
•
Database Name: Specify the logical DB2 database name determined in the chapter "Preparing for
Installation" in the task Planning Database Creation.
The database name must also be defined as an alias in DB2 Connect to establish a successful connection to
your PeopleSoft database, as described in the chapter "Installing and Configuring DB2 Connect."
•
Symbolic ID: Specify 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 PeopleSoft Access ID defined in the chapter "Preparing for Installation" in the task
Planning Database Creation.
This is also the User ID value with which you should be currently logged on to Data Mover. This value is
case sensitive.
•
Access Password: Specify the PeopleSoft Access Password defined in the chapter "Preparing for
Installation" in the task Planning Database Creation.
This is also the User password value with which you should be currently logged on to Data Mover.
198
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
•
Creating a Database
Connect ID: For DB2 for z/OS, specify the Connect ID that can be used for the initial connection to DB2
for z/OS. This ID is used for connecting to the database.
Note. The Connect ID must be defined as a valid logon ID in the database security management software.
The Connect ID only needs to be granted SELECT access on PS.PSDBOWNER, PSACCESSPRFL,
PSACCESSPROFILE, PSOPERDEFN, and PSSTATUS. This ID should be granted no other database
authorities.
•
Application Server ID: The Application Server ID 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.
•
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 check box 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.
•
Table Owner: The name of the table owner ID determined in the chapter "Preparing for Installation" in
the task Planning Database Creation.
This value will populate the CREATOR field in the system catalog table SYSIBM.SYSTABLES. It is this
value that identifies all the tables as belonging to the logical PeopleSoft database.
•
Index Storage Group: Specify the storage group where the index spaces will be created.
Later you have to edit the delivered script IXDDL.SQL with this value.
•
Tablespace Storage Group: Specify the storage group for tablespaces.
This value must be the same as that used in the XXDDL.SQL/XXDDLU.SQL script described earlier when
the Tablespaces were created.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
199
Creating a Database
Chapter 7
12. 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.
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
200
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
supported by the character set you used to create your database.
13. 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.
A script <dbname>dbo.dms is created in the PS_HOME\scripts directory, and the script is displayed in the
Data Mover input window. The log files will be written to the location you have specified for the Data Mover
Log Directory in the Configuration Manager profile.
Note. If you selected a Database Type of System in the Database Setup dialog box (above), you must use the
Data Mover DBSPACE command to properly override the default database names in the generated Data
Mover script (script <dbname>dbo.dms). The appendix "Extracting DDL for PTSYS Database" discusses a
sample script that you can use to customize the database names for your location. Refer to this appendix for
information on creating a PTSYS database.
See Also
PeopleTools: Data Management
PeopleTools: Security Administration, "PeopleSoft Authorization IDs"
"Extracting DDL for PTSYS Database"
Task 7-9: 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.
Note. You should already be signed on in bootstrap mode from having completed the previous task.
Verify that the same Connect ID was used in the Database Setup, and Configuration Manager panel. If you
accepted all defaults, the Connect ID is people.
See PeopleTools: Data Management.
Warning! The Data Mover utility uses the INSERT SQL command to populate all the tables in PeopleSoft
database. Notify your systems programmer and operations staff that this activity will generate more DB2 z/OS
logging activity than usual.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
201
Creating a Database
Chapter 7
See Also
Checking the Log Files and Troubleshooting, Running Data Mover
Task 7-9-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. If you have logged out of Data Mover after creating the DMS script, log back on again in Bootstrap mode;
otherwise skip the next instruction.
3. Choose File, Open to open the DMS script you created earlier.
Browse the directory where the script was created: PS_HOME\scripts. Open the DMS script with the name
<dbname>DBO.dms, where <dbname> is the name of the database you provided when creating the script.
4. One of the statements in the script grants select authority on PS.PSDBOWNER to the Connect ID.
GRANT SELECT ON PS.PSDBOWNER TO <Connect ID>;
5. If you have not granted the Access ID (the ID that you used to log on to Data Mover to execute the script) a
level of authority that would permit it to execute this statement, the Data Mover script will fail and stop at the
statement.
You can exercise three options to prevent this failure:
•
Grant SELECT access on PS.PSDBOWNER to PUBLIC, and remove this GRANT statement from the
script.
•
Remove this GRANT statement from the script and perform it later with an ID that is authorized to issue
grants on PS.PSDBOWNER.
• Grant authority to the Access ID to grant access on PS.PSDBOWNER to other user IDs.
6. Select File, Run to execute the script.
When you run the script, Data Mover typically performs the following actions:
•
IMPORT *
Load data into PeopleTools and application tables.
•
ENCRYPT_PASSWORD *
Encrypt security information for the database.
Task 7-10: Checking the Log Files and Troubleshooting
This section discusses:
•
Checking the Log Files
•
Running Data Mover
•
Troubleshooting
•
Improving Performance
202
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
•
Creating a Database
Improving Execution
Task 7-10-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.
This is the same directory you specified for the Data Mover Log Directory in the Configuration Manager profile,
unless you edited this location in the DMS script.
See "Setting Up the Install Workstation," Editing the Default Profile.
Task 7-10-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.
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.
See Also
PeopleTools: Data Management
Task 7-10-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
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
203
Creating a Database
Chapter 7
*; 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, or in the "Creating Indexes" section later in this chapter, 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>dbo.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.
<RECORD NAME> is the PeopleSoft record name as defined in PSRECDEFN, not necessarily the same as
the DB2 table name. With the exception of the PeopleSoft PeopleTools tables, most PeopleSoft record names
are appended with PS_ to create the DB2 table 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
First delete the rows from the partially inserted table (for example, record) by using the DELETE FROM
<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>;
DELETE FROM <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
204
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
/
SET LOG ptengs.log;
SET INPUT ptengs.db;
SET NO RECORD;
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 NO RECORD;
SET NO VIEW;
SET NO SPACE;
SET NO TRACE;
SET UNICODE ON;
SET START PSPNLFIELD;
DELETE FROM PSPNLFIELD;
IMPORT *;
For the DELETE 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).
Task 7-10-4: Improving Performance
The following tips can help you save time when running the Data Mover scripts:
•
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.
Task 7-10-5: Improving Execution
Data Mover, by default, commits at the end of each table. If you prefer, when running Data Mover, you can
include a SET COMMIT command (such as SET COMMIT 5000) to force a commit after the specified number
of rows have been inserted into the table. However, if you use this option, and Data Mover ends abnormally
again, you must mass delete the rows contained in the current table.
If the script stops and the table is partially inserted with the message below:
Importing PSPNLFIELD
Rows inserted into PSPNLFIELD
5000, 10000, 15000
Bypass the record using the SET START AFTER command and complete the import. In a second pass, import the
partially inserted table using this command:
Replace_data <record_name>;
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
205
Creating a Database
Chapter 7
Task 7-11: Creating Indexes
All DDL statements to create the indexes for your application are located in the HLQ.PSvvv.DDLLIB(IXDDL)
file. Edit the IXDDL file to make changes to the delivered DDL to customize the OWNER#ID, OBJ#OWNER,
DEFINE YES, DEFINE NO, and STOGROUP values to the specific values used at your site:
Note. You may then use the IXDDL script with the PeopleSoft Tablespace DDL Automation Assistance Tool
(PSTAAT) to further optimize index DDL. See the appendix "Using the PeopleSoft Tablespace DDL Automation
Assistance Tool" for more details.
•
OWNER#ID: The statement SET CURRENT SQLID may be used, but is not required. All objects in the
CREATE INDEX statements are fully qualified.
•
OBJ#OWNER: This value should equate to the CREATOR field in the SYSIBM.SYSINDEXES catalog
table.
•
DEFINE YES or DEFINE NO: The default for the delivered index DDL is DEFINE NO.
If you do not want to defer creation of the underlying VSAM index datasets until rows are inserted into tables
(DEFINE NO), edit the IXDDL file in ISPF as follows:
change all 'DEFINE NO' to 'DEFINE YES'
or
change all 'DEFINE NO' to ' '
If you want to permanently change the delivered default for index DDL to DEFINE YES, edit the Data Mover
script PS_HOME/scripts/DDLDB2.DMS by removing DEFINE NO from the end of the index model
statement. Terminate the statement with a semi-colon and save the script. For example:
Original:
CREATE [UNIQUE] INDEX **OWNER**.[IDXNAME] ON **OWNER2**.[TBNAME] (⇒
[IDXCOLLIST]) USING STOGROUP **STOGROUP** PRIQTY **PRIQTY** SECQTY⇒
**SECQTY** [CLUSTER] BUFFERPOOL **BUFFERPL** CLOSE NO DEFINE NO;
New:
CREATE [UNIQUE] INDEX **OWNER**.[IDXNAME] ON **OWNER2**.[TBNAME] (⇒
[IDXCOLLIST]) USING STOGROUP **STOGROUP** PRIQTY **PRIQTY** SECQTY⇒
**SECQTY** [CLUSTER] BUFFERPOOL **BUFFERPL** CLOSE NO;
After you edit the script, you must run the STOREDDL.DMS script to update the index model ddl definition.
See Updating PeopleTools System Tables.
• STOGROUP
Save your changes and submit the DDL statements either through SPUFI or DSNTEP2. It is preferable to submit
this in batch mode using DSNTEP2. This task can take several hours to complete, depending on the product line
you are installing.
If you decide to submit this through SPUFI, verify that the designated output data set is allocated with sufficient
tracks or cylinders to hold the result of processing all the CREATE INDEX statements. You should consider
creating a SPUFI output dataset with file attributes: VB,Record Length =4092,Blk size=4096, SPACE (Primary
20 cylinders, Secondary 5 cylinders).
206
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
Important! Do not change the name of any index. All indexes in this script are cataloged in the PeopleSoft
system tables. If you change an index name, the physical index will not match the index definition stored in
PeopleTools. These index discrepancies will be reported as exceptions in the DDDAUDIT report.
Task 7-12: 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 the DB2 RUNSTATS Utility:
•
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.
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-13: 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
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
207
Creating a Database
•
Running PeopleTools Conversions
•
Converting Integration Broker
•
Running Additional PeopleTools Conversions
Chapter 7
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 the DB2 RUNSTATS Utility. If you are installing an application
SYS or DMO database that is not delivered on PeopleSoft PeopleTools 8.55, please proceed with this task.
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 the DB2
RUNSTATS Utility.
Task 7-13-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.
208
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
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-13-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-13-3: Creating New PeopleTools Tablespaces
Review the XXDDL.SQL (non-Unicode) or XXDDLU.SQL (Unicode) 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 (non-Unicode) or ptddlupgu.sql (Unicode) script.
Work with your database administrator (DBA) to review, edit, and then run the ptddlupg.sql (non-Unicode) or
ptddlupgu.sql (Unicode) script to create any missing tablespaces before continuing with the installation.
See Also
"Creating a Database," Creating DB2 Databases, Storage Groups, and Tablespaces
Task 7-13-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 SPUFI, DB2 Command Center, 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:
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
209
Creating a Database
Chapter 7
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
rel842, rel843, rel844, rel845, rel846, rel847, rel848, rel849, rel850, rel851, rel852,
rel853, rel854, and rel855
8.42
rel843, rel844, rel845, rel846, rel847, rel848, rel849, rel850, rel851, rel852, rel853,
rel854, and rel855
8.43
rel844, rel845, rel846, rel847, rel848, rel849, rel850, rel851, rel852, rel853, rel854,
and rel855
8.44
rel845, rel846, rel847, rel848, rel849, rel850, rel851, rel852, rel853, rel854, and
rel855
8.45
rel846, rel847, rel848, rel849, rel850, rel851, rel852, rel853, rel854, and rel855
8.46
rel847, rel848, rel849, rel850, rel851, rel852, rel853, rel854, and rel855
8.47
rel848, rel849, rel850, rel851, rel852, rel853, rel854, and rel855
8.48
rel849, rel850, rel851, rel852, rel853, rel854, and rel855
8.49
rel850, rel851, rel852, rel853, rel854, and rel855
8.50
rel851, rel852, rel853, rel854, and rel855
8.51
rel852, rel853, rel854, and rel855
8.52
rel853, rel854, and rel855
8.53
rel854 and rel855
8.54
rel855
8.55
None
Use the scripts in the following table for Unicode databases:
210
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
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
Application Database Version
Required Scripts for Unicode Databases
8.41
rel842u, rel843u, rel844u, rel845u, rel846u, rel847u, rel848u, rel849u, rel850u,
rel851u, rel852u, rel853u, rel854u, and rel855u
8.42
rel843u, rel844u, rel845u, rel846u, rel847u, rel848u, rel849u, rel850u, rel851u,
rel852u, rel853u, rel854u, and rel855u
8.43
rel844u, rel845u, rel846u, rel847u, rel848u, rel849u, rel850u, rel851u, rel852u,
rel853u, rel854u, and rel855u
8.44
rel845u, rel846u, rel847u, rel848u, rel849u, rel850u, rel851u, rel852u, rel853u,
rel854u, and rel855u
8.45
rel846u, rel847u, rel848u, rel849u, rel850u, rel851u, rel852u, rel853u, rel854u, and
rel855u
8.46
rel847u, rel848u, rel849u, rel850u, rel851u, rel852u, rel853u, rel854u, and rel855u
8.47
rel848u, rel849u, rel850u, rel851u, rel852u, rel853u, rel854u, and rel855u
8.48
rel849u, rel850u, rel851u, rel852u, rel853u, rel854u, and rel855u
8.49
rel850u, rel851u, rel852u, rel853u, rel854u, and rel855u
8.50
rel851u, rel852u, rel853u, rel854u, and rel855u
8.51
rel852u, rel853u, rel854u, and rel855u
8.52
rel853u, rel854u, and rel855u
8.53
rel854u and rel855u
8.54
rel855u
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. If the application database you are installing is 8.53, run the following SQL commands:
DROP TABLE PS_PTIACPTMPLTDEFN;
DROP TABLE PS_PTIACPTMPLTSTEP;
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
211
Creating a Database
Chapter 7
5. Edit and run the grant.sql script in the PS_HOME\scripts directory. This will grant permissions to the Connect
ID.
6. 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.
7. 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.
8. If you are applying a required for install PeopleSoft PeopleTools patch, invoke Data Mover in user mode and
run PS_HOME\scripts\PTPATCH.DMS.
9. 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-13-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.
212
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
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.
Selecting Project PPLTLS84CUR in the Copy From File dialog box
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
213
Creating a Database
Chapter 7
4. The Copy From File dialog box appears.
Select all object types and then click the Options button.
The Copy From File dialog box showing that PPLTLS84CUR will be copied
214
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
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.
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-13-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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
215
Creating a Database
Chapter 7
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.
216
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
217
Creating a Database
Chapter 7
10. On the Copy from File dialog box, click the Copy button.
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-13-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.
218
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
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.
Selecting Project PPLTLS84CURDEL in the Copy From File dialog box
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
219
Creating a Database
Chapter 7
4. The Copy From File dialog box appears.
Select all object types and click the Options button.
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-13-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
220
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
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.
Task 7-13-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).
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
221
Creating a Database
Chapter 7
6. Select Build script file in the Build Execute Options region.
7. Click Settings.
The Build Settings dialog box appears:
Build Settings dialog box: Scripts tab
8. Select the Scripts tab.
9. Select Write Alter comments to script.
222
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
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
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
223
Creating a Database
Chapter 7
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 database name.
16. Edit the generated SQL script for the correct tablespace names and sizing parameters if you are not using
delivered PeopleSoft Tablespace names.
17. 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-13-10: Migrating Records to New Tablespaces
This section discusses:
•
Copying the Tablespace Record Project
•
Running Alter Tools Tables
224
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
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.
Selecting Project PT84TBLSPC in the Copy From File dialog box
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
225
Creating a Database
Chapter 7
4. The Copy From File dialog box appears.
Select all object types and click the Options button.
The Copy From File dialog box showing that PT84TBLSPC will be copied
226
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
227
Creating a Database
Chapter 7
4. Select Build, Project.
The Build dialog box appears:
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.
228
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
7. Click Settings.
The Build Settings dialog box appears:
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.
229
Creating a Database
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, 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 database name.
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 move the tables to the correct tablespaces.
Task 7-13-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:
230
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
Note. DB2 for z/OS scripts need the "set current sqlid" statement so that the tables are created with the correct
owner ID. Open each script listed below, and then uncomment and modify all of the statements specific for DB2
for z/OS to reflect your environment.
1. Invoke Data Mover by running PS_HOME\bin\client\winx86\psdmt.exe.
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
231
Creating a Database
Chapter 7
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
Scripts to Run
8.40
pt841tls, pt842tls, pt843tls, pt844tls, pt845tls, pt846tls, pt847tls,
pt848tls, pt849tls, pt850tls, pt851tls, pt852tls, pt853tls, pt854tls,
and pt855tls
8.41
pt842tls, pt843tls, pt844tls, pt845tls, pt846tls, pt847tls, pt848tls,
pt849tls, pt850tls, pt851tls, pt852tls, pt853tls, pt854tls, and
pt855tls
8.42
pt843tls, pt844tls, pt845tls, pt846tls, pt847tls, pt848tls, pt849tls,
pt850tls, pt851tls, pt852tls, pt853tls, pt854tls, and pt855tls
8.43
pt844tls, pt845tls, pt846tls, pt847tls, pt848tls, pt849tls, pt850tls,
pt851tls, pt852tls, pt853tls, pt854tls, and pt855tls
8.44
pt845tls, pt846tls, pt847tls, pt848tls, pt849tls, pt850tls, pt851tls,
pt852tls, pt853tls, pt854tls, and pt855tls
8.45
pt846tls, pt847tls, pt848tls, pt849tls, pt850tls, pt851tls, pt852tls,
pt853tls, pt854tls, and pt855tls
8.46
pt847tls, pt848tls, pt849tls, pt850tls, pt851tls, pt852tls, pt853tls,
pt854tls, and pt855tls
8.47
pt848tls, pt849tls, pt850tls, pt851tls, pt852tls, pt853tls, pt854tls,
and pt855tls
8.48
pt849tls, pt850tls, pt851tls, pt852tls, pt853tls, pt854tls, and
pt855tls
8.49
pt850tls, pt851tls, pt852tls, pt853tls, pt854tls, and pt855tls
8.50
pt851tls, pt852tls, pt853tls, pt854tls, and pt855tls
8.51
pt852tls, pt853tls, pt854tls, and pt855tls
8.52
pt853tls, pt854tls, and pt855tls
8.53
pt854tls and pt855tls
8.54
pt855tls
8.55
None
4. Run the pslanguages.dms Data Mover script in the PS_HOME\scripts directory.
This script loads language-specific seed data.
232
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
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 nonEnglish 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 DB2ODBC -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-13-12: Running PeopleTools Conversions
This section discusses:
•
Understanding Usage of Application Engine Programs
•
Converting Portal Objects
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
233
Creating a Database
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
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 DB2ODBC -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.
234
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
•
Creating a Database
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 DB2ODBC -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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
235
Creating a Database
Chapter 7
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 DB2ODBC -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 DB2ODBC -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:
<PS_HOME>\bin\client\winx86\psae -CD <dbname> -CT DB2ODBC -CO <oprid> -CP⇒
236
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
<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 DB2ODBC -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 DB2ODBC -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 DB2ODBC -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 DB2ODBC -CO <oprid> -CP⇒
<pswd> -R INSTALL -AI UPGPTHASH
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
237
Creating a Database
Chapter 7
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 DB2ODBC -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 DB2ODBC -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 DB2ODBC -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 DB2ODBC -CO <oprid> -CP⇒
<pswd> -R INSTALL -AI UPGPT851DBC
Task 7-13-13: Converting Integration Broker
This section discusses:
238
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
•
Updating Integration Broker Defaults
•
Creating Integration Broker Objects
•
Saving Application Messaging Objects
•
Exporting Node Transactions
•
Deleting Application Messaging Objects
Creating a Database
• 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 DB2ODBC -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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
239
Creating a Database
Chapter 7
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.
240
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
Task 7-13-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 DB2ODBC -CO <oprid> -CP⇒
<pswd> -R INSTALL -AI UPGPTSERVOPR
Task 7-14: Running the DB2 RUNSTATS Utility
It is recommended that you run the DB2 RUNSTATS utility against the xxWORK tablespaces at this point. The
tables in these tablespaces are designated as temporary tables or tables against which %UpdateStats is being
performed.
Note. The PeopleSoft Tablespace DDL Automation Assistance Tool (PSTAAT) isolates temporary tables to
individual tablespaces named as follows: TMP00001, TMP00002 and so on. Do not run RUNSTATS against any
of the TMPnnnnn tablespaces at this time because this could prove detrimental to performance. The TMPnnnnn
tablespaces should also be excluded from routine RUNSTATS and other database maintenance jobs. See the
appendix "Using the PeopleSoft Tablespace DDL Automation Assistance Tool" for more details.
Task 7-15: Creating PeopleSoft Views
This section discusses:
•
Understanding PeopleSoft Views
•
Creating Views in Data Mover
•
Creating Views in Application Designer
Understanding PeopleSoft Views
If you had to carry out the task "Updating Database to Latest PeopleTools Release" you have already created your
views, in which case you can skip this task.
When creating the PeopleSoft Views, you can use Data Mover or Application Designer to create the objects
directly, or you may use Application Designer to generate a DDL script of SQL statements, which can then be run
using another utility such as SPUFI or DSNTEP2 and/or a User ID other than the Access ID.
Task 7-15-1: Creating Views in Data Mover
To create views in Data Mover:
1. Start Data Mover in User mode using a valid PeopleSoft operator ID, for example, PS or VP1.
See Running Data Mover.
2. Select File, Open from the Data Mover menu and navigate to PS_HOME\scripts.
3. Select the script CREATEVW.dms.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
241
Creating a Database
Chapter 7
4. Select File, Run to execute the script.
5. Exit Data Mover.
Task 7-15-2: Creating Views in Application Designer
To create views in Application Designer:
1. Start Application Designer; for example:
•
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.
2. Create a new project. Choose File, New, and then select Project from the New dialog.
3. Insert all PeopleTools view records into the project:
a. Choose Insert, Definitions into Project. The Insert into Project dialog box appears.
b. Select a Definition Type of Records.
c. In the Selection Criteria control group, choose a Type of View/Query View; and then press ENTER to
select the records.
This example shows the Insert into Project dialog box with a list of results in the Record Name area.
Insert into Project dialog box
d. Click Select All, and then click Insert to insert the View/Query View records into the project.
e. Click Close to close the Insert into Project dialog box.
242
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
4. Build the project.
a. Choose Build, Project. The Build dialog box appears.
b. In the Build Options group, select the Create Views check box. In the Build Execute Options group, select
the Execute SQL now radio button to create the views directly, or the Build script file radio button to
generate a DDL script of CREATE VIEW statements.
Selecting Create Views and Execute SQL now in the Build dialog box
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
243
Creating a Database
Chapter 7
c. If you select Build script file, click Settings, go to the Scripts tab, and enter the output directory and
filename where you want the DDL statement script written in the area All Output File Name.
In this example, the directory and filename are c:\pshrdmo\scripts\createvw.sql.
Build Settings dialog box: Scripts tab
d. Click OK to return to the Build dialog box.
e. Click Build to build the views in the project.
Depending on the Build Execute Option you selected, Application Designer will either directly build the
views on the database or generate a script file of CREATE VIEW DDL statements. If you have opted to
generate the script file, execute the DDL statements either through SPUFI or DSNTEP2. Because of the
time it may take the script to complete, we recommend submitting this script in batch mode using
DSNTEP2. You may also need to prefix the script with the SQL command SET CURRENT SQLID =
<ownerid>.
Note. On DB2 z/OS, when an object is dropped, all the dependent objects are automatically dropped. As a
result some of the drop view statements could fail—and generate errors—if they were dependent on the
view earlier dropped in the script. Please ignore these errors and restart the remaining part of the script.
Task 7-16: Building Temporary Tables
This section discusses:
•
Understanding Temporary Tables
244
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
•
Running SQR SETSPACE.SQR
•
Correcting Invalid Database/Tablespace Combinations
•
Setting the Number of Temporary Tables
•
Using the Volatile Table Attribute
•
Building the Temporary Tables and Their Indexes
Creating a Database
Understanding Temporary Tables
In this task you use Application Designer to create temporary tables. PeopleSoft software has a temporary table
structure where the number of instances for each base temporary table is controlled internally to PeopleSoft
PeopleTools. The definition of each base temporary table is stored in the PeopleSoft PeopleTools table
PSRECDEFN. The temporary table instances themselves are not defined. The table PSRECTBLSPC contains the
database and tablespace values for each record defined in PSRECDEFN. The DDL generated by Application
Designer to create the temporary tables uses the database and tablespace information from the base temporary
table definition in PSRECTBLSPC. The delivered database and tablespace values are in synch with the XXDDL
or XXDDLU script that you ran earlier to create the databases and tablespaces. If you changed the database or
tablespace name values in this script for tablespaces originally named xxWORK, you need to either update the
PSRECTBLSPC table or revise the DDL script to be generated to create the temporary tables.
Oracle recommends that you run SQR SETSPACE.SQR against your database and use the output from the SQR
as a guide in making the necessary updates or revisions. How and where to make the adjustments is discussed in
the later section "Correcting Invalid Database/Tablespace Combinations."
Note. If you used the PeopleSoft Tablespace DDL Automation Assistance Tool (PSTAAT) to optimize the
installation DDL, run the SETSPACE.SQR to update table PSRECTBLSPC with the database and tablespace
values created by PSTAAT.
Task 7-16-1: Running SQR SETSPACE.SQR
In this procedure, you run SQR SETSPACE.SQR to update table PSRECTBLSPC with the database and
tablespace values from the DB2 system catalog. Application Designer uses the database and tablespace values
stored in PSRECTBLSPC to generate DDL statements to create the tables.
SETSPACE.SQR serves multiple purposes:
•
It updates PSRECTBLSPC with the database/tablespace values from the DB2 system catalog table
SYSIBM.SYSTABLES for the tables defined in the DB2 System Catalog.
•
It reports tables in PSRECTBLSPC that are updated with a new database or tablespace name.
•
It reports tables that are defined in PSRECTBLSPC, but not defined in the DB2 system catalogs, and whether
the database/tablespace combination defined for the record is valid or invalid (not defined in the DB2 system
catalog table SYSIBM.SYSTABLESPACE).
•
It syncs up the database/tablespace combinations used in PSRECTBLSPC with the PeopleTools "master"
tablespace table PSTBLSPCCAT by inserting the valid combinations in PSTBLSPCCAT if they have not
already been defined.
•
It reports those database/tablespace values added to the PSTBLSPCCAT table.
•
It summarizes and reports database/tablespace combinations defined in PSTBLSPCCAT that are not valid.
The reports are a valuable tool in determining how and where to make revisions so the temporary tables are
created in the correct location, and without error.
To run SQR SETSPACE.SQR:
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
245
Creating a Database
Chapter 7
Submit the Job PSHLQ.PPvvv.JCLLIB(SETSPACE) to execute the SQR on the mainframe.
The SDSF logs will display the results of running the SQR and information related to the success of executing this
SQR.
An output file will be written to PSHLQ.PPvvv.SQRLIST(SETSPACE) detailing the records processed and
actions taken.
Note. The SQR can be run multiple times without any negative impact, but the output file will be overwritten with
each execution. You may want to rename the member PSHLQ.Ppyyy.SQRLIST(SETSPACE) to another name
before each resubmission of the SQR.
Task 7-16-2: Correcting Invalid Database/Tablespace Combinations
Review the output in PSHLQ.PPvvv.SQRLIST(SETSPACE). Note any messages with "Table Undefined —
DB/TS Invalid," but most importantly, note any Warning messages in the second Phase of the output report.
These warning messages summarize the database/tablespace name combinations defined in PSRECTBLSPC that
have not been defined in the DB2 system catalog tables.
There are five options for making the necessary revisions. Of these options, Option 1 is the recommended one, for
several reasons. Editing can be done globally; no table data will be impacted as it would in other options; you are
guaranteed that the temporary table will be built in the database and tablespace that you intend; and you may have
already found it necessary to edit the script file of DDL statements to create the Temporary table for other
reasons.
•
Option 1 (Recommended): Proceed through the installation process and build a script file of the DDL
statements to create the temporary tables. After the script has been generated, but before executing it, globally
edit the database/tablespace name combinations using the second Phase of the output report as a guide to the
"before" values, changing them to your preferred site specific values.
•
Option 2: Update the PSRECTBLSPC table directly via the database interface of choice before building the
script file of DDL statements to create the temporary tables. Use the second Phase of the output report as a
guide. The SQL to correct each invalid database/tablespace combination would be scripted as follows:
UPDATE PSRECTBLSPC SET DBNAME = '<new dbname>',
DDLSPACENAME = '<new tablespacename>'
WHERE DBNAME = '<old dbname>'
AND DDLSPACENAME = '<old tablespacename>'
AND DBTYPE = (SELECT MAX(A.DBTYPE) FROM PSRECTBLSPC A
WHERE RECNAME = A.RECNAME
AND A.DBTYPE IN (' ','1'))
•
Option 3: Run SQR SETDBNAM to update the database value in PSRECTBLSPC with a "best guess" value
based on the tablespace value defined in PSRECTBLSPC. The accuracy of this SQR is based on the following
caveats:
•
The ID or Current SqlID that was used to create the tablespaces must be the same value as the owner ID of
the tables comprising the logical PeopleSoft database. In other words, the CREATOR field value in
SYSIBM.SYSTABLESPACE must be the same value as the CREATOR field in SYSIBM.SYSTABLES.
•
The given tablespace name and CREATOR value in SYSIBM.SYSTABLESPACE must represent a
unique relationship. For a given CREATOR, if you have defined a given tablespace name in more than
one database, the SQR will use the database value associated with the tablespace that contains the fewest
number of tables.
If either of these requirements is not met, either a database value will not be found and PSRECTBLSPC will not
be updated, or PSRECTBLSPC could be updated with a database value different from that intended.
246
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
To run the SQR SETDBNAM, follow the same procedure as running SQR SETSPACE, using the JCL Job
PSHLQ.PPvvv.JCLLIB(SETDBNAM) instead.
•
Option 4: Log into the database via Application Designer, and update the record definitions with valid
database/tablespace combinations, before building the script of DDL statements to create the temporary tables.
Use the first Phase of the output report as a guide. (This could be a tedious and time-consuming process and is
not recommended over the previously described options.)
•
Option 5: Create the database/tablespace combinations in DB2 so they are no longer invalid, before executing
the script file of DDL statements to create the Temporary tables. Use the second Phase of the output report as
a guide to the databases and tablespaces that need to be created. (This is not recommended simply because it
is likely to contradict the naming standards established for your DB2 installation.)
Task 7-16-3: Setting the Number of Temporary Tables
Normally, you will leave the number of temporary tables set to the default defined in the database. You may want
to change this setting for optimal performance, depending on various aspects of your implementation, including
account transaction volumes, benchmark numbers for the current hardware and database platform, and your
service-level requirements.
Oracle delivers a minimum of three temporary table instances in most cases. You cannot adjust the number of
temporary tables unless you have installed the PeopleSoft Pure Internet Architecture. (See "Setting Up the
PeopleSoft Pure Internet Architecture in GUI Mode" or "Setting Up the PeopleSoft Pure Internet Architecture in
Console Mode.") You may skip this step entirely, and come back to it after PeopleSoft Pure Internet Architecture
has been installed and you have a better idea of how many instances of the temporary tables might best fit your
processing requirements. Another option is to update the PeopleTools table that controls the number of temporary
table instances directly. Using the Database SQL interface of choice, issue the following SQL:
UPDATE PSOPTIONS SET TEMPTBLINSTANCES = <#>, TEMPINSTANCEONLINE = <#>⇒
WHERE TEMPINSTANCEBATCH = 0
The number of instances (#) for either field should not be less than 3 or greater than 9.
For non-EPM applications, it is strongly recommended that the TEMPTBLINSTANCES and
TEMPINSTANCEONLINE values be the same. For EPM applications we strongly recommend that you take the
delivered defaults.
Note. Again, this step can be performed at installation and/or at any time during the life of your database. The
only caveat is that when any of the parameters are changed that would impact the number of temporary table
instances, all temporary tables should be regenerated.
Task 7-16-4: Using the Volatile Table Attribute
Beginning with PeopleSoft PeopleTools 8.48 and later, all temporary tables are created using the volatile
keyword.
Sample DB2 for z/OS volatile temporary DDL follows:
CREATE TABLE Q848902.PS_AEEXT_TAO (PROCESS_INSTANCE DECIMAL(10) NOT
NULL,
AE_INT_1 SMALLINT NOT NULL,
AE_APPLID CHAR(12) NOT NULL,
AE_SECTION CHAR(8) NOT NULL,
AE_STEP CHAR(8) NOT NULL) VOLATILE IN Q848902.PTAPPE;
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
247
Creating a Database
Chapter 7
The volatile attribute specifies that the DB2 optimizer should favor index access on this table whenever possible
for SQL operations regardless of the presence of statistics.
For more details on the volatile table attribute, refer to the DB2 for z/OS SQL Reference and the DB2 for z/OS
Administration Guide.
Task 7-16-5: Building the Temporary Tables and Their Indexes
Use the following procedure to build temporary tables in the database.
Note. You may use the temporary table DDL script created at the end of this task as input to the PeopleSoft
Tablespace DDL Automation Assistance Tool (PSTAAT) to isolate each of the temporary tables to its own
tablespace.
To build temporary tables:
1. Open Application Designer.
2. Choose File, New. In the New dialog, select Project, and then click OK.
3. Choose Insert, Definitions into Project.
4. Set Definition Type to Records and Type to Temporary Table.
Insert into Project dialog box
5. Press ENTER, or click Insert and then click the Select All button. This selects all of the PeopleTools Records
for temporary tables.
6. Click Insert to insert all of the temporary tables into the new project.
7. Click Close to close the Insert into Project dialog.
248
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
8. Before building the project, you should save it. Choose File, Save Project As and enter a project name such as
TEMPTBL.
9. Choose Build, Project. The Build dialog appears.
10. In the Build Options group, select the Create Tables check box. The Create Index check box should be
selected by default.
11. Select Build script file to direct the DDL to a file.
12. Click the Settings button. The Build Settings dialog appears.
13. On the Create tab, select Recreate table if it already exists (if it is not already selected) under Table Creation
Options.
Selecting the Recreate table if it already exists in the Build Settings dialog box
14. Select the Scripts tab, and select Output to Single File under Script File Options.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
249
Creating a Database
Chapter 7
15. Under Script File Names, specify the path and filename for the output file to contain the DDL to create the
Temporary tables and their indexes (for example, PS_HOME\scripts\TEMPDDL.SQL).
The path and filename in this example is c:\pshrdmo\scripts\createtmp.sql.
Specifying the path and filename in the All Output File Name section
16. Click OK to accept the build settings.
17. Click Build to build temp tables. You may receive a warning message, which you can disregard because the
temp tables do not contain any existing data.
18. After the script generation process has finished, click Close in the Build Progress dialog box to return to
Application Designer.
19. Transfer the file of DDL statements just created to the mainframe server PDS HLQ.PSvvv.DDLLIB
(filename).
20. If you have corrected the invalid database/tablespace combinations following Option 1 described earlier, and
not updated the PSRECTBLSPC table with the database and tablespace names used in your installation, you
need to edit the file, changing both the database and tablespace names from the values as would be noted in
the second Phase of the output report from SQR SETSPACE, to your site-specific values.
Note. If you intend to use the %UpdateStats functionality, you should use the PeopleSoft Tablespace DDL
Automation Assistance Tool (PSTAAT) to isolate each of the temporary tables to its own tablespace to avoid
contention in any concurrently running processes. See the appendix "Using the PeopleSoft Tablespace DDL
Automation Assistance Tool."
21. When the file has been edited with the appropriate database and tablespace name values, save your changes
and submit the DDL statements either through SPUFI or DSNTEP2. It is preferable to submit this in batch
mode using DSNTEP2, because the task could take over an hour to complete.
250
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
Task 7-17: Creating PeopleSoft Triggers
This section discusses:
•
Understanding PeopleSoft Triggers
•
Creating Triggers in Data Mover
•
Creating Triggers in Application Designer
Understanding PeopleSoft Triggers
When creating the PeopleSoft Triggers, you can use Data Mover or Application Designer to create the objects
directly, or you can use Application Designer to generate a DDL script of SQL statements, which can then be run
using another utility such as SPUFI or DSNTEP2, and with a UserID with a greater level of database authority.
Task 7-17-1: Creating Triggers in Data Mover
To create triggers in Data Mover:
1. Start Data Mover in User mode, using a valid PeopleSoft operator ID, for example, PS or VP1.
See Running Data Mover.
2. Choose File, Open from the Data Mover menu and navigate to PS_HOME\scripts.
3. Select the script CREATETRGR.dms.
4. Choose File, Run to execute the script.
5. Exit Data Mover.
Task 7-17-2: Creating Triggers in Application Designer
To create triggers in Application Designer:
1. Start Application Designer, for example:
•
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.
2. Create a new project. Choose File, New, and then select Project from the New dialog.
3. Insert all PeopleTools Table records into the project.
To insert the Table records:
a. Choose Insert, Definitions into Project. The Insert into Project dialog appears.
b. Select a Definition Type of Records.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
251
Creating a Database
Chapter 7
c. In the Selection Criteria control group, choose a Type of Table; and then press ENTER to select the
records.
Insert into Project dialog box
d. Click Select All, and then click Insert to insert the Table records into the project.
e. Click Close to close the Insert into Project dialog.
4. Build the project.
a. Choose Build, Project. The Build dialog displays.
252
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
b. In the Build Options group, select the Create Trigger check box. In the Build Execute Options group,
select either the Execute SQL now radio button to create the triggers directly, or the Build script file radio
button to generate a DDL script of CREATE TRIGGER statements.
Build dialog box
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
253
Creating a Database
Chapter 7
c. If you have selected the Build script file radio button, click the Settings button, go to the Scripts tab, and
enter the output directory and filename where you want the DDL statement script written.
Build Settings dialog box
d. Click OK to return to the Build dialog.
5. Click Build to build the triggers associated with the tables in the project.
Depending on the Build Execute Option selected, Application Designer will either directly build the triggers
on the database or generate a script file of CREATE TRIGGER DDL statements. If you have opted to
generate the script file, execute the DDL statements either through SPUFI or DSNTEP2. Because of the time
it may take the script to complete, we recommend submitting this script in batch mode using DSNTEP2. You
may also need to prefix the script with the SQL command SET CURRENT SQLID = <ownerid>.
Task 7-18: 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.
254
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
Task 7-19: 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.
Task 7-19-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-19-2: Populating the Translated System Data
To populate the translated system data:
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
255
Creating a Database
Chapter 7
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-20: Running SQR Reports
This section discusses:
•
Understanding Running SQR Reports
•
Binding the dbcalls.bnd
•
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-20-1: Binding the dbcalls.bnd
You need to bind the dbcalls.bnd before running SQR reports.
To bind dbcalls.bnd:
1. Using an ID with mainframe logon and BINDADD privileges, log on to DB2 Connect Command Line
Processor:
db2 => CONNECT TO <database name> USER <mainframe User Id>
Note. Enter your current password for "mainframe User Id": <mainframe User Id password>.
2. The Windows SQR bind executable is located in the File or Report Server directory (for example, PS_HOME\
bin\sqr\db2\BINW\dbcalls.bnd).
256
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
•
Creating a Database
Issue the following bind command for an EBCDIC installation:
db2 => bind <ps_home>\bin\sqr\db2\BINW\dbcalls.bnd blocking all grant⇒
public⇒
sqlerror continue
•
For a Unicode installation, you must bind the windows SQR executable with encoding unicode as follows:
db2 -> bind <ps_home>\bin\sqr\db2\BINW\dbcalls.bnd encoding unicode⇒
blocking⇒
all grant public sqlerror continue
Note. The executable program PSSQR.EXE is a wrapper program used by PeopleSoft Process Scheduler to run
SQR reports. It is not designed to run manually outside of Process Scheduler. That is, the PeopleSoft system does
not support running PSSQR from the command line.
Task 7-20-2: 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\DB2\binw.
Select sqrw.exe and click Open.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
257
Creating a Database
Chapter 7
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
Description
-I
Specifies the directories that SQR will search for the #INCLUDE
files. (A trailing slash is required.)
-f
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.
258
-ZIF
Sets the full path and name of the SQR initialization file. The -ZIF
flag should point to your PS_HOME\sqr\pssqr.ini file.
-keep
Keeps the .SPF file after the program runs. This enables you to
view the report with the SQR viewer.
-printer:ht
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.
Chapter 7
Creating a Database
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.
Task 7-20-3: 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\DB2\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.
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
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
259
Creating a Database
•
Username: Enter the access ID.
•
Password: Enter the access password.
Chapter 7
• Report arguments: Make any necessary modifications to the saved arguments.
8. Click OK.
Task 7-21: Updating PeopleSoft System Tables
This section discusses:
•
Understanding PeopleSoft System Tables
•
Updating PeopleSoft System Tables
Understanding PeopleSoft System Tables
In this task, you run SQR scripts that update PeopleTools tables with information from the DB2 system catalog
tables.
•
SETSPACE.SQR was run in an earlier task, but should be re-run at this point. It updates PSRECTBLSPC with
the database and tablespace information captured from the DB2 system catalog table SYSIBM.SYSTABLES,
inserts valid database and tablespace combinations defined in PSRECTBLSPC that have not yet been defined
in PSTBLSPCCAT, and provides an audit report of actions taken and invalid database and tablespace
combinations defined in PSRECTBLSPC but not defined in the DB2 system catalog table
SYSIBM.SYSTABLESPACE. You can run this SQR multiple times without negative impact.
•
SETTMPIN.SQR inserts rows into PSRECTBLSPC to store the database and tablespace location for each
temporary table instance defined in the DB2 system catalog table SYSIBM.SYSTABLES. You need to run
this SQR after each time you create or refresh the temporary tables on your database. You can run this SQR
multiple times without negative impact.
Note. This SQR will not facilitate regeneration of the temporary tables by ensuring that each instance is
rebuilt in the database/tablespace location to which it was originally assigned. The purpose of the SQR is to
capture the location of each temporary table instance after it has been created in the database, and sync
PSRECTBLSPC with the DB2 system catalog.
Task 7-21-1: Updating PeopleSoft System Tables
To update PeopleSoft system tables initiate SQRW.exe as you did in the task Running SQR Reports and run the
SETSPACE.SQR and SETTMPIN.SQR (if applicable) programs.
Note. Oracle also provides SETINDEX.SQR and SETBUFF.SQR, which will help the PeopleSoft DBA keep the
PeopleSoft system tables in sync with the DB2 catalogs.
Task 7-22: Binding DB2 Plans
If you are not planning to run COBOL on the mainframe, this step is not necessary.
260
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
You need to bind the following DB2 Plans used by PTPSQLRT—the first one is for the Native Attach Facility for
UNIX System Services, and the second one is for the Call Attach Facility. On the z/OS server, submit the
following two JCL jobs:
HLQ.PSVVV.JCLLIB(BINDAADD)
HLQ.PSVVV.JCLLIB(BINDEADD)
The only acceptable message reads:
BIND SUCCESSFUL
If you receive any other message, it means you have encountered an error. Common bind errors include:
•
Program PTPSQLRT failed to precompile (jobs PSCOBDA and/or PSCOBDE) and the DBRM was not
generated. If this is the case, run PSCOBDA or PSCOBDE again, and carefully examine the return codes.
•
If you get a "Plan Already Exists" error, do a bind/replace using BINDAREP and BINDEREP.
Task 7-23: 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 DB2ODBC -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.
See "Setting Up the Install Workstation."
Task 7-24: 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.
Task 7-25: Checking the Database
Run and examine the SQR reports to verify that your database is complete.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
261
Creating a Database
Chapter 7
See Running SQR Reports.
See Updating PeopleTools System Tables.
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."
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
Task 7-26: 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.
262
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
7. Click Insert, and then click Select All.
8. Click Insert, and then click Close.
9. Select Build, Project.
The Build dialog box appears:
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
263
Creating a Database
Chapter 7
12. Click Settings.
The Build Settings dialog box appears:
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.
264
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
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
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
265
Creating a Database
Chapter 7
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 database name.
22. Edit the generated SQL script for the correct tablespace names and sizing parameters if you are not using
delivered PeopleSoft tablespace names.
23. Run the generated SQL scripts in your platform-specific query tool to bring your database structure in sync
with the PeopleTools tables.
266
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 7
Creating a Database
Task 7-27: Disabling %UpdateStats
The %UpdateStats meta-SQL function allows an Application Engine program to update DB2 catalog statistics
after it has populated temporary tables with transient data used for intermediate query result sets. This allows the
DB2 optimizer to choose a better access path when these tables are joined to other tables. To optimally use
%UpdateStats for DB2 z/OS, it is highly recommended that tables subject to this feature be placed in their own
tablespace. %UpdateStats invokes the DB2 RUNSTATS utility through the IBM DSNUTILS stored procedure.
Because RUNSTATS executes at the tablespace level, having multiple tables in a given tablespace can degrade
the performance of an Application Engine program that invokes this utility through %UpdateStats. Consider using
PSTAAT (see the appendix "Using the PeopleSoft Tablespace DDL Automation Assistance Tool") to optimize
the table to tablespace mapping for Application Engine temporary tables. If you have not installed and authorized
the DSNUTILS stored procedure for use in your environment, or, if you have not isolated Application Engine
temporary tables to individual tablespaces, you may wish to consider disabling the %UpdateStats function by
setting DBFLAGS to 1 in your Process Scheduler configuration file. See the previous section, Using
%UpdateStats, or search the PeopleSoft documentation for more details on using DBFLAGS to disable
%UpdateStats.
If you have not implemented the DSNUTILS stored procedure and/or followed the traditional installation path,
you might consider disabling recognition of the %UpdateStats function by setting DBFLAGS to 1 in your Process
Scheduler configuration file. See the previous section, "Using %UpdateStats," or search the PeopleSoft
documentation for more details on using DBFLAGS to disable %UpdateStats.
See PeopleTools: Data Management.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
267
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.
Application servers are not supported on z/OS because Oracle Tuxedo cannot run on the mainframe. For this
reason, you can only install an application server in a "physical" three-tier configuration—with the application
server on a machine separate from the database server machine. You cannot run a "logical" three-tier
configuration—with the application server on the same machine as the database server.
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
269
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," 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.
270
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.
If you are running DB2 for z/OS, you can issue this command from the UNIX prompt:
db2 connect to <database name> user <z/OS ID> using <password>
If you are running DB2 for z/OS and are setting up your application server on a Microsoft Windows machine,
enter the preceding command at a DB2 Connect command window, or use DB2 Connect's Command Center or
Client Configuration Assistant.
See "Installing and Configuring DB2 Connect."
Task 8A-4: Creating, Configuring, and Starting an Initial
Application Server Domain
This section discusses:
•
Creating, Configuring, and Starting the Application Server Domain
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
271
Configuring the Application Server on Windows
Chapter 8A
•
Testing the Three-Tier Connection
•
Importing an Existing Application Server Domain Configuration
•
Setting Up a Custom Application Server Domain Configuration
•
Troubleshooting Common Errors
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:
•
272
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 8A
Configuring the Application Server on Windows
•
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 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 :[DB2ODBC]
3) Query Servers : No 19) UserId :[QEDMO]
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]
13) Push Notifications : No Actions
=========
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
273
Configuring the Application Server on Windows
Chapter 8A
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:
Do you want to change any config values (y/n) [n]?
c. Reply n, and press ENTER, at this prompt:
274
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 8A
Configuring the Application Server on Windows
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 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:
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
275
Configuring the Application Server on Windows
Chapter 8A
•
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.
276
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.
277
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
278
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.
279
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
280
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.
281
Configuring the Application Server on Windows
Chapter 8A
properly configured.
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
282
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. We do not support application servers on z/OS.
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.
Application servers are not supported on z/OS because Oracle Tuxedo cannot run on the mainframe. For this
reason, you can only install an application server in a "physical" three-tier configuration—with the application
server on a machine separate from the database server machine. You cannot run a "logical" three-tier
configuration—with the application server on the same machine as the database server.
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
283
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.
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," 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>'
284
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 8B
Configuring the Application Server on UNIX
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
285
Configuring the Application Server on UNIX
Chapter 8B
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.
If you are running DB2 for z/OS, you can issue this command from the UNIX prompt:
db2 connect to <database name> user <z/OS ID> using <password>
If you are running DB2 for z/OS and are setting up your application server on a Microsoft Windows machine,
enter the preceding command at a DB2 Connect command window, or use DB2 Connect's Command Center or
Client Configuration Assistant.
See "Installing and Configuring DB2 Connect."
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:
-------------------------------286
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 8B
Configuring the Application Server on UNIX
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...
***********************************************************
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:
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
287
Configuring the Application Server on UNIX
Chapter 8B
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 :[DB2ODBC]
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]
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.
288
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 8B
Configuring the Application Server on UNIX
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:
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
289
Configuring the Application Server on UNIX
Chapter 8B
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.
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.
290
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 8B
Configuring the Application Server on UNIX
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.
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
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
291
Configuring the Application Server on UNIX
Chapter 8B
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
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
292
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 8B
Configuring the Application Server on UNIX
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.
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
293
Configuring the Application Server on UNIX
•
Chapter 8B
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
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:
•
294
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
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 8B
Configuring the Application Server on UNIX
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=
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
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
295
Configuring the Application Server on UNIX
•
Chapter 8B
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
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
296
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
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.
297
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.
298
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.
299
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
300
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.
301
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
302
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.
303
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
304
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.
305
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
306
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.
307
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
308
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.
309
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
310
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.
311
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.
312
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.
313
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.
PeopleSoft Internet Architecture Report Repository window
314
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.
315
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.
316
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.
317
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
318
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.
319
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.
320
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.
321
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:
PeopleSoft Internet Architecture Webserver Admin Credentials window for an existing domain
322
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.
323
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
324
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.
325
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
326
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.
327
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
328
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.
329
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.
330
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.
331
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.
PeopleSoft Internet Architecture Report Repository window
332
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.
333
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
334
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.
335
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
336
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.
337
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
338
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.
339
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.
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:
340
Server Name
Purpose
HTTP or HTTPS Port Number
server1
PORTAL applications
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.
341
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.
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.
342
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.
343
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.
344
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.
345
Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode
Chapter 9A
12. Enter the AppServer Domain Connection password two times (optional).
In this example, the password fields are blank.
PeopleSoft Internet Architecture AppServer Connection Password window
346
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.
347
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.
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."
348
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
HTTP Port Number
HTTPS Port Number
server1
5555
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.
349
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.
PeopleSoft Internet Architecture Web Profile Credentials window
350
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.
351
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
352
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.
353
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.
354
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.
355
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:
356
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.
357
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.
358
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.
359
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
360
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 WebLogicDomainWebLogicServer.
--------------------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.
361
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:
362
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.
363
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:
364
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.
365
Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode
Chapter 9A
2. Select (press) Navigator.
NavBar side page
The menu structure appears.
366
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.
367
Setting Up the PeopleSoft Pure Internet Architecture in GUI Mode
Chapter 9A
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
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
PeopleTools Option Page Selection
PSOPTIONS.DBLENGTHTYPE Value
Unicode-encoded database or a nonUnicode SBCS database
Others
N
Japanese database on DB2 LUW
DB2 MBCS
D
Non-Unicode Japanese database
MBCS
M
Note. If your installation uses the Shift- Note. The MBCS option is not
JIS character set for Japanese, you must supported for DB2 z/OS.
use this option.
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.
368
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.
369
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.
371
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.
Note. We do not support web servers on z/OS.
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
372
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 9B
Setting Up the PeopleSoft Pure Internet Architecture in Console Mode
with relevant data associated with incoming calls, such as customer or case details.
See PeopleTools: MultiChannel Framework.
•
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.
373
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
374
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.
375
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
376
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.
377
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 []:
378
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.
379
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
380
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.
381
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.
382
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.
383
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⇒
384
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.
385
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.
386
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.
387
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
Purpose
HTTP or HTTPS Port Number
server1
PORTAL applications
X
psemhub
PeopleSoft Environment Management X+1
Framework applications (PSEMHUB)
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.
388
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.
389
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]:
390
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.
391
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.
392
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.
393
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
394
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 9B
Setting Up the PeopleSoft Pure Internet Architecture in Console Mode
REPORTS_DIR=
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.
395
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
396
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.
397
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.
398
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.
399
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
400
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 WebLogicDomainWebLogicServer.
--------------------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.
401
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:
402
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.
403
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:
404
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.
405
Setting Up the PeopleSoft Pure Internet Architecture in Console Mode
Chapter 9B
2. Select (press) Navigator.
NavBar side page
The menu structure appears.
406
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.
407
Setting Up the PeopleSoft Pure Internet Architecture in Console Mode
Chapter 9B
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
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
PeopleTools Option Page Selection
PSOPTIONS.DBLENGTHTYPE Value
Unicode-encoded database or a nonUnicode SBCS database
Others
N
Japanese database on DB2 LUW
DB2 MBCS
D
Non-Unicode Japanese database
MBCS
M
Note. If your installation uses the Shift- Note. The MBCS option is not
JIS character set for Japanese, you must supported for DB2 z/OS.
use this option.
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.
408
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.
409
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.
411
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.
412
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.
413
Setting Up Process Scheduler on Windows
Chapter 10A
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.
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.
414
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.
415
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
416
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.
417
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.
418
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. If the PeopleSoft Process Scheduler is on DB2 z/OS, use
FTP/FTPS or HTTP/HTTPS.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
419
Setting Up Process Scheduler on Windows
Chapter 10A
Note. If you are using FTP/FTPS or SFTP, the corresponding service must be set up in your web server.
Note. If you are on DB2 z/OS, you need to have JRE set up on your Process Scheduler server.
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.
420
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.
421
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.
422
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.
423
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.
424
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.
425
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.
•
426
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.
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
Property Value
ACTIVEMODE
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
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
ENABLEEPRT
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.
EXTENDEDPASSIVEMODE
•
•
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
Specify the Java keystore (JKS) password.
JKSPATH
Specify the Java keystore (JKS) path.
PASSWORD
Specify the password associated with the USER property,
which identifies the FTP User ID.
USER
Specify the FTP User ID used for authentication when
accessing the FTP site.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
427
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.
428
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.
429
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.
430
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
Property Value
ACTIVEMODE
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
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.
EXTENDEDPASSIVEMODE
•
•
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
Specify the Java keystore (JKS) password.
JKSPATH
Specify the Java keystore (JKS) user.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
431
Setting Up Process Scheduler on Windows
Chapter 10A
Property Name
Property Value
KEYSTOREPASSWORD
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.
PASSWORD
Specify the password associated with the USER property,
which identifies the FTP User ID.
SSLUAGELEVEL
•
•
0 - No SSL: No SSL will be used.
•
•
2 - Control: Require SSL for the control connection.
1 - Try SSL: Try using SSL, but proceed as normal
otherwise.
3 - SSL Only: (Default) Require SSL for all
communication.
USER
Specify the FTP User ID used for authentication when
accessing the FTP site.
VERIFYHOST
•
•
0: Do not verify the server for host name.
•
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.
VERIFYPEER
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.
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:
432
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.
433
Setting Up Process Scheduler on Windows
Chapter 10A
3. On the Report Node Definition page, select SFTP from the Protocol drop-down list.
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.
434
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.
435
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
Property Value
AUTHTYPE
Select one of the following the authentication types:
•
•
•
PUBLICKEY
PASSWORD
ANY
PASSWORD
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
Enter the password for the private key.
PRIVATEKEY
Select the private key.
PUBLICKEY
Select the public key.
SSHKEYALIAS
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."
USER
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.
436
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.
437
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
438
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10A
•
Setting Up Process Scheduler on Windows
Verifying the Process Scheduler Server Status
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
Operating System
PSNT
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.
439
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. Specify 1 for nt for the configuration templates.
The nt configuration is based on the operating system Process Scheduler server will be booted from.
Process Scheduler Configuration templates:
1) nt
440
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10A
Setting Up Process Scheduler on Windows
2) os390
Select config template number:
7. 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] 2) Master Scheduler : Yes 10) DBTYPE :[DB2ODBC] 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\ODB⇒
\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.
441
Setting Up Process Scheduler on Windows
Chapter 10A
8. 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
Description
Master Scheduler
Select this option to enable the Master Scheduler Server
(PSMSTPRC). The default is to enable the server.
See PeopleTools: Process Scheduler.
App Engine
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.
Perf Collator
Select this option to enable the PSPPMSRV server
process.
See PeopleTools: Performance Monitor, "Enabling the
Required Elements on the Monitoring System."
Domain Gateways
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."
Push Notifications
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."
442
Load config as shown
Load the selections you made in the Quick Configure
menu.
Custom configuration
Make custom selections in PSADMIN, using options that
are not available in the Quick Configure menu.
Edit environment settings
Edit, add, remove, comment out, and review domain-level
environment variables.
DBNAME
Specify the database name that is associated with a
PeopleSoft Process Scheduler Server Agent, such as
HRDMO, FSDMO, SADMO, and so on.
DBTYPE
Specify the database type: DB2ODBC (for DB2 for z/OS).
PrcsServer
Specify the process server name. This must match the
name defined in the Server Definition table, such as PSNT
or PSUNX.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10A
Setting Up Process Scheduler on Windows
Parameter
Description
UserId
Enter the user ID, such as VP1 or PS.
UserPswd
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.
ConnectID
Enter the connect ID. This value is required.
ConnectPswd
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.
Log/Output Dir
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.
SQRBIN
Enter the path to the SQR executables.
AddToPATH
(Optional for Tuxedo) Specify an additional directory that
is appended to the PATH environment variable.
DBBIN
Enter the path to the database drivers; that is, your
connectivity software.
DomainConnectPswd
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.
9. 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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
443
Setting Up Process Scheduler on Windows
Chapter 10A
10. To start Process Scheduler, choose 1, for Administer Domain.
11. 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) :
12. 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.
13. 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.
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
444
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10A
Setting Up Process Scheduler on Windows
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.
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
445
Setting Up Process Scheduler on Windows
Chapter 10A
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
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.
446
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10A
Setting Up Process Scheduler on Windows
> 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.
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
447
Setting Up Process Scheduler on Windows
Chapter 10A
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
Value
TEMP
Specify the location of the TEMP directory on the
Windows server, as in C:\TEMP.
TUXDIR
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.
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
448
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10A
Setting Up Process Scheduler on Windows
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.
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
449
Setting Up Process Scheduler on Windows
Chapter 10A
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.
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.
450
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10A
Setting Up Process Scheduler on Windows
3. On the Process Definition page, select Override Options, as shown in this example.
Process Definition page: Override Options
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
451
Setting Up Process Scheduler on Windows
Chapter 10A
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.
452
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 (especially %PS_FILEDIR%) must be specified.
•
A supported version Microsoft Office must be present on the process scheduler server, and Microsoft Excel
must be installed.
•
The MSXML COM object for Microsoft Excel, msxml4.dll, must be present on the system.
For confirmation, navigate to %SystemRoot%\system32\msxml4.dll. Right-click and select Properties. On the
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
453
Setting Up Process Scheduler on Windows
Chapter 10A
msxml4.dll Properties dialog box, select the Version tab, and then Product Version. As shown on this example
of the msxml4.dll Properties dialog box, the version number must be 4.20 or above.
msxml4.dll Properties dialog box: Version tab
See Also
PeopleTools: Setup Manager
Microsoft support, support.microsoft.com
Task 10A-9: Installing Products for PS/nVision
This section discusses:
•
Understanding the PS/nVision Setup
•
Installing Products for PS/nVision in Excel Automation Mode
•
Installing Microsoft .NET Framework Products for PS/nVision
•
Installing Microsoft Open XML SDK for PS/nVision
454
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10A
Setting Up Process Scheduler on Windows
Understanding the PS/nVision Setup
PS/nVision can operate in the following three modes for PS/nVision:
•
OpenXML mode
OpenXML is the default mode for PeopleSoft PeopleTools.
•
Excel automation mode
•
Cross-platform mode
Cross Platform is the only supported mode on the UNIX platforms that are certified for executing PS/nVision
Reports on the web.
The different modes of executing PS/nVision are enabled by setting the UseExcelAutomation parameter in the
Process Scheduler configuration file (psprcs.cfg) as follows:
•
0 - OpenXML mode
•
1 - Excel Automation mode
•
2 - Cross Platform mode
See Also
PeopleTools: PS/nVision
PeopleTools: Process Scheduler
Task 10A-9-1: Installing Products for PS/nVision in Excel Automation Mode
To set up PS/nVision in Excel automation mode:
•
For all batch servers, install Microsoft Excel on the batch server. PeopleSoft PeopleTools supports 64–bit
versions of Microsoft Excel 2010 and Excel 2013.
Note. The 32–bit version of Microsoft Excel should not be installed on the machine where PS/nVision needs
to run in Excel Automation Mode, as that would cause issues with running PS/nVision with 64–bit Microsoft
Excel.
•
If the batch server is on a 64–bit Microsoft Windows 2008 machine, create an empty "Desktop" folder with
this path:
C:\Windows\System32\config\systemprofile\Desktop
Task 10A-9-2: Installing Microsoft .NET Framework Products for PS/nVision
This section discusses:
•
Installing Microsoft .NET Framework 3.5
•
Verifying the Microsoft .NET Framework Installation on Microsoft Windows 2008 R2
•
Installing Microsoft .NET Framework 4.0
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
455
Setting Up Process Scheduler on Windows
Chapter 10A
Installing Microsoft .NET Framework 3.5
Before setting up PS/nVision in OpenXML mode, use these instructions to install Microsoft .NET Framework.
Microsoft Open XML SDK 2.0 requires Microsoft .NET Framework versions 3.5 and version 4.0.
Note. If your operating system is Microsoft Windows 2008 R2, see the following section.
See Verifying the Microsoft .NET Framework Installation on Microsoft Windows 2008 R2.
To install Microsoft .NET Framework 3.5 SP1:
1. If there are any versions of Microsoft .NET Framework installed on your computer:
a. Select Start, Programs, Control Panel, Add/Remove Programs
b. Locate the existing Microsoft .NET Framework installations and remove them.
2. Go to PS_HOME\setup\dotnetredist.
3. Run the dotnetfx35.exe.file.
456
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10A
Setting Up Process Scheduler on Windows
4. Review the license agreement, select the option I have read and ACCEPT the terms of the License Agreement,
and then click Install.
Microsoft .NET Framework 3.5 SP1 Setup Welcome to Setup window
A progress window appears. Do not close the installer window when you see this message: "Download
complete. You can now disconnect from the Internet," as the installation continues after this point.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
457
Setting Up Process Scheduler on Windows
Chapter 10A
Microsoft .NET Framework 3.5 SP1 Setup Download and Install window
458
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10A
Setting Up Process Scheduler on Windows
5. Click Exit when the installation is complete.
The Setup Complete window includes the message "Microsoft .NET Framework 3.5 SP1 has been installed
successfully."
Microsoft .NET Framework 3.5 SP1 Setup Complete window
Verifying the Microsoft .NET Framework Installation on Microsoft Windows 2008 R2
If your operating system is Microsoft Windows 2008 R2, Microsoft .NET Framework 3.5 SP1 is included as a
feature. To verify that Microsoft .NET Framework 3.5 SP1 is installed and enabled:
1. Open Server Manager.
Note. Server Manager is found under Administrative Tools.
2. Verify if Microsoft .NET Framework 3.5 SP1 is listed as a feature in the Feature Summary section.
If yes, then Microsoft .NET Framework 3.5 SP1 is already installed on this computer and it is enabled.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
459
Setting Up Process Scheduler on Windows
Chapter 10A
3. If Microsoft .NET Framework 3.5 SP1 is not listed in the feature summary, then click Add Features to open
the Add Feature wizard.
In this example, Microsoft .NET Framework 3.5 SP1 is listed as .NET Framework 3.5.1 (Installed).
Add Features Wizard dialog box
4. If Microsoft .NET Framework 3.5 SP1 is listed in the list of features, it means it is installed on this computer,
but not enabled.
To enable this feature, select the check box for Microsoft .NET Framework 3.5 SP1 and complete the Add
Feature process. Consult the Microsoft Windows documentation for information on completing the process.
5. If Microsoft .NET Framework 3.5 SP1 is not listed in the list of features, then it is not installed on this box.
Refer to the previous section to install Microsoft .NET Framework 3.5 SP1.
See Installing Microsoft .NET Framework 3.5 SP1.
Installing Microsoft .NET Framework 4.0
To install Microsoft .NET Framework 4.0:
1. If there is an existing installation of Microsoft .NET Framework 4.0 installed on your computer:
a. Select Start, Programs, Control Panel, Add/Remove Programs
b. Locate the existing Microsoft .NET Framework installation and remove it.
2. Go to PS_HOME\setup\dotnetredist.
3. Run the dotNetFx40_Full_x86_x64.exe.file.
460
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10A
Setting Up Process Scheduler on Windows
4. Review the license agreement, select the option I have read and accept the license terms, and then click Install.
Microsoft .NET Framework 4 Setup window with license agreement
A progress indicator appears
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
461
Setting Up Process Scheduler on Windows
Chapter 10A
Microsoft .NET Framework 4 Setup progress indicator
462
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10A
Setting Up Process Scheduler on Windows
5. Click Finish when the installation is complete.
Microsoft .NET Framework 4 Installation Complete window
Task 10A-9-3: Installing Microsoft Open XML SDK for PS/nVision
As described in the previous section, you must have installed Microsoft .NET Framework versions 3.5 and 4.0
before beginning this installation.
To install Microsoft Open XML SDK V2.0:
1. Go to PS_HOME\setup\OpenXmlSDK.
2. Run the OpenXMLSDKv2.msi file.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
463
Setting Up Process Scheduler on Windows
Chapter 10A
3. Click Next on the welcome window.
Microsoft Open XML SDK 2.0 welcome window
464
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10A
Setting Up Process Scheduler on Windows
4. Review the license agreement, select the option I agree, and then click Next.
Microsoft Open XML SDK 2.0 License Agreement window
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
465
Setting Up Process Scheduler on Windows
Chapter 10A
5. Accept the default location for the installation, C:\Program Files\Open XML SDK\V2.0, and then click Next.
Microsoft Open XML SDK 2.0 Select Installation Folder window
466
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10A
Setting Up Process Scheduler on Windows
6. Click Next on the Confirm Installation window to begin the installation.
Microsoft Open XML SDK 2.0 Confirm Installation window
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
467
Setting Up Process Scheduler on Windows
Chapter 10A
7. Click Close when the installation is complete.
Microsoft Open XML SDK 2.0 Installation Complete window
468
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10B
Setting Up Process Scheduler on UNIX
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 Up Process Scheduler Server Agent
Prerequisites
If your database runs on z/OS, you need to set up a Microsoft Windows batch environment on a Microsoft
Windows application server or on a dedicated Microsoft Windows workstation for Microsoft Windows-specific
batch processes, such as nVision reports, Cube Builder, or Microsoft Word. These processes are Microsoft
Windows-specific applications that cannot be executed by the Process Scheduler on z/OS.
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.
•
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.
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:
$HOME/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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
469
Setting Up Process Scheduler on UNIX
Chapter 10B
See Also
PeopleTools: Process Scheduler
My Oracle Support, Certifications
Task 10B-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.
If you were using PeopleSoft PeopleTools 8.50 or earlier, remove PS_HOME/appserv/PSADMIN prior to
installing the new release. If you have any customized configuration files (such as psappsrv.cfg, psconfig.sh,
pscbl.mak, psrun.mak, psprcs.cfg, and so on), copy them to another directory so that they are not overwritten
during the upgrade process. This enables you to preserve any tuned variables.
Configuration files are typically overwritten when you install the new release using the PeopleSoft Installer.
Task 10B-2: Setting Up Process Scheduler Security
This section discusses:
•
Understanding Process Scheduler Security
•
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
within your PeopleSoft database.
You must carry out this task to start Process Scheduler successfully.
Task 10B-2-1: 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.
470
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10B
Setting Up Process Scheduler on UNIX
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 10B-3: Setting Up Process Scheduler to Transfer Reports
and Logs to the Report Repository
This section discusses:
•
Understanding Report Distribution
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
471
Setting Up Process Scheduler on UNIX
Chapter 10B
•
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
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.
472
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10B
Setting Up Process Scheduler on UNIX
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
473
Setting Up Process Scheduler on UNIX
Chapter 10B
Task 10B-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 10B-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. If the PeopleSoft Process Scheduler is on DB2 z/OS, use
FTP/FTPS or HTTP/HTTPS.
474
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10B
Setting Up Process Scheduler on UNIX
Note. If you are using FTP/FTPS or SFTP, the corresponding daemon must be set up in your web server.
Note. If you are on DB2 z/OS, you need to have JRE set up on your Process Scheduler server.
Task 10B-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 10B-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 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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
475
Setting Up Process Scheduler on UNIX
Chapter 10B
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:
476
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10B
Setting Up Process Scheduler on UNIX
•
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 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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
477
Setting Up Process Scheduler on UNIX
Chapter 10B
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.
478
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10B
Setting Up Process Scheduler on UNIX
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 UNIX, the default directory is <user_home>/PeopleSoft Internet Architecture/psreports/.
•
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.
479
Setting Up Process Scheduler on UNIX
Chapter 10B
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
Property Value
ACTIVEMODE
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
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
ENABLEEPRT
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.
EXTENDEDPASSIVEMODE
•
•
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.
480
JKSPASSWORD
Specify the Java keystore (JKS) password.
JKSPATH
Specify the Java keystore (JKS) path.
PASSWORD
Specify the password associated with the USER property,
which identifies the FTP User ID.
USER
Specify the FTP User ID used for authentication when
accessing the FTP site.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10B
Setting Up Process Scheduler on UNIX
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
481
Setting Up Process Scheduler on UNIX
Chapter 10B
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.
482
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10B
Setting Up Process Scheduler on UNIX
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 UNIX, the default directory is <user_home>/PeopleSoft Internet Architecture/psreports/.
•
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
483
Setting Up Process Scheduler on UNIX
Chapter 10B
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
Property Value
ACTIVEMODE
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
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.
EXTENDEDPASSIVEMODE
•
•
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.
484
JKSPASSWORD
Specify the Java keystore (JKS) password.
JKSPATH
Specify the Java keystore (JKS) user.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10B
Setting Up Process Scheduler on UNIX
Property Name
Property Value
KEYSTOREPASSWORD
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.
PASSWORD
Specify the password associated with the USER property,
which identifies the FTP User ID.
SSLUAGELEVEL
•
•
0 - No SSL: No SSL will be used.
•
•
2 - Control: Require SSL for the control connection.
1 - Try SSL: Try using SSL, but proceed as normal
otherwise.
3 - SSL Only: (Default) Require SSL for all
communication.
USER
Specify the FTP User ID used for authentication when
accessing the FTP site.
VERIFYHOST
•
•
0: Do not verify the server for host name.
•
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.
VERIFYPEER
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.
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:
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
485
Setting Up Process Scheduler on UNIX
Chapter 10B
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.
486
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10B
Setting Up Process Scheduler on UNIX
3. On the Report Node Definition page, select SFTP from the Protocol drop-down list.
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
487
Setting Up Process Scheduler on UNIX
Chapter 10B
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 UNIX, the default directory is <user_home>/PeopleSoft Internet Architecture/psreports/.
•
488
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.
Chapter 10B
Setting Up Process Scheduler on UNIX
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
Property Value
AUTHTYPE
Select one of the following the authentication types:
•
•
•
PUBLICKEY
PASSWORD
ANY
PASSWORD
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
Enter the password for the private key.
PRIVATEKEY
Select the private key.
PUBLICKEY
Select the public key.
SSHKEYALIAS
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."
USER
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
489
Setting Up Process Scheduler on UNIX
Chapter 10B
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 10B-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 PSUNX). The Server Definition page appears.
3. Select the Distribution tab.
Server Definition page for PSUNX: 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.
490
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10B
Setting Up Process Scheduler on UNIX
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 10B-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 10B-4: Setting Up Process Scheduler Server Agent
This section discusses:
•
Understanding Process Scheduler Server Agent
•
Changing the Default Operating System
•
Creating and Configuring a Process Scheduler Server
•
Reconfiguring a Process Scheduler Server
•
Verifying the Process Scheduler Server Status
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
Operating System
PSUNX
UNIX
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
491
Setting Up Process Scheduler on UNIX
Chapter 10B
Task 10B-4-1: Changing the Default Operating System
By default, Process Scheduler is set up to run a process request from a Process Scheduler Server Agent started in
a Microsoft Windows server when the value of the ServerName field in the Process Request Dialog page is left
blank. If you plan to run all processes other than Microsoft Windows-based programs (such as nVision) from
UNIX, you must change the default operating system.
Note. If you do not change the default operating system from Windows to UNIX and you do not plan to set up a
Process Scheduler Server Agent in Microsoft Windows, process requests that are created will be directed to a
Microsoft Windows-based operating system and will remain in the "Queued" status.
To change the default operating system for process requests that were not assigned a Process Scheduler Server
Name:
1. Select PeopleTools, Process Scheduler, System Settings.
2. Under Primary Operating System, choose UNIX from the drop-down list.
3. Click on the System Purge Options tab. Enter the date for the next purge of process requests in the Next Purge
Date field.
4. Enter the time for the next purge of process requests in the Next Purge Time field. The default time is
12:00:00AM.
5. Enter a Recurrence if you want to set a regular purging basis.
6. Choose Save.
Task 10B-4-2: 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. 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. Run the psadmin command.
You see the PeopleSoft Server Administration menu, as in this example:
-------------------------------------------PeopleSoft Server Administration
--------------------------------PS_CONFIG_HOME /home/JSMITH/psft/pt/8.55
PS_HOME /home/PT855
PS_APP_HOME /home/HC9.2
1) Application Server
2) Process Scheduler
3) Search Server
492
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10B
Setting Up Process Scheduler on UNIX
4) Web (PIA) Server
5) Switch Config Home
6) Replicate Config Home
7) Refresh Config Home
q) Quit
Command to execute (1-7 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] Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
493
Setting Up Process Scheduler on UNIX
Chapter 10B
2) Master Scheduler : Yes 10) DBTYPE :[DB2ODBC] 3) Perf Collator : No 11) PrcsServer :[PSUNX]
4) Domains Gateway : No 12) UserId :[QEDMO]
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/ODB⇒
/bin] 18) AddToPATH :[%PS_HOME%/cblbin]
19) 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-18, h, or q):
494
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10B
Setting Up Process Scheduler on UNIX
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
Description
Master Scheduler
Select this option to enable the Master Scheduler Server
(PSMSTPRC). The default is to enable the server.
See PeopleTools: Process Scheduler.
App Engine
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.
Perf Collator
Select this option to enable the PSPPMSRV server
process.
See PeopleTools: Performance Monitor, "Enabling the
Required Elements on the Monitoring System."
Domain Gateways
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."
Push Notifications
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 config as shown
Load the selections you made in the Quick Configure
menu.
Custom configuration
Make custom selections in PSADMIN, using options that
are not available in the Quick Configure menu.
Edit environment settings
Edit, add, remove, comment out, and review domain-level
environment variables.
DBNAME
Specify the database name that is associated with a
PeopleSoft Process Scheduler Server Agent, such as
HRDMO, FSDMO, SADMO, and so on.
DBTYPE
Specify the database type: DB2ODBC (for DB2 for z/OS).
PrcsServer
Specify the process server name. This must match the
name defined in the Server Definition table, such as PSNT
or PSUNX.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
495
Setting Up Process Scheduler on UNIX
Chapter 10B
Parameter
Description
UserId
Enter the user ID, such as VP1 or PS.
UserPswd
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.
ConnectID
Enter the connect ID. This value is required.
ConnectPswd
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.
Log/Output Dir
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.
SQRBIN
Enter the path to the SQR executables.
AddToPATH
(Optional for Tuxedo) Specify an additional directory that
is appended to the PATH environment variable.
DomainConnectPswd
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.
496
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10B
Setting Up Process Scheduler on UNIX
-------------------------------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.
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 10B-4-3: 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. Run the command:
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:
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
497
Setting Up Process Scheduler on UNIX
Chapter 10B
************************************************************
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.
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.
498
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10B
•
Setting Up Process Scheduler on UNIX
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 10B-4-4: 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
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⇒
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
499
Setting Up Process Scheduler on UNIX
Chapter 10B
Service
--------- ---------- -------- -- ------ --------- -----------⇒
---DDL 46845 pt-ibm20 0 9 450 ( IDLE )
PSMONITORSRV MONITOR MONITOR 1 0 0 ( IDLE )
PSAESRV 00101.00001 AESRV 1 0 0 ( IDLE )
PSAESRV 00101.00002 AESRV 2 0 0 ( IDLE )
PSAESRV 00101.00003 AESRV 3 0 0 ( IDLE )
PSPRCSRV SCHEDQ BASE 101 0 0 ( IDLE )
PSMSTPRC MSTRSCHQ BASE 102 0 0 ( IDLE )
PSDSTSRV DSTQ BASE 103 0 0 ( IDLE )
>
Note. You can also do this using the following command line argument:
psadmin -p status -d <DBNAME>
Note. 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.
500
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
Setting Up Process Scheduler on z/OS
This chapter discusses:
•
Prerequisites
•
Preparing the Process Scheduler File System for a PeopleTools-Only Upgrade
•
Granting Required Authorization in DB2 and UNIX System Services
•
Setting Up Process Scheduler Security
•
Setting Up Process Scheduler to Transfer Reports and Logs to the Report Repository
•
Setting Up Process Scheduler Server Agent
Prerequisites
If your database runs on z/OS, you need to set up a Microsoft Windows batch environment on a Microsoft
Windows application server or on a dedicated Microsoft Windows workstation for Microsoft Windows-specific
batch processes, such as nVision reports, Cube Builder, or Microsoft Word. These processes are Microsoft
Windows-specific applications that cannot be executed by the Process Scheduler on z/OS.
Before setting up your Process Scheduler, you must:
•
Install database connectivity to be able to communicate with your database server (Process Scheduler requires
a direct connection to the database).
The Process Scheduler running on z/OS USS uses the DB2 ODBC component to connect to DB2. DB2
ODBC must be installed by your DB2 systems programmer; installation details are available in the IBM DB2
Installation Guide.
•
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 JDK/JRE 1.6.0 (z/OS Java 2 kit) on z/OS.
•
Apply all the required IBM patches listed in the document "Important PTFs for the PeopleSoft on DB2 for
z/OS."
See Important PTFs for the PeopleSoft on DB2 for z/OS, My Oracle Support (search for the article name).
•
Set up your database connectivity to access the PeopleSoft database from UNIX System Services with ODBC
for z/OS.
•
Install IBM's system stored procedure DSNUTILS. This is only required if you intend to run
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
501
Setting Up Process Scheduler on z/OS
Chapter 10C
%UPDATESTAT meta-SQL coded in Application Engine, COBOL and Process Scheduler. If you do not
have DSNUTILS installed, make sure you set the DBFLAGS parameter in the Process Scheduler
Configuration file to "1" to disable performing this statistics within.
See "Creating a Database," Planning Your Installation.
•
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.
•
PeopleSoft binaries are compiled and linked with IBM's XPLINK (Extra option Linkage) option enabled. In
order for all PeopleSoft executables to successfully run from UNIX System Services (USS), it is
recommended to include the IBM Language Environment Run Time library CEE.SCEERUN2 dataset
concatenated into your system library using IBM's LNKLIST utility. This IBM library CEE.SCEERUN2 may
have been renamed in your system. It will be the dataset containing the CELHV003 load module.
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 10C-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 10C-2: Granting Required Authorization in DB2 and UNIX
System Services
This section discusses:
502
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
•
Setting UNIX System Services Authorization
•
Setting DB2 Authorization
Setting Up Process Scheduler on z/OS
Task 10C-2-1: Setting UNIX System Services Authorization
This section discusses:
•
Providing Read/Write Access to the Designated Log/Output Directory
•
Providing Access to TSO and USS
Providing Read/Write Access to the Designated Log/Output Directory
All processes released by Process Scheduler will create and write files to an Hierarchical File System (HFS)
directory in UNIX System Services (USS). This HFS directory is designated by the Log/Output Directory
parameter found in the Process Scheduler section of the Process Scheduler configuration file. By default the
log/output directory will be
$PS_HOME/appserv/prcs/<database name>/log_output
JCL's generated by Process Scheduler to submit COBOL or SQR include step(s) that will copy the log file(s) and
reports (for SQR) to the Log/Output directory in USS. If the JCL job card includes the USER/PASSWORD
parameter, the user ID specified in the USER parameter must also be given read/write access to this HFS
directory. In this case, where multiple mainframe ID's will be writing to this directory, you need to set up a group
ID (GID) in RACF and assign the mainframe user ID to this GID. Once you have established this in RACF, make
sure the group ID is the owning group of the log/output directory.
As an example, HRASB and PSOFT IDs are required to write to the log/output directory. A DBAUNIX group ID
is set up so both HRASB and PSOFT are connected to this group in RACF. For the group to have read/write
access, the mode of the directory is changed (using the UNIX command chmod) so UID and GID have read/write
access.
$ ls -l
total 152
drwxrwx--- 11 HRASB DBAUNIX 8192 Dec 5 17:43 log_output
Providing Access to TSO and USS
All mainframe user IDs involved in submitting a JCL in TSO or Process Scheduler and Application Engine in
USS must be set up in RACF to have access to both TSO and USS environments. Certain procedures in Process
Scheduler will perform an OCOPY (from a JCL) or OPUT as a TSO command in USS to transfer files from a
PDS into an HFS directory. These procedures are triggered when posting reports and log files from a COBOL
and/or SQR. The Distribution Agent will temporarily copy the files from a partitioned dataset (PDS) or sequential
file into a designated HFS directory before posting the files to the repository.
To verify that the mainframe ID has all the proper authorization to perform the transfer, you can issue this test
from USS.
To verify the mainframe ID's authorization:
1. Log in to the USS with the user ID that will be used to boot Process Scheduler
2. Enter the following command in USS:
tso OPUT "'<Partitioned data set(member)>' '<HFS file>"
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
503
Setting Up Process Scheduler on z/OS
Chapter 10C
As an example:
$ tso OPUT "'FS.FS840A8.JCLLIB(SQRSAMP)' '/tmp/test.txt'"
OPUT 'FS.FS840A8.JCLLIB(SQRSAMP)' '/tmp/test.txt'
IGD103I SMS ALLOCATED TO DDNAME SYS00001
In this example, the PDS member SQRSAMP is copied into the HFS file /tmp/test.txt.
See Also
IBM publications, http://www-1.ibm.com/servers/eserver/zseries/zos/unix/bpxa1pub.html
Systems Planning Guide (SA22-7800)
User's Guide (SA22-7801)
Task 10C-2-2: Setting DB2 Authorization
This section discusses:
•
Setting Authorization for DB2 Plan for ODBC for OS390
•
Setting Authorization for DB2 Plans for COBOL
•
Setting Authorization for DB2 Plan for SQR
Setting Authorization for DB2 Plan for ODBC for OS390
The privilege to execute the DB2 plan for the CLI/ODBC package DSNAOCLI must be given to the mainframe
ID used to login to UNIX System Services to start Process Scheduler Server Agent. When Process Scheduler or
Application Engine program connects to the DB2 database, CLI/ODBC authenticates the connection based on the
user ID that initiates the program from UNIX System Services.
Grant EXECUTE on PLAN <PLAN for CLI Package DSNAOCLI> To <Unix Service⇒
Login ID>
Setting Authorization for DB2 Plans for COBOL
Enter the following command to set authorization for DB2 Plans for COBOL:
Grant EXECUTE on PLAN <SQLRT Plan PTPSQLRA and PTPSQLRE> To <Access-Id> or⇒
<Ownerid>;
The variable <SQLRT Plan PTPSQLRA and PTPSQLRE > refers to the plans created during database creation.
See "Creating a Database," Binding DB2 Plans.
Setting Authorization for DB2 Plan for SQR
Enter the following command to set authorization for DB2 Plan for SQR:
Grant EXECUTE on PLAN <SQR PLAN> To <Access-Id> or <Ownerid>;
The variable <SQR PLAN> refers to the plan created when installing SQR for z/OS.
504
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
Setting Up Process Scheduler on z/OS
Task 10C-3: Setting Up Process Scheduler Security
This section discusses:
•
Understanding Process Scheduler Security
•
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
within your PeopleSoft database.
You must carry out this task to start Process Scheduler successfully.
Task 10C-3-1: 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.
505
Setting Up Process Scheduler on z/OS
Chapter 10C
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.
Note. When setting up Process Scheduler on UNIX or Windows, you must have the right user ID to start an
application server. This authorization is not required to bring up Process Scheduler in z/OS UNIX System
Services because Process Scheduler is not booted through Tuxedo in this platform.
Task 10C-4: Setting Up Process Scheduler to Transfer Reports
and Logs to the Report Repository
This section discusses:
•
Understanding Report Distribution
•
Setting Up Single Signon to Navigate from PIA to Report Repository
•
Determining the Transfer Protocol
506
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
•
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 z/OS
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.
507
Setting Up Process Scheduler on z/OS
Chapter 10C
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.
508
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
Setting Up Process Scheduler on z/OS
Task 10C-4-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 10C-4-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. If the PeopleSoft Process Scheduler is on DB2 z/OS, use
FTP/FTPS or HTTP/HTTPS.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
509
Setting Up Process Scheduler on z/OS
Chapter 10C
Note. If you are on DB2 z/OS, you need to have JRE set up on your Process Scheduler server.
Task 10C-4-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 10C-4-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 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.
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.
4. Enter the following information in the Distribution Node Details area:
510
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
•
Setting Up Process Scheduler on z/OS
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:
•
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 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
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
511
Setting Up Process Scheduler on z/OS
Chapter 10C
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.
3. On the Report Node Definition page, select FTP from the Protocol drop-down list.
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.
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.
•
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.
512
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
Setting Up Process Scheduler on z/OS
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
Property Value
ACTIVEMODE
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
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
ENABLEEPRT
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.
EXTENDEDPASSIVEMODE
•
•
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
Specify the Java keystore (JKS) password.
JKSPATH
Specify the Java keystore (JKS) path.
PASSWORD
Specify the password associated with the USER property,
which identifies the FTP User ID.
USER
Specify the FTP User ID used for authentication when
accessing the FTP site.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
513
Setting Up Process Scheduler on z/OS
Chapter 10C
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.
3. On the Report Node Definition page, select FTPS from the Protocol drop-down list.
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.
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:
514
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
Setting Up Process Scheduler on z/OS
•
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.
•
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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
515
Setting Up Process Scheduler on z/OS
Chapter 10C
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
Property Value
ACTIVEMODE
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
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.
EXTENDEDPASSIVEMODE
•
•
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.
516
JKSPASSWORD
Specify the Java keystore (JKS) password.
JKSPATH
Specify the Java keystore (JKS) user.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
Setting Up Process Scheduler on z/OS
Property Name
Property Value
KEYSTOREPASSWORD
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.
PASSWORD
Specify the password associated with the USER property,
which identifies the FTP User ID.
SSLUAGELEVEL
•
•
0 - No SSL: No SSL will be used.
•
•
2 - Control: Require SSL for the control connection.
1 - Try SSL: Try using SSL, but proceed as normal
otherwise.
3 - SSL Only: (Default) Require SSL for all
communication.
USER
Specify the FTP User ID used for authentication when
accessing the FTP site.
VERIFYHOST
•
•
0: Do not verify the server for host name.
•
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.
VERIFYPEER
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.
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:
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
517
Setting Up Process Scheduler on z/OS
Chapter 10C
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.
3. On the Report Node Definition page, select SFTP from the Protocol drop-down list.
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.
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:
•
518
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
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
Setting Up Process Scheduler on z/OS
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.
•
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.
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
Property Value
AUTHTYPE
Select one of the following the authentication types:
•
•
•
PUBLICKEY
PASSWORD
ANY
PASSWORD
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
Enter the password for the private key.
PRIVATEKEY
Select the private key.
PUBLICKEY
Select the public key.
SSHKEYALIAS
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."
USER
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Specify the user ID to be authenticated.
519
Setting Up Process Scheduler on z/OS
Chapter 10C
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.
Task 10C-4-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 PSOS390). The Server Definition page appears.
3. Select the Distribution tab.
Server Definition page for PSOS390: Distribution tab
4. Click the lookup button for Distribution Node Name to display the report node names and select the name of
520
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
Setting Up Process Scheduler on z/OS
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.
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 10C-4-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 10C-5: Setting Up Process Scheduler Server Agent
This section discusses:
•
Understanding Process Scheduler Server Agent
•
Changing the Default Operating System
•
Setting Up Your Environment
•
Validating and Editing the ODBC Initialization File
•
Creating a Process Scheduler Server
•
Configuring Process Scheduler Server
•
Working with Shell JCL Templates
•
Starting a Process Scheduler Server
•
Verifying the Process Scheduler Server Status
•
Stopping the Process Scheduler Server
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
521
Setting Up Process Scheduler on z/OS
Chapter 10C
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
Operating System
PSOS390
z/OS
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 10C-5-1: Changing the Default Operating System
By default, Process Scheduler is set up to run a process request from a Process Scheduler Server Agent started in
a Microsoft Windows server when the value of the ServerName field in the Process Request Dialog page is left
blank. If you plan to run all processes other than Microsoft Windows-based programs (such as nVision) from
z/OS, you must change the default operating system.
Note. If you do not change the default operating system from Microsoft Windows to z/OS and you do not plan to
set up a Process Scheduler Server Agent in Windows, process requests that are created will be directed to a
Windows-based operating system and will remain in the "Queued" status.
To change the default operating system for process requests that were not assigned a Process Scheduler Server
Name:
1. Select PeopleTools, Process Scheduler, System Settings.
2. Under Primary Operating System, choose OS390 from the drop-down list.
3. Click on the System Purge Options tab. Enter the date for the next purge of process requests in the Next Purge
Date field.
4. Enter the time for the next purge of process requests in the Next Purge Time field. The default time is
12:00:00AM.
5. Enter a Recurrence if you want to set a regular purging basis.
6. Choose Save.
Task 10C-5-2: Setting Up Your Environment
Alternatively, make sure the following environment variables are set in the profile file in the user's home
directory:
Run psconfig.sh file from PS_HOME:
. ./psconfig.sh
522
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
Setting Up Process Scheduler on z/OS
Task 10C-5-3: Validating and Editing the ODBC Initialization File
The PeopleSoft Batch Transfer program generates the ODBC initialization file based on the parameters entered in
the PeopleSoft Server Transfer panel. The ODBC initialization file is written to:
$PS_HOME/appserv/odbc.ini
The ODBC initialization file contains the following key information:
•
DB2 subsystem name
•
Plan name for the DSNAOCLI CLI package
• Method used to attach to DB2 (default is RRSAF)
Here is an example of an initialization file for a DB2 subsystem called DSNW with DB2 plan DSNACLI:
[COMMON]
MVSDEFAULTSSID=DSNW
APPLTRACE=0
APPLTRACEFILENAME=
MULTICONTEXT=1
CONNECTTYPE=1
; Set up the DB2 Subsystem Definition
[DSNW]
MVSATTACHTYPE=RRSAF
PLANNAME=DSNACLI
Verify that all the information contained in this file is accurate. If you plan to set up multiple Process Scheduler
Server Agents for different instances of a PeopleSoft database and these databases reside in different DB2
subsystems, you must create a different ODBC initialization file for each DB2 subsystem.
Task 10C-5-4: Creating a Process Scheduler Server
This section describes how to create a Process Scheduler server.
Note. 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. 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 a Process Scheduler Server:
1. From PS_HOME/appserv on the batch server, type 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.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
523
Setting Up Process Scheduler on z/OS
Chapter 10C
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 PeopleSoft Process Scheduler Administration menu.
4. Select 2 for Create a Process Scheduler Server Configuration:
-------------------------------------------PeopleSoft Process Scheduler Administration
------------------------------------------- 1) Administer a Process Scheduler Server
2) Create a Process Scheduler Server Configuration
3) Delete a Process Scheduler Server Configuration
4) Import an existing Process Scheduler 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
You see screen messages like these:
Process Scheduler Configuration templates:
1) os390
Selecting the only Process Scheduler Configuration template available...
Creating Process Scheduler Server for Database HRDMO...
Copying Process Scheduler Server configuration file(s)...
Copying Process Scheduler JCL template files...
Process Scheduler Shell JCL template files copied.
Process Scheduler Server configuration created.
At this point, you are returned to the PeopleSoft Process Scheduler Administration menu.
Task 10C-5-5: Configuring Process Scheduler Server
This section discusses:
•
Configuring a Process Scheduler Server
•
Using [Startup]
524
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
•
Using [OS390]
•
Using [Process Scheduler]
•
Using [Application Engine]
Setting Up Process Scheduler on z/OS
Note. The section may not mention certain PSADMIN sections, if you do not need to change any of their defaults.
For more in depth descriptions of the Process Scheduler options in the PSADMIN, consult the PeopleTools:
Process Scheduler product documentation.
Configuring a Process Scheduler Server
To configure a Process Scheduler Server:
1. The PeopleSoft Process Scheduler Server Administration interface should already be on your screen from the
last step, but if it is not, go to PS_HOME/appserv and enter:
psadmin
Press ENTER, and then 2 to access the PeopleSoft Process Scheduler Administration menu.
2. From the PeopleSoft Process Scheduler Administration menu, select option 1 to Administer a domain:
------------------------------------------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) : 1
3. Select the database for which the Process Scheduler needs to be configured.
Database list:
1) HRDMO
Select item number to configure: 1
4. At the following 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.
Specify n if you have already edited psprcs.cfg.
See PeopleTools: Process Scheduler.
Using [Startup]
When using PSADMIN to configure a Process Scheduler Server Agent, you first encounter the Startup section:
Values for config section - Startup
DBName=
DBType=DB2ODBC
UserId=
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
525
Setting Up Process Scheduler on z/OS
Chapter 10C
UserPswd=
ConnectId=
ConnectPswd=
ServerName
StandbyDBName=
StandbyDBType=
StandbyUserId=
StandbyUserPswd=
Do you want to change any values (y/n)? [n]: y
The following table describes each value in the Startup section:
Value
Description
DBName
Specify the database name associated with a particular
Process Scheduler Server Agent, such as HRDMO, FSDMO,
SADMO, and so on.
DBType
Specify the database type. The default for DB2 for z/OS is
DB2ODBC.
UserId
Enter the user ID.
UserPswd
Enter the user password.
The password is hidden by masking characters as you type.
ConnectId
Enter the connect ID. This value is required.
ConnectPswd
Enter the connect password. This value is required.
The password is hidden by masking characters as you type.
ServerName
For DB2 for z/OS, ignore this item.
StandbyDBName
For DB2 for z/OS, ignore this item.
StandbyDBType
For DB2 for z/OS, ignore this item.
StandbyUserId
For DB2 for z/OS, ignore this item.
StandbyUserPswd
For DB2 for z/OS, ignore this item.
When you change the UserPswd or ConnectPswd field, you are prompted for an option to encrypt the value
entered for the password field:
Do you want to encrypt this password? [y]:y
Enter y if you want the password stored in encrypted form in the Process Scheduler configuration file. (The
default is to encrypt the password.)
526
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
Setting Up Process Scheduler on z/OS
Using [OS390]
The OS390 section contains OS/390-specific values:
Values for config section - OS390
ODBC Initialization File=%PS_HOME%/appserv/odbc.ini
Shell JCL Library=%PS_SERVDIR%/shelljcl
High Level Qualifier for System Datasets=
High Level Qualifier for Log Datasets=
Plan name for PTPSQLRT with CAF=
Plan name for PTPSQLRT with TSO=
DB2 Sub-System=
VIO eligible unit group=SYSDA
Enable Parallel Processing=0
DECIMAL=PERIOD
TSO Character Set=cp037
Do you want to change any values (y/n)? [n]:
The following table describes each parameter in the OS390 section.
Parameter
Description
ODBC Initialization File
File containing ODBC setting to connect to the DB2
subsystem where the PS database is created.
Shell JCL Library
The subdirectory containing all JCL templates used for
submitting COBOL or SQR in native z/OS.
High Level Qualifier for System Datasets
Datasets to which PeopleSoft installations are copied during
batch transfer. For example, PT.PT810TA.
High Level Qualifier for Log Datasets
Datasets that represent the high level qualifier for all logs
and reports generated from processes submitted through
Process Scheduler.
Plan name for PTPSQLRT with CAF
DB2 plan used to run COBOL called within an Application
Engine program via Remote Call
Plan name for PTPSQLRT with TSO
DB2 plan used to run COBOL from TSO via JCL created
from the COBOL shell JCL template (SHECBL.JCT)
DB2 Sub-System
DB2 subsystem name where your database resides—for
example, DSND
VIO eligible unit group
DASD volume group used by Remote COBOL invoked by
an Application Engine program
Enable Parallel Processing
A Y/N flag which sets the Parallel processing parameter in
the COBOL shell JCL template (SHECBL.JCT)
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
527
Setting Up Process Scheduler on z/OS
Chapter 10C
Parameter
Description
DECIMAL
The value should reflect the setting for the DECIMAL
parameter found in the ZPARM of the DB2 subsystem
where the database resides. Valid values are DECIMAL or
COMMA.
TSO Character Set
The codepage for the TSO environment. The default value is
CP037 (IBM037: Latin1 code page).
Using [Process Scheduler]
After you have set your Trace values, the Process Scheduler section allows you to set all of the environment
variables associated with the Process Scheduler.
Values for config section - Process Scheduler
Prcs Job Name=
Prcs Job Account=
PrcsServerName=PSOS390
PS Configuration File=%PS_HOME%/psconfig.sh
Max Reconnect Attempt=12
Reconnection Interval=300
Authentication Timeout=5
TOOLBIN=%PS_HOME%/bin
Log/Output Directory=%PS_SERVDIR%/log_output
LogFence=5
DEFAULTPRINTER=
Do you want to change any values (y/n)? [n]:
The following table describes the parameters you must update in the Process Scheduler section:
Parameter
Description
Prcs Job Name
Job name assigned to the Process Scheduler program. This is
set in USS using the __BPX_JOBNAME environment
variable setting.
Prcs Job Account
Job Account assigned to the Process Scheduler program.
This is set in USS using the __BPX_ACCT_DATA
environment variable setting.
Using [Application Engine]
This section contains Application Engine values:
Values for config section - Application Engine
AE Job Name=%JOBNAME%%SFX%
AE Job Account=%JOBACCT%
528
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
Setting Up Process Scheduler on z/OS
Do you want to change any values (y/n)? [n]:
The following table describes each parameter in the Application Engine section:
Parameter
Description
AE Job Name
Job name assigned to an Application Engine program. This
is set in USS using the __BPX_JOBNAME environment
variable setting.
AE Job Account
Account assigned to an Application Engine program. This is
set in USS using the __BPX_ACCT_DATA environment
variable setting.
Note. After you complete your changes in PSADMIN, you must shut down and restart the server to put the new
settings into place.
Task 10C-5-6: Working with Shell JCL Templates
This section discusses:
•
Understanding Shell JCL Templates
•
Editing a Shell JCL Template
•
Customizing the Process Scheduler's Shell JCL Template
Understanding Shell JCL Templates
When starting a Process Scheduler Server, shell JCL template files are read once and stored into memory as part
of the initialization procedure. Process Scheduler will generate a JCL for COBOL and SQR based on the JCL
stored in memory. If you have modified any of the shell JCL templates after the Process Scheduler Server was
started, Process Scheduler will refresh the JCL stored in memory before submitting the next COBOL or SQR
request.
The PeopleSoft Server Transfer program creates a directory PS_HOME/appserv/prcs/shelljcl in UNIX Services to
store a master copy of the shell JCL templates. When you create a Process Scheduler Server Configuration, it
copies this shell JCL templates into the <PS_HOME>/appserv/prcs/<database_name>/shelljcl directory. This
includes all the JCLs used for running COBOL and SQR through Process Scheduler.
See "Creating a Database."
The following table lists the shell JCL templates used in Process Scheduler:
JCL
Description
SHELCBL.JCT
Invoked by Process Scheduler when user requests to run a COBOL
program
SHELSQRF.JCT
Invoked by Process Scheduler when user requests to run an SQR
program and specifies from the Process Scheduler page to route the
output to a file, web or email.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
529
Setting Up Process Scheduler on z/OS
Chapter 10C
JCL
Description
SHELSQRP.JCT
Invoked by Process Scheduler when user requests to run an SQR
program and specifies from the Process Scheduler panel to route the
output to a printer.
SHELSQROUTP.JCT
Used in conjunction with SHELSQRP.JCT or SHELSQRF.JCT.
This template contains the file definition for creating a partitioned
data set for SQR report files. Process Scheduler will use this
template when the SQR output format is one of the following:
•
•
•
•
SHELSQROUTS.JCT
Acrobat Reader (PDF)
Post Script (PS)
Line Printer (HP)
HP format
Used in conjunction with SHELSQRP.JCT or SHELSQRF.JCT.
This template contains the file definition for creating a sequential
data set for SQR report files. Process Scheduler will use this
template when the SQR output format is one of the following:
HTM
SPF
These shell JCL templates need to be modified to comply with your site standards.
Note. Process Scheduler does not use a JCL to submit an Application Engine program. Instead, Process Scheduler
will fork another (child) process in UNIX System Services and run Application Engine in this new process. This
schema is similar to Windows or UNIX operating system.
Editing a Shell JCL Template
To edit a shell JCL template:
1. Select option 1 for Administer a Process Scheduler Server from the PeopleSoft Process Scheduler
Administration menu:
-------------------------------------------PeopleSoft Process Scheduler Administration
------------------------------------------- 1) Administer a Process Scheduler Server
2) Create a Process Scheduler Server Configuration
3) Delete a Process Scheduler Server Configuration
4) Import an existing Process Scheduler Configuration
q) Quit
Command to execute (1-4, q): 1
2. Select 7 for Edit a Shell JCL:
------------------------------------------PeopleSoft Process Scheduler Administration
------------------------------------------530
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
Setting Up Process Scheduler on z/OS
Scheduler Name: HRDMO
1) Start Process Scheduler Server
2) Stop Process Scheduler Server
3) Show Status
4) Configure Process Scheduler Server
5) Edit Process Scheduler Configuration File
6) Kill a Process Scheduler Server
7) Edit a Shell JCL
q) Quit
Command to execute (1-7, q) : 7
3. Select the database for which the Process Scheduler needs to be configured.
Database list:
1) HRDMO
Select item number to edit: 1
4. Select the JCL from the list you intend to modify.
This opens the JCL in a vi editor screen.
JCL list:
1) shelcbl.jct
2) shelsqrf.jct
3) shelsqroutp.jct
4) shelsqrouts.jct
5) shelsqrp.jct
Select JCL file to edit: 1
5. Modify the JCL using vi commands
6. Save your changes by using the vi command :wq
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
531
Setting Up Process Scheduler on z/OS
Chapter 10C
If you are not familiar with the vi editor and would prefer to edit the JCLs using ISPF editor, you can use the TSO
oedit command in the TSO session. IBM's TSO oedit command allows you to modify any files residing in UNIX
System Services from a TSO session. You can edit any of the shell JCL templates found in <PS_HOME>/
appserv/prcs/<database_name>/shelljcl directory as shown below. Consult your z/OS system administrator for
using the oedit command at your site.
Editing a shell JCL template
Customizing the Process Scheduler's Shell JCL Template
All the Process Scheduler's shell JCLs use meta-strings to pass data stored in the database or Process Scheduler
configuration files. Process Scheduler takes advantage of meta-strings to generate the JCL based on one of these
sources:
•
User's profile who initiated the request
•
Parameters defined in the Process Scheduler Configuration file.
• Parameters defined in the Process Type Definition Page or Process Definition Page
A good example of data that can be passed includes job account and job name. To enter the values of some of
these variables you need to identify the Process Profile being used. Choose PeopleTools, Security, User Profiles,
User Profiles. Then search on the ID used to log on to the PeopleSoft Pure Internet Architecture. Make note of the
Process Profile Name. Then choose PeopleTools, Security, Permissions & Roles, Permission Lists and select the
Process Profile Name that was identified. Select Process tab, Process Profile Permissions.
The shell JCL templates are tunable and should be changed according to your site-specific standards. The table
below identifies all the available meta-strings you can use in a shell JCL template.
If you create a new JCL template, you must be aware of the following:
•
The Shell ID is restricted to three characters.
532
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
•
Setting Up Process Scheduler on z/OS
The Shell ID is associated with the Process Type Definition.
Meta-Strings
Description
%JOBNAME%
Specifies the value entered in z/OS Job Controls Name
field of the Process Profile Permission page for the
Permission Lists specified as the User ID's Process Profile.
The Process Profile for a User ID can be set using the User
Profiles page in the Maintain Security component.
%JOBACCT%
Specifies the value entered in z/OS Job Controls Account
field of the Process Profile Permission page.
%OUTDEST%
Specifies the output destination based on the value entered
in the Server Destinations File or Printer fields of the
Process Profile Permission page.
%SFX%
A one-character code issued by Process Scheduler. The
system will randomly assign a value from A to Z.
%OPRID%
The user ID used to submit the request from Process
Scheduler.
%PRCSLOGFILE%
The name of the log file Process Scheduler used to redirect
all data written to output for Application Engine or
SYSOUT in COBOL or SQR
%PRCSLOGDIR%
The directory where all log files or reports are written to in
UNIX System Services for a process.
%ACCESSID%
The access ID assigned for a user ID defined in
PSOPRDEFN.
%INSTANCE%
The process instance number assigned to a process
request.
%RUNID%
The run control ID used to submit the process request.
%OWNERID%
The owner ID for the PeopleSoft database.
%PRCSNAME%
The program name as defined in the Process Definition
page.
%DB2SUB%
The name of the DB2 subsystem specified in the DB2 SubSystem parameter of the OS390 section found in the
Process Scheduler Configuration file.
%PERFSTAT%
The flag used to set the Performance Statistic option in the
COBOL shell JCL. This is set to 'Y' when the bit value of
128 is assigned to the TraceSQL parameter of the Trace
section found in the Process Scheduler Configuration file.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
533
Setting Up Process Scheduler on z/OS
Chapter 10C
Meta-Strings
Description
%DYNEXPLN%
The flag used to set the Dynamic Explain option in the
COBOL shell JCL. This is set to 'Y' when the bit value of
256 is assigned to the TraceSQL parameter of the Trace
section found in the Process Scheduler Configuration file.
%PARALLEL%
The flag used to set the Dynamic Explain option in the
COBOL shell JCL. This is based on the flag set in the
Enable Parallel Processing parameter of the OS390
section found in the Process Scheduler Configuration file.
"%TSOPLAN%
The DB2 plan name subsystem specified in the Plan name
for PTPSQLRT with TSO parameter of the OS390 section
found in the Process Scheduler Configuration file.
%PSHLQ%
The high level qualifier of the PeopleSoft dataset specified
in High Level Qualifier for Datasets parameter of the
OS390 section found in the Process Scheduler
Configuration file.
Here is a sample job control card in one of the shell JCLs:
//%JOBNAME%%SFX% JOB %JOBACCT%,'PS-PRCS ',CLASS=E,MSGCLASS=X,
// NOTIFY=%OPRID%
If you choose not to use meta-strings, you can also update the job cards to remove all these variables and
replace them with actual values.
In the SHELL JCL for SQR, OUTNODE denotes either a z/OS partitioned data set (PDS) or sequential data
set. The PDS is a requirement for SQR output. If the SQR report XRFPANEL were directed to file output, the
following substitution would occur:
The following line in SHELSQRF.JCT
// OUTNODE='%OUTDEST%'
would be changed to:
// OUTNODE='HR.H800RAB',
If an SQR process were directed to print, the following substitutions would occur:
SQR:
// OUTNODE='DEST=U3', OPTIONAL:USER-DEF OUTPUT
..
//*********************************************************************
//* Main portion of JCL Shell
*
//*********************************************************************
..
//SQROUTP DD SYSOUT=*,DEST=U3
z/OS Job Controls:
z/OS job controls specify the z/OS job name you want assigned to each process submitted. This value can be
up to seven characters. Do not use lowercase letters or any quotation marks. If you included the %SFX%
meta-string as part of your job name, Process Scheduler will append a one-character alphabetical suffix to this
534
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
Setting Up Process Scheduler on z/OS
name (A through Z, chosen randomly), before job submission.
For example, if you entered USRMVS1, the assigned job name would become USRMVS1A through
USRMVS1Z. After you enter the z/OS job name, enter the job account number used in your installation.
Specify an account code to be inserted as the JCL accounting code.
Task 10C-5-7: Starting a Process Scheduler Server
Once you have configured the Process Scheduler Server, you are ready to start it.
To start a Process Scheduler Server:
1. Select option 1 for Administer a domain.
------------------------------------------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) : 1
2. Select the domain that you want to start.
Database list:
1) HRDMO
Select item number to start: 1
3. On the PeopleSoft Process Scheduler Administration menu, choose 1 for Start Process Scheduler Server.
------------------------------------------PeopleSoft Process Scheduler Administration
------------------------------------------ Scheduler Name: HRDMO
1) Start Process Scheduler Server
2) Stop Process Scheduler Server
3) Show Status
4) Configure Process Scheduler Server
5) Edit Process Scheduler Configuration File
6) Kill a Process Scheduler Server
7) Edit a Shell JCL
q) Quit
Command to execute (1-7, q) : 1
This will launch the Process Scheduler program.
Starting Process Scheduler Server PSOS390 for Database HRDMO ...
PeopleSoft Process Scheduler Started Normally
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
535
Setting Up Process Scheduler on z/OS
Chapter 10C
Task 10C-5-8: 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 3, for Show Status:
------------------------------------------PeopleSoft Process Scheduler Administration
------------------------------------------ Scheduler Name: HRDMO
1) Start Process Scheduler Server
2) Stop Process Scheduler Server
3) Show Status
4) Configure Process Scheduler Server
5) Edit Process Scheduler Configuration File
6) Kill a Process Scheduler Server
7) Edit a Shell JCL
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
Process Scheduler Server PSOS390 for Database PT84x is currently running
Process Agents PID
-------------- --- Process Scheduler 1144
Distribution Agent 35163243
Monitor 50332247
Note. 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.
Note. If you have not configured z/OS with a Distribution Node, the Distribution Agent will not be started. You
must execute that task before the Distribution Agent will be booted with the Process Scheduler server. See
Validating and Editing the ODBC Initialization File.
Task 10C-5-9: Stopping the Process Scheduler Server
To stop the Process Scheduler Server:
536
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 10C
Setting Up Process Scheduler on z/OS
1. From the PeopleSoft Process Scheduler menu, choose option 2, for Stop Process Scheduler Server.
------------------------------------------PeopleSoft Process Scheduler Administration
------------------------------------------ Scheduler Name: HRDMO
1) Start Process Scheduler Server
2) Stop Process Scheduler Server
3) Show Status
4) Configure Process Scheduler Server
5) Edit Process Scheduler Configuration File
6) Kill a Process Scheduler Server
7) Edit a Shell JCL
q) Quit
Command to execute (1-7, q) : 2
2. To stop the Process Scheduler Server for a specific database, type the number corresponding to the
appropriate database.
Example (to stop Process Scheduler Server for the database HRDMO):
Database list:
1) HRDMO
Select item number to stop: 1
Command sent to stop Process Scheduler Server PSOS390 for Database⇒
HRDMO. The⇒
Server Will stop the next time that it wakes up.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
537
Part II
Discretionary Installation
The second part of the installation guide includes optional tasks, tasks that are only required by certain
environments, and those that you may decide to defer until after the initial installation.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
539
Chapter 11
Configuring Integration Between PeopleSoft
PeopleTools and Oracle SES
This chapter discusses:
•
Understanding PeopleSoft PeopleTools and SES Integration
•
Preparing for the Integration of PeopleSoft PeopleTools and SES
•
Configuring SES for the Search Framework
•
Setting Up the PeopleSoft Application Server for the Search Framework
•
Setting Up Search Framework User IDs
•
Using the Search Administration Activity Guide
•
Verifying PeopleSoft PeopleTools and SES Connectivity
Understanding PeopleSoft PeopleTools and SES Integration
The PeopleSoft Search Framework provides a standard, declarative method for creating, deploying, and
maintaining search indexes for all of your PeopleSoft applications. Oracle Secure Enterprise Search (SES) is the
search engine on which the PeopleSoft Search Framework relies.
Before you can set up integration between PeopleSoft PeopleTools and Oracle Secure Enterprise Search, you
must first have SES installed and running successfully. Then you need to ensure that various elements on the
PeopleSoft Application Server and PeopleSoft Integration Broker are set appropriately. Integration Broker is the
vital link between PeopleSoft PeopleTools and SES. As such, it is essential to make sure that the gateway,
domains, nodes, services, and WSDL elements are activated and configured properly.
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" (Doc 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.
See Also
PeopleTools: Search Technology
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
541
Configuring Integration Between PeopleSoft PeopleTools and Oracle
SES
Chapter 11
Task 11-1: Preparing for the Integration of PeopleSoft
PeopleTools and SES
This section discusses:
•
Installing Oracle Secure Enterprise Search
•
Reviewing the PeopleSoft PeopleTools Prerequisites
Task 11-1-1: Installing Oracle Secure Enterprise Search
Before you begin the tasks in this chapter to integrate PeopleSoft PeopleTools and Oracle SES for the PeopleSoft
Search Framework, you must obtain Oracle SES from the Oracle Software Delivery Cloud portal, and complete
the installation. Use the Oracle Secure Enterprise Search documentation for hardware and software requirements,
and installation instructions.
See Installation and upgrade guide, Oracle Secure Enterprise Search Documentation 11g Release 2 (11.2.2.0.0),
http://docs.oracle.com/cd/E35215_01/index.htm.
PeopleSoft PeopleTools 8.55 supports Oracle SES 11.2.2.2. Be sure to check My Oracle Support Certifications
for up-to-date certification information. Check My Oracle Support for any patches, updates, or fixes you need to
apply for your Oracle SES installation.
After you complete the Oracle SES installation, make sure to record the following information, as it will be
required when configuring the integration between Oracle SES and PeopleSoft PeopleTools:
•
SES server host name, and the port on which SES is listening.
For example: sesserver.example.com:7777
•
SES administrator user ID and password, as in the credentials you use to sign on to the SES administration
console.
Task 11-1-2: Reviewing the PeopleSoft PeopleTools Prerequisites
Before you begin the tasks in this chapter to integrate PeopleSoft PeopleTools and Oracle SES for the PeopleSoft
Search Framework, the following items need to be installed, configured, and functional:
•
PeopleSoft PeopleTools
You need to have installed PeopleSoft PeopleTools and have at least the following items configured, as
described in the previous chapters of this installation documentation:
•
•
PeopleSoft database
•
Application server
•
Process Scheduler server
•
Integration Broker
See PeopleTools: Integration Broker Administration.
PeopleSoft Application
Because the searching feature is intended primarily for your end users, having your PeopleSoft application
database installed and available is recommended. This will allow you to define realistic search objects for
your testing and production environments.
See your PeopleSoft application installation documentation.
542
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 11
Configuring Integration Between PeopleSoft PeopleTools and Oracle
SES
Record the PeopleSoft Pure Internet Architecture signon URL as it will be required when carrying out the tasks in
this chapter:
For example: http://hostname.example.com:80/ps/signon.html
See "Setting Up the PeopleSoft Pure Internet Architecture," Accessing the PeopleSoft Signon.
Task 11-2: Configuring SES for the Search Framework
This section discusses:
•
Understanding the Oracle SES Configuration
•
Creating a Federated Trusted Entity
•
Activating the Identity Plug-in
•
Configuring SES Authentication Timeout Settings
•
Enabling Character Set Detection
•
Activating the Document Service Plugin
•
Using a Proxy with Oracle SES
Understanding the Oracle SES Configuration
After you have Oracle SES installed and running, you need to carry out the post-installation procedures in this
section to prepare the Oracle SES instance for integration with a PeopleSoft application system.
To complete these steps you will need access to the Oracle SES administration console, using the following URL
syntax:
http://<host>:<port>/search/admin/index.jsp
See Also
Administrator's Guide, Oracle Secure Enterprise Search Documentation 11g Release 2 (11.2.2.0.0),
http://docs.oracle.com/cd/E35215_01/index.htm
Task 11-2-1: Creating a Federated Trusted Entity
To create a federated trusted entity:
1. Sign on to the Oracle SES administration console.
2. Select the Global Settings tab.
3. In the Search list, select the Federation Trusted Entities link.
4. In the Entity Name edit box, enter the entity you want to create.
5. For Entity Password enter a password to associate with the trusted entity.
Note. Make note of the entity name and password, as you will be required to submit these credentials when
defining the Oracle SES instance in the PeopleSoft Search Framework administration interface.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
543
Configuring Integration Between PeopleSoft PeopleTools and Oracle
SES
Chapter 11
Note. The Identity Plug-in check box does not need to be selected, nor does the Authentication Attribute edit
box have to be populated.
6. (Recommended) In the Description edit box, add text to distinguish this entity.
7. Click Add.
Task 11-2-2: Activating the Identity Plug-in
To activate the identity plug-in:
1. Sign on to the Oracle SES administration console.
2. Select the Global Settings tab.
3. Under System, select the Identity Management Setup link.
4. On the Identity Management Setup page, select PeopleSoft source type from the Available Identity Plug-ins
list and click the Activate button.
Note. Only one identity plug-in can be active.
5. Specify the following parameters:
•
HTTP endpoint for authentication: Enter the URL to your PeopleSoft listening connector using the
following syntax:
http://<machine_name>:<port>/PSIGW/PeopleSoftServiceListeningConnector
Note. If you need to specify an end point on a node other than the default node, then specify that node
name in the URL. For example, for node name PS_HR:
http://sesserver12:7779/PSIGW/PeopleSoftServiceListeningConnector/PS_HR
•
User ID: Enter the user ID that is the Search Framework administrator on the PeopleSoft side. That is,
specify the user with Search Framework permission lists associated with it.
•
Password: Enter the password associated with your Search Framework administrator user ID.
• ToolsRelease: Enter the PeopleSoft PeopleTools version number, for example 8.55.
6. Click Finish.
See Also
PeopleTools: Security Administration
Setting Up Search Framework User IDs
Task 11-2-3: Configuring SES Authentication Timeout Settings
The default Oracle SES timeout settings may not be suitable for contacting the PeopleSoft system and retrieving
authentication and authorization data. To ensure that the two systems interact successfully, it is recommended that
you modify these settings to avoid authentication or authorization timeout scenarios. In general, the timeout
setting should be high enough to allow for the Oracle SES instance to contact the PeopleSoft web service
operation endpoint to retrieve the authentication data.
To configure Oracle SES authentication timeout settings:
544
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
Chapter 11
Configuring Integration Between PeopleSoft PeopleTools and Oracle
SES
1. Sign on to the Oracle SES administration console.
2. Select the Global Settings tab, and click the Query Configuration link under Search.
3. In the General area, set Maximum Number of Results to 999999.
4. Scroll down to the Query-time Authorization Configuration section and set the Timeout Threshold setting to
at least 120000 milliseconds.
5. In the Secure Search Configuration section under the Security Filter Configuration subsection, set these
similar to the following:
•
Security Filter Lifespan: 1440
•
Authentication Timeout: 1200000
• Authorization Timeout: 180000
6. Click Apply.
Task 11-2-4: Enabling Character Set Detection
The character set detection feature enables the crawler to automatically detect character set information for
HTML, plain text, and XML files. Character set detection allows the crawler to properly cache files during
crawls, index text, and display files for queries. This is important when crawling multibyte files (such as files in
Japanese or Chinese).
This feature is currently accessible from the Oracle SES Administration console. It is turned on by default.
Task 11-2-5: Activating the Document Service Plugin
Use the following steps to activate the PeopleSoft search-specific document service plugin, which is delivered
with the Oracle SES installation. Activating the document service plugin is required to access all types of indexes.
To activate the document service plugin:
1. Log in to the SES administration console with your administration credentials.
2. Select the Global Settings page.
3. Click Document Services under Sources.
4. Click the Edit icon on the Default pipeline.
5. Select Create New Manager, and click Next.
6. Select the instance Default PeopleSoft Doc Service Instance in the Available Services pane, and click Move to
make the service appear in the Used in pipeline pane.
7. Click Apply.
Task 11-2-6: Using a Proxy with Oracle SES
To use an HTTP proxy with the Oracle SES search framework,
•
Follow the instructions for registering a proxy in the Oracle SES administrator's guide.
See Secure Enterprise Search Administrator's Guide, Oracle Secure Enterprise Search Documentation 11g
Release 2 (11.2.2.2),
http://docs.oracle.com/cd/E35215_01/admin.11222/e35070/tuning002.htm#BENRI10055.
•
Follow the instructions in this section to set up the PeopleSoft Integration Broker.
See Using the Search Administration Activity Guide.
Copyright © 2015, Oracle and/or its affiliates. All Rights Reserved.
545
Configuring Integration Between PeopleSoft PeopleTools and Oracle
SES
•
Chapter 11
Specify the proxy in the integrationGateways.properties file.
See PeopleTools: Integration Broker Administration, "Running Integration Gateways Behind Proxy Servers."
Task 11-3: Setting Up the PeopleSoft Application Server for the
Search Framework
Your application server domain may be set up as per your site's typical specifications, however, make sure your
domain meets these Search Framework requirements:
•
At least two PSAPPSRV server processes are set to start in the domain.
• The Pub/Sub Servers (Publish/Subscribe) feature is enabled for the domain.
See PeopleTools: System and Server Administration.
Task 11-4: Setting Up Search Framework User IDs
Depending on the user, you will need to set up different permissions for Search Framework tasks. PeopleSoft
PeopleTools provides the permission lists described in the following table. To enable Search Framework tasks for
a user, your PeopleSoft Security Administrator should verify that these roles exist. If not, the Security
Administrator should add the roles as follows:
1. Select PeopleTools, Security, User Profiles, User Profiles.
2. Select a User ID.
3. On the User Profiles page, select the Roles tab.
4. Add the roles, as listed in the following table.
Permission List
Role
Description
PTPT3100
Search Administrator
Provides access to the Search
Framework development pages used for
managing searchable objects within