Starting an application server starts both the application server and any applications that run inside the application server. When starting an application server it is important to note that while the application server may start successfully, applications running inside an application server may fail to start.
Important: Do not start a WebSphere Commerce or WebSphere Commerce Payments application server as root. Starting these application servers as root changes the permissions on important files which may cause WebSphere Commerce and WebSphere Commerce Payments to function incorrectly.
To start an application server, do the following:
- Ensure that your database management system is started.
- Issue the following commands in a terminal window:
su - WAS_user cd WAS_installdir/bin ./startServer.sh server_name
where:
- WAS_user
- is the WebSphere Application Server user ID. The default WebSphere Application Server user ID is wasuser
- WAS_installdir
- is the installation directory for WebSphere Application Server.
- server_name
- is the name of the application server you want to start. This parameter is
case-sensitive - ensure that you have the correct case in the spelling of the
application server name.
The names of application servers are as follows:
Application Application server name WebSphere Commerce WC_commerce_instance_name WebSphere Commerce Payments payments_instance_name_Commerce_Payments_Server where commerce_instance_name is the name of the WebSphere Commerce instance and payments_instance_name is the name of the WebSphere Commerce Payments instance.
The default name of the WebSphere Commerce instance is demo, so the name of the default WebSphere Commerce application server is WC_demo.
The default name of the WebSphere Commerce Payments instance is wpm, so the name of the default WebSphere Commerce Payments application server is wpm_Commerce_Payments_Server.
The application server was successfully started when the following message is displayed:
Server server_name open for e-business
- Check the application server log files to ensure that the application server and the applications running inside the application server started without errors.
To stop an application server, do the following:
- Issue the following commands in a terminal window:
su - WAS_user cd WAS_installdir/bin ./stopServer.sh server_name
where:
- WAS_user
- is the WebSphere Application Server user ID. The default WebSphere Application Server user ID is wasuser
- WAS_installdir
- is the installation directory for WebSphere Application Server.
- server_name
- is the name of the application server you want to stop. This parameter is
case-sensitive - ensure that you have the correct case in the spelling of the
application server name.
The names of application servers are as follows:
Application Application server name WebSphere Commerce WC_commerce_instance_name WebSphere Commerce Payments payments_instance_name_Commerce_Payments_Server where commerce_instance_name is the name of the WebSphere Commerce instance and payments_instance_name is the name of the WebSphere Commerce Payments instance.
The default name of the WebSphere Commerce instance is demo, so the name of the default WebSphere Commerce application server is WC_demo.
The default name of the WebSphere Commerce Payments instance is wpm, so the name of the default WebSphere Commerce Payments application server is wpm_Commerce_Payments_Server.
The application server was successfully stopped when the following message is displayed:
Server server_name stop completed
- Check the application server log files to ensure that the application server and the applications running inside the application server stopped without errors.