I have been trying to get UAG set up to route users to my SharePoint 2013 webapp using hostnamed site collections.
Currently I have one app per hostnamed site collection in the trunk, and that works. However, we are going to create more and more hostnamed site collections, and I was under the impression I could do it all with one app instead of creating another UAG app for every site. So I'm wondering if I've done something wrong.
Setup:
SP2013 Webservers:
Each has a web application with no hostname listening to IP:443 with wildcard cert *.contoso.org
this web app "contoso web app" has several hostnamed site collections.
The top path-based required site collection is www.contoso.org/
hostnamed site collections: my.contoso.org, apps.contoso.org, etc
UAG 2010 Sp3 server:
Trunk:
trunk.contoso.org on port 443
Cert: *.contoso.org on UAG server
Application 1:
Farm of web apps
Webservers Addresses: web1.constoso.org, web2.constoso.org (because I'm not using SSL Termination I had to create DNS entries for each webserver )
Paths: /
Public host name: www.constoso.org
App2:
same but public host name my.contoso.org
App3:
same but public hostname apps.contoso.org
Am I doing this correctly? When I read UAG sp3 "supports host named site collections" I was under the impression I could do this with only one uag application.
Reading Wictor Willen's post ( http://www.wictorwilen.se/sharepoint-2013-and-unified-access-gateway-uag-2010-service-pack-3 )it looks like he only has one application with hostnamed site collections. The only difference I can see is he has *.sp.contoso.org which tells me. ... can I use only one UAG application but I have to have one more domain level? So instead of my.contoso.org I'd have to have my.x.contoso.org? That seems odd. I have read about a hundred posts and articles on this and can't find what is wrong.
Thanks for any help, even if it's "yes that's how you have to do it"