Application Server failed to boot

While booting the application server on AIX 6.1, I encountered the below issue:

PSAPPSRV.921614 (0) [03/18/10 10:24:55](3) PSJNI: Creating a Java VM instance

PSAPPSRV.979130 (0) [03/18/10 10:24:56](3) PSJNI: Created a Java VM instance

PSAPPSRV.979130 (0) [03/18/10 10:24:56](1) PSJNI: EnvImplementation::threadAttach: Could not attach to the Java VM

PSAPPSRV.979130 (0) [03/18/10 10:24:56](1) PSJNI: EnvImplementation::Ctor: Failed to attach the current thread

PSSAMSRV.868352 (0) [03/18/10 10:24:56](3) PSJNI: Created a Java VM instance

PSAPPSRV.921614 (0) [03/18/10 10:24:56](3) PSJNI: Created a Java VM instance

PSAPPSRV.921614 (0) [03/18/10 10:24:56](1) PSJNI: EnvImplementation::threadAttach: Could not attach to the Java VM

PSAPPSRV.921614 (0) [03/18/10 10:24:56](1) PSJNI: EnvImplementation::Ctor: Failed to attach the current thread

PSSAMSRV.868352 (0) [03/18/10 10:24:56](1) PSJNI: EnvImplementation::threadAttach: Could not attach to the Java VM

PSSAMSRV.868352 (0) [03/18/10 10:24:56](1) PSJNI: EnvImplementation::Ctor: Failed to attach the current thread

To solve this issue, I added PS_HOME\jre\bin to the app server AddToPATH variable.

PeopleTools client error on workstation

After setting up the client on the windows machine, sometimes users get the error message while trying to run pscfg.exe, pside.exe or psdmt.exe.

PS_HOME\bin\client\winx86\pscfg.exe

Error: This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem

In the PeopleTools 8.50 Installation guide, the task titled "Verifying Necessary Files for Installation on Windows" explains that the issue is caused by the C Run Time (CRT) files not getting updated which will cause PeopleTools not to run.

This from the PT 8.50 Installation guide Task "Verifying Necessary Files for Installation on Windows":

PeopleSoft PeopleTools 8.50 is developed using Microsoft Visual C++ 2005. Microsoft, as part of VC++ 2005, changed the way applications use and ship the required C Run Time (CRT) files (these files are installed as shared assemblies). PeopleSoft PeopleTools 8.50 programs require these files to be present or the programs will not run.

During PeopleSoft PeopleTools installation, the install programs will automatically update the Microsoft Windows machine performing the installation. However, if the bin folder or PS_HOME has been copied from one machine to any other machine to run PeopleTools, chances are the MS VC++ modules might not have installed already on that machine and user might get the error while trying to run any PeopleTools executable:

Error: This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem

To implement the solution, execute the following steps:

1. Go to PS_HOME\setup\vcredist.

2. Run vcredist_x86.exe.

The installation is completed automatically.

Try running any PeopleTools client executable now.

Oracle installation hangs

Oracle installation hangs at 89% in 11G

"hangs @89% complete" problem...To comeover from this, one needs to uncheck the "Configure Enterprise Manager" option in installation step 4.

Configuration of Enterprise manager is all along a different set of installation, one can carry that out separately.

Tip on Oracle 11.1.0.6 installation on AIX 6.1

Between the installation of Oracle 11.1.0.6 on AIX 6.1, I got an error message

messageUsername cannot be empty

Exception in thread "FileSystemPreferencesHook" java.lang.SecurityException: Could not lock User prefs. Lock file access denied.

at java.util.prefs.FileSystemPreferences.checkLockFile0ErrorCode(FileSystemPreferences.java:956)

at java.util.prefs.FileSystemPreferences.lockFile(FileSystemPreferences.java:945)

at java.util.prefs.FileSystemPreferences.sync(FileSystemPreferences.java:751)

at java.util.prefs.FileSystemPreferences.flush(FileSystemPreferences.java:844)

at java.util.prefs.FileSystemPreferences.syncWorld(FileSystemPreferences.java:488)

at java.util.prefs.FileSystemPreferences.access$1200(FileSystemPreferences.java:61)

at java.util.prefs.FileSystemPreferences$5$1.run(FileSystemPreferences.java:466)

To correct the problem, one need to edit 'refhost.xml' and change the PACKAGE VALUE to the value of the installed fileset ...

Server installation

-------------------------

$ cd database/stage/prereq/db/

$ cp -p refhost.xml refhost.xml.ORIG

$ vi refhost.xml

Look for the line (at or about line 55) ...

package value="xlC.aix50.rte" version="9.0.0.0"

Change it to ...

package value="xlC.aix61.rte" version="9.0.0.5"

Save and quit

Client installation

-----------------------

$ cd client/stage/prereq/client/

$ cp -p refhost.xml refhost.xml.ORIG

$ vi refhost.xml

Look for the line (at or about line 55) ...

package value="xlC.aix50.rte" version="9.0.0.0"

Change it to ...

