Sun GlassFish Communications Server 2.0 High Availability Administration Guide

Editing Configuration Settings

To configure a load balancer in the Admin Console, on the left frame, click the Converged Load Balancers node and then click the desired load balancer listed under the node. Open the Settings tab. This displays the Edit Converged Load Balancer Configuration Settings page.

The following table describes the load balancer configuration settings.

Table 2–1 Load Balancer Configuration Settings

Setting 

Description 

Policy Type 

Specifies whether the load balancing algorithm is determined by HTTP Policy and SIP Policy or by a DCR file. 

HTTP Policy 

Specifies the policy to be used for routing HTTP requests. The only allowed value is round-robin, which means the load balancer cycles through the cluster's server instances in a specified order.

SIP Policy 

Specifies the policy to be used for routing SIP requests. Specifies the parameters on which a consistent hashing policy is applied to obtain the hash key. This can be a single value or comma-separated values of parameter names to hash on. If more than one parameter is specified, the concatenated values of the parameters are used for applying the consistent hashing. The default is from-tag,call-id.

Upload DCR File 

Specifies the DCR file, which stores data centric rules for both HTTP and SIP requests. By default this file is not specified. If this file is specified, the default path and name is domain-dir/cluster/config/data-centric-rules.xml. If the converged load balancer configuration that specifies the data centric rules file does not reference any cluster or stand-alone server instance, the default path and name is domain-dir/config/data-centric-rules.xml.

If this file is specified, the instructions in this file override the HTTP Policy and SIP Policy settings. For more information about this file, see The Data Centric Rules File.

If an HTTP request doesn't match any DCR file rules, a hash key is generated using the remote host and port. If a SIP request doesn't match any DCR file rules, a hash key is generated using from-tag,call-id.

Property 

Allows you to set property names and values.