Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Clusters: Configuration: General

Configuration Options     Advanced Configuration Options     Related Tasks     Related Topics

This page allows you to define the general settings for this cluster.

Configuration Options

Name Description
Name

The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.

MBean Attribute:
ClusterMBean.Name

Changes take effect after you redeploy the module or restart the server.

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-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.

MBean Attribute:
ClusterMBean.DefaultLoadAlgorithm

Cluster Address

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.

MBean Attribute:
ClusterMBean.ClusterAddress

Changes take effect after you redeploy the module or restart the server.

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.

MBean Attribute:
ClusterMBean.NumberOfServersInClusterAddress

Minimum value: 1

Changes take effect after you redeploy the module or restart the server.

Enable Transaction Affinity

If enabled, a server's transaction requests go to servers in the cluster that are already participating in the global transaction.

MBean Attribute:
ClusterMBean.TxnAffinityEnabled

Changes take effect after you redeploy the module or restart the server.

Advanced Configuration Options

Name Description
WebLogic Plug-In Enabled

Specifies if this cluster will receive requests from a proxy plug-in or HttpClusterServlet.

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 getRemoteAddr will 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 parameter (weblogic-plugin-enabled=false) in the config.xml file.
  • 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.

WeblogicPluginEnabled is duplicated both in ClusterMBean and ServerMBean. ClusterMBean overrides ServerMBean.

MBean Attribute:
ClusterMBean.WeblogicPluginEnabled

Changes take effect after you redeploy the module or restart the server.

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.

MBean Attribute:
ClusterMBean.ServiceAgeThresholdSeconds

Minimum value: 0

Maximum value: 65534

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

MBean Attribute:
ClusterMBean.MemberWarmupTimeoutSeconds

Minimum value: 0

Service Activation Request Response Timeout

The maximum time, in milliseconds seconds, for services to wait for response from cluster members.

MBean Attribute:
ClusterMBean.ServiceActivationRequestResponseTimeout

Changes take effect after you redeploy the module or restart the server.

Related Tasks

Related Topics


Back to Top