Create a cluster : Basic cluster settings
Use this page to enter the basic cluster settings.
To view this administrative console page, click...
Servers | Clusters | New
- Cluster name
Name of the cluster. The cluster name must be unique within the cell.
- Prefer local
- The node scoped routing optimization is enabled or disabled. The default is enabled, which means that EJB requests are routed to the client node when possible. Enabling this setting improves performance because client requests are sent to local enterprise beans.
- Create replication domain for this cluster
Specifies that when the cluster is created, a replication domain is also created with the cluster. The replication service transfers both J2EE application data and any internal data that is used to maintain the application data among WebSphere Application Server run-time processes in a cluster of application servers.
Create a separate replication domain to use with each component that acts as a consumer of the replication. For example, one can configure one replication domain to use with a session manager and another domain to use with dynamic cache. The replication domain name that is created is identical to the cluster name. To manage the replication domain that is created, click...
Environment | Replication domains
- Existing server
- Whether to create an empty cluster or to add an existing application server to the cluster.
To create a cluster without an existing application server as a cluster member, click Do not include an existing server in this cluster.
To add an existing server to the cluster, click Select an existing server to add to this cluster and choose the application server to add to the cluster. This application server becomes a template for any additional cluster members that you add to the cluster. When adding servers to a cluster, the only way to remove an application server from a cluster is to delete the application server.
Specifies the amount of work that is directed to the application server.
If the weight value for the server is greater than the weight values that are assigned to other servers in the cluster, the server receives a larger share of the cluster workload. The value can range from 0 to 20. Enter zero to indicate that you do not want requests to route to this application server unless this server is the only server that is available to receive requests.
See AlsoClusters and workload management