I had hoped to be able to get the PeopleTools Testing Framework posts complete before I proceeded to installing the latest update patch for PeopleTools. After constantly reading that you need to update to the latest for PTF, I decided I was being silly, and I broke down and went through the update.
Here’s what I did:
First, I downloaded the update from Oracle Support:
At this point, I probably could have done the Change Assistant package. I chose to do the full install version because it would complement the instructions that I already have.
Stop the Services
When I rebooted, everything should be stopped. To avoid rebooting, make sure that you have stopped all:
- App Servers
- Process Schedulers
- Web Servers
- PSEM Agents
Just a thought: I would clear the cache on your servers – app, batch, and web – to make sure that everything stopped as it should. You might visually scan task manager also.
Now, keep in mind that I don’t take any responsibility for mistakes that you make or problems with anything. Hey, this is free information. So, your on your honor — back up just in case. I have a VM Instance, and I just backed up the whole machine.
When it asks for the license code, enter it in the blanks. If you are like me and didn’t write down the code, look up the PeopleTools license code for your platform here.
Stamping New Version in Database
Next, you need to stamp the database with the new PeopleTools version to show the file system and database are in sync. You simply run the ptpatch.dms data mover script in the scripts directory of your PeopleSoft Home. (I just logged in as PS, not boot strap mode).
Database Changes/App Designer Project
The next major step is to install the App Designer project. This is copying the meta data into the database.
Once it is loaded, Build the project. You should be able to use the Build > Project option.
For some reason, that option wouldn’t work for me. So, I just built each record manually. Here are the records I had to build:
Note: if you select Build project, you should see the full list of records in the Scope.
Messages from the message catalog do not copy via a project when copying from a file. So, we have to use this data mover script.
PIA: I had just deleted the whole PIA Home thinking that I was going to reinstall. I wish I had just deleted the cache and used the re-deploy option. Oh, well.
Then, clear App Server cache. Since I did that at the beginning, I don’t have to worry about that.
Now, I have a 8.51.11 instance!