Microsoft Official Course 5061A Implementing Microsoft Office SharePoint Server 2007

Course 5061A: Implementing Microsoft® Office SharePoint® Server 2007 Information in this document, including URL and o...

Author: Microsoft

14 downloads 796 Views 18MB Size Report

This content was uploaded by our users and we assume good faith they have the permission to share this book. If you own the copyright to this book and it is wrongfully on our website, we offer a simple DMCA procedure to remove your content from our site. Start by pressing the button below!
Report copyright / DMCA form

DOWNLOAD PDF

Course 5061A: Implementing Microsoft® Office SharePoint® Server 2007

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. 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. The names of manufacturers, products, or URLs are provided for informational purposes only and Microsoft makes no representations and warranties, either expressed, implied, or statutory, regarding these manufacturers or the use of the products with any Microsoft technologies. The inclusion of a manufacturer or product does not imply endorsement of Microsoft of the manufacturer or product. Links may be provided to third party sites. Such sites are not under the control of Microsoft and Microsoft is not respons ble for the contents of any linked site or any link contained in a linked site, or any changes or updates to such sites. Microsoft is not responsible for webcasting or any other form of transmission received from any linked site. Microsoft is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement of Microsoft of the site or the products contained therein. © 2007 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, BizTalk, Excel, ForeFront, FrontPage, InfoPath, Internet Explorer, MSN, OneNote, Outlook, PowerPoint, SharePoint, SQL Server, Visual Basic, Visual C#, Visual Studio, Windows, Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Product Number: 5061AT Part Number: X13-38679 Released: 03/2007

Table of Contents Introduction Introduction ........................................................................................................................................i Course Materials............................................................................................................................... ii Microsoft Learning Product Types................................................................................................... iv Microsoft Learning ........................................................................................................................... vi Microsoft Certification Program ...................................................................................................... vii Facilities........................................................................................................................................... xi About This Course .......................................................................................................................... xii Prerequisites.................................................................................................................................. xiv Course Outline................................................................................................................................ xv Course Outline (continued)............................................................................................................ xvi Virtual Machine Environment........................................................................................................ xvii Demonstration: Using Microsoft Virtual PC ................................................................................... xix

Module 1: Overview of Microsoft® Office SharePoint® Server 2007 Overview....................................................................................................................................... 1-1 Lesson 1: Introduction to Office SharePoint Server 2007 ............................................................ 1-2 Lesson 2: Integrating Office SharePoint Server 2007 in the Enterprise..................................... 1-11 Lesson 3: Office SharePoint Server 2007 Architecture.............................................................. 1-25 Lab: Exploring Office SharePoint Server 2007........................................................................... 1-32 Lab Shutdown............................................................................................................................. 1-34 Review ........................................................................................................................................ 1-35

Module 2: Planning and Designing for Microsoft® Office SharePoint® Server 2007 Solutions Overview....................................................................................................................................... 2-1 Lesson 1: Preparing for an Office SharePoint Server 2007 Implementation ............................... 2-2 Lesson 2: Planning and Designing for Non-Functional Requirements...................................... 2-11 Lab: Documenting Non-Functional Requirements for Office SharePoint Server 2007 Solutions ............................................................................................................................ 2-23 Lab Shutdown............................................................................................................................. 2-28 Review ........................................................................................................................................ 2-29

Module 3: Deploying Microsoft® Office SharePoint® Server 2007 Overview....................................................................................................................................... 3-1 Lesson 1: Office SharePoint Server 2007 Deployment Architecture ........................................... 3-2 Lesson 2: Installing Office SharePoint Server 2007..................................................................... 3-8 Lesson 3: Managing Shared Service Providers ......................................................................... 3-15 Lab: Planning for and Deploying Office SharePoint Server 2007 .............................................. 3-19 Lab Shutdown............................................................................................................................. 3-23 Review ........................................................................................................................................ 3-24

Module 4: Administering Microsoft® Office SharePoint® Server 2007 Overview....................................................................................................................................... 4-1 Lesson 1: Creating Office SharePoint Server 2007 Sites ........................................................... 4-2 Lesson 2: Managing Office SharePoint Server 2007 Features................................................. 4-13 Lab: Managing Sites and Features............................................................................................. 4-20 Lab Shutdown............................................................................................................................. 4-24 Review ........................................................................................................................................ 4-25

Module 5: Implementing Portal Solutions Overview....................................................................................................................................... 5-1 Lesson 1: Creating Portal Sites .................................................................................................... 5-2 Lesson 2: Implementing Collaborative Features ........................................................................ 5-10 Lesson 3: Implementing User Profiles and Audiences............................................................... 5-16 Lab: Implementing Collaborative Features in Portal Sites ......................................................... 5-23 Lab Shutdown............................................................................................................................. 5-29 Review ........................................................................................................................................ 5-30

Module 6: Implementing Content Management Solutions Overview....................................................................................................................................... 6-1 Lesson 1: Overview of Content Management .............................................................................. 6-2 Discussion: Content Management and Enterprise Content Management ................................... 6-3 Lesson 2: Managing Documents and Content with Office SharePoint Server 2007.................. 6-14 Lesson 3: Implementing Content Management Processes........................................................ 6-25 Lab: Implementing Content Management Sites and Processes ................................................ 6-31 Lesson 4: Implementing Content Management Policies ............................................................ 6-38 Lab: Implementing Auditing and Policies ................................................................................... 6-47 Lab Shutdown............................................................................................................................. 6-55 Review ........................................................................................................................................ 6-56

Module 7: Implementing Business Intelligence Solutions Overview....................................................................................................................................... 7-1 Lesson 1: Configuring and Incorporating Business Data Catalog Applications into Portal Solutions .............................................................................................................................. 7-2 Lesson 2: Implementing Microsoft Office SharePoint Server 2007 Excel Services..................... 7-8 Lesson 3: Implementing Business Intelligence Dashboards...................................................... 7-13 Lesson 4: Creating Report Center Web Sites ............................................................................ 7-19 Lesson 5: Implementing Microsoft Office SharePoint Server 2007 Forms Server..................... 7-24 Lab: Implementing Business Intelligence Solutions with Microsoft Office SharePoint Server 2007 ....................................................................................................................... 7-27 Lab Shutdown............................................................................................................................. 7-40 Review ........................................................................................................................................ 7-41

Module 8: Implementing Search and Indexing Overview....................................................................................................................................... 8-1 Lesson 1: Office SharePoint Server 2007 Search and Indexing.................................................. 8-2 Lesson 2: Implementing Search ................................................................................................... 8-7 Lab: Implementing Search and Indexing.................................................................................... 8-19 Lab Shutdown............................................................................................................................. 8-25 Review ........................................................................................................................................ 8-26

Module 9: Maintaining and Optimizing Microsoft® Office SharePoint® Server 2007 Overview....................................................................................................................................... 9-1 Lesson 1: Implementing Office SharePoint Server 2007 Backup and Restore ........................... 9-2 Lab: Backing Up and Restoring Office SharePoint Server 2007 Configurations and Data........ 9-10 Lesson 2: Monitoring Office SharePoint Server 2007 ................................................................ 9-15 Lab: Monitoring Office SharePoint Server 2007 Solutions......................................................... 9-27 Lab Shutdown............................................................................................................................. 9-30 Review ........................................................................................................................................ 9-31 Course Evaluation ...................................................................................................................... 9-33

Index ...............................................................................................................1-10

Module 1: Overview of Microsoft® Office SharePoint® Server 2007 Table of Contents Overview 1-1 Lesson 1: Introduction to Office SharePoint Server 2007 1-2 Lesson 2: Integrating Office SharePoint Server 2007 in the Enterprise 1-11 Lesson 3: Office SharePoint Server 2007 Architecture 1-25 Lab: Exploring Office SharePoint Server 2007 1-32 Lab Shutdown 1-34 Review 1-35

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. 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. The names of manufacturers, products, or URLs are provided for informational purposes only and Microsoft makes no representations and warranties, either expressed, implied, or statutory, regarding these manufacturers or the use of the products with any Microsoft technologies. The inclusion of a manufacturer or product does not imply endorsement of Microsoft of the manufacturer or product. Links are provided to third party sites. Such sites are not under the control of Microsoft and Microsoft is not responsible for the contents of any linked site or any link contained in a linked site, or any changes or updates to such sites. Microsoft is not responsible for Webcasting or any other form of transmission received from any linked site. Microsoft is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement of Microsoft of the site or the products contained therein. 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. © 2007 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, BizTa k, Excel, ForeFront, FrontPage, InfoPath, Internet Explorer, MSN, OneNote, Outlook, PowerPoint, SharePoint, SQL Server, Visual Basic, Visual C#, Visual Studio, Windows, Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Module 1: Overview of Microsoft® Office SharePoint® Server 2007

1-1

Overview

Objectives After completing this module, you will be able to: •

Describe Microsoft® Office SharePoint® Server 2007.

•

Explain how Office SharePoint Server 2007 integrates with many different products and systems in the enterprise.

•

Describe the Office SharePoint Server 2007 architecture.

Microsoft Office SharePoint Server 2007 enables organizations to build a variety of business solutions. Office SharePoint Server 2007 is built on the foundations of Microsoft® Windows® SharePoint® Services 3.0 and ASP.NET version 2.0 and provides an extensible solution framework that enables organizations to build specific solutions quickly and efficiently.

1-2


Lesson 1: Introduction to Office SharePoint Server 2007

Objectives After completing this lesson, you will be able to: •

Describe the types of solutions that Office SharePoint Server 2007 is designed to provide.

•

Explain the design goals for Office SharePoint Server 2007.

•

List the main components of Office SharePoint Server 2007.

•

Describe the additional administrative functions that Office SharePoint Server 2007 adds over Windows SharePoint Services.

Office SharePoint Server 2007 has been designed to provide strategic benefits for organizations. It enables organizations to build a variety of applications, such as portal, business intelligence, and content management solutions. Office SharePoint Server 2007 provides new capabilities over the Windows SharePoint Services platform on which it is based. You must plan for and manage these new capabilities when you implement solutions based on Office SharePoint Server 2007 solutions.


1-3

What Is Office SharePoint Server 2007 for?

Introduction Office SharePoint Server 2007 is designed to help you build a variety of solutions, quickly and efficiently.

Types of Solutions Office SharePoint Server 2007 is based on Windows SharePoint Services and you can use it to build the following broad types of solutions: •

Collaborative solutions, where information workers can use the latest technologies to work together as teams, regardless of their individual locations.

•

Portal solutions that provide access to relevant information for users when they need it.

•

Content management solutions (including Web content management solutions, document management solutions, and records management solutions) that streamline the processes of publishing and protecting information.

•

Search solutions that enable information workers to find data that is stored in various locations in the enterprise.

•

Forms solutions that gather business information in a streamlined and efficient manner.

•

Business intelligence solutions that empower decision-makers to assess business information and make informed decisions.

1-4


In addition, Office SharePoint Server 2007 provides many features that you can use to manage business processes across these broad types of solutions.


1-5

Office SharePoint Server 2007 Design Goals

Introduction Office SharePoint Server 2007 has been designed with various goals in mind. These goals are concerned with improving the efficiency with which information workers and business managers can perform their jobs.

Design Goals For collaborative solutions, the design goals include the provision of a collaborativeoriented base framework, interoperability with communication technologies, and extensibility features that enable information workers to collaborate in intuitive and efficient ways. For portal solutions, the goals include the provision of information in a timely and context-sensitive manner that ensures information workers have the tools and information they need to undertake the tasks that their roles demand. The goals for content management solutions include the provision of robust and flexible frameworks that help organizations manage every aspect of their content processes and life cycles, including managing documents, records, and Web-based content. The search goals include ensuring information workers have access to appropriate information, including access to content and people that will help them perform their tasks in an efficient manner. The powerful forms features were designed to streamline, consolidate, and automate data capture processes, so that business processes can run smoothly and efficiently.

1-6


For business intelligence solutions, the goals include the provision of features and technologies that enable business decision-makers to make well-informed choices based on robust data analysis. All of these functional goals are supported by a solution framework that enables customers, partners, and independent software vendors to build specific solutions that meet the business and technical requirements of diverse organizations.

Intranet, Extranet, and Internet Single Architecture In addition to the functional goals, Office SharePoint Server 2007 was designed to provide a single platform that can be used for intranets, extranets, and Internet presence sites. Organizations can now implement solutions on a single architecture to satisfy the various requirements of these different scenarios. The next lesson describes how to integrate Office SharePoint Server 2007 with Microsoft® Internet Security and Acceleration (ISA) Server 2006 to provide scalable and secure extranet and Internet solutions.


1-7

Office SharePoint Server 2007 Components

Introduction Office SharePoint Server 2007 solutions typically include many features that the underlying Windows SharePoint Services 3.0 platform provides. For example, lists, document libraries, links, contacts, events, notifications, and calendars often provide the foundation for portals, collaboration, content management, and business intelligence solutions. The ability to access all these information types through Web browsers and on mobile devices helps to ensure the usability and manageability of these solutions. Office SharePoint Server 2007 builds on the Windows SharePoint Services foundation by providing two key sets of components that help organizations build powerful and specific business solutions: The Office SharePoint Server 2007 Shared Service Provider, and Office SharePoint Server 2007 Features.

Office SharePoint Server 2007 Shared Service Provider The Shared Service Provider performs intensive tasks that can be shared among different sites and site collections, even across members of a server farm. The Shared Service Provider is independent of any particular solution or Web site, although the functionality can be configured differently for specific Web applications. The Office SharePoint Server 2007 Shared Service Provider includes: •

Enterprise-level search capabilities that: •

Crawl content sources, including SharePoint sites, Business Data Catalogs (BDC), file systems, and other information stores.

1-8


•

•

•

Build and maintain indexes on those content sources.

•

Run queries on those indexes and return search results.

Microsoft Office Excel® services that: •

Enable the configuration of trusted locations for Excel workbooks.

•

Enable programmatic access to Microsoft Excel Calculation Services.

User management capabilities that store and manage: •

User profiles.

•

My Sites.

•

Membership data.

•

Colleague data.

Office SharePoint Server 2007 Features To enable organizations to build specific solutions, Office SharePoint Server 2007 provides sets of features that focus on particular areas of functionality. Features can be activated to add functionality to a solution, or they can be deactivated to prevent that functionality from being used. Additionally, features can have different scopes, depending on how they are developed. Their scope can apply at the server farm level, the Web application level, the site collection level, or the site level. Office SharePoint Server 2007 includes the following features that build on the Windows SharePoint Services platform to provide functionality for different types of solutions: •

•

•

BDC functionality and Web Parts that: •

Use delegation to access data stores securely.

•

Retrieve data from those data stores.

•

Display the retrieved data to information workers.

Content publishing functionality and workflows that: •

Streamline and manage authoring, editing, and publishing processes.

•

Ensure information is managed in a way that conforms to policies and regulations.

•

Enable multilingual publishing scenarios.

Business intelligence functionality and Web Parts that: •

Display charts and spreadsheet data.

•

Display Key Performance Indicators (KPIs).


1-9

What Administrative Considerations Does Office SharePoint Server 2007 Introduce?

Introduction The basic model of developing solutions with Office SharePoint Server 2007 is to assemble and configure features and services so that they meet the requirements of specific solutions. In some cases, additional custom development may also be included. This model makes it easier for developers to build powerful solutions. However, it also introduces considerations that system administrators and implementers must take into account. The powerful, scalable architecture of Office SharePoint Server 2007 server farms provides many technical benefits, but it also introduces administrative tasks.

Server Farm Administration Each member of a server farm must be kept synchronized with all the other members in terms of the Office SharePoint Server 2007 Shared Service Provider, Office SharePoint Server 2007 Features, and Web Parts.

Shared Service Provider Administration Administrators also require knowledge about how the powerful Office SharePoint Server 2007 Shared Service Provider functions. For example, administrators will need to configure the Shared Service Provider correctly, monitor performance and usage, and optimize the provider if necessary. The application integration capabilities of Office SharePoint Server 2007 also introduce administrative and design features for specific solutions. Although the tools Office

1-10


SharePoint Server 2007 provides are straightforward to use, it is important that administrators and implementers understand best practices when integrating disparate enterprise systems. The more powerful search facilities that Office SharePoint Server 2007 provides also need to be administered correctly. Implementing a poorly designed search-and-indexing strategy might not provide adequate or appropriate search results, or might degrade performance of Office SharePoint Server 2007 solutions if the operations place too heavy a load on the physical servers.

Business Critical Issues Additionally, the nature of Office SharePoint Server 2007 solutions means that they will quickly become critical systems for organizations. Therefore, it is particularly important that Office SharePoint Server 2007 solutions provide a high level of availability and are maintained to ensure information is not lost in the event of hardware failures. They must also be optimized so that solution performance is acceptable.


1-11

Lesson 2: Integrating Office SharePoint Server 2007 in the Enterprise

Objectives After completing this lesson, you will be able to describe the following regarding how Office SharePoint Server 2007 integrates with many different products and systems in the enterprise: •

The close integration between Office SharePoint Server 2007 and 2007 Microsoft Office system client applications.

•

How Office SharePoint Server 2007 uses Windows Workflow Foundation (WF) services.

•

How Office SharePoint Server 2007 integrates with Microsoft Exchange Server 2007.

•

How ISA Server 2006 can publish and protect extranet and Internet sites based on Office SharePoint Server 2007.

•

How Office SharePoint Server 2007 can use Active Directory® directory services.

1-12


Office SharePoint Server 2007 provides collaborative enterprise solutions. Typically, enterprise-wide collaborative solutions include features and functionality from other products, in addition to using the collaborative features of Office SharePoint Server 2007. It is important, therefore, to understand how Office SharePoint Server 2007 integrates with various enterprise products.


1-13

Office SharePoint Server 2007 and Microsoft Office 2007 Client Applications

Introduction Office SharePoint Server 2007 is part of the 2007 Microsoft Office suite of products. The 2007 Office release includes client applications, such as Microsoft Office Word® 2007, Microsoft Office Excel 2007, and Microsoft Office Outlook® 2007. The client applications and Office SharePoint Server 2007 have been designed to seamlessly work together.

File Formats Microsoft Office applications support new file formats based on open XML standards. In general, there are two types of file formats: those that include macros and those that do not include macros. For example, Office Word 2007 documents that contain macros can be saved as .docm files, whereas Office Word 2007 documents that do not contain macros can be saved as .docx files. The open standards enable Office SharePoint Server 2007 to manipulate Office files seamlessly—Office SharePoint Server 2007 was developed to handle the file formats. This makes it easy to use and reuse content (such as text, charts, calculated values, slides, and other objects) that are stored in document library files. Additionally, Office SharePoint Server 2007 supports Information Rights Management (IRM) features for document libraries. Along with the ability to handle Office file formats, this enables Office files to be stored in document libraries in an unprotected state

1-14


(so that indexing and search features will work) but ensures that IRM attributes are applied to those files when information workers access or download them.

Office Outlook 2007 Increasingly, information workers use Microsoft Office Outlook® 2007 as their preferred application for collaboration with other team members. Office Outlook 2007 and Office SharePoint Server 2007 have been designed to work together to help collaboration. Full two-way synchronization is now possible, so SharePoint contact management, task management, e-mail management, and event and meeting management is now fully integrated into the Office Outlook 2007 client application. Furthermore, information workers can use Office Outlook 2007 to take lists and document libraries offline. They can work on offline list data and documents and then synchronize with Office SharePoint Server 2007 when they next connect to the server.

Excel Services One of the new features of Office SharePoint Server 2007 is a shared service called Excel Services. Excel Services enable an administrator to specify trusted locations for Office Excel 2007 workbooks, so that information workers can view and access charts, data, and other objects directly from Office SharePoint Server 2007 Web pages. Developers can also create applications that programmatically access Office Excel 2007 calculation services. Overall, the integration between Office SharePoint Server 2007 and Office Excel 2007 functionality provides the foundation for many types of business intelligence solutions in addition to providing information workers and business decision-makers with user interfaces in Web pages that are similar to those in Office Excel 2007.

Office Forms Server 2007 The 2003 release of Microsoft Office introduced the Microsoft Office InfoPath® client application into the Office suite of products. Now, however, a new product called Microsoft Office Forms Server 2007 is included in the 2007 Office release. This new product provides server-side forms management capabilities and is integrated closely with Office SharePoint Server 2007. For example, server-side InfoPath forms can now be rendered and used in Web browsers and can also include data-driven features, such as accessing data from BDC applications.

Office SharePoint Designer 2007 Microsoft Office SharePoint Designer 2007 is a new application that replaces Microsoft Office FrontPage® 2003. Designers and developers can use Office SharePoint Designer 2007 to open an Office SharePoint Server 2007 site for editing. It includes features that provide designers with fine control over page layouts and appearances. Additionally, designers and developers can use Office SharePoint Designer 2007 to add and configure custom controls and Web Parts and to incorporate advanced features such as custom workflows and data-driven forms into SharePoint sites.


1-15

Office Project Server 2007 Microsoft Office Project Server 2007 can be integrated with the core platform and advanced components of Office SharePoint Server 2007. Because Project Server 2007 and Office SharePoint Server 2007 are built on the common Microsoft SharePoint Products and Technologies platform, implementers and developers can use a common set of development tools and techniques to integrate and extend all of the products. Office Project Server 2007 includes the Office SharePoint Server 2007 core and administrative services, which enable you to implement a comprehensive project management solution. For example, Office Project Server 2007 can import a task list from Office SharePoint Server 2007 and convert it to a proposals and operations project. The project can then be accessed by Microsoft Office Project Web Access to provide simple timesheets, tasks, and resource management. Furthermore, Office Project Server 2007 can convert the proposals and operations project into a full project-management solution for your business that includes schedule recalculations, cost management, and comprehensive reports. As another example, Office Project Server 2007 can make use of Office SharePoint Server 2007 list-based KPIs in project-management solutions.

Microsoft Office Access 2007 You can integrate Microsoft Office SharePoint Server 2007 and Office Access 2007 in various ways. You can move a database from Office Access 2007 to a SharePoint site by using the Move to SharePoint Site Wizard. The wizard creates lists on the SharePoint site that are linked as tables in your database. Office Access 2007 also creates a new front-end application that includes forms, reports, and the new linked tables that were exported. After the SharePoint lists are created, users can work with the lists on the SharePoint site or in the linked tables in Office Access 2007. Users can also open Access forms and reports from a SharePoint site, and they can open lists in rich Access views. Access forms, reports, and datasheets can appear alongside other views on a SharePoint site. When you choose an Access view, Office Access 2007 starts and opens the requested form, report, or datasheet. This makes it easy for users to run a rich Access report on a SharePoint site without having to manually start Office Access 2007. Users can also create databases from SharePoint lists by opening a SharePoint list in Office Access 2007. If the database does not already exist, Office Access 2007 will create it, and then create a set of forms and reports based on the list. Office Access 2007 also provides offline access to SharePoint lists. Users can work on the offline data in Office Access 2007, and then synchronize their changes when they reconnect with the SharePoint site at a later time.

1-16


Microsoft Office OneNote 2007 Users can share Microsoft Office OneNote® information with others in a read-only form by publishing their notes to Office SharePoint Server 2007. They can publish notes in a variety of formats, such as a PDF file, a single-file Web page, a separate OneNote section, or a Word document. Users can then post published files to a SharePoint site.


1-17

Office SharePoint Server 2007 and Windows Workflow Foundation

Introduction Before the release of Office SharePoint Server 2007, workflows were often considered the missing piece in collaborative solutions. Office SharePoint Server 2007 now integrates closely with Windows Workflow Foundation to provide powerful workflow functionality for collaborative solutions.

Document Routing Workflows Office SharePoint Server 2007 solutions include document routing and approval workflows, by default. Information workers can use the Web user interface for SharePoint sites to define workflows for documents.

SharePoint Designer Workflows Often, workflows that are more complex than the built-in approval and document routing ones will be required in collaborative solutions. For example, typical collaborative workflows will include e-mail notification steps, task assignment steps, and metadata manipulation steps. Designers and information workers can create custom workflows that include all of these step types, along with custom logic, by using Office SharePoint Designer 2007. You do not need to write custom code to create custom workflows with Office SharePoint Designer 2007—you can create them by stepping through the SharePoint Designer 2007 workflow wizards.

1-18


Visual Studio Workflows Some collaborative solutions will require more complex workflow logic and features than you can create by using Office SharePoint Designer 2007. For example, your solution might require a workflow to manage nonlinear, state-machine states for documents or other SharePoint objects. Developers can use Microsoft Visual Studio® 2005 and Windows Workflow Foundation to create complex workflows. You can then incorporate them into your Office SharePoint Server 2007 solutions to provide powerful, managed collaborative workflows.


1-19

Office SharePoint Server 2007, Microsoft Exchange Server 2007, and Microsoft Office Outlook 2007

Introduction E-mails are an intrinsic part of most collaborative solutions. The close integration of Office SharePoint Server 2007 with Microsoft Exchange Server 2007 and Microsoft Office Outlook 2007 now means that using e-mails in collaborative solutions is seamless for information workers.

Alerts and Notifications Exchange Server 2007 is the e-mail server of choice in many organizations. Office SharePoint Server 2007 collaborative solutions can make use of Exchange Server 2007 e-mail facilities for all of its collaborative e-mail requirements, such as notifying users when they have been added as a site member and sending alerts when new information has been added, deleted, or updated.

Sending SharePoint Lists as E-Mails All SharePoint-based lists and libraries can now be identified by an e-mail address or alias. This enables information workers to send an e-mail to a list or library. Office SharePoint Server 2007 lists and libraries store the received e-mail in the list or library, which provides an extremely efficient way for information workers to disseminate information from their mailbox to other team members.

1-20


Managed Mail Folders Records management features provide one of the powerful new capabilities of Office SharePoint Server 2007. Records management is used to control official versions, retention, and expiration of documents and other enterprise information. Often, recordstype data is contained within e-mails. Office SharePoint Server 2007 and Exchange Server 2007 work together to provide managed mail folders to help records managers and compliance officers manage the e-mail in individual mailboxes. They can define a set of standard folders, each with an explicit business purpose, in which individual employees can file their e-mail. These folders can be deployed to individual information workers based on their roles within the organization, so that people who fill equivalent roles across a company can have similar top-level filing structures in their mailboxes.

Shared Calendars Additional integration between Office SharePoint Server 2007 and Exchange Server 2007 is provided by shared calendars. Effectively, information workers can view and manipulate shared calendars that are managed by Exchange Server 2007 from within Office SharePoint Server 2007 solutions. This helps information workers collaborate by providing information about other team members’ availability and the availability of other resources, such as meeting rooms and projectors.

Shared Tasks Information workers often rely on the tasks features of Office Outlook 2007 in their collaborative roles. Those tasks can be stored and managed by Exchange Server 2007. The full synchronization between Office SharePoint Server 2007, Office Outlook 2007, and Exchange Server 2007 means that information workers do not have to deal with duplicate (or triplicate) lists of tasks.

Shared Contacts Information workers often use the contact features of Office Outlook 2007 in their collaborative roles. Those contacts can be stored and managed by Exchange Server 2007. The full synchronization between Office SharePoint Server 2007, Office Outlook 2007, and Exchange Server 2007 means that information workers do not have to deal with duplicate (or triplicate) lists of contacts.

LinkAccess Exchange Server 2007 provides features for publishing and enabling access to Office SharePoint Server 2007 documents from within e-mails. When an information worker receives a link to such a document while working remotely using Microsoft Office Outlook Web Access, Exchange Server 2007 uses a feature named LinkAccess to retrieve and display the document. LinkAccess uses remote procedure calls over HTTPS to access Office SharePoint Server 2007 documents, thereby eliminating the need for a virtual private network.


1-21

Office SharePoint Server 2007 and Microsoft ISA Server 2006

Introduction Many organizations use Office SharePoint Server 2007 as a basis for their intranet solutions. However, with remote working models becoming more common, and with increasing requirements for collaboration with external business partners, extending intranets into extranets is becoming more common. Creating extranets adds additional concerns, such as security and ensuring that links to internal resources are rendered correctly. The integration of Office SharePoint Server 2007 with Microsoft ISA Server 2006 addresses these concerns.

Security for Extranets You can use ISA Server 2006 to publish Office SharePoint Server 2007 solutions as extranets over the infrastructure of the Internet. ISA Server 2006 acts as a firewall and authentication point to help secure your extranet from malicious users. Additionally, you can use ISA Server 2006 to implement Secure Sockets Layer (SSL) encryption for all communication on the Office SharePoint Server 2007 extranet. Furthermore, ISA Server 2006 provides authentication and security management features, such as forms authentication and delegation that help you to identify users and ensure that they have appropriate access to resources in the extranet.

Link Translation When you publish an Office SharePoint Server 2007 solution with ISA Server 2006, you need to manage how links are rendered in users’ Web browsers. Links in SharePoint sites

1-22


will often refer to internal Web sites and other resources by using computer names or internal Internet Protocol (IP) addresses. Computer names and internal IP addresses will not typically be accessible by Web browsers using the published extranet. ISA Server 2006, however, can help you manage these scenarios by providing link translation as part of the publishing process. For example, it can replace IP addresses or computer names that reference hyperlinks with fully qualified addresses that are accessible in the extranet solutions.


1-23

Office SharePoint Server 2007 and Microsoft Active Directory Directory Services

Introduction Collaborative solutions often concern information about people and business. A lot of useful information about employees is typically stored in Active Directory stores, such as security group memberships, e-mail addresses, contact details, and organizational structures. The integration between Office SharePoint Server 2007 and Active Directory enables this type of useful information to be used in collaborative solutions.

Active Directory Users and Groups Part of implementing collaborative solutions involves defining how users are authenticated and authorized. Office SharePoint Server 2007 includes an Active Directory authentication provider that can be used to authenticate users based on their user credentials and group membership. Additionally, Office SharePoint Server 2007 includes a pluggable provider architecture that enables users to be authenticated by other lightweight directory access protocol (LDAP) directories. Within Office SharePoint Server 2007 solutions, you can also use Active Directory users and group membership as the basis for authorization.

1-24


Active Directory User Profiles Business data about people, such as job titles, departments, e-mail addresses, contact details, and organizational structures, is increasingly used in collaborative solutions. Information workers often need to find people who can help them as much as they need to find facts and figures. This type of useful, person-oriented information is typically stored in Active Directory. Office SharePoint Server 2007 provides new and enhanced profile features that integrate with Active Directory, such as the ability to define Active Directory as the profile store, the ability to import profile data from Active Directory, and the ability to synchronize Office SharePoint Server 2007 profile information with Active Directory. Furthermore, Office SharePoint Server 2007 audiences can be defined by using Active Directory-based properties.

Active Directory Contact Objects for E-mail Enabled Lists One of the new features of Office SharePoint Server 2007 is that it provides the capability for users to send e-mails to SharePoint lists. You can use the SharePoint Central Administration application to enable this capability. When you configure the incoming e-mail settings, a new Active Directory contact object is created. You must ensure, therefore, that the application pool identity for the SharePoint Central Administration application has permission to create the contact object in Active Directory.


1-25

Lesson 3: Office SharePoint Server 2007 Architecture

Objectives After completing this lesson, you will be able to describe the following aspects of the Office SharePoint Server 2007 architecture: •

The logical components of Office SharePoint Server 2007.

•

How the logical components of Office SharePoint Server 2007 map to physical components.

•

The administrative tools and architecture for Office SharePoint Server 2007.

Before you implement Office SharePoint Server 2007 solutions, you must understand the logical and physical architecture of Office SharePoint Server 2007.

1-26


Office SharePoint Server 2007 Logical Architecture

Introduction Office SharePoint Server 2007 solutions are built on a hierarchy of logical components, each of which provides specific functionality.

Office SharePoint Server 2007 Logical Units Office SharePoint Server 2007 consists of the following logical units: •

Server farm. This high-level unit is characterized by a number of Web and application servers that are logically grouped together and share a common configuration database.

•

Web application. This unit provides Web server functionality. An Office SharePoint Server 2007 Web application corresponds to an Internet Information Services (IIS) Web site.

•

Site collection. This unit defines the settings and the context for grouping together a number of sites and subsites. A site collection is similar to a traditional top-level virtual directory in IIS, although there will not be an IIS mapping to the virtual directory.

•

Site. This unit provides an entry point into a specific solution or set of functionality. A site is similar to a subfolder in a traditional top-level virtual directory in IIS, although there will not be an IIS mapping to the virtual directory.

•

Feature. This unit provides specific functionality and data as part of a larger solution. A feature can contain data, metadata, and functionality.


1-27

Office SharePoint Server 2007 Features Although features are typically used within sites and site collections, they can have different scopes. For example, depending on their scope, features can be deployed and activated (or deactivated) at the site level, the site collection level, the Web application level, or the server farm level.

1-28


Demonstration: Office SharePoint Server 2007 Feature Architecture

The instructor will provide a demonstration to show the logical relationship between features and the Office SharePoint Server 2007 logical architecture.


1-29

Office SharePoint Server 2007 Physical Architecture

Introduction Before you implement the logical features for an Office SharePoint Server 2007 solution, you must understand how the logical units map to physical components in the Office SharePoint Server 2007 architecture.

Office SharePoint Server 2007 Physical Units The physical architecture of Office SharePoint Server 2007 consists of the following: •

Database server. This component stores and manages configuration data, site data and metadata, and index databases. All the members of a server farm must use the same database server, because it stores and manages the configuration database that controls the settings for the server farm.

•

Application server. This component performs application services. For example, you can have one application server in your server farm manage search and indexing and another manage user profile imports and synchronization.

•

Web front-end server. This component manages requests for Office SharePoint Server 2007 solutions. It consists of a number of virtual directories that provide application features, such as application management pages, templates, themes, and registered components such as Web Part assemblies.

1-30


Office SharePoint Server 2007 Administrative Architecture

Introduction Administration of a server farm or stand-alone server involves adding to, editing, or deleting data that is stored in the configuration database. You do not need to edit the data directly; instead you can use Office SharePoint Server 2007 administrative tools.

Three-Tier Administration Office SharePoint Server 2007 administrative settings are stored in a Microsoft SQL Server™ 2005 database. You can use the SharePoint Central Administration tool to access and modify the settings in the configuration database. The administrative Web site is based on a three-tier physical architecture that consists of Web pages and .NET Framework objects that access the database to retrieve, add, edit, or delete configuration data. The administrative model is also based on a three-tier logical architecture: •

Tier 1 encompasses all of the administrative features and functionality for centrally managing the server farm. Tier 1 administrative tasks are typically performed by an organization's IT administrators and can include a wide range of tasks, such as farmlevel resource management tasks, farm-level status checks and monitoring, and farmlevel security configurations. For example, a tier 1 administrator might be responsible for creating new Web applications and site collections, managing incoming and outgoing e-mail settings for the farm, and managing server farm topology.


1-31

•

Tier 2 encompasses all of the administrative features and functionality for managing shared services across a server farm. Tier 2 administrative tasks are typically performed by a business unit IT administrator and can include a wide range of management tasks at the service level, such as configuring search, indexing, or usage reporting.

•

Tier 3 encompasses all of the administrative features and functionality for managing sites within a server farm. Tier 3 administrative tasks are typically performed by a business unit site administrator and can include a wide range of site-specific management tasks, such as Web Part management, access management, and content management. For example, a tier 3 administrator might be responsible for creating a new list on a site, configuring access permissions for users, and modifying site hierarchy.

Administration Tools The main administrative tool is the SharePoint Central Administration Web site. This tool is accessible from the Start menu on computers with Windows SharePoint Services and Office SharePoint Server 2007 installed. This tool is a shortcut to the URL of the aforementioned administrative Web site. Therefore, you can also navigate to the URL of the administrative Web site from any computer that has network access to the Web server. Office SharePoint Server 2007 and Windows SharePoint Services also provide an administrative command-line utility called stsadm.exe. This utility provides similar functionality to the administrative Web site, but in command-line format. You can use stsadm.exe to create batch files for automating administrative tasks. Additionally, stsadm.exe provides additional commands that the administrative Web site does not have. For example, the following command changes the alert frequency to one minute from the default five minutes by using the setproperty operation: stsadm -o setproperty -propertyname job-immediate-alerts -url http://litwareportal -propertyvalue "every 1 minutes between 0 and 59"

1-32


Lab: Exploring Office SharePoint Server 2007

After completing this lab, you will be able to: •

Explore and review a default installation of Office SharePoint Server 2007.

Estimated time to complete this lab: 15 minutes

Introduction In this lab, you will explore a default installation of Office SharePoint Server 2007.

Lab Setup Before you begin the lab, you must: •

Start the 5061A_LON-DC-01-01 virtual machine.

•

Log on to the virtual machine with the user name Administrator and the password Pa$$w0rd.


1-33

Exercise 1: Reviewing an Office SharePoint Server 2007 Implementation In this exercise, you will explore the features of a default Office SharePoint Server 2007 site. The principal tasks for this exercise are as follows:

f

•

Explore the default home page.

•

Explore the Document Center.

Explore the default home page

Tasks 1.

2.

Supporting information

Review the home page.

Sign-in as a different user.

f

On the Start menu, point to All Programs, and then click Internet Explorer.

•

In the Address bar, type http://litwareportal and then press ENTER. After a few seconds, the home page appears.

•

Notice that the site includes a number of different tabs. This site design is the default layout for an Office SharePoint Server 2007 site.

•

Notice the links on the left side of the page. These links are provided by the default layout in an Office SharePoint Server 2007 site.

•

Near the top of the page, click Welcome LITWAREINC\Administrator, and then click Sign in as Different User.

•

In the Connect to LITWAREPORTAL.LITWAREINC.COM dialog box, in the User name box, type LITWAREINC\Student

•

In the Password box, type Pa$$w0rd and then click OK.

•

Notice that the welcome message near the top of the page reads Welcome Student.

•

Near the top of the page, click Welcome Student, and then click Sign in as Different User.

•

In the Connect to LITWAREPORTAL.LITWAREINC.COM dialog box, in the User name box, type LITWAREINC\Administrator

•


Explore the Document Center

Tasks 1.

•

Review the Document Center tab.

Supporting information •

Click the Document Center tab.

•

On the left side of the page, click

1-34


Tasks

Supporting information Documents. The document library is displayed.

2.

Create a new document.

•

Click New.

•

In the Microsoft Internet Explorer dialog box, click OK. A new document is opened in Microsoft Word.

•

In the new document, type My first document.

•

Click Save.

•

In the Save As dialog box, notice that the location is the Documents library in the Office SharePoint Server 2007 site.

•

Click Save.

•

In the Microsoft Office Word dialog box, click OK.

•


•

