After you install and
configure a deployment environment,
use the administrative tools to monitor and control the resources
in the deployment environment, including deployment managers, node
agents, and clusters.
Starting deployment managers
The deployment manager is a server process.
You must start
the deployment manager before you can use its administrative console
to manage the cell.
Stopping a deployment manager
Stop the deployment manager server process
when performing
certain maintenance activities such as migrating to a new version
of the product or uninstalling the product. You can stop the deployment
manager at any time without affecting the operation of the servers
in its domain.
Starting node agents
The node agent of a managed node is
a server process that
must be started before you can start servers on the node. The node
agent must be started for the deployment manager to communicate with
it.
Stopping a node agent
Use the administrative tools when you
need to stop a node
agent (for example, to change the system clock). Node agents are administrative
agents that represent a node to your system and manage the servers
on that node.
Starting and stopping deployment environments
You can start or stop deployment environments based on
IBM-supplied patterns directly from the administrative console. You
cannot manage custom deployment environments with this procedure.
Starting a cluster
You can start all the servers in a cluster (cluster members)
in one action. When you start a cluster you automatically enable workload
management.
Stopping a cluster
You can stop all the servers that are members of the same
cluster at the same time by stopping the cluster.