After creating a server, you can monitor its runtime state, change
its configuration, start and stop the server, and perform a range of other
administrative tasks to manage the server.
Before you begin
These tasks are for servers that you have already created.
Why and when to perform this task
The running of applications and services depends on the configuration
and running of ESB servers.
After creating a server, you can perform a range of other administrative tasks
to manage the server.
You can manage servers using either the administrative
console or a range of wsadmin commands.
This topic provides a summary
of alternative ways to manage available servers with the administrative console,
and provides links to where the associated tasks are described.
Steps for this task
- Display the list of servers.
In the navigation pane,
click .
This displays the Application
Servers collection page, which lists the servers, their cell, and
the nodes holding the servers. For each server, this page also shows the status
that indicates whether a server is started, stopped, or unavailable. You can
use this page to perform a number of actions on servers; for example, to create
new servers, start or stop servers, or open a page of detail settings for
a server.
- Display details about a server.
Display the list
of servers on the Application Servers page, then click
the name of the server.
This displays the settings
page for that server. You can use this page to view detailed information about
a server and its resources, or to change the configuration of the server and
its resources.
- Starting an application serverstart a server.
To be able to run applications and services, a server must be started.
If the server is in a network deployment cell, the node agent must already
be running.
- To start a node agent for a managed node, run the command wesb_install\profiles\profile_name\bin\startNode where profile_name is the name of the custom profile
for the managed node.
- To start a server, display the list of servers on the Application
Servers collection page, select the checkbox for the server, then
click Start.
- Detecting and handling problems with runtime componentsDetecting and handling problems with runtime componentsMonitor the running of clusters
and their members.
You must monitor the status of run-time
components to ensure that after starting they remain operational as needed.
You
can browse messages displayed in the server logs. You can also use the page of the administrative console to monitor the status of
run-time components.
- Stopping an application serverStop a server.
Stopping a server prevents it being used to run applications and
services.
Display the list of servers on the Application Servers collection
page, select the checkbox for the server, then click Stop.
- Deleting a server
Deleting a server deletes the
server identity and configuration, including the deployment of applications
and service on that server. The server is then no longer available to deploy
applications and services.
Display the list of servers on the Application
Servers page, select the check box for the server, then click Delete.
Last updated: Wed 06 Dec 2006 07:08:08
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)