When in a production environment there are times when it is not beneficial to have the previous login userid showing on the login page.  This is especially true when in kiosk mode where you really don’t want people to know other accounts within the system.

In order to change this setting you need to go into the web profile configuration for the PIA site in question.  The web profile being used will be in the configuration.properties file of the PIA site you are working on.  Typically the web profile will be DEV or TEST or KIOSK or PROD.

Navigate to:  Home > PeopleTools > Web Profile > Web Profile Configuration, select you web profile you want to change:

Under the Security Tab: change parameter – “days to auto fill userid” to 0 (zero).

Save the change and reboot your application server and web server, probably not a bad idea to clear cache here as well.

When you sign onto a PIA servlet, a new connection is established within the application server.  This error can occur occurs when that new connection cannot be established between the Web Server and the Application Server. Some reasons this occurs:

1. In the configuration.properties file for the PIA site the server/jolt port identified is invalid or the web server is unable to communicate to the application server identified in the file.  Web Servers are sometimes configured on a separate subnet in what is referred to as a DMZ to protect outside attacks from the backend systems, the firewall rules will sometimes need to be adjusted to allow this specific communication from web to app server to occur.

The configuration.properties file is located: %PS_HOME%\webserv\{DOMAIN}\applications\peoplesoft\PORTAL\WEBINF\psftdocs\{PIA-Site}\

2. In order to make PIA more dynamic and manageable PeopleSoft introduced web-profiles a few years back.  Web Profiles allow for PIA to managed online within the PeopleTools.  However, in order for the Web Server to access the database to get the web profile settings there needs to be a security user that has access to this information.  PeopleSoft by default has the user PTWEBSERVER with a default password of PTWEBSERVER, there is a delivered role:  “PeopleTools Web Server”, which is linked to the delivered permission list: “PTPT1500”.  You can still log into the site with other user profiles but the defaults from the web profile are not in effect because this user is invalid.  In the configuration.properties file there is a line item for the web profile user and password, and typically they are both encrypted.  Encrypted values start with {V1.1}.  You can enter these values un-encrypted, noting that they are both case sensitive.

In order to encrypt the userid and password, you need to run the PSCipher utility.

3. Make sure the PTWEBSERVER user account is not locked.  Check PSOPRDEFN.ACCTLOCK field it should be = 0. (zero).

4.  Another reason this can also happen is that the web profile listed in the configuration.properties file is not actually listed in the web profile configuration tables.  This happens sometimes during environment refreshing where profiles are renamed/deleted and the reference is no longer there.  Change the configuration.properties file to a valid web profile.

Sometimes you just need to do things in an RDC session that would appear simply, but its Windows!

If you want to hit Control + Alt + Delete to get options to lock/logoff/password change/task manager in an RDC session (remote desktop session), you need to use the key combination:

Control + Alt + End

Don’t ask me where that one came from, but it works! 🙂

Oracle decided to integrate PeopleSoft patching into their main database for patch fix, and in the process the commonly used Update ID, has been change to be associated with what I call the Bug Incident, but they are referring to as the Patchset in ARU.

The ARU is Oracle’s Automated Release Update system and has gone by various other names.  Since I maintain a few patch lists I have some serious updating to do, but at least they made some nice documents to show the old and new numbers.  The new system appears to be clunky and difficult to to use like all new patch systems in the past.  Hopefully it will get easier to use and understand with some more use.  Good luck!

Here is the list for the Campus Solutions 8.9 & 9.0 Campus Bundles:

Campus Solutions 9.0 Bundles

Campus Solutions 8.9 Bundles

I found this video that shows you have to create a database when ASM is installed.

YouTube Video

I found that when I manually created the Oracle Database, that because the ASM dynamically names everything, I simply removed the directory & file name reference and replaced it with the +ASM group where I wanted the datafile to be located.  If you look at the ptddl script for a PeopleTools database or the hcddl script for an HR database you will see how it will say the directory+file name:

‘/oracle/oradata/dbfiles/tablespace1.dbf’ is replaced with:

‘+ASMHRORPTGROUP1’ depending on what you named it.