Publishing multiple SharePoint applications on a single port

Updated: February 15, 2013

Applies To: Unified Access Gateway

This topic describes how to deploy SharePoint web applications via Forefront Unified Access Gateway (UAG) in a topology in which the server running SharePoint Products and Technologies publishes multiple web applications on a single port.

The topology is as follows:

• A server running SharePoint Products and Technologies publishes multiple web applications on a single port, each with a unique host header.

• Each SharePoint web application is published via only one Forefront UAG trunk.

• The public address of the SharePoint site is different from the internal address of the site.

• External users access the SharePoint site over HTTPS; internal users access the same site over HTTP.

Two SharePoint web applications on a single server and using the same port, published via a single trunk

You must perform the following procedures on the server running SharePoint Products and Technologies, and on Forefront UAG. You can repeat these procedures to publish as many SharePoint web applications as required, via Forefront UAG; however, you cannot publish the same SharePoint web application more than once on each Forefront UAG trunk.

• Configuring Forefront UAG settings—Configure the Forefront UAG server to add a SharePoint web application to the trunk.

• Configuring the server running SharePoint Products and Technologies—Configure the server running SharePoint Products and Technologies.

Configuring Forefront UAG settings

This procedure describes the steps you must do on the Forefront UAG server to add SharePoint web applications to the trunk.

To add a SharePoint web application to the trunk

1. In the Forefront UAG Management console, click the trunk to which you want to add the application, and then in the Applications area, click Add.

2. In the Add Application Wizard, on the Select Application page, click Web, and then in the list, click Microsoft Office SharePoint Server 2013, Microsoft SharePoint Server 2010, or Microsoft Office SharePoint Server 2007.

   Important

   Do not publish the same SharePoint web application twice on the same trunk.

3. On the Select Endpoint Policies page, select the relevant SharePoint download and upload policies. These policies have been designed specifically for use with published SharePoint applications.

4. On the Web Servers page, do the following:

   • In the Addresses box, enter the public host name of the SharePoint web application (for example, HRPortal).

     Note

     Do not enter the internal host name of the load-balanced SharePoint site or of the server running SharePoint Products and Technologies.

   • In the Paths box, you can optionally define one or more paths on which the application resides, by double-clicking an empty line and entering a path. Note that the path must start with a slash.

   • In either the HTTP Port box or the HTTPS Port box, enter the port via which the application is published.

   • In the Public host name box, enter the public host name of the SharePoint web application, and then click Next. For more information, see About public host names. Note that the Replace host header with the following option is not relevant for this topology, and the box should be left empty.

5. On the Authentication page, do the following:

   • To allow rich client applications, such as Microsoft Word or Microsoft Excel, to authenticate directly to the SharePoint application without authenticating to the portal, select the Allow rich clients to bypass trunk authentication check box.

   • To use Office Forms Based Authentication (MSOFBA), select the Use Office Forms Based Authentication for Office client applications check box.

     Important

     Make sure that you read About rich clients and MSOFBA before you select this check box.

6. On the Portal Link page of the wizard, configure the portal link for the application.

   If you are publishing Microsoft SharePoint Server 2010, make sure that the Open in a new window check box is selected.

7. When you have completed the wizard, click Finish.

   The Add Application Wizard closes, and the application that you defined appears in the Applications list.

8. On the toolbar of the Forefront UAG Management console, click the Activate configuration icon, and then on the Activate Configuration dialog box, click Activate.

   After the configuration is activated, the message "Forefront UAG configuration activated successfully" appears.

Configuring the server running SharePoint Products and Technologies

This procedure describes the steps to configure the AAM settings on the server running SharePoint Products and Technologies.

For SharePoint Server 2013 it is recommended to configure host-named site collections instead of AAM. See Create a site collection in SharePoint 2013.

To configure the server running SharePoint Products and Technologies

1. On the server running SharePoint Products and Technologies, open the SharePoint Central Administration tool.

2. In the SharePoint 2013 Central Administration tool or in the SharePoint 2010 Central Administration tool, under System Settings, click Configure alternate access mappings.

   Note

   When using SharePoint Server 2007, in the SharePoint 3.0 Central Administration tool, click the Operations tab, and then under Global Configuration, click Alternate access mappings.

3. On the Alternate Access Mappings page, in the Alternate Access Mapping Collection list, click Change Alternate Access Mapping Collection, and then, on the Select an Alternate Access Mapping Collection dialog box, select the application that you want to configure.

4. On the Alternate Access Mappings page, click Edit Public URLs.

5. On the Edit Public Zone URLs page, in a zone box that is not yet defined, such as the Internet zone, enter the URL of the same public host name that you entered in the Public host name box when you added the SharePoint web application to the Forefront UAG trunk (as described in Configuring Forefront UAG settings). Make sure that the URL includes the protocol, according to the trunk type.

   For example, if you are publishing an application via an HTTPS trunk that resides in the domain woodgrovebank.com, and the application's public host name that you entered in Forefront UAG is HRPortal, enter the following URL: https://HRPortal.woodgrove.com.

6. When you have finished, click Save.

   Note

   Continue to the next step only if the Forefront UAG trunk via which users access the application is an HTTPS trunk, and if communication between the trunk and the server running SharePoint Products and Technologies is over HTTP (default Forefront UAG settings).

7. If the Forefront UAG trunk via which users access the application is an HTTPS trunk, and if communication between the trunk and the server running SharePoint Products and Technologies is over HTTP (default Forefront UAG settings), on the Alternate Access Mappings page, click Add Internal URLs, and then on the Add Internal URLs page, do the following:

   • In the URL protocol, host and port box, enter the internal URL of the SharePoint web application that you assigned in the Public host name box when you added the SharePoint web application to the Forefront UAG trunk (described in Configuring Forefront UAG settings). Make sure that the URL includes the protocol, according to the protocol that the application uses internally.

     For example, if you are publishing an application that uses the HTTP protocol internally and the public host name that you entered in Forefront UAG is HRPortal, enter the following URL: https://HRPortal.woodgrovebank.com.

   • In the Zone list, click the same zone in which you defined the public host name (in step 5 of this procedure), and then click Save.