Application Server Could Not Create Shared Cache One of the causes of the error Could not create shared cache. (0,0) on the signon screen is if the application server is running low or has run out of disk space. Large log files from traces are a common cause of this error, particularly if you are using application server tracing, so once you clear up some space, check that you don't have any unnecessary tracing turned on. Freeing up some disk space seems to resolve the error without the need for any server restarts.WebLogic PIA Java Home While setting up the PIA for Oracle WebLogic, I was getting the following message (this is on Windows servers but has similar implications on Linux): The JRE was not found in directory C:\Oracle\JRockit. (JAVA_HOME) Please edit your environment and set the JAVA_HOME variable to point to the root directory of your Java installation. Press any key to continue . . . Weird, since JAVA_HOME was set up correctly in environment variables and did not equal the value in the message shown (should be C:\Oracle\JRockit\JRE). Turns out, Weblogic reads this from the script commEnv.cmd (or commEnv.sh for Linux). Open this script and look for JAVA_HOME and adjust accordingly. Note in my case, this script is located under the WebLogic installation directory and then common\bin.Monitor Sessions through WebLogic Console The weblogic console allows you to monitor the number of sessions on your PeopleSoft application. First, login to the console using the following URL format: http://{webserver}:{port}/console You will need to login with the appropriate credentials which were set when installing WebLogic. From here, click on the OK link in your system status (bottom-left): Expand the server/subsystem name (e.g. PIA) and click on the PeopleSoft application: Next, find and click on the root of the PeopleSoft site: In the settings click on Monitoring and you will see information about sessions related to your PeopleSoft site as shown: Tuxedo Message Catalogs Error I was playing around with getting the PeopleTools client (application designer, configuration manager, data mover etc) when I tried logging in through the application server and received the follow error: (I've dummied values to protect the innocent :) Could not connect to application server YOUR_PS_DB (//appserver.example.com:7000). Make sure the Tuxedo message catalogs (CMDTUX_CAT, etc.) are in C:\ORACLE\PEOPLESOFT\Tuxedo. Contact your system administrator or check the Tuxedo log for more information. I love how they still tell you to contact your system administrator... Anyway, this message tells you exactly what is wrong - you don't have the tuxedo folder where it is trying to find it - in this example C:\ORACLE\PEOPLESOFT. So copy the tuxedo folder including the subfolders locale and udataobj. NOTE: if you are missing the locale folder you will get the same message. If you are missing the udataobj folder you will get the following message: Could not connect to application server YOUR_PS_DB. Make sure the PeopleTools authentication server (PSAUTH) is booted Application Tracing Firstly PeopleSoft gives you the option to set trace flags from the sign on screen: It is particularly useful for tracing sign on (e.g. SSO), however it is too cumbersome to trace a particular component or page. If you need to do that, I recommend logging in normally and then using the tracing options available from: PeopleTools > Utilities > Debug Once you click the signon trace link, you're given a myriad of tracing options: Its up to you to decide what you need, but remember, with tracing, less is often more, don't get carried away. After all, you're looking for a needle in a haystack, no need to make that haystack bigger than it needs to be! NOTE: the signon tracing link can be disabled through web profile settings. However, there's a way around this. If you notice your URL when you click the hyperlink it changes and includes a trace directive: Regular signon URL is something like this: https://server:port/psp/ps/?cmd=login With tracing, the signon URL includes the trace directive: https://server:port/psp/ps/?cmd=login&trace=y So, regardless of whether you can see the hyperlink, you can still turn on signon tracing using the trace directive.The Connect ID The connect ID is used from PeopleTools 8+ and was implemented to replace the need for PeopleSoft to create users in the database. The connect ID is a valid database user that is used during two-tier (database) signon. So it applies to tools such as application designer and data mover. If you don't have a connect ID configured in configuration manager or you have the wrong connect password then you will get an invalid access ID and password for signon error EVEN if you use a valid PeopleSoft login (user name and password). Invalid Access ID and password for signon -- see your security administrator. Use configuration manager to set the correct Connect ID in the Startup tab: NOTE: that you can't get the connect password from the configuration file easily as it is encrypted. Redirect To Login Page When you access the root level of your PeopleSoft site, you normally get a web server message that allows you to click on a link that will take you to the login page. Here's a screenshot example of what I'm referring to with Weblogic: For various reasons (e.g. security, user-friendliness) you might want to instead do a redirect directly to the PeopleSoft login page. You can achieve this with a meta tag redirect on the HTML page. First, navigate to your web server directory, and under PORTAL or PORTAL.WAR find the file {{index.html}. This is the page you see by default. At the top of this file, just below the first tag, add the following: ... ...