Showing posts with label PSEMHUB. Show all posts
Showing posts with label PSEMHUB. Show all posts

Monday, January 19, 2015

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











Thursday, March 20, 2014

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