This database is accessed for every user and administrative action. Search service application The Crawl database stores the state of the crawled data and the crawl history. Search service application The Property database stores information that is associated with the crawled data, including properties, history, and crawl Property database queues.
User Profile service The Profile database stores and manages users and associated information. It also stores information about a user's social application Profile network in addition to memberships in distribution lists and sites. User Profile service The Synchronization database stores configuration and staging data for use when profile data is being synchronized with application directory services such as Active Directory. Synchronization database SharePoint creates hive structure while SharePoint creates hive structure in windows operating system.
Folders in 12 hive Structure 1. Bin 3. Config 4. Data 5. Help 7. ISAPI 8. Logs 9. Resources Template Folders in 14 hive structure 1.
Template Policy User Code WebClients Secure Store 2. State 3. Web analytics staging 4. Web analytics 5. Search Service 6 Search reporting Application. Service administration Applica tion Crawl 7. Search Service 8. User Profile Service 9. User Profile Service Total views 5, On Slideshare 0. From embeds 0. Number of embeds Downloads 2. Shares 0. Comments 0. Likes 4. You just clipped your first slide! Clipping is a handy way to collect important slides you want to go back to later.
Now customize the name of a clipboard to store your clips. Visibility Others can see my Clipboard. Cancel Save. These resources are available in Visio. This poster describes the SharePoint, Microsoft Azure, and SharePoint Server on-premises configurations that business decision makers and solutions architects need to know about.
Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Microsoft recommends you install a download manager. Microsoft Download Manager.
Manage all your internet downloads with this easy-to-use manager. It features a simple interface with many customizable options:. Download multiple files at one time Download large files quickly and reliably Suspend active downloads and resume downloads that have failed. Yes, install Microsoft Download Manager recommended No, thanks. What happens if I don't install a download manager? Why should I install the Microsoft Download Manager? In this case, you will have to download the files individually.
You would have the opportunity to download individual files on the "Thank you for downloading" page after completing your download. For more information about the sandbox restrictions, see Sandboxed Solutions in SharePoint and its child topics and the Microsoft patterns and practices guidelines for Sandboxed Solutions.
A solution that is designed to run in the sandbox can be deployed by a farm administrator as a farm solution. It might perform better if it is, because it would run in the IIS worker process instead of the sandboxed worker process.
Not all SharePoint execution is in an IIS worker process, a sandboxed worker process, or the proxy process. The following are some examples:. The SharePoint Timer Service owstimer.
It runs under the farm account. Within the category of farm solutions , a further distinction can be made when the requested resource is an. If the requested page is what SharePoint calls an application page , the returned page is passed to the regular ASP. NET page parser; but if the requested page is what SharePoint calls a site page , the returned page is routed through a special safe mode parser.
The distinction between the two kinds of parsing is best understood in light of the distinction between the two kinds of pages. For more information about both subjects, see Pages, Parsing, and Safe Mode later in this article. Application pages cannot be included in sandboxed solutions. All pages installed as part of a sandboxed solution use safe mode parsing. Farm solutions divide into two types depending on where their assemblies are deployed and the trust level of the assemblies' execution:.
They are callable from any SharePoint web application on the farm. They have to be separately deployed to every SharePoint web application that needs to call them. Sandboxed solutions are deployed inside a SharePoint solution package. Thus, they are deployed and persisted in the site collection's content database. As noted earlier, they do not run in full trust: Instead, they run within a highly restricted CAS policy and can only call a restricted subset of the SharePoint object model.
A sandboxed solution can be accessed only in site collections to which it is deployed. When a sandboxed solution is accessed for the first time, such as when a user navigates to a page that contains a Web Part from a sandboxed solution , any assemblies in the solution are unpacked from the solution package and copied to the file system of the server that is handling the sandbox request.
Recall that the server that handles the sandbox request is not necessarily the front-end web server that is handling the initial HTTP request. The User Code Host Service can be run on back-end application servers in the farm instead. Because the sandboxed worker process cannot copy anything to the file system, the copying is done by the User Code Host Service.
The assemblies do not stay in the file cache perpetually. When the user session that accessed the assemblies finishes, the assemblies stay in the cache for only a short time, and they may be reloaded from there if another user session accesses them. Eventually, if they are not accessed, they are removed according to a proprietary algorithm that takes into account how busy the server is and how much time has gone by since the assemblies were last accessed.
If the sandboxed solution is used after that time, the assemblies are unpacked again and copied to the UCCache. Administrators, developers, and third-party code should not add, remove, or load anything from the UCCache. It should be accessed only by the SharePoint infrastructure. The SharePoint solutions architecture includes a technique by which a sandboxed solution can call custom operations that run in full trust. The technique requires that a farm solution be developed that includes one or more classes that derive from SPProxyOperation.
Each of these defines an operation that will run in full trust and can be called from sandboxed solutions by using the ExecuteRegisteredProxyOperation method. The proxy operations can return data to the sandboxed solution. Like all farm solutions , the assembly with the proxy operations can be deployed only if it is from a trusted source. Figure 6 shows how a request that accesses a sandboxed solution is processed when the sandboxed solution makes a call to a full-trust proxy.
The preceding description might give the impression that, with the hybrid technique, a farm solution and a sandboxed solution are always developed together by the same development team.
In fact, the farm solution may be developed specifically to provide certain operations to any and all sandboxed solutions that need those services, including sandboxed solutions that are developed by other teams. For example, because a sandboxed solution cannot write to the SharePoint Unified Logging Service ULS logs, a farm solution that opened proxy logging operations to sandboxed solutions would be very useful. Another hybrid technique uses client-side code to access the resources that cannot be accessed from a sandboxed solution.
For example, a sandboxed solution could include a custom site page with JavaScript that makes calls to the SharePoint JavaScript client object model. Also, a sandboxed solution could include a Web Part that hosts a Silverlight application. The latter application can make calls to the SharePoint Silverlight client object model. Both of these kinds of pages can be mergers of master and content pages and, indeed, every ASCX page that is built into SharePoint, whether it is an application page or a site page, is a combination of a master and content page.
Typical purpose : Application pages tend to be function-oriented, especially functionality that is needed by many kinds of websites within a given web application; for example, the standard form for creating a new list item is an application page. Site pages tend to be content-oriented; for example, the list-of-lists page of a standard team site.
However, exceptions to both tendencies are possible. Indeed, we currently recommend that third-party developers develop custom Web Parts, which can be added to site pages, to handle their solution's functionality whenever possible, rather than develop custom application pages. Customizablility : Site owners and other users who have appropriate permissions can customize site pages, but not application pages.
Users can also add an entirely new ASCX page to a website's Site Pages gallery, but only web application administrators can install a new application page. All of these classes derive from the ASP.
NET Page class. They can have static Web Parts, but there is little point to using a static Web Part instead of an ordinary control on an application page because end users cannot customize application pages anyway.
See later in this section for more information. A site page that has been customized, such as with Microsoft SharePoint Designer, is stored in the content database of the website for which it was customized. New site pages that have been added to the Site Pages gallery are stored just as customized pages.
Even an uncustomized site page has an entry in the content database; but whereas the entry of a customized page contains the ASPX markup that constitutes the page, the entry for an uncustomized page contains the path of the. An uncustomized page can be shared by many websites. If it is, it is referenced in each website's content database, with all the entries pointing to the same physical file. For example, every Team Site has a content database entry pointing to the default Team Site home page.
If the home page is customized on any of the sites, it is copied into the page's entry in the content database in its customized form, and the pointer to the uncustomized version is removed. Sometimes the uncustomized site page is referred to as a page template and the pages in the content database as page instances. However, remember that if the page is not customized in a particular website, the "instance" of the page is simply the database entry pointing back to the file on the file system.
Availability : An application page can be accessed from every website in the web application and is therefore shared among all the websites. But a site page is available only to a user of the website where it is deployed. Uncustomized site pages are shared by multiple websites, as noted earlier, but only websites where they have been specifically provisioned either as part of a Feature or as part of a site definition.
Parsing mode : Application pages are parsed in direct mode , which just means that they are parsed by the standard ASP. NET page parser. The first time an application page is requested, it is parsed and compiled and cached in the front-end web server's memory, where it remains until the application domain or the entire IIS host is recycled.
With every subsequent request for the page, it is served from the cache, if it is there. Uncustomized site pages are also parsed in direct mode, but customized site pages, and new pages that are added to the Site Pages gallery, are parsed in safe mode.
Safe mode processing differs from direct mode that is, from standard ASP. NET page processing in the following ways:. Only controls including Web Parts that are registered as safe in the web application's web.
Inline server-side code is not allowed in safe mode, and an error page is returned to the user if the safe mode parser finds inline code on the requested site page. Code behind that is compiled into a separate assembly is allowed, and so is embedded JavaScript.
The terms safe mode parsing , safe mode processing , and safe mode rendering are used interchangeably in SharePoint documentation. Security and performance are the motivations for the two kinds of pages, especially the difference in processing mode. One of the purposes of SharePoint is to delegate administrative control to ordinary business users instead of requiring the intervention of network administrators and IT professionals.
For this reason, users are allowed to add new pages and customize existing pages. If these users were allowed to add any control or Web Part they wanted or add any code blocks they wanted to the pages, there is a great danger that poor performing or malicious code would be added to a page.
The reason that pages that use safe mode are not compiled is that there may be thousands of pages on a SharePoint installation. If every one of them was compiled into an assembly and loaded in memory, the performance of the server would be degraded, and only recycling the application domain would remove them.
Moreover, recycling the application domain would remove all assemblies, not just the seldom-used pages. There is also a limit on the number of assemblies that can be loaded in an application domain that is imposed by the. NET Framework. The safe mode parser only creates a control tree for the page, which can be unloaded again from memory immediately after use.
On the other hand, pages that are shared, such as application pages and uncustomized site pages should be compiled on first use, because these pages are used a lot and subsequent requests for them can be handled much faster if the pages are cached as assemblies in the server memory. That is why they run in direct mode. It is possible to allow inline code, unsafe controls, or both, on selected customized site pages.
However, you should use extreme caution when you make these kinds of changes, because they cancel the security benefits of safe mode. The directory path is a "virtual path" that points to a set of files in the content database. Notice that allowing unsafe controls only enables such controls that are added in an editing tool, such as SharePoint Designer.
This might be useful if you have reason to believe that the customized page will be visited often enough to justify compiling it into a DLL cached in memory. Within the category of site pages, there are additional distinctions.
Standard site pages are wiki-enabled pages that allow inline Web Parts. Standard pages are objects of a class that derives from WikiEditPage. Web Parts pages, on the other hand, derive from WebPartPage. They have one or more Web Part zones into which Web Parts can be added, and they have no wiki-editable area.
SharePoint Server adds a third kind of site page: PublishingPage. NET, not another kind of site page. SharePoint also has a set of built-in pages that are designed for mobile devices. They do not use the ASP. There is one respect in which a SharePoint mobile page is more like a customized site page: If the page contains a mobile Web Part adapter, the adapter must be registered as a safe control or it is not rendered.
The primary data structure in SharePoint Foundation is the list. Every list belongs to a list type. Similarly, every column in a list has a field type, and every list item has a content type.
External data—that is, data from outside the SharePoint content databases—can also be shown and managed in SharePoint. Data in SharePoint Foundation is primarily stored as tables much as it is in a relational database, except that the tables are called "lists" in SharePoint lingo.
These are called content databases. However, there are some differences between relational database tables and SharePoint Foundation lists:. Data is not queried by SQL. For more information about server-side data querying, see Building Block: Queries and Views and the topic Querying from Server-side Code , along with its child topics.
You can programmatically write data to the lists using either the server object model or the LINQ to SharePoint provider. NET Data Services. For more information about client-side data querying, see Querying from Client-side Code. Directly accessing the back-end computer that is running SQL Server by using SQL queries, stored procedures, or any other method is not supported.
A list can have a column whose possible values are the values of a column on a different list. The lookup column relationship between the lists is somewhat like a foreign key relationship between two relational tables. However, the field on the target list that provides the values is not necessarily the foreign key. This column is, in effect, always the foreign key in any lookup relationship.
Lists can be joined just as tables can, but with some restrictions. There must be a lookup relation between the lists or they cannot be joined. For more information about list joins, see List Joins and Projections. A SharePoint Foundation document library is a special kind of list in which each row includes an attached document, and the other columns are data about the document, such as its author, when it was last edited, and who has it checked out.
Picture libraries are similar except that the attached file is an image file. Every list has a list type, and SharePoint Foundation includes many built-in list types that enable end-users to create the most common kinds of business and team solutions. Among these are Announcements, Tasks, and Calendar.
Developers can also create custom list types. A row in a list—that is, a list item—also has a type. These are called content types.
Each is basically a set of columns and metadata. The simplest is the built-in Item content type. All other content types are derived from Item. SharePoint Foundation includes many built-in content types, such as Event and Announcement. Developers can create custom content types. A column in a list, also known as a "field," also has a type, and it is distinct from the data type of the values that can be stored in the field. A SharePoint Foundation field type includes not only information about the underlying data type, but also information about how the data is formatted and rendered on forms, such as the forms for creating, displaying, and editing specific list items.
For example, it is the field type that determines whether a field value is entered as string or from a drop-down list of values.
Developers can create custom field types. One or more specific instances of the data source, such as a particular SAP database, are defined in the model, including connection and security information about the data source. The business entities in the data source, such as Customer or Order, are represented in the model by external content types, and the model also defines relationships between these entities.
Finally, the model defines, for each entity, a set of standard operations, called stereotyped operations , that can be performed on the entity, including create, retrieve, update, and delete operations. The models are stored in a dedicated database on the SharePoint farm computer that is running SQL Server, which is distinct from the configuration database and the content databases. This database is called the metadata store.
After a model is added to the metadata store, users can access the external data in a variety of ways. For example, in SharePoint Foundation, users can create a SharePoint list out of an external content type, such as Customer, or add a column of data from the external source to an existing list.
SharePoint Server has some BCS enhancements: It includes some built-in Web Parts for working with external data, and it enables users to search the external data.
Also, SharePoint Workspace and Microsoft Office client applications can access and display the external data directly. Finally, with SharePoint Server , users can index and search the external data sources.
0コメント