Clusters: Configuration: General
Configuration Options Advanced 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.
Default Load Algorithm
Defines the algorithm to be used for load-balancing between replicated services if none is specified for a particular service. The
round-robinalgorithm cycles through a list of WebLogic Server instances in order.
Weight-basedload balancing improves on the round-robin algorithm by taking into account a pre-assigned weight for each server. In
randomload balancing, requests are routed to servers at random.
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.
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.
Enable Transaction Affinity
If enabled, a server's transaction requests go to servers in the cluster that are already participating in the global transaction.
Enable Concurrent Single Activation
Specifies whether to allow the concurrent activation, deactivation, or restart of two or more singleton services.
Advanced Configuration Options
Name Description WebLogic Plug-In Enabled
Specifies if this cluster will receive requests from a proxy plug-in or
There are three values you can select in WebLogic Plug-In Enabled:
- Select Yes if the cluster will receive requests from a proxy plug-in or
HttpClusterServlet. A call to
getRemoteAddrwill return the address of the browser client from the proprietary WL-Proxy-Client-IP header, instead of the Web server.
- Select No to disable the
weblogic-plugin-enabled=false) in the
- Select Inherit for this cluster to inherit the value selected for WebLogic Plug-In Enabled for the domain.
Note: If you are using Oracle HTTP Server, the WebLogic Proxy Plug-In, or Oracle Traffic Director to distribute client requests to a Managed Server or a cluster, Oracle recommends choosing Yes.
For non-clustered servers that will receive proxied requests, this attribute may be set at the server level, on the Server > Configuration > General page.
WeblogicPluginEnabledis 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.
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
Service Activation Request Response Timeout
The maximum time, in milliseconds seconds, for services to wait for response from cluster members.
- Configure clusters
- Assign server instances to clusters
- Configure server migration in a cluster
- Configure cross-cluster replication