HCM 9.2 and 8.53 Demo Install Notes

These are my notes from a recent HCM 9.2 / 8.53.02 setup I did.   I tried out the database wizard again this time.  Had a few hiccups but it seemed to work.  I still think it’s easier and quicker to create the database manually, especially when the java process ran at 100% on one cpu for about 20 to 30 minutes as the notes indicate below.  All said, it was an easy build and I didn’t see any significant issues/problems.

Update:  See the notes for HCM 9.2 / 8.54.03 / Patch Image 9

Install web componenents on web server

Things needed:
  1. wls1036_generic.jar
  2. jdk-7u17-linux-x64.tar.gz  or jdk-7u9-linux-x64.rpm (actually anything jdk7u2 +)
  3. License key for PeopleTools Oracle Install:
  4. PeopleTools 8.53.02 patch
  • Weblogic Media location: /opt/media/media/8.53/ptools.weblogic
  • Weblogic/JDK Install location: /opt/apps/
  • PeopleTools Media location: /opt/media/media/8.53/ptools
  • PeopleTools Install location: /opt/apps/psoft/pt853
  • HCM Application Install location: /opt/apps/psoft/hcm92

The Install

$ cd /opt/apps
$ tar zxvf /opt/media/media/8.53/ptools.weblogic/jdk-7u17-linux-x64.tar.gz
$ export JAVA_HOME=/opt/apps/jdk1.7.0_17
$ $JAVA_HOME/bin/java -jar /opt/media/media/8.53/ptools.weblogic/wls1036_generic.jar -log=./logs/wls1036HcmInstall.log

Weblogic Install prompts
Middleware Home= /opt/apps/wls1036.hcm92
Typical Install
JDK detected fine
Default product install directories

$ cd /opt/apps/psoft
$ /opt/media/media/8.53/ptools/Disk1/setup.sh

PeopleTools Install Prompts
PS_HOME=/opt/apps/psoft/pt853

$ /opt/media/media/hcm92/Disk1/setup.sh

HCM Application Install Prompts
PS_APP_HOME=/opt/apps/psoft/hcm92

$ /opt/media/media/8.53/patch.02/cd85302/Disk1/setup.sh

Patch Install Prompts
PS_HOME=/opt/apps/psoft/pt853


Install app components on app/prcs server:

Things needed:
  1. tuxedo111130_64_Linux_01_x86.bin
  2. COBOL Compiler ?
  3. License key for Oracle Install:
  4. HCM license key for Oracle:
  5. PeopleTools 8.53.02 patch
  • Weblogic Media location: /opt/media/media/8.53/ptools.tuxedo
  • Tuxedo Install location: /opt/apps/
  • PeopleTools Media location: /opt/media/media/8.53/ptools
  • PeopleTools Install location: /opt/apps/psoft/pt853
  • HCM Application Install location: /opt/apps/psoft/hcm92

The Install

$ cd /opt/apps

$ /opt/media/media/8.53/ptools.tuxedo/tuxedo111130_64_Linux_01_x86.bin -i console

Tuxedo Install Prompts
FULL INSTALL
Use existing ORACLE_HOME=/opt/apps
Use default TUXDIR=/opt/apps/tuxedo11gR1
Install Samples = Y
tlisten password = ********
Install SSL Support = N
$ cd tuxedo11gR1
$ . tux.env
$ tmadmin -v
INFO: Oracle Tuxedo, Version 11.1.1.3.0, 64-bit, Patch Level (none)

$ cd /opt/apps/psoft
$ /opt/media/media/8.53/ptools/Disk1/setup.sh

PeopleTools Install Prompts
PS_HOME=/opt/apps/psoft/pt853
$ /opt/media/media/hcm92/Disk1/setup.sh
HCM Application Install Prompts
PS_APP_HOME=/opt/apps/psoft/hcm92
$ /opt/media/media/8.53/patch.02/cd85302/Disk1/setup.sh
Patch Install Prompts
PS_HOME=/opt/apps/psoft/pt853

On Change Assistant VM

Install all tools options to D:\PT.853
Install application to D:\HCM92

