Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

MOSS Site Architecture

  Asked By: Gaurang    Date: Oct 19    Category: MOSS    Views: 861

Can you let me know site hierarchy of MOSS?

Am I correct?

Web application

|

Site Collection (Portal)

|

WSS Site

Share: 

 

6 Answers Found

 
Answer #1    Answered By: Irving Hurley     Answered On: Oct 19

I like to include Managed Path as a first class citizen in the
hierarchy. So, I typically list it like this:
Farm > Web Application > Managed Path > Site Collection > Top-level Web
> Child Web

I uploaded the image that I use in my class here:
f9g.yahoofs.com/.../b28f.jpg?gr4aSDGB
OUple5tK

Of course, within a Web:
Web > List/Library/Gallery > List Item > Field

 
Answer #2    Answered By: Tiana Whitaker     Answered On: Oct 19

One of the large
Pharma's that I have been deploying MOSS globally to are now making heavy
use of managed paths. One of the hardest areas when doing architecture
work (Including Portal Site Topology's) is getting this information in
order. It takes time to map out how the business works and where and how
the divisions want to fall into line with one another.

 
Answer #3    Answered By: Alice Chandler     Answered On: Oct 19

While it's been said before it's worth saying again; there are two kinds
of Managed Paths:

1. Explicit Included Managed Paths that can have one site  collection
directly in the root
2. Wildcard Included Managed Paths that can have multiple named site
collections by no site collection  in the root

Excluded Managed Paths are no longer needed as ASP.NET checks the file
system first before passing a request to WSS v3.

One other thing I find fascinating about Managed Paths: the CAN include
a forward slash.

As you may already know, Managed Paths cannot contain Managed Paths.
However, consider the following scenario...

Create a Wildcard Managed Path called Products and place within it the
following named site collections:
Paper
Chemical
Bulk

The resulting URLs would be http://[site]/Products/Paper,
http://[site]/Products/Chemical, and http://[site]/Products/Bulk. But if
someone browsed to http://[site]/Products, wham 404. I call this a hole
in the URL.

vs.

Create the following Explicit Managed Paths:
Products
Products/Paper
Products/Chemical
Products/Bulk

Now you can create a single site collection in the root of each Managed
Path; all four URLs work as expected.

One downside is that you can only create Managed Paths from within
SharePoint 3.0 Central Administration whereas MOSS provides for the
creation of named site collections from the Sites Web. Not sure if there
are other problems or not. Thoughts?

 
Answer #4    Answered By: Lynette Sawyer     Answered On: Oct 19

I actually did a Screencast on this very thing yesterday. Todd can provide
a link if he likes.

 
Answer #5    Answered By: Joanne Greer     Answered On: Oct 19

I haven't had a chance to watch Bob's screencast but you can find it
here:
http://bobfox.net/Video%20Demos/ManagedPathsDemo.wmv

 
Answer #6    Answered By: Vinay Thakur     Answered On: Oct 19

it doesn't actually link to the file

Bob, any chance you could republish this for us ?

 
Didn't find what you were looking for? Find more on MOSS Site Architecture Or get search suggestion and latest updates.




Tagged: