Start an application server

When you start an application server, a new server process starts. This new server process is based on the process definition settings of the current server configuration.

Before you start an application server, verify that all of the application required resources are available. We must also start all prerequisite subsystems.

If we want server components to dynamically start as they are needed by the installed applications, verify that the Start components as needed option is selected in the configuration settings for the application server before you start the application server. Selecting this option can improve startup time, and reduce the memory footprint of the application server. Starting components as they are needed is most effective if all of the applications that are deployed on the server are of the same type. For example, using this option works better if all of the applications are web applications that use servlets, and JSP (JSP). This option works less effectively if the applications use servlets, JSPs, and EJB.

Avoid trouble:

gotcha

The node agent for the node on which an application server resides must be running before we can start the application server.

This procedure for starting a server also typically applies to restarting a server. The one exception might be if a server fails and you want the recovery functions to complete their processing before starting new work on that server. In this situation, you must restart the server in recovery mode.

After creating an application server definition, we can start, stop, or manage the new server using the administrative console, or we can use commands to complete 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 typically 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 is not intended to be used to control the state of individual servers in the cluster at the time the cluster is started. This property is intended only as a way to control the state of the subcomponent of a server. You should use the Server options on the administrative console, or the startServer and stopServer command-line commands to start and stop the individual servers of a cluster.

Avoid trouble: When a child process starts, Java appends the runtime path to the LIBPATH environment variable to ensure that it is using the correct library paths. Because this implementation does not check to see if the runtime path already exists in the LIBPATH environment variable, existing entries might get duplicated. However, when the parent process is stopped, then started, all of the additional runtime paths that were added to the LIBPATH environment variable when child processes started are removed from the LIBPATH environment variable.gotcha

There are several options available for starting an application server.


Results

The specified server starts. To verify that the server is in start state, in the administrative console, click Servers > Server Types > WebSphere application servers.


What to do next

After the server starts, deploy the applications to run on this server.

If we must start an application server with standard Java debugging enabled:

  1. In the administrative console, click Servers > Server Types > WebSphere application servers.

  2. Click the name of the application server with the processes to trace and debug.

  3. Under Server Infrastructure, click Java and process management > Process definition.

  4. Select Control.

  5. Select Java virtual machine.

  6. On the Java virtual machine page, select the Debug mode option to start the standard Java debugger. Set Debug mode arguments, if they are needed.

  7. Click OK.

  8. Save the changes to a configuration file

  9. Stop the application server.

  10. Start the application server again as previously described.


Related tasks


Restarting an application server in recovery mode
Stopping an application server
Manage application servers
Administer application servers
Create application servers
Use command-line tools


WASService command


Related reference


addNode command
removeNode command
serverStatus command
startNode command
stopNode command
startServer command
stopServer command
startManager command
stopManager command