none
extending Q on publishing many web-apps from same SP Farm on single trunk - only the top in app list works truely..

    Pergunta

  • WT..

    When i try to access to the var web-apps i always get the page of the first one in the applications list in the trunk UI..

    How can I force UAG to differentiate between them?

    this is critical for project success.

    tnx


    roys99

    domingo, 28 de abril de 2013 12:21

Todas as Respostas

  • domingo, 28 de abril de 2013 17:42
    Moderador
  • yes but it does not resolve my issue

    I have many web apps published on same sp farm - all using same ip BUT NATURALY DIFFERENT urls (IN SAME DOMAIN).

    I have been playing with this for many days now and have not resolved it.

    splitting between different trunks is no solution as SSO scope is only within a trunk.

    I would be very thankful for any advise.


    roys99

    domingo, 12 de maio de 2013 05:12
  • Hi Roy,

    UAG application association is based on HOST+PORT+PATH. If you have any application that share the same HOST+PORT+PATH you get "conflict" and UAG will associate the application with the first one on the list.

    For example, if you have:

    App #1 - http://server.company.com/

    App #2 - http://server.company.com/subfolder/

    Any request with app #2 will be associate with App #1, because http://server.company.com/subfolder/ match the rule for App #1.

    If the applications are published as SharePoint, you may consider creating separate site collection for each application with different name.

    If the applications are not SharePoint, the only trick I am aware of, is creating fake "hosts" in the HOSTS file in the UAG that point to the same IP of the web application and then publish the applications using those fake HOSTS entry. In the example above, let's say the backend server (server.company.com) address is 192.168.100.200, so if you will create the following HOSTS entries in the local UAG machine:

    192.168.100.200 app1.comapny.com app2.company.com

    You will be able to publish the two applications differently in UAG:

    App #1: http://app1.company.com/

    App #2: http://app2.company.com/subfolder/

    Although the backend server is the same, the UAG will think the two servers are different servers and you will not have a conflict...

    (Please note you have an option to replace the host header UAG sends to the backend server, so the fake addresses will not get all the way to the backend).

    Hope this helps..

    Ophir.

    ---

    Ophir Polotsky - Aman Group

    domingo, 12 de maio de 2013 17:31
    Moderador
  • hi,

    You say:

    "

    For example, if you have:

    App #1 - http://server.company.com/

    App #2 - http://server.company.com/subfolder/

    Any request with app #2 will be associate with App #1, because http://server.company.com/subfolder/ match the rule for App #1.

    "

    ! This is exactly it - I DO NOT have the same path !

    my apps are named  http://a1.mydomain.com , http://a2.mydomain.com and so on. each one is a web-app and all are published on same SharePoint 2010 farm on same NLB IP. But as the host name is different I would assume UAG would differentiate between them. yet I have this issue - also for NONE sharepoint apps..

    Roy


    roys99

    domingo, 19 de maio de 2013 05:58
  • Hi Roy,

    Does the backend server (SharePoint) is set with different name (on the "Web Server" tab) ?

    If the backend server is the same, from UAG point of view, it is the same server (no matter the external hostname is different).

    In that case, using HOSTS entry in the UAG will allow it to distinguish between the applications.

    If you are using different hostname in the "web server" tab - then this may be different issue...

    Ophir.

    segunda-feira, 20 de maio de 2013 04:06
    Moderador