PSCA Install and Configuration - Upgrade to 9.2

In this POC I am upgrading HCM 9.1 PT 8.53.x to HCM 9.2 PT 8.56.x

VM setup 

1. I have done native OS installs on Windows 2016 VM of PUM Image 25 (VM name: PUM25) and Upgrade Source 03 (VM Name: UPG03) and those systems are up and running. 
2. Next I have copy of production up on SQL Server 2014 on a Windows 2016 VM. (VM Name: DB).
3. I have two other Windows 2016 VMs one for App/Prcs VM and the other for PIA. Native OS - DPK method install of middleware like tuxedo, weblogic and tools, app homes using the command line
          psft-dpk-setup.bat --env_type midtier --deploy_only --deploy_type all

         No domains have been deployed yet
4. Software is installed on E:/psft (E:\ is local drive on the VM)

PSCA/Oracle Client/PT Client Setup
I am running my PSCA on the App/Prcs VM mentioned above. 
Map drives to E$ on PUM25, UPG03 and \\PUM25\E$\psft\pt\hcm_pi_home

Installed SQL Server Management Studio and related drivers for SQL Server 2014. 

Opened CMD as admin and navigated to \\PUM25\E$\psft\pt\tools_client and ran SetupPTClient.bat -t

This will install Oracle client and Oracle based PT Client on the C:\ drive. This PT Client will be used to connect to PUM25 and/or UPG03.
Also installed PSCA - default location on C:\ drive.

Created 32-bit and 64-bit ODBC connections for my copy of prod database. PT 8.53 just needs 32-bit but when PSCA makes the connectivity test it uses 64-bit version.

Verified that I can connect to PUM24, UPG03 and Copy of Prod via application designer as well as the appropriate SQL tool.

PSCA Configuration
Launch PSCA as admin
Select Update Manager

General Option 
    - PS_HOME - point it to the local install ps_home
    - Create local directories to store download, output and staging and point them appropriately
    - point to SQLCMD.EXE file for SQL Query Tool
PUM Source - point to the Oracle db, SQL Client Tool would be path to sqlplus.exe, PS_HOME, PS_APP_HOME and PS_CUST_HOME would be the Oracle PT client installed in the prior step. 
Don't have to enable any check-boxes
PI_HOME - will be the mapped drive to hcm_pi_home mapped earlier
PIA URL to PUM signon page
Did not enable EM Hub

Upload Upg Source db to PUM
Launch the "Upload Target Database Information to Image" option and select the Upgrade Source database and upload that to the PUM Image.
Once done login to PUM PIA, navigate to PeopleTools > Lifecycle Tools > Update Manager > Update Manager Dashboard and Click on Define Upgrade Package.
Named my package HR91TO92.
Follow prompts select required for upgrade fixes too.
So it should create HR91TO92UPG and HR91TO92RFU. 
Now back in PSCA, Select HR91TO92UPG from the drop-down and it should prompt for downloading HR91TO92RFU too. So download both packages to the download directory.
As we will doing a tools upgrade too at the same time, copy PS_HOME\PTU\updPTU856.zip to the download folder manually.

Selected "Upgrade to New Application Release"
Initial Pass is selected by default
Setup target database - copy of prod
SQL Client tool - will be path to SQLCMD.EXE
Current home - will be the copied hr91 directory, I have one directory which has both tools and app so provided the same path for PS_HOME, PS_APP_HOME and PS_CUST_HOME
Enabled Configure New Homes for Upgrade
Provided paths for new homes the ones created by the DPK install on this VM.

Setup Upgrade Source database - this is similar to the PUM Source database configuration done earlier.

Select Upgrade page - should show Upgrade Source and target information correctly. Application and Tools upgrade sections will be selected and grayed out. Each one should have a package listed under the appropriate section. 
Select the Required for Upgrade Package section.
then continue to compatibility check screen. Verify that all are return green. If anything is not then step through previous screens to verify the inputs and selections. A total of 11 checks are performed.

Click on Finish and the upgrade job will be created and PSCA will start running the steps. The first step is a manual stop.

It creates 3 jobs, RFU, UPG and PT Upgrade.

Using PUM to apply PRP (PeopleSoft Release Patchset)

PeopleSoft (Oracle) with the advent of 9.2 release introduced the PUM tool to apply and migrate patches/bundles/fixes. Going forward an individual patch or fix is now called as PRP (PeopleSoft Release Patchset).

So in a nutshell the process is to download the PRP, apply it to the current Image (which means you might have to first download and get the latest version of the PUM Image up and running) and then apply it to your Demo (this might be optional) continued with applying the PRP to your DEV, TST/QA and finally Production.
I have covered some basic steps on how PUM works in the post here.

Pre-reqs
I had to install the latest PeopleTools client which came with the Image 10. Also had to install Oracle 64 bit client. Mapped the pi_home share to a drive on my workstation. Make sure pi_home is writtable. For making it writtable do the following

Edit the /etc/samba/smb.conf file

Before >> guest account = nobody

After >> guest account = root

Under the [pi_home] section

Before >> writable = no

After >> writable = yes

Restart samba service as below

