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).
Avoid trouble: To ensure compatibility with other WebSphere
® products, the default
setting for this option is deselected. Before selecting this option,
verify that any other WebSphere products,
that you are running in conjunction with this product, support this
functionality.
gotcha
About this task
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 prior to new work being started
on that server. In this situation, you must restart the server in
recovery mode.
If you create any
additional application servers, you cannot start, stop, or manage
these servers using the administrative console that is associated
with the original base server. You must either use command-line tools
to perform these tasks for the additional servers, set up an administrative
console for each server, or configure an administrative agent to provide
a single interface to all of your servers, including the original
base server. An administrative agent makes it easier to more fully
administer these unfederated application servers.
Avoid trouble: If you
create additional application servers, only use one server to modify
and save configurations. There is no coordination of configuration
setting between the different servers and if you modify and save configurations
on multiple servers, your data might become corrupted.
gotcha
There are
several options available for starting an application server.
Procedure
- You can use
the administrative console to complete the following steps:
- Click .
- Select server1 and click . You can view
the status and any messages or logs to make sure the application server
starts.
You can use the Start menu on a Microsoft® Windows® operating system. For example, if you are using the Express™ version of the product, click nprofile_name.
You 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.
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.
If a Windows service
has been created for the application server, optionally use the Windows Services utility to
start, stop, and monitor the basic status of the server.
- To launch the Services utility, click Start > Settings
Control Panel.
The Control Panel folder displays.
- Double-click the Administrative Tools icon.
The
Administrative tools folder displays.
- Double-click the Services icon.
Read about
the Services utility in the Windows online
help.
Read the topic about the WASService command for information
about adding and removing Windows services.
You can
issue a startServer command. Read the topic on the startServer
command for information about the command, including such information
as running the command and defining the file name for the start server
log. Read the topic on using command-line tools for information such
as determining from what directory to run the startServer command.
You
can check that the server has successfully started by checking the
start server log. If the server has started successfully, the last
two lines of the start server log look like the following example:
Server launched. Waiting for initialization status.
Server server1 open for e-business; process id is 1932.
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.
If you need to start an application
server with standard Java™ debugging
enabled:
- 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 .
- On the Java virtual machine
page, select the option to enable 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.