You can start all members of a cluster at the same time by requesting
that the state of a cluster change to running. That is, you can start
all application servers in a server cluster at the same time.
Before you begin
Make sure that the members of your cluster have the debug port properly
set. If multiple servers on the same node have the same debug port set, the
cluster could fail to start. See
Java virtual machine settings
for
more information on how to change the debug port.
If
you use the Windows Services facility to start and stop application servers
that are part of a cluster, remember that the cluster state does not always
update correctly. For example, if a cluster is running and you stop a cluster
member through the Services GUI, the cluster state remains as started
even though the server is no longer running.
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 state becomes running.
Procedure
- In the administrative console, click Servers > Clusters.
- Select the clusters whose members you want started.
- Click Start or RippleStart.
- Start launches the server process of each member of the cluster
by calling the node agent for each server to start the servers. After all
servers are running, the state of the cluster changes to running. If
the call to a node agent for a server fails, the server does not start.
- RippleStart combines stopping and starting operations. It first
stops and then restarts each member of the cluster. For example, your cluster
contains 3 cluster members named server_1, server_2 and server_3.
When you click RippleStart, server_1 stops and restarts, then server_2 stops
and restarts, and finally server_3 stops and restarts. Use the RippleStart
option instead of manually stopping and then starting all of the application
servers in the cluster.
Important: If recently added cluster members do not start,
you might not have selected Synchronize changes with Nodes when you added
the members to the cluster. To determine if this is the problem:
- In the administrative console click Servers > Clusters,
select the cluster whose members did not start, and click Stop.
- Save your configuration. As part of saving
the change to the configuration, you can select Synchronize changes with
Nodes before clicking Save on the Save page.
- Start the cluster and verify that all of the cluster members
now start.
Results
When you start the members of a cluster, you automatically enable
workload management.