converged-lb-config (Sun GlassFish Communications Server 2.0 Administration Reference)

Sun GlassFish Communications Server 2.0 Administration Reference

converged-lb-config

Defines a converged load balancer configuration, which can be referenced by a 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 2.0 Administration Guide.

Superelements

converged-lb-configs

Subelements

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

Table 1–42 converged-lb-config Subelements


Element	Required	Description
converged-lb-policy	only one	Specifies the load balancing policy used by the converged load balancer.
converged-lb-cluster-ref	one or more; only one if this subelement's `selfloadbalance` attribute is `true`; zero if a `server-ref` is defined	References a cluster. This element contains some attributes related to load balancing.
server-ref	one or more; zero if a `converged-lb-cluster-ref` is defined	References a stand-alone server instance, which does not belong to a cluster. The referenced server element contains some attributes related to load balancing.
property	zero or more	Specifies a property or a variable.

Attributes

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

Table 1–43 converged-lb-config Attributes


Attribute	Default	Description
`name`	none	Specifies the name of the converged load balancer configuration.

Properties

The following table describes properties for the converged-lb-config element.

Table 1–44 converged-lb-config Properties


Property	Default	Description
`load-increase-factor`	`1`	Specifies the factor by which a single recovered server instance is incrementally included in load distribution. Allowed values are decimal numbers between 0 and 1. The load factor starts at zero and increases by `load-increase-factor` every `load-factor-increase-period-in-seconds` until it reaches 1. For example, if `load-increase-factor` is set to `0.1` and `load-factor-increase-period-in-seconds` is set to `60`, it takes ten minutes for a recovered instance to be fully included in load distribution. The `load-increase-factor` and `load-factor-increase-period-in-seconds` properties are applicable to all SIP requests and to HTTP requests for converged applications only if data-centric rules are specified. The `load-increase-factor` and `load-factor-increase-period-in-seconds` properties have no effect on the round-robin algorithm, which is applicable to HTTP requests for pure web applications.
`load-factor-increase-period-in-seconds`	`0`	Specifies the number of seconds between load factor increases for a recovered server instance. If `load-factor-increase-period-in-seconds` is set to zero, `load-increase-factor` has no effect. The load factor for the recovered instance becomes 1 immediately. If `load-factor-increase-period-in-seconds` is set and `load-increase-factor` is not set, the recovered instance gets no load for `load-factor-increase-period-in-seconds`. After `load-factor-increase-period-in-seconds` lapses, the load factor for the recovered instance becomes 1.
`sendUDPResponseFromBackend`	`false`	If `true`, specifies that UDP responses are sent to the client from the back end instead of the front end, saving an extra network hop.