In the Edit Offline dialog box, click OK.

•

Close Microsoft Word. The Microsoft Office Word dialog box appears.

•

Click Yes.

•

In the Check In dialog box, select 1.0 Major version (Publish).

•

In the Version Comments box, type First published version and then click OK.

•

Notice that the Document Center page is refreshed, and that your new document appears.

•

Close Internet Explorer.

Lab Shutdown After you complete the lab, you must shut down the 5061A_LON-DC-01-01 virtual machine and discard any changes. Important: If the Close dialog box appears, ensure that Turn off and delete changes is selected and then click OK.


1-35

Review

You have now completed this module and can: •

Describe Office SharePoint Server 2007.

•

Explain how Office SharePoint Server 2007 integrates with many different products and systems in the enterprise.

•

Describe the Office SharePoint Server 2007 architecture.

Module 2: Planning and Designing for Microsoft® Office SharePoint® Server 2007 Solutions Table of Contents Overview 2-1 Lesson 1: Preparing for an Office SharePoint Server 2007 Implementation 2-2 Lesson 2: Planning and Designing for Non-Functional Requirements 2-11 Lab: Documenting Non-Functional Requirements for Office SharePoint Server 2007 Solutions 2-23 Lab Shutdown 2-28 Review 2-29

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, email addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. 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. The names of manufacturers, products, or URLs are provided for informational purposes only and Microsoft makes no representations and warranties, either expressed, implied, or statutory, regarding these manufacturers or the use of the products with any Microsoft technologies. The inclusion of a manufacturer or product does not imply endorsement of Microsoft of the manufacturer or product. Links are provided to third party sites. Such sites are not under the control of Microsoft and Microsoft is not responsible for the contents of any linked site or any link contained in a linked site, or any changes or updates to such sites. Microsoft is not responsible for Webcasting or any other form of transmission received from any linked site. Microsoft is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement of Microsoft of the site or the products contained therein. 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. © 2007 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, BizTa k, Excel, ForeFront, FrontPage, InfoPath, Internet Explorer, MSN, OneNote, Outlook, PowerPoint, SharePoint, SQL Server, Visual Basic, Visual C#, Visual Studio, Windows, Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Module 2: Planning and Designing for Microsoft® Office SharePoint® Server 2007 Solutions

2-1

Overview


Prepare and plan for implementing Microsoft® Office SharePoint® Server 2007 solutions.

•

Describe typical non-functional requirements for Office SharePoint Server 2007based solutions and how to consider these requirements at the design stage.

Office SharePoint Server 2007 allows organizations to build a variety of business solutions. You must plan and design each of these solutions if you are to maximize the potential of Office SharePoint Server 2007 in your organization. This module introduces you to the wider planning and design methodologies specified in the Microsoft Solutions Framework (MSF), including the Team Model. The module also introduces you to the recommended practices based on the planning and design worksheets available in the Office SharePoint Server 2007 Resource Kit.

2-2


Lesson 1: Preparing for an Office SharePoint Server 2007 Implementation

Objectives After completing this lesson, you will be able to: describe the following aspects of Office SharePoint Server 2007: •

High-level methodology and processes.

•

All design and implementation team roles.

•

How to interpret functional requirements and define non-functional requirements.

Office SharePoint Server 2007 provides a flexible, scalable platform for a wide range of business applications. It is a robust platform that enables agile development because of the speed with which you can develop and deploy solutions. It is important to use a consistent and robust methodology for planning and design that identifies both business and technical requirements.


2-3

Discussion: Planning and Designing Office SharePoint Server 2007 Implementations

Introduction The instructor will now lead a class discussion. Please ensure that you participate in the discussion, when appropriate, to ensure that you and the other class members benefit fully from the discussion.

Discussion Points You can use the following discussion points to help start the discussion. Feel free to discuss other related points as they arise. •

Share experiences from planning and design exercises when deploying SharePointbased or other solutions.

•

Did you use the MSF methodology?

•

What role did you take in planning and designing the solution?

•

Describe the roles of others in the planning and design team.

•

Who identified the functional and non-functional elements of the solutions specification?

•

What lessons did you learn from the experiences?

2-4


Overview of Design and Development Processes and Methodologies

Introduction Design and development of Office SharePoint Server 2007 solutions should adhere to the MSF methodology. MSF is an iterative, milestone-driven development model. You can align continual refinement with predefined milestones or goals. These goals act as assessment or transition points.

MSF Phases MSF employs a phased approach to project development that includes the following five phases: •

Envisioning

•

Planning

•

Developing

•

Stabilizing

•

Deploying

Each of these phases is associated with a completion milestone. Dependent tasks cannot be undertaken until the appropriate milestone has been achieved. The major milestones include the following: •

Vision/scope approval


•

Project plan approval

•

Scope completion

•

Release readiness approval

•

Deployment completion

2-5

Within each phase, depending on the type or complexity of the project, you can have interim milestones. The use of a phased approach enables you to complete and approve high-level business definition and design tasks before you engage in any development. Many solution-development projects fail because of poorly specified business requirements during the envisioning phase; the application works from a technical perspective but the solution does not deliver what the business requested. By matching each phase with an assessed or approved milestone, you can mitigate against such a situation in your projects. The major milestones are points in the project life cycle when the entire team synchronizes the milestone deliverables with each other and with the customer’s expectations. At this time, the customer, stakeholders, and team formally review the project deliverables. When the team and the customer agree that the major milestone has been successfully achieved, the project can proceed.

Iteration The use of milestones does not negate rapid or early development. MSF provides an iterative model for the development of code, documents, designs, plans, and other deliverables. This means that you produce versioned deliverables, which can allow you to begin development on an agreed specification.

Office SharePoint Server 2007 and MSF Two of the benefits of Office SharePoint Server are how quickly applications can be developed, deployed and reused, and how end-users can create their own custom solutions by using site-provisioning processes and Office SharePoint Designer 2007. Therefore, development and deployment of Office SharePoint Server 2007 solutions is slightly different from traditional projects. You should adhere to MSF-style guidelines at the planning and design stage. However, after you deploy Office SharePoint Server 2007, you must be aware of some fundamental differences in how sites and solutions are created. The self-service nature, and the ability of power users to develop site features, means that Office SharePoint Server 2007 can quickly and efficiently satisfy the requirements of business users, as compared with traditional solutions.

2-6


Overview of the Team Model Roles

Introduction An important component in the delivery of a successful project is to ensure that you have the correct team working together. MSF identifies the necessary resources in the Team Model, which specifies the roles within a project team, each role’s accountability, and the team’s shared responsibilities. Team decisions must reflect a sound understanding of the business goals and the technological capabilities of the development platform. This means that in addition to a single project vision, the team must contain a broad base of skills.

Team Roles The roles within the project team reflect the MSF methodology and the Microsoft Operations Framework (MOF) team model. Each role brings specific skills to the team that address requirements of the five phases. This does not mean that there are only five roles to match the five phases. In an area such as development, the team will need test and end-user experience skills in addition to traditional developer skills. Project team roles include: •

Product management

•

Program management

•

Development

•

Test

•

User experience


•

2-7

Release management Note: MOF is a complementary framework developed by Microsoft to help organizations manage teams and processes for operational systems.

Each of these groups, also referred to as team clusters, may contain numerous members, especially the development, test, user experience, and release management clusters. Members of these groups may not necessarily be the direct customers of the solution. However, you should ensure that managers and other organizational leaders who understand the requirements of the business processes are fully involved throughout the project, especially during the envisioning phase. Without their insight it will be impossible to identify the functional specifications for the solution.

Team Role Responsibilities While all roles have responsibilities within each of the phases, each role is the primary driver within a specific phase. The following list associates the milestones for each phase with the role that acts as the primary driver: •

Vision/scope approval─product management.

•

Project plan approval─program management.

•

Scope completion─development and user experience.

•

Release readiness approval─testing and release management.

•

Deployment completion─release management.

2-8


Guidelines for Interpreting Functional Specifications

Introduction A business requirements specification document is a composite of functional and nonfunctional solution requirements. Few business users would realize that they have to specify, or require, non-functional elements in their solution. This is because business users, and often project sponsors, primarily focus on what the solution will do, rather than the environment within which it should operate. Even where they are concerned with non-functional features, such as governance, they may regard these as functions. To interpret a functional specification, you must understand what you should define as a functional requirement and what you should define as a non-functional requirement.

Functional Specifications A function describes an aspect of a solution with which a user will knowingly interact. This will include elements such as: •

Business functions

•

User interfaces

•

Programming interfaces

•

Capabilities

•

Interaction

•

Appearance

•

Interoperability


•

Navigation

•

Content architecture

2-9

Many of these functional requirements apply to various types of applications, not just Office SharePoint Server 2007 solutions. However, content architecture may require special attention, because traditional Web applications may not include this type of requirement. It is important that the key stakeholders and the design team specify the content architecture requirements very thoroughly. For example, they should determine the types of content that should be stored at each of the following levels: •

Site collection

•

Site

•

Page

•

List and document library

•

List and document library folders and subfolders

•

Documents

•

List items

The content structure will affect information worker efficiency, system manageability, scalability, security design, content functionality, and search functionality.

Non-functional Specifications Non-functional requirements are often underlying technological or business requirements. For a business-critical solution, it is essential that you provide business continuity in your design. Business users may assume that the solution will always be available. You must identify the level of business continuity that the business user must have. You may do this by questioning the user about how long the business could continue to perform at an acceptable level if the solution were unavailable. Based on the aggregated user responses, you can then identify an infrastructure platform that can support the business availability requirements. Other non-functional elements may include: •

Capacity

•

Performance

•

Security

Note: For more information about specific non-functional requirements for Office SharePoint Server 2007, see Module 9, “Maintaining and Optimizing Microsoft Office SharePoint Server 2007.”

Security is an important business focus. You must identify the security requirements for a solution within your requirements documentation. This is particularly important when

2-10


you are dealing with remote and mobile users, where authentication and authorization issues arise. Note: You should challenge all assumptions for non-functional requirements. A user may state that a solution must be available at all times. However, an expensive clustered hardware solution may not be justified on the grounds of business continuity.

Planning Worksheets Microsoft provides a series of planning and design worksheets to support you in identifying the functional and non-functional requirements for an Office SharePoint Server 2007 implementation. These form a library of templates designed to help designers capture specification information during the envisioning phase of an Office SharePoint Server 2007 project. You can use the worksheets in conjunction with your existing specification-development tools or templates. This is not an exhaustive set of documents but a growing body of documentation that has been developed from proven practices for developing solutions based on SharePoint Products and Technologies.


2-11

Lesson 2: Planning and Designing for Non-Functional Requirements

Objectives When you implement an Office SharePoint Server 2007 solution, you must understand the non-functional requirements and options for the platform. The collaborative nature of Office SharePoint Server 2007, together with the distributed nature of its users, means that you will have to select security mechanisms, define operational metrics, and identify interoperability requirements from your business requirements specification. After completing this lesson, you will be able to describe typical non-functional requirements for Office SharePoint Server 2007-based solutions and how to consider these requirements at the design stage. You will be able to: •

Describe the authentication scenarios and providers for Office SharePoint Server 2007.

•

Describe the security characteristics, requirements, and issues for Office SharePoint Server 2007 solutions.

•

Describe the operational metrics, requirements, and issues for Office SharePoint Server 2007 solutions.

•

Describe the interoperability requirements and issues for Office SharePoint Server 2007 solutions.

2-12


Guidelines for Implementing Office SharePoint Server 2007 Authentication

Choosing an Authentication Method Authentication defines the mechanism by which you allow users to access Office SharePoint Server 2007 solutions. The most important issue is that you select the appropriate approach for your business security requirements. Office SharePoint Server 2007 supports “pluggable,” non-Windows® based authentication, which may be a benefit in some environments. The broad range of authentication options available for Office SharePoint Server 2007 provides ongoing flexibility and security for your implementation. You can specify the authentication mechanism by editing the Web.config file for the Office SharePoint Server 2007 Web application. NTLM (Windows-integrated) authentication. Windows NTLM authentication is a secure, proven protocol that is based on encrypting user names and passwords before sending them over the network. NTLM is commonly referred to as challenge-response. NTLM authentication is the default authentication mechanism for Office SharePoint Server 2007. Kerberos (Windows-Integrated) authentication. The Kerberos protocol is based on ticketing and is also available within Office SharePoint Server 2007. With the Kerberos protocol, a user must first provide a valid user name and password to an authentication server before it can grant the user a ticket. The ticket can then be used on the network to request other network resources. To use this, both the client and server must have a


2-13

trusted connection to the domain Key Distribution Center. Also, both the client and server must be compatible with the Active Directory® directory service. In addition to its increased security, the Kerberos protocol offers some performance benefits, because it caches client information after authentication; this may be of benefit in large server farm environments. The Kerberos protocol can also delegate the client credentials from the Office SharePoint Server 2007 front-end Web server to other backend servers, such as Microsoft SQL Server™. Anonymous authentication. You can enable anonymous access to allow users to view pages anonymously. Most Internet Web sites allow browsers to view pages anonymously. Anonymous access must be granted at the Web application level. If anonymous access is allowed for the Web application then site administrators can decide whether to: •

Grant anonymous access to a site.

•

Grant anonymous access only to lists and libraries.

•

Block anonymous access to a site altogether.

Anonymous access relies on the anonymous user account on the Web server. This account is created and maintained by Microsoft Internet Information Services (IIS), not the Office SharePoint Server 2007 site. By default in IIS, the anonymous user account is IUSR_ComputerName. When you enable anonymous access, you are, in effect, granting that account access to the SharePoint site. Allowing access to a site, or to lists and libraries, grants View Items permission to the anonymous user account. Even with View Items permission, however, there are restrictions to what anonymous users can do. Anonymous users cannot: •

Use the Office SharePoint Designer 2007 remote procedure call.

•

Upload or edit documents in document libraries, including wiki libraries.

Basic authentication. Basic authentication is part of the HTTP 1.0 protocol specification, which means that it works with most browsers. Basic authentication provides a simple mechanism for transmitting user IDs and passwords from a browser to a Web server. The user security information is transmitted as plain text, which may represent an unacceptable level of security for some implementations. However, you can protect user credentials by implementing Secure Sockets Layer (SSL) encryption for scenarios where basic authentication must be used. ASP.NET forms authentication. Office SharePoint Server 2007 supports nonWindows-based identity systems by integrating with the pluggable ASP.NET forms authentication system. For example, developers can work with the Microsoft SQL Server provider to store and manage user credentials in a custom SQL Server database. Additionally, Office SharePoint Server 2007 ships with a forms-based LDAP authentication provider.

2-14


Protecting Credentials by using SSL SSL offers a data-encryption method that is particularly suited to granular channel protection for a particular application, rather than for all applications and services running on a computer. SSL, which supports authentication by means of public key certificates, must be implemented by individual applications. The major advantages of SSL are its maturity as a standard and its support by a wide variety of server and client computers. It may be used in association with other authentication options, such as basic authentication, to provide a more secure system of authentication.

Mixed Authentication Methods You can use a mix of authentication models, which enables you to implement intranets, extranets, and Internet solutions. For example, you might authenticate office-based users by using the Kerberos protocol to take advantage of delegated authentication with downstream services, but use NTLM for remote workers to allow them to access solutions over the Internet from non-trusted client computers. You could also implement anonymous authentication so that content consumers can access the published versions of your content over the Internet. Note: To implement mixed authentication, you will typically require a developer to create a custom authentication provider. For example, a developer could create a single provider that enables a user to be authenticated by using either Windows authentication or a custom SQL Server authentication process.


2-15

Guidelines for Implementing Office SharePoint Server 2007 Authorization and Security

Introduction Security for site collections and sites is controlled by assigning permissions to users and groups for a specific entity (such as site, list, or item). When you plan for site security, you need to decide to what degree you want to control permissions for individual entities and how you want to categorize and manage your users.

Planning for Security An important part of the security model that Office SharePoint Server 2007 implements is that site owners, project managers, and other solution administrators have the ability to manage permissions and users. Unlike traditional systems, the burden of creating users and groups and setting their permissions is not placed solely on the server administrator or IT department. However, you will still need to plan security requirements before you implement Office SharePoint Server 2007. The following planning and design worksheets address a range of security requirements: •

Policy worksheet.

•

Site and content security worksheet.

•

Users and user types worksheet.

•

Custom permission levels and groups worksheet (Microsoft Windows SharePoint Services).

2-16


•

People, profiles, and policies worksheet.

Designing Authorization Office SharePoint Server 2007 includes the following objects that enable you to implement authorization for Office SharePoint Server 2007 solutions: •

Individual user permissions. This grants individual users permissions to perform specific actions.

•

Permission level. This is a predefined set of permissions that grants users permission to perform a set of related actions. The default permission levels are: Limited Access, Read, Contribute, Design, and Full Control.

•

User. This describes a user account that can be authenticated through the authentication method used for the server. You can add individual users and directly assign a permission level to each user; users do not have to be part of a group. For reasons of efficiency, you should assign permissions to groups rather than users.

•

Group. This describes the permissions granted to number of related users (a group). Office SharePoint Server 2007 groups are assigned a default permission level, but the permission level for any group can be changed as needed. Anyone assigned a permission level that includes the Create Groups permission (included in the Full Control permission level by default) can create custom Office SharePoint Server 2007 groups.

•

Securable object. This describes when a user or group is assigned a permission level for a specific securable object, such as a site, list, library, folder, document, or item. By default, permissions for a list, library, folder, document, or item are inherited from the parent site, list, or library. However, if you assign a user a permission level for a particular securable object that includes the Manage Permissions permission, that user can change the permissions for that securable object. By default, permissions are initially controlled at the site level, with lists and libraries inheriting the site permissions. You can use list-, folder-, and item-level permissions to further control which users can view or interact with the site content. You can return to inheriting permissions from a parent list, the site as a whole, or a parent site at any time.

Identifying Security Issues Office SharePoint Server 2007 enables people to share information about themselves and their work to encourage collaboration, build and promote expertise, and target relevant content to the people who need to see it. You can tailor content to each person in any organization and enable administrators to set policies to protect privacy. Office SharePoint Server 2007 provides a set of configurable policies so that Profile Services administrators can make the appropriate information available to meet the needs of the organization. Policies may vary between shared service providers, so you must


2-17

review collaboration needs across the organization to develop a plan for implementing an appropriate mix of policies. Every personalization feature and property exposed in user profiles and personal sites has a recommended default policy that can be customized based on the needs of each organization.

Microsoft Forefront Security for SharePoint Microsoft Forefront Security for SharePoint (formerly called Antigen for SharePoint) provides application-level security that is specifically designed to protect Office SharePoint Server 2007 implementations. The increasing number of attacks on applications means that defenses should extend beyond traditional network and host operating system attacks, providing a “defense-in-depth” model. Microsoft Forefront anti-malicious software and secure access products are specially tuned to integrate with and protect the Office SharePoint Server 2007 applications. This integration provides critical protection against new generations of application-specific attacks.

2-18


Guidelines for Defining Operational Metrics

Introduction Any application implementation is judged by its performance, availability, manageability, and scalability. You must establish realistic metrics by which you can assess these elements of your solution. You can only create these based on a sound knowledge of the solution and its user base.

Performance Managing solution performance is based on an assessment of hardware, communications infrastructure, and application design. No user likes an application that performs slowly, but you need to assess whether an instant response is a business requirement or just an understandable user preference. Servicing the performance needs of your users will be influenced by: •

User types, such as local, remote, and mobile users.

•

Operation types, such as complex and simple operations.

•

Usage, such as constant, frequent, or occasional use.

You can combine this information with an understanding of peak activity periods such as period ends or morning versus afternoon to model a peak workload requirement. You should also assess database options such as indexing and query management, because database performance will have a significant effect on overall solution performance.


2-19

Note: For more information about performance requirements for Office SharePoint Server 2007, see Module 9, “Maintaining and Optimizing Microsoft Office SharePoint Server 2007.”

Scalability A number of performance variables also affect scalability, including hardware and communications. You can develop a solution based on a server farm environment if you want the scalability of a multitier topology. However, to understand the requirements for future scalability, you must have a thorough understanding of the solution you are implementing. As with performance planning, you need to know the user types, operation types, and usage, but in this case you need to also know the changes that will occur and the impact they may have on capacity and throughput. The Estimate Data Capacity Requirements worksheet helps you identify a baseline and then estimate data volume changes based on the following: •

Number of documents

•

Number of versions

•

Average document size

You should use these volume projections to remodel you performance estimates to establish potential throughput and performance models for your increased solution workload. Note: For more information about scalability requirements for Office SharePoint Server 2007, see Module 3, “Deploying Microsoft Office SharePoint Server 2007.”

Availability Availability planning for Office SharePoint Server 2007 must exist within the wider business continuity plan for your organization. However, you can identify specific elements of Office SharePoint Server 2007 by using the Availability Plan worksheet. Solution availability must reflect the business requirements established during your planning phase. You must design redundancy options across the range of server roles, such as Web, application, or database, to fit your environment. Note: For more information about availability requirements for Office SharePoint Server 2007, see Module 3, “Deploying Microsoft Office SharePoint Server 2007.”

Manageability Management and maintenance of your Web server farm requires you to establish acceptable levels of performance and availability. Once these are in place, you can develop service-level metrics against which you will be assessed. Each maintenance and management regime is different. What successful implementations have in common is a well-documented set of protocols related to management, often based on MOF or the IT

2-20


Infrastructure Library standards. Again, these should sit within your wider IT management strategy. The Site Maintenance Plan worksheet provides a document within which you can describe your overall maintenance plan. You can also notate features specific to Office SharePoint Server 2007, such as use of quotas to manage site collection storage sizes or application of site-use confirmation and deletion to manage unused site collections. Note: For more information about performance requirements for Office SharePoint Server 2007, see Module 9, “Maintaining and Optimizing Microsoft Office SharePoint Server 2007.”


2-21

Guidelines for Defining Interoperability Requirements

Introduction A feature of Office SharePoint Server 2007 is its broad range of interoperability options. This includes integration with external data through the Business Data Catalog (BDC) and the business intelligence features of Office SharePoint Server 2007 and single signon services that enable users to access other line-of-business solutions. When you plan for an Office SharePoint Server 2007 implementation, it is essential that you identify all interoperability requirements.

Business Data Catalog The BDC is a service for registering line-of-business applications and certain business data types and properties of those applications. The BDC is managed from the Shared Services Administration page for each Shared Services Provider. For each line-ofbusiness application that the Web applications and site collections of a Shared Services Provider use, you must first register the line-of-business application and the business data types and properties that you want to expose to users. The connectivity between the BDC and traditional line-of-business sources uses Web services. Connectivity between the BDC and database systems is achieved by using ADO.NET providers. Here, metadata defines BDC methods for executing SQL statements or stored procedures.

2-22


Business Intelligence Office SharePoint Server 2007 can provide an organization with business intelligence capabilities by preserving data integrity. It also offers search, integration, analysis, rendering, and collaboration options. Data warehousing and data mining are techniques that are used for gathering useful information from existing data sources. Business intelligence solutions frequently use online analytical processing tools to provide meaningful data. Office SharePoint Server 2007 business intelligence solutions typically include analysis data provided by external systems, such as Microsoft SQL Server 2005 Analysis Services and Excel Services. Connections to external data sources for analysis are held in data connection libraries. Office SharePoint Server 2007 can also use data from other business applications, known as line-of-business applications. This data can be displayed and analyzed in similar ways as the data in data connection libraries, providing an integrated view of all business data in the organization. These are registered in the BDC.

Single Sign-On Single sign-on authentication enables users to access multiple system resources without having to provide authentication credentials more than once. Office SharePoint Server 2007 implements single sign-on authentication by including a Windows service and a secure credentials database.

Other Integration Scenarios Office SharePoint Server 2007 provides many more interoperability opportunities in addition to those already mentioned. For example, if your solution must use content from another Office SharePoint Server 2007 system, you can use the Web Services for Remote Portlets (WSRP) Consumer Web Part; if the solution uses RSS Feeds, you can use the RSS Web Part; if the solution connects business processes, you can create and implement workflows.


2-23

Lab: Documenting Non-Functional Requirements for Office SharePoint Server 2007 Solutions


Interpret functional specifications.

•

Add non-functional requirements to the specifications.


Introduction In this lab, you will work with a partner or in a small group to complete a paper-based exercise to plan for an Office SharePoint Server 2007 deployment. You will then compare your plan with a sample solution plan.

Lab Setup For this lab, you will use the planning and specification documentation available in the virtual machine environment. Before you begin the lab, you must: •


•


2-24


Lab Scenario In this lab, you will work with a partner or in a small group to complete paper-based exercises to plan elements of an Office SharePoint Server 2007 implementation. You will read and analyze a business scenario document and a functional specification document. You will then use the information you have analyzed to complete planning worksheets for team roles and responsibilities and functional requirements. You will then complete non-functional worksheets that include considerations of authentication methods and data capacity requirements. You will also compare your worksheets with sample solutions and discuss your results with the other class members.


2-25

Exercise 1: Preparing for an Office SharePoint Server 2007 Implementation In this exercise, you will analyze requirements and plan for an Office SharePoint Server 2007 implementation. The principal tasks for this exercise are as follows:

f

•

Analyze the business scenario and functional specification.

•

List Team Cluster members.

•

List functional requirements.

Analyze the business scenario and functional specification

Tasks 1.

2.


Study the overarching scenario.

Review the functional specification.

f

Using Windows Explorer, browse to the E:\Labfiles\Lab02\Starter\ folder.

•

Double-click the Litware Business Scenario.docx file.

•

In the Microsoft Office Word dialog box, click OK. The document opens in Office Word 2007.

•

Read the Litware Business Scenario.docx document carefully. Ensure that you understand the overarching scenario specified in the document.

•

Switch to Windows Explorer.

•

Double-click the Litware Portal Functional Specification.docx file.

•


•

Read the Litware Portal Functional Specification.docx document carefully. Ensure that you understand the requirements specified in the document.

List Team Cluster members

Tasks 1.

•

Complete the Planning Team Roles and Responsibilities Worksheet.


Switch to Windows Explorer.

•

Double-click the Planning Team Roles and Responsibilities Worksheet.docx file.

•


•

Complete all sections of the worksheet based on the information available to you in the business scenario and functional specification documentation.

2-26


Tasks 2.


Compare your planning worksheet with the • sample worksheet.

f

2.

•

Double-click the Planning Team Roles and Responsibilities Worksheet.docx file.

•


•

Compare the document with the one you completed in the previous task.

•

Discuss the differences or similarities between the two documents with your lab partner.

•

Close all documents, and exit Microsoft Office Word.

List functional requirements

Tasks 1.

Using Windows Explorer, browse to the E:\Labfiles\Lab02\Solution\ folder.

Complete the Functional Requirements Worksheet.



•

Double-click the Functional Requirements Worksheet.docx file.

•


•


Compare the planning worksheets with the • sample worksheet.


•

Double-click the Functional Requirements Worksheet.docx file.

•


•


•


•



Exercise 2: Defining Non-Functional Requirements for Office SharePoint Server 2007 In this exercise, you will select the appropriate authentication methods and estimate capacity requirements based on the functional requirements. The principal tasks for this exercise are:

f

•

Identify required authentication methods.

•

Estimate data capacity requirements.

Identify required authentication methods

Tasks 1.

2.


Complete the Authentication Methods Worksheet.

Compare the deployment worksheet with the sample worksheet.

f


•

Double-click the Authentication Methods Worksheet.docx file.

•


•


•

Using Windows Explorer, browse to the E:\Lab02\Solution\ folder.

•

Double-click the Authentication Methods Worksheet.docx file.

•


•


•


•


Estimate data capacity requirements

Tasks 1.

•

Complete the Estimate Data Capacity Requirements Worksheet.



•

Double-click the Data Capacity Worksheet.docx file.

•


2-27

2-28


Tasks

2.


Compare the deployment worksheet with the sample worksheet.

•


•


•

Double-click the Data Capacity Worksheet.docx file.

•


•


•


•




2-29

Review

Review You have now completed this module. You should now be able to: •

Prepare and plan for implementing Office SharePoint Server 2007 solutions.

•

Describe typical non-functional requirements for Office SharePoint Server 2007based solutions and how to consider these requirements at the design stage.

You should now understand the project team requirements necessary to plan, develop, and deploy your solution. You have used some of the worksheets available to help you plan your Office SharePoint Server 2007 solution. Integral to a successful project is your ability to gather accurate business information so that you can make the best selection of functional and non-functional solutions for your organization. It may be useful to reflect on how the module content will affect your next planning and designing exercise for deploying an Office SharePoint Server 2007 implementation.

Review Questions Consider the following questions: •

How will MSF and the Team Model affect your next Office SharePoint Server 2007 solution planning?

•

How will you capture functional and non-functional requirements for your next Office SharePoint Server 2007 solution? How will this differ from previous requirements gathering exercises?

Module 3: Deploying Microsoft® Office SharePoint® Server 2007 Table of Contents Overview 3-1 Lesson 1: Office SharePoint Server 2007 Deployment Architecture 3-2 Lesson 2: Installing Office SharePoint Server 2007 3-8 Lesson 3: Managing Shared Service Providers 3-15 Lab: Planning for and Deploying Office SharePoint Server 2007 3-19 Lab Shutdown 3-23 Review 3-24

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, email addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. 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. The names of manufacturers, products, or URLs are provided for informational purposes only and Microsoft makes no representations and warranties, either expressed, implied, or statutory, regarding these manufacturers or the use of the products with any Microsoft technologies. The inclusion of a manufacturer or product does not imply endorsement of Microsoft of the manufacturer or product. Links are provided to third party sites. Such sites are not under the control of Microsoft and Microsoft is not responsible for the contents of any linked site or any link contained in a linked site, or any changes or updates to such sites. Microsoft is not responsible for webcasting or any other form of transmission received from any linked site. Microsoft is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement of Microsoft of the site or the products contained therein. 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. © 2007 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, BizTa k, Excel, ForeFront, FrontPage, InfoPath, Internet Explorer, MSN, OneNote, Outlook, PowerPoint, SharePoint, SQL Server, Visual Basic, Visual C#, Visual Studio, Windows, Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Module 3: Deploying Microsoft® Office SharePoint® Server 2007

3-1

Overview


Describe the Microsoft® Office SharePoint® Server 2007 deployment architecture.

•

Install and configure Office SharePoint Server 2007.

•

Describe and manage Shared Service Providers.

You can deploy Office SharePoint Server 2007 in a number of topologies and configurations to meet a wide range of operational requirements. You can use the wizardbased installation process to deploy different configurations, from single-server installations to server farm environments. The Shared Service Provider architecture adds to this flexibility by enabling you to specify which services in your solutions run on which computers and to provide application and security separation.

3-2


Lesson 1: Office SharePoint Server 2007 Deployment Architecture

Objectives After completing this lesson, you will be able to describe the Office SharePoint Server 2007 deployment architecture. You will be able to: •

List and describe deployment models.

•

List and describe deployment environments.

•

List hardware, software, and licensing requirements.

Office SharePoint Server 2007 provides a flexible deployment architecture that enables you to configure an infrastructure that meets your organization’s requirements. For example, you can deploy Office SharePoint Server 2007 on a single server for small-scale topologies or you can install and configure a fully scaled-out server farm topology for larger installations. Before you plan for or install Office SharePoint Server 2007, you must be familiar with the different deployment models and deployment environments. In addition, you must be aware of the hardware, software, and licensing requirements for Office SharePoint Server 2007.


3-3

Office SharePoint Server 2007 Deployment Models

Introduction You can install and configure Office SharePoint Server 2007 in a number of deployment topologies, from single-server installations to small or fully scaled-out server farms. The various configurations enable you to deploy solutions that meet your organization’s requirements, both in terms of operational capabilities and infrastructure constraints.

Single-Server Deployments For small-scale solutions, you can deploy Office SharePoint Server 2007 on a single server computer. A single-server configuration is useful if you want to evaluate the features and capabilities of Office SharePoint Server 2007 but you do not want to spend a lot of time installing components and configuring settings. A single-server configuration is also useful if you are deploying a small number of Web sites and you want to minimize administrative overhead. When you deploy Office SharePoint Server 2007 on a single server using the default settings, the setup program automatically installs Microsoft SQL Server™ 2005 Express Edition and uses it to create the configuration database and content database for your SharePoint site. Alternatively, you can use Microsoft SQL Server 2005 to store and manage the databases in a single server deployment, but you must ensure that you have already installed SQL Server before deploying Office SharePoint Server 2007.

3-4


Small Server Farm Deployments If you are hosting a large number of sites or you want the improved performance and scalability of a multitier topology, you can deploy Office SharePoint Server 2007 in a server farm environment. A small server farm typically consists of a database server running Microsoft SQL Server 2005 and one or two Web servers running Internet Information Services (IIS) and Office SharePoint Server 2007. In this configuration, the Web servers are also configured as application servers. The Web server role responds to clients requesting Web pages; the application server role provides Office SharePoint Server 2007 services, such as search, indexing, and Excel Services. If you install two or more Web servers, you must ensure that they all use the same configuration database.

Scaled-Out Farm Deployments For increased performance and scalability, you can introduce additional servers to perform the application server roles. A medium server farm typically consists of a database server, an application server running Office SharePoint Server 2007, and one or two Web servers running Office SharePoint Server 2007 and IIS. In this configuration, the application server provides indexing services and Excel Services, and the Web servers provide Web services and search services. A large server farm typically consists of two clustered database servers, two or more application servers running Office SharePoint Server 2007, and several load-balanced, Web servers running IIS and Office SharePoint Server 2007. In this configuration, each of the application servers is dedicated to providing specific Office SharePoint Server 2007 services, such as search, indexing, or Excel Services.


3-5

Office SharePoint Server 2007 Deployment Environments

Introduction Many organizations implement a variety of different environments to meet their business needs. Depending on the environments your company implements, you will need to ensure that they are managed in an appropriate manner.

Environments The following table describes typical Office SharePoint Server 2007 environments. Environment

Description

Development

This type of environment is used by developers who create custom components, such as Microsoft Windows® Workflow assemblies, Web Parts, and event handlers. The development environment is not usually identical to the live production environment, because it typically includes developer tools, such as Microsoft Visual Studio® 2005, and Microsoft Visual Studio Team Foundation Server.

Test

As part of the development process, custom components must be installed and tested before they are deployed to the live production environment. The test environment should mirror the live production environment as closely as possible, although testers often require developer tools and debuggers to identify problems with custom components.

3-6


Environment

Description

Authoring

For content management solutions, it is often useful for authors to produce content in a separate environment from the live production environment. Authoring environments enable content authors to work on servers located on your organization’s intranet, while content consumers access the production servers on the Internet. These environments also enable you to implement editing and approval processes before you publish content for consumers. Typically, the authoring environment is similar to the production environment but may include additional authoring tools and workflows.

Staging

In addition to the authoring environment, many organizations also implement staging environments for content management solutions. Unlike authoring environments, staging environments should mirror the production environment as closely as possible. This is because staging environments are used to perform final tests on the solutions and content before they are published to content consumers and end users.

Production

Content consumers and end users use the production environment, which usually consists of the most powerful servers and scaled-out topologies. The actual configuration of the production environment depends on its use. For example, an Internet Web site may contain content that is updated on a scheduled basis from the staging environments but is not editable by the users. Additionally, for business intelligence solutions or collaborative solutions, the production environment may provide rich functionality for the end user.

Migrating Solutions and Content Depending on your organization’s requirements, you may have to manage the migration and synchronization of solutions between different environments. You must ensure that you can deploy custom assemblies from development and test environments to live production servers. You can use a variety of tools for deploying custom assemblies, such as xcopy, gacutil, Microsoft Windows Installer packages, stsadm.exe, and Visual Studio Project Deployment tools. You must also ensure that you can deploy content between authoring, staging, and production environments. You can use the built-in content deployment features of Office SharePoint Server 2007 to achieve this. For complex content deployment solutions, you might also create routing workflows based on Windows Workflow Foundation technologies.


3-7

Office SharePoint Server 2007 Deployment Prerequisites

Introduction Before you deploy Office SharePoint Server 2007, you must understand the hardware and software requirements.

Software Requirements Depending on a server’s specific role, you must ensure that software prerequisites are met before installing Office SharePoint Server 2007. All Web servers and application servers must run Microsoft Windows Server® 2003 (Standard, Enterprise, or Datacenter) with Service Pack 1 (SP1) and have the Microsoft .NET Framework version 3.0 installed. Web servers must also be configured to run IIS in IIS 6.0 worker process isolation mode. Database servers must have Microsoft SQL Server 2005 or Microsoft SQL Server 2000 with Service Pack 3 (SP3) or later installed. In addition, all of the computers must use the NTFS file system.

Hardware Requirements It is recommended that Web servers and application servers have a dual-processor computer with processor clock speeds of 2.5-gigahertz (GHz) or higher and a minimum of 2 gigabytes (GB) of RAM. It is recommended that database servers have a dual-processor with clock speeds of 2.0 GHz or higher and a minimum of 2 GB of RAM.

3-8


Lesson 2: Installing Office SharePoint Server 2007

Objectives After completing this lesson, you will be able to install and configure Office SharePoint Server 2007. You will also be able to: •

Describe the installation options and processes.

•

Describe post-installation administrative tasks.

•

Explain the issues with deploying Office SharePoint Server 2007 in a server farm configuration.

You can install and configure Office SharePoint Server 2007 by using the installation wizard. After installation, the wizard will prompt you to complete a number of administrative tasks so that Office SharePoint Server 2007 is ready for use in your solutions.


3-9

Office SharePoint Server 2007 Installation Process

Introduction You can install Office SharePoint Server 2007 by using the setup wizard from the installation CD. The wizard enables you to install a stand-alone server configuration for a single-server deployment. It also enables you to install Office SharePoint Server 2007 in a server farm configuration. For a server farm you can choose which components to install onto which servers.

Stand-Alone Server Installations To install Office SharePoint Server 2007 on a stand-alone server, you must be a member of the Administrators group on the computer or a member of a group that is a member of the Administrators group on the computer, such as the Domain Admins group. You must also install and configure the required software on the server, including IIS, Microsoft .NET Framework 2.0, ASP.NET 2.0, and Windows Workflow Foundation Runtime Components. Once you have installed and configured the necessary software, you can then use the setup wizard. You will be prompted to enter the product key and to accept the terms of the license agreement. You can then perform a basic installation, and all components for a stand-alone server will be installed in the default location of %windir%\Program Files\Microsoft Office Servers. If you want to specify a different installation location, you must perform an advanced installation. You then specify that you want a stand-alone installation before changing the installation location.

3-10


