Working on a new PSNT server, I ran into the following error:

This looks serious, but if you look closely, you might actually see the problem. When the Process Scheduler Domain is built it defaults the SQRBIN parameter. In my case, my %PS_HOME% was e:\psft\pt852 not e:\psoft\pt852. After changing the SQRBIN parameter to: %PS_HOME%\bin\sqr\ORA\bin….. Everything was good! Don’t forget to stop/restart the process scheduler for this change to take effect.

Last week I was giving a demonstration on Enterprise Portal or as some like to call it the “Interaction Hub”, and as I was asking some questions about their existing architecture I found they had an odd issue.  In their demo environments the new Integration Broker Workcenter comes up without a problem, but in their existing production environments the workcenter page comes up but the left navigation collection pagelet renders with the following message:

This struck me as an odd error message, and after some google searches and a good look through MOS, I could not find anything that generated a solution to the problem.  I did find some notes where invalid XSL caused issues, and I found another issue where the temp directory was invalid on windows 2008 (make sure temp directory exists).

I had the client check to make sure that the production installation table was correct and that the license code was correct, and in both cases they were fine.  So this left me with no answer without digging in.  However, I was working on an upgrade for another client on the weekend and as I was doing the last touch ups on the system I found a DMS script that had the following statement in it:

This statement enables Navigation Collections and the Pagelet Wizard pagelets within an environment. Once this statement was ran, we had success.

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.