Starting an application 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 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.
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.
When 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 available for starting an application server.
In this information ...Related tasks
| IBM Redbooks, demos, education, and more |