Starting clusters

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.

Why and when to perform this task

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.

When you request that all members of a cluster start, the cluster state changes to websphere.cluster.partial.start 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 websphere.cluster.running.

Steps for this task

  1. Click Servers > Clusters in the console navigation tree to access the Server Cluster page.
  2. Put a checkmark in the check boxes beside those clusters whose members you want started.
  3. 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 websphere.cluster.running. If the call to a node agent for a server fails, the server will 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.

Results

Note to Windows users: If you start and stop application servers that are part of a cluster using the Windows Services facility, 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.


Related tasks
Balancing workloads with clusters



Searchable topic ID:   trun_wlm_cluster_start
Last updated: Jun 21, 2007 4:55:42 PM CDT    WebSphere Application Server Network Deployment, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/trun_wlm_cluster_start.html

Library | Support | Terms of Use | Feedback