none
Trunk and URLs RRS feed

  • Question

  • Hi,

    Is there a way for a single trunk to respond to multiple URL names? For e.g.:

    - www.company.com

    - finance.company.com

    - sales.company.com

    IIS can do this via Host Headers - so is UAG intelligent enough to have 1 trunk & 1 IP and multiple URLs?

    Or must each URL have its own trunk and its own IP address?

    Thanks

     

    Wednesday, April 28, 2010 9:48 AM

Answers

All replies

  • Each trunk can only have 1 portal, so a single URL in which to hit the trunk.  Where host headers and such come into play is being able to route to each application that you create via the URL assigned.  ie.  portal.company.com opens the UAG portal, which financeApp.company.com opens up an AP system directly, that is hosted in the UAG portal.  You can group your apps together via folders within the portal which can help you with organizing how your portal looks, but from what I've experienced, there's no way to have a 2nd URL / portal on the same trunk.
    Wednesday, April 28, 2010 1:32 PM
  • So can I have this for example:

    trunk URL: uag.company.com, 1 valid Internet ip address (but then have multiple applications published like this:)

    - 1st application (SPS 2007) - host header: sales.company.com, redirecting to server 1.1.1.2

    - 2nd application (SPS 2007) - host header: marketing.company.com, redirecting to server 1.1.1.2

    - 3rd application (SPS 2007) - host header: finance.company.com, redirecting to server 1.1.1.2

    1.1.1.2 is the backend internal SPS 2007 server, and each site exists on that box, and is available via host header configuration.

     

    Regards,

    Wednesday, April 28, 2010 1:45 PM
  • When you publish SPS, it asks for the public hostname. So yes, you can publish multiple hostnames for multiple web applications on a single SPS server.  It's as simple as just running the the Application Wizard for SPS.

    Just make sure you're Alternate Access Mapping and addressing information is correct.

    • Edited by D N G Wednesday, April 28, 2010 2:50 PM Added details
    Wednesday, April 28, 2010 2:48 PM
  • That is great news.

    Just a pity UAG won't honour the /secure "virtual directory" concept of most IIS/SPS servers.

    Anyway - thanks again

    Wednesday, April 28, 2010 3:03 PM
  • Keep in mind that if you're routing internally by IP address, that you'll have to check the "Replace the host header with the following" checkbox in Step 5 of the Add Application Wizard, or IIS won't know how to handle the call on the MOSS boxes.
    Wednesday, April 28, 2010 3:05 PM
  • I see that config box...but why is there the "PATH / " area ...its obviously confusing me.
    Wednesday, April 28, 2010 3:14 PM
  • You can route different things based on path.  ie.  https://subdomain.domain.com/ points to one thing while https://subdomain.domain.com/thisPath has different rules associated with it.
    Wednesday, April 28, 2010 3:54 PM
  • Oh I see, I thought it was the other way round...i.e. if someone types in http://company.com this should redirect to an internal server as follows: http://internalserver/directory

    But its actually like this: external URL of http://company.com/directory redirects to http://someinternalserver

    not too clear in the help files...is the above assumption correct?

     

    Wednesday, April 28, 2010 5:48 PM
  • That's exactly it, with the exception that the requested directory will be added to the internal URL.
    • Proposed as answer by Clement D. _ Wednesday, April 28, 2010 6:44 PM
    Wednesday, April 28, 2010 6:44 PM
  • so hang on...are you saying I could have this:

    http://company.com/secure (external URL) - and this could call http://internalserver/secure (internal URL)?

    And, on a single trunk, in the same SPS application I could have multiple paths defined:?

    http://company.com/secure (external URL) - http://internalserver/secure (internal URL)?

    http://company.com/finance (external URL) - http://internalserver/finance (internal URL)?

    http://company.com/marketing (external URL) - http://internalserver/marketing (internal URL)?

     

    Thanks

    Wednesday, April 28, 2010 7:44 PM
  • Yep.  Same functionality out of TMG / ISA.
    Wednesday, April 28, 2010 8:01 PM
  • OK, now I am even more confused...according to http://social.technet.microsoft.com/Forums/en-US/forefrontedgeiag/thread/43708368-1737-4d2e-a5c2-2d40a8f4d58d that /virtual_directory method was said to be not supported?

    There might be confusion to my questions though.

    Just tried this route...and it worked.

    http trunk: uag.company.com; published SPS website http://www.company.com

    on the SPS server, created virtual directories for /secure, /finance/, /marketing

    On UAG, I didnt need to define anything for /secure, /finance/, /marketing

    When testing from an Internet (external) client all the paths worked fine....http://www.company.com, http://www.company.com/secure, etc etc

     

    Now, when I create the HTTPS trunk - I understand that I need to use a different URL from http://www.company.com....maybe something like https://secure.company.com

    I think I am getting my head around this URL path thing...finally ;-)

    Thursday, April 29, 2010 6:49 AM
  • OK, now I am even more confused...according to http://social.technet.microsoft.com/Forums/en-US/forefrontedgeiag/thread/43708368-1737-4d2e-a5c2-2d40a8f4d58d that /virtual_directory method was said to be not supported?

    There might be confusion to my questions though.

    Just tried this route...and it worked.

    http trunk: uag.company.com; published SPS website http://www.company.com

    on the SPS server, created virtual directories for /secure, /finance/, /marketing

    On UAG, I didnt need to define anything for /secure, /finance/, /marketing

    When testing from an Internet (external) client all the paths worked fine....http://www.company.com, http://www.company.com/secure, etc etc

     

    Now, when I create the HTTPS trunk - I understand that I need to use a different URL from http://www.company.com....maybe something like https://secure.company.com

    I think I am getting my head around this URL path thing...finally ;-)


    Those will work, because anything that follows the path you input ie. "/" will be returned.  So if you published an application like www.company.com and put /secure/ in the path area, visitors would only be able to access anything that was in that path or below it.  In that example, they would not be able to get to /finance/ unless you added that as a path as well.
    • Marked as answer by Erez Benari Tuesday, May 4, 2010 12:08 AM
    Thursday, April 29, 2010 11:22 PM