Basic 2 of SharePoint-concept of site and site set

Site and site set

==================

Let's look back and ask a basic question: what is a WSS website?

First, the WSS site is a content storage container. The site content is mainly stored in the form of a list, a document library, and a child site.

 

Second, the website is an entity that can control security, and the content can be accessed by some configured users. A site either defines its own user set or inherits the user of the parent site. A site also includes a collection of user groups and a set of permissions, which define the Access Site List and document library capabilities of different types of users.

 

WSS does not perform user authentication. as an alternative, WSS relies on its IIS and ASP.. Net Authentication provider infrastructure to complete authentication operations. however, in the authorization part, WSS is indeed responsible. WSS provides user interface elements and Code, allowing privileged users to configure authorization for different elements in the site. WSS 3.0 also introduces the valuable security trimming feature, through which the commands and elements in the site can be viewed only by those users who have the right to access them.

 

Third, the site is a scalable application that can completely customize the user interface. the website administrator can create pages to customize the appearance and layout of the users. A site administrator can also use a browser to modify the navigation structure of the site.

 

Fourth, the website is the basis for using Microsoft Web Part Page and Web Part technology. the website administrator can customize the Web Part Page by setting the Web part. A user can modify, add, and delete Web parts to personalize the Web Part Page. all custom and personalized data is stored in the content database.

 

Each WSS site must be within the range of an existing web application. however, the website cannot exist independently as an entity in the Web application. each WSS site must be created within the scope of site collection. the site set is the container of the WSS site. each site set must have a top-level site. in addition to top-level sites, the site set also includes the hierarchical structure of sub-site points. shows some possible descriptive structures of the site set. the first site set only contains one top-level site. the second site set contains a sub-site under the top-level site. the third site set contains a sub-site hierarchy with slightly complex points.

When a company uses WSS Or Moss for the first time, the first problem is how to partition the site in the site. for example, should we create a large site set with many sub-sites? Or do I create many independent site sets? These decisions are finally made after reading the following paragraphs. you must obtain some knowledge about how the actions taken to partition a site to a site point set affect the scope of Management permissions, security boundaries, backup and restoration, and site design.

 

You should ask yourself why does the WSS architecture require a container for its sites? For beginners, the site set represents a range of management permissions. if you are assigned as the administrator of a site set, you have full permission to do whatever you want on any existing or future site in the site set.

 

Imagine that a large enterprise needs to create thousands of sites every year. the management of so many sites is not something that people in the IT department can pick up in a timely manner. the concept of site set is very important, because it allows IT department personnel to hand over the management responsibility to the department that owns the site set, so that they can perform management operations on their own.

 

Let's look at an example. in many companies, a person in the IT department is responsible for creating site sets for the needs of some functional departments. during the creation process, the IT department grants one or more users of the functional department administrator permissions on the level of site set creation. then, users with such permissions in functional departments can add users themselves. They can also create site elements, such as lists and document libraries, without the assistance of the IT department.

 

They can also add sub-sites under top-level sites. This allows them to increase their sub-site hierarchy as appropriate, or configure security options for these sub-sites.

 

The second motivation for using the site set is that they provide a membership relationship and a range of security authorization. according to Microsoft's design, each site set is in a security group, and is independent of any other site set on which users are site members and what users are authorized to do.

 

For example, assume that the IT department of a litware company has created a site set for the Sales Department and another site set for the accounting department. even though a user in the accounting department has administrator permissions in his site set, he cannot manage the security settings in the site set in the sales department. this is because the WSS architecture regards each site set as an island with security settings, and they are irrelevant to each other.

 

The third motivation for using the site set is that the site set provides a range of convenient backup and restoration operations. you can back up a site set and restore it accurately. the site set can be restored on the backup machine. in addition, the site set can be restored to different places on site, or even off site. this Backup recovery site set technology can be used as a policy application to migrate WSS sites from the test environment to the production environment.

 

Last, the site set provides many site elements and custom queries. for example, The WSS object model enables you to run queries and expand the list in all site sets. this capability cannot be used between site sets. therefore, when your application wants to summarize the list of several sites, you have a reason to put these sites in the same site set.

You can also create multiple custom site elements to reuse in sites in a site set. for example, if you create a website column in a top-level website, this website column can be reused by all the following sub-sites. this allows you to define website columns with certain types of features, such as format, legal validation, or a list of options, you can reuse this website column in different lists later. after a while, you can update the definition of the website bar, so that all your modifications will take effect in the list of referencing the same website bar in the entire site set. the site set is newly introduced in wss3.0.

 

How to Create a site set? The procedure is as follows:

Start-> Administrative Tools-> SharePoint 3.0 Central Administration open the Administration Center.

Application Management tab-> create site collection button

Enter necessary data and press OK to create a site set.

Note that the site set you just created does not have a site. Therefore, accessing the site set you created using a browser will render nothing visible.

You must create another top-level site.