service smb restart

Map a drive and when prompted for credentials provide

workgroup\root as the username and root’s password as the password


1. Navigate through wizard (Tools > Change Action)
2. Selection Action would be Update Manager
3. On the General tab, select PS_HOME. For this example I am working on FSCM Image 10, running on tools 8.54.05. So I installed the client from the PUM image share to my local drive under C:\PT85405. Designated a download, staging and output directory. Assigned path to Oracle client. Had to install the 64 bit version which was delivered part of the image share.
4.  PUM Source tab - stepped through the wizard and made sure connection successful. Mapped the share to a drive on my workstation. \\image_ip_address\pi_home
5. EM Hub tab - pointed it to my demo db. My Demo db is running FS 9.2, PT 8.53.14 on SQL Server 2012
6. On Select Tab - selected "Apply downloaded PeopleSoft Release Patchset to PeopleSoft Image".

So now the current wizard is complete and the next one pops-up.

1. Select download directory where you downloaded the zip file from Oracle's website
2. PSCA will only show applicable patches if your download directory contains other zip files. Select and move on.
3. Compatibility check should run to success.
4. Apply summary - eye ball and make sure everything looks right.

PSCA will create a job and start applying the project to the Image db. Verify logs once done.

Login to the Image 10 PIA and navigate to PeopleTools > Lifecycle Tools > Update Manager > Define Change Package. I have already uploaded my demo db to this Image 10 db. (definitely another post on that to follow). Provide a package name, select "Specific Updates" radio button, provide bug number and finish creating the package.

So prior to 9.2 this was a simple step, search for patch on Oracle website, download and apply to demo, but now its very very elaborate. Come to terms, no other way out !!

Using PeopleSoft Update Manager (PUM)

This is a test to understand how PUM works and what are the different pieces involved.

Workstation/Laptop config
Windows 7 Enterprise, 64bit OS, 12GB RAM, 237GB HDD

VM Details

FSC92DMO - Patch 16877487: PEOPLESOFT FSCM IMAGE 9.2.001
EP92P005 - Patch 17965081: PEOPLESOFT FSCM IMAGE 9.2.005

Disk Space Details

zip files – 24.5GB
zip files expanded – 25GB
.ova file – 25GB
So total disk space used before even creating appliance = 75GB

Once .ova file is created the expanded files can be deleted.

The .ova file can be deleted once the VM is up and running

Both VMs once up and running take around 90 GB

Environments

EP92P005 (PI) - FSCM 9.2 Image #5, PT 8.53.09
FSC92DMO (target) - FSCM 9.2, Demo, PT 8.53.04

If target and PI are at different minor tools release, then run client install from the higher tools release (8.53.09) and then install PSCA running at tools rel 8.53.09. Basically take whatever comes with the PI environment, as that would generally be latest and greatest.

Update the environment long and short name in the following page before starting any agents.
PeopleTools > Utilities > Administration > PeopleTools Options

I am starting FSC92DMO VM first and then the EP92P005. As Dynamic IP addressing option has been chosen, the first one has 192.168.56.102 and the next one 103.

Verify App Designer, SQL Developer and web connectivity to both envs.

http://192.168.56.102:8000/ps/signon.html

http://192.168.56.103:8000/ps/signon.html

EMHUB/Agents

Logged into FSC92DMO VM, su in as psadm1, updated PSEMAgent config URL to http://192.168.56.102:8000/PSEMHUB/hub and Unix drives to crawl to /opt/oracle|/home/psadm2

Rename the delivered search-results.xml file to search-results-old.xml and then start the agent in the background as follows.

./StartAgent.sh &

 

Did a local client install under c:\apps\PT853. Updated the PSEMAgent config file here also to point to http://192.168.56.102:8000/PSEMHUB/hub and windows drives to crawl set to C:/apps/PT853|C:/apps/oracle

Started the agent as an administrator.

 

Start PSCA

 
 

 

 

 

 

C:\apps\PT853\ is where the workstation install of PT 8.53 and 09 patch was done
Y:\ is mapped to the pi_home share of the PI environment.

EMF Agent is running on target which is FSC92DMO. I have one agent running on the Linux VM. So it found App/Prcs and Web. For File Server Linux is not a certified option, which is why I have a local install of PeopleTools which acts as the file server.

 

Additional Options - no changes took defaults

 

 

 

Target is FSC92DMO db and source will be the PI image db EP92P005.

 

 

Click Next and then Finish on the confirmation screen.

 

Now file server section is automatically filled out.

 

Key in the db name and once you tab out the following screen appears

 

Click Next to view the confirmation screen and then Click on Finish which will take you back to the following screen

Key in the URL to the PI environment.

 

 

Examine Patch Target and Source db info as displayed above.

Now click on the “Open Browser and Connect to the PI Database” button.
Signon page pointing to the PI Image URL opens up. Rest of the steps are now done within PIA and we will come back to this page to apply the change package which will be created in your PIA session.

Step 1 is automatically grayed out, as we only have one target db in this case.

Provide a Package name and click next

So there are 30 patches that need to be applied

Now back in PSCA.

Now begin applying this patch as normal.