Starting an application server starts a new server process
based on the process definition settings of the current server configuration.
Before you begin
Before you start an application servers verify that all
of the resources. that the applications running on this server require,
are available. You must also start all prerequisite subsystems.
Avoid trouble:
- 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 valude might need to be
done at the node agent level such that the application server inherits
the right 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.
gotcha
About this task
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.
There are several
options available for starting an application server.
Procedure
- You can use
the administrative console.
- Click Servers > Application servers.
- Click server1 and click Start. 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 system. For
example, if you are using the Express version of the product, click Start
> Programs > IBM WebSphere > Base Vn > Profiles
> profile_name > Start the server.
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.
- You can issue a startServer command.
You can issue a command from the command
line. Use the startServer command
from the app_server_root/bin
directory, as shown in the following example. To start a server that
is associated with a non-default profile, issue the startServer command
from the profile_root/bin directory.
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.
Results
The specified server starts. To verify that the server is
in start state, in the administrative console, click Servers >
Application Servers.
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 Servers> Application Servers,
and then click the application server with the processes that you
want to trace and debug.
- Under Server Infrastructure,
click Java and Process Management > Process Definition.
- Select Java Virtual Machine.
- On the Java virtual machine page, select the Debug Mode option
to enable the standard Java debugger. Set Debug Mode arguments,
if they are needed, and then, click OK.
- Save the changes to a configuration file
- Stop the application server.
- Start the application server again as previously described.