7.4

Option Description and algorithm parameters
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.
HTTPHEADER The HTTP header name is looked up in each HTTP request.
The header name in parenthesis is not case sensitive which is similar to the ACL
'hdr()' function.
The HTTPHEADER algorithm parameter has one option headerName=<name>.
For example, you can use host as the HTTPHEADER algorithm parameter.
If the header is absent or does not contain any value, the round robin algorithm is
applied.
URL The URL parameter specified in the argument is looked up in the query string of
each HTTP GET request.
The URL algorithm parameter has one option urlParam=<url>.
If the parameter is followed by an equal sign = and a value, then the value is
hashed and divided by the total weight of the running servers. The result
designates which server receives the request. This process is used to track user
identifiers in requests and ensure that a same user ID is always sent to the same
server as long as no server goes up or down.
If no value or parameter is found, then a round robin algorithm is applied.
4 (Optional) Select the persistence method for this pool.
Persistence tracks and stores session data, such as the specific pool member that serviced a client
request. With persistence, client requests are directed to the same pool member for the life of a
session or during subsequent sessions.
Protocol Persistence method supported
HTTP None, Cookie, Source IP
HTTPS None, Source IP and SSL Session ID
Configuring vRealize Automation
VMware, Inc. 397