Use commands or the administrative console to stop and
start individual resources in the runtime environment, including deployment
managers, node agents, deployment environments, and clusters.
Starting and stopping 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. 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 and stopping node agents
Node agents are administrative agents that represent a
node to your system and manage the servers on that node. The node
agent is a server process that must be started before you can communicate
with the deployment manager or start servers on the node. If you need
to stop or restart the node agent (for example, for system maintenance
like changing the system clock), use the administrative console.
Starting and stopping deployment environments
You can start or stop deployment environments based on
IBM-supplied patterns directly from the administrative console; this
action stops and starts all clusters in the deployment environment.
Starting and stopping a cluster
You can start or stop all of the servers in a cluster (cluster
members) in one action. When you start a cluster you automatically
enable workload management.