7.3

Table Of Contents
3 (Optional) Select the algorithm balancing method for this pool.
The algorithm options and the algorithm parameters for the options that require them are described in
the following table.
Option Description and algorithm parameters
ROUND_ROBIN Each server is used in turn according to the weight assigned to it.
If the load balancer was created in vRealize Automation, the weight is the same
for all members.
This is the smoothest and fairest algorithm when the server's processing time
remains equally distributed.
Algorithm parameters are disabled for this option.
IP-HASH Selects a server based on a hash of the source IP address and the total weight of
all the running servers.
Algorithm parameters are disabled for this option.
LEASTCONN Distributes client requests to multiple servers based on the number of
connections already on the server.
New connections are sent to the server that has the fewest connections.
Algorithm parameters are disabled for this option.
URI The left part of the URI (before the question mark) is hashed and divided by the
total weight of the running servers.
The result designates which server receives the request. This ensures that a URI
is always directed to the same server as long as no server goes up or down.
The URI algorithm parameter has two options -- uriLength=<len> and
uriDepth=<dep>. Enter the length and depth parameters on separate lines in the
Algorithm parameters text box.
Length and depth parameters are followed by a positive integer number. These
options can balance servers based on the beginning of the URI only.
The length parameter indicates that the algorithm should only consider the
defined characters at the beginning of the URI to compute the hash. The length
parameter range should be 1<=len<256.
The depth parameter indicates the maximum directory depth to be used to
compute the hash. One level is counted for each slash in the request. The depth
parameter range should be 1<=dep<10.
If both parameters are specified, the evaluation stops when either parameter is
reached.
Configuring vRealize Automation
VMware, Inc. 400