Sharepoint基本概念
2014-03-15 00:16
357 查看
There is a great deal of confusion around some terms related to the different levels of SharePoint hierarchy. Some of this is buzword overload and some has been brought about by inconsistent usage from Microsoft (and to be fair actually most of us in this
industry).
So if you’ve ever wondered what things like Farm, WFE, NLB, Web Application, Site Collection and Top Level Site mean I am going to try and clarify the different terms without getting too technical as some of this stuff needs
to be know by advanced, or power, users. I’ve missed out some of the more esoteric th
4000
ings like managed paths in the interests of readers sanity.
When you load a page each element (including the page itself) makes a request to SharePoint and receives some data – which can be html, images, files etc.
A device to distribute requests from your users browsers to the Web Front Ends
A collection of servers that take requests from users (via the NLB), process them and return the data.
This is the primary method for scaling – as the number of users grow you add more WFE’s.
The database servers store all volatile data (i.e. data that changes) in SharePoint.
You have exactly 1 configuration database and 1 to many content databases.
Each content database can only be on 1 server (more technically if you consider failover servers) but you can have different content databases on different servers – another method of scaling with increased load.
Authentication is the process of deciding WHO a user is.
Authorization is the process of deciding WHAT they can do.
IIS (the web server) handles Authentication alongside things like Active Directory and SharePoint handles authorization.
Authentication methods include things like Anonymous, Basic, Forms, Integrated (NTML/Kerberos and Claims).
A collection of servers (web, database, index) that together make up a SharePoint Installation – aka Topology.
You can do all this (web/datababase/index etc) on a single server in “Simple Installation” mode in which case you don’t need a NLB. For many small businesses this is plenty enough.
Medium sized businesses usually start with at least 2 Web Front Ends (WFE’s) and a database server.
Multinationals can have some very complex setups involving dozens
of components.
A common small SharePoint Farm topology - two WFE servers and a database server.
The entire installation as a whole. So if something has “Farm” level scope it applies to everything.
An IIS Website that has been configured to run SharePoint.
Can only be created in the Central Admin UI (or via the STSADM tools etc)
A Farm has one running the central administration site and 1 to many others running normal SharePoint sites.
This is generally how the main part of the URL is defined – e.g. http://somesite.yourcompany.com and http://othersite.yourcompany.com will be separate Web Applications.
This authentication method is set at the Web Application level – though you can have the same content (i.e. SharePoint site) delivered by two different web applications with two different authentication methods.
Port and network card bindings, host headers and a host of other networky stuff is set at the Web Application level – so if you want external users, for example, to have access to a site that would apply at the Web Application level (you can apply more granular
restrictions using authorization security though).
The Application Pool (the account that SharePoint runs under and the resources that it can consume) are also set at the Web Application level.
Note – Used to be known as “Virtual Server” before the days of Virtualization technologies.
Each web application has at least 1 Site Collection (but can have many).
Each Site collection has exactly 1 ‘Top Level Site’.
The Site Collection doesn’t actually contain anything itself - that is down to the Top Level Site.
This is the level that things like the Recycle bin and Quotas are organised at.
Each site
collection can only use a single content database (though multiple site collections can us the same content database) – this has major design implications as there aremaximum recommended sizes
for a content database.
A Top Level Site is a site… at the top level… see – this terminology is not that confusing after all
Most of the time we can use Top Level Site and Site Collection interchangeably - in fact Microsoft do this all the time.
Each Top Level Site has zero to many sub-sites (simply called sites)
This is the lowest level that many things can be scoped to, for example only the Top Level site contains a web part Gallery so you can’t say Collection X, Site A can have a web part but Collection X, Site B can’t.
When you look at Site Settings in a top level site you will see the highlighted sections – in a sub site you will not. Both are called Sites in the UI.
Site
(aka Web’s) – these are the actual sites that you use.
A site can be a top-level site or a sub site of the top level site.
A site can also have other sites – these are called sub-sites.
Sub sites can also have other sub sites and so on.
A site can inherit its parent’s permissions or define its own – more on this complex subject in a future article.
Finally a Site! - the thing that you actually use and what most of us think as "SharePoint"
References
TechNet
– Creating Your First Web Application, Site Collection and Web Site
TechNet
– Farm topology management
industry).
So if you’ve ever wondered what things like Farm, WFE, NLB, Web Application, Site Collection and Top Level Site mean I am going to try and clarify the different terms without getting too technical as some of this stuff needs
to be know by advanced, or power, users. I’ve missed out some of the more esoteric th
4000
ings like managed paths in the interests of readers sanity.
General Terms
Request
When you load a page each element (including the page itself) makes a request to SharePoint and receives some data – which can be html, images, files etc.
Network Load Balancer (NLB)
A device to distribute requests from your users browsers to the Web Front Ends
Web Front Ends – (WFE)
A collection of servers that take requests from users (via the NLB), process them and return the data.This is the primary method for scaling – as the number of users grow you add more WFE’s.
Database
The database servers store all volatile data (i.e. data that changes) in SharePoint.You have exactly 1 configuration database and 1 to many content databases.
Each content database can only be on 1 server (more technically if you consider failover servers) but you can have different content databases on different servers – another method of scaling with increased load.
Authorisation and Authentication
Authentication is the process of deciding WHO a user is.Authorization is the process of deciding WHAT they can do.
IIS (the web server) handles Authentication alongside things like Active Directory and SharePoint handles authorization.
Authentication methods include things like Anonymous, Basic, Forms, Integrated (NTML/Kerberos and Claims).
Farm
A collection of servers (web, database, index) that together make up a SharePoint Installation – aka Topology.You can do all this (web/datababase/index etc) on a single server in “Simple Installation” mode in which case you don’t need a NLB. For many small businesses this is plenty enough.
Medium sized businesses usually start with at least 2 Web Front Ends (WFE’s) and a database server.
Multinationals can have some very complex setups involving dozens
of components.
A common small SharePoint Farm topology - two WFE servers and a database server.
When you hear someone talking about ‘Scope’ this is what they mean. |
Farm
The entire installation as a whole. So if something has “Farm” level scope it applies to everything.
Web Application
An IIS Website that has been configured to run SharePoint.Can only be created in the Central Admin UI (or via the STSADM tools etc)
A Farm has one running the central administration site and 1 to many others running normal SharePoint sites.
This is generally how the main part of the URL is defined – e.g. http://somesite.yourcompany.com and http://othersite.yourcompany.com will be separate Web Applications.
This authentication method is set at the Web Application level – though you can have the same content (i.e. SharePoint site) delivered by two different web applications with two different authentication methods.
Port and network card bindings, host headers and a host of other networky stuff is set at the Web Application level – so if you want external users, for example, to have access to a site that would apply at the Web Application level (you can apply more granular
restrictions using authorization security though).
The Application Pool (the account that SharePoint runs under and the resources that it can consume) are also set at the Web Application level.
Note – Used to be known as “Virtual Server” before the days of Virtualization technologies.
Site Collection
Each web application has at least 1 Site Collection (but can have many).Each Site collection has exactly 1 ‘Top Level Site’.
The Site Collection doesn’t actually contain anything itself - that is down to the Top Level Site.
This is the level that things like the Recycle bin and Quotas are organised at.
Each site
collection can only use a single content database (though multiple site collections can us the same content database) – this has major design implications as there aremaximum recommended sizes
for a content database.
Top Level Site
A Top Level Site is a site… at the top level… see – this terminology is not that confusing after all Most of the time we can use Top Level Site and Site Collection interchangeably - in fact Microsoft do this all the time.
Each Top Level Site has zero to many sub-sites (simply called sites)
This is the lowest level that many things can be scoped to, for example only the Top Level site contains a web part Gallery so you can’t say Collection X, Site A can have a web part but Collection X, Site B can’t.
When you look at Site Settings in a top level site you will see the highlighted sections – in a sub site you will not. Both are called Sites in the UI.
Site
(aka Web’s) – these are the actual sites that you use.
A site can be a top-level site or a sub site of the top level site.
A site can also have other sites – these are called sub-sites.
Sub sites can also have other sub sites and so on.
A site can inherit its parent’s permissions or define its own – more on this complex subject in a future article.
Finally a Site! - the thing that you actually use and what most of us think as "SharePoint"
References
TechNet
– Creating Your First Web Application, Site Collection and Web Site
TechNet
– Farm topology management
相关文章推荐
- 微软宣布任命纳德拉为CEO,盖茨辞去董事长职位
- 微软新CEO 纳德拉:这个行业不推崇传统,只尊重创新
- 使用命令修改注册表键值及权限
- Microsoft Windows Vista 简体中文企业版 MVL DVD IMG 32-bit(1.9GB)
- 微软Word 2007数学插件 Microsoft Math 提供下载
- Microsoft Windows Server 2008 Beta 3VHD官方镜像下载
- Microsoft Office 2007 SP1 简体中文正式版 升级包官方下载地址
- Microsoft Access 数据库常规规格
- SharePoint 客户端对象模型 (一) ECMA Script
- 在Javascript里访问SharePoint列表数据的实现方法
- 从ASP.NET得到Microsoft Word文档的代码
- Microsoft Office 2007 全系列迅雷下载
- 使用Microsoft Ajax Minifier减小JavaScript文件大小的方法
- 未在本地计算机上注册“Microsoft.Jet.OleDb.4.0”提供程序错误的解决方法
- Microsoft SQL Server 2005 Express 远程访问设置详述,100%成功篇
- Microsoft Windows Server Code Name"Longhorn"Beta 3 正式发布! 下载
- Microsoft Search 服务无法启动 解决办法.
- Microsoft UniveRSS v0.8.0.0 微软的3D RSS阅读器 下载
- 3ff8 《sharepoint 2010云计算解决方案》使用SQL Azure 的BI 解决方案
- [手机资讯]Windows Phone 7首款机型8月25日开卖