The SystemOut.log file is not available in the WebSphere Commerce development environment. The contents of the Console view contain the messages that are discussed here.
To ensure that WebSphere Commerce is started:
- Open the following log file in a text editor:
WAS_installdir/logs/server_name/SystemOut.log
WAS_userdir/logs/server_name/SystemOut.log
where server_name is the name of the WebSphere Commerce application server. WebSphere Commerce application servers always have a name of WC_instance_name, where instance_name is the name of the WebSphere Commerce instance.
For example, if you have a WebSphere Commerce instance called demo, the server_name would be WC_demo.
- Ensure that the log file does not contain any Java exceptions.
- Ensure that the following text appears near the end of the log file:
WSVR0221I: Application started: WC_instance_name . . . . . WSVR0001I: Server WC_instance_name open for e-business
where instance_name is the name of the WebSphere Commerce instance.In the Console view, WC_instance_name is replaced with server1.
Note: Some text that appears in the log file has been omitted to indicate the relevant messages clearly.
The log file may contain text after these lines if you have performed any tasks using the WebSphere Commerce tools including the WebSphere Commerce Accelerator, the Administration Console, and the Organization Administration Console.
If WebSphere Commerce fails to start, you will see messages similar to the following near the end of the log file:
WSVR0101W: An error occurred starting, WC_instance_name WSVR0217I: Stopping application: WC_instance_name . . WSVR0220I: Application stopped: WC_instance_name . . WSVR0003E: Server WC_instance_name failed to start.
where instance_name is the name of the WebSphere Commerce instance.
In the Console view, WC_instance_name is replaced with server1.
Note: Some text that appears in the log file has been omitted to indicate the relevant messages clearly.