Starting 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 begin
Before you start an application server, verify that all of the application required resources are available. You must also start all prerequisite subsystems.
If you 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 your applications are web applications that use servlets, and JavaServer Pages (JSP). This option works less effectively if your applications use servlets, JSPs, and Enterprise JavaBeans (EJB).
- To ensure compatibility with other WebSphere® products, the default setting for the Start components as needed option is cleared. Before selecting this option, verify that any other WebSphere products, that you are running with this product, support this function.
- When you start an application server from the console, the application server inherits the node agent's environment, including the ulimit settings. Setting the ulimit to the needed value might need to be done at the node agent level such that the application server inherits the correct values from the node agent.
- When you start an application server from a command line, you must specify the ulimit settings in the OS shell before you issue the startServer command because in this scenario, the application server inherits the ulimit settings of the OS shell.
About this task
The node agent for the node on which an application server resides must be running before you 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 you create an application server definition, you can start, stop, or manage the new server using the administrative console, or you 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 startServer and stopServer command-line commands to start and stop the individual servers of a cluster.
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 theThere are several options available for starting an application server.
Procedure
Results
The specified server starts. To verify that the server is in start state, in the administrative console, click
.What to do next
After the server starts, deploy the applications that you want to run on this server.
- In the administrative console, click .
- Click the name of the application server with the processes that you want to trace and debug.
- Under Server Infrastructure, click .
- Select .
- Select .
- On the Java virtual machine page, select the option to start the standard Java debugger. Set arguments, if they are needed.
- Click OK.
- Save the changes to a configuration file
- Stop the application server.
- Start the application server again as previously described.