Load balancing

Access Gateway can act as a load balancer to distribute its own loads and those of protected web resources.

  • Load balancing is disabled by default. You can enable and configure it in the Access Gateway Admin UI console.
  • Access Gateway uses sticky sessions, or persistence, to route second and subsequent requests to the same replicated back-end protected web resource.
  • Load balancing uses weight allocations to determine the percentage of total requests that Access Gateway directs to each host.
  • Access Gateway uses health checks to test and remove protected web resources from the load-balancing pool.

See Enable Access Gateway load balancing in an application.

Typical Access Gateway load balancer architecture.