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.The node agent for the node on which the Application Server resides must be running before you can start the Application Server.
This procedure for starting a server normally also 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.
If the node agent for the node on which the Application Server resides is not running, run the startNode command and then run the startServer command.
# ./startServer.sh server1Use the startManager command from the /usr/IBM/WebSphere/AppServer/product/bin directory:
# ./startManager.shYou 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.
If the node agent does not start, run the startNode command and then run the startServer command. Once a node agent completely stops running and remains stopped, you cannot remotely start the node agent from the Node Agents page. You must run the startNode command to start the node agent on the node where it runs.
To start the Application Server with standard Java debugging enabled:
Result
Once the server is started, you can install your applications.Related reference
addNode command
removeNode command
serverStatus command
startNode command
startServer command
stopNode command
stopServer command
startManager command
stopManager command