Starting an application server starts a new server process based on the process definition settings of the current server configuration.
Why and when to perform this task
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 also 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 create a new application server definition using a base WebSphere Application Server, you cannot start, stop, or manage the new server using the administrative console that is associated with the original base server. You must use commands to perform these tasks for the new server.
If you create a new application server definition using WebSphere Application Server Express, you cannot start, stop, or manage the new server using the administrative console that is associated with the original base server. You must use commands to perform these tasks for the new server.
After you create a new application server definition, you can start, stop, or manage the new server using the administrative console, or you can use commands to perform these tasks for the new server.
After you start an Application Server, other processes might not immediately discover the running application server. Application servers are discovered by the node agent. However, node agents are discovered by the deployment manager. Even though node agents usually discover local application servers quickly, it might take a deployment manager up to 60 seconds to discover a node agent.
If you are using clusters, the Initial State property of the application server subcomponent (Servers > Application servers > server_name > Administration > Server Components > Application Server) is not intended to be used to control the state of individual servers in the cluster at the time the cluster is started. It is intended only as a way to control the state of the Application Server subcomponent of a server. It is best to start and stop the individual servers of a cluster using the Server options of the administrative console or command line commands (startServer and stopServer).
There are several options for starting an application server:
Steps for this task
If the node agent is not running, issue the startNode command and then issue 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 issue the startNode command to start the node agent on the node where it runs.
Server launched. Waiting for initialization status. Server server1 open for e-business; process id is 1932.
The startServer.log file is located in the profile_root\logs\server1 directory if you have installed your server with the default settings. The server name and process id vary depending on your settings.
# ./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 profile_root/logs/server1/ directory.
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.
To start the Application Server with standard Java debugging enabled:
Result
Once the server is started, you can install your applications.What to do next
You can use one of these same options to stop an application server.Related reference
addNode command
removeNode command
serverStatus command
startNode command
startServer command
stopNode command
stopServer command
startManager command
stopManager command