When starting and stopping an application server, a number of log files are generated. After starting or stopping an application server check the log files to ensure that both the application server and the application that run inside the application server started or stopped successfully.
The contents of the Console view when stopping and starting an application server are the same as the contents of the SystemOut.log file described below. To save log files when stopping and starting application servers in the WebSphere test environment, refer to the WebSphere Studio Application Developer information center.
The application server log files are in the following directory:
WAS_installdir/logs/server_name
WAS_userdir/logs/server_name
The WebSphere Commerce application server name is WC_instance_name, where instance_name is the name of the WebSphere Commerce instance. Each WebSphere Commerce instance runs in its own application server.
The WebSphere Commerce Payments application server name is instance_name_Commerce_Payments_Server, where instance_name is the name of the WebSphere Commerce Payments instance.
The following log files should be examined after starting or stopping an application server:
startServer.log
- This log file contains messages generated when the application server was starting. The application server started successfully if this log file contains the text "Server server_name open for e-business", where server_name is the name of the application server that was started.
OS/400 users should refer to the SystemOut.log file for this information. Refer to the description of SystemOut.log for more information.
Note: The successful start of an application server does not necessarily indicate that the application that runs inside the application server started successfully. For that information, examine the SystemOut.log file.
- stopServer.log
- This log file contains messages generated when the application server was stopping. The application server stopped successfully if this log file contains the text, Server server_name stop completed, where server_name is the name of the application server that was stopped.
- SystemErr.log
- This log file contains Java exceptions and stack traces. These exceptions are caught by enterprise applications and their associated application servers.
An empty SystemErr.log file does not necessarily indicate success since not all error messages generated by an application are considered to be error messages by the operating system. You must also examine the contents of the SystemOut.log file.
- SystemOut.log
- This log file contains messages generated when the applications running inside the application server are being started or stopped. This log file will not contain error messages - such messages will appear in the SystemErr.log file. However, this log file will contain error messages that the operating system does not see as error messages.
Both this log file and the SystemErr.log file should be checked after starting an application server to confirm that the applications inside the application server being started have also started successfully.
Refer to the WebSphere Application Server documentation for more information on all of the log files appearing in the log files directory.