Building out a new HCM 9.2 Update Image 9 DEMO

As mentioned here an updated version of  the PeopleSoft HCM media was released in late 2014.  I’ve done a few Demo installs of this on both Linux and Windows now, and here are my notes from a Linux install.  As in the past, these are rough notes I take when I do any install and not a how-to guide.  This install requires PeopleTools 8.54.03 patch as that is the level of PeopleTools within the database.  The media available on Oracle Software Delivery Cloud is only 8.54.00.  This install includes all PeopleSoft HCM patches through Update Image 9, a great thing for those using it to upgrade.

 

  • Download media
  • Download PeopleTools 8.54.03 patch
  • Download and install current JAVA 7 JDK (April 2015 is indicated as end of Public Updates)
  • Normal Weblogic install
    • export JAVA_HOME=/opt/apps/jdk1.7.0_71
    • export PATH=$JAVA_HOME/bin:$PATH
    • /opt/apps/wls1212
    • normal install options
  • tools install web
    • 8.54 delivered with java version “1.7.0_51”
    • /opt/apps/psoft/pt854
    • apply 8.54.03 patch
    • Install HCM 92PI9 media
  • PIA creation
    • on this server $PS_CFG_HOME=$PS_HOME
    • Documentation refers to PIA_HOME as a new variable, which defaults to PS_CFG_HOME unless set.  PIA_HOME was not detected by the installer when set.
    • web server root = /opt/apps/wls1212 and detected properly.
    • IB Gateway and PTWEBSERVER Passwords: ***********
    • Domain Connection Password = ****
    • Problems with GUI displays.
    • PS reports = /opt/apps/psoft/psreports
    • Web server root directory : /opt/apps/wls1212
    • 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 : .clientname.com
    • Application server name : appsrv1.clientname.com
    • JSL port : 9090
    • HTTP port : 8090
    • HTTPS port : 4439
    • Report repository directory : /opt/apps/psoft/psreports
    • PIA webserver directory : /opt/apps/psoft/pt854/webserv
  • Normal Tuxedo install
    • Full Install
    • Oracle home = /opt/apps
    • installed to /opt/apps/tuxedo12.1.1.0
    • password: ********
    • SSL support: no
  • App and Batch Tools install
    • /opt/apps/psoft/pt854
    • apply 8.54.03 patch
    • Install HCM 92PI9
  • Database Setup
    • Full Tux install
      • sudo mkdir /u01/tux12
      • ./tuxedo12110_64_linux_5_x86.bin -i console
      • installed to /u01/tux12/tuxedo12.1.1.0
      • password: *********
      • SSL support no
    • Tools install
      • /u01/psoft/pt854
      • apply 8.54.03 patch
      • source psconfig.sh
      • source tux.env
    • App install
      • /u01/psoft/hcm92pi9
      • export $PS_APP_HOME=/u01/psoft/hcm92pi9
    • Database prereq steps
      • Create $ORACLE_HOME/dbs/initHCM92PI9.ora
      • Create directory structure
        $ mkdir /u01/app/oracle/oradata/HCM92PI9
        $ mkdir /u01/app/oracle/admin/HCM92PI9
        $ mkdir /u01/app/oracle/admin/HCM92PI9/pfile
        $ mkdir /u01/app/oracle/admin/HCM92PI9/adump
        $ mkdir /u01/app/oracle/fast_recovery_area/HCM92PI9
      • orapwd file=$ORACLE_HOME/dbs/orapwHCM92 entries=5
        password = **********
      • edit SCRIPTS
        $ 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
      • edit tnsname.ora to add HCM92PI9 entry
      • export $ORACLE_SID=HCM92PI9
    • Run database wizard
      • cd $PS_HOME/setup/PsMpDbInstall;
      • Answer prompts
        Installation location: (DEFAULT: /u01/psoft/pt854):
        PS_APP_HOME: /u01/psoft/hcm92pi9
        ->1- Non-Container DB
        ->1- Non-Unicode Database
        ->1- Western European ISO 8859-1
        ->1- Demo
        ->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/hcm92pi9/modifiedscripts
        ->1- Create new SID
        Oracle SID: HCM92PI9
        DatabaseName; HCM92PI9
        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/initHCM92PI9.ora]:
        Appserver User []: PSAPPS
        Password []: ********
        PTWEBSERVER  Password []: ********
        enable or disable all other user profiles: ->2- Enable
        ->2- I would like to set a different password
        Password []: ********
        ->1- ENG – US English

Update: I forgot some notes about running the database wizard.  This also applies to app/prcs servers.

Error running ENCRYPT_PASSWORD *;
Error: Process aborted. Possibly due to JVM is not available or missing java class or empty password.
Didn’t troubleshoot, Ran OK from Windows;

The encrypt_password failed because of out of the box environment variables allowing Java 1.6.0_32 to be found.  Tuxedo 12.1.1.0 is delivered with Java JRE 6 and the tux.env sets JAVA_HOME=$TUXDIR/jre.  $JAVA_HOME is then prepended to $PATH thereby causing the wrong JRE to be used if you source tux.env after psconfig.sh.

This produces the following error:

 

 

 

2 thoughts on “Building out a new HCM 9.2 Update Image 9 DEMO
  1. This solved the encrypt_password error from the database wizard:
    UPDATE PSOPRDEFN SET ENCRYPTED = 1
    WHERE OPRID IN (‘PS’,’PTWEBSERVER’)
    Then, re-ran the encrypt_password script and it worked.

    Reference –> E-SEC: ENCRYPT_PASSWORD Error: Process aborted. Possibly due to JVM is not available or missing java class or empty password. (Doc ID 2001214.1)

    The database wizard exited after the error, so the remaining scripts needed to be run manually from Data Mover(Createtrgr.dms, createvw.dms, createtemptbl.dms)

Leave a Reply

Your email address will not be published. Required fields are marked *