Create the application in Access Gateway

  1. Sign in to the Access Gateway Admin UI console.
  2. Click the Applications tab.
  3. Click +Add.

  4. Select the Header Based option from the application menu. Click Create.

  5. In the Essentials pane, specify the following:

    Field Value
    Label A name for the application.
    Public Domain A fully qualified host name, for example ext-header.example.com
    Protected Web Resource

    The URL of the protected resource. For example, int-header.example.com[:port].

    When you configure a protected web resource, you can optionally set up load balancing for the resource. See Configure load balancing.
    Group Enter the group containing the users who should have access to the application.
    Description Optional. An appropriate description for your application.

Configure load balancing

  1. Expand the Protected Web Resource tab.
  2. Enable Load Balancing By Access Gateway. A table of hostnames and weights representing the target load-balancing instances appears. This table is initially empty. Click the Edit icon to modify an entry in the table, or click the Delete icon to delete an entry.
  3. Choose either HTTP or HTTPS as the URL scheme. Each protected web resource that you add inherits this scheme.
  4. Optional. Enable and enter the Host Header value.
  5. Complete the following steps to add a host. Repeat these steps as required:
    1. Click Add protected web resource.
    2. Enter a fully qualified hostname:port combination, like for example, https://backendserver1.atko.com:7001.
    3. Enter a weight from 1 to 100. Enter 0 to specify that a host is disabled.
    4. Click Okay.

  6. Optional. Configure health checks. They use GET operations to confirm that back-end resources are functional. New requests aren't routed to resources that have been labeled unhealthy by the health checks.

    1. Enable Load Balancer Health Check.
    2. Click Edit to modify health check settings.
    3. Modify the settings as required.
      Field Value

      Default
      Path The URI path to the resource used in the health check. /
      Method The HTTP method used in the health check. Always GET
      Status code The HTTP status code used to determine health. 200
      Interval The interval between health checks in seconds. 10
      Request timeout The health check request timeout in seconds. 1
      Healthy threshold The number of requests that must succeed before a host is considered healthy. 3
      Unhealthy threshold The number of requests that must fail before a host is considered unhealthy. 3
    4. Click Save.

Next steps

Add a certificate to the header application