Install 8.53.02 patch to D:\PT.853


Try out DB wizard for 8.53

Install 8.53 and 8.53.02 patch to /u01/psoft/pt853
Install HCM 9.2 to /u01/psoft/hcm92
Install Tuxdo Full Install to /u01/tux

# mkdir /u01/tux
# chown oracle:oracle /u01/tux/
$ export PS_HOME=/u01/psoft/pt853; export PS_APP_HOME=/u01/psoft/hcm92
$ . $PS_HOME/psconfig.sh
$ . /u01/tux/tuxedo11gR1/tux.env

Database prereqs
$ mkdir /u01/app/oracle/oradata/HCM92
$ mkdir /u01/app/oracle/admin/HCM92
$ mkdir /u01/app/oracle/admin/HCM92/pfile
$ mkdir /u01/app/oracle/admin/HCM92/adump
$ mkdir /u01/app/oracle/fast_recovery_area/HCM92
$ orapwd file=$ORACLE_HOME/dbs/orapwHCM92 entries=5
$ vi $PS_HOME/scripts/unix/createdb10.sql
:1,$s/oradata/app\/oracle\/oradata/g
$ vi $PS_HOME/scripts/unix/utlspace.sql
:1,$s/u03/u01\/app\/oracle/g
$ vi $PS_APP_HOME/scripts/unix/hcddl.sql
:1,$s/u04/u01\/app\/oracle/g
$ vi $ORACLE_HOME/network/admin/tnsnames.ora
add HCM92 entry
$ export ORACLE_SID=HCM92
$ cd $PS_HOME/setup/PsMpDbInstall
$ ./setup.sh

Prompts
Installation Location: (DEFAULT: /u01/psoft/pt853):
PS_APP_HOME: /u01/psoft/hcm92
database platform: ->1- Non-Unicode Database
Character Set: ->1- Western European ISO 8859-1
Database type: ->1- Demo
PeopleSoft Application: ->1- PeopleSoft HCM Database – US English
sqlplus path: [/u01/app/oracle/product/11.2.0/dbhome_1/bin]:
ORACLE_HOME: [/u01/app/oracle/product/11.2.0/dbhome_1]:
Location of modified scripts: /u01/psoft/hcm92/modifiedscripts
Create or use existing SID: ->1- Create new SID
Oracle SID: HCM92
DatabaseName; HCM92
Mount Point 1: u01
Mount Point 2: u01
Mount Point 3: u01
Enable AutoExtend: ->1- Yes
Peoplesoft owner ID: SYSADM
Peoplesoft owner password: ********
Peoplesoft connect ID: people
Peoplesoft connect password: ********
Peoplesoft default tablespace: [PSDEFAULT]:
Location of init.ora file complete path: [/u01/app/oracle/product/11.2.0/dbhome_1/dbs/initHCM92.ora]:
Appserver User []: PSAPPS
Password []: ********
Webserver User : PTWEBSERVER  * Webserver User name was not a prompt.
Password []: ********
enable or disable all other user profiles: ->2- Enable
Password for other OPRIDs: ->2- I would like to set a different password
Password []: ********
Base Language: ->1- ENG – US English

Failure 1:  ORACLE_SID not set, so hung on runCreatedb10.sh
Failure 2:  had undo_tablespace=UNDOTBS1 in initHCM92.ora which did not match psundo name
Failure 3:  tried to do install with only tux client installed, needed full install
Failure 4:  didn’t shutdown running instance from Failure 3

Java process ran at 100% for a while after utlspace, probably parsing output.

SQL> select toolsrel from sysadm.psstatus;

TOOLSREL
——————–
8.53
SQL> select count(*) from sysadm.ps_maintenance_log;
  COUNT(*)
———-
0

Update HCM92 database to 8.53.02

