Share via

Publishing load-balanced Web farms

  • Article

Updated: July 31, 2012

Applies To: Unified Access Gateway

Forefront Unified Access Gateway (UAG) allows you to publish a single Exchange server or a load-balanced Web farm of Exchange servers.

You can choose to publish a load balanced Web farm on the Deploying an Application page of the Add Application Wizard. If you are also publishing Outlook Web Access or Outlook Anywhere, follow the procedures described in Publishing Outlook Web Access on a Forefront UAG portal or Publishing Outlook Anywhere on a Forefront UAG portal, and then when you reach the Deploying an Application page of the Add Application Wizard, continue with the following procedure.

To publish a load-balanced Web farm

  1. On the Deploying an Application page of the Add Application Wizard, click Configure a farm of application servers.

  2. On the Load-Balanced Web Servers page of the wizard:

    • In the Addresses list, enter the IP addresses or host names of the Client Access servers.

    • In the Public host name box, enter the public host name for this application.

    • If you want to use the Web server farm name in the HTTP host header, select the Use the farm name in the HTTP host header check box, and in the Farm host name box, enter the host name of the Web server farm.

    • Select the affinity method to be used for Web farm requests.

  3. On the Configure Connectivity Verifiers page of the wizard, configure the method by which the state of the Web farm members will be determined, and configure the connectivity verifier response thresholds.

    The three connectivity verifier methods are:

    • Send an HTTP GET request—Forefront UAG sends an HTTP GET request and waits for the reply. Use this method to verify that a Web server is running and can be reached by Forefront UAG.

    • Send a ping request—Forefront UAG sends a ping request to the specified server and waits for a reply. Use this method to verify that a server is running and can be reached by Forefront UAG.

    • Establish a TCP connection—Forefront UAG tries to establish a TCP connection to a specific port on the specified server. Use this method to verify that a specific service is running on the server and can be reached by Forefront UAG.

    Note

    When publishing Exchange services on an HTTPS trunk, you must have a trusted and unexpired certificate on the Exchange Client Access server.

  4. Complete the wizard as described in Publishing Outlook Web Access on a Forefront UAG portal or Publishing Outlook Anywhere on a Forefront UAG portal.