You can start all the servers in a cluster (cluster members)
in one action. When you start a cluster you automatically enable workload
management.
About this task
When you request that all
members of a cluster start, the cluster state changes to partially
started and each server that is a member of that cluster
launches, if it is not already running. After all members of the cluster
are running, the cluster states changes to running.
The Ripplestart option
first stops and then starts each server in turn.
Tip: If
you are using clusters, the Initial State property of the Application
Server subcomponent (Servers > Application servers > server_name > Administration > Server
Components > Application Server) is not intended to be
used to control the state of individual servers in the cluster at
the time the cluster is started. It is intended only as a way to control
the state of the Application Server subcomponent of a server. It is
best to start and stop the individual members of a cluster using the
Server options of the administrative console or command line commands
(startServer and stopServer).
If
you use a deployment environment pattern of
Remote Messaging or
Remote
Messaging and Remote Support, there can be multiple clusters that
depend on one another. If such a case exists, start the infrastructure
and the clusters as follows to avoid potential startup problems:
- Infrastructure startup sequence:
- Database, Lightweight Directory Access Protocol (LDAP), and Web
servers
- Deployment manager (if needed)
- Node agents
- Cluster startup sequence:
- Messaging infrastructure cluster
- Support cluster (CEI)
- Application deployment cluster
To start a cluster, perform the following steps.