Setting the startServer.log and stopServer.log file locations when running the startServer and stopServer commands
 Technote (troubleshooting)
 
Problem(Abstract)
How do I set the startServer.log and stopServer.log file locations? This location is created when running the startServer, stopServer, startNode, stopNode, startManager, and stopManager commands.
 
Resolving the problem
When you use the commands located in the $WAS_HOME/bin directory to start the servers, a startServer.log or stopServer.log file is created to log the information. The files, by default, go to $WAS_HOME/logs/server name director; no matter what environment variables you set in WebSphere® Application Server, this does not change.

To change the log file locations, add the -logfile path and file name flag to the end of the command used to run the script. Thereafter the script creates and uses the path and file name to log the information that would have logged in the startServer.log or stopServer.log.

Note: If you do not define a file name, or the location does not allow the script to write to it (no permission), an error is thrown in the command prompt or terminal. The operation is not cancelled; instead, the logging is not captured in a file.

Example:

>startServer server1 -logfile C:\logs\start.log

 
 
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 > Servlet Engine/Web Container
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1162880
IBM Group: Software Group
Modified date: Mar 10, 2004