package value="xlC.aix61.rte" version="9.0.0.5"

Save and quit

Then, try again with './runInstaller'

This is a known bug and resolution ID 741422.1 has been delivered for it.

Bind Variables on PeopleSoft Home Page

Prior to PT 8.48 release, there was a record WEBLIB_MENU, using which we were able to pass the dynamic variables to show the same on PeopleSoft Home Page. Below is the
resolution (Resolution # 1, copied from Oracle PeopleSoft Metalink site)

From PT 8.48 and above, one will not be able to find out the record WEBLIB_MENU. The design has been changed. Below is another resolution (Resolution # 2) how to pass the bind
variables like User ID, Instance name etc on the home page.

Resolution # 1 (Prior to PT 8.48, Oracle PeopleSoft Metalink, resolution ID # 623430.1)

E-PIA : How do you add/modify bind variables to change the look and feel. [ID 623430.1]

Resolution # 2 (PT 8.48 and above)

1. Open up App Package PT_BRANDING > Class BrandingBase in application designer. Search for the string ‘add &addjs’. Add the below code above the comment which contains the string ‘add &addjs’:

&greeting = "User: " %UserId " in Database: " %DbName;

The overall code will be like:

/* Added to show the bind variables on the home page */
&greeting = "User: " %UserId " on Database: " %DbName;
/* add &addjs to PT_IFRAME_HDR_SWAN (bind 22) and PT_IFRAME_HDR(bind 23) */

If this looks fine in presentation, its okay, however, the style/font of this variable "&greeting" can be taken care by PSHOMEPAGE Style Sheet

2. Open the PSHOMEPAGE Style Sheet in application designer, locate the "greeting" style class and replace this piece of code with the below code:

/*.greeting {
color: #FFFFFF;
font-family: Arial, Helvetica, sans-serif;
font-size: 12pt;
font-weight: bold;
}*/

/* Customized for the home page bind variables looks*/

.greeting {
color: #FFFFFF;
font-family: Arial, Helvetica, sans-serif;
font-size: 10pt;
font-weight: bold;
}

The above delivered code is commented and below is the customized one. You can use more alterations according to your choice.

Hope this will be of some help.

Cheers!!!

Folder and content missing on Portal

This is a very common issue when a new page/component get transferred from one instance to another or when someone create a new component. Portal registry index plays a major role in that and that is why sometimes after migration, we find the migrated content is not visible. For the same, below are some steps which needs to be done.

1. Bouncing the webserver and clearing its cache

This is required to get the new or migrated component on the portal. Webserver gets the information of the new object and reflect the same. For the cache, you can also specify the Cache Stale Interval value under PeopleTools > Web Profile > Web Profile Configuration. On the caching tab there is the Cache Stale Interval value. By default this is set to 86,400 seconds or 24 hrs. You will also want to uncheck the caching boxes on this page.

2. Manual solution

If bouncing the webserver is not a feasible solution, below steps can be done.

-- Go to the Structure and Contents. PeopleTools > Portal > Structure and Contents.
-- Click on appropriate content which is not coming up.
-- Change its sequence number from zero to something else.
-- Save.
-- Go back to the same content again.
-- Change its sequence number back to zero.
-- Save.
-- Signout from the application.
-- Clear your browser's cache.
-- Signin again and check.

From Peoplebooks about the Browser Cache settings
Browser cache can be set for either the user or the entire system. There are a few methods that may help, however it is recommended that in a production environment, unless you are using a kiosk situation or users are sharing computers, that you leave the defaults of these cache settings as delivered.

This type of caching is held in browser cache for the time specified or when a forced refresh occurs. By default this is set to 900 minutes. To change this setting, for everyone, do the following:

a) Navigate to PeopleTools->Personalization->Personalization Optionsb) Enter PPTL for the Option Category Levelc) Click the View All link on the gridd) Click the Format tab on the gride) Click the Set Option Default Value link for the METAXP User Optionf) To disable, set the default value to 0g) Signout of the current session, Delete browser cache, and sign back in for the change to take effect.

The app server or web server does not have to be rebooted for this to take.

NOTE:

To set this option for just the user logging on you need to go to the My Personalizations link at the bottom of the Portal menu structure and choose General options. Then set the override value of the Time page held in cache to 0. This does NOT require an app server reboot however you will need to delete your browser cache.

SchedulerTransfer servlet - posting issue

Issue: Distribution agent failed to post the files to report repository.

Error message: The XML file returned by the web server is invalid. XML document object creation failed.

Solution: This is an issue with SchedulerTransfer servlet which requires authentication. When a report needs to get transfer to report repository, distribution agant use SchedulerTransfer servlet for this purpose. SchedulerTransfer servlet checks for the default local node and if there is no authentication there, it will get fail. The Default Local Node must have the Authentication Option set to 'Password'. Application server needs a restart post this change.

Navigation below...

Peopletools > Integration Broker > Integration Setup > Nodes > Default Local Node must have Password Authentication

PeopleTools->Portal- > Node Definitions