Since the migration from the old PeopleSoft support site into MOS (My Oracle Support), I have been finding it very hard to find the upgrade home pages. I am not sure why they don’t have a link right in the patches area, but they don’t, or I haven’t found it yet.

However, the other day I was wondering around on the PeopleBooks site and I found something very interesting:

www.oracle.com/pls/psft/homepage

Down at the bottom there was this:

PeopleSoft Install and Upgrade Resource Site
Use this link to access the site for documentation and related files to help in your install and upgrade project.

All the upgrade home pages are listed here and are easily accessible.

There are many reasons node pinging can fail but one of the most common issues I have found for this is caused by the keystore on the weblogic web instance.

Most organizations will load in there SSL certificates and change the default passwords of the keystore. When this happens you have to modify the integrationGateways.properties file to tell it the keystore file name and path and the password for the keystore.

You can modify the file online in PeopleSoft from the gateway setup page or on the backend system by navigating to the PSIGW applications folder on the weblogic instance.

Look for the lines and update them accordingly:

Save the file and try the ping again. They should now successfully ping.

I like to setup the integration broker gateway to use HTTPS, however, usually when you enter in the https gateway:

It will return an error that there is a failure loading the gateway connectors. This is because the SSL Certificate used to secure the website does not have a trusted root certificate within the digital certificates page in PeopleSoft.

Open the certificate and view the root level of the certificate. In windows you can open the certificate and it will allow you export the certificate. Once you get the root certificate (top-level) open click on the export button and select the base 64 x.509 format. Open that certificate file up in a text editor and it should have a BEGIN and END section and a bunch of characters in the middle. Select all the information in the file and log into PeopleSoft and navigate to:

Click on the + button and on the new blank line add a certificate type “ROOT CA” and enter in alias for the certificate you are going to enter. Then click the button to add the certificate and that will open a page where you can paste in your certificate that should be on your clipboard. Click Save and you should now see your root certificate in the listing.

Reboot your application server and clear the cache, and then go back to the gateway and load in your connectors. They should now load without an issue.

When creating custom single signon PeopleCode it can often appear that the code is not firing.

Single signon PeopleCode is very fickle code, and some regular PeopleCode functions will cause major issues. For example putting in popup messages to debug the code will actually cause the code to fail. Make sure functions like WinMessages, MsgGet, MessageBox, and other interactive information function are not in your code.

Make sure all your function references are actually within the same Record/Field/PeopleCode Event, Single Signon Peoplecode will fail if you put in a function call that is stored within another Record/Field/PC-Event. You also should make sure that the Signon PeopleCode is stored in the FieldChange or FieldDefault event, I always put my code in the FieldDefault.

Make sure the you have a valid userid/password within the execute peoplecode as area of the signon peoplecode activation page or make sure that the user logging into the system has the appropriate privileges to execute the signon peoplecode.

Lastly, Shutdown the application server, clear cache, and restart before attempting another test.

I have a site setup that requires SSL in order to show all the functionality of my demo PeopleSoft environments.  However, I have several other requirements for SSL, so I have a WildCard SSL certificate.

According to PeopleSoft wildcard certificates are unsupported however, I have had no problem using them with Weblogic 10.3.0.1 or higher.  I have not tried it with earlier versions, but I really don’t see why they wouldn’t work.

On my first environment I create a CSR (Certificate Signing Request) using the pskeymanager tool.  Next I submit that CSR into my provider (in my case GoDaddy), and I generate a signed certificate which I import using the pskeymanager tool.

Next I go into the console and turn the SSL on and set it to use the custom identity custom trust settings and enter the alias and my vault passwords.  After committing the changes the certificate should be working correctly.

On my next system I install my PIA as per normal, but before I start things up, I copy the pskey file from server 1 to server 2.  This file is located in the <webserver_home>/<domain>/piaconfig/keystore folder.  Now I start the server up and go into the console and setup the SSL exactly the same as I did on server 1.

I have not found a clean way to export the signed certificate out of one vault and import it into a second vault.  But this procedure works like a charm.