Create clustersOne can manage appservers collectively using a cluster. To create a cluster, view information about clusters, or manage server members on a cluster, use the Server Cluster page.
- Go to the Server Cluster page. Click Servers > Clusters in the console navigation tree. The Server Cluster page lists clusters of application servers in the cell and states whether a cluster is stopped, started or unavailable.
- Click New to access the Create New Cluster page.
- Type a cluster name.
- (Optional) To enable or disable node scoped routing optimization, place a checkmark in the Prefer local enabled check box. The default is enabled, which indicates that, if possible, EJB requests are routed to the client's node. If you enable this feature, performance is improved because client requests are sent to local EJBs.
- (Optional) To enable memory-to-memory replication of HttpSession (for failover) or replication of cached data and cache invalidations with a Web Container's dynamic caching, select options supporting data replication.
- Choose whether to create an empty cluster or to create a cluster based on an existing server.
To create an empty cluster, do not include an existing server in this cluster.
To create a cluster based on an existing server member, add server members to this cluster. To add a server member, choose Select an existing server to add to this cluster and then, from the drop-down list, select the server you want to add.
- Click Next.
- (Optional) Add appservers cluster(members) to the cluster. For each new cluster member, do the following:
- Type the name of a new appserver cluster(member) to add to the cluster.
- Select the node on which the server will reside.
- Specify the server weight. The weight value controls the amount of work directed to the appserver. If the weight value for the server is greater than the weight values assigned to other servers in the cluster, then the server receives a larger share of the servers' workload. The value can range from 0 to 20.
- Specify whether to generate a unique HTTP port.
- Specify whether to create a replication entry for the server. A replication entry enables memory-to-memory replication of HttpSession (for failover) or replication of cached data and cache invalidations with a Web Container's dynamic caching.
- Specify the server template.
- Click Apply to finish the cluster member. Repeat the above steps to define another cluster member.
- Click Next and review the summary of changes.
- Click Finish to complete the configuration.
- Click Save on the administrative console taskbar and save your administrative configuration. As part of saving the change to the configuration, you can select Synchronize changes with Nodes before clicking Save on the Save page.
- Before you can start the cluster, the configuration needs to be synchronized to the nodes. If you selected Synchronize changes with Nodes when saving your configuration in the previous step, you can ignore this step. If you are running automatic synchronization, wait until synchronization runs. Or, run manual synchronization to get the configuration files moved to the nodes. Click System Administration > Nodes and, on the Nodes page, select the node and click Synchronize or Full Resynchronize. The Nodes page displays status indicating whether the node is synchronized.
- To further configure a cluster, click on the cluster's name under Name. This displays the settings for the server cluster instance. Note that, unless you have clicked Save and saved your administrative configuration, you only see the Configuration and Local Topology tabs; to see the Runtime tab as well save your administrative configuration. Also, ensure that changes are synchronized to the nodes (step 12).
Balancing workloads with clusters
Server cluster collection
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.