office2010培训资料 (1)

An approach to solution architecture for SharePoint Products and Technologies Date published:September 2008Summary:When you work with Windows® SharePoint® Services 3.0 and Microsoft® Office SharePoint Server 2007 deployments, you must ensure that the architecture of the deployment is intuitive to your users, will scale and grow with your business over time, and importantly, that it performs well. The first stage of architecting a scalable solution is to design and deploy a server farm. However, you must also design appropriate information architecture for the solutions and information deployed on that server farm. By architecting the information structure and solution deployment, you can improve the efficiency of your Windows SharePoint Services 3.0 or Office SharePoint Server 2007 deployments.This paper describes one way to design your information architecture by using metadata, site columns, content types, and managed properties. It also explains the feature and solution architectures, site definitions, and site templates.You can view a video of a presentation that covers this material at For alternative guidance for designing SharePoint Products and Technologies solutions, see Site and solution planning ( in the Office SharePoint Server technical library. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.© 2008 Microsoft Corporation. All rights reserved.Microsoft, SharePoint, and Windows are trademarks of the Microsoft group of companies.All other trademarks are property of their respective owners. Table of ContentsINFORMATION ARCHITECTURE1Site Columns1Best Practices for Site Columns1Content Types2Best Practices for Content Types2Managed Properties4Best Practices for Managed Properties4Content Databases5Content Database Architecture5Hardware Considerations6Configuring Content Databases for DBAs6SOLUTION ARCHITECTURE7Web Applications, Site Collections, and Sites7Server Farms7Web Applications8Content Databases8Site Collections8Sites9Variation Labels9Feature Architecture10What Is a Feature?10What Are Feature Scopes?10What Are Feature Dependencies11Hidden Features11Feature-site Template Associations12Installing and Uninstalling Features12How to Install Features12Scripted Feature Installs12How to Uninstall a Feature Completely12Activating and Deactivating Features13Activating and Deactivating Features by Using the User Interface13Activating and Deactivating Features by Using the Command Prompt14Solutions and Deployment14What Is a Solution?14Where to Deploy a Solution15How to Synchronize Solutions in a Farm16Site Definitions16What Is a Site Definition?16What Do Site Definitions Consist of?16Installing a Site Definition17Site Templates18What Is a Site Template?18What Do Site Templates Consist of?18Installing a Site Template18编号：时间：2021年x月x日书山有路勤为径，学海无涯苦作舟页码：第19页 共22页Information ArchitectureYou must ensure that you design your information architecture before you deploy your environment; this will save you subsequent time and effort. The key to developing robust and appropriate information architectures is to research and understand the business data and business intelligence requirements of your users.When you plan your information architecture, you will find it useful to perform usage analysis to establish which sites and subsites receive the most traffic. You can analyze usage in your organization's existing deployments by examining the log files generated by Internet Information Services (IIS). There are numerous third-party tools available that generate usage reports based on these logs. If your users are currently working in a Windows SharePoint Services 2.0 environment, by using the Central Administration Web Application, you can activate Usage Analysis Processing. This gathers information from the IIS logs and generates a usage report for a specified site. You can use this information in conjunction with user surveys to establish what content is accessed most frequently; this will enable you to determine which content needs to be most easily accessible. You can also use user surveys to develop a clear plan for developing metadata that best describes content.Site ColumnsTo develop accurate and pertinent metadata, you must first analyze user requirements. The key aim of taxonomy and metadata development is to provide targeted information to your users. SharePoint Products and Technologies provide site columns that provide a reusable template for controlling metadata. By using site columns, you can manage the structure and availability of content for your users. You can use site columns to gather metadata for content and to maintain a consistent use of metadata across the sites in your site collection. When you define a site column, you can associate it with any content type or list. For example, you can specify that any document that a user uploads to a specific list must have an author. To do this, create a custom site column that describes the type of data required, such as author, and then associate that site column with the list of your choice. Note that this is done through the configuration options for the list or library in question rather than from the site column. The site columns you specify for your content types are used as part of the index process and can help you to provide relevant search results.Best Practices for Site ColumnsWhen you develop metadata for your sites, you must determine the exact requirements of your users. You should work with your users to determine what data they use on a regular basis and how they describe this data, this will enable you to make the data more discoverable for your users. Custom site columns provide the administrator with a reusable solution that can be applied to lists or libraries in a site collection. To determine accurate site column specifications, you must examine the data that your users work with and perform interviews to gain a better understanding of what descriptive information is important to them. When you develop site columns, you must remember that they each represent an attribute that a user will manage for a particular content type. By defining site columns that can be applied across multiple lists, you can ensure that a particular type of metadata can be enforced across your deployment.For example, after examining user requirements, you may determine that all documents are generated for specific customers. From your user interviews, you may also determine that your users want to be able to locate all files associated with a particular customer. Finally, you may determine that your organization has a limited number of customers; the organization produces data for Litware Inc., AdventureWorks, and Fourth Coffee.In this situation, you can develop a site column called Customer. By using the gathered information, you can determine that the Customer site column must be a multiple-choice column that enables users to select one of the three clients. You can also specify that the column is a required field when users add their content. By prescribing the options available to your users, you can ensure that content added to a site that has been produced for Litware Inc will have the same Customer property value. If you specify the site column type as a Single line of text rather than a Choice, users can enter incorrect values. For example, a document added with a Customer property of LitwareIncorporated is not assigned the same Customer value as one added with a Customer property of Litware Inc.The advantage of producing site columns is that you can apply them across the lists in your site or site collection. Additionally, you can subsequently modify site columns, and the changes that you make can be passed down to the lists that inherit that particular site column. In the example of the Customer site column, if your organization acquires a new customer, such as Contoso, you can modify the site column so that the new customer name is displayed in the list of choices. However, note that although the options change for new content when you modify an existing option, you must change the content your users have already stored on an individual basis.Note: When you create a site column, you are given the option of adding the column to an existing group or creating your own groups. We recommend that you create your own groupings. By defining groups of site columns that have been identifiably defined for a specific group, such as a department or product type, you provide an easily understood structure for your metadata assignment.The following list details the factors that you must consider when you develop site columns:· Who is the information aimed at?· What type of data do users work with?· Can users already find the information they require?· How do users work with content?· What functionality do users require?· What information requirements does your organization have?Content TypesYou use content types to store multiple types of documents in a single list, each with its own specific associated metadata. For example, you can create a different content type for each different type of presentation document, such as technical, sales, or training presentations. Each content type has site columns associated with it that determine the metadata stored for that particular content type. The use of content types enables you to maintain a consistent use of metadata for particular types of documents across your sites and lists.Best Practices for Content TypesMany organizations require multiple types of content. Windows SharePoint Services 3.0 and Office SharePoint Server 2007 provide content types that enable administrators to architect a flexible solution for defining metadata, and default templates, specific to a type of content. It is also possible to associate workflows and policies with content types. By linking your workflows to a content type, your organization can track and ensure that users are following the appropriate business-driven content processes.Content types are independent of document type; you use specific metadata to define and organize your content types. The following table illustrates how you can define different content types for your organization.Document TypeContent TypeMetadataOffice Word DocumentProposalTitleCreated byCustomerProductDesign SpecificationTitleCreated byCustomerProductVersionMicrosoft Office PowerPoint® PresentationSales PresentationTitleCreated byCustomerDelivery dateTechnical PresentationTitleCreated byCustomerDelivery dateDepartmentDelivered byWhen you examine the existing information architecture in your organization, you must evaluate the types of document that your users use on a regular basis. You can create content types that reflect the type of information with which users work; this helps users to understand and locate information. By defining distinct content types with distinct compulsory or required metadata fields, you can enforce a strict structure on the properties exposed by certain documents. You must also observe and model the stages of common business processes; this will enable you to develop workflows that represent the real-life processes your organization follows. Planning for workflows enables you to automate processes that previously had to be done by hand; this increases business efficiency.Note: For more information on workflow development, see Configuring Forms Services and Excel Services (You must design content types carefully before you deploy them into your environment. Ensure that your content types fit with your overall information architecture; this includes the site or site collection they are designed for and the way in which your users will navigate to them. Creating inappropriate content types will result in user confusion, inability to locate relevant information, and a lack of pertinent structure throughout your sites and lists. A poorly designed content type may be too generalized to provide any relevant content information. For example, if you create a content type of Acceptance Letter that is a Microsoft Office Word document and has only Title and Created by properties, you reduce the chances of users locating that item through a property value search. However, if you create a content type of Acceptance Letter that is an OfficeWord document and has Interviewee, Interviewer, Created by, Date created, and Department properties, you produce a far more locatable content type.When you develop content types, you must consider the following issues:· What document types do your users deal with?· What site columns have you defined for user content?· How will your users locate content?· Where does this content reside in the overall site structure in terms of business, organizational, or process information?· What business requirements can you address by defining content types?Managed PropertiesYou use managed properties to manage the organization of content metadata. Managed properties are only made available through Office SharePoint Server 2007; organizations that plan to deploy a Windows SharePoint Services 3.0 environment will not be able to take advantage of them.A managed property is essentially a property that you map to one or many crawled properties. Crawled properties are discovered by the search index service component when crawling content. You use managed properties to improve the search experience; they enable users to perform a search for the managed property that returns results for many content items that have a property to which the managed property is mapped.Best Practices for Managed PropertiesMany organizations maintain multiple types of content spread across multiple sources. Office SharePoint Server 2007 enables administrators to index content from various sources such as the SharePoint sites in a farm or the Business Data Catalog. In many situations, these different sources may each have their own metadata associated with content. For example, suppose your organization stores documents in two separate content sources. One source uses a column called Creator and the other source uses a column called Writer. Now suppose you want to perform a search for any document that was created or written by John Peoples. If you do not create a managed property, you must perform two property searches.QueryResultsCreator: John PeoplesAny document from the first content source with a Creator property that matches John Peoples.Writer: John PeoplesAny document from the second content source with a Creator property that matches John Peoples.However, managed properties enable you to consolidate these two queries into a single query. To do this, you create a single managed property such as Author. You then map this property to the existing crawled properties Creator and Writer.Note: A property will only appear in the crawled property list when it has been used at least once. The property will be added to the crawled property list when the index process next runs.Each time you create a new managed property or you modify an existing one a full crawl is required in order to “populate” managed property to values of mapped crawl properties,. At the end of the full crawl, you can then perform property searches based on that property that return results from both sources.By using managed properties, you can improve the search experience for your users; this will increase productivity and reduce time wasted on switching between queries. You must design managed properties before you deploy them into your environment. If you create inappropriate managed properties, users will be unable to locate relevant information quickly. If you plan and design managed properties badly, searches will yield inaccurate or no search results. For example, if you create a managed property of Date Created but you map this to the crawled properties CreationDate and ModifiedDate, your search result will contain items that were created on a certain date and also those that were modified on that date.When you develop managed properties, you must consider the following issues:· What content sources are available to users?· How does content from one source relate to content from another?· What properties do they share and will they map easily?· Will there be a benefit to the user if you create a managed property?Content DatabasesContent Database ArchitectureWhen you plan for deployment of content databases, you must decide how to create them. You can create databases automatically by using the SharePoint Products and Technologies Configuration Wizard or by using the Central Administration interface. However, your organization may have a security policy that specifies that a Database Administrator (DBA) must perform all database creation. In this situation, the DBA must create them separately from the deployment team.The following steps illustrate how to create content databases by using the Central Administration interface.1. In Central administration, click Application Management. 2. Under SharePoint Web Application Management, click Content databases. 3. When the Manage Content Databases page has loaded, click Add a content database.4. Enter the details for your content database, and then click OK.To create content databases, the SharePoint Products and Technologies configuration wizard initially creates a database for the Central Administration Service. The configuration wizard then creates one database per Web application on your farm.There is a common misconception that there exists a hard limit of 50GB on the size of a content database. This misconception may have arisen from guidance given for SharePoint Portal Server (SPS) 2003 and Windows SharePoint Services 2.0 whereby it was suggested that content databases remained less than or equal to 50GB due to the absence of a convenient content recovery scenario. For example, if a document was deleted in an SPS 2003 or Windows SharePoint Services 2.0 environment, the only way to recover the document was to restore a content database from backup. In Office SharePoint Server 2007 these factors can be mitigated due to added content recovery facilities, such as the recycle bin,