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 can balance traffic load across a group of servers, monitor the health of each application server, and apply a variety of load balancing policies. Enterprise Application Access uses these advanced application settings to configure server load balancing:

  • Metric. Enterprise Application Access 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, Enterprise Application Access 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. Enterprise Application Access 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.

Configure server load balancing for applications and connectors

  1. Log in to the Enterprise Center.

  2. In the Enterprise Center navigation menu, select Application Access > Applications > Applications.

  3. Select the application to open it.

  4. In Advanced > Server load balancing select one of the Metric parameters:

    • Round-robin (default)
    • IP hash
  5. Optionally, to enable sticky cookies, select Enable Session Stickiness.

    1. Choose either to Specify cookie age and enter a cookie age in seconds or Derive the age from the server cookie if you prefer to use the cookie lifetime set by the origin server. If you choose to derive the age from the server, type the server cookie name into the field.

    2. Select Refresh sticky cookie.

  6. Optionally, to use sticky cookies for connectors, go to the advanced settings Miscellaneous and select Use sticky cookies for connectors.

  7. Click Save and Deploy.

Enable load balancing for several application servers

Configure an application for load balancing using two or more application servers.

  1. Log in to the Enterprise Center.

  2. In the Enterprise Center navigation menu, select Application Access > Applications > Applications.

  3. Select the application to open it.

  4. In Settings > Advanced > Server load balancing in the Application server IP/FQDN enter the IP address or FQDN and port number for an application server.

  5. Click Add more to add additional servers.

  6. In Advanced > Server load balancing select one of the Metric parameters:

    • round-robin (default)
    • IP hash
  7. To enable sticky cookies, select Enable Session Stickiness.

  8. Choose either to Specify cookie age and enter a cookie age in seconds or Derive the age from the server cookie if you prefer to use the cookie lifetime set by the origin server. If you choose to derive the age from the server, type the server cookie name into the field.

  9. Select Refresh sticky cookie.

  10. To use sticky cookies for connectors, go to the advanced settings Miscellaneous and select Use sticky cookies for connectors.

  11. Click Save and Deploy.


Did this page help you?