Server Farm Installations To deploy Office SharePoint Server 2007 in a server farm environment, you will need one or more security accounts that will be used in the following context: •

A user account that you can use to install Office SharePoint Server 2007 and run the SharePoint Products and Technologies Configuration Wizard. This account must be: •

A domain user account.

•

A member of the Administrators group on each of your Web and application servers.

•

A member of the SQL Server Logins.

•

A member of the SQL Server Database Creator server role.

•

A member of the SQL Server Security Administrators server role.

•

A domain user account that you can specify as the Office SharePoint Server 2007 service account.

•

A domain user account under which the Office SharePoint Server Search service can run.

•

A domain user account that is used to crawl content on your sites and create indexes.

•

A domain user account that acts as the application pool identity for your site collection's Web application.

•

A domain user account that acts as the application pool identity for the Shared Services Provider application pool.

•

A domain user account under which the Shared Service Provider runs.

For more information about account requirements, see "Deployment for Office SharePoint Server 2007" in the Office SharePoint Server 2007 Resource Kit. You must also use the SQL Server 2005 Surface Area Configuration tool to support TCP/IP for local and remote connections. Then, as with the stand-alone installation, you must install and configure the required software on the server before using the setup wizard. When you use the setup wizard, you will be prompted to enter the product key and to accept the terms of the license agreement. After that, you may perform an advanced installation. If you are setting up a computer that will act as an application server or as a Web server and an application server, you should perform a complete installation. If you are setting up a computer that will act only as a Web server, you should install only the Web components. The option you choose depends on your specific topology and the role you want the server to perform.


3-11

Post-Installation Configuration

Introduction When the installation process has completed, you must complete the configuration of your server. The setup wizard will prompt you to run the SharePoint Products and Technologies Configuration Wizard. If you choose not to use this wizard directly after installing Office SharePoint Server 2007, you can run it from the Start menu at a later time.

SharePoint Products and Technologies Configuration Wizard The SharePoint Products and Technologies Configuration Wizard automates several configuration tasks, including installing and configuring the configuration database, installing Office SharePoint Server 2007 services, and installing the SharePoint Central Administration Web application. After the SharePoint Central Administration Web application has been installed, you can use it to perform other administrative tasks, such as configuring incoming and outgoing e-mail settings, creating SharePoint sites, and configuring diagnostic logging settings.

Windows SharePoint Services Web Application service You must start the Windows SharePoint Services Web Application service on every computer that you want to act as a Web server that was set up using the complete option during setup. This service only starts by default on servers that were set up using the Web server option. To enhance security, you can leave this service turned off on application

3-12


servers that do not provide Web content to client computers. Also, you do not need to turn this service on to use SharePoint Central Administration on a server.


3-13

Server Farm Considerations

Introduction After you install Office SharePoint Server 2007 in a server farm, you must perform additional configuration tasks.

