Clusters: Configuration: General
Configuration Options Related Tasks Related Topics
This page allows you to define the general settings for this cluster.
Name Description Name
The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.
The address that forms a portion of the URL a client uses to connect to this cluster, and that is used for generating EJB handles and entity EJB failover addresses. (This address may be either a DNS host name that maps to multiple IP addresses or a comma-separated list of single address host names or IP addresses.)
Defines the address to be used by clients to connect to this cluster. This address may be either a DNS host name that maps to multiple IP addresses or a comma separated list of single address host names or IP addresses. If network channels are configured, it is possible to set the cluster address on a per channel basis.
Default Load Algorithm
The algorithm to be used for load-balancing between replicated services if none is specified for a particular service. The round-robin algorithm cycles through a list of WebLogic Server instances in order. Weight-based load balancing improves on the round-robin algorithm by taking into account a pre-assigned weight for each server. In random load balancing, requests are routed to servers at random.
Defines the algorithm to be used for load-balancing between replicated services if none is specified for a particular service.
WebLogic Plug-In Enabled
Set this attribute to true if the cluster will receive requests from a proxy plug-in or
HttpClusterServlet. When WeblogicPluginEnabled is true, a call to getRemoteAddr will return the address of the browser client from the proprietary
WL-Proxy-Client-IPheader, instead of the web server.
For non-clustered servers that will receive proxied requests, this attribute may be set at the server level, on the
WeblogicPluginEnabled is duplicated both in
Service Age Threshold
The number of seconds by which the age of two conflicting services must differ before one is considered older than the other.
Client Cert Proxy Enabled
When set to true for a cluster, this attribute specifies that certs from clients of web applications hosted on the server instances in the cluster are provided in the special
WL-Proxy-Client-Certheader sent by a proxy plug-in or
ClientCertProxyEnabledcan be defined at the cluster level, at the server level, and at the web application level, in
This setting is useful if user authentication is performed on the proxy server—setting
clientCertProxyto true causes the proxy server to pass on the certs to the cluster in a special header,
WL-Proxy-Client-Certheader could be provided by any client with access to WebLogic Server. WebLogic Server takes the certificate information from that header, trusting that is came from a secure source (the plug-in) and uses that information to authenticate the user.
For this reason, if you set
clientCertProxyto true, use a connection filter to ensure that WebLogic Server accepts connections only from the machine on which the plug-in is running.
Member Warmup Timeout
Maximum number of seconds that a cluster member will wait to discover and synchronize with other servers in the cluster. Normally, the member will be able to sync in 30 seconds. If the value of this attribute is higher, that does not necessarily mean that it will take longer for the member to warmup. Instead it defines an upper bound on the time that a server will wait to sync with the servers that it has discovered. If the value is set 0, servers will not attempt to discover other running server in the cluster during server initialization
Number Of Servers In Cluster Address
Number of servers to be listed from this cluster when generating a cluster address automatically. This setting has no effect if Cluster Address is explicitly set.
- Configure clusters
- Assign servers to clusters
- Configure server migration in a cluster
- Configure cross-cluster replication