Filter
Top Products
6320ax04.fm Draft Document for Review July 28, 2004 7:33 pm
240 Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide
WebSphere Commerce instance management
This section describes how to start and stop, as well as how to check the status,
of the WebSphere Commerce instance.
Checking instance status
Run the following command from the <was_home>\bin directory:
serverStatus WC_<instancename>
Where <instancename> is the name of the instance. If the instance is running, the
last message from the serverstatus command will be:
ADM0508I: The Application Server “WC_demo” is STARTED
If the instance is not running, the last message will be:
ADMU0509I: The Application Server "WC_<instancename>" cannot be reached. It
appears to be stopped.
Other messages are possible, for example when the instance is starting or
stopping.
Starting the instance
Run the following command from the <was_home>\bin directory:
startServer WC_<instancename>
Where <instancename> is the name of the instance. When the instance is started,
the last message from the serverstatus command should be:
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server WC_<instancename> open for e-business; process id is
<process_id>
If the instance was already running, the some of the messages from the
startServer command will be:
ADMU3028I: Conflict detected on port 8882. Likely causes: a) An instance
of the server WC_<instancename> is already running b) some other process
is using port 8882
ADMU3027E: An instance of the server may already be running:
WC_<instancename>
Note: The parameters to the serverStatus, startServer and stopServer scripts
are case sensitive.