Specifying Alternate Access Mappings If you install and configure Office SharePoint Server 2007 on a single server, and a user browses to your server, the server will render the content that is in your Web application. However, if you add additional servers to your server farm, the newly added servers will not have alternate access mappings configured to your Web application. You can use the Operations tab in the SharePoint Central Administration tool to configure outbound and incoming URLs. The outgoing URL is the URL that you want users to use to access your Web application. If you have a load-balanced configuration with a host name, you must add the host name to the Outbound URL for the Default zone. The incoming URL is the URL that you want to map to the Web application. It includes the protocol, the host name, and the port for the server that you want to map to your Web application (for example, http://servername:8080). If you have a load-balanced configuration, you should add the server name of each of your Web servers to the list of internal URLs. This will allow each of your Web servers to reach the content in your Web application.

3-14


Synchronizing Web and Application Servers All of the Web and application servers in your server farm must have the same SharePoint Products and Technologies installed. For example, if all of the servers in your server farm are running Office SharePoint Server 2007, you cannot add a server to your farm that is running only Microsoft Office Project Server 2007. To run Office Project Server 2007 and Office SharePoint Server 2007 in your server farm, you must install Office Project Server 2007 and Office SharePoint Server 2007 on each of your Web servers. Furthermore, if your solutions include custom Web Parts, workflow assemblies, solution features, or other custom components, you must ensure that all Web servers in the farm have those components installed and configured in the same way.

Configuring Application Services After you have installed and configured Office SharePoint Server 2007 on all of your Web and application servers, you must configure Office SharePoint Server 2007 services. The services you must configure depend on your server topology and the server roles you deploy. You must start and configure the Office SharePoint Server Search service on at least one of your Web or application servers. This service provides search and indexing services. You can start and configure this service on any type of server, including the following: •

A server that is acting as an application server and that provides only Office SharePoint Server 2007 services.

•

A server that is acting as both an application server and a Web server and which provides both Office SharePoint Server 2007 services and Web services.

•

A server that is acting as a Web server and provides only Web services.

Clustering SQL Server 2005 Database Servers You can take advantage of SQL Server 2005 clustering and failover support to increase the availability of your solutions in the event of a hardware failure on your database server. Alternatively, you can use SQL Server database mirroring or log shipping to provide redundancy in the data layer. For more information about increasing availability with SQL Server 2005, see the SQL Server 2005 documentation.


3-15

Lesson 3: Managing Shared Service Providers



•

Describe the process for creating a Shared Service Provider and list commonly used Office SharePoint Server 2007 Shared Service Providers.

Shared Service Providers form an important part of the entire Office SharePoint Server 2007 product, and hence your solutions.

3-16


What Is a Shared Service Provider?

Introduction The Shared Services Provider in Office SharePoint Server 2007 is conceptually similar to shared services in SharePoint Portal Server 2003, but its architecture has been completely restructured and redesigned. It is now built on a new provider model.

Office SharePoint Server 2007 Shared Service Provider The Office SharePoint Server 2007 Shared Service Provider includes virtually all of the services that multiple applications use in Office SharePoint Server 2007. These include: •

Full-text and property indexing and search services.

•

Business Data Catalog services.

•

Notification services for generating alerts.

•

User profile services.

•

Audience and targeting services.

•

Excel Services.

•

Single sign-on services.

•

Usage reporting services.


3-17

Creating the Shared Service Provider

Introduction After you have installed and configured Office SharePoint Server 2007, you must create the Shared Service Provider. The Shared Service Provider makes it possible to share Office SharePoint Server 2007 services across your server farm. Office SharePoint Server 2007 does not create the Shared Service Provider by default in a farm environment, so you must create it manually.

Shared Service Provider Creation Process You can create the Shared Service Provider by using the Application Management tab in the SharePoint Central Administration tool. When you create the Shared Service Provider, you must specify a Web application that will be used to manage it. You can create the Web application before you start the process and then select it as you create the Shared Service Provider. Alternatively, you can create the Web application as part of the Shared Service Provider creation process. You must also provide the user name and password of an account with which the Shared Service Provider will run. You must then specify the database server, database name, and SQL authentication credentials to be used with the Shared Service Provider. Additionally, you can specify the search database server, database name, and SQL Server authentication credentials.

3-18


After you have created the Shared Service Provider, you can then administer the functionality that it provides, such as searching and indexing, Business Data Catalog services, and Excel Services.


3-19

Lab: Planning for and Deploying Office SharePoint Server 2007

After completing this lab, you will be able to plan for and deploy Office SharePoint Server 2007. In this lab, you will work with a partner or in a small group to complete a paper-based exercise to plan for an Office SharePoint Server 2007 deployment. You will then compare your plan with a sample solution plan. You will also install Office SharePoint Server 2007 and perform post-installation configuration tasks, which are based on the sample plan. Estimated time to complete this lab: 60 minutes

Lab Setup For this lab, you will use the available virtual machine environment. Before you begin the lab, you must: •


•


3-20


Exercise 1: Creating Deployment Plans for Office SharePoint Server 2007 In this exercise, you will explore the scenario deployment requirements so that you can complete a deployment planning worksheet. The principle tasks for this exercise are as follows:

f

•

Analyzing the deployment scenario.

•

Documenting the deployment plan.

Analyze the deployment scenario Tasks


1.

•


•

Double-click the Litware Deployment Scenario.docx file.

•

In the Microsoft Office Word dialog box, click OK. The document opens in Microsoft Word 2007.

•

Read the Litware Deployment Scenario.docx document carefully. Ensure that you understand the overarching scenario specified in the document.

•

On a blank piece of paper, list the servers and briefly summarize the functionality that you think each server needs to provide. Discuss your conclusions briefly with your lab partner.

2.

f

Study the overarching scenario.

Determine the deployment requirements.

Document the deployment plan Tasks


1.

•


•

Double-click the Topology plan worksheet.docx file.

•


•

Using your conclusions from the previous task, complete the worksheet.

•


•

Double-click the Topology plan worksheet.docx file.

•


•


•


•


2.

Complete the deployment worksheets.

Compare the deployment worksheets with the sample deployment plan.


3-21

Exercise 2: Installing Office SharePoint Server 2007 In this exercise, you will install and configure Office SharePoint Server 2007. The principle tasks for this exercise are as follows:

f

•

Installing Office SharePoint Server 2007.

•

Performing post-installation configuration tasks.

Install Office SharePoint Server 2007 Tasks


1.

•

Using Windows Explorer, browse to the C:\MOSS 2007 Setup\ folder.

•

Double-click setup.exe.

•

On the Enter your Product Key page, in the text box, type F6YVR4XY7K-RCVY4-37FBK-G44PY

•

Click Continue.

•

On the Read the Microsoft Software License Terms page, select the I accept the terms of this agreement check box, and then click Continue.

•

On the Choose the installation you want page, click Advanced.

•

On the Server Type tab, select the Stand-alone – Install all components on a single machine (includes SQL Server 2005 Express Edition). Cannot add servers to create a SharePoint farm option.

Run the Setup application.

Note: You are choosing this option only because of the limitations of the virtual machine configuration. In the workplace, one of the other options may be more appropriate for your business needs. •

Click the File Location tab, and review the installation paths.

•

Click the Feedback tab, and select the No, thank you option.

•

Click Install now. The Office SharePoint Server 2007 installation process begins. Note: The process will take between 10 minutes and 15 minutes to complete. Use this time to review the additional reading on the Student CD. You should concentrate on the planning and deployment guides in the Upgrade and Deployment Guides\Planning Deployment and Upgrade Migration Guides folder.

2.

Run the SharePoint Products and Technologies Configuration Wizard.

•

When the setup process has completed, you are prompted to complete the configuration of your server. Ensure that the Run the SharePoint Products and Technologies Configuration Wizard now check box is selected.

•

Click Close to start the SharePoint Products and Technologies Configuration Wizard.

•

On the Welcome to SharePoint Products and Technologies page, click Next.

•

In the SharePoint Products and Technologies Configuration Wizard warning dialog box that notifies you that some services may have to be started or reset during configuration, click Yes.

3-22


Tasks

Supporting information The wizard performs the configuration tasks. Note: The process will take between 10 minutes and 15 minutes to complete. Use this time to continue reviewing the additional reading on the Student CD. •

On the Configuration Successful page, click Finish. Internet Explorer appears, and the Home Web page is displayed. Note: If the page cannot be displayed, or you encounter other errors, press F5 to refresh the page.

f

Perform post-installation configuration tasks Tasks


1.

•

On the Start menu, point to All Programs, and then point to Microsoft Office Server. Then click SharePoint 3.0 Central Administration. Internet Explorer appears, and the Central Administration Web page is displayed.

•

On the Central Administration home page, click the Operations tab on the top navigation bar.

•

On the Operations page, in the Topology and Services section, click Servers in farm.

•

On the Servers in Farm page, click LITWAREPORTAL.

•

In the Service section, click Office SharePoint Server Search.

•

On the Configure Office SharePoint Server Search Service Settings page, in the Query and Indexing section, ensure that the Use this server for indexing content check box and the Use this server for serving search queries check box are selected.

•

In the Contact E-mail Address section, in the E-mail Address box, type [email protected]

•

In the Web Front End And Crawling section, ensure that the Use all web front end computers for crawling option is selected, and then click OK.

•

Click the Application Management tab on the top navigation bar.

•

On the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farm's shared services.

•

On the Manage this Farm's Shared Services page, click SharePoint – 80.

•

In the Default Time Zone section, in the Select time zone list, click (GMT – 08:00) Pacific Time (US and Canada).

•

In the Maximum Upload Size section, in the Maximum upload size box, type 100.

•

Review all of the other settings but do not change any of the default values. Then click OK.

•

On the Application Management page, in the Office SharePoint Server Shared Services section, click Create or configure this farm's shared services.

2.

3.

Configure the Search service.

Configure the Shared Service Provider.

Configure indexing settings.


Tasks

3-23


Click SharedServices1 (Default).

•

In the Search section, click Search settings.

•

On the Configure Search Settings page, in the Crawl Settings section, click Default content access account.

•

In the Default content access account section, in the Account box, type LitwareInc\Administrator

•

In both the Password box and the Confirm Password box, type Pa$$w0rd

•

Click OK.

•

In the Crawl Settings section, click Content sources and crawl schedules.

•

On the Manage Content Sources page, click Local Office SharePoint Server sites.

•

On the Edit Content Source page, in the Crawl Schedules section, under Full Crawl, click Create schedule.

•

In the Manage Schedules -- Web Page Dialog dialog box, in the Type section, click Weekly.

•

In the Settings section, select the Sunday check box, and then click OK.

•

In the Crawl Schedules section, under Incremental Crawl, click Create schedule.

•

In the Manage Schedules dialog box, click OK.

•

In the Start Full Crawl section, select the Start full crawl of this content source check box, and then click OK.

•

Close all instances of Internet Explorer.


3-24


Review

Review You have now completed this module. You can now: •

Describe the Office SharePoint Server 2007 deployment architecture.

•

Install and configure Office SharePoint Server 2007.

•


Module 4: Administering Microsoft® Office SharePoint® Server 2007 Table of Contents Overview 4-1 Lesson 1: Creating Office SharePoint Server 2007 Sites 4-2 Lesson 2: Managing Office SharePoint Server 2007 Features 4-13 Lab: Managing Sites and Features 4-20 Lab Shutdown 4-24 Review 4-25


Module 4: Administering Microsoft® Office SharePoint® Server 2007

4-1

Overview


Describe the options available for centralized and decentralized site provisioning and the templates that you can use to create Microsoft® Office SharePoint® Server 2007 sites.

•

Describe the features available in Office SharePoint Server 2007, their functions, and how to manage them.

Introduction When you deploy Office SharePoint Server 2007, you have a range of administrative options and tools available to you, including: •

Centralized or decentralized site provisioning.

•

Templates.

•

Deployable functional components, called features.

These provide flexibility that enables you to maintain centralized control of functional administration or delegate some elements of these duties to users. Irrespective of your choice, you maintain control of the nonfunctional elements of administration, such as security.

4-2


Lesson 1: Creating Office SharePoint Server 2007 Sites


Explain what site provisioning is, and how to manage the provisioning process.

•

Describe the process of self-service site creation.

•

List Office SharePoint Server 2007 site templates and explain the use of each template.

Office SharePoint Server 2007 provides a flexible and agile platform for provisioning sites for users. In addition to the traditional centralized provisioning framework, you can delegate functional administration to users at a number of different levels, including the creation of top-level site collections, sites, or personal sites. To ensure that you provide users with a consistent and usable administrative environment, you must plan your site creation and management approach before you implement one or more methodologies. After completing this lesson, you will be able to describe the management options available for centralized and decentralized site provisioning, their benefits, and the templates that you can use for creating Office SharePoint Server 2007 sites.


Discussion: Functional Administrative Tasks for Office SharePoint Server 2007

Introduction The instructor will now lead a class discussion. Please participate in the discussion to ensure that you and your class members can fully benefit from the discussion.

Discussion Points Use the following points to help start the discussion. Feel free to discuss other related points as they arise. •

Who creates sites within your organization?

•

Why are these sites created by this group or groups?

•

Who decides on the available functionality of these sites?

•

How involved are the users in the site-creation process?

•

What do you consider to be the most important elements of site functionality?

•

How are sites managed in your organization?

•

What are the most significant issues in site provisioning and management in your organization?

•

Are all sites in your organization the same or do you provide options for different functionality within each site?

•

How do you identify the functional requirements for each site or site collection?

4-3

4-4


•

Is site creation or function management a significant overhead for administrators in your organization?


4-5

Overview of Site Provisioning

Managing Provisioning Processes Architecturally, Office SharePoint Server 2007 now has a three-tier administration model. This makes it easier for IT organizations to differentiate administrative roles and assign administrative responsibilities. •

Tier 1 tasks include the administration of features and functionality for centrally managing the server farm. A Tier 1 administrator might be responsible for creating new Web applications and site collections, managing incoming and outgoing e-mail settings for the farm, and managing server farm topology.

•

Tier 2 tasks include the administration of features and functionality for managing shared services across a server farm.

•

Tier 3 tasks include the administration of features and functionality for managing sites within a server farm. For example, a Tier 3 administrator might create new lists on a site, configure access permissions for users, and modify site hierarchy.

You can only create new site collections by using the Central Administration user interface. This means that only members of the Farm Administrators group can complete this task. Site provisioning is the delivery of useable sites for customers. You may choose to provision all sites or allow an amount of user self-service in site creation. To support you as you plan your provisioning requirements, Microsoft provides a number of planning

4-6


and design worksheets. They include the Site creation worksheet, Site maintenance worksheet, and the Site hierarchy choices worksheet documents. These worksheets will help you to identify your baseline requirements.

Managing Quotas You can use quotas to check and limit site storage. This is important in the overall management of your deployment. Office SharePoint Server 2007 provides a flexible quota-management system that allows you to set limits on site and site-collection data sizes. You can send warning e-mails to site owners when site storage reaches a specified threshold limit. You can also automatically stop users adding additional data to a site if storage reaches the site's maximum limit. Quotas templates and site collection quotas and locks are both located in SharePoint Site Management in the Application Management section of Central Administration. You can edit existing quota templates or create new quota templates based on existing options. Once you have specified the warning and maximum thresholds, you can apply these to the site collections that you create. When managing quotes, ensure that you: •

Create a range of quotas to support different system or user requirements.

•

Include enough scope for reasonable site growth.

•

Provide a realistic notice period between the warning e-mail and locking a site for exceeding its quota.


4-7

Self-Service Site Creation

Introduction A centralized administration approach may suit your organization if you prefer to maintain control and management over top-level sites. However, the default centralized method may not suit all organizations. Office SharePoint Server 2007 also provides a range of distributed management options.

Self-Service Site Management Self-Service Site Management allows users to create and manage their own top-level Web sites without recourse to an IT administrator. When you turn on Self-Service Site Management for a Web application, users can create their own top-level Web sites under a specific path. By default this path is /sites/, although you can include other paths as required. You can enable Self-Service Site Management by using the following procedure: 1. In the SharePoint Central Administration application, click the Application Management tab. 2. In the Application Security area, click Self-Service Site Management. 3. In the Enable Self-Service Site Creation area, click On. 4. Select the Require Secondary Contact check box (recommended).

4-8


When you enable Self-Service Site Creation, an announcement appears in the Announcements list on the home page of the top-level Web site. This provides a link to the site creation sign-up page. Only site members with site creation permissions can follow the link. The sign-up page for Self-Service Site Management can be customized or replaced with a page that includes all of the information you may need, using out-of-thebox facilities and without the need to develop new code. If you have multiple Web applications, you must enable each individually. Self-Service Site Management allows users with appropriate access rights to create their own top-level sites, reducing IT administrator intervention. To minimize IT administrator overheads you might: •

Specify that a secondary site collection administrator is mandatory. Administrative alerts, such as those for when quotas are exceeded, go to the primary and secondary administrators so the secondary administrator can manage alerts.

•

Define a storage quota and set it as the default quota for the Web application.

•

Set the number of sites allowed per content database.

•

Enable unused Web site notifications, so that you can request owners to verify that sites are still required.

Because Self-Service Site Creation creates new top-level Web sites on an existing Web application, new sites automatically conform to the Web application's default quota settings, unused Web site notification settings, and other administrative policies. The self-service process allows user to specify metadata for the site and specify that the site should be listed in the Site Directory.

Other User Site-Management Options Two additional options enable users to create their own sites and provide greater control over your Office SharePoint Server 2007 environment: •

Subsites. You can limit users to creating subsites of existing sites, rather than new site collections and top-level sites. A user with either Full Control or Hierarchy Manager permissions on an existing site can create a subsite. While this gives you greater control over the number of top-level sites, it may increase the administrative overhead, depending on the number of sites required. If users create sites at different levels within the site collection hierarchy, this may lead to confused navigation of your site collection. You can remove this capability from users if you remove the Create Subsites option right from the Full Control and Hierarchy Manager permissions, either at the site collection or Web application level.

•

Personal sites. You can allow users to create personal sites, also known as My Sites. These are site collections stored under the /personal/ path of the Web application. Personal sites are created for individual users, so they may not be an appropriate option if the user requires the ability to create sites for groups or communities. The


My Sites facility is enabled by default at the Web-application level in Office SharePoint Server 2007.

4-9

4-10


Office SharePoint Server 2007 Site Templates

Introduction Together, Windows® SharePoint® Services 3.0 and Office SharePoint Server 2007 provide a wide range of templates for creating sites.

Windows SharePoint Services Windows SharePoint Services includes the following categories and templates: •

•

Collaboration templates •

Team Site. This creates a site for teams to create, organize, and share information quickly and easily. It includes a document library and basic lists such as announcements, calendar, contacts, and quick links.

•

Blank Site. This creates a site with a blank home page. You can use a compatible Web page editor to add interactive lists or any other features.

•

Document Workspace. This creates a site for colleagues to work together on documents. It provides a document library for storing documents and supporting files, a task list for assigning to-do items, and a links list for resources related to the document.

•

Wiki Site. This creates a site where users can quickly and easily add, edit, and link Web pages without previous knowledge of Web page design.

•

Blog. This creates a site to post information and allow others to comment on it.

Meeting templates


4-11

•

Basic Meeting Workplace. This template provides the facilities to plan, organize, and track your meeting. This meeting workspace contains the following lists: objectives, attendees, agenda, and document library.

•

Blank Meeting Workplace. This template provides a blank meeting workspace for you to customize based on your requirements.

•

Decision Meeting Workplace. This template provides a meeting workspace in which to review relevant documents and record decisions. This meeting workspace contains the following lists: objectives, attendees, agenda, document library, tasks, and decisions.

•

Social Meeting Workplace. This template provides a planning tool for social occasions and features a discussion board and a picture library to post pictures of the event. This meeting workspace contains the following lists and Web Parts: attendees, directions, image/logo, things to bring, discussions, and picture library.

•

Multipage Meeting Workplace. This template provides the facilities to plan, organize, and track your meeting with multiple pages. It contains the following lists: objectives, attendees, and agenda. It also includes two blank pages for users to customize based on their requirements.

Office SharePoint Server 2007 Office SharePoint Server 2007 includes the following categories and templates: •

Enterprise templates •

Records Repository. This creates a site designed for records management. Records managers can configure the routing table to direct incoming files to specific locations. The site prevents records from being modified after they are added to the repository.

•

News Home. This creates a site for managing news articles and links to them quickly and easily. It includes sample news article layouts and an archive for storing older news items.

•

Document Center. This template creates a site to centrally manage documents in an enterprise.

•

Personalization Site. This template creates a My Site personalization site. It includes page layout and personalization specific Web Parts.

•

Site Directory Area Template. This template creates a site that lists important sites in your organization. It includes different views for Categorized Sites, Top Sites, and the Site Map.

•

Report Center Site. This template creates a site that simplifies the creation, management, and delivery of Web pages, documents, and Key Performance Indicators that communicate metrics, goals, and business intelligence information.

4-12


•

•

Search Center. This template creates pages dedicated to searching. The main welcome page features a simple search box in the center of the page. The template includes two tabs: one for general searches and the other for searches for information about people. You can add and customize tabs to focus on other search scopes or result types.

Publishing templates •

Publishing and Team Collaboration Site. This creates a site for publishing Web pages on a schedule. It also contains team collaboration features, including a calendar and basic lists for announcements and contacts. Teams can use these features to create, organize, and share information quickly and easily. A document and picture library is included for storing Web publishing assets.

•

Publishing Site. This template creates a site for publishing Web pages on a schedule, with workflow features enabled. By default, only publishing subsites can be created under this site. A document and picture library is included for storing Web publishing assets.


4-13

Lesson 2: Managing Office SharePoint Server 2007 Features


Describe what a feature is and explain its advantages over previous versions of Office SharePoint Server.

•

List features specific to Office SharePoint Server 2007 and describe how to manage those features.

•

Describe how to deploy, activate, and deactivate Office SharePoint Server 2007 features.

Introduction Office SharePoint Server 2007 provides modular components, called features. You can deploy, and then activate or deactivate them within farms, Web applications, site collections, and sites. You can use features to minimize your administrative overheads when managing your Office SharePoint Server 2007 environment.

4-14


What Is a Feature?

Introduction Features help to reduce the administrative overhead for system managers and can streamline deployment of solution functionality. Features offer ease of deployment and management when compared to configuration options available in previous versions of SharePoint Products and Technologies. Administrators can use this proven practice to deploy solution features centrally and delegate feature management to departmental administration roles if necessary. Features provide the following capabilities: •

Scoping rules, which specify where the feature code runs.

•

Pluggable activation and deactivation behavior.

•

Version management.

•

Simplified solution deployment.

Scoping Rules Office SharePoint Server 2007 has four levels in the logical architecture: server farms, Web applications, site collections, and sites. You can deploy, activate, and deactivate features at any of these levels, referred to as the scope of the feature. A feature may have a dependency on other features, at any scope. These are also hierarchical, for example, a site collection feature cannot have a dependency on a site feature.


4-15

Pluggable Activation and Deactivation Behavior You can deploy a feature without implementing its functionality for the scope, because a feature must be activated before any functionality is enabled. For example, you may decide to deploy Excel Services features, because you know that it will be used within the solution at a future release, but choose not to activate the feature immediately. With this facility, you can deploy a feature but activate it only for individual sites, site collections, or Web applications. Server farm features are activated by default, but you can deactivate features that are not required or necessary for a site or site collection.

Simplified Deployment Features also provide a benefit for IT professionals and developers who deploy Office SharePoint Server 2007 solutions. The reusable nature of features makes deployment faster and more granular. You can deploy features across your environment and then activate or deactivate them, based on the business requirements. You can also delegate feature management rights to individual site administrators.

Version Management Features provide an additional advantage for version management. Rather than copying code for reuse, with the associated issues for upgrades or modifications, you can deploy and activate a single version of the code as a feature. This can provide advantages across many functions available in Office SharePoint Server 2007. For example, you can activate a form template feature from the Manage Form Templates page for a site collection.

4-16


Office SharePoint Server 2007-Specific Features

Introduction Each of the four feature scopes in Office SharePoint Server 2007 has specific features, including both content management and business intelligence elements. This architecture allows you to deploy features at a high level but provide a granular implementation policy. The scopes have clear dependencies, for example, the provision of Excel Services requires that this feature be activated at the farm scope before deployment at the Web application, site collection, or site scope.

Business Intelligence Features •

Farm scope •

Data Connection Library. This provides business data access through the data collection library.

•

Excel Services Farm features. This provides farm-scope Excel Services features. This is a prerequisite of subordinate scope Excel Services features.


•

•

•

4-17

Web application scope •

Office Server Enterprise Search. This uses the Office Server Search service to search over a wider range of business resources, including people profiles, business data, and remote and custom content sources.

•

Office SharePoint Server Enterprise Web application features. This provides features such as the Business Data Catalog (BDC), Forms Services, and Excel Services in the enterprise license.

Site collection scope •

Office SharePoint Server Enterprise Site Collection features. This provides the BDC, Forms Service, and Excel Services in the enterprise license.

•

Office SharePoint Server Standard Site Collection feature. This provides the user profiles and search features in the standard license.

Site scope •

Office SharePoint Server Enterprise Site feature. This provides the BDC, Forms Services, and Excel Services in the enterprise license.

•

Office SharePoint Server Standard Site feature. This provides the user profiles and search features in the standard license.

Content Management Features Each of the scopes has the following features: •

•

•

Web application scope •

Office Server Site Search. This uses the Office Server Search service for site and list searches.

•

Office SharePoint Server Standard Web application features. This provides features such as user profiles and search in the standard license.

Site collection scope •

Office SharePoint Server Publishing Infrastructure. This provides centralized libraries, content types, master pages, and layouts. It also includes page scheduling and other publishing functionality for a site collection.

•

Office SharePoint Server Search Web Parts. This provides all Web Parts required for the Search Center.

Site scope •

Office SharePoint Server Publishing. This creates a Web page library and supports libraries and publishing pages.

4-18


Managing Office SharePoint Server 2007 Features

Deploying Features When you install Windows SharePoint Services 3.0 and Office SharePoint Server 2007, approximately 150 default features are automatically installed. Developers can also create additional features. Features are held in a series of subfolders within \Program Files\Common Files\Microsoft Shared\ web server extensions\12\TEMPLATE\FEATURES. Each feature folder has a file, called Feature.xml, which defines the feature’s properties. In addition, there may be supporting program files. The Feature.xml file contains information about the feature, such as description, version, scope, dependencies, and required resources. You must install individual features before you can use them. To do this, run the following command at the command prompt: stsadm –o installfeature –filename <path of the Feature.xml file relative to the 12\TEMPLATE\FEATURES folder >

To uninstall a feature so that its definition is no longer available within a server farm, you can use the uninstall feature command. You must deactivate features before uninstalling them unless they are Web application-scoped or farm-scoped features. To uninstall a feature use the following command: stsadm –o uninstallfeature –filename <path of the Feature.xml file relative to the 12\TEMPLATE\FEATURES folder >


4-19

Activating Features In addition to installing a feature, you must activate it before you can use it, unless the feature is server farm-scoped. You can activate features by using the site collection and site administration pages. You can also activate a feature by running the following command from the command prompt: stsadm –o activatefeature –name < folder in FEATURES directory containing the Feature.xml file > -url http://Server/Site/Subsite

Deactivating Features You can deactivate features through the site collection and site administration pages by using the Activate and Deactivate buttons. You can also use the command line or a script with the following command: stsadm –o deactivatefeature –name < folder in FEATURES directory containing the Feature.xml file > -url http://Server/Site/Subsite

Important: When you deactivate a feature, any data that is associated with the feature is deleted from the site content database.

4-20


Lab: Managing Sites and Features


Create sites.

•

Manage Office SharePoint Server 2007 features for site collections and sites.

Introduction In this lab, you will work on your own to complete two Virtual PC-based exercises to create a site collection and two sites for Litware, Inc. You will then manage features of the site collection and sites, activating and deactivating features for each. Estimated time to complete this lab: 45 minutes



•


Lab Scenario You are responsible for creating site collections and sites for the Litware, Inc. Office SharePoint Server 2007 solution.


4-21

Site Collection and Site Creation Requirements The initial requirement is a for a single site collection for the Sales group that will contain two sites. The site collection should be based on the Document Center template. One of the sites should be a Wiki, for informal team collaboration. The other site should be a Search Center. The plan is not to limit the size of these initially, as you will monitor volume over the coming months to see if restrictions are likely to be required later. The Wiki site will not require all of the features that will be available in the Document Center, but it will require controlled publishing.

4-22


Exercise 1: Creating and Managing Office SharePoint Server 2007 Sites The principle tasks for this exercise are as follows:

f

•

Create a site collection based on an Office SharePoint Server 2007 site collection template.

•

Create two sites in the site collection.

Creating a site collection and two sites Tasks


1.

•


•

Click the Application Management tab.

•

In the SharePoint Site Management section, click Create site collection. The Create Site Collection page appears.

•

In the Web Application section, click http://litwareportal:18097/, and then click Change Web Application.

•

In the Select Web Application -- Web Page Dialog dialog box, click SharePoint – 80.

•

On the Create Site Collection page, in the Title box, type Sales Sites

•

In the Description box, type Sale Group Site Collection

•

In the Web Site Address section, click /sites/ in the list. Then type SalesSites in the adjacent box.

•

In the Select a template list, click the Enterprise tab, and then click Document Center.

•

In the Primary Site Collection Administrator area, in the User name box, type Administrator and then click the Check Names icon to verify the user name.

•

Click OK. When the Top-Level Site Successfully Created page appears, click the http://litwareportal/sites/SalesSites link. The Sales Sites home page appears in a new window.

•

Click Site Actions, and then click Create.

•

In the Web Pages section, click Sites and Workplaces.

•

In the Title box, type Sales Search

•

In the Description box, type Sales Search Center

•

In the URL name box, type Search

•

In the Select a template list, click the Enterprise tab, and then click Search Center.

•

Accept all other default settings. Then, near the bottom of the page, click Create. The Sales Search site is created.

2.

Create a Site Collection.

Create a new Search Center site.


4-23

Tasks


3.

•

Click the Home tab.

•

Click Site Actions, and then click Create.

•

In the Web Pages section, click Sites and Workplaces.

•

In the Title box, type Sales Wiki

•

In the Description box, type Sales Group Wiki Site

•

In the URL name box, type SalesWiki

•

In the Template Selection list, click Wiki Site.

•

Click Create. The Sales Wiki Web site is created.

•

Click the Home tab. Leave Internet Explorer running – you will use it in the next exercise.

Create a new Wiki site

4-24


Exercise 2: Activating and Deactivating Office SharePoint Server 2007 Features The principle tasks for this exercise are as follows:

f

•

Activate site collection features.

•

Activate and deactivate site features.

Activating and deactivating site collection and site features Tasks


1.

•

Click Site Actions, and then click Site Settings.

•

In the Site Collection Administration section, click Site collection features.

•

Click Activate for Office SharePoint Server Publishing Infrastructure.

•

When the page has reloaded, click Activate for Office SharePoint Server Search Web Parts.

•

Click the Sales Wiki tab.

•


•

In the Site Administration section, click Site features.

•

Click Deactivate for Office SharePoint Server Enterprise Site features.

•

Read the warning message, and then click Deactivate this feature.

•

Click Activate for Office SharePoint Server Publishing. This feature has a dependency and requires that Office SharePoint Server Publishing Infrastructure be activated at the site collection scope. You activated the required feature in the previous task.

•

Make a note of the features that are currently active.

•

Click the Sales Search tab.

•


2.

3.

Activate site collection features for the Sales Sites site collection.

Activate and Deactivate features for the Sales Wiki site.

Review the active features in the Sales Team Site site.

•

In the Site Administration section, click Site features.

•

Make a note of the features that are currently active.

•


Lab Shutdown After you complete the lab, you must shut down the 5061a_LON-DC-01-04 virtual machine and discard any changes. Important: If the Close dialog box appears, ensure that Turn off and delete changes is selected and then click OK.


4-25

Review


Describe the process and the templates that you can use for creating Office SharePoint Server 2007 sites.

•

Describe features available in Office SharePoint Server 2007, their functions, and how to manage them.

Office SharePoint Server 2007 offers a range of templates, features, and user site management options to help you administer your environment. Together, these provide greater agility of deployment and flexibility of configuration than was available in previous versions. You can maintain control over all non-functional features and provide a better user experience in functional management.

Review Questions How will you use features to streamline the administration of your Office SharePoint Server 2007 environment? Which of the feature options do you think are most appropriate for your organization?

Module 5: Implementing Portal Solutions Table of Contents Overview Lesson 1: Creating Portal Sites Lesson 2: Implementing Collaborative Features Lesson 3: Implementing User Profiles and Audiences Lab: Implementing Collaborative Features in Portal Sites Lab Shutdown Review

5-1 5-2 5-10 5-16 5-23 5-29 5-30


Module 5: Implementing Portal Solutions

Overview

Portals are one of the key types of solutions that you can implement with Microsoft® Office SharePoint® Server 2007.


Describe the portal-based features of Office SharePoint Server 2007.

•

Describe and implement collaborative features in portal solutions.

•

Describe and implement User Profiles in portal solutions.

5-1

5-2


Lesson 1: Creating Portal Sites

Office SharePoint Server 2007 provides many built-in portal features, such as portal site templates and administrative tools.


Describe portal site templates.

•

List and describe the portal administrative tools.

•

Describe personal sites and explain how they fit in to collaborative portal solutions.


5-3

Discussion: Portal Sites and Collaboration

The instructor will now lead a class discussion. Please ensure that you participate in the discussion, when appropriate, to ensure that you and the other class members benefit fully from the discussion.

Discussion Points Use the following discussion points to help start the discussion. Feel free to discuss other related points as they arise. •

What do you understand by the term ‘portal’?

•

What do you understand by the term ‘collaboration’?

•

Does your organization currently use portals? If so, what does your organization use portals for?

•

What challenges, if any, have you encountered in previous portal-implementation projects?

•

How does personalization generally fit into collaborative portal solutions?

5-4


Portal Site Templates

Microsoft Office SharePoint Server 2007 provides a number of templates that you can use to help you build collaborative portal solutions.

Publishing Templates The two most commonly used templates for portal solutions are: •

The Collaboration Portal template. The Collaboration Portal provides a starter site hierarchy that is suitable for an intranet divisional portal or a portal for a small organization. It includes a home page, a News site, a Site Directory, a Document Center, and a Search Center with Tabs site. Typically, you use this type of site to host team sites.

•

The Publishing Portal template. The Publishing Portal provides a starter site hierarchy for an Internet-facing site or a large intranet portal. You can customize this type of site easily with your organization’s branding. The site includes a home page, a sample Press Releases subsite, a Search Center, and a logon page. Typically, you use this type of site to publish Web pages with approval workflows.

Enterprise Templates Office SharePoint Server 2007 provides other types of templates that you can use to build specific collaborative functionality into your portal solutions. For example, if your organization requires central document management, you can build a Document Center.


5-5

A Document Center can be the main focus of a portal. Alternatively, it can be an additional site. If you use the Publishing Portal template to create a portal, and you want to add a site to list and categorize important sites in your organization, you can create a site based on the Site Directory template. Similarly, if you want to add a dedicated search-based site, you can create a site based on the Search Center or Search Center with Tabs template. A site based on the Search Center template includes pages that you can use to perform advanced searches and display search results. The Search Center with Tabs template includes two tabs: one for general searches and another for searches for information about people. You can also add and customize tabs to focus on other search scopes or result types. Organizations often require sites that information workers can use to store personal information and share that information with other portal users. You can create a site based on the My Site Host template, which information workers can then use to create and manage their personal My Site sites. Note: You will learn more about the implementation of My Sites (and how to use them in collaborative portals) later in this module.

5-6


Administrative Portal Tools

A successful portal must be very easy to use. This is because information workers might not be IT specialists. To create easy-to-use portal solutions, you must design and manage informational taxonomy and hierarchies. You must also ensure that users can navigate through the hierarchy in an intuitive manner. Office SharePoint Server 2007 provides a number of different tools that can help you manage the structure and hierarchy of portal solutions.

Site Directory The site directory maintains a list of sites that have been created in the portal. The directory listing can include metadata that describes the site, such as titles and categories. You can also define custom metadata for the site directory. For example, you might create a custom column to store the name of the project manager for all project-based collaborative sites. Additionally, you can create custom views of the site directory to enable a user to find a specific site quickly and easily. Custom views can include specific columns, sort orders, and groupings to make navigation easier for users.

Site Map Office SharePoint Server 2007 provides a new site map feature that you can use to view the hierarchy of the entire portal from a central location. The site map includes links to each site and subsite in the portal hierarchy.


5-7

Site Manager You will sometimes want to reorganize portal structure and hierarchy. For example, your organization may change its divisional hierarchy. Office SharePoint Server 2007 provides Site Manger functionality for portal sites. You can use this functionality to reorganize portal structures. When you use the Site Manager features to move, promote, or demote a site, all navigational elements are updated automatically to reflect your changes.

5-8


My Site Personal Sites

Many organizations find value in enabling employees to share information through personal My Site sites. Office SharePoint Server 2007 provides many features for My Sites that help users efficiently find and share relevant information.

My Sites My Sites provide one of the key foundations of social networking in collaborative environments. Information workers can use features such as Web Parts and lists to network with colleagues and contacts. Note: You will learn more about social networking later in this module.

Information workers often use My Sites to store information that they want to keep private alongside information that they want to share with colleagues and partners. You can use Office SharePoint Server 2007 to provide two versions of each My Site site. Users can have a public-facing version of their site to store information that they want to be generally available to other users. They can also have a private-facing site to store information that they do not want to disseminate to a wider audience. In addition, users can selectively secure information so that only specified individuals, such as their manager or close colleagues, can view it. Office SharePoint Server 2007 provides a useful view switcher that enables users to see what information on the site is available to the people who may visit their personal site.


5-9

Administering My Sites Users create their My Site sites the first time they click the My Site link in the portal site. To control the physical location for My Site sites, create a site based on the My Site Host template. Note: You can specify only one My Site Host location for the Shared Service Provider in a server farm. If you have created a portal based on the Collaboration Portal template, a My Site Host location will already have been created for you. However, if your portal is based on a different template, you can add My Site capabilities by creating a top-level site collection based on the My Site Host template.

Additionally, you can control the name and URL assigned to each user. For example, if users from different domains use the portal, there is the possibility that two different users might have the same logon name. This could lead to duplicates and conflicts when users create and access My Site sites. To prevent possible duplicate My Sites URLs, you can specify that each user is identified in the form <domain>_<username>, where <domain> is the domain name, and <username> is the user’s logon name. Furthermore, you can control whether users can change the language settings for their My Site.

My Sites and Office 2007 Client Applications When users create their My Site site, they will be prompted to choose whether to add the site as a location for saving and opening Microsoft Office 2007 documents. This feature means that users can share information in documents very efficiently and seamlessly; the Office application Open and Save As dialog boxes provide a named location that maps to the user’s My Site site.

5-10


Lesson 2: Implementing Collaborative Features

You can use portals just to provide a gateway to other information stores. However, you can also use them to facilitate collaboration between employees, partners, customers, and suppliers in different organizations. Office SharePoint Server 2007 provides many features to support collaboration in portal solutions. These features include collaborative Web Parts, integration points with other collaboration technologies, and integration points with other applications and information stores.


Describe the collaborative portal Web Parts.

•

Explain the real-time collaboration integration of Microsoft Office SharePoint Server 2007 with Microsoft® Live Communication Server.

•

Describe how to use Single Sign-On services to incorporate information and applications into portal solutions.


5-11

Collaborative Web Parts

Previous versions of Office SharePoint Portal Server and Windows SharePoint Services provide many collaborative Web Parts to help teams of users work together on projects and share information. These Web Parts include the following: •

Contact Web Parts. These display useful, customizable contact details.

•

Task Web Parts. These indicate which employee is to complete which task, along with status information and due dates for each task.

•

Discussion Web Parts. These enable users to participate in threaded, asynchronous conversations.

•

Document Library Web Parts. These enable users to share and control documentbased information.

•

Site User and Member Web Parts. These provide information about site users. This includes their current online status.

Office SharePoint Server 2007 has new collaborative Web Parts, many of which focus on social networking functionality. These new collaborative Web Parts include the following: •

Colleague Web Parts. These provide links to other users in one of the following three categories: •

Users you have added as a colleague.

•

Users that have added you as a colleague.

5-12


•

Users that have been shared with you by another colleague.

•

Colleague Tracker Web Parts. These list colleagues and their recent changes.

•

In Common Between Us Web Parts. These display elements in common between you and the person browsing your My Site.

•

People Search Web Parts. These enable you to search for a person with specific knowledge or attributes, rather than searching for actual information.

•

People Search Core Results Web Parts. These enable you to search for a person and view the properties of the people returned by the search.


5-13

Guidelines for Implementing Real-Time Communication

Many information workers now work remotely or flexibly. Businesses must be able to locate people at short notice and use the appropriate technology to communicate with them. You can integrate Microsoft® Office Communicator 2007 and Microsoft Live Communications Server 2007 with Office SharePoint Server 2007 to provide completely integrated collaborative solutions. Office Communicator 2007 is an integrated communications client that enables information workers to collaborate in real time. Office Communicator 2007 integrates with Microsoft Office System applications and enterprise telephony infrastructure. Office Live Communications Server 2007 provides a powerful, scalable enterprise instant messaging and integrated presence solution. The features that Office Live Communications Server 2007 and Office Communicator 2007 provide, such as instant messaging and video conferencing, add powerful collaborative advantages to your solutions. However, you must be aware of some issues when you design and implement these solutions. These issues include the following: •

Increased Internet bandwidth requirements for remote workers, who might be limited to slow Internet connections.

•

Firewall policies that might prevent certain content, such as streamed video from video conferences, or application sharing features, from being locked.

•

Limited screen capabilities of PDAs and Smartphones used by mobile workers.

5-14


Windows SharePoint Services and Microsoft Office SharePoint Server 2007 ease some screen-capability issues as they provide mobile Web Parts and mobile versions of content. Microsoft Office InfoPath® 2007 also helps address these issues for form-based pages by providing wizards that create mobile-compatible forms.


5-15

Implementing Single Sign-On for Portal Solutions

Single Sign-On for Office SharePoint Server 2007 is implemented as a shared service for the entire server farm. Single Sign-On enables a user to be authenticated by an Office SharePoint Server 2007-based portal solution. Office SharePoint Server 2007 then passes alternative credentials to a variety of other applications. The user is not prompted for different user names and passwords for each system. Single Sign-On stores and maps the required user names and passwords for each integrated application in a database. It then retrieves these credentials for each user as they access a specific application or database from the portal. The most typical uses of Single Sign-On with Office SharePoint Server 2007 are to integrate with Business Data Catalog applications and line-of-business applications that require different credentials from the portal. Prior to the release of Office SharePoint Server 2007 and Microsoft BizTalk® Server 2006, these two product suites both implemented versions of Single Sign-On. However, these versions were not compatible with each other. Office SharePoint Server 2007 and BizTalk Server 2006 now use the same Single Sign-On service. This means that you can define credential mappings only once and have those credentials used throughout your enterprise by both Office SharePoint Server 2007 and BizTalk Server 2006.

5-16


Lesson 3: Implementing User Profiles and Audiences

You will often need to incorporate user information into your collaborative solutions. Office SharePoint Server 2007 provides an extensible and flexible profile framework to help you build people-oriented collaborative solutions.


Describe what a user profile is.

•

Describe User Profile stores.

•

Explain how to import User Profile data from external directories.

•

Describe the audience and targeting features provided by Office SharePoint Server 2007.


5-17

What Is a User Profile?

User Profiles hold information about site users. You can use the Shared Service Provider administration pages to define what information is held in User Profiles. Office SharePoint Server 2007 provides improvements to properties that enhance the User Profile features of Office SharePoint Portal Server 2003. These improvements include the following: •

Multi-valued properties. Properties now support multiple values. There are many scenarios in which this improvement can be useful. For example, you can define a multi-valued property to store users’ interests or address information.

•

Properties with open or closed choice lists. You can bind User Profile properties to a vocabulary that contains a list of possible values. If the property uses a closed list, users must select from the predefined values. If the property uses an open list, users can add new values.

•

Properties from external data sources. When you create a new property for a profile instance, you can map the property to an external data source, such as an entity registered in the Business Data Catalog.

•

Privacy policies. You can assign privacy policies to properties. Privacy policies restrict who can access the properties. For example, you can set policies to restrict property access to Only Me, My Manager, My Workgroup, My Colleagues, or Everyone.

5-18


•

Object properties. You can define a property as an Object type. This enables you to include any common language runtime object in the profile store. As the Web farm administrator, you must deploy the object to the Web server as part of application deployment. The object is then accessible in deployed solutions.

Using Profiles in Portal Solutions Built-in features of Office SharePoint Server 2007, such as audience targeting and My Sites, use the User Profile store and User Profile data. In addition, you can incorporate User Profile properties in custom solutions.


5-19

User Profile Stores

Office SharePoint Server 2007 maintains User Profiles by using Microsoft SQL Server™ as a data storage provider. Profile data can be imported into the User Profile store from Microsoft Active Directory® or other Lightweight Directory Access Protocol (LDAP) stores. Office SharePoint Server 2007 User Profiles are based on the Microsoft .NET Framework User Profile architecture. This means that you can create custom profile providers and profile stores and then import profile properties from those custom profile solutions. If you have imported the profile data from an external source, you can still extend User Profiles with custom properties.

5-20


Profile Directory Import

If you import profile data from an external source, such as Active Directory, you will typically want to keep the imported data up-to-date with the values maintained by that external source. The Shared Service Provider administration pages provide features that help you to manage profile data synchronization.

Full Imports Full imports populate the Office SharePoint Server 2007 User Profile store by creating properties and populating them with values from the external source. A full import is typically performed as you set up the User Profile store. You can also use full imports to replace all existing User Profile data with the most current values available from the external source.

Incremental Imports You can use incremental imports after you have performed at least one full import. An incremental import adds, updates, or deletes data in the User Profile store that has been added, modified, or deleted in the external source after the last User Profile import operation. Incremental imports are typically more efficient to perform than full imports.

Scheduled Imports You can create schedules for import operations. This means that you do not have to remember to periodically refresh the data in the User Profile store in response to changes in the external data source. You can schedule both full imports and incremental imports.


5-21

For example, you might specify a typical schedule where a full import is performed once per week, and incremental imports are performed on a daily basis. Note: You should schedule User Profile import operations for times when server load is at a minimum.

5-22


Audiences and Targeting

Most collaborative portal solutions require you to make relevant information readily accessible to users. For example, your solution might include a list for storing and disseminating announcements to employees. Many of these announcements might be made on an office-by-office basis; a specific announcement might be relevant only to employees in a particular location. You do not have to create separate announcement lists. You can use audiences and targeting to specify which announcements are targeted at which users.

Creating Audiences You can use the Shared Service Provider administration pages to create audiences. You can define an audience by any of the following attributes: •

Group membership, such as all members of an Active Directory group.

•

Organizational hierarchy, such as all employees who report to the vice president of sales, either directly or indirectly.

•

Any User Profile property or combination of User Profile properties, such as all users who have stated an interest in cycling and like travel to destinations abroad.


5-23

Lab: Implementing Collaborative Features in Portal Sites


Create portal sites.

•

Create and manage personal sites.

•

Create and manage audiences and targeting.




•


5-24


Exercise 1: Creating and Managing Portal Sites In this exercise, you will create a new Web application to host a portal site for Litware, Inc. You will then create and configure the portal site in the new Web application. The principle tasks for this exercise are as follows: •

Create a portal site.

•

Explore the portal site.

•

Configure the structure of the portal site.

•

Modify the portal site settings.

•

Test the portal site settings.

Tasks


1.

•


•


•

In the SharePoint Site Management section, click Create site collection. The Create Site Collection page appears.

•

In the Web Application section, click http://litwareportal:18097/, and then click Change Web Application.

•


•

In the Title box, type WebPortal

•

In the Description box, type Employee Extranet Portal

•

In the Web Site Address section, click /sites/ in the list. Then type WebPortal in the adjacent box.

•

In the Template Selection section, click the Publishing tab.

•

Click Collaboration Portal.

•

In the Primary Site Collection Administrator section, in the User name box, type LitwareInc\Administrator.

•

Click OK. The Operation in Progress page appears. After a short time, the Top Level Site Created Successfully page appears.

•

Click http://litwareportal/sites/WebPortal. The WebPortal page appears in a new window.

•

Click the View All Site Content link.

•

Review the lists of Document Libraries, Lists, Discussion Boards, and Sites and Workspaces.

•

Click the WebPortal tab. Notice that there is a tab named Reports.

•

On the Site Actions menu, click Manage Content and Structure.

•

In the tree-view control, point to Reports, and then click the arrow for this item.

2.

3.

Create a portal site.

Explore the portal site.

Configure the portal site structure.


Tasks

4.

5.

Modify the portal site settings.

Test the portal site settings.

5-25


In the shortcut menu, click Move.

•

In the Move… -- Web Page Dialog dialog box, click Document Center, and then click OK. The Reports item is moved into the Document Center hierarchy.

•

When the move operation is complete, in the Address bar, type http://litwareportal/sites/WebPortal and then press ENTER. The home page appears. Notice that the Reports tab is no longer visible.

•

Click the Document Center tab. Notice that the Reports item is present in the Site Hierarchy control for the Document Center.

•

Click the WebPortal tab.

•

On the Site Actions menu, point to Site Settings, and then click Modify All Site Settings.

•

In the Site Collection Administration section, click Site directory settings.

•

In the Site Creation Metadata section, select the Enforce listing new sites in Site Directory check box.

•

Select One site category is mandatory, and then click OK.

•

Click the WebPortal tab.

•

On the Site Actions menu, click Create Site.

•

In the Title box, type Employees

•

In the Description box, type Employee Personal Sites

•

In the URL name box, type employees

•

In the Template Selection section, click the Enterprise tab.

•

Click Personalization Site.

•

In the Site Categories section, clear the Information Technology check box.

•

Select the Research & Development check box, and then click Create. The Operation in Progress page appears. After a short time, the Employees site appears. Note: You were required to select at least one category because of the steps you completed in the previous task.

•

Near the top left of the page, click WebPortal.

•

Notice that a new tab named Employees is included in the WebPortal site. Then close all instances of Internet Explorer.

5-26


Exercise 2: Managing Personal Sites In this exercise, you will create your personal site and configure Microsoft Office 2007 client applications to add your site as a document location. This principle tasks for this exercise are as follows: •

Configure global settings for My Sites.

•

Create a personal site.

•

Configure Microsoft Office 2007.

•

Save a document from Microsoft Office Word 2007 to your personal site.

•

Review your profile information.

Tasks


1

•

On the Start menu, click SharePoint 3.0 Central Administration. Internet Explorer starts and loads the Central Administration page.

•

In the Shared Services Administration section, click SharedServices1. After a short period of time, the Shared Services Administration: SharedServices1 page appears.

•

In the User Profiles and My Sites section, click My Site settings.

•

In the Site Naming Format section, select the User name (resolve conflicts by using domain_username) option, and then click OK.

•

Start Internet Explorer, and then navigate to http://litwareportal/sites/WebPortal.

•

Click the Employees tab.

•

Click the My Home tab. The Create My Site page appears. After a short time, the My Site site appears.

•

In the Configure My Site for Microsoft Office dialog box, click Yes.

•

On the Start menu, point to All Programs, point to Microsoft Office, and then click Microsoft Office Word 2007.

•

In Microsoft Word, type My Resume

•

On the top toolbar, click Save.

•

In the Save As dialog box, in the Save in list, click My Site.

•

Double-click Personal Documents.

2

3

4

Configure global settings for employees’ My Sites.

Create your personal site.

Save a document to your site.

Review your profile.

•

Click Save.

•

Close Microsoft Office Word.

•

In Internet Explorer, click the My Home tab. Notice that the My Resume document is displayed in the Documents list.

•

Click the My Profile tab.

•

Click Edit Details. Review the properties that can be set by default for a user profile.

•

Leave Internet Explorer running. You will use it in the next exercise.


5-27

Exercise 3: Managing User Profiles and Targeting In this exercise, you will import User Profiles and configure audiences for targeting information. This principle tasks for this exercise are as follows: •

Import profile information from Active Directory.

•

Create Audiences for targeting.

Tasks 1

2

3

4

5


Add the Student account as a • member of the WebPortal site. •

Configure Active Directory Profile Full Import tasks.

Configure Active Directory Profile Incremental Import tasks.

Modify the Student user’s profile.

Create Audiences.

In the Address bar, type http://litwareportal/sites/WebPortal and then press ENTER. On the Site Actions menu, point to Site Settings, and then click People And Groups.

•

Click New.

•

In the Users/Groups box, type LitwareInc\Student and then click OK.

•

Switch to the instance of Internet Explorer that currently displays the Shared Services Administration: SharedServices1 page.

•

In the User Profiles and My Sites section, click User profiles and properties.

•

In the Profile and Import Settings section, click Configure profile import.

•

In the Source section, click Current Domain (LitwareInc).

•

In the Microsoft Internet Explorer message box, click OK.

•

In the Default Access Account section, click Specify Account.

•

In the Account name box, type LitwareInc\Administator

•

In the Password box, type Pa$$w0rd

•

In the Confirm password box, type Pa$$w0rd

•

In the Full Import Schedule section, select the Schedule full import check box.

•

In the Start at list, click 12:00 AM.

•

In the Incremental Import Schedule section, select the Schedule incremental import check box.

•

In the Start at list, click 3:00 AM.

•

Ensure that the Every day option is selected, and then click OK.

•

On the User Profiles and Properties page, click Start full import.

•

Click Refresh until the Profile import status reads Idle.

•

Click View user profiles.

•

Click LITWAREINC\Student, and then click Edit.

•

In the Office box, type Bothell

•

Click Save and Close.

•

In the Shared Services Administration section on the left of the page, click the SharedServices1 link.

•

In the Audiences section, click Audiences.

5-28


Tasks

6

Target content to the Office Workers audience.


Click Create Audience.

•

In the Name box, type Office Workers

•

In the Owner box, type LitwareInc\Administrator and then click OK.

•

If the AutoComplete dialog box appears, click No.

•

In the Operand section, click the Property option.

•

In the list below the Property option, click Office.

•

In the Operator list, click =.

•

In the Value box, type Bothell and then click OK.

•

Click Compile Audience. Notice that the audience currently contains one member. (If one member does not display, wait a few seconds and click Compile Audience again.)

•

Click View membership, and notice that the Student account is a member of the audience.

•

In the Address bar type http://litwareportal/sites/WebPortal and then press ENTER. The home page appears.

•


•

Click the Announcements link in the main pane.

•

On the Settings menu, click List Settings.

•

Click Audience targeting settings.

•

Select the Enable audience targeting check box, and then click OK.

•


•

Click Add new announcement.

•

In the Title box, type New Coffee Machine!

•

In the Body box, type The coffee machine is on the third floor. All office workers can use it free of charge.

•

Click the Browse icon next to the Target Audiences box.

•

Click Office Workers.

•

Click Add – >, Click OK, and then click OK again. Note: Although the Administrator account is not a member of the Office Workers audience, you can still see the announcement because it was created by using the Administrator account.

7

Test audience targeting.

•

Near the top of the page, click Welcome LITWAREINC\Administrator, and then click Sign in as Different User.

•

In the Connect to LITWAREPORTAL.LITWAREINC.COM dialog box, in the User name box, type LITWAREINC\Student

•


•

Notice that the welcome message near the top of the page reads Welcome Student. Notice that you can also see the new announcement about the coffee machine when signed in as the Student user.

•




5-29

5-30


Review

You have now completed this module. You should now be able to: •

Describe and implement the portal-based features of Office SharePoint Server 2007.

•

Describe and implement collaborative features in portal solutions.

•

Describe and implement User Profiles in portal-based solutions.

Module 6: Implementing Content Management Solutions Table of Contents Overview 6-1 Lesson 1: Overview of Content Management 6-2 Discussion: Content Management and Enterprise Content Management 6-3 Lesson 2: Managing Documents and Content with Office SharePoint Server 2007 6-14 Lesson 3: Implementing Content Management Processes 6-25 Lab: Implementing Content Management Sites and Processes 6-31 Lesson 4: Implementing Content Management Policies 6-38 Lab: Implementing Auditing and Policies 6-47 Lab Shutdown 6-55 Review 6-56


Module 6: Implementing Content Management Solutions

6-1

Overview

Introduction Microsoft® Office SharePoint® Server 2007 provides features that enable you to manage content across your organization. These features can help you to comply with recordkeeping regulations, automate the management of large volumes of information, and protect and preserve sensitive corporate information.


Describe the basics of the content management process and explain how various parts of these processes are implemented in Office SharePoint Server 2007 solutions.

•

Describe content and document-management concepts and processes in Office SharePoint Server 2007 solutions.

•

Implement standard and advanced content management processes.

•

Implement the advanced features of Office SharePoint Server 2007 to enable robust policies and auditing for enterprise-level content management.

6-2


Lesson 1: Overview of Content Management

Introduction Organizations use a variety of processes to author, approve, publish, and manage electronic information. This information may be for internal or external consumption and may include a range of content formats. Increasingly, the content relates to business transactions and activities, which organizations must maintain in accordance with regulatory obligations.


Explain why organizations require content management processes.

•

Describe the key components of a typical content management process.

•

Describe the authoring and approval process

•

Describe the Office SharePoint Server 2007 components that support content management processes.

•

Describe the site collection and site-level features that enable content management processes.


6-3

Discussion: Content Management and Enterprise Content Management

Introduction The instructor will now lead a class discussion. Please ensure that you participate, when appropriate, to ensure that you and the other class members benefit fully from the discussion.


Who creates content in your organization?

•

What types of content do they create?

•

How much of this content is business-critical?

•

How does your organization manage business-critical information in terms of: •

Security?

•

Compliance?

•

Retention and disposal?

•

Delivery?

•

Change control?

6-4


•

What do you understand by the term ‘content management’?

•

What do you understand by the term ‘enterprise content management’?

•

How does Microsoft Content Management Server 2002 fit with Office SharePoint Server 2007?


6-5

What Is Content Management?

Content Management Drivers The term content management describes the increasingly popular trend of publishing business information in managed repositories for Web browser delivery. Delivery of information on the Internet or on business intranets and extranets has a number of implications for businesses. The delivery medium offers immediate publishing and distribution of data, which means that the following scenarios become possible: •

Authoring by nonprofessional writers.

•

Publishing by nonprofessional publishers.

The growth in the amount of content reflected the appetite of users for current information. Business staff, partners, and customers all want real-time access to data. In addition, the range of formats deliverable by using Web and other technologies means that content is available in graphical, text, video, and sound formats. Audiences also want information formatted for their use. For example, buyers and repair engineers require different types of information about the same product, although some elements are common to both. The formatting of this information may also change dependent on whether the output device is a computer or a mobile screen. This means that a new paradigm for information development and delivery is necessary to maintain information integrity and usability.

6-6


Content Management Deliverables Content management provides a controlled environment for authoring, branding, publishing, and managing business information. You can reuse and render content to provide information in the view, format, or depth that is appropriate to the target audience. Decentralization of business authoring and distribution requires a formal, but simple-touse, framework for content developers, editors, approvers, and publishers. Content management provides information controls, such as version control, check in and check out, workflow, and access control. You can use template pages and cascading style sheets to standardize page layouts, navigation, and visual motifs. This enables you to customize a site with your organization's branding. Many of these content development options are available through traditional hypertext markup language (HTML). However, information workers may not be familiar with HTML. Additionally, development environments do not typically offer the workflow and management structures necessary for business users. Content management offers a Web-based authoring environment with workflow capabilities that provide secure authoring, approval, and publishing.

Business Integration Content management now delivers more than just a content development and delivery platform. Integration with other business systems, such as e-mail, now extends content management capabilities. This tighter integration may reflect the growth of compliance requirements.

Enterprise Content Management and Web Content Management The terms enterprise content management (ECM) and Web content management (WCM) reflect subtle differences between two content management strategies. ECM includes records management, WCM, and document management. You manage enterprise content by using workflow rules, retention and expiration policies, and auditing. WCM is primarily a content authoring and publishing activity. This can include Internet, extranet, and intranet outlets. As with ECM, you can use workflows to manage the WCM process. However, these workflows focus on authoring and approval of content.


6-7

Authoring and Approval Process

Authoring and Approval Process Office SharePoint Server 2007 offers a rich set of authoring options. You can use the Web browser environment or other applications, such as Microsoft Office, to create content. Irrespective of the development toolset, you can place authoring in a workflow that manages the creation, submission, approval, and publication of business content. The use of authoring and approval workflows is based on user types. When you create a site, you can add users in the following groups to include them in the workflow: •

Owners, who have full control over the site.

•

Members, who can contribute content to the site.

•

Approvers, who can approve content submitted by contributors and contribute content.

There are a number of other groups, such as Designer and Visitor, but these are not specifically designed for the authoring approval workflow.

Creating Contributions A contributor can create and edit pages. Office SharePoint Server 2007 provides a series of templates for new page creation, such as Article Page with Image on Left and Blank Web Part Page. When contributors create a new page or edit an existing one, they must have the changes approved by an authorized user before the page can be published. The contributor can check it in to a draft share and reedit the work as required. When the

6-8


contributor or the collaborative team is satisfied with the content, the page must be submitted for approval. The page is not published until it is approved by a member of the Approver group. A minor draft is indicated by a point number, so a new page is given a minor draft version of 0.1.

Approving Contributions Approval by a member of either the Approver or Owner group publishes the submitted page, updating the page version number to a major number, such as 1.0. There are a number of ways in which you can check, approve, or reject a submission. A user in either the Approver or Owner group can review the current approval tasks, which are found in Workflow Tasks. You can claim a workflow task, in this case an approval, and then complete the approval process. This is most often the case where there are a number of approvers, as claiming tasks ensures that only one reviewer works on a page at any time. In an organization with only one member of the Approver group it is unnecessary to claim tasks. An approver can review items with a Pending Approval status from the View Reports option on the Site Settings menu. This menu contains additional options that you can use to locate Approval Pending items. These options include My Tasks, All Draft Documents, items that will be published or expire in the coming seven days, items checked out by the approver, and items last modified by the approver. You can approve multiple pages simultaneously by using the checkboxes available on this page. In addition to maintaining content history with version numbers, contributors and approvers can add version comments. To approve a submitted page, click Approve. This in-place approval also provides a view of the document history. When you approve a submitted page, it becomes available for publishing. This may not be an immediate event because the page may be under the control of a time or date restriction in a workflow. The publishing process, especially in a multi-tier environment, will almost certainly have scheduled content updates.


6-9

Office SharePoint Server 2007 Content Management Components

Introduction Two of the key components that provide content management functionality in Office SharePoint Server 2007 are document libraries and workflows. These two components provide the repository and life cycle management for a document in a site. Office SharePoint Server 2007 provides document libraries and workflows through template sites and features. However, both document libraries and workflows are extensible, so you can create additional libraries and workflows to reflect your business requirements.

Content Libraries Document libraries are collections of files in Office SharePoint Server 2007 that you share with other site users. Most Office SharePoint Server 2007 document management features are delivered through document libraries. There are four available library types: •

Document library

•

Picture library

•

Form library

•

Wiki page library

A document library can hold different file types. Authorized users can create or upload files to the library, which makes them available to other site users. A library can hold a range of document types. However, when you create a new library, you can associate a

6-10


default document template with a document library. This means that a user who creates a new document from within the library is offered a document template. The following list details the available document templates: •

None

•

Microsoft Office Word 97-2003 document

•

Microsoft Office Excel® 97-2003 spreadsheet

•

Microsoft Office PowerPoint® 97-2003 presentation

•

Microsoft Office Word document

•

Microsoft Office Excel spreadsheet

•

Microsoft Office PowerPoint presentation

•

Microsoft Office OneNote® section

•

Microsoft Office SharePoint Designer Web page

•

Basic page

•

Web Part page

A library with a default document template of None can only store documents. You may find that grouping types together makes it easier for users to identify where document types are located. For example, if your organization produces a lot of Microsoft Office PowerPoint presentations, it may be easier if you collect these together in a single library. A picture library is designed to hold images. Although these could be held in a document library, a picture library provides slideshow views. Picture libraries also allow you to use any compatible editor to edit images. A form library holds business forms, such as those created in Microsoft Office InfoPath®. You should group forms together because they are often application or business-process specific. A wiki library is designed specifically for wiki style data, with a document template that offers you a browser-based editing interface. You can create other document libraries in a wiki site. Document libraries also have settings that you can use to configure workflows, schedules, policy, and permissions for a particular library. It is also possible to create additional columns to configure metadata that is associated with that document library.

Workflows Office SharePoint Server 2007 provides the facility to attach business process logic to content in the form of workflows. You can associate a workflow with a range of Office SharePoint Server 2007 elements, including document libraries, documents, or list items. A workflow can control many aspects of the life cycle of an item. You can create workflows that are as simple or complex as your business processes require, both


6-11

automatic and user initiated. There is a range of workflows shipped as part of the Office SharePoint Server 2007 feature set. Additionally, users can create workflows with Office SharePoint Designer 2007. Developers can use Windows® Workflow Foundation and the Microsoft Visual Studio® 2005 Extensions for Windows Workflow Foundation, which are described more fully later in this module.

6-12


Office SharePoint Server 2007 Content Management Features

Introduction Features provide groups of functions that you can activate or deactivate in your server farm, Web application, site collection, and site scopes. There are a number of content management-specific features that you must activate to implement approval, content types, and page layout publishing content management functions. The farm scope features are activated by default. Web application scope features deal with function sets, such as Office SharePoint Server Enterprise Web application features. You will typically activate them by default in a content management deployment, because these will enable content management functionality. The majority of content management-specific features are in the site collection scope.

Site Collection Feature Scope The site collection feature scope applies to all content management subsites that you create. Irrespective of whether you implement document management or publishing subsites, you must activate key workflow and management features. These features include the following: •

Office SharePoint Server Publishing Infrastructure. This provides centralized libraries, content types, master pages, and layouts. It also enables page scheduling and other publishing functionality for a site collection.

•

Office SharePoint Server Search Web Parts. This provides all the Web Parts you require for Search Center.


6-13

•

Disposition Approval Workflow. This manages document expiration and retention by allowing participants to decide whether to retain or delete expired documents.

•

Collect Signatures Workflow. This gathers the signatures needed to complete a Microsoft Office document.

•

Routing Workflow. This provides workflows that send a document for feedback or approval.

•

Three-State Workflow. This workflow tracks items in a list.

•

Translation Management Workflow. This manages document translation by creating copies of the document to be translated and assigning translation tasks to translators.

Site Feature Scope You must also ensure that the Office SharePoint Server Publishing feature is activated at the site scope. This creates a Web page library, and supporting libraries and publishing pages, based on page layouts.

6-14


Lesson 2: Managing Documents and Content with Office SharePoint Server 2007

Introduction Office SharePoint Server 2007 provides a rich content management environment. In addition to the wide range of template sites and Web browser authoring, you can organize and manage content based on your organization-specific content definitions and metadata. You can also extend your content management to include corporate e-mail.


Explain the use of content management templates in Microsoft Office SharePoint Server 2007.

•

Explain file types, content types, and the relationship between them.

•

Describe the different ways in which Office SharePoint Server 2007 supports the authoring process.

•

Explain how e-mails can be included in content management processes.

•

Describe how to interact with documents by using metadata and Document Actions.


6-15

Content Management Templates

Introduction Office SharePoint Server 2007 provides a range of content management templates for ECM and WCM. You can deploy these to create ready-to-use content management sites in your organization. The templates are grouped in the Enterprise and Publishing tabs in the Create Site Collection and Create Site pages. Default content and management elements, such as document libraries and workflows, are installed as standard.

Enterprise Content Management Templates The following table describes the available ECM templates. Site Collection Templates

Description

Document Center

This template provides an infrastructure site to centrally manage documents in your enterprise.

Records Center

This template creates a site designed for records management. Records managers can configure Office SharePoint Server 2007 to direct incoming files to specific locations. The site prevents records from being modified after they are added to the repository.

Publishing Templates The following table describes the available publishing templates: Site Collection Templates

Description

Collaboration Portal

This is a starter site hierarchy template for an intranet portal. It includes a home page, a News site, a Site Directory, a Document

6-16


Site Collection Templates

Description Center, and a Search Center with Tabs. Typically, this site has nearly as many contributors as readers, and you use it to host team sites.

Publishing Portal

This template provides an Internet-facing site or a large intranet portal. You can customize this site with distinctive branding easily. The site includes a home page, a sample press releases subsite, a Search Center, and a login page. Typically, this site has many more readers than contributors, and you use it to publish Web pages with approval workflows.

Site Templates

Description

Publishing Site with Workflow This template provides a site for publishing Web pages on a schedule by using approval workflows. It includes document and image libraries for storing Web publishing assets. By default, you can only create sites with this template in publishing site collections.


6-17

File Types and Content Types

Introduction A single content management site may hold a range of different file types, such as documents, images, and spreadsheets. However, you can also classify a file by its content type.

What Is a Content Type? A content type is a group of reusable settings that describe the shared behaviors for a specific type of content. Office SharePoint Server 2007 enables you to create different content types. For example, a document library or list may have a variety of file type inputs. You can group these file types in a content type and then manipulate and interrogate them together. Content types are not related to file types. A file type is defined in the application you use to create a file, such as Microsoft Office Excel. It is a common misconception to view file types and content types as interchangeable terms. Content types are hierarchical, so that one content type can inherit characteristics from another. They are defined in the Site Content Type Gallery of a site collection or a site. Site content types are available for use in any subsites of the site for which they have been defined. You can add content types at site collection or site level.

Content Type Options A content type can specify the following settings: •

The site columns (metadata) that you want to assign to items of this type.

6-18


•

The document template on which to base new items of this type.

•

The custom New, Edit, and Display forms to use with this content type.

•

The workflows available for items of this content type.

•

The custom solutions or features associated with items of this content type.

You can use content types to organize content across different libraries or lists in a site collection. For example, you can create a contract data type at the site collection level that you can reuse at site level. Content types can be used on multiple document libraries over many team sites, so you should create them at the highest level within the Office SharePoint 2007 system.

Content Type Configuration Settings When you create a new content type, you can configure a number of attributes, including the following: •

Name, description, and group.

•

Advanced settings. •

Document template.

•

Read-only option.

•

Update subsites (the default setting of this property is Yes).

•

Workflow settings.

•

Document Information Panel settings.

•

Information management policy settings.

•

Manage document conversion for this content type.

In addition to these settings, you can define metadata (columns) for the content type. You can reuse existing site columns or create new columns that reflect business requirements. You can then use this metadata within forms or workflows to help manage your content.


6-19

Authoring Content

Introduction Office SharePoint Server 2007 offers a rich and varied authoring experience. You can create content within the browser interface, Microsoft Office 2007 applications, or other compatible authoring applications.

Web Browser Authoring A site collection offers a number of page consistency options. These are detailed in the following table. Page Consistency Option

Description

Master page

The site collection can mandate Site Master Page layout for publishing pages, System Master Page layout for forms and lists, or an alternate style sheet if you have an internal branding standard that you wish to use.

Title, description, and icon

This enables you to change the title, description, or icons for your sites.

Navigation

You can specify whether to show subsites and pages in the navigation menu, how to sort navigation elements, and the navigation hierarchy. You can also hide navigation elements.

Page layouts and site templates

You can restrict or enlarge the range of subsite and page layout templates available to users. For example, you may not want users to create Redirect Pages, so you can remove this option from the list of available page layouts.

Welcome page

Allows you to specify a welcome page.

6-20


Page Consistency Option

Description

Tree view

Provides support for tree views and the Quick Launch option.

Site theme

You can theme your sites based on a range of color and style options available in Office SharePoint Server 2007.

The Web Browser Interface The Web browser interface provides a fully-functional authoring environment. You use the page creation options to define page layout. Page layout includes text, image, links, table of contents, and Web Part options. When you create a new page, you can add titles and descriptive text. You can use the Web browser to check the spelling of any text. You can then edit a page to include new text, images, links, or Web Parts. The text editor provides a broad range of authoring toolbar options, such as style, font, attribute, table, and image manipulation. You can use the image editor to specify image size and layout and to create hyperlinks from the image. You can perform all editing in an approval workflow. This ensures quality and consistency of work.

Office 2007 Client Application Authoring The term Smart Client Authoring describes the use of Office 2007 Client applications to author Web pages in Office SharePoint Server 2007. Many users prefer to create Web pages in familiar applications, such as Microsoft Office Word. Office SharePoint Server 2007 enables users to save documents in a document library and then convert the document to a Web page. On the Application Management site settings page, you can enable document conversion. This displays the document types that you can convert and the formats that you can convert them into. For example, you can convert Word Document to Web Page (docx into html) or XML to Web Page (xml into html). You can develop custom converters for file types not available in Office SharePoint Server 2007, to extend the conversion function.


6-21

Including E-Mails as Content

Introduction E-mail is an important form of business content. Your organization may therefore want to store e-mail in a managed content environment. Regulatory or statutory rules require businesses to maintain correspondence. Office SharePoint Server 2007 provides the facility to integrate e-mail within your content sites. As with other content formats, you can configure sites to automatically include e-mail submissions.

E-Mail Content Locations You can enable and configure the following lists and libraries to receive e-mails: •

Document libraries

•

Picture libraries

•

Forms

•

Blogs

•

Discussion boards

•

Announcements

•

Calendars

Incoming E-Mail Support In Central Administration, you can enable incoming e-mail support in Incoming E-mail Settings. This ensures that incoming e-mail is available for all site collections. You must

6-22


specify whether Microsoft SharePoint Directory Management Service provides advanced features, such as the creation and management of e-mail distribution groups from SharePoint sites. You must also define an incoming e-mail address and specify whether to accept e-mail from all e-mail servers or only from a named list.

E-Mail Library Settings By default, libraries and lists do not accept e-mails. In the Incoming E-mail Settings options of an individual library, you can enable incoming e-mail settings. In this setting page you must configure the following elements: •

A library e-mail address. This will take the SMTP mail server configured in Central Administration as the mail domain name.

•

E-mail attachment handling.

•

Meeting invitation handling.

•

E-mail security.

You can configure lists, such as an Announcement list, by using similar options.


6-23

Document Information and Actions

Introduction You can associate information with documents that you store in Office SharePoint Server 2007 repositories in the form of metadata. You can use this information to trigger or interact with workflows. You can integrate document information with the Document Information Panel available in Microsoft Office 2007 applications.

Document Information Because content types can be independent of file types, the same document information panel is displayed within each of the 2007 Microsoft Office system client applications. For example, if you assign the same content type to a Microsoft Office Word document and a Microsoft Office PowerPoint presentation, you still specify only one custom document information panel, which would be displayed in each application. You create new document information elements by creating a new column for a Document Library. This allows you to specify a range of metadata types and styles, including the following: •

Single line of text

•

Multiple lines of text

•

Choice (menu to choose from)

•

Number (1, 1.0, 100)

•

Currency ($, ¥, €)

6-24


•

Date and Time

•

Lookup (information already on this site)

•

Yes/No (check box)

•

Person or Group

•

Hyperlink or Picture

•

Calculated (calculation based on other columns)

•

Business data

These information types are associated with available Office SharePoint Server 2007 features. For example, you cannot create a Business Data information type for a document library unless the Office SharePoint Server Enterprise feature is activated for the site. The metadata is application independent. You can specify whether it is entered by the user or calculated. You can also stipulate that metadata is mandatory.

Document Actions Windows SharePoint Services 3.0 provides a set of standard actions that you can perform on the files stored in document libraries. For example, information workers might use the Check Out action to lock a file for editing. They can then use the Check In action to update the file with their recent changes and unlock it so that it can be edited by other users. Office SharePoint Server 2007 provides additional actions, depending on the features that you have enabled for the library. For example, if you have created a Records Repository site that manages document retention and expiration policies, an information worker (or a workflow) can use the Send To action to move a file to the repository. Additionally, you can create additional document actions for a library. For example, if your solution integrates with a third-party document management system, you can create an action for sending files to that external system.


6-25

Lesson 3: Implementing Content Management Processes

Introduction You can manage the life cycle of your business content by using integral workflows in Office SharePoint Server 2007. For organizations that require unique workflows, there are wizard-driven or programmatic solutions available, which integrate seamlessly with Office SharePoint Server 2007. These facilities allow all companies to adopt a managed approach to content publishing and records management.


Describe how to manage content-based Web publishing and deployment.

•

Explain how to create advanced authoring and approval processes.

•

Explain how to implement standard authoring and approval processes.

6-26


Implementing Standard Authoring and Approval Processes

Introduction Office SharePoint Server 2007 provides built-in authoring and approval workflow processes. This means that you do not have to specify or design your own requirements to take advantage of the business benefits of an approval model.

Available Workflows When you activate the content management site collection features, you can use the following site collection workflows: •

Approval

•

Collect Feedback

•

Collect Signatures

•

Disposition Approval

•

Three-State

•

Translation Management

You can easily change these through the browser to create serial or parallel workflows reporting. On the Site Collection Workflows page of Site Settings, you can review active and inactive site collection workflows. The active workflows are available for all content management sites within the site collection. In Site Collection Settings, in the Workflows option, you can review the available workflows. You cannot change available workflows here.


6-27

Creating Advanced Authoring and Approval Processes

Introduction Processes are often specific to an individual company. You can create more sophisticated workflows for Office SharePoint Server 2007 by using associated workflow development environments, including the following: •

SharePoint Designer 2007.

•

Microsoft Visual Studio 2005 Custom Workflows.

The ability to develop extensible workflows provides a robust platform for providing business benefit to an organization. More complex or multi-system workflows may require programmatic development tools. However, it is often beneficial to allow users to develop business workflows within a wizard. Both of these options are available for Office SharePoint Server 2007.

SharePoint Designer 2007 SharePoint Designer 2007 provides you with a wizard-driven environment to design workflows that associate business logic with document libraries or lists. SharePoint Designer does more than create workflows. You can also create pages, Web sites, content, HTML, and other Web related files. A workflow can be initiated manually, automatically when a new item is created, and automatically when an item is changed. A user can be prompted for initiation information if necessary.

6-28


The stages in the workflow are called steps in SharePoint Designer 2007. These can be dependent on a custom condition, such as file type created on a specific date. You can create custom conditions that allow you to trigger the workflow if the condition status is met. For example, the workflow may run if the Approval Status equals Pending for the item. When a condition is true, you can initiate an action, such as sending an e-mail or creating a task in a task list. The workflow allows you to include variables. You can include additional steps or branches, called Else If branches. Workflow Designer 2007 validates the workflow, associates it, and saves it back to Office SharePoint Server 2007 in the workflows available for the site.

Microsoft Visual Studio 2005 Custom Workflows The Microsoft Visual Studio 2005 Extensions for Windows Workflow Foundation provides developers with a visual designer. This uses the Visual Studio user interface for the graphical construction and debugging of workflow applications, based on the Windows Workflow Foundation engine. Windows Workflow Foundation provides a fully-functional workflow development environment for developers. This includes full support for Microsoft Visual Basic® and Microsoft Visual C#®, debugging, a graphical workflow designer, and the ability to develop workflows in code. Windows Workflow Foundation describes the stages in a workflow as activities. Each workflow is an instance that runs on a single workflow engine for each application domain. Windows Workflow Foundation provides programmatically configurable exception handling, workflow tracking, workflow serialization, and dynamic, runtime updates.


6-29

Guidelines for Content-Based Web Publishing and Deployment

Introduction The use of a multi-tier content deployment strategy is common in most large Internet Web site development scenarios. This may include a three-tier structure of a development, staging, and production hierarchy. This provides a secure (internal) environment for authors and an Internet-facing production environment, beyond a demilitarized zone. The staging environment replicates the production infrastructure, but within the internal security setting. Smaller implementations may use a two-tier authoring and production setup.

Content Deployment Office SharePoint Server 2007 provides content deployment features that allow you to push content from one site collection to another on different server farms. The configuration of the content deployment functionality is set at the server farm level. On the Site Settings page, you can configure the content deployment settings and define paths for content movement. On the Content Deployment Settings page, you can configure the following options for the farm: •

Acceptance of content deployment jobs.

•

An import server name.

•

An export server name.

•

Use of encryption.

6-30


•

A temporary file location.

•

The number of content deployment reports to maintain.

On the Manage Content Deployment Paths and Jobs page, you can create content deployment paths. Here you specify the source Web application and site collection, the URL of the destination Central Administration Web Application, authentication information, and the destination Web application and site collection. When you create a path, you must associate a job or a series of jobs with the path. The job defines the specific sites to deploy and the automated deployment schedule. In a scenario with a three-tier hierarchy, you create another path and job from the second to the third tier. Content deployment automatically picks up the dependent page layout and packages it up along with the page. Should an emergency deployment be necessary, such as an important press release or a correction to content, you can use a job called Quick Deploy, which is automatically created for each path. The Quick Deploy link is located on the Page Editing toolbar for a site owner. This facility can be extended beyond the owner by adding users to the Quick Deploy User group.


6-31

Lab: Implementing Content Management Sites and Processes


Create content management sites.

•

Manage authoring workflows and processes.




•


Lab Scenario Litware, Inc. has found that there are an increasing number of departmental and team Web sites appearing on their intranet. These sites sometimes have outdated or erroneous information, which is causing confusion within the company. To alleviate this situation, the company has decided to implement content management for publishing and document management. It is essential that these are available quickly. Your task is to use Office

6-32


SharePoint Server 2007 templates to create a site collection and a site for document management and publishing.


6-33

Exercise 1: Create Content Management Sites In this exercise, you will create two content management sites. The principal tasks for this exercise are as follows:

f

•

Create two site collections for content management sites.

•

Create two content management sites.

•

Manage the available features and workflows for the sites.

Create a publishing site collection and site for the Sales Group Tasks

Detailed Steps

1.

•

On the Start menu, point to All Programs, point to Microsoft Office Server, and then click SharePoint 3.0 Central Administration. Internet Explorer appears, and the Central Administration Web page is displayed.

•

On the Central Administration page, click the Application Management tab.

•

Under SharePoint Site Management, click Create site collection.

•

In the Web Application section, click http://litwareportal:18097/ and then click Change Web Application.

•


•

In the Title box, type Sales Publishing

•

In the Description box, type Sales Publishing Site Collection

•

In the Web Site Address section, click /sites/ in the list. Then type SalesPub in the adjacent text box.

•

In the Select a template list, click the Publishing tab.

•

Click Publishing Portal.

•

In the Primary Site Collection Administrator area, in the User name box, type LitwareInc\Administrator, and then click OK.

•

When the Top-Level Site Successfully Created page appears, click the http://litwareportal/sites/SalesPub link.

•

On the Sales Publishing page, click Site Actions and then click Create Site.

•

In the Title box, type Sales Process

•

In the Description box, type Sales Workflow Site

•

In the URL name box, type SalesProc

•

In the Select a template list, click Publishing Site with Workflow and then click Create.

2.

f

Create a publishing site collection for the Sales team.

Create a publishing site or the Sales team.

Create a document management site collection and site for the Marketing Group Tasks

Detailed Steps

1.

•

Switch to the Central Administration page in Internet Explorer.

•


Create a document center site collection for the

6-34


Tasks Marketing department.

2.

Create a document center for Marketing documents.

Detailed Steps •

In the SharePoint Site Management area, click Create site collection.

•

In the Title box, type Marketing Document Center

•

In the Description box, type Marketing Document Center Site Collection

•

In the URL list, click /sites/, and then type MDCSC in the box to complete the URL path.

•

In the Select a template list, click the Enterprise tab.

•

Click Document Center.

•

In the Primary Site Collection Administrator area, in the User name box, type LitwareInc\Administrator, and then click OK.

•

When the Top-Level Site Successfully Created page appears, click the http://litwareportal/sites/MDCSC link.

•

On the Marketing Document Center page, click Site Actions, and then click Create.

•

In the Web Pages list, click Sites and Workplaces.

•

In the Title box, type Marketing Documents

•

In the Description box, type Marketing Document Site

•

In the URL name box, type MarketingDocs

•

In the Select a template list, click Team Site, and then click Create.

•

When the site has been created, close all instances of Internet Explorer.


6-35

Exercise 2: Managing Authoring Workflows and Processes In this exercise, you will manage the authoring workflow for the Sales publishing site. The principal tasks for this exercise are as follows:

f

•

Manage the available features for the Sales publishing site.

•

Test the availability of the standard authoring and approval workflow.

•

Create a custom workflow by using Office SharePoint Designer.

Manage the available features and workflows for the Sales publishing site Tasks

Detailed Steps

1.

•

Start Internet Explorer.

•

In the Address bar, type http://litwareportal/sites/SalesPub and then press ENTER.

•

Click Site Actions, point to Site Settings, and then click Modify All Site Settings.

•

In the Site Collection Administration list, click Site collection features.

•

Review the activation status of the following items:

2.

Check available site collection workflows.

Check the availability of the standard authoring and approval workflow.

•

Collect Signature Workflow.

•

Disposition Approval Workflow.

•

Routing Workflows.

•

Three-state workflow.

•

Translation Management Workflow.

•

Click Activate for Three-state workflow.

•

Click Deactivate for Translation Management Workflow.

•

On the Warning page, click Deactivate this feature.

•

Click Site Actions, point to Site Settings, and then click Modify All Site Settings.

•

In the Galleries section, click Workflows.

•

In the Site Collection Workflows section check that all workflows are Active, except for Translation Management.

•

On the Site Collection Workflows page, click the Sales Process tab.

•

Near the top of the page, click Edit Page.

•

In the Page Content section, click Edit Content.

•

Type Welcome to the Sales Content Publishing Process Site!

•

Near the top of the page, click Check In to Share Draft, and then click Submit for Approval.

•

In the Type a message to include with your request box, type Please review as soon as possible.

•

Near the bottom of the page, click Start.

•

Click Site Actions, point to View Reports, and then click Pending Approval.

6-36


Tasks

f

Detailed Steps •

Point to default.aspx, and then in the dropdown list, click Approve.

•

In the Approve -- Web Page Dialog dialog box, click OK.

•

In the Type comments to include with your response box, type Approved! and then click Approve.

•

In the Address bar, type http://litwareportal/sites/SalesPub/SalesProc and then press ENTER. The page has been approved and published.

Create a custom workflow by using Office SharePoint Designer Tasks

Detailed Steps

1.

•

In the Address bar, type http://litwareportal/sites/MDCSC and then press ENTER.

•

On the Site Actions menu, click Site Settings.

•

In the Users and Permissions section, click People and groups.

•

Click New.

•

In the Users/Groups box, type LitwareInc\Student, and then click OK.

•

Click the Home tab.

•

On the File menu, click Edit with Microsoft Office SharePoint Designer. After a few seconds, the page is loaded in the Microsoft Office SharePoint Designer application.

•

When the page has completely loaded, on the File menu, point to New, and then click Workflow.

2.

Add the Student user to the Marketing Document Center Site Collection.

Create a new custom workflow for managing the document proof process.

Note: it may take a short time before the page loads completely. Until it has loaded, the New menu item will be unavailable. •

In the Give a name to this workflow box, type Handoff for Proof

•

In the What SharePoint list should this workflow be attached to? list, click Documents.

•

Click Next.

•

In the Step Name box, type Assign Proof Task

•

Click Actions, and then click Assign a To-do Item.

•

Click a to-do item.

•

In the Custom Task Wizard, click Next.

•

In the Name box, type Ready for Proof, and then click Finish.

•

Click these users.

•

In the Or select from existing Users and Groups list, click LITWAREINC\student, click Add>>, and then click OK.

•

Click Actions, and then click Send an Email.

•

Click this message.

•

In the To box, type [email protected]

•

In the Subject box, type Ready for proof

•

Click Add Lookup to Body.


Tasks

3.

Test the new custom workflow for managing the document proof process

6-37

Detailed Steps •

In the Source list, ensure that Current Item is selected.

•

In the Field list, click Name, and then click OK.

•

Click to the right of the field that has just been inserted, and then press SPACE.

•

Type is ready for proof. The document is located:

•

Click Add Lookup to Body.

•

In the Source list, ensure that Current Item is selected.

•

In the Field list, click Type (icon linked to document), and then click OK.

•

Click OK, and then click Finish. The workflow is validated and saved.

•

Close Microsoft Office SharePoint Designer.

•

In the left navigation section, click Documents.

•

On the New menu, click Document.

•

In the Microsoft Internet Explorer dialog box, click OK. Microsoft Word appears.

•

Type My first document.

•


•

In the Save As dialog box, click Save.

•


•

In the second Microsoft Office Word dialog box, click OK.

•


•

Close Microsoft Word. In the Microsoft Office Word dialog box, click Yes.

•

In the Check In dialog box, in the Version Comments box, type Ready for first proof pass, and then click OK. After a few seconds, the document appears on the Documents page in Internet Explorer.

•

Point to My first document, and in the dropdown list that appears, click Workflows.

•

In the Start a New Workflow section, click Handoff for Proof.

•

On the Handoff for Proof page, click Start.

•

In the left navigation section, click Tasks. Notice that a new task has been created and assigned to the Student user. In a real environment, the Student user will also have received an email with a link to the document that requires a proof pass.

•

Click Ready for Proof.

•

Click Edit Item. Notice that the task includes a link to the document that requires a proof pass.

•

Click Cancel, and then close Internet Explorer.

Important: After you complete the lab, you must leave the 5061A_LON-DC-01-06 virtual machine running; you will continue with the virtual machine in the next lab.

6-38


Lesson 4: Implementing Content Management Policies

Introduction Office SharePoint Server 2007 includes a specialized template for records repository sites. A records repository is a site where you can store and audit content. Records managers can configure a routing table to direct incoming files to specific locations. The site prevents records from being modified after they are added to the repository. The records repository is the core element of a records management solution and provides functionality that enables you to implement and automate many aspects of your corporate policy.


Describe the key content management issues that organizations must address.

•

Explain how to create and enforce content policies.

•

Describe records repository sites and templates.

•

Explain the advantages of, and the process for implementing, managed mail folders as records repositories.


6-39

Overview of Enterprise Content Management Issues

Compliance Every organization is subject to information management regulations of some description. Your precise legal obligations will vary according to your industry and your trading location. The following table summarizes some of the more common compliance requirements. Legislation

What it Requires

Sarbanes-Oxley

The Sarbanes-Oxley Act requires publicly-traded companies to demonstrate that they have controls in place to ensure the privacy and integrity of their financial data. External auditors must attest that financial data is protected from alteration and unauthorized access as it moves through the organization.

SB 1386

SB 1386 is a California State bill that applies to any company that does business in the state of California. Companies must ensure that personal information about customers is adequately protected, and that any breaches of confidentiality are disclosed to the affected individuals in a timely manner.

GLBA

The Gramm-Leachy Bliley Act (GLBA) applies to all financial institutions and financial services providers. Such companies must implement various safeguards to ensure the integrity and confidentiality of customer information.

The Data Protection Act (DPA)

This 1998 British law regulates the processing of information relating to individuals, including the obtaining, holding, use, expiration, or disclosure of such information. Organizations must prove compliance with DPA requirements.

6-40


Typical Requirements The legal obligations and information management goals of typical organizations create a number of broad record management requirements. A typical record management solution must address the following issues: •

Maintain the confidentiality and integrity of sensitive information.

•

Ensure the privacy of sensitive information with access controls.

•

Ensure the availability of critical information to authorized users.

•

Enable the auditing of access to sensitive information.

•

Ensure that regulated and critical information is retained for a specified period of time.

•

Discard information that is of no further use or which must be destroyed in compliance with regulations.

Content Growth The volume of content developed and consumed in enterprise organizations has increased exponentially since the advent of the Internet, extranets, and intranets. Much of this information comes from the so called “inadvertent publishers.” All companies can encounter this scenario. However, large enterprise organizations have large populations and the effect on IT resources such as infrastructure and support staff can represent a significant cost. Much of the published content is also relatively unstructured. In line with the growth in the volume of information, there has been an increase in the number of file types associated with business projects. Users demand filter and search facilities that offer criteria that can associate disparate file types. The potential for content chaos is clear. Because the content is business information, it is essential that organizations provide a version-managed infrastructure that provides integration across business platforms and a secure and easy-to-use environment.


6-41

Creating and Enforcing Content Policies

Introduction Policies specify how documents are managed in your server farm, Web applications, site collections, and sites. The server farm-level policy specifies the options that are available to Web applications, site collections and sites. The four possible options are: •

Labels

•

Auditing

•

Expiration

•

Barcodes

You do not specify actions for these policy areas at the server farm level; you specify them at the site collection and site levels.

Web Application Policy The Web application policy manages access-level security. You can create policies to grant full access, read-only access, deny write access, or deny all access to a user or group, at a Web application level. You grant this policy to all sites in the Web application, and it overrides any permissions established in individual site elements. You can create alternative zones with which a Web application is associated, such as an intranet or extranet. You can use different authentication methods for different zones, such as NTLM or forms.

6-42


Site Collection and Site Policies Policies for sites and site collections set actions and limits on labels, auditing, expiration, and barcodes. You can create policies from the Site Settings page. A policy must have a name and description, and you can provide a Policy Statement that outlines the rationale of the policy. You can enable each of the policy areas individually. You can use each of the policy areas as described in the following table. Policy Area

Description

Labels

You can add a label to a document to ensure that important information about the document is included when it is printed. To specify the label, type the text you want to use in the Label format box. Alternatively, the user is prompted for the label text before saving or printing. You can also specify a label format to place restrictions on the label text or to include document properties. A label format cannot include calculated or built-in properties. To ensure that labels are appropriate, you can set font, style, point size, and justification for text, as well as the physical size of the label.

Auditing

You can specify the events that are audited for documents and items subject to a policy when you enable auditing. These events include when users: •

Open or download documents, viewing items in lists, or viewing item properties.

•

Edit items.

•

Check out or check in items.

•

Move or copy items to another location in the site.

•

Delete or restore items.

Expiration

You can use the expiration policy to schedule content disposition to comply with regulatory requirements. You specify the retention period for content and the action to take when content reaches its expiration date. This retention period can be a number of days, months, or years from when the content was created or last modified. When the content reaches this date, you can set an action to execute, such as delete, or you can initiate a workflow.

Barcodes

If your Office SharePoint Server 2007 solution requires barcodes, you can assign a barcode to each document or item. You can also configure Microsoft Office applications to require users to insert these barcodes into documents.


6-43

Designing and Implementing Records Repositories

Introduction The legislative and regulatory demands on enterprise organizations to retain business records have increased reliance on content management solutions. Records compliance demands that an organization can produce records and their information management history. You must have policies that dictate how the organization manages content records. Clearly these requirements are well suited to a content management solution.

Records Repository Template Office SharePoint Server 2007 provides a records repository in the Records Center site. This site template offers a range of ECM capabilities, which includes the following. Capability

Description

Vault Capabilities

The Records Center has several features that help ensure the integrity of the records stored within it, including the following:

Information Management Policy Enforcement

•

Records are never automatically modified by the system.

•

Site administrators can configure the Records Center to maintain versions of records to prevent unauthorized changes.

•

Division of data from metadata, which ensures that the core record is not changed, even when it is necessary to add metadata for analysis or management purposes. Changes to metadata are also versioned.

•

Auditing, which logs use of or changes to records together with information on the user who has accessed the record.

•

Disposition, which uses approval workflows to manage record

6-44


Capability

Description existence for definable periods. •

Barcodes, which can provide records with a unique barcode image and numeric value.

Record collection programmable interface

You can configure automatic submission of files to the site for documents and e-mail.

Record routing

You can automate record reconciliation to the correct location based on content type.

Hold

You can lock, or hold, records that are under investigation so that they cannot be changed, deleted, or expired.

Designing a Records Repository When you design a records management solution, the most important planning task is to complete a file plan. The file plan identifies, categorizes, and describes the requirements of each type of record and effectively determines the structure of the records repository. The file plan is usually completed with input from legal advisors and board-level approval because of the business-critical nature of records management and compliance. When you complete the file plan, you can design the structure of the records repository site. You configure metadata, retention policies, and audit policies at the document library level. This means that you should create a document library for each type of record. Microsoft provides planning worksheets to assist you in the design process, such as the Document Library for Retaining Records worksheet, the Policy worksheet, and the Records Routing Table worksheet.

Creating a Records Repository Office SharePoint Server 2007 provides a Records Repository site template. You should choose a suitable title, description, and URL for your site and then use the site template to create the site. When you have created the records repository site, the next step is to create a document library for each record type that you require. You can add columns to each document library to store the metadata required by the corresponding content type. You can specify whether a particular column must contain information. You should configure the policy settings of each document library to audit retention and disposition activities as specified in the file plan.

Configuring Records Routing The records repository site includes a record routing table. This enables you to specify which document library should receive incoming records, based on the metadata supplied with the record. Unallocated records can be routed to a dedicated holding library. When this happens, the originating user is sent a secure Web link and prompted to provide the missing metadata.


6-45

Implementing Managed Mail Folders as a Records Repository

Introduction You can use Office SharePoint Server 2007 to extend records management solutions to all types of records, rather than just electronic document records. The increase in business information held in e-mails, together with the requirement for e-mail records management, makes it essential for many organizations to management e-mail content in a more robust content management engine than the mail server application.

E-Mails Microsoft Exchange Server 2007 enables administrators to push managed folders to user inboxes by using records management policies. These managed folders can be associated with records repository sites in Office SharePoint Server 2007. The user adds related email folders and these e-mails are sent to the records repository site by using SMTP. You can use custom programs that interface with the Windows SharePoint Services object model to route e-mail from other e-mail servers to the record repository site.

E-Mail Routing You can configure connections between Exchange Server 2007 servers and the records repository site. The records repository site treats e-mails like other records. It routes incoming e-mails to a document library according to the information that you provide in the records routing table.

6-46


Integration with Exchange Server 2007 Exchange Server 2007 includes various records management features. Your Exchange administrator can create managed folders and push these folders to user mailboxes. Managed folders are typically associated with a specific type of content or business area, such as finance or sales. You can assign policies to these managed folders, such as retention and disposition schedules. Users can manually manage the process of adding incoming e-mail to the appropriate folder. Alternatively, you can create rules to automate this process. These rules might allocate the e-mail to a folder based on an e-mail attribute, such as the sender address. However, to achieve a centralized records management solution, you should connect your Exchange Server 2007 managed folders to your records repository site. This will enable you to administer a single set of records management policies on a single platform. You can use SMTP to automatically route e-mail records from a particular managed folder to the records repository site. You must create entries in the records repository routing table that identify the correct document library for incoming e-mail records. You can apply policies such as retention, expiration, and audit to these e-mail records in the same way that you would for any other record. The Exchange administrator must also configure the SMTP service to route e-mail to Office SharePoint Server 2007.


6-47

Lab: Implementing Auditing and Policies


Produce a high-level plan for a records management solution.

•

Implement and configure a records management solution.


Lab Setup For this lab, you will use the virtual machine from the previous lab in this module.

Lab Scenario Litware, Inc. is growing very quickly and needs to manage increasingly large numbers of electronic records, including contracts, financial reports, and invoices. These must be retained for fixed periods of time, under carefully controlled conditions, to comply with legal regulations and company policy. One of the key organizational goals for the new ECM system is to manage the retention and audit of these records. The Chief Information Officer, supported by the legal department, has produced a file plan that identifies which Litware, Inc documents should be retained as records and how each record type should be managed. Your task is to plan and design a records repository site that implements the file plan. You will also use the Litware, Inc. test portal to try out your records repository site design.

6-48


Exercise 1: Planning Records Management Solutions In this exercise, you will plan a records repository site by completing planning worksheets. These worksheets are based on a file plan anda memo on legal issues. The principal tasks for this exercise are as follows:

f

•

Analyze the file plan and the auditing requirements.

•

Plan the Invoices document library.

•

Plan the Contracts document library.

•

Plan the routing table entries for the Invoices and Contracts record types.

Analyze the file plan and the auditing requirements Tasks

Detailed Steps

1.

•

Open Windows Explorer and browse to the E:\Labfiles\Lab06\Starter folder.

•

Double-click LitwareFilePlan.docx. In the Microsoft Office Word dialog box, click OK. The document opens in Microsoft Word.

•

Read the LitwareFilePlan.docx document carefully. Ensure that you understand the requirements for each record type.

•

Using Windows Explorer, browse to the E:\Labfiles\Lab06\Starter folder.

•

Double-click LitwareAuditoryRequirements.docx. In the Microsoft Office Word dialog box, click OK. The document opens in Microsoft Word.

•

Read the LitwareAuditoryRequirements.docx document carefully. Ensure that you understand the requirements for each record type.

2.

f

Study the file plan.

Review the auditing requirements.

Plan the Invoices document library Tasks

Detailed Steps

1.

•


•

Double-click DocumentLibraryForRetainingRecordsWorksheet.docx. In the Microsoft Office Word dialog box, click OK. The document opens in Microsoft Word.

•

Use the information in the file plan and the auditing requirements to complete the Document Library for Retaining Records Worksheet the Invoices record type.

•

Save your completed worksheet in the E:\Labfiles\Lab06\Starter folder with the file name InvoicesDocumentLibrary.docx. In the Microsoft Office Word dialog box, click OK.

•

Using Windows Explorer, browse to the E:\Labfiles\Lab06\Solution folder.

•

Double-click InvoicesDocumentLibrary.docx. In the Microsoft Office Word dialog box, click OK.

2.

Complete the Document Library for Retaining Records worksheet for the Invoices record type.

Compare your completed worksheet to the sample solution.


Tasks

6-49

Detailed Steps The document opens in Microsoft Word.

f

•

Compare the worksheet with the one completed in the previous task.

•

Discuss the differences or similarities between the two worksheets with your lab partner.

•


Plan the Contracts document library Tasks

Detailed Steps

1.

•


•

Double-click DocumentLibraryForRetainingRecordsWorksheet.docx. In the Microsoft Office Word dialog box, click OK. The document opens in Microsoft Word.

•

Use the information in the file plan and the auditing requirements to complete the Document Library for Retaining Records Worksheet for the Contracts record type.

•

Save your completed worksheet in the E:\Labfiles\Lab06\Starter folder with the file name ContractsDocumentLibrary.docx. In the Microsoft Office Word dialog box, click OK.

•

Using Windows Explorer, browse to the E:\Labfiles\Lab06\Solution folder.

•

Double-click ContractsDocumentLibrary.docx. In the Microsoft Office Word dialog box, click OK. The document opens in Microsoft Word.

•

Compare the worksheet with the one you completed in the previous task.

•

Discuss the differences or similarities between the two worksheets with your lab partner.

•

Close all documents, and exit Microsoft Office Word, without saving any changes.

2.

Complete the Document Library for Retaining Records worksheet for the Contracts record type.

Compare your completed worksheet to the sample solution.

6-50


Exercise 2: Implementing Records Management Solutions In this exercise, you will implement a records repository site based on the worksheets you completed in the previous exercise. The Litware, Inc test portal uses a Document Center with two content types, Contract and Invoice. You will use these content types to test your records management configuration. The principal tasks for this exercise are:

f

f

•

Create the records repository site.

•

Create content types.

•

Implement the file plan.

•

Configure the records routing table.

•

Configure the Web application to use the records repository site.

•

Test the records routing functionality.

Create the records repository site Tasks

Detailed Steps

1.

•

Start Internet Explorer and browse to http://litwareportal. The Home page appears.

•

On the Site Actions menu, click Create Site.

•

In the Title box, type Records

•

In the Description box, type Records management site

•

In the URL name box, type records

•

In the Select a template list, click the Enterprise tab, and then click Records Center.

•

Click Create. The records repository site is created.

Create the records repository site.

Create content types for Invoices and Contracts Tasks 1.

Detailed Steps

Create the records content • types. •

Click the Document Center tab. On the Site Actions menu, click Site Settings.

•

In the Galleries section, click Site content types.

•

Click Create.

•

In the Name box, type Contract

•

In the Select parent content type from list, click Document Content Types.

•

In the Parent Content Type list, click Document, and then click OK.

•

On the Site Actions menu, click Site Settings.

•

In the Galleries section, click Site content types.

•

Click Create.

•

In the Name box, type Invoice


Tasks

f

6-51

Detailed Steps •

In the Select parent content type from list, click Document Content Types.

•

In the Parent Content Type list, click Document, and then click OK.

•


•


•

On the Settings menu, click Document Library Settings.

•

In the Content Types section, click Add from existing site content types.

•

In the Available Site Content Types list, click Contract, hold the CTRL key down and then click Invoice.

•

Click Add>> and then click OK.

Implement the file plan Tasks

Detailed Steps

1.

•

Click the Records tab.

•

On the Site Actions menu, click Create.

•

On the Create page, in the Libraries section, click Document Library.

•

In the Name box, type Contracts

•

In the Description box, type Customer contracts

•

Under Create a version each time you edit a file in this document library, click Yes.

•

In the Document Template list, click None.

•

Click Create. The Contracts document library is added to the records repository site.

•

On the Contracts document library tool bar, on the Settings menu, click Create Column.

•

In the Column name box, type Customer

•

Under Require that this column contains information, click Yes and then click OK.

•

On the Settings menu, click Create Column.

•

In the Column name box, type Expiry Date

•

Select Date and Time.

•


•

On the Contracts document library tool bar, on the Settings menu, click Document Library Settings.

•

In the Permissions and Management section, click Information management policy settings.

•

Select Define a policy, and then click OK.

•

On the Edit Policy: Document page, in the Auditing section, select Enable Auditing.

•

Select Editing items and Deleting or restoring items.

2.

3.

Create the Contracts document library.

Add columns to the Contracts document library to store metadata.

Configure the policy settings for the Contracts document library.

6-52


Tasks

4.

5.

6.

Create the Invoices document library.

Add columns to the Invoices document library to store metadata.

Configure the policy settings for the Invoices document library.

Detailed Steps •

In the Expiration section, select Enable Expiration.

•

Select A time period based on the item’s properties, and then set the retention period to Expiry Date + 7 years.

•

Under When the item expires, select Perform this action, ensure Delete is selected in the list, and then click OK.

•

On the Site Actions menu, click Create.

•

On the Create page, in the Libraries section, click Document Library.

•

In the Name box, type Invoices

•

In the Description box, type Invoices received from suppliers

•

Under Create a version each time you edit a file in this document library, click Yes.

•

In the Document Template list, click None.

•

Click Create. The Invoices document library is added to the records repository site.

•

On the Invoices document library tool bar, on the Settings menu, click Create Column.

•

In the Column name box, type Supplier

•

Under Require that this column contains information, click Yes.

•

Click OK.

•

On the Settings menu, click Create Column.

•

In the Column name box, type Date Paid

•

Select Date and Time.

•


•

On the Settings menu, click Document Library Settings.

•

In the Permissions and Management section, click Information management policy settings.

•

Select the Define a policy option, and then click OK.

•

On the Edit Policy: Document page, in the Auditing section, select Enable Auditing.

•

Select Opening or downloading documents, viewing items in lists, or viewing item properties.

•

In the Expiration section, select Enable Expiration.

•

Select A time period based on the item’s properties, and then set the retention period to Date Paid + 7 years.

•

Under When the item expires, select Perform this action, ensure Delete is selected in the list, and then click OK.

•


•

Click the Records tab.


f

Configure the records routing table Tasks

Detailed Steps

1.

•

On the Records page, in the Record Routing Web Part, click New.

•

On the Record Routing: New Item page, in the Title box, type Contract.

•

In the Location box, type Contracts.

•

In the Aliases box, type Agreement and then click OK.

•

On the Record page, in the Record Routing Web Part, click New.

•

On the Record Routing: New Item page, in the Title box, type Invoice.

•

In the Location box, type Invoices.

2.

f

f

6-53

Add a routing table entry for contracts.

Add a routing table entry for invoices.

•

In the Aliases box, type Bill/Demand and then click OK.

•


Configure the Web application to use the records repository site Tasks

Detailed Steps

1.

•

Click Start, and then click SharePoint 3.0 Central Administration.

•


•

On the Application Management page, under External Service Connections, click Records center.

•

Select the Connect to a Records Center option.

•

In the URL box, type http://litwareportal/records/_vti_bin/officialfile.asmx

•

In the Display name box, type Official Files and then click OK.

Configure the Web application to use the records repository site.

Test the records routing functionality Tasks

Detailed Steps

1.

•

Browse to http://litwareportal.

•

Click the Document Center tab

•


•

On the New menu, click Contract.

•


•

In the blank document, type Test Contract

•


•


•


•


•


•

Close Microsoft Word.

•

In the Microsoft Office Word dialog box, click Yes.

•

In the Check In dialog box, click OK.

Add a contract and an invoice to the Document Center.

6-54


Tasks

2.

3.

Route the contract and the Invoice to the records repository site.

Detailed Steps •

The Test Contract document appears in the Documents library.

•

On the New menu, click Invoice.

•


•

In the blank document, type Test Invoice

•


•


•


•


•


•

Close Microsoft Word.

•

In the Microsoft Office Word dialog box, click Yes.

•

In the Check In dialog box, click OK.

•

The Test Invoice document appears in the Documents library.

•

Point to the Test Contract document.

•

In the dropdown list that appears, point to Send To, and then click Official Files.

•

In the Customer box, type Contoso

•

Next to the Expiry Date box, click Select a date from the calendar.

•

Click today’s date, and then click OK.

•

On the Operation Completed page, click OK.

•

Point to the Test Invoice document.

•

In the dropdown list that appears, point to Send To, and then click Offical Files.

•

In the Supplier box, type Adventure Works

•

Next to the Date Paid box, click Select a date from the calendar.

•

Click today’s date, and then click OK.

•

On the Operation Completed page, click OK.

Verify that the contract and • invoice have been routed • correctly. •

Click the Records tab. In the left navigation section, click Contracts. Click the folder in the library.

•

Verify that a record for the Test Contract.docx has been added to the Contracts document library.

•

In the left navigation section, click Invoices.

•

Click the folder in the library.

•

Verify that a record for Test Invoice.docx has been added to the Invoices document library.

•




6-55

6-56


Review


Describe the basics of the content management process and explain how various parts of these processes are implemented in Office SharePoint Server 2007 solutions.

•

Describe content and document-management concepts and processes in Office SharePoint Server 2007 solutions.

•

Implement standard and advanced content management processes.

•

Implement the advanced features of Office SharePoint Server 2007 that enable robust policies and auditing for enterprise-level content management.

Office SharePoint Server 2007 offers a range of packaged content management solutions including site templates, features, and workflows. You can extend all of these components by using wizards or programmatic tools. The scalable site templates provided in Office SharePoint Server 2007 make ECM or WCM simpler to implement and use.

Review Questions What is the difference between ECM and WCM? Which of the content management template sites do you think are most appropriate for your organization?

Module 7: Implementing Business Intelligence Solutions Table of Contents Overview 7-1 Lesson 1: Configuring and Incorporating Business Data Catalog Applications into Portal Solutions 7-2 Lesson 2: Implementing Microsoft Office SharePoint Server 2007 Excel Services 7-8 Lesson 3: Implementing Business Intelligence Dashboards 7-13 Lesson 4: Creating Report Center Web Sites 7-19 Lesson 5: Implementing Microsoft Office SharePoint Server 2007 Forms Server 7-24 Lab: Implementing Business Intelligence Solutions with Microsoft Office SharePoint Server 2007 7-27 Lab Shutdown 7-40 Review 7-41


Module 7: Implementing Business Intelligence Solutions

7-1

Overview

Microsoft® Office SharePoint® Server 2007 provides many features that can help you to implement robust and useful business intelligence solutions.


Describe the key part that the Business Data Catalog plays in Office SharePoint Server 2007-based solutions, and describe the process of creating Business Data Catalog applications.

•

Describe the features and capabilities of Excel Services, and explain how they contribute to business intelligence solutions.

•

Describe business intelligence dashboards and capabilities, and explain how they form the cornerstone of business intelligence solutions.

•

Describe Office SharePoint Server 2007 Report Center features.

•

Describe how you can incorporate server-side forms into business intelligence solutions, and explain the different processes that you must use to deploy no-code and code-based forms.

7-2


Lesson 1: Configuring and Incorporating Business Data Catalog Applications into Portal Solutions

The Business Data Catalog is one of the key features of Office SharePoint Server 2007. It provides easy and intuitive access to external databases from within Office SharePoint Server 2007 sites.


Describe the structure and purpose of the Business Data Catalog.

•

Explain how to create Business Data Catalog applications.

•

Describe how to incorporate external data into SharePoint sites.


7-3

Discussion: Business Data and Business Intelligence

The instructor will now lead a class discussion. Please ensure that you participate in the discussion, when appropriate, to ensure that you and the other class members benefit fully from the discussion.


How does your organization typically incorporate database information into Web sites?

•

Think of some typical sources of data that information workers and business managers might need to access and analyze.

•

What sort of representations would information workers and business managers like to see in SharePoint sites?

7-4


What Is the Business Data Catalog?

The Business Data Catalog is a new feature of Office SharePoint Server 2007. It is one of the key additions that Office SharePoint Server 2007 provides to the Windows® SharePoint Services framework.

Data Sources The Business Data Catalog provides connectivity to external data sources. Information workers and business decision-makers can use this connectivity to access and analyze data from line-of-business applications, data analysis systems, and databases. You can create connections in the Business Data Catalog to many different types of external systems and databases, such as Microsoft SQL Server™ 2005 databases, SQL Server Analysis Services databases, any ADO.NET source, and any Web service.

Business Data Catalog Applications When you define a Business Data Catalog application, you specify the connection details for the external system. You can also define Business Data Catalog entities that represent database tables, database views, stored procedures, database functions, or any other object that represents data. For example, you can use a Business Data Catalog application to retrieve data from an external system by using queries. You can then display the results of the queries in SharePoint sites.


7-5

Creating Business Data Catalog Applications

You can create a Business Data Catalog application by using the administrative features that Office SharePoint Server 2007 provides.

Shared Services Provider The Office SharePoint Server 2007 Shared Service Provider creates and manages Business Data Catalog applications. You can use the Shared Service Provider administrative Web application to create, manage, and delete Business Data Catalog applications. The process for creating and managing Business Data Catalog applications is a simple task for administrators and application implementers.

Application Definition Files Although the process for creating a Business Data Catalog application is simple, it relies on an application definition file. This type of file is an XML-based definition of the application. It includes connection details, definitions of entities and their properties, and definitions of how to retrieve data from, and interact with, those entities. The creation of an application definition file is typically a complex task. It is usually performed by a developer who has a good understanding of XML. The developer must also posses an indepth understanding of the external database or system to be able to create queries that access data correctly. You will review an application definition file in the lab for this module.

7-6


Incorporating Data from External Sources in SharePoint Sites

When you have created a Business Data Catalog application, you can incorporate the data from the application into Office SharePoint Server 2007 sites.

Data-Driven Web Parts Office SharePoint Server 2007 includes Web Parts that you can use for Business Data Catalog applications. For example, you can create a Business Data Catalog application that provides an input parameter for an employee’s last name and then retrieves employee details from an external human resources database. You can then add a Business Data List Web Part to a page in the Office SharePoint Server 2007 site and specify that it is connected to the employee entity in the Business Data Catalog application. Site users can then enter an employee’s last name in the Business Data List Web Part. The Web Part automatically retrieves and displays the details of all employees with that last name.

Data-Driven Lists You can also use the data from a Business Data Catalog application to populate the contents of SharePoint lists. For example, when you create a list, you can specify that it contains a column of type Business Data. When users create a new list item, they can include data from the Business Data Catalog application in the list.

Drilldown Data One of the powerful features of Business Data Catalog applications is that an information worker can drill down through the data to access related details from the external system. For example, when you create a data-driven list, you can specify that the data-bound


7-7

business data column will retrieve additional data from the external system. Furthermore, you can create connected Business Data List Web Parts. This enables you to use the values in one Web Part as an input to another Web Part. When you access data in the first Web Part, you can use this data to retrieve related data and display it in the second Web Part.

7-8


Lesson 2: Implementing Microsoft Office SharePoint Server 2007 Excel Services

Excel Services for Office SharePoint Server 2007 are a key part of the business intelligence infrastructure.


Describe the uses and benefits of Excel Services.

•

Explain how to set up a trusted location and why this is necessary.

•

Describe how to publish and access Microsoft Office Excel® data in Office SharePoint Server 2007 sites.


7-9

What Are Excel Services?

Excel Services are a key feature of Office SharePoint Server 2007. They enable information workers and business decision-makers to use a Web browser to access data and other objects from Excel workbooks.

Excel Services for Business Decision-Makers Business decision-makers require access to specific types of information that they can use to make timely and informed decisions. They often require summarized information and graphical representations of data so that they can obtain an overview of a specific situation. Business decision-makers typically use workbook features, such as charts, data tables, PivotTables, and analysis features, as the basis on which to form their decisions. Microsoft Office Excel 2007 workbooks provide these extremely useful features, and many business decision-makers are already comfortable with using them. Excel Services provide functionality that you can use to incorporate Office Excel 2007 workbooks and features directly into SharePoint sites. You do not need to develop any custom code. For example, you can include Office Excel workbooks and charts directly in SharePoint sites by using the built-in features of Office SharePoint Server 2007.

Excel Services for Developers In addition to providing the built-in features that incorporate Office Excel data into SharePoint sites, Excel Services enable developers to create custom solutions. Excel Services expose the Office Excel 2007 object model. Developers can use the object model to create and manipulate Office Excel objects programmatically. For example, a

7-10


developer can create a custom Web Part that creates and manipulates Excel objects dynamically; business decision-makers can then use that functionality to analyze Excel data and objects. Furthermore, developers can create custom functions in Excel workbooks and make these functions available to SharePoint sites.


7-11

Configuring Trusted Locations for Excel Services

You can incorporate Office Excel data, objects, and functionality in SharePoint sites by using the site features and Web Parts that Office SharePoint Server 2007 provides. However, you must configure trusted locations to store Office Excel workbooks before you can use them.

Shared Service Provider You can create trusted locations for Office Excel workbooks by using the Office SharePoint Server 2007 Shared Service Provider. You use the Shared Service Provider administration pages to specify the document libraries that you will use to store workbooks. When you specify the library location, you can also specify the type of functionality that will be available to users. For example, you can specify whether Excel functions are available.

7-12


Publishing and Accessing Excel Data

After you have specified that a document library is a trusted location, users can access and display data from the workbooks in that library.

Uploading Office Excel Workbooks Site members can simply upload Office Excel workbooks to a trusted location, just as they would do for any other type of document or file. When a workbook is uploaded, its data and functionality become available to other site members.

Excel Web Access Web Parts Information workers can access data and objects from Office Excel workbooks by using Excel Web Access Web Parts. Users first specify the URL of the workbook that contains the data or objects that they want to display on the page. They also specify a range of cells (such as A1:C7) or a named range (such as SalesFigures) to define the data that they want to display. If users want to display an object, such as a chart or a PivotTable, they can specify the name of the object. When a page that contains Excel Web Access Web Parts is loaded in the Web browser, Office SharePoint Server 2007 retrieves the data or the object from the specified workbook. It then renders the worksheet data or chart in the Web page.


7-13

Lesson 3: Implementing Business Intelligence Dashboards

Business decision-makers often require Web pages that display both summaries and graphical representations of business data. This provides a holistic view, which decisionmakers can use to interpret results from many different sources together. Key Performance Indicators (KPIs) are an important tool for decision-makers. You use KPIs to assess an organization's performance.


Define KPIs and explain how to use them.

•

Describe how to create KPIs.

•

Explain how to build a business intelligence dashboard.

7-14


What Is a Key Performance Indicator?

KPIs provide business decision-makers with insight into how well a specific part of an organization is functioning. KPIs are typically based on a summary of detailed data, such as the sum of sales for the North West region in quarter 1 of the fiscal year. However, a KPI is more than just a simple piece of summarized data. A KPI is actually a composite of an indicator value, a goal level, and, optionally, a warning level.

Indicator Values An indicator value is the part of the KPI that represents the current state of the data. For example, an indicator value might represent the actual sum of sales for the North West region in quarter 1 of the fiscal year. Alternatively, it might represent actual employee attrition rates in Europe. The indicator value is the part of the KPI that the decision-maker monitors and assesses when making decisions about the tactical or strategic directions for the organization.

Warning Levels Typically, a KPI will also include a warning level. Business decision-makers compare indicator values to warning levels to determine whether the organization must take remedial action. In some cases, there is a problem if the indicator level is below the warning level. For example, if the indicator value for the sales KPI is below the warning level, the decisionmaker will realize that action must be taken to increase sales. Without such action, the organization may not meet its sales targets.


7-15

In other cases, there is a problem if the indicator level is above the warning level. For example, if the employee attrition rate is above the warning level, the decision-maker will realize that the organization must take action to increase employee retention.

Goal Levels In addition to a warning level, a KPI also typically includes a goal level. The goal level specifies the criteria that the organization is working towards fulfilling. For example, the sales KPI typically includes a goal level based on the organization’s sales forecast. The employee attrition rate KPI usually includes a goal level based on the organization’s employee turnover targets. Business decision-makers typically interpret an indicator that has reached or exceeded the goal level as an indication that the organization is meeting its targets for that specific area of the business.

7-16


Defining Key Performance Indicators

Office SharePoint Server 2007 includes specific, dedicated support for KPIs.

Key Performance Indicator Lists The foundation for implementing KPIs in Office SharePoint Server 2007 solutions is based on specialized KPI lists. You can create KPI lists by using the list creation features that Office SharePoint Server 2007 provides.

Key Performance Indicator Data Sources When you have created a KPI list, you can then define KPIs that business decisionmakers can use in their decision-making processes. You can base a KPI on any of the following data sources: •

Other SharePoint list items.

•

Excel Services workbook data.

•

SQL Server Analysis Services cubes.

Alternatively, you can specify that the KPI values will be entered manually.

Key Performance Indicator Attributes When you create a KPI, you can specify the following attributes together with their source: •

Indicator value

•

Goal value


•

7-17

Warning level

For example, if you create a KPI from Excel Services workbook data, you can specify that the indicator value is located in one cell, the goal value is located in another cell, and the warning level is located in a third cell in the workbook. When you specify the warning level, you can also define whether it is better for the indicator value to be higher or lower than the warning level. For example, it is better that a sales indicator is higher than the warning level. However, an employee attrition rate that is lower than the warning is desirable. By specifying this attribute correctly, you can ensure that business decision-makers receive an accurate picture of the indicator value compared to the warning level.

7-18


Building Business Intelligence Dashboards

When you implement the Business Data Catalog, Excel Services, and KPIs, you will typically expose their functionality to business decision-makers on a business intelligence dashboard. A business intelligence dashboard is simply a Web Part page that gathers together views of data into a centralized location. This gives decision-makers a holistic view of the organization’s performance. Typically, a business intelligence dashboard will include some or all of the following Web Parts: •

Key Performance Indicator (KPI) Web Parts.

•

Business Data Catalog Web Parts.

•

Excel Data Web Parts.

•

Excel Chart Web Parts.

You can configure each Web Part to meet your organization’s specific requirements. In general, however, you build the business intelligence dashboard by adding KPI Web Parts in a similar way to adding other types of Web Parts. In addition, a business intelligence dashboard might include Reporting Web Parts. Reporting in Office SharePoint Server 2007 is covered in the next lesson of this module.


7-19

Lesson 4: Creating Report Center Web Sites

Office SharePoint Server 2007 provides Report Center Web sites that you can use to disseminate business reports to information workers in your organization.


Describe the Report Center and Report Center Web sites.

•

Explain how to incorporate SQL Server Reporting Services and Microsoft Office PerformancePoint 2007 reports into Office SharePoint Server 2007 solutions.

•

Describe how you can store, cache, and access reports with Office SharePoint Server 2007.

7-20


What Is Report Center?

Report Center is a feature that Office SharePoint Server 2007 provides to facilitate report access and aggregation. With this feature, information workers and business decisionmakers can access reports at the most convenient time and location.

Report Center Web Sites Office SharePoint Server 2007 provides a Report Center Web site template that you can use to build Report Center Web sites. Other templates, such as the Collaboration Portal site template, also include Report Center Web sites as subsites. You will typically use Report Center Web sites as the starting point for building business intelligence dashboards.


7-21

Integrating with Reporting Services

The Report Center feature of Office SharePoint Server 2007 integrates with external reporting services such as Microsoft SQL Server 2005 Reporting Services and Office PerformancePoint 2007.

Microsoft SQL Server 2005 Reporting Services You can configure Report Center to both aggregate and provide access to the reports that SQL Server 2005 Reporting Services provide. With previous versions of SharePoint Products and Technologies, you must install Office SharePoint Server 2007 extensions on the SQL Server Report server. You must also install the Reporting Services feature pack in the SharePoint Report Center Web site. However, you can use Office SharePoint Server 2007 to integrate directly with SQL Server 2005 Reporting Services by implementing Report Center KPIs. You can then publish and secure reports in document libraries so that information workers can access them easily. Information workers typically subscribe to, view, and manage reports by using Report Viewer Web Parts. These Web Parts use the Reporting Services Simple Object Access Protocol (SOAP) application programming interface (API) to retrieve and manage reports.

Office PerformancePoint Server 2007 Office PerformancePoint Server 2007 provides reports by combining analysis tools and business scorecards with planning, forecasting, and budgeting features.

7-22


Office PerformancePoint Server 2007 uses SQL Server 2005 to provide the data processing, management, and control infrastructure for its features and reports. Organizations can use Office SharePoint Server 2007 as a development platform for integrating Office PerformancePoint Server 2007 with other enterprise applications. Office PerformancePoint Server 2007 operations are exposed as Web services. Developers can use these Web services to integrate SharePoint sites with Office PerformancePoint Server 2007.


7-23

Storing and Accessing Reports

SQL Server 2005 Reporting Services provides the data and the processing that organizations require to generate reports.

SQL Server Reporting Services and SharePoint Libraries The SQL Server 2005 Reporting Services database caches and stores SQL Server 2005 Reporting Services. However, when you include these types of reports in Office SharePoint Server 2007 Report Center Web sites, report libraries also cache and store those reports. When a user accesses a report, Office SharePoint Server 2007 connects to SQL Server 2005 Reporting Services to determine whether the report in the SharePoint library is up-to-date. If it is up-to-date, the report from the SharePoint library renders in the Web browser. If it is out-of-date, the latest version of the report is retrieved from SQL Server 2005 Reporting Services and renders in the Web browser; the version in the SharePoint library is also updated so that it can be used in future requests.

7-24


Lesson 5: Implementing Microsoft Office SharePoint Server 2007 Forms Server

Forms provide many useful features for gathering information as part of business processes. You can use the data that forms gather to help the business process. Decisionmakers can also analyze this data.


Explain the key features and benefits of Office SharePoint Server 2007 Forms Server.

•

Describe the deployment of server-side forms.


7-25

What Are Server-Side Forms?

Microsoft Office InfoPath® Forms were introduced in Microsoft Office InfoPath 2003. These forms provided users with convenient and easy-to-use forms for entering data. However, they provided a purely client-based solution and were not integrated with server products, such as Microsoft Office SharePoint Portal Server 2003.

Server-Side Forms Office SharePoint Server 2007 introduces the concept of server-side InfoPath forms. Microsoft Office Forms Server 2007, included in Office SharePoint Server 2007, provides server-side form processing capabilities. For example, you can create online forms that users access from SharePoint sites. The user can then submit the form to SharePoint libraries. Furthermore, developers can create server-side InfoPath forms that are used with Office SharePoint Server 2007 in an integral way. For example, a developer can create a form to extend the document information panel for documents stored in SharePoint libraries. As another example, a developer can create a form to provide additional metadata-gathering features and validation features for a document when an information worker uploads it to a SharePoint library.

7-26


Server-Side Form Deployment

Server-side forms can contain powerful features, such as connections to SharePoint lists or other data sources and custom code for performing specific operations. Therefore, as an administrator, you will need to control the forms that users and developers create in Office SharePoint Server 2007 sites.

No-Code Form Deployment If a form does not contain server-side code or data connections, information workers or developers can upload the form to a SharePoint library. They do not require authorization beyond that required for uploading any other type of file.

Code-Based Form Deployment If a server-side form contains code that will run on the server, a user cannot simply upload the form. This is because the code could compromise the security and performance of the Office SharePoint Server 2007 site. The code could contain malicious actions. Alternatively, the form may contain poorly-written code that performs in an unexpected or unacceptable way. Therefore, server-side forms that contain server-side code must be installed by an administrator. You can install a server-side form by using the administrative Web pages for the site.


7-27

Lab: Implementing Business Intelligence Solutions with Microsoft Office SharePoint Server 2007


Create Business Data Catalog applications.

•

Implement Excel Services.

•

Create business intelligence dashboards.

•

Create server-side InfoPath forms.

•

Deploy server-side InfoPath forms.



Start the Start the 5061A_LON-DC-01-07 virtual machine.

•


7-28


Exercise 1: Creating Business Data Catalog Applications In this exercise, you will create a Business Data Catalog application from an application definition file. You will then use the Business Data Catalog application to drive the contents of a Web Part and a SharePoint list. The principle tasks for this exercise are as follows: •

Review the Business Data Catalog application definition file.

•

Create the Business Data Catalog application.

•

Add a Business Data List Web Part to a Web page.

•

Test the Business Data List Web Part.

•

Create a data-driven custom list.

•

Add a business data column to the data-driven custom list.

•

Create a new item in the data-driven custom list.

Tasks


1.

•

On the Start menu, click Windows Explorer.

•

Browse to the E:\Labfiles\Lab07\Starter folder.

•

Double-click LitwareEmployees.xml. Internet Explorer appears.

2.

Review the Business Data Catalog application definition file.

Create the Business Data Catalog application.

•

In the Information Bar dialog box, click OK.

•

Review the contents of the Properties group of elements in the LobSystemInstance element.

•

Review the SQL SELECT statement in the GetEmployees method element.

•

Close Internet Explorer, and then close Windows Explorer.

•


•

In the navigation bar on the left side of the page, under Shared Services Administration, click SharedServices1. After a short period of time, the Home page for the Shared Service Provider appears.

•

On the Home page, under Business Data Catalog, click Import application definition.

•

On the Import Application Definition page, click Browse.

•

In the Choose file dialog box, browse to the E:\Labfiles\Lab07\Starter folder.

•

Click LitwareEmployees.xml, and then click Open.

•

On the Import Application Definition page, click Import. The Importing Application Definition page appears, and then the Application Definition Import Successful page appears.

•

On the Application Definition Import Successful page, click OK.

•



7-29

Tasks


3.

•

Start Internet Explorer.

•

In the Address bar, type http://litwareportal/Pages/Default.aspx and then press ENTER.

•

On the Site Actions menu, click Edit Page.

•

Under Top Zone, click Add a Web Part.

•

In the Add Web Parts -- Web Page Dialog dialog box, click All Web Parts.

•

Select the Business Data List check box, and then click Add.

•

Under Top Zone, in the Business Data List Web Part, click the Open the tool pane link.

•

In the Business Data List pane on the right side of the page, in the Type section, click Browse.

•

In the Business Data Type Picker -- Web Page Dialog dialog box, under Application, click LitwareInc, and then click OK.

•

At the bottom of the Business Data List pane, click OK.

•

On the Page menu, click Save and Stop Editing.

Test the Business Data List Web Part.

•

In the Employee List Web Part, in the first list, click EmployeeID.

•

Type 19 in the box, and then click Retrieve Data. The details for the employee with an ID of 19 are retrieved.

Create a data-driven custom list.

•

In the navigation bar on the left side of the page, click View All Site Content.

•

Near the top of the page, click Create.

•

In the Custom Lists section, click Custom List.

•

On the New page, in the Name box, type Employees List and then click Create.

4.

5.

6.

7.

Add a Business Data List Web Part to the home page.

Add a business data column • to the data-driven custom list.

Create a new item in the data-driven custom list

On the Employees List page, on the Settings menu, click Create Column.

•

On the Create Column: Employees List page, in the Column name box, type EmployeeInfo

•

Under The type of information in this column is, click Business data.

•

In the Additional Column Settings section, under Type, click Browse.

•

In the Business Data Type Picker -- Web Page Dialog dialog box, click LitwareInc, and then click OK.

•

In the Display this field of the selected type list, click LastName.

•

Under Add a column to show each of these additional fields, select the FirstName and the ID check boxes, and then click OK.

•

On the Employees List page, click New.

•

On the Employees List: New Item page, in the Title box, type Ms

•

Next to the EmployeeInfo box, click Browse.

•

In the Choose Employee -- Web Page Dialog dialog box, type 181 in the box, and then press ENTER.

•

Under FirstName, click Belinda, and then click OK.

•

On the Employees List: New Item page, click OK. A new list item is

7-30


Tasks

Supporting information created based on data retrieved from the Business Data Catalog application. •



7-31

Exercise 2: Implementing Excel Services In this exercise, you will implement Excel Services, including configuring trusted locations and using Excel workbooks as the source for KPIs. The principle tasks for this exercise are as follows: •

Configure Excel Services trusted locations.

•

Add a Microsoft Office Excel 2007 workbook to the trusted location.

•

Create a KPI list.

•

Create two KPIs.

Tasks


1.

•

On the Start menu, click SharePoint 3.0 Central Administration.

•

In the navigation bar on the left side of the page, under Shared Services Administration, click SharedServices1.

•

On the Home page, under Excel Services Settings, click Trusted file locations.

•

In the Excel Services Trusted File Locations page, click Add Trusted File Location.

2.

3.

Configure Excel Services Trusted Locations.

Add a Microsoft Office Excel 2007 workbook to the trusted location.

Create a Key Performance Indicator

•

In the Address box, type http://litwareportal/Docs/Documents

•

Scroll to the bottom of the page, and then click OK. If the AutoComplete dialog box appears, click No.

•


•


•

Browse to the E:\Labfiles\Lab07\Starter folder.

•

Double-click SalesSummary.xlsx. The workbook is opened in Microsoft Excel

•

Review the data and the chart in the SalesSummary.xlsx workbook.

•

Close Microsoft Excel. If you are prompted to save changes, click No.

•

Close Windows Explorer.

•

On the Start menu, click Internet Explorer.

•

In the Address bar, type http://litwareportal/Pages/Default.aspx and then press ENTER.

•


•

In the navigation bar on the left side of the page, click Documents.

•

On the Documents page, click Upload.

•

On the Upload Document: Documents page, click Browse.

•

In the Choose file dialog box, browse to the E:\Labfiles\Lab07\Starter folder.

•

Click SalesSummary.xlsx, and then click Open.

•

On the Upload Document: Documents page, click OK.

•

Click Check In.

•

Click the Home tab.

•

In the navigation pane on the left side of the screen, click View All

7-32


Tasks


List.

4.

5.

Create the Total Sales (YTD) Key Performance Indicator.

Create the Q1 Sales Key Performance Indicator

Site Content. •

On the All Site Content page, click Create.

•

On the Create page, under Custom Lists, click KPI List.

•

On the New page, in the Name box, type Sales KPIs and then click Create.

•

On the Sales KPIs page, on the New menu, click Indicator using data in Excel workbook.

•

On the Sales KPIs: New Item page, in the Name box, type Total Sales (YTD)

•

In the Description box, type Total sales for all regions this year

•

In the Comments box, type We all have responsibility for meeting these goals

•

Next to the Workbook URL box, click Browse.

•

In the Select a Link -- Web Page Dialog dialog box, click Up.

•

Double-click Document Center.

•

Double-click Documents.

•

Click SalesSummary, and then click OK.

•

On the Sales KPIs: New Item page, under Cell Address for Indicator Value, click Select.

•

In the /Docs/Documents/SalesSummary.xlsx -- Web Page Dialog dialog box, click cell G7.

•

Under Cell Address for Indicator Value, click Set.

•

Click cell G8.

•

Under Cell Address for Indicator Goal, click Set.

•

Click cell G9.

•

Under Cell Address for Indicator Warning, click Set, and then click OK.

•

On the Sales KPIs: New Item page, click OK.

•

On the Sales KPIs page, on the New menu, click Indicator using data in Excel workbook.

•

On the Sales KPIs: New Item page, in the Name box, type Q1 Sales

•

In the Description box, type Quarter 1 Sales

•

Next to the Workbook URL box, click Browse.

•


•

Double-click Document Center.

•


•


•

On the Sales KPIs: New Item page, under Cell Address for Indicator Value, click Select.

•

In the /Docs/Documents/SalesSummary.xlsx -- Web Page Dialog dialog box, click cell C7.

•

Under Cell Address for Indicator Value, click Set.

•

Click cell C8.

•

Under Cell Address for Indicator Goal, click Set.


Tasks

7-33


Click cell C9.

•

Under Cell Address for Indicator Warning, click Set, and then click OK.

•

On the Sales KPIs: New Item page, click OK.

Note: You will use the Key Performance Indicators in the next exercise.

7-34


Exercise 3: Creating Business Intelligence Dashboards In this exercise, you will build a business intelligence dashboard by adding KPI Web Parts and Excel Web Access Web Parts to a SharePoint site. The principle tasks for this exercise are as follows: •

Add KPI Web Parts.

•

Configure the key performance indicator Web Part.

•

Configure the KPI details Web Part.

•

Add an Excel Web Access Web Part.

Tasks


1.

•

Click the Home tab.

•

On the Site Actions menu, click Edit Page.

•

Under Middle Right Zone, click Add a Web Part.

•


•

Scroll down until you can see the Dashboard group.

•

Select the Key Performance Indicators check box.

•

Select the KPI Details check box, and then click Add.

•

In the Key Performance Indicator Web Part, click the Open the tool pane link.

•

Under Indicator List, click Browse.

•


•

Click Up again.

•

Point to Title, and then click the arrow that appears.

•

Click Sales KPIs.

•

Double-click Sales KPIs.

2.

3.

4.

Add Key Performance Indicator Web Parts.

Configure the Key Performance Indicator Web Part.

Configure the KPI Details Web Part.

Add an Excel Web Access Web Part.

•

Click Total Sales (YTD), and then click OK.

•

At the bottom of the Key Performance Indicator tool pane, click OK.

•

In the KPI Details Web Part, click the Open the tool pane link.

•

Under KPI List, click Browse.

•

In the Select a Link -- Web Page Dialog dialog box, click Q1 Sales, and then click OK.

•

In the KPI drop-down list, click Q1 Sales.

•

At the bottom of the KPI Details tool pane, click OK.

•

Under Middle Left Zone, click Add a Web Part.

•


•

Select the Excel Web Access check box, and then click Add.

•

In the Excel Web Access Web Part, click the Click here to open the tool pane link.

•

Next to the Workbook box, click the ellipsis […].

•

In the Select a Link -- Web Page Dialog dialog box, double-click


Tasks

7-35

Supporting information Document Center.

5.

View the Business Intelligence Dashboard

•


•


•

In the Named Item box, type SalesChart and then click OK.

•

if the AutoComplete dialog box appears, click No.

•

On the Page menu, click Save and Stop Editing.

•

Review the Home page, and then close Internet Explorer.

7-36


Exercise 4: Creating Server-Side InfoPath Forms In this exercise, you will create a server-side InfoPath form that retrieves data from a SharePoint list and submits the data to a SharePoint library. The principle tasks for this exercise are as follows: •

Import an existing holiday request form into Office InfoPath 2007.

•

Configure the form template for browser compatibility.

•

Enable users to submit the form to a document library.

•

Configure a control to retrieve data from a SharePoint list.

•

Publish the form template.

Tasks 1.


Import an existing holiday • request form into Office • InfoPath 2007. •

On the Start menu, click Windows Explorer. Browse to the E:\Labfiles\Lab07\Starter folder. Double-click HolidayRequest.docx. The document is opened in Microsoft Word.

•

Review the document, and then close Microsoft Word.

•

Close Windows Explorer.

•

Click Start, point to All Programs, point to Microsoft Office, and then click Microsoft Office InfoPath 2007.

•

On the Getting Started page, click Import a Form.

•

On the Import Wizard page, click InfoPath importer for Word documents, and then click Next.

•

Click Browse, and then browse to the E:\Labfiles\Lab07\Starter\ folder.

•

Click HolidayRequest.docx, and then click Open.

•

Click Finish.

•

Wait for the form conversion to complete, and then click OK. Note: Office InfoPath 2007 has created user controls from the text constructs in the original file.

2.

Configure the form template for browser compatibility.

•

On the Tools menu, click Form Options.

•

In the Category list, click Compatibility.

•

Under Browser Compatibility, click Design a form template that can be opened in a browser or InfoPath.

•

In the box, type http://litwareportal/

•

In the Category list, click Security and Trust.

•

Clear the Automatically determine security level check box, and then select the Full Trust.

•

Select the Sign this form template check box, and then click Create Certificate. When the Microsoft Office InfoPath dialog box appears, click OK.

•

In the Category list, click Property Promotion.

•

Click Add, click FullName, and then click OK.

•

Click Add, click StartDate, click OK, and then click OK again.


7-37

Tasks


3.

•

On the Tools menu, click Submit Options.

•

In the Submit Options dialog box, click Allow users to submit this form.

•

Under Send form data to a single destination, in the list, click SharePoint document library.

•

Click Add. The Data Connection Wizard appears.

•

In the Document library box, type http://litwareportal/Docs/Documents/Forms/AllItems.aspx

•

Click fx.

•

Click Insert Function.

•

Click concat, and then click OK.

•

In the Insert Formula box, double-click the first instance of double click to insert field.

•

Click FullName, and then click OK.

•

In the Insert Formula box, double-click the second instance of double click to insert field.

•

Click Department, and then click OK.

•

In the Insert Formula box, double-click the third instance of double click to insert field.

•

Click StartDate, and then click OK. Click OK again.

•

Click Next, and then click Finish.

•

In the Submit Options dialog box, click OK.

•

Right-click the Department box, click Change To, then click DropDown List Box.

•

Right-click the Department list, then click Drop-Down List Box Properties.

•

Under List box entries, select Look up values from an external data source, and then click Add.

•

On the Data Connection Wizard page, click Create a new connection to, and then click Next.

•

Select SharePoint library or list, and then click Next.

•

In the SharePoint site details box, type http://litwareportal/Lists/Departments/AllItems.aspx

4.

Enable users to submit the form to a document library.

Configure the Department control.

Note: This is the URL of a SharePoint list that contains the name of every department in Litware, Inc. •

Click Next.

•

Verify that Departments is selected in the Select a list or library list, and then click Next.

•

Select the Title check box, and then click Next.

•

Click Next, and then click Finish.

•

In the Drop-Down List Box Properties dialog box, to the right of the Entries box, click Select XPath.

•

Expand the dataFields tree node.

•

Expand the Departments tree node.

•

Click Title.

7-38


Tasks

5.

6.

7.

Configure the Start Date and End Date controls.

Verify the form template.

Publish the form template.


Click OK, and then click OK again.

•

Right-click the Start Date box, click Change To, and then click Date Picker.

•

Right-click the End Date box, click Change To, and then click Date Picker.

•

In the Design Checker pane, ensure that Verify on server is selected, and then click Refresh.

•

Verify that no errors or messages are reported.

•

On the File menu, click Publish.

•

In the Microsoft Office InfoPath dialog box, click OK.

•

In the Save As dialog box, navigate to the E:\Labfiles\Lab07\Starter folder.

•

Click Save.

•

On the Publishing Wizard page, select To a network location, and then click Next.

•

Click Browse, and then browse to the E:\Labfiles\Lab07\Starter\PublishedForms folder.

•

In the File name box, type HolidayRequest and then click OK. Note: The template must be published to a different location from the location in which it was saved.

•

Click Next.

•

On the Publishing Wizard page, under If users access the form template from the published location by using a different path, clear the contents of the box, and then click Next.

•

Click Publish, and then click Close.

•

Close Office InfoPath 2007.


7-39

Exercise 5: Deploying Server-Side InfoPath Forms In this exercise, you will deploy the server-side form that you created in the previous exercise to a Office SharePoint Server 2007 site. The principle tasks for this exercise are as follows: •

Upload the form template to InfoPath Forms Services.

•

Activate the form template to a site collection.

•

Create the Vacation Request content type.

•

Add the Vacation Request content type to the Document Center Documents library.

•

Test the Vacation Request form.

Tasks


1.

•

On the Start menu, click SharePoint 3.0 Central Administration.

•


•

Under InfoPath Forms Services, click Upload form template.

•

Click Browse.

•

In the Choose file dialog box, browse to the E:\Labfiles\Lab07\Starter\PublishedForms\ folder.

•

Click HolidayRequest.xsn, and then click Open.

•

Click Upload.

•

When the form template is uploaded successfully, click OK.

•

Refresh the page until the Status of the HolidayRequest.xsn form changes to Ready.

•

On the Manage Form Templates page, point to HolidayRequest.xsn and then click the arrow.

•

Click Activate to a Site Collection.

•

In the Activation Location section, click http://litwareportal:18097/ssp/admin, and then click Change Site Collection.

•

In the Select Site Collection – Web Page Dialog dialog box, in the Web Application section, click http://litwareportal:18097, and then click Change Web Application.

•

In the Select Web Application – Web Page Dialog dialog box, click SharePoint – 80, and then click OK.

•

On the Activate Form Template: HolidayRequest page, click OK.

•

In the Address bar, type http://litwareportal and then press ENTER.

•

On the Site Actions menu, point to Site Settings and then click Modify All Site Settings.

•

Under Galleries, click Site content types

•

Click Create.

•

In the Name box, type Vacation Request

•

In the Description box, type Use this form to book a vacation

•

In the Select parent content type from list, select Microsoft

2.

3.

Upload the form template to InfoPath Forms Services.

Activate the form template to a site collection.

Create the Vacation Request content type.

7-40


Tasks

Supporting information Office InfoPath.

4.

5.

Add the Vacation Request content type to the Document Center Documents library.

Test the Vacation Request form.

•

In the Parent Content Type list, select HolidayRequest.

•

Click OK, and then click the Document Center tab.

•

On the task pane on the left hand side of the page, click Documents.

•

Click Settings, and then click Document Library Settings.

•

Under Content Types, click Add from existing site content types.

•

In the Available Site Content Types list, click Vacation Request, click Add>, and then click OK.

•

On the breadcrumb trail control, click Documents.

•

Click the arrow on the New menu, and then click Vacation Request. Note: Because Office InfoPath 2007 is installed on your computer, the form will open in Office InfoPath 2007 instead of in a browser window.

•

In the Microsoft Office InfoPath Security Notice dialog, click Trust all documents from this publisher.

•

In the Network Connection Unavailable dialog, click Try to Connect.

•

In the Full Name box, type your name.

•

If the AutoComplete message box appears, click No.

•

In the Department list, click Publishing.

•

In the Start Date date picker, click tomorrow’s date.

•

In the End Date date picker, click the date that is one week from tomorrow.

•

On the tool bar, click Submit.

•

Verify that the form was submitted successfully, and then click OK.

•

Close Office InfoPath 2007 without saving changes.

•

Return to the browser page. Verify that the form you completed was added to the Documents document library.



Review

You have now completed this module. You should now be able to: •

Describe the key part that the Business Data Catalog plays in Office SharePoint Server 2007-based solutions, and describe the process of creating Business Data Catalog applications.

•

Describe the features and capabilities of Excel Services, and explain how they contribute to business intelligence solutions.

•

Describe business intelligence dashboards and capabilities, and explain how they form the cornerstone of business intelligence solutions.

•

Describe Office SharePoint Server 2007 Report Center features.

•

Describe how you can incorporate server-side forms into business intelligence solutions, and explain the different processes that you must use to deploy no-code and code-based forms.

7-41

Module 8: Implementing Search and Indexing Table of Contents Overview 8-1 Lesson 1: Office SharePoint Server 2007 Search and Indexing 8-2 Lesson 2: Implementing Search 8-7 Lab: Implementing Search and Indexing 8-19 Lab Shutdown 8-25 Review 8-26


Module 8: Implementing Search and Indexing

8-1

Overview

Objectives Organizations hold information in locations such as file shares, Web sites, business applications, and e-mails. Business users often require access to this data. The amount of information can grow everyday, particularly in the case of e-mails. Therefore, users must be able to search through vast amounts of information effectively. Microsoft® Office SharePoint® Server 2007 provides facilities for indexing and searching this data, which enables business users to work more efficiently. After completing this module, you will be able to: •

Explain the search and indexing features of Microsoft Office SharePoint Server 2007, and explain which features are provided by Windows® SharePoint Services and which are provided by Office SharePoint Server 2007.

•

Describe the process of defining content to be indexed, indexing that content, and performing searches.

8-2


Lesson 1: Office SharePoint Server 2007 Search and Indexing

A search service must return relevant content to enable users to locate information distributed across their organization. This lesson explains the search and indexing features of Office SharePoint Server 2007. It also explains which features are provided by Windows SharePoint Services and which are provided by Office SharePoint Server 2007.


Describe the enterprise search capabilities of Office SharePoint Server 2007.

•

Describe the enhanced features of Office SharePoint Server 2007 Search.


8-3

Fundamentals of Search and Indexing

Enterprise Search Capabilities You can configure Office SharePoint Server 2007 Search to crawl and index content stored in various locations in an organization. Locations include files shares and information stored in line-of-business applications.

Content You can refine search queries in several ways to enable you to find the most relevant information. For example, you can use predefined content scopes to narrow the scope of your search or use advanced filters on content metadata, such as author and file type.

People A key component of Microsoft Office SharePoint Server 2007 search is the ability to search for other people in the organization. You can search for people by skills or department. When you have found them, you can also identify their subordinates and managers.

Knowledge Knowledge Network is an add-on to Office SharePoint Server 2007 that enables you to search for people by automating the discovery of the business relationships and subject matter expertise of everyone in the network. Key information is also stored in line-of-business applications. Office SharePoint Server 2007 Search can also search line-of-business application content exposed by the Business Data Catalog.

8-4


Note: Unlike previous versions of SharePoint Products and Technologies, Office SharePoint Server 2007 provides two search services: Windows SharePoint Services Help Search and Office SharePoint Server Search. You can use each of these services to crawl, index, and query content. Each service uses a separate index. If you do not want users to be able to search the Help system, you should not start this service.


8-5

Enhanced Search Features

Introduction Windows SharePoint Services and Office SharePoint Server 2007 both use the same technology for search and indexing. Office SharePoint Server 2007 Search has several enhanced features to provide relevant search results. The enhanced capabilities of Microsoft Office SharePoint Server 2007 Search include the following options: •

Configuration of Office SharePoint Server 2007 Search to crawl internal and external content sources.

•

Definition of Best Bets, which match popular keywords with the most relevant portal site pages, documents, or external Web sites.

•

Definition of managed properties for advanced searching.

•

Implementation of search and query reporting.

•

The ability to search for people.

•

The ability to search for knowledge.

Relevance At the Shared Service Provider level, you can specify relevance settings for content locations to influence their position in search results. The relevance settings indicate how authoritative the content in a particular location is. There are four authoritative groups, as follows: •

Most authoritative pages.

8-6


•

Second-level authoritative pages.

•

Third-level authoritative pages.

•

Non-authoritative sites.

The relevance settings weight content in search results based on their authoritative level. However, the relevance settings do not supersede the keyword settings at the site collection level.


8-7

Lesson 2: Implementing Search

Office SharePoint Server 2007 Search enables administrators and information workers to easily configure and locate content stored across the organization. This lesson describes the process you use to index and locate content. You use this process to define the content you want to index, index that content, and perform searches.


Explain how to identify and create content sources.

•

Explain how to identify and assign content scopes.

•

Describe how to build indexes.

•

Describe the integration of Office SharePoint Server 2007 Search with Microsoft Knowledge Network.

•

Describe how to configure and perform searches.

8-8


Defining Content Sources

Identifying Content Sources You create content sources to identify the groups of related content or data that you want to crawl and index. Additionally, you must specify the crawl schedule for that content. Office SharePoint Server 2007 Search has one content source configured by default. This source includes all of the Web applications, and therefore all of the site collections, that use the Shared Service Provider. You can create content sources for the following types of content: •

SharePoint sites, from the same server farm or different server farms.

•

Web sites, internally or on the Internet.

•

File shares.

•

Exchange Public Folders.

•

Other third-party content stores.

•

Business data stored in line-of-business applications.

You should consider the following guidelines when you identify content sources: •

Group closely related content.

•

Group content that is available at similar times.

•

You can use a content source as the focus of a content scope rule.

•

You cannot group business data content with other content in the same content source.


8-9

•

Set crawler impact rules for external content sources that are not under your direct control.

•

You can use a particular content source to crawl only one of the above content types.

Creating Content Sources You define content sources at the Shared Service Provider level. To create a content source, perform the following steps: 1. Start SharePoint 3.0 Central Administration. 2. On the Central Administration page, click Shared Services Provider. 3. On the Shared Services Provider page, click Search settings. 4. On the Configure Search Settings page, click Content sources and crawl schedules. 5. On the Manage Content Sources page, click New Content Source. 6. Specify the Content Source Type, the Start Addresses, and the Crawl Schedules and then click OK.

8-10


Defining Content Scopes

How to Identify Scopes Content scopes are named sets of rules that you use to filter search results. Content scope rules define the subsets of content that the search returns. The subsets of content should follow a common theme that users are likely to want to search through. For example, you might define content scopes for each division in your organization. You can select your division content scope when you perform a search to return sales information from only your division. You can define content scope rules for the following: •

Web addresses

•

Properties (such as Author = Lisa Miller)

•

Content sources

•

All content

When content matches a rule it can be included, excluded, or used to satisfy a required match condition when combined with other rules in the content scope.

Assigning Content Scopes You can create content scopes at the Shared Service Provider level or the site collection level. Content scopes that you create at the site collection level are only available for that site collection. Content scopes that you create at the Shared Service Provider level are


8-11

known as shared content scopes and can be used in all site collections. Two shared content scopes are available by default: •

All Sites

•

People

You can make shared content scopes available to users at the site collection level. You can also copy and modify these scopes to create a unique content scope for a single site collection.

8-12


Building Indexes

Process When Office SharePoint Server 2007 builds an index of a content source, the crawler uses an appropriate protocol handler to connect to the start address defined by the content source. The textual content is then processed. This stage uses any crawl and crawl impact rules that you have set. IFilters are the code that allows the Indexing Service to index different file formats and without which contents of a file cannot be indexed. The crawler will enlist suitable IFilters to extract text from any files it finds. During the crawl, the crawler returns two streams, one for object metadata and permissions and another for object content. The properties and permissions are stored in a property store table and the content is sent to the content full-text index. The permissions information is used to filter the search results so that users see only content appropriate to their permission levels. Before the content stream is put into the content index, word breakers and word stemmers are used to break the stream into words. Noise words are non-searchable words, such as “the” or “it”. Because they are so common there is no value indexing them, so are also removed at this stage. Note: Thesaurus files, word breaker files, and word stemmer files are installed in locale-specific subfolders of the C:\Program Files\Common Files\Microsoft Shared\web server extensions\12 folder by default.


8-13

The content index is then propagated from the index server to the query servers. The content indexes are automatically and continuously propagated. This ensures that the search results are as up-to-date as possible.

Crawler Settings You can configure crawler settings at the server farm level, the server level, and the Shared Service Provider level. Server farm-level settings include the following: •

The contact e-mail address that the crawler uses when crawling content.

•

Proxy server details.

•

Connection timeouts.

Crawler impact rules are also configured at the server farm level. These rules give you control over the number of simultaneous requests made for a particular site being crawled. SSP-level settings include the following: •

The default content access account.

•

Crawl rules for sites. You can configure the crawler to follow links from a site, but not to crawl the content on that site. You can also specify whether the crawler can follow links with query strings.

•

The types of files that will be crawled, specified by file type extension.

Note: To search the contents of a file, you must install the appropriate IFilter.

Index Reports At the Shared Service Provider level, reports are available for analyzing search queries and search results. These reports are critical for the continuous assessment of enterprise searches and will help you to identify areas for improvement. The search queries reports are as follows: •

Queries over previous 30 days.

•

Queries over previous 12 months.

•

Top query origin site collections over previous 30 days.

•

Queries per scope over previous 30 days.

•

Top queries over previous 30 days.

The search results reports are as follows: •

Search results destination pages.

•

Queries with zero results.

•

Most clicked Best Bets.

8-14


•

Queries with zero Best Bets.

•

Queries with low click through.

Performance Implications Crawling content and building indexes are processor-intensive activities. You can use server-level settings to control the impact that indexing and crawling has on performance. For a particular server you can use the following settings: •

Enable or disable indexing.

•

Limit the indexing activity for the server by limiting the number of threads that it can use.

•

Designate a specific server for crawling content.


8-15

Integrating Search with Knowledge Network

Introduction You can enhance Office SharePoint Server 2007 Search by opting to integrate it with Knowledge Network. Knowledge Network consists of a client component and a server component. The Knowledge Network client is deployed on users’ desktops. It crawls contacts and keywords from Microsoft Outlook®, Microsoft MSN® Messenger, Microsoft Windows Messenger, and Office Communicator. Keywords are determined from the subject and body of e-mails only, not attachments. The Knowledge Network client analyzes the data and recommends the best possible Knowledge Network profile for you, which you can then customize. This profile is synchronized with your My Site profile, when it is published to the Knowledge Network server component. The Knowledge Network server component enhances Office SharePoint Server 2007 Search in the following ways: •

My Site is periodically updated with your keywords and contacts.

•

You can perform more refined searches on expertise.

•

You can search for external contacts (an External People tab is added to Search Center).

•

You can find out who knows whom internally and externally (a Find People Who Know This Person link is made available on people in Search Center and My Site).

8-16


•

You can use permissions to hide results from user searches, but let search show a link to request further information.

Knowledge Network enables you to perform the following tasks: •

Find people with whom you have communicated.

•

Find people in your organization who have experience or expertise in a specific area.

•

Find people in your organization who can help you connect with a particular person.

•

Find out what and whom you have in common with other people.


8-17

Performing Searches

Searchable Entities You can search for almost any content. The most common entities searched against are documents, Web page content, list item content, and people within an organization. You can also perform searches can against Business Data Catalog information.

Keywords Keywords are specific words or phrases that you define at the site collection level to provide more targeted search results. A keyword can be associated with synonyms for a specific word or phrase, a definition of the keyword, and Best Bet links to content that is closely related to the keyword. When you perform a search on the keyword or any of the synonyms defined for that keyword, the definition and any Best Bets will be displayed in the search results. Note: Content scopes do not filter out any keyword results returned.

Basic Searches To perform a basic search, use the search box on any page or in Search Center. To narrow a basic search, select a content scope in the Content Scope list if available.

Advanced Searches Advanced searches allow you to create a more targeted search. The Advanced Search page allows you to specify various refinements, including the following:

8-18


•

Match an exact phrase or any, all, or none of the words entered.

•

Narrow the search by properties and metadata.

•

Narrow the search by document type.

•

Filter the search by using content metadata.


8-19

Lab: Implementing Search and Indexing


Define content sources and scopes.

•

Build indexes.

•

Perform searches.




•


Lab Scenario The enterprise architect has determined the organizational goals, overall vision, and scope for Office SharePoint Server 2007 Search and Indexing in an enterprise content management solution. Your role is to implement a prototype query server to test some of the organizational search requirements. You will configure search and indexing on file shares and perform basic and advanced searches, and a people search.

8-20


Exercise 1: Defining Content Sources and Scopes In this exercise, you will create content sources for file shares. You will also create a content scope and define rules to specify what content will be included in the scope. The principal tasks for this exercise are as follows:

f

•

Create content sources.

•

Create a content scope.

•

Define the rules for the content scope.

Create content sources for the Technical Documentation file shares Tasks

Detailed Steps

1.

•

On the Start menu, point to All Programs, point to Microsoft Office Server, and then click SharePoint 3.0 Central Administration.

•

In the navigation bar on the left side of the page, under Shared Services Administration, click SharedServices1. After a short period of time, the Home page for the shared service provider appears.

•

On the Home page, click Search settings.

•

On the Configure Search Settings page, click Content sources and crawl schedules.

•

On the Manage Content Sources page, click New Content Source.

•

On the Add Content Source page, in the Name box, type Technical Documents File Share

•

In the Content Source Type section, select File Shares.

•

In the Start Addresses section, type \\litwareportal\Technical Documents

•

In the Crawl Schedules section, under the Full Crawl list, click Create schedule.

•

In the Type section, click Weekly.

•

Select Sunday, and then click OK.

•

Under the Incremental Crawl list, click Create schedule.

2.

Create a content source for the Technical Documents file share.

Create a content source for the SharePoint Technical Documents file share.

•

Select Daily, and then click OK.

•

At the bottom of the Add Content Source page, click OK.

•

On the Manage Content Sources page, click New Content Source.

•

On the Add Content Source page, in the Name box, type SharePoint Technical Documents File Share

•

In the Content Source Type section, select File Shares.

•

In the Start Addresses section, type \\litwareportal\SharePoint Technical Documents

•

In the Crawl Schedules section, in the Full Crawl list, click At 12:00 AM every Sun of every week.

•

In the Incremental Crawl list, click At 12:00 AM every day, and then click OK.

•



f

f

8-21

Create the Tech Docs content scope Tasks

Detailed Steps

1.

•

On the Manage Content Sources page, in the breadcrumb control, click Search Settings.

•

In the Scopes section¸ click View scopes.

•

On the View Scopes page, click New Scope.

•

On the Create Scope page, in the Title box, type Tech Docs and then click OK.

Create the Tech Docs content scope.

Define the rules for the Tech Docs content scope Tasks 1.

Detailed Steps

Add a rule to include content • from the Technical • Documents File Share content source. •

For the Tech Docs item, click Add rules. On the Add Scope Rule page, in the Scope Rule Type section, select Content Source. In the Content Source list, click Technical Documents File Share.

•

In the Behavior section, ensure that Include is selected, and then click OK.

•


8-22


Exercise 2: Building Indexes In this exercise, you will configure crawl rules for a Web site and specify the default content access account. You will also perform a full crawl for each of the content sources to build an index. The principal tasks for this exercise are as follows:

f

f

f

•

Build the index.

•

Review the crawl log.

•

Update the search scopes.

Build the index Tasks

Detailed Steps

1.

•

In the breadcrumb control, click Search Settings.

•

On the Configure Search Settings page, click Content sources and crawl schedules.

•

Point to Local Office SharePoint Server Sites, and in the list that appears, click Start Full Crawl.

•

Point to Technical Documents File Share, and in the list that appears, click Start Full Crawl.

•

Point to SharePoint Technical Documents File Share, and in the list that appears, click Start Full Crawl.

•

Next to the New Content Source link, click Refresh until the Status for each content source reads Idle. This might take up to 10 minutes.

Start a full crawl of each content source.

Review the crawl log Tasks

Detailed Steps

1.

•


•

Click Crawl logs.

View the contents of the crawl log.

•

Click litwareportal.

•

Review the content that was crawled by clicking the right pointing arrow next to 1 – 50 until you have reviewed all 261 items.

Update the Tech Docs scope Tasks

Detailed Steps

1.

•


•

In the Scopes section, click Start update now.

•

After a minute, press F5 to refresh the page. Ensure that the Scopes needing update item reads 0.

•

In the Address bar, type http://litwareportal/ and then press ENTER.

•

On the Site Actions menu, point to Site Settings, and then click

2.

Update scopes.

Add the scope to the LitwarePortal site.


Tasks

8-23

Detailed Steps Modify All Site Settings. •

In the Site Collection Administration section, click Search scopes.

•

Click Search Dropdown.

•

Select Tech Docs, and then click OK.

•

Click the Home tab.

•


8-24


Exercise 3: Performing Searches In this exercise, you will perform several searches. These searches will show you how to use content scopes and Search Center to refine your searches. You will also search for people within the organization and see their relationships with other people in the organization. The principal tasks for this exercise are as follows:

f

•

Perform basic searches.

•

Perform an advanced search.

•

Perform a people search.

Perform basic searches Tasks


1.

Perform a basic search from the LitwarePortal home page.

•

On the Home page, in the Search box, type planning search and press ENTER.

•

Review the results and the number of results returned.

Perform a basic search from the Document Center page.

•


•

On the Document Center page, in the Search box, type planning search and press ENTER.

•

Review the results and the number of results returned. The results are the same as those returned by the previous search.

•


•

On the Document Center page, select Tech Docs in the list next to the Search box.

2.

3.

f

Perform a basic search within the Tech Docs content scope from the Document Center page.

•

In the Search box, type planning search and press ENTER.

•

Review the results and the number of results returned. The results are for documents that are defined by the rules for the Tech Docs content scope. Fewer results are returned than from the previous searches.

Perform an advanced search Tasks


1.

•

On the Search page, in the Search box, type document libraries and press ENTER.

•

Review the results and the number of results returned.

•

Click the Advanced Search link next to the Search box.

•

On the Advanced Search page, in the Narrow the search section, in the Result type list, click Word Documents.

•

In the Add property restrictions section, in the Where the Property list, click Name.

•

In the box, type moss

•

Click Search.

2.

Start with a basic search.

Narrow the results by performing an advanced search.


Tasks


f

8-25

Review the results. Fewer results are returned than from the previous search.

Perform a people search Tasks


1.

•

Perform a people search.

On the Search page, just above the Search box, click the People tab.

•

In the Search box, type Administrator and press ENTER.

•

Click the first result. You are redirected to your My Site.

•

In the Colleagues section, you will see an entry for Student. Click the Student link. You can now see the Student user’s colleagues.

•



8-26


Review

Review You have now completed this module. You should now be able to: •

Explain the search and indexing features of Microsoft Office SharePoint Server 2007, and explain which features are provided by Windows SharePoint Services and which are provided by Microsoft Office SharePoint Server 2007.

•

Describe the process of defining content to be indexed, indexing that content, and performing searches.

Module 9: Maintaining and Optimizing Microsoft® Office SharePoint® Server 2007 Table of Contents Overview Lesson 1: Implementing Office SharePoint Server 2007 Backup and Restore Lab: Backing Up and Restoring Office SharePoint Server 2007 Configurations and Data Lesson 2: Monitoring Office SharePoint Server 2007 Lab: Monitoring Office SharePoint Server 2007 Solutions Lab Shutdown Review Course Evaluation

9-1 9-2 9-10 9-15 9-27 9-30 9-31 9-33


Module 9: Maintaining and Optimizing Microsoft® Office SharePoint® Server 2007

9-1

Overview

Microsoft® Office SharePoint® Server 2007 offers you both menu-driven and commandline options to back up and restore data and configurations. This module describes the options available for you to develop backup and restore strategies for your organization. The module also reviews the options available for optimizing performance and the tools provided by Office SharePoint Server 2007 and Microsoft Windows Server® 2003 to monitor and tune your solution. When you monitor performance, you must establish a realistic baseline for your implementation. Microsoft provides planning worksheets to help you to develop this baseline.


Describe the factors that affect the backup and restoration of Microsoft Office SharePoint Server 2007 data and the processes for performing backup and restore operations.

•

Describe the Microsoft Office SharePoint Server 2007 performance counters, and explain the significance of the most important ones.

•

Describe the process and concepts for monitoring and tuning Microsoft Office SharePoint Server 2007-based operations, explain the difference between throughput and response times, describe the factors that affect these two measurements, and describe approaches that you can use to maximize throughput and response times.

9-2


Lesson 1: Implementing Office SharePoint Server 2007 Backup and Restore

Office SharePoint Server 2007 offers more extensive backup and restore flexibility than previous versions of SharePoint Products and Technologies. The backup and restore options are based on Office SharePoint Server 2007 server farm level or content database level backups. Office SharePoint Server 2007 also has a Recycle Bin for recovery of minor deletions.


Describe how to back up Office SharePoint Server data and configurations.

•

Describe how to restore Office SharePoint Server data and configurations.


9-3

Discussion: Maintaining Office SharePoint Server 2007

Introduction The instructor will now lead a class discussion. Please ensure that you participate in the discussion, when appropriate, to ensure that you and the other class members benefit fully from the discussion.

Discussion Points You can use the following discussion points to help start the discussion. Feel free to discuss other related points as they arise. •

Describe some operational tasks that you need to perform for Office SharePoint Server 2007.

•

What are the key elements necessary to protect Office SharePoint Server 2007 sites and data from computer failures?

•

How can you establish an acceptable performance baseline for your Office SharePoint Server 2007 solutions?

•

What tools do you currently use for backing up your data?

•

Which of these backup methods do you use: o

Full?

o

Differential?

o

Scripts using command prompt tools (stsadm)?

o

Snapshots?

9-4


o

SAN?

o

High availability solutions?

o

Off-site storage?

o

Disaster recovery testing?

•

What tools do you currently use for performance management?

•

How do you optimize applications?

•

What are the hardware and software elements that can affect Office SharePoint Server 2007 solution performance?


9-5

Backing Up Office SharePoint Server 2007 Data and Configurations

Introduction You must maintain a complete and current backup set of your business data and the configurations of your solution to ensure its availability. You can then restore this backup set onto a new server system if necessary. Office SharePoint Server 2007 provides native tools that you can use to perform data and configuration backups from the Central Administration page. You can also use command-line tools to backup and restore Office SharePoint Server 2007. You must implement the Office SharePoint Server 2007 backup facilities within your overall backup strategy.

Central Administration Backup The backup and restore options are located in Central Administration, on the Operations page. You can back up the entire server farm or elements of the server farm, such as a single content database. The Select Component to Backup page presents you with a hierarchy of check boxes that you can use to select server farm elements. When you select the Farm check box, you can back up the entire Office SharePoint Environment, which includes content databases, configuration files, Shared Services Providers, and search indexes. Your selections are highlighted in blue. If you want a more granular backup, you can select individual components to back up. You can select from the following options: •

Farm. This backs up content and configuration data for the entire server farm.

9-6


•

Windows SharePoint Services Web Application. This backs up a collection of Central Administration Web applications.

•

SharePoint_AdminContent. This backs up content for the Web Application.

•

Shared Services Provider. This backs up the database and configuration settings for the Shared Service Provider, including indexes.

•

Content Database. This backs up specific content databases from a selected Web application.

•

Global Search Settings. This backs up the search settings for the server farm.

•

Windows SharePoint Services Help Search. This backs up search instances for Windows SharePoint Services Help and search index files on the search server.

When you have selected the objects to back up, you can select a full or differential backup. A full backup copies all files. A differential backup copies only files changed since the last full backup was taken. Therefore, differential backups are faster. It is important to plan your backup schedule and decide how often you need to take a full backup. You should implement a minimum of a full backup once a week together with daily differential backups. You must plan the backup schedule when you review the volatility and business criticality of the Office SharePoint Server 2007 data. When you have selected the type of backup, you can then select where to save the backup files. It is essential that you test backup files regularly, by restoring to another location.

Command Line Backup You can use the stsadm command to run backup and restore commands from a command prompt. You can use these commands with a script to create your own backup schedule. The stsadm -o backup command can back up either site collections or the entire server farm, which is referred to as catastrophic backup in the command help. To get a syntax description for the backup option, type the following command at a command prompt. stsadm –help backup

This displays the following result. For site collection backup: stsadm.exe -o backup -url -filename [-overwrite] For catastrophic backup: stsadm.exe -o backup -directory -backupmethod [-item ] [-percentage ] [-backupthreads ] [-showtree] [-quiet]


9-7

It is useful to see a full example to understand the semantics of the command. For example, to back up a site collection called mysitecollection from litwareportal to a directory called backup on the C: drive, type the following at the command prompt. Stsadm –o backup –url http://litwareportal/sites/mysitecollection -filename c:\backup

This creates a subdirectory called backup1 in c:\backup, within which the site collection is backed up. To create a new backup, you must either add the -overwrite switch to your command or specify a new target location.

9-8


Restoring Office SharePoint Server 2007 Data and Configurations

Introduction You must ensure that you can successfully restore backups that you have generated. Office SharePoint Server 2007 provides menu-driven and command-line options for restoring backups.

Central Administration Restore The Restore from Backup page initially prompts you for the location of the backup files. When you specify the file location, Office SharePoint Server 2007 shows a history of the backups that exist at that location. You can select the appropriate backup and specify the components that you want to restore. You are presented with a list of available components. For example, a full backup of a site collection will allow you to restore only that site collection, but a full backup of a server farm will allow you to restore any of the available components of the server farm. The component options are the same as the backup component options, such as Farm, Windows SharePoint Services Web Application, SharePoint_AdminContent, Shared Services Provider, Content Database, Global Search Settings, and Windows SharePoint Services Help Search. When you have made your selection, you are prompted as to whether this is a new configuration or the existing configuration. You must also provide user logon details for SQL authorization. For new configurations, you must also specify the Web application


9-9

URL and name, the database server name, file location on the server, and the new name for the new databases.

Command-Line Restore You can use the stsadm command to run a restore command from a command prompt. The stsadm -o restore command can restore site collections. It can also restore an entire farm that you have backed up by using the stsadm -o backup command. To get a syntax description for the backup option, type the following command at a command prompt. stsadm –help restore

This displays the following result. For site collection restore: stsadm.exe -o restore -url -filename [-hostheaderwebapplicationurl <web application url>] [-overwrite] For catastrophic restore: stsadm.exe -o restore -directory -restoremethod [-backupid ] [-item ] [-percentage ] [-restorefarm] [-showtree] [-suppressprompt] [-username <username>] [-password <password>] [-newdatabaseserver ] [-quiet]

The Recycle Bin The Recycle Bin available in Office SharePoint Server 2007 is not a structured restore facility like the stsadm command or the Backup and Restore menu options. However, it does allow users to replace data objects that they have inadvertently deleted. The Recycle Bin settings are in the Web application settings page. You can choose to have the Recycle Bin available to all applications, and you can specify the number of days that the deleted data is maintained. There are two stages in the recycle process. The first stage of the Recycle Bin is available to all users and provides a site level view of deleted content, but users can only retrieve items that they deleted. The second stage is the administrator level, or Site Collection Recycle. Only administrators can access this stage.

9-10


Lab: Backing Up and Restoring Office SharePoint Server 2007 Configurations and Data


Back up Microsoft Office SharePoint Server 2007 configurations and data.

•

Restore Microsoft Office SharePoint Server 2007 configurations and data.




•


Lab Scenario Litware Inc. has a business-critical Office SharePoint Server 2007 implementation. Part of the initial brief for the solution was that it should be available to all users. A crucial element of availability is that the company has a robust backup and restore strategy, to protect business data and configurations against loss. The IT group must develop and test data and configuration backup and restore routines.


9-11

Exercise 1: Performing Backup Operations In this exercise, you will back up the data and configuration information for a site collection. The principal tasks for this exercise are as follows:

f

•

Back up site content and configurations by using the Central Administration interface.

•

Back up server farm content by using the stsadm command.

Back up site content and configurations by using the Central Administration interface Tasks


1.

•


•

Expand My Computer, and then click AllFiles (E:).

•

On the File menu, point to New, and then click Folder.

•

Type Backup and then press ENTER.

•

Double-click the Backup folder.

•

On the File menu, point to New, and then click Folder.

•

Type FarmBackup and then press ENTER.

•

On the Start menu, point to All Programs, point to Microsoft Office Server, and then click SharePoint 3.0 Central Administration.

•

On the Central Administration page, click the Operations tab.

•

In the Backup and Restore section, click Perform a backup.

•

Select SharePoint – 80.

•

Click Continue to Backup Options.

•

In the Type of Backup section, ensure that the Full option is selected.

•

In the Backup location box, type E:\Backup and then click OK.

•

On the Backup and Restore Status page, click Refresh until details of the backup are displayed.

•

Click Refresh and scroll down to see the phase that the backup has reached. This should read In process for the SharePoint – 80 item and the WSS_Content item.

•

Click Refresh until the Progress reads Completed for both items.

Back up site content only.

9-12

f


Back up server farm content by using the stsadm command Tasks


1.

•

On the Start menu, point to All Programs, point to Accessories, and then click Command Prompt.

•

At the command prompt, type cd "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN" and then press ENTER.

•

At the command prompt, type stsadm -help backup and then press ENTER.

•

Review the options for the stsadm -o backup command.

•

At the command prompt, type stsadm -o backup -directory E:\Backup\FarmBackup -backupmethod full –showtree and then press ENTER.

•

Review the Office SharePoint Server 2007 hierarchy that the command will back up.

•

At the command prompt , type stsadm -o backup -directory E:\Backup\FarmBackup -backupmethod full and then press ENTER. The backup process starts.

•

When the process has completed, use Windows Explorer to browse to the E:\Backup\ folder.

•

Review the contents of the folder and its subfolders.

2.

Review farm backup by using the stsadm.exe command.

Back up the entire farm by using the stsadm.exe command.


9-13

Exercise 2: Performing Restore Operations In this exercise, you will restore data and configuration information for a site collection. The principal tasks for this exercise are as follows:

f

•

Restore site content and configurations by using the Central Administration interface.

•

Restore content by using the stsadm command.

Restore site content and configurations by using the Central Administration interface Tasks 1.

f


Restore site content and • configuration information • only. •

Switch to Internet Explorer. Click the Operations tab. In the Backup and Restore section, click Restore from backup.

•

In the Backup location box, change the location to E:\Backup and then click OK.

•

Select the backup for Farm\Windows SharePoint Services Web Application\SharePoint - 80.

•

Click Continue Restore Process.

•

Select SharePoint – 80.

•

Click Continue Restore Process.

•

Select the Same Configuration option.

•

In the Microsoft Internet Explorer dialog box, click OK.

•

Click OK, and then on the Backup and Restore Status page, click Refresh until details of the restore are displayed.

•

Click Refresh until the progress reads Completed for both the SharePoint – 80 and the WSS_Content items.

Restore content by using the stsadm command Tasks


1.

•

On the Start menu, point to Administrative Tools and then click Services.

•

Scroll down until you can see the Windows SharePoint Services Administration service.

•

Right-click the Windows SharePoint Services Administration service, and then click Start. Wait for the service to start before continuing with this exercise.

Restore an entire farm by using the stsadm.exe command.

Important: If you do not start this service before attempting to restore a server farm, the restore operation will fail. Note that this service is not configured to start automatically. •

Switch to the command prompt window.

•

At the command prompt , type stsadm -help restore and press ENTER. Review the options for the stsadm -o restore command.

•

At the command prompt, type stsadm -o restore -directory

9-14


Tasks

Supporting information E:\Backup\FarmBackup -restoremethod overwrite and press ENTER. •

You are prompted that all selected items will be overwritten. Type Y and then press ENTER.

•

When the restore process has completed, review the messages in the command prompt window. Then close the command prompt window.

•

Close Windows Explorer and then close Internet Explorer.

Important: After you complete the lab, you must leave the 5061A_LON-DC-01-09 virtual machine running; you will continue with the virtual machine in the next lab.


9-15

Lesson 2: Monitoring Office SharePoint Server 2007

You must monitor the performance of your Office SharePoint Server 2007 solution to maintain user productivity and solution availability. The Performance Monitor available with Windows Server 2003 provides you with you the tools to monitor critical server performance statistics, such as processor performance and paging. In addition to these metrics, Office SharePoint Server 2007 adds solution-specific counters.


Explain the reasons for monitoring performance and availability.

•

Explain how to use and interpret Microsoft Office SharePoint Server 2007 performance counters.

9-16


Using Performance Monitor

Introduction Most organizations routinely monitor hardware and application performance and availability metrics. This provides benchmarks that you can use to analyze trends and provide proactive solution maintenance, such as system upgrades or solution tuning. Microsoft provides the Performance Monitor tool to trace system activity on your Windows Server 2003 system.

Monitoring Performance Server performance metrics for Office SharePoint Server 2007 are based primarily on the response time available to clients’ systems; users are most concerned with the refresh rate available in their browsers. As an administrator responsible for monitoring performance, you must ensure that users receive optimal performance. There are a range of factors that will affect this, such as the following: •

Server performance

•

Application performance

•

Network performance

•

Client performance

Within each of these factors there are subsystems and protocols that you can monitor and tune. You must identify the bottlenecks that have an adverse effect on user productivity.


9-17

Performance monitoring is an ongoing process. You must establish an acceptable performance benchmark and then gather performance data that you analyze against this target. This enables you to identify trends and preempt performance issues.

Monitoring Availability Availability monitoring differs from performance monitoring, because the goal is to identify failures rather than trends. You must identify points of critical breakdown and ensure that you are alerted when one occurs. For example, server hardware or database connectivity failures may make an Office SharePoint Server 2007 solution unavailable to users. To mitigate this, you must incorporate alerts into your solution design. This may involve the use of network or system monitoring tools which alert you when threshold transgressions occur, such as a disk becoming full, a network failure, or a processor malfunction.

Using Performance Monitor Windows Server 2003 provides the Performance Monitor as a component of the Microsoft Management Console. Performance Monitor measures the data (performance counters) from the performance objects that are built into the operating system or from applications running on a system. You can select from a comprehensive array of performance objects to trace and analyze current and historical data on subsystem performance. Performance Monitor can also create alerts about threshold incidents, such as excessive Microsoft SQL Server™ Lock Waits, which might indicate that the SQL Server is unable to cope with the volume of user requests. You can create and schedule performance and availability management tasks. Against each task you can set an action, such as sending an alert. You can display the output from Performance Monitor as a graph or as a report. You can also optionally save log files for later analysis.

Monitoring Shared Service Providers A Shared Service Provider (SSP) shares resources for shared services in the server farm. Business Data Catalog (BDC) is a shared service in Office SharePoint Server 2007. You can trace the performance of the BDC by monitoring the SQL connections counters.

Microsoft Operations Manager Microsoft Operations Manager (MOM) provides an Office SharePoint Server 2007 Pack that monitors events in the application event log. The management pack provides alerts on events that might indicate possible service provision or configuration problems, such as the following: •

Data backup or restore fails.

•

Core services (such as search, alert notifications, and administration) are not running.

•

Content source crawl fails.

•

Search propagation of one or more content indexes fails.

9-18


•

Audience compilation or profile import fails.

Performance and Capacity Guidelines There are some base guidelines for performance and capacity planning for Office SharePoint Server 2007. These can only offer broad guidance, as each Office SharePoint Server 2007 solution will have its own unique requirements. Recommended guidelines are detailed in the following table. Element

Guideline

Maximum number of site collections in an Office SharePoint Server 2007 database

50,000

Maximum number of Web sites in a site collection

250,000

Maximum number of lists in a site

2,000

Maximum number of items in a list

10,000,000

Maximum number of documents in a document library

2,000,000

Maximum number of documents in a folder

2,000

Maximum document size in a file

2Gb

Maximum number of indexed Items in an SSP

50,000,000

Maximum number of search scopes in a site collection

1,000

Maximum number of number of profiles in an SSP

5,000,000


9-19

Office SharePoint Server 2007 Performance Counters

Introduction There are some server and application counters that are essential when you monitor the performance of your Office SharePoint Server 2007 implementation. Some of these are server focused, such as processor or memory performance. However, others are specific to Office SharePoint Server 2007.

Generic Performance Objects and Counters There are a number of generic performance counters that you should monitor with Performance Monitor for any server system. The following table outlines these counters. Performance Object (Counter) Processor (% Processor Time)

Network Interface (Bytes Total/sec)

Logical Disk (% Idle Time and % Free Space)

Description This shows processor usage over a period of time. If this is consistently too high, over 75-85%, you may find performance is adversely affected. Remember to count “Total” in multiprocessor systems. You can measure the utilization on each processor as well, to ensure balanced performance between cores. This is the rate at which data is sent and received via the network interface card. You may need to investigate further if this rate is over 40-50% network capacity. To fine tune your investigation, monitor Bytes received/sec and Bytes Sent/sec. There are a number of logical disk options that you should review. You need to monitor peak disk activity. The percentage of idle time shows if disks are overloaded. You may want to check each logical disk. You should also always be aware of the available disk space. To further assess your logical disks, investigate Disk Write/sec

9-20


Performance Object (Counter)

Description and Disk Reads/sec.

Physical Disk (Avg. Disk Queue Length)

Paging File (% Usage and % Usage Peak)

Memory (Available Mbytes) Server (Various) ASP.NET Applications AND ASP.NET (Request Wait Time) Cache (Various)

This is the average number of read and write requests that were queued for the selected disk during the sample interval. You should keep this below 2. Excessive disk queuing affects performance. The server paging file, sometimes called the swapfile, holds “virtual” memory addresses on disk. Page faults occur when a process has to stop and wait while required “virtual” resources are retrieved from disk into memory. These will be more frequent if the physical memory is inadequate. You can review Page Faults/sec in the Memory performance object. This shows the amount of physical memory available for allocation. Insufficient memory will lead to excessive use of the page file and an increase in the number of page faults per second. There are a number of server related counters that measure session, logon, access, and file metrics. Office SharePoint Server 2007 provides the building block for an HTML page that are rendered in the user browser over HTTP. As the number of wait events increases, users will experience degraded page rendering performance. The effective use of the cache for read and write operations can have a significant effect on server performance. You must monitor for increased cache failures, indicated by a reduction in the Async Fast Reads/sec or Read Aheads/sec.

Office SharePoint Server 2007 Performance Objects and Counters In addition to the generic performance objects and counters applicable to any server or Web server, there are a number of Office SharePoint Server 2007 performance objects and counters that you should review with Performance Monitor. The table outlines the key Office SharePoint Server 2007 performance objects and counters. Performance Object (Counter)

Description

SharePoint Search Archival Plug-in

This indicates the number of documents waiting in a queue. When this number grows, users will suffer degraded performance.

(Blocked documents) SharePoint Search Gatherer (Idle Threads) SharePoint Search Gatherer Process (Waiting Documents)

SharePoint Search Indexer Catalog

This indicates the number of threads, or processes, waiting for documents. An increase in this number may lead to reduced performance for users. This is the number of documents waiting to be processed. When this number goes to zero, the catalog is idle. This number indicates the total queue size of unprocessed documents in the gatherer. If this number increases, it may indicate a processing bottleneck. This performance object and its counters indicate the performance of the indexer catalog. This will show the size and the status of processes such as merges.


Performance Object (Counter)

9-21

Description

(Various) SharePoint Search Schema Plug-in

This performance object and its counters provide information about documents and aliases.

(Various) Web Service (Various)

You can select specific Office SharePoint Server 2007 instances to monitor, including Microsoft SharePoint Administration, SharePoint Central Administration v3, and SharepointSSPWeb.

Interpreting Counters There are seldom definitive values for counters, which is why performance monitoring is an ongoing process. To keep track of counter variables over time, archive periodic performance samples. These samples will indicate changes in usage. If queue lengths increase or thread processing per second decreases then more users are competing for the finite resources on your Office SharePoint Server 2007 implementation. You can compare the current capacity status of your implementation against the initial planning benchmark, which will give advanced warning that you should upgrade hardware or modify your server topology.

9-22


Page Request Cycles

Introduction The page request cycle defines the steps taken when a page is rendered into a client browser. Page request cycles are more complex in Web applications than they are for other interactive applications, because a page is often built from a collection of component parts. The content of these parts may exist on remote servers in different applications. The basic steps in the page cycle are as follows: •

A Web application receives an HTTP Request.

•

The request is processed.

•

The request for component parts of an HTML page is serviced by the application.

•

The page is rendered as a single HTML page within the client browser.

Page request cycle performance is dependent on the complexity of the page and the diversity of its component elements.

Office SharePoint Server 2007 Page Requests An Office SharePoint Server 2007 page structure uses a series of elements to construct the final page. These elements include: •

Master page.

•

Page layout page.

•

Content of the page.


•

9-23

Content for Web Parts, retrieved from the database.

Each element can cause a performance overhead. The use of custom Web Parts can cause serious response overheads. For example, a Web Part that renders the folders and files document library as items in a list can cause a significant performance problem if there is a complex folder structure. The process will iterate through the entire folder hierarchy before delivering results to the page. To alleviate this, modify the search code to display only the next folder level.

Application Specific Performance Monitoring for Page Requests An Office SharePoint Server 2007 administrator should work with a development team to advise on performance monitoring standards. It is useful to include performance optimization counters when you test code. This inclusion of diagnostic code is sometimes called instrumentation. For example, the developer should include a timer counter. The timer is triggered as the Web Part begins to render and switched off when the Web Part load completes. The developer can implement this as a counter or an event log. You can add counters to Performance Monitor to check specific page performance. You must have administrative privileges to create performance counters and event log sources in code. When you monitor the performance of Web Parts that contain privileged code, you must ensure that the following conditions are met: •

Performance counters and event log sources have already been manually created on the server.

•

The developer has included a WindowsInstaller class that creates performance counters and event log sources as part of the setup routine.

•

The instrumented code runs with administrative privileges for the purposes of testing.

9-24


Baselining for Performance

Introduction It is important to understand that well-written applications run efficiently on appropriate supporting hardware and software. There is no undocumented procedure that makes software perform more quickly. Acceptable performance is a consequence of planning. You must select the correct product and topology to service your performance requirements. Microsoft provides a number of planning worksheets that are specifically designed to help you establish the correct baseline for future performance monitoring and analysis. These include the following: •

Estimate data capacity requirements worksheet.

•

Estimate peak throughput worksheet.

Estimating peak throughput enables you to identify potential volume bottlenecks early in the planning cycle. You must review the output of the planning exercise against system and topology capacity for your platform. When you have established this baseline, you can monitor response times against the acceptable standard.

Planning Throughput Throughput describes the number of operations that occur on a system over a defined period. The Estimate peak throughput worksheet enables you to gather the following key elements required for throughput analysis: •

Number of users.


•

Percentage of active users per day.

•

Total number of operations per active user per day (common + complex).

•

Number of business hours per day.

9-25

These elements provide an average estimated throughput, based on the following calculations: •

The number of users is multiplied by the percentage of active users.

•

The result is multiplied by the total number of operations per active user per day.

•

The result is divided by the product of 3,600 (seconds in an hour) and the number of business hours per day to provide the number of operations per second. Note: In the worksheet, the number of seconds in an hour is also multiplied by 100 to provide the result as a percentage.

You must weight this average with a value from 1 to 5 to show estimated peak time operations. These may be affected by the complexity of an operation, For example, a page that uses a number of Web Parts that make multiple database requests will mean that each page read operation is more complex. You should complete estimation sheets for each of your site types, such as Team Sites or Records Repositories. The different operational requirements of different Office SharePoint Server 2007 solutions may have a significant impact on the peak throughput. This planning worksheet can help you establish an estimated baseline for your throughput capacity. You can monitor counters such as ASP.NET Current Requests to tune the elements of the calculations.

Measuring Response Times User response times are the single most important performance metric in any interactive application. This is particularly the case with browser client interfaces. Measuring response times is not difficult; a stopwatch or a watch that can display seconds will allow you to establish good working standards. You must ensure that you monitor at appropriate times to ascertain realistic timings. The following table outlines the key times that you should record. It also outlines possible follow-up actions. Key Response Criteria

Description

Follow-up Actions

Primary logon and logoff times

Processing logons may present Use Performance Monitor to performance problems that are trace logon responses. not related to your Office SharePoint Server 2007, such as an overloaded domain controller or a problem with remote clients.

Peak work times

This can include period ends or Use Performance Monitor to product launch dates and may be trace performance information. particular to specific departments. These may not have any connection with the Office

9-26


Key Response Criteria

Description

Follow-up Actions

SharePoint Server 2007 server but may increase network or other server traffic. All workgroups

As some departments may use Use Performance Monitor to unique databases, it is important trace performance information. to have a schedule for measuring response times for each.

Recurring assessment

You should monitor samples at similar points in the day at different periods. This will minimize errors caused by anomalies.

Create a schedule that ensures a valid range of data input and enables you to identify anomalies.


9-27

Lab: Monitoring Office SharePoint Server 2007 Solutions


Add performance counters to Performance Monitor.


Introduction In this lab, you will work individually to complete a virtual machine exercise and a paper-based exercise to monitor system performance and estimate system throughput requirements.

Lab Setup For this lab, you will use the virtual machine from the previous lab in this module.

Lab Scenario The Litware, Inc. Office SharePoint Server 2007 implementation has proved a success. You are keen to maintain the level of user satisfaction for both the current implementation and the proposed extension to another company within the corporation. To maintain performance, you decide to monitor the current statistics and maintain a performance log. You also want to plan the capacity for a new deployment. To do this,

9-28


you must use the Microsoft worksheet to obtain a baseline for the throughput requirements.


9-29

Exercise 1: Monitoring Microsoft Office SharePoint Server 2007 In this exercise, you will add performance counters to Performance Monitor. The principal tasks for this exercise are as follows:

f

f

•

Add generic and Office SharePoint Server 2007 performance counters.

•

Create an alert.

Add generic performance counters Tasks


1.

•

On the Start menu, point to All Programs, point to Administrative Tools, and then click Performance.

•

Click New Counter Set, and then click Add.

•

In the Performance object list, click ASP.NET, click the Request Wait Time counter, and then click Add.

•

In the Performance object list, click Processor, click the % Processor Time counter, and then click Add.

•

In the Performance object list, click Logical Disk, click the % Space Free counter, and then click Add.

•

In the Performance object list, click Memory, click the Cache Faults/sec counter, and then click Add.

•

In the Performance object list, click Office Server Search Gatherer Process, click the Waiting Documents counter, and then click Add.

•

Click Close.

Add counters.

Create an alert Tasks


1.

•

In the left pane, expand the Performance Logs and Alerts option.

•

Right-click Alerts, and then click New Alert Settings.

•

In the New Alert Settings dialog box, type Office SharePoint Server 2007 Alerts, and then click OK.

•

Click Add.

•

In the Performance object list, click Logical Disk, and then click the % Free Space counter.

•

Click _Total, and then click Add.

•

Click Close.

•

In the Alert when value is list, click Under.

•

In the Limit box, type 20 and then click the Action tab.

•

Select Run this program, and type C:\WINDOWS\system32\perfmon.exe in the Run this program box.

•

Click the Schedule tab.

•

When prompted, provide a user name of Litwareinc\Administrator and a password of Pa$$w0rd, and

Create an alert in Performance Monitor.

9-30


Tasks

Supporting information then click OK. •

Click OK and then close Performance Monitor. Note: When the free disk space falls below 20 percent, Performance Monitor will start. You will not see this behavior in this lab.



9-31

Review


Describe the factors that affect the backup and restoration of Microsoft Office SharePoint Server 2007 data and the processes for performing backup and restore operations.

•

Describe the Microsoft Office SharePoint Server 2007 performance counters, and explain the significance of the most important counters.

•

Describe the process and concepts for monitoring and tuning Microsoft Office SharePoint Server 2007-based operations, explain the difference between throughput and response times, describe the factors that affect these two measurements, and describe approaches that you can use to increase throughput and response times.

You should now understand the major elements of how to protect your data by using the Office SharePoint Server 2007 backup and restore options. You should also be aware of the rationale for system monitoring and some of the tools available to help you monitor your Office SharePoint Server 2007 solution. It may be useful to reflect on how the module content will affect the data management and performance monitoring of your Office SharePoint Server 2007 implementation.

Review Questions •

How will you back up your Office SharePoint Server 2007 data and configurations in the future?

9-32


•

Which generic performance objects should you monitor on an Office SharePoint Server 2007 server?


9-33

Course Evaluation

Your evaluation of this course will help Microsoft understand the quality of your learning experience. Please work with your training provider to access the course evaluation form. Microsoft will keep your answers to this survey private and confidential and will use your responses to improve your future learning experience. Your open and honest feedback is valuable and appreciated.

Index A Access (Microsoft Office), 1.17 to 1.18 activating features, 4.22 Active Directory Directory Services, 1.26 to 1.27 activities, 6.32 administration administrative architecture, 1.34 to 1.35 business critical issues, 1.12 creating sites, 4.3 to 4.14 managing features, 4.15 to 4.22 My Sites personal sites, 5.9 Office Project Server 2007, 1.17 performance counters, 9.25 portal tools, 5.6 to 5.7 Recycle Bin, 9.10 server farms, 1.11 Shared Service Provider, 1.11 to 1.12 Administrators group, 3.10 to 3.11 ADO.NET, 7.5 alerts collaborative solutions, 1.21 creating, 9.31 threshold incidents, 9.19 anonymous authentication, 2.14 to 2.15 Antigen for SharePoint, 2.18 API (application programming interface), 7.23 appearance, 2.10 application definition files, 7.6 application servers, 3.16 Approval workflow, 6.29 Approver group, 6.8 to 6.9 ASP.NET, 2.15, 3.10 audiences content management and, 6.6 portal solutions, 5.22 auditing content policies, 6.48 implementing, 6.54 to 6.63 records management, 6.50 authentication choosing methods, 2.13 to 2.15 content deployment, 6.34 content policies, 6.47 LDAP and, 1.26 mixed methods, 2.15 protecting credentials, 2.15

Shared Service Providers, 3.20 single sign-on, 2.23, 5.15 authoring advanced approval processes, 6.31 to 6.32 approval process, 6.8 to 6.9, 6.29 to 6.30, 6.39 client applications, 6.23 content management and, 6.6 to 6.7 creating contributions, 6.9 Web browser, 6.22 to 6.23 authoring environment, 3.6, 6.33 authorization Active Directory and, 1.26 designing, 2.17 implementing, 2.16 to 2.18 restoring backups, 9.9 availability monitoring, 9.19 availability planning, 2.20 Availability Planning worksheet, 2.20 Available Mbytes performance counter, 9.22 Avg. Disk Queue Length performance counter, 9.22

B backups exercise, 9.13 to 9.14 overview, 9.6 to 9.8 restoring, 9.9 to 9.10 bandwidth, 5.13 barcodes, 6.48 baselining, 9.26 to 9.28 basic authentication, 2.14 BDC (Business Data Catalogs) business intelligence features, 4.19, 7.3 to 7.8 creating applications, 7.6, 7.31 to 7.33 data from external sources, 7.7 to 7.8 monitoring service, 9.19 Office Forms Server 2007, 1.16 overview, 2.22, 7.5 searching content, 8.4, 8.17 Shared Service Providers, 3.18, 3.21 single sign-on authentication, 5.15 support for, 1.9 User Profile feature, 5.17 Web Parts, 7.19 benchmarks, 9.18 Best Bets, 8.5, 8.17 BizTalk Server (Microsoft), 5.15 Blog template, 4.13

2

Index

Business Data Catalogs. See BDC (Business Data Catalogs) business intelligence solutions BDC applications, 7.3 to 7.8 decision making and, 1.5 design goals, 1.7 Excel Services, 7.9 to 7.13 features, 4.18 implementing, 7.29 to 7.43 implementing dashboards, 7.14 to 7.20 interoperability and, 2.23 Report Center Web sites, 7.21 to 7.25 server-side forms, 7.26 to 7.28 business requirements creating metadata, 6.20 functional specifications, 2.9 to 2.10 non-functional specifications, 2.10 to 2.11 planning worksheets, 2.11 Bytes/Total/sec performance counter, 9.21

C calendars, shared, 1.22 capacity, 2.10, 9.20, 9.26 Central Administration. See SharePoint Central Administration challenge-response, 2.13 Check In action, 6.27 Check Out action, 6.27 client applications authoring, 6.23 integrating with, 1.15 to 1.18 My Sites personal sites, 5.9 clustering SQL Servers, 3.16 Collaboration Portal template, 5.4, 7.22 collaborative solutions Active Directory users and groups, 1.26 e-mails, 1.21 implementing for portals, 5.10 to 5.15, 5.23 to 5.29 implementing user profiles, 5.16 to 5.22 My Sites personal sites, 5.8 overview, 1.4, 1.6, 1.14 shared calendars, 1.22 shared contacts, 1.22 shared tasks, 1.22 templates for, 4.12, 4.14 Colleague Tracker Web Parts, 5.12 Colleague Web Parts, 5.12 Collect Feedback workflow, 6.29 Collect Signatures workflow, 6.14, 6.29 communication, real-time, 5.13 Communicator (Microsoft Office), 5.13

compliance requirements ECM, 6.45 to 6.46 for records, 6.49 to 6.50 confidentiality, 6.46 configuration alternate access mappings, 3.15 to 3.16 application services, 3.16 backing up, 9.6 to 9.8 content types, 6.20 to 6.21 post-installation, 3.13 to 3.14 records routing, 6.51 restoring, 9.9 to 9.10 synchronizing Web/application servers, 3.16 Web Parts, 7.19 workflow, 6.12 configuration database, 1.34 contact objects (Active Directory), 1.27 Contact Web Parts, 5.11 contacts, shared, 1.22 content architecture, 2.10 Content Deployment Settings page, 6.33 content growth, 6.46 content management. See also also ECM (enterprise content management); also WCM (Web content management) content types, 6.19 to 6.21 defined, 6.6 deliverables, 6.7 feature scope, 4.19 to 4.20 file types, 6.19 implementing policies, 6.43 to 6.63 implementing processes, 6.28 to 6.41 managing documents and content, 6.15 to 6.27 Office SharePoint Server components, 6.10 to 6.12 Office SharePoint Server features, 6.13 to 6.14 solutions overview, 1.4, 1.6, 6.3 to 6.14 templates for, 6.17 to 6.18 content scope, 8.10 to 8.11, 8.17 content types configuring settings, 6.20 to 6.21 content management, 6.19 to 6.21 defined, 6.19 records repositories, 6.50 content, searching by, 8.3 crawlers, 8.9, 8.12 to 8.13 credentials Shared Service Providers, 3.20 single sign-on authentication, 2.23, 5.15 SQL Servers, 2.15 SSL encryption and, 2.14 to 2.15

Index

D dashboards creating, 7.37 to 7.38 implementing, 7.14 to 7.20 Report Center Web sites, 7.22 Data Protection Act (DPA), 6.45 data sources Business Data Catalogs, 7.5 content scope for, 8.10 defining for searches, 8.8 to 8.9, 8.21 to 8.22 KPI, 7.17 deactivating features, 4.22 "defense-in-depth" model, 2.18 deploying phase (MSF), 2.5 deployment completion milestone, 2.6, 2.8 content-based, 6.33 to 6.34 emergency, 6.34 environments for, 3.5 to 3.6 exercise, 3.22 to 3.27 of features, 4.16 prerequisites for, 3.7 to 3.8 server farm models, 3.4 server-side forms, 7.28 simplified, 4.16 to 4.17 single-server models, 3.3 design process. See MSF methodology Designer group, 6.8 developing phase (MSF), 2.5 development (team role), 2.7 to 2.8 development environment, 3.5, 6.31 development process Excel Services, 7.11 MSF methodology, 2.2 to 2.8 differential backups, 9.7 Discussion Web Parts, 5.11 Disposition Approval workflow, 6.14, 6.29 Document Center, 1.37, 4.14, 5.5 Document Information Panel, 6.26 document libraries actions, 6.27 capacity planning, 9.20 content management, 6.10 document information, 6.26 to 6.27 Excel Services, 7.12 functional specifications, 2.10 records management, 6.50 Reporting Services, 7.23 templates, 6.11 Document Library for Retaining Records worksheet, 6.50

Document Library Web Parts, 5.11 Document Workspace template, 4.12 documents/documenting actions, 6.27 associating information with, 6.26 to 6.27 functional specifications, 2.10 managing, 6.15 to 6.27, 6.38 non-functional requirements, 2.24 to 2.29 routing workflows, 1.19 security for, 2.17 site provisioning, 4.8 domain user accounts, 3.11 drilldown data, 7.8

E ECM (enterprise content management) defined, 6.7 issues, 6.45 to 6.46 Records Center site, 6.49 templates, 6.17 Else If branches, 6.32 e-mail Active Directory contact objects, 1.27 collaborative solutions, 1.21 content management and, 6.24 to 6.25 crawler settings, 8.13 LinkAccess, 1.22 managing mail folders, 1.22, 6.52 to 6.53 managing site storage quotas, 4.8 records repositories, 6.50, 6.52 to 6.53 encryption, 2.14, 6.34 enterprise content management. See ECM (enterprise content management) envisioning phase (MSF), 2.5 Estimate Data Capacity Requirements worksheet, 2.20 event log sources, 9.25 Excel (Microsoft Office) Excel Services, 7.10 publishing data, 7.13 Web Parts, 7.19 Excel Services as KPI data source, 7.17 to 7.18 business intelligence features, 4.18, 7.9 to 7.13 feature scope and, 4.17 overview, 1.16, 7.10 to 7.11 server farms and, 3.4 Shared Service Providers, 3.18, 3.21 trusted locations, 7.12 Excel Web Access Web Parts, 7.13 Exchange Public Folders, 8.8 Exchange Server (Microsoft)

3

4

Index

integrating with, 1.21 to 1.23, 6.53 records repositories, 6.52 to 6.53 expiration policy, 6.48 extranets content growth, 6.46 content policies, 6.47 link translation, 1.25 security for, 1.24 to 1.25 single architecture, 1.7

F Farm Administrators group, 4.8 Feature.sml file, 4.21 features activating, 4.22 deactivating, 4.22 defined, 4.15 managing, 4.15 to 4.27 overview, 4.10 to 4.12 search, 8.5 to 8.6 uninstalling, 4.21 file plans, 6.50 file types content management support, 6.19 crawler settings, 8.13 filters for, 8.3 supported, 1.15 filters content growth and, 6.46 content metadata, 8.3, 8.18 content scope as, 8.10, 8.17 permissions as, 8.12 firewalls, 5.14 form library, 6.10, 6.12 forms content policies, 6.47 server-side, 7.26 to 7.28, 7.39 to 7.43 solutions for, 1.5, 1.7 % Free Space performance counter, 9.21 full backups, 9.7, 9.9 Full Control permission, 4.11 full imports, 5.20 functional specifications, 2.9 to 2.10

G gacutil tool, 3.6 goal level (KPIs), 7.16, 7.18 Gramm-Leachy Bliley Act, 6.45 groups

authoring and approval process, 6.8 designing authorization, 2.17 site-management options, 4.11

H hardware deployment prerequisites, 3.8 monitoring performance, 9.18 to 9.19 Hierarchy Manager permission, 4.11 HTML, 6.23, 6.31, 9.24 HTTP Request, 9.24 HTTPS, 1.22 hyperlinks, 6.23

I Idle Threads performance counter, 9.22 % Idle Time performance counter, 9.21 IFilters, 8.12 IIS (Internet Information Services) anonymous authentication, 2.14 deployment prerequisites, 3.7 server farm deployments, 3.4 stand-alone server installations, 3.10 implementation. See also also specific solutions authorization and security, 2.16 to 2.18 preparing, 2.2 to 2.11 reviewing, 1.37 to 1.38 importing user profile data, 5.20 to 5.21 In Common Between Us Web Parts, 5.12 incoming URL, 3.15 incremental imports, 5.20 indexes backups, 9.7 building, 8.12 to 8.14, 8.23 to 8.24 overview, 8.3 to 8.4 Shared Service Providers, 3.18 indicator value (KPIs), 7.15, 7.18 Information Rights Management (IRM), 1.16 installation process exercise, 3.25 to 3.27 server farms, 3.11 SharePoint Central Administration Web application, 3.13 stand-alone servers, 3.10 instant messaging, 5.13 Internet, 1.7, 6.46 Internet Protocol (IP), 1.25 interoperability functional specifications, 2.10 non-functional requirements, 2.22 to 2.23 intranets

Index

content growth, 6.46 content policies, 6.47 single architecture, 1.7 IRM (Information Rights Management), 1.16

K Kerberos authentication, 2.13, 2.15 Key Distribution Center, 2.13 keywords, 8.5 to 8.6, 8.15, 8.17 Knowledge Network, 8.3, 8.15 to 8.16 knowledge, search by, 8.3, 8.5 KPIs (Key Performance Indicators) building dashboards, 7.19 to 7.20 decision making and, 7.14 defining, 7.17 to 7.18 overview, 7.15 to 7.16 support for, 1.10, 1.17 Web Parts, 7.19

L labels, 6.48 LDAP (lightweight directory access protocol), 1.26, 5.19 line-of-business applications as data sources, 7.5 portal solutions, 5.15 registering, 2.22 searching, 8.4, 8.8 link translation, 1.25 LinkAccess, 1.22 lists capacity planning, 9.20 data-driven, 7.7 e-mail enabled, 1.27 KPI, 7.17 Live Communications Server (Microsoft Office), 5.13 Lock Waits (SQL Server), 9.19

M macros, file formats and, 1.15 maintenance, 2.21 Manage Content Deployment Paths and Jobs page, 6.34 manageability, 2.21 meeting templates, 4.13 Member group, 6.8 metadata content types, 6.20 crawlers and, 8.12

document information, 6.26 to 6.27 document libraries, 6.12, 6.50 records management, 6.50 searching by, 8.3, 8.18 Microsoft Forefront Security for SharePoint, 2.18 Microsoft ISA Server, 1.24 to 1.25 Microsoft Management Console, 9.19 Microsoft MSN Messenger, 8.15 Microsoft Office Document Information Panel, 6.26 Microsoft Office Forms Server 2007, 1.16 Microsoft Office InfoPath 2007, 5.14, 7.27 Microsoft Office Project Web Access, 1.17 Microsoft Office SharePoint Portal Server, 7.27 Microsoft Operations Manager (MOM), 9.20 Microsoft SharePoint Directory Management Service, 6.25 Microsoft SQL Server. See SQL Server (Microsoft) Microsoft Windows Installer packages, 3.6 Microsoft Windows Messenger, 8.15 migrating solutions and content, 3.6 milestones, MSF methodology, 2.5 to 2.6 mixed authentication, 2.15 MOF (Microsoft Operations Framework), 2.7 to 2.8, 2.21 monitoring performance baselining, 9.26 to 9.28 exercise, 9.29 to 9.31 overview, 9.17 page request cycles, 9.24 to 9.25 performance counters, 9.21 to 9.23 Performance Monitor, 9.18 to 9.20 MSF methodology defined, 2.5 iteration, 2.6 milestones, 2.5 to 2.6 Office SharePoint Server and, 2.6 phases, 2.5 to 2.6 Team Model roles, 2.7 to 2.8 My Site Host template, 5.5 My Site personal sites, 5.8 to 5.9, 8.15 My Sites facility, 4.11

N navigation, 2.10 .NET Framework deployment prerequisites, 3.7 stand-alone server installations, 3.10 three-tier administration via, 1.34 News Home template, 4.13 noise words, 8.12 non-functional requirements

5

6

Index

authentication, 2.13 to 2.15 authorization and security, 2.16 to 2.18 documenting, 2.24 to 2.29 interoperability, 2.22 to 2.23 interpretation guidelines, 2.10 to 2.11 operational metrics, 2.19 to 2.21 notifications collaborative solutions, 1.21 Shared Service Providers, 3.18 site storage quotas, 4.10 NTFS file system, 3.7 NTLM authentication, 2.13, 2.15, 6.47

O Office Communicator, 8.15 Office PerformancePoint Server 2007, 7.24 Office SharePoint Server (Microsoft) administrative architecture, 1.34 to 1.35 components, 1.8 to 1.10 design goals, 1.6 to 1.7 features overview, 1.9 to 1.10 types of solutions, 1.4 to 1.5 Office SharePoint Server Forms Server, 7.26 to 7.28 Office SharePoint Server Publishing Infrastructure, 6.13 Office SharePoint Server Search Web Parts, 6.14 OneNote (Microsoft Office), 1.18 Open dialog box, 5.9 operational metrics, 2.19 to 2.21 outgoing URL, 3.15 Outlook (Microsoft Office) integrating with, 1.21 to 1.23 Knowledge Network and, 8.15 overview, 1.16 shared contacts, 1.22 shared tasks, 1.22 Owner group, 6.8 to 6.9

P Page Editing toolbar, 6.34 page request cycles, 9.24 to 9.25 passwords basic authentication, 2.14 Shared Service Providers, 3.20 single sign-on, 5.15 PDAs, 5.14 peak throughput, 9.26 to 9.27 People Search Core Results Web Parts, 5.12 People Search Web Parts, 5.12

people, searching by, 8.3, 8.5, 8.16 performance indexes and, 8.14 monitoring, 9.17 to 9.31 non-functional specifications, 2.10 operational metrics, 2.19 to 2.20 server farm deployments, 3.4 performance counters, 9.19, 9.21 to 9.23, 9.31 Performance Monitor tool, 9.18 to 9.23 permissions designing authorization, 2.17 Knowledge Network and, 8.16 managing, 2.16 property store table, 8.12 site-management options, 4.11 Web application policies, 6.47 personal sites, 4.11, 5.8 to 5.9 picture library, 6.10 to 6.11 PivotTables, 7.10, 7.13 planning availability, 2.20 for security, 2.16 to 2.17 planning phase (MSF), 2.5 planning worksheets, 2.11, 9.27 pluggable behavior, 4.16 to 4.17 policies implementing, 6.54 to 6.63 privacy, 5.17 records repositories, 6.50 Policy worksheet, 6.50 portal solutions BDC applications, 7.3 to 7.8 collaborative features, 5.10 to 5.15, 5.23 to 5.29 creating portal sites, 5.2 to 5.9 overview, 1.4, 1.6 user profiles and audiences, 5.16 to 5.22 PowerPoint (Microsoft Office), 6.11 privacy policies, 5.17 processors, 3.8 % Processor Time performance counter, 9.21 product management (team role), 2.7 to 2.8 production environment, 3.6, 6.33 profile information. See user profiles Profile Services administrators, 2.18 program management (team role), 2.7 to 2.8 project plan approval, 2.6, 2.8 Project Server (Microsoft Office), 1.17, 3.16 properties audiences and, 5.22 content scope, 8.10 creating with full imports, 5.20 property store table, 8.12

Index

searching by, 8.5, 8.18 user profile information, 5.17 to 5.19 property store table, 8.12 publishing content management and, 6.6 to 6.7, 6.37 Excel data, 7.13 Reporting Services and, 7.23 site collections, 6.37 templates for, 4.14, 6.18 Web, 6.33 to 6.34 Publishing Portal template, 5.4 to 5.5

Q Quick Deploy job, 6.34 Quick Deploy User group, 6.34 quotas, managing for sites, 4.8

R RAM, 3.8 Records Center site, 6.49 records management, 1.22, 6.49 to 6.51 Records Repository template, 4.13, 6.43, 6.50, 9.27 Records Routing Table worksheet, 6.50 Recycle Bin, 9.10 release management (team role), 2.8 release readiness approval, 2.6, 2.8 relevance settings for search results, 8.6 Report Center, 7.22 Report Center Site template, 4.14, 7.22 Report Center Web sites, 7.21 to 7.25 Report Viewer Web Parts, 7.23 Reporting Services (SQL Server), 7.23, 7.25 Reporting Web Parts, 7.20 Request Wait Time performance counter, 9.22 response times, measuring, 9.28 restoring backups, 9.9 to 9.10, 9.15 to 9.16 retention policies, 6.50 Routing workflow, 6.14 RSS feeds, 2.23 RSS Web Part, 2.23

S Sarbanes-Oxley Act, 6.45 Save As dialog box, 5.9 SB 1386 (bill), 6.45 scalability, 2.20, 3.4

scheduling imports, 5.20 scope completion, 2.6, 2.8 scoping rules, 4.16 to 4.17 Search Center template, 4.14 searches backing up settings, 9.7 content growth and, 6.46 defining content scope, 8.10 to 8.11, 8.21 to 8.22 defining content sources, 8.8 to 8.9, 8.21 to 8.22 enhanced features, 8.5 to 8.6 implementing, 8.25 to 8.26 index reports, 8.14 integrating with Knowledge Network, 8.15 to 8.16 noise words in, 8.12 overview, 1.4, 1.7, 8.3 to 8.4 performing, 8.17 to 8.18 Shared Service Providers, 1.8 to 1.9, 3.18 security authentication and, 2.14 content-based deployment, 6.33 e-mail, 6.25 for extranets, 1.24 to 1.25 identifying issues, 2.18 implementing, 2.16 to 2.18 non-functional specifications, 2.10 to 2.11 planning for, 2.16 to 2.17 Reporting Services, 7.23 Web application policies, 6.47 Self-Service Site Management, 4.9 to 4.10 sensitive information, 6.46 server farms administrative considerations, 1.11, 1.34 to 1.35 alternate access mappings, 3.15 to 3.16 as content sources, 8.8 backups, 9.6 to 9.7 content deployment, 6.33 content policies, 6.47 crawler settings, 8.13 deployment models, 3.4 feature scope and, 4.17 installing, 3.11 Kerberos authentication, 2.14 managing, 2.21 managing provisioning processes, 4.7 uninstalling features, 4.21 server-side forms, 7.26 to 7.28, 7.39 to 7.43 setproperty operation, 1.35 shared calendars, 1.22 shared contacts, 1.22 Shared Service Providers administrative considerations, 1.11 to 1.12 assigning content scopes, 8.11

7

8

Index

backups, 9.7 Business Data Catalogs, 7.6 creating content sources, 8.9 Excel Services, 7.12 index reports, 8.13 managing, 3.17 to 3.21 monitoring, 9.19 overview, 1.8 to 1.9 search relevance settings, 8.6 shared tasks, 1.22 SharePoint Central Administration administration tools, 1.35 backups, 9.6 to 9.7 creating content sources, 8.9 creating Shared Service Provider, 3.20 e-mail enabled lists, 1.27 e-mail support, 6.25 installing, 3.13 modifying configuration database, 1.34 restoring backups, 9.9 to 9.10 user interface, 4.8 Web site, 1.35 SharePoint Designer overview, 1.17 workflows for, 1.19, 6.12, 6.31 SharePoint Products and Technologies Configuration Wizard, 3.13 Simple Object Access Protocol (SOAP), 7.23 simplified deployment, 4.16 to 4.17 single sign-on authentication overview, 2.23 portal solutions, 5.15 Shared Service Provider, 3.18 single-server deployment, 3.3 Site Collection Recycle, 9.10 site collections available workflows, 6.14, 6.29 to 6.30 business intelligence features, 4.19 capacity planning, 9.20 content deployment, 6.33 content management features, 4.19, 6.13 to 6.14 content policies, 6.47 to 6.48 content scopes, 8.11 content types, 6.19 to 6.20 creating, 4.8 feature scope and, 4.17, 6.13 to 6.14 functional requirements, 2.10 security, 2.16 templates for, 6.17 to 6.18 Site Content Type Gallery, 6.19 Site creation worksheet, 4.8 site directory, 5.6

Site Directory Area Template, 4.14 Site hierarchy choices worksheet, 4.8 Site Maintenance Plan worksheet, 2.21 Site maintenance worksheet, 4.8 Site Manager, 5.7 site maps, 5.6 site provisioning, 4.7 to 4.8 Site User and Member Web Parts, 5.11 sites administrative portal tools, 5.6 to 5.7 business intelligence features, 4.19 capacity planning, 9.20 content management, 4.20, 6.35 to 6.41 content policies, 6.47 to 6.48 content types, 6.19 crawler settings, 8.13 creating, 4.3 to 4.14 feature scope and, 4.17, 6.14 functional requirements, 2.10 managing, 4.23 to 4.27 personal, 4.11 portal, 5.2 to 5.9 publishing, 6.37 security, 2.16 to 2.17 self-service creation, 4.9 to 4.10 storage quotas, 4.8 templates for, 4.12 to 4.14, 6.18 Smart Client Authoring, 6.23 Smartphones, 5.14 SMTP, 6.25, 6.53 SOAP (Simple Object Access Protocol), 7.23 software requirements, 3.7 SQL Server (Microsoft) administrative settings, 1.34 Business Data Catalogs, 7.5 clustering, 3.16 credentials, 2.15 deployment prerequisites, 3.7 Kerberos authentication, 2.14 Lock Waits, 9.19 Office PerformancePoint Server and, 7.24 Reporting Services, 7.23, 7.25 Shared Service Providers, 3.20 SQL Server 2005 Surface Area Configuration Tool, 3.11 SQL Server Analysis Services database, 7.5, 7.17 SSL (Secure Sockets Layer), 2.14 to 2.15 stabilizing phase (MSF), 2.5 staging environment, 3.6, 6.33 steps, 6.32 storage managing quotas, 4.8, 4.10

Index

My Sites personal sites, 5.8 report, 7.25 user profile data, 5.18 to 5.19 stsadm.exe utility automating tasks, 1.35 backups, 9.7 to 9.8 migrating solutions, 3.6 restoring backups, 9.10 subsites, 4.11 synchronizing Knowledge Network profile, 8.15 Web/application servers, 3.16

T Task Web Parts, 5.11 tasks authoring/approval process, 6.9 shared, 1.22 team clusters, 2.8 Team Model (MSF), 2.7 to 2.8 Team Site template, 4.12, 9.27 templates content management, 6.17 to 6.18 document libraries, 6.11 enterprise, 5.5 for records repository sites, 4.13, 6.43, 6.50 new page creation, 6.9 planning worksheets, 2.11 portal site, 5.4 to 5.5 Report Center Web site, 7.22 site, 4.12 to 4.14, 6.18 test (team role), 2.7 to 2.8 test environment, 3.5 thesaurus files, 8.12 Three-State workflow, 6.14, 6.29 Tier 1 logical level, 1.34, 4.7 Tier 2 logical level, 1.35, 4.7 Tier 3 logical level, 1.35, 4.7 timer counters, 9.25 Translation Management workflow, 6.14, 6.29 triggering workflows, 6.32 trusted locations, 7.12

U uninstall feature command, 4.21 URLs, 3.15, 5.9 % Usage Peak performance counter, 9.22 % Usage performance counter, 9.22

user accounts designing authorization, 2.17 domain, 3.11 Shared Service Providers, 3.20 user experience (team role), 2.7 to 2.8 user interfaces functional specifications, 2.9 SharePoint Central Administration, 4.8 Web browser, 6.23 Windows Workflow Foundation, 6.32 user management, 1.9 user names, 5.15 User Profile data, 5.18 user profiles Active Directory, 1.27 capacity planning, 9.20 data storage, 5.18 to 5.19 importing data, 5.20 to 5.21 in portal solutions, 5.18 overview, 5.16 to 5.19 Shared Service Providers, 3.18

V version management, 4.16 to 4.17, 6.7 video conferencing, 5.13 View Items permission, 2.14 vision/scope approval, 2.5, 2.8 Visitor group, 6.8 Visual Basic (Microsoft), 6.32 Visual C# (Microsoft), 6.32 Visual Studio (Microsoft) Custom Workflows, 6.31 Extensions for Windows Workflow Foundation, 6.12, 6.32 Project Deployment tools, 3.6 workflows for, 1.20

W Waiting Documents performance counter, 9.23 warning level (KPIs), 7.15, 7.18 WCM (Web content management), 6.7, 6.17 Web addresses, 8.10 Web applications backups, 9.7 business intelligence features, 4.19 content management features, 4.19 content policies, 6.47 feature scope and, 4.17 page request cycles, 9.24

9

10

Index

Web browsers, 6.22 to 6.23 Web content management. See WCM (Web content management) Web pages functional specifications, 2.10 page request cycles, 9.24 to 9.25 templates for creating, 6.9 three-tier administration via, 1.34 Web Parts collaborative features, 5.11 to 5.12 configuring, 7.19 dashboards, 7.19 data-driven, 7.7 drilldown data, 7.8 Excel Services and, 7.12 to 7.13 managing reports, 7.23 Web browser interface, 6.23 Web publishing, content-based, 6.33 to 6.34 Web servers deployment models, 3.4 deployment prerequisites, 3.8 synchronizing, 3.16 Web services Business Data Catalog and, 2.22 Office PerformancePoint Server, 7.24 WSRP, 2.23 Wiki page library, 6.10, 6.12 Wiki Site template, 4.13 Windows SharePoint Services mail folders, 6.52 search and indexing, 8.5 Web Application service, 3.13 Windows Workflow Foundation content management, 6.12 integrating with, 1.19 to 1.20 migrating solutions, 3.6 Runtime Components, 3.10 Visual Studio and, 6.12, 6.32 WindowsInstaller class, 9.25 Word (Microsoft Office), 1.15, 6.11 word breakers, 8.12 word stemmers, 8.12 Workflow Tasks, 6.9 workflows authoring and approval process, 6.8, 6.31 to 6.32, 6.39 configuring, 6.12 content management and, 6.7, 6.10, 6.12 content types and, 6.20 for document routing, 1.19 for Office SharePoint Designer, 1.19, 6.12 for Visual Studio, 1.20

integration scenarios, 2.23 migrating solutions and content, 3.6 site collections, 6.14, 6.29 to 6.30 WSRP (Web Services for Remote Portlets), 2.23

X xcopy tool, 3.6 XML, 6.23, 7.6

Microsoft Official Course 5061A Implementing Microsoft Office SharePoint Server 2007

Microsoft Office SharePoint Server 2007 Best Practices

Microsoft Office SharePoint Server 2007 - Das Handbuch

Microsoft® SharePoint® Server 2007 Bible

Microsoft Office System 2007 (Microsoft Official Academic Course Series)

Microsoft Office PerformancePoint Server 2007

Microsoft SharePoint 2007 for Office 2007 Users

Microsoft Office PerformancePoint Server 2007

Microsoft Office SharePoint Designer 2007 Bible

Professional Microsoft Office SharePoint Designer 2007

Professional Microsoft Office SharePoint Designer 2007

Microsoft SharePoint 2007 Unleashed

Microsoft Office SharePoint Designer 2007 Bible

Microsoft® Office SharePoint® Server 2007: A Beginner's Guide

Beginning SharePoint 2007 Administration: Windows SharePoint Services 3 and Microsoft Office SharePoint Server 2007

Microsoft SharePoint 2007 Unleashed

Microsoft SharePoint 2007 Unleashed

Microsoft Office Excel (2007)

Microsoft Office Excel 2007

Microsoft Office 2007. Самоучитель

Microsoft Office 2007 QuickSteps

Microsoft Office Word (2007)

Microsoft Office 2007 Simplified

Microsoft SharePoint Server 2010 Bible

Microsoft SharePoint 2007 Development Unleashed

Microsoft SharePoint 2007 For Dummies

Microsoft SharePoint 2007 Development Unleashed

Microsoft SharePoint 2007 For Dummies

Using Microsoft Office Outlook 2007

Microsoft Office 2007 Business Intelligence

Microsoft Official Course 5061A Implementing Microsoft Office SharePoint Server 2007

Microsoft Office SharePoint Server 2007 Best Practices

Microsoft Office SharePoint Server 2007 - Das Handbuch

Microsoft® SharePoint® Server 2007 Bible

Microsoft Office System 2007 (Microsoft Official Academic Course Series)

Microsoft Office PerformancePoint Server 2007

Microsoft SharePoint 2007 for Office 2007 Users

Microsoft Office PerformancePoint Server 2007

Microsoft Office SharePoint Designer 2007 Bible

Professional Microsoft Office SharePoint Designer 2007

Professional Microsoft Office SharePoint Designer 2007

Microsoft SharePoint 2007 Unleashed

Microsoft Office SharePoint Designer 2007 Bible

Microsoft® Office SharePoint® Server 2007: A Beginner's Guide

Beginning SharePoint 2007 Administration: Windows SharePoint Services 3 and Microsoft Office SharePoint Server 2007

Microsoft SharePoint 2007 Unleashed

Microsoft SharePoint 2007 Unleashed

Microsoft Office Excel (2007)

Microsoft Office Excel 2007

Microsoft Office 2007. Самоучитель

Microsoft Office 2007 QuickSteps

Microsoft Office Word (2007)

Microsoft Office 2007 Simplified

Microsoft SharePoint Server 2010 Bible

Microsoft SharePoint 2007 Development Unleashed

Microsoft SharePoint 2007 For Dummies

Microsoft SharePoint 2007 Development Unleashed

Microsoft SharePoint 2007 For Dummies

Using Microsoft Office Outlook 2007

Microsoft Office 2007 Business Intelligence

Recommend Documents