Add Access Gateway load balancing to an existing application

Available since Access Gateway version 2022.2.3

1. Configure load balancing:

   1. Sign in to the Access Gateway Admin UI console.
   2. Select the Applications tab.
   3. Click edit () in the row containing the application.
   4. Select the Settings tab.
   5. Expand the Protected Web Resources tab.
   6. Enable Load Balancing. A table appears that stores hostnames and weights that represent load balancing instances. This table is initially empty. Click edit () to modify an entry in the table, or click delete () to delete an entry.
   7. Choose either HTTP or HTTPS as the URL scheme. Each protected web resource that you add inherits this scheme.
   8. Optional. Enable and specify Host Header value.
   9. Complete the following steps to add a host, repeat as required:
      1. Click Add protected web resource.
      2. Enter a fully qualified hostname:port combination. For example, https://backendserver1.atko.com:7001.
      3. Enter a weight from 1 to 100. Enter 0 to specify that a host is disabled.

         Weights represent the percentage of requests to route to this host.

         For example, two hosts of weights 2:1 would result in roughly 66% of requests being routed to the host weighted 2 and about 33% of requests being routed to the host weighted 1.

      4. Click Okay.

2. Optional. Configure health checks: Health checks use GET operations to confirm back and resources are functional. Resources deemed unhealthy aren't routed new requests.

   1. Enable Load Balancer Health Checks.
   2. Click Edit to modify health check settings.
   3. Modify settings as required.

      Field	Value	Default
      Path	URI to resource used in health check.	/
      Method	HTTP method used.	Always GET
      Status code	HTTP status code used to determine health.	200
      Interval	Interval between health checks in seconds.	10
      Request timeout	Health check request timeout in seconds.	1
      Healthy threshold	Number of successful requests before a host is considered healthy.	3
      Unhealthy threshold	Number of failed requests before a host is considered unhealthy.	3

   4. Click Save.
3. Click Done.