WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


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.

Before you begin

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:
  1. Infrastructure startup sequence:
    1. Database, Lightweight Directory Access Protocol (LDAP), and Web servers
    2. Deployment manager (if needed)
    3. Node agents
  2. Cluster startup sequence:
    1. Messaging infrastructure cluster
    2. Support cluster (CEI)
    3. Application deployment cluster
To start a cluster, perform the following steps.
Procedure
  1. From the administrative console of the deployment manager, click Servers > Clusters.
  2. Select the cluster you want to start.
  3. Start the cluster.
    Note: If you use a deployment environment pattern of Remote Messaging or Remote Messaging and Remote Support make sure that you have started infrastructure components and that you start the clusters in the proper sequence, as described in About this task.
    • If your servers are stopped, click Start. This option calls the node agent for each server to launch the server process. If a call to a node agent for a server fails, the server does not start.
    • If your servers are running, click Ripplestart to first stop and then restart each cluster member.
      Note: The Ripplestart option restarts servers in sequence and ensures that at least one server in the cluster is online to handle requests.

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.zseries.doc/doc/tadm_start_cluster.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).