On UIS Cloud, click Cloud Services on the top navigation bar.
On the UIS-Sec portal of UIS Manager Standard Edition, click Network Services on the top navigation bar.
From the left navigation pane, select Network & Security > Load Balancers.
Click the name of a load balancer.
Click the Real Server Farms tab.
Click Create.
Configure the parameters as described in "Parameters."
Click Create.
Name: Enter a name for the real server farm.
Description: Enter a description for the real server farm.
Listener: Select a listener for the real server farm.
LB Algorithm: Select a load balancing algorithm for the real server farm. Options include the following:
Round Robin—Distribute requests to real servers based on their weight values. The higher the weight of a real server, the more requests that the real server receives.
Lease Connections—Distributes requests to the real server with the fewest connections. The least connections algorithm is a dynamic scheduling algorithm. The scheduler records the number of connections for each real server. When a request is distributed to a real server, the number of connections for the real server increases by one. When a connection is terminated or expired, the number of connections for the real server decreases by one. The least connections algorithm estimates the load of each real server based on the number of active connections to the server.
Source Address—Perform hash calculation on the source address of an access request and then distribute the request to the matching real server to make sure that access requests from a client is always distributed to the same real server.
Session Persistence: Select whether to enable session persistence. After you enable session persistence, the load balancer distributes access requests from the same client to the same real server for processing. Options include null, APP_COOKIE, HTTP_COOKIE, and SOURCE_IP.
APP_COOKIE—Distinguishes different clients by creating different cookies in the app sessions. Subsequent requests from clients with the same cookie are processed by the same real server. If you select this option, you must configure an app cookie name.
HTTP_COOKIE—Marks the HTTP response when a client connects to a real server for the first time. Subsequent requests with the same mark are processed by the same real server.