The LIBPATH environment variable is not picked up when the Application Server is running as non-root in the UNIX environment
 Technote (troubleshooting)
 
Problem(Abstract)
If an Application Server is running as a non-root user and is started through the console, the Application Server does not pick up the LIBPATH environment variable setting in the user's .profile.
 
Cause
If the node agent and the Application Server are set to run as the same non-root user, such as wasadmin when the node agent is started with the root user, the node agent process still shows wasadmin as the owner:
After logging in as wasadmin and starting server1 from the command line using
./startServer.sh server1
the .profile set for the wasadmin user is issued and LIBPATH is set.

You might prefer or require that the console starts the Application Servers. When starting the Application Server from the Administrative Console, the properties set by the node agent are used when the Application Server starts. Therefore, if the node agent is not started by the wasadmin user, the Application Server does not inherit the wasadmin user's .profile setting of the LIBPATH variable.
 
Resolving the problem
When running the node agent from a non-root user, the Application Server must be started by the same non-root user. With this restriction, the node agent can pick up the LIBPATH variable from the non-root user's .profile and pass it onto the Application Server process.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > System Management/Repository
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1158690
IBM Group: Software Group
Modified date: Jan 26, 2004