Why and when to perform this task
Starting a server starts a new server process based on the process definition settings of the current server configuration.This
procedure for starting a server normally applies to restarting a server. The
one exception might be if a server fails and you want the recovery functions
to complete their processing prior to new work being started on that server.
In this situation you must restart
the server in recovery mode.
If you created a new server definition using a base WebSphere Application Server, you cannot start, stop, or manage the new server using the original base Application Server.
There are several options for starting an Application Server:
Steps for this task (dependent on configuration)
Server launched. Waiting for initialization status. Server server1 open for e-business; process id is 1932.
The startServer.log file is located in the <drive>:\Program Files\IBM\WebSphere\AppServer\profiles\profile_name\logs\server1 directory if you have installed your server with the default settings. The server name and process id vary depending on your settings.
# ./startServer.sh server1You can check that the server has successfully started by checking the startServer.log file. If the server has successfully started, the last two lines of the startServer.log file reads:
Server launched. Waiting for initialization status. Server server1 open for e-business; process id is 1932.On AIX, the startServer.log file is located in the /usr/IBM/WebSphere/AppServer/profiles/profile_name/logs/server1/ directory.
To start the Application Server with standard Java debugging enabled:
Result
Once the server is started, you can install your applications.Related reference
serverStatus command
stopServer command
startManager command