Create a cluster: Basic cluster settings
Use this page to enter the basic settings for a cluster. To view this console page, click Servers > Clusters > WebSphere application server clusters > New.
Cluster name
Name of the cluster. The cluster name must be unique within the cell.
(zos) Short name
Short name for this cluster. This field only appears if you are running on z/OS .
The short name is used as the WLM APPLENV name for all servers that are part of this cluster.
If we specify a short name for a cluster member, the name:
- Must be one to eight characters in length
- Must contain only uppercase alphanumeric characters
- Cannot start with a number
- Must be unique in the cell
If we do not specify a short name, the system assigns a default short name that is automatically unique within the cell. We can change the generated short name to conform with the naming conventions.
Prefer local
The host scoped routing optimization is enabled or disabled. The default is enabled, which means that, when possible, enterprise bean requests are routed to the client host. Enable this setting improves performance because client requests are sent to local enterprise beans.
(zos) This field does not apply for z/OS.
Information Value Data type Boolean Default true Supported configurations: If we enable the preferLocal optimization, the deployment manager must be running to affect the configuration. If the deployment manager is shut down, preferLocal optimization is not performed and requests might be dispersed across all the members of the cluster.
Configure HTTP session memory-to-memory replication
Specifies that when the cluster is created, a memory-to-memory replication domain is created for each of the members of this cluster.
If a replication domain is created, it is given the same name as the cluster and is configured with the default settings for a replication domain. When the default settings are in effect, a single replica is created for each piece of data and encryption is disabled.
If the WAS cluster has session Memory to Memory replication enabled, then the plug-in configuration file for that server cluster must have the GETDWLMTable property set to true.
Also, if a replication domain is created, the SIP container and web container for each cluster member is configured for memory-to-memory replication.
(zos) Also, if a replication domain is created, the web container for each cluster member is configured for memory-to-memory replication.
(zos) Start with Version 7.0.0.5, if a replication domain is created, the SIP container and web container for each cluster member is configured for memory-to-memory replication.
To modify the replication domain settings, in the console, click Environment > Replication domains > replication_domain_name.
The default mode setting for the replication domain is Both client and server. In this mode, all data sent to either the client or the server is replicated. This setting is good for an environment that has a middle to low traffic load. However, if the environment has a high traffic load, you should change the replication domain mode setting to either Client only , or Server only, because these settings provide better scaling. In Client only mode, only data sent to the client is replicated. In Server only mode, only data sent to the server is replicated.
To modify the mode setting for a replication domain:
- In the console, click Servers > Server Types > WebSphere application servers > server_name.
- Under Container settings, click either SIP container settings or Web container settings, and then click Session management > Distributed environment settings > Memory-to-memory replication.
- (zos) Under Container settings, click Web container settings, and then click Session management > Distributed environment settings > Memory-to-memory replication.
- Select a different mode. It does not matter whether you change the mode under the SIP container or the web container because the same replication domain settings apply to both containers.
Avoid trouble: If we change any of the replication domain settings for one cluster member, including the mode setting, you should change them for all of the other members of the cluster.gotcha
Related concepts
Clusters and workload management
Create a cluster: Create first cluster member
Create a cluster: Create additional cluster members
Create a cluster: Summary settings