Share Point 2010 Architecture 01
Post on 24-Oct-2014
Embed Size (px)
SharePoint Server ArchitecturePublished: February 2011 Summary: Learn about the architectures of Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Server 2010, including the platform stack, the Microsoft ASP.NET-IIS integrated request pipeline, the server and client object models, and the execution process system for sandboxed solutions and farm solutions. Applies to: Microsoft SharePoint Foundation 2010 | Microsoft SharePoint Server 2010 Provided by: Ricky Kirkham, Microsoft Corporation Contents
Overview of SharePoint Foundation and SharePoint Server Architectures What Is SharePoint? SharePoint Development Platform Stack SharePoint as an ASP.NET-IIS Application SharePoint Configuration Stack SharePoint Deployment Models Process and Execution Trust Model Pages, Parsing, and Safe Mode Data Model, Data Management, and Query System Services and the Service Application Framework Site Definitions and Web Templates SharePoint Security Server Object Model in SharePoint Client Object Models in SharePoint Workflows in SharePoint Conclusion
1|P a g eAbad Net | P.O. Box100898 | Riyadh 11645 | Saudi Arabia | www.Abadnet.com.sa T: +96614918199 | M: +966545156659 | F: +96614918199
SharePoint Server Architecture
Overview of SharePoint Foundation and SharePoint Server ArchitecturesThis article provides an overview of the architectures of Microsoft SharePoint Foundation and SharePoint Server, including the platform stack, the Microsoft ASP.NET-IIS integrated request pipeline, the server and client object models, the execution process system for sandboxed solutions and farm solutions, and more.
What Is SharePoint?The use of the plural term "architectures" in the title is not a mistake. SharePoint has many architectures, partly because "architecture" has many meanings in the context of software development, but also because SharePoint itself is many thingsthings that in the past would have been distinct applications or platforms. The following is a selection of some of the most important things that SharePoint is: A portal server with delegated administration. SharePoint enables information workers (IW) who have no knowledge of website design or website administration to create, almost instantly, attractive and functioning websites. This relieves information technology (IT) departments from the burden of creating and administering the sites, and it empowers the IWs to create their own sites for teams, blogs, wikis, and other purposes. A groupware application kit. SharePoint provides a platform on which IWs can create collaboration solutions that include document libraries and workspaces, workflows, wikis, blogs, and team-oriented lists, such as Events, Announcements, and Tasks. Microsoft SharePoint Workspace (formerly Microsoft Office Groove 2007) provides an offline experience for these collaboration solutions. A workflow host. Business processes can be systematized and modeled with workflows that are triggered by associated events; for example, the addition of a document to a document library. A content management application. SharePoint Server Enterprise Content Management (ECM) features include document management, records management, and web content management. A Business Intelligence (BI) application kit. The Microsoft Business Connectivity Services (BCS) features of SharePoint enable data from non-SharePoint sources, such as a SAP installation or Oracle database, to be accessed (read/write) just as if it were an ordinary SharePoint list. The operating system of an intranet. SharePoint can provide for an intranet many of the functions that an operating system provides for a computer, including storing and copying files, hosting services, starting applications, and securing data. (This is not to imply that SharePoint can only be used on an intranet. SharePoint can also host extranet and Internet-facing solutions.) A host for services. SharePoint deployments make data available through a client object model, the REST-based Windows Communication Foundation (WCF) Data Services (formerly ADO.NET2|P a g eAbad Net | P.O. Box100898 | Riyadh 11645 | Saudi Arabia | www.Abadnet.com.sa T: +96614918199 | M: +966545156659 | F: +96614918199
This article discusses the architectures of SharePoint 2010 (with many links to more detailed information) in several senses, including the platform stack on which SharePoint runs, the configuration layers, the client and server object models, the services framework, the HTTP request pipeline, and the worker process system.
SharePoint Development Platform StackFigure 1 shows how SharePoint Foundation is built on Microsoft .NET Framework 3.5, ASP.NET, and Internet Information Services (IIS). SharePoint is also built on SQL Server, but you can install SQL Server on a dedicated server that does not have SharePoint installed, which is typical in a production farm. All of these platforms must be running on a 64-bit installation of Windows Server 2008 on the server computers. SharePoint Server, in turn, is built on SharePoint Foundation. There are two editions of SharePoint Server: Standard and Enterprise.
3|P a g eAbad Net | P.O. Box100898 | Riyadh 11645 | Saudi Arabia | www.Abadnet.com.sa T: +96614918199 | M: +966545156659 | F: +96614918199
SharePoint Server Architecture
Figure 1. The platform stack for SharePoint development
Perhaps the most noteworthy aspect of the figure is that IIS and ASP.NET are shown as a single platform. This is because SharePoint requires that IIS operate in integrated mode with ASP.NET. Hence, from a SharePoint point of view, they are effectively a single web-hosting application. For more information about this, see the next section, SharePoint as an ASP.NET-IIS Application. In Figure 1, the smaller boxes that have no fill represent some selected subparts of the platform that contains them, or on which they depend. The two thin, downward-pointing arrows indicate some specific dependencies that are shown only as examples. Many other specific dependencies are not shown in the figure. The thick, left-pointing arrows indicate that the entity on the right side accesses the entity to which the arrow points. For example, BCS accesses external databases.
4|P a g eAbad Net | P.O. Box100898 | Riyadh 11645 | Saudi Arabia | www.Abadnet.com.sa T: +96614918199 | M: +966545156659 | F: +96614918199
SharePoint Server Architecture
SharePoint as an ASP.NET-IIS ApplicationAs the High Level Object Model section later in this article shows in more detail, the highest level of organization in a SharePoint deployment, other than the farm itself, is the web application. Aweb application in SharePoint terminology is closely related to what is called a website in IIS terminology. An IIS website monitors for incoming requests through a particular port, and it checks for a particular host header or IP address, or both. Every SharePoint Foundation web application is hosted in an IIS website that has the same name as the web application. It can be helpful, especially when you are trying to see the relation between SharePoint and IIS from a high and broad perspective, to think of the SharePoint web application and its corresponding IIS website as a single entity. Nevertheless, the SharePoint web application and the IIS website are not quite the same thing (and they are represented by different classes in the SharePoint object model: theSPWebApplication class and the SPIisWebSite class). For one thing, although there is usually a one-to-one relation between SharePoint web applications and IIS websites, this is not always the case. It is possible to extend a SharePoint web application to multiple IIS websites, although that is not a common design. Figure 2 shows the IIS websites and application pools on a SharePoint Foundation front-end web server.
Figure 2. IIS Manager on a SharePoint Foundation front-end web server
5|P a g eAbad Net | P.O. Box100898 | Riyadh 11645 | Saudi Arabia | www.Abadnet.com.sa T: +96614918199 | M: +966545156659 | F: +96614918199
SharePoint Server ArchitectureJust as in any application that is built on the ASP.NET-IIS integrated pipeline, when a front-end web server receives a request from a client for a page or other resource in a SharePoint site, the request is passed through a pipeline of units that process the request. This processing includes authenticating the user, verifying the users authorization, building the response, sending the response, and finally, logging the request. For more information about the integrated pipeline, see ASP.NET Integration with IIS 7. The response to any request is produced by an HTTP handler object. Requests are assigned to one or another HTTP handler object (or