Server load balancing for applications and connectors

Load balancing efficiently distributes network traffic across a group of back end servers. A load balancer is piece of hardware (or virtual hardware) that distributes network and application traffic across different servers. It’s used to increase the concurrent user capacity and overall reliability of applications. Enterprise Application Access (EAA) can balance traffic load across a group of servers, monitor the health of each application server, and apply a variety of load balancing policies. EAA uses these application advanced settings to configure server load balancing:

Metric. EAA distributes traffic across origin servers by either round-robin or IP hash metrics. For round-robin balancing, traffic is distributed across all available servers. For IP hash balancing, EAA takes a hash from a specified server and serves the session content from there. The default metric is round-robin.

Enable session stickiness for applications. Session stickiness makes sure that a session uses the same connector when interacting with the application. When this is enabled, EAA uses sticky cookies which stay in place and do not change in order to maintain the same IP address for the session. In this way, the application always sees the same IP address for the session. This feature is needed for state maintenance of some applications.

Refresh sticky cookies. EAA can refresh a sticky cookie to make sure that the content goes to the same connector (server) to prevent session lag or content loss in a session. Even after the session length has passed, the session does not go to a new connector. This feature is only available when you enable session stickiness.

Use sticky cookies for connectors. Server redundancy balances the load on servers and provides a backup or fail-over contingency for your traffic. You can prevent server redundancy by using sticky cookies for connectors. This feature, disabled by default, ensures that requests get routed to the same server, also referred to as a connector, instead of a backup server. Enable this to ensure that requests always route to the same connector when multiple connectors are deployed for a single application, and the user connection goes to the same connector each time. This feature is available even if you do not enable session stickiness.