Overall steps, some already complete  As always, read the README file as these steps could change
  1.  Backup pristine database
    1.  Shutdown immediate
    2.  startup mount
    3.  rman target /
    4.  configure controlfile autobackup on;
    5.  configure device type disk parallelism 2 backup type to compressed backupset;
    6.  backup database;
    7.  SQL> alter database open;
  2.  Download and extract patch
  3.  Shutdown all processes for ENV to patch
  4.  Backup existing Tools directories
  5.  Install patch files
  6.  Update database patch version (PS_MAINTENANCE_LOG entry)
    1.  run %PS_HOME%\scripts\ptpatch.dms
  7.  Apply patch project
    1.  Launch patched App Designer
    2.  Tools -> Copy Project -> From File
    3.  %PS_HOME%\projects select PATCH853
    4.  select Common and English language only
    5.  Copy the project
    6.  Build project
      1.  Build Options: create tables/view, alter tables, create script only
      2.  Create Settings: Skip table, recreate view, recreate index only if modified
      3.  Alter Settings: Drop Column, truncate data, add/change/rename/delete, alter by rename
      4.  Script settings: write alter comments, split scripts and change path if desired
    7.  Edit generated SQL script if needed
    8.  Run Script
  8.  Load Messages and Data Project (Skipped, no new script delivered)
    1.  run %PS_HOME%\scripts\msgtlsupg.dms via Data Mover in bootstrapmode
  9.  Multilingual steps (Skipped, not running ML)
    1.  Load Translations: Copy PATCH853ML to Database via App Designer
    2.  Load Messages: Run %PS_HOME%\scripts\msgtl<lang_cd>.dms via Data Mover
  10.  Reinstall needed apps and reconfigure
    1.  Change Assistant
    2.  PIA -> Redeploy
    3.  PeopleSoft Test Framework
    4.  Client tools
    5.  Clear rowset cache; run %PS_HOME%\scripts\clear_rowset_cache.dms
    6.  Purge App/Web cache
    7.  Re-create app domains (you may miss new options if ony only reconfigure)
    8.  restart processes
  11. Take database backup

The PeopleSoft ReleaseAdaptor

The PeopleSoft ReleaseAdaptor is used to manipulate delivered projects to meet the requirements needed to apply them to your current environment.  Usually this is run as a step in Change Assistant.  The ReleaseAdaptor consists of files including:

%PS_HOME%\bin\client\winx86\releaseadaptor.bat
%PS_HOME%\bin\client\winx86\project_filters.xml
%PS_HOME%\bin\client\winx86\adaptdms.bat
%PS_HOME%\bin\client\winx86\transform_programs.xml
%PS_HOME%\bin\client\winx86\ProjectFilter.bat
%PS_HOME%\bin\client\winx86\ProjectInspector.bat
%PS_HOME%\class\projectadaptor.jar

The project_filters.xml file contains information about all object types in PeopleSoft and assigns them an ID number and other metadata such as a Description and Valid PeopleTools Releases (beginning and end). If you look at the file, you’ll see Records are 0, Indexes have an ID of 1, PermissionLists are 53, and so on.

The PeopleTools 8.51 project_filters.xml file has 101 object types (remember we started with 0) and PeopleTools 8.52 has 120 object types. As Oracle releases new object types for newer PeopleTools releases this allows them to transform a project to meet your needs. If your running PeopleTools 8.51 and applying an update that adds new features in 8.52 via new object types, Oracle can remove those new object types from the project during this step in Change Assistant.

Problems can arise if you are not applying bundles and maintenance packs via Change Assistant. As you won’t be able to apply the new object types to your older PeopleTools level. The Change Assistant template should indicate if the ReleaseAdaptor is a required step, but Oracle has been known to make a mistake in the past.

If you have an update failing at the ReleaseAdaptor step or perhaps the project load step first make sure you have everything for the ReleaseAdaptor up to date and that it’s running properly. If you’re running PeopleTools 8.51 and applying a bundle that was released after PeopleTools 8.52 you need to apply the most recent ReleaseAdaptor patch. For instance I know Bundle 8 for both HCM 9.1 and ELM 9.1 have PeopleTools 8.52 objects in them. Usually with Change Assistant you should notice the prereq. Make sure when you apply the update however that the files on your Change Assistant machine are updated properly.

Errors indicating a problem running or the lack of running the ReleaseAdaptor include:

Project PRJXXXXX contains an invalid definition type (XXX) and can not be opened.