Publishing multiple SharePoint Sites in one name space (Full Version)

All Forums >> [ISA 2006 Publishing] >> SharePoint Publishing



Message

forumscm -> Publishing multiple SharePoint Sites in one name space (26.May2008 9:01:19 PM)


Hi,
 
I have a client that wants to publish multiple SharePoint sites and servers in a single name space.
 
EX:
 
intranet.local.domain/sharepointsite1/
intranet.local.domain/sharepointsite2/
intranet.local.domain/sharepointsite3/
 
sharepointsite1 is actualy server1.local.domain:999
sharepointsite2 is actualy moss2.local.domain:345
sharepointsite3 is actualy devmoss.local.domain:745
 
The external name is different than internal site as described.
 
Each rule is setup so that the external path would be matching the site as the example above.
 
External: /sharepoint1/ * Internal: /*
 
For that part it looks like it's working.
 
I have manage to find all the different internal paths and links to configure the Link Translation.
 
I have setup the AAM in SharePoint.
 
Here's my problem.
 
Some time Cancel or Close buttons won’t be change in the code given in IE.
 
Sometimes web pages will be translated to the correct URL.
EX:
 
intranet.local.domain/sharepointsite1/Pages/default.aspx
 
If you go in the user rights pages I get a double /sharepoint1/sharepoint1/_layouts/people.aspx
 
Does anybody knows if there could be any other way to do this or if it's by design?
 
Thank you,
 
CM



forumscm -> RE: Publishing multiple SharePoint Sites in one name space (28.May2008 11:58:25 AM)

Hi all,
 
I have found the answer.
 
What i"m trying to do is called asymmetrical paths.
 
MOSS 2007 dosn't support that.

 
From MS:
Microsoft Office SharePoint Server 2007 does not support asymmetrical paths. The path of the URL must be symmetrical between the public URL and the internal URL.
 
In compatibility testing, no link translation feature from any reverse proxy server, including ISA Server 2006, is sufficient to fix all Office SharePoint Server 2007 links to use the public URL. Office SharePoint Server 2007 embeds its URLs in many places and in a variety of encodings. Reverse proxy servers are currently not sophisticated enough to find and fix all of the URLs.

You can read the entire article at:
http://technet.microsoft.com/en-us/library/cc288609.aspx

Thanks,
CM



Page: [1]