Start and stop an application server on AIX, Linux, and Solaris operating environment
Starting an application server starts both the application server and any applications that run inside the application server.
When starting an application server the application server may start successfully but applications running inside an application server may fail to start. Ensure that log files are checked for problems.
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:
- Ensure that your database management system is started.
- Do one of the following:
- Issue the following commands in a terminal window
su - WC_non_root_user cd WC_profiledir/bin- For a WAS ND manager profile
su - root cd WAS_ND_profiledir/bin
where:
- WC_non_root_user
- The non-root user ID under which the application server will run.
- WC_profiledir
- The directory for WAS profile used for WebSphere Commerce.
- WAS_ND_profiledir
- The directory for WAS profile used for WAS ND manager profile.
- Do one of the following:
- To start an application server, enter
./startServer.sh application_servername- To stop an application server, enter
./stopServer.sh application_servername- To start the deployment manager
./startManager.sh- To stop the deployment manager
./stopManager.sh
where:
application_servername is the name of the application server you want to start or stop. The default WAS application server name is server1.
- Check the log files for any problems or errors. The log files are located in directory:
- WC_profileDir/logs/server1
Related Concepts
Application server log files
Related tasks
Ensure that WebSphere Commerce is started
Start and stop WebSphere Commerce