Ensure that WebSphere Commerce is started

The SystemOut.log file should be reviewed when a WebSphere Commerce instance is started.

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:

1. Open the following log file in a text editor:

   AIX|Linux|Solaris|I5/OS|Windows:

   WC_profiledir/logs/server1/SystemOut.log

2. Ensure that the log file does not contain any Java exceptions.

3. Ensure that the following text appears near the end of the log file:

    Server launched. Waiting for initialization status.
     .
     .
     .
     .
     .
    Server server1 open for e-business; process id is xxxx.
   
   
   

   where xxxx is the process ID of the WAS.
   
   

   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:

An error occurred starting, server1
  .
  .
  .
  .
Server server1 failed to start.

Some text that appears in the log file has been omitted to indicate the relevant messages clearly.

 

Related Concepts

Application server log files

 

Related tasks

Start and stop WebSphere Commerce
Ensure that the database is started
Ensure that the Web server is started