converged-lb-policy (Sun GlassFish Communications Server 1.5 Administration Reference)

Sun GlassFish Communications Server 1.5 Administration Reference

converged-lb-policy

Specifies the load balancing policy used by the converged load balancer.

Note –

Some topics in the documentation pertain to features that are available only in domains that are configured to support clusters. Examples of domains that support clusters are domains that are created with the cluster profile. For information about profiles, see Usage Profiles in Sun GlassFish Communications Server 1.5 Administration Guide.

Superelements

converged-lb-config

Subelements

The following table describes subelements for the converged-lb-policy element.

Table 1–44 converged-lb-policy Subelements


Element	Required	Description
property	zero or more	Specifies a property or a variable.

Attributes

The following table describes attributes for the converged-lb-policy element.

Table 1–45 converged-lb-policy Attributes


Attribute	Default	Description
`http`	`round-robin`	(optional) Specifies the load balancing policy for pure HTTP requests. This attribute applies to the HTTP part of converged HTTP/SIP requests if `dcr-file` is not specified. The only allowed value is `round-robin`, which means that the load balancer cycles through the cluster's server instances in a specified order.
`sip`	`from-tag,call-id`	(optional) Specifies the load balancing policy for SIP requests if `dcr-file` is not specified. Specifies the parameters on which a consistent hashing policy is applied to obtain the hash key. The default is the only allowed value.
`dcr-file`	none	(optional) Specifies the `data-centric-rules.xml` file path name, which provides the rules for applying consistent hashing on SIP and converged HTTP/SIP requests. By default this file is not specified. If specified, this file takes precedence over the `http` and `sip` attributes. This can be an absolute or relative path. A relative path is relative to `domain-dir/cluster/config`. If a request doesn't match any DCR file rules, a hash key is generated using `from-tag,call-id`. For an HTTP request, this is the remote host port and address.