Is publishing multiple sites including Sharepoint 2007, IIS 6, WSS 2.0 through one UAG application possible? RRS feed

  • Question

  • My company has a internal web portal hosted on a Sharepoint 2007 server.  The primary site and most content is hosted on the Sharepoint server but is also used as a portal to several other web applications and sites on different servers.  Some are IIS 6 web servers, 1 IIS 7 server, and a WSS 2.0 server.

    I am trying to configure UAG to access this primary server site portal but also be able to navigate through the portal to the other sites which are on different servers.

    I am able to access the Sharepoint 2007 site itself publishing a Sharepoint 2007 application in UAG.  But when accessing I am only able to see the content from the Sharepoint 2007 server application I published, cannot navigate to the other sites and web apps.  I thought I might be able to add the other serves into the Addresses section of the Web Servers tab in Application Properties for the published Sharepoint site.  But when attempting to do that I get an error saying "Youn can publish only one server for this application type".

    I am going to try and do the same by publishing a new application type.  But I am not sure if what I am trying to do is even possible.  And if possible which application type should I attempt to configure?

    The two most obvious choices are Other Web Application (application specific hostname) and Generic Browser-Embedded Application (multiple servers). 

    Has anyone tried something similar to this? Can my company portal that is hosted on several different web server types be published as a single application in UAG?

    Thanks in advance

    Tuesday, March 29, 2011 9:30 PM


All replies

  • I am publishing about 10 different applications on UAG. I created multiple trunks, and one of them is used for publishing SharePoint and 4 other applications on one trunk. Once you create trunk, you just need to create Applications (publishing rules).  For generic IIS or Apache sites, just use Web --> Other Web Applications.

    Do you get any error messages when you access other applications?

    My suggestion to you would be to create http trunk, and try publishing apps one by one. Also make sure you update external DNS records

    Friday, April 1, 2011 12:30 AM
  • thanks for the response, i have a much better handle on UAG now than i did a few days ago, mostly through trial and error, really not a lot of tech info out there yet on UAG

    i have been able to get most sites and functionality on my portal working.  like you said for generic IIS sites and the WSS 2.0 site i just published Web - Other Web Application (i used the 'portal hostname' option as opposed to 'application specific hostname' option, would like to know the difference but haven't found good information yet).  By publishing 'Other Web Application' for each of my generic IIS servers and the WSS 2.0 server everthing works great linking from my primary portal which is a Sharepoint 2007 site to the IIS and WSS 2.0 sites.

    my problem now is trying to go navigate directly from the primary portal to other areas of the portal that are on other Sharepoint 2007 web applications.

    For my scenario:

    Primary portal - Sharepoint 2007 site

    Internal URL -  http://spserver.mydomain.com:45964/sites/myportal (runs on port 45964 web app)

    UAG Published URL (external) - https://moss.mydomain.com/sites/myportal

    AAM on Sharepoint is configured with public and internal mappings.

    2nd site - Sharepoint 2007 site 

    Internal URL - http://spserver.mydomain.com/sites/site1 (this site runs on default web site port 80 web app)

    UAG Published URL (external) - https://web-app.mydomain.com/sites/site1

    AAM is configured properly, this site is accessible when linking directly off the UAG portal home page.

    But in my company portal home page there is a tab created that links to this second site, tab is configured for the internal URL (http://spserver.mydomain.com/sites/site1).  This portal is used internally as well so the tab must point to the internal DNS name and associated URL. 

    Problem is that when clicking that tab through the UAG session my machine is trying to access an internal URL and UAG does not recognize that this is my published Sharepoint app since when publishing Sharepoint through UAG you must configure a public URL and configure AAM.

    When publishing generic web sites you just configure UAG with the internal host name and UAG parses through your site and uses HAT (host addresss translation) to replace the internal name with something like https://uag.mydomain.com/uniquesig6bde2668a4c1c5537c654fb04c6ba522/uniquesig0/logo.jpg.  For Sharepoint publishing it cannot work like this.

    So how can I link from one Sharepoint site to another Sharepoint site when each run in their own Sharepoint web application and therefore are required to be published individually in UAG?

    Friday, April 1, 2011 1:14 PM
  • An applications specific hostname uses a dedciated FQDN so that the application can be accessed directly, rather than via the portal. These applications can be accessed using application-name.domain.com as opposed to portal.domain.com...SharePoint is a good example of an application like this...

    Have a look here too: http://blogs.technet.com/b/edgeaccessblog/archive/2010/01/15/what-happened-to-basic-and-webmail-trunks.aspx



    Jason Jones | Forefront MVP | Silversands Ltd | My Blogs: http://blog.msedge.org.uk and http://blog.msfirewall.org.uk
    • Marked as answer by Erez Benari Thursday, May 5, 2011 6:17 PM
    Friday, April 1, 2011 1:30 PM
  • Here's another good resource for SharePoint publishing http://blogs.technet.com/b/ben/archive/2010/12/29/sharepoint-publishing-concepts-and-considerations.aspx

    There are 2 potential scenarios with variations of using same or different protocols

    1. Sharepoint internal and external names are same
    2. SharePoint internal and external names are different

    I would reccomend you using same internal and external urls, if possible. It makes things much cleaner and simpler for management and development.

    For your scenario, create HTTP trunk and then publish both portals (you can publish multiple SP portals on one trunk; e.g i have 3 public and 2 dev) to make sure AAM is working ok. Use one of these two blogpost to do that. Once you confirm AAM is working ok, remove http trunk, create https and publish your portals. You also need to create HTTP to HTTPS redirect trunk.

    • Marked as answer by Erez Benari Thursday, May 5, 2011 6:17 PM
    Saturday, April 2, 2011 2:02 AM