2423301.pdf

Contents

Overview 1

Lesson: The Architecture and Design of SharePoint Products and Technologies 2

Lesson: Features and Terminology for SharePoint Products and Technologies 8

Lab A: Installing SharePoint Products and Technologies on a Single Server 15

Lesson: Types of Servers 19

Lesson: SharePoint Products and Technologies Installation Options 24

Module 1: Introduction to SharePoint Products and Technologies

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. 2004 Microsoft Corporation. All rights reserved. Microsoft, MS-DOS, Windows, Windows NT, Windows Server, Active Directory, BizTalk, FrontPage, InfoPath, Microsoft Press, MSDN, OneNote, Outlook, PowerPoint, SharePoint, Visual Basic, Visual Studio, and Windows Media 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: Introduction to SharePoint Products and Technologies iii

Instructor Notes Microsoft® SharePoint� Products and Technologies is the next generation of SharePoint technology that greatly expands its capabilities to provide a central location for information sharing and collaboration. Although there are some similarities to previous technologies, it�s important for the students to learn the new and expanded capabilities that make it very different from its predecessor. Understanding the design and architecture and becoming familiar with the new features and terminology will enable the students to successfully deploy an implementation type that meets their business needs.

After completing this module, students will be able to:

! Understand the design goals and resulting architecture. ! Learn the new features and terminology. ! Become familiar with the server types and how they are part of the

implementation. ! Be introduced to the differing implementation types and capabilities.

To teach this module, you need the Microsoft PowerPoint® file 2012B_01.ppt.

It is recommended that you use PowerPoint 2002 or later to display the slides for this course. If you use PowerPoint Viewer or an earlier version of PowerPoint, all the features of the slides may not be displayed correctly.

To prepare for this module:

! Read all of the materials for this module.

Presentation: 1 hour, 15 minutes Lab: 45 minutes

Required materials

Important

Preparation tasks

iv Module 1: Introduction to SharePoint Products and Technologies

How to Teach This Module This section contains information that will help you to teach this module.

Lesson: The Architecture and Design of SharePoint Products and Technologies

Stress that SharePoint Products and Technologies is designed to promote collaboration.

These include consistent experience, integration with Microsoft .NET framework, integrated storage strategy, and trustworthy computing: security and reliability.

Lesson: Features and Terminology for SharePoint Products and Technologies

The intent of the instructor-led practices is to familiarize the students with the user interface. The goal for the students is not to complete the process but to be prepared for the lab exercises.

Take 20 minutes to open up Cardiff on the instructor�s computer and show the features of SharePoint Portal Server from a user�s perspective. You can show the basic portal architecture including the home page, topics, news, My Site, and the site registry. You can practice the portal search feature, or how to use a document library, and so forth. You may also illustrate how to create a Microsoft Windows® SharePoint Services site and then demonstrate how you can then build a site collection from that site.

You, the instructor, may keep the Cardiff virtual computer running for the entire module for use in the instructor-led practices. Since you will not be completing the lab yourself, there is no need to have the Dublin virtual computer running.

At the end of each day in the classroom, keep the virtual computers running for use in the next day�s class. Restarting the computers will require a minimum of 30 minutes.

There are some terms that have changed and there are also some new terms dealing with SharePoint Products and Technologies. Be sure to know what these terms are and how they are defined.

Take 10 minutes to open Cardiff on the instructor�s computer and show some of these items.

Architectural Overview

Design Goals

Instructor-Led Practice: Features of SharePoint Products and Technologies

SharePoint Products and Technologies Terminology

Module 1: Introduction to SharePoint Products and Technologies v

Lab A: Installing SharePoint Products and Technologies on a Single Server

This lab is included at this point due to the time required for SharePoint Products and Technologies to install on the Dublin virtual computer.

DO NOT have the students shut down the Dublin virtual computer upon completion of the lab, as it will be necessary to complete the SharePoint Products and Technologies installation in the next module.

Lesson: Types of Servers Take 10 minutes to open up the instructor computer and show how Madrid will act as a front-end server

Take 10 minutes to open up the instructor computer and show how Melbourne will act as a back-end server

Lesson: SharePoint Products and Technologies Installation Options

Take 10 minutes to open up the instructor computer and show how Cardiff supports a single-server deployment

Take 10 minutes to open up the instructor computer and show how Madrid supports a server farm deployment

Exercise 1: Installing SharePoint Products and Technologies

Warning

Front-End Servers

Back-End Servers

Single Server Scenario

Server Farm Scenario

vi Module 1: Introduction to SharePoint Products and Technologies

Lab Results Performing the lab in this module introduces the following configuration change:

! Lab A: Installing SharePoint Products and Technologies on a Single Server

• Exercise 1: Installing SharePoint Products and Technologies At the end of this lab SharePoint Products and Technologies will be installed, but not configured on the Dublin virtual computer.

Module 1: Introduction to SharePoint Products and Technologies 1

Overview

*****************************ILLEGAL FOR NON-TRAINER USE******************************

Microsoft® SharePoint� Products and Technologies provide a central location for information sharing and collaboration. Although there are some similarities to previous technologies, there are many new and expanded capabilities that make it very different from its predecessor. Understanding the design and architecture and becoming familiar with the new features and terminology will enable you to successfully deploy an implementation type that meets your business needs.

After completing this module, you will be able to:

! Explain the design goals for SharePoint Products and Technologies and the resulting portal architecture.

! Explain the SharePoint Products and Technologies features and terminology.

! Explain the types of server and how they are part of the implementation. ! Explain implementation types and capabilities.

Introduction

Objectives

2 Module 1: Introduction to SharePoint Products and Technologies

Lesson: The Architecture and Design of SharePoint Products and Technologies


The architecture and design of the SharePoint Products and Technologies are based on the original 2001 versions of SharePoint technologies. Feedback was gathered from customers and numerous deployments to determine the design goals that led to the existing architecture. In this lesson, you will find an introduction to SharePoint Products and Technologies and a detailed description of their design and architecture.

After completing this lesson, you will be able to:

! Explain the SharePoint Products and Technologies. ! Explain the architecture of SharePoint Products and Technologies. ! Explain the design goals of SharePoint Products and Technologies.

Introduction

Lesson objectives


Introduction to SharePoint Products and Technologies


SharePoint Products and Technologies are server products in the Microsoft Office System that build upon Microsoft Windows® SharePoint Services to add deep customization of your content and unify your SharePoint sites and services into a single corporate portal. With SharePoint Products and Technologies, you can create portal sites for partners, company divisions, or your entire company, you can target content to the appropriate audience, and you and your users can create personalized views and content delivery methods for your SharePoint sites.

SharePoint Products and Technologies also provide portal-wide areas and searches that you can use to find and organize information that spans multiple SharePoint sites.

Because SharePoint Products and Technologies are built on top of Windows SharePoint Services, all features of Windows SharePoint Services are available in SharePoint Products and Technologies. You can affiliate a SharePoint site with a SharePoint Products and Technologies portal site to enhance the SharePoint site with additional features, including links to the SharePoint Products and Technologies portal site, links to relevant SharePoint Products and Technologies areas, links to portal-wide search features, and enhancements to the Presence Control features in Windows SharePoint Services. To connect to a portal site, you must be a member of a site group with the Manage Web Site right for the Windows SharePoint Services site.

You can configure only one portal site for each end-user IIS virtual Web server. The portal site corresponds to the SharePoint Products and Technologies top-level site for both the virtual server and the site collection rooted at the virtual server.

Each SQL Server content store for SharePoint Portal Server can only contain one portal site collection. Each SQL Server content store for Windows SharePoint Services can contain as many as 50,000 site collections, even if the site collection is hosted under a SharePoint Portal Server portal site.


Architectural Overview


Web portals are a popular way to bring information from several different sources into one convenient place to enable collaboration across the organization. SharePoint Products and Technologies provide an easy way to create Web portals with integrated document management services and search capabilities. You can establish a central point of access to all your existing key business information and applications, as well as share information across file servers, databases, public folders, Internet sites, and SharePoint Team Services-based Web sites.

Microsoft designed the next generation of SharePoint Products and Technologies to use a common set of Microsoft Windows Server� 2003 services named Windows SharePoint Services. This set of services takes advantage of the performance, stability, and security features of the Microsoft .NET Framework. The following applications are based on Windows SharePoint Services:

! SharePoint Portal Server 2003. ! Team sites, document and meeting workspace sites. ! Microsoft partner-developed solutions and Microsoft customer-developed

solutions.

Windows SharePoint Services is a set of services that you use to create and maintain team sites, document and meeting workspaces. SharePoint Products and Technologies consist of Windows SharePoint Services and SharePoint Portal Server. These powerful server products enable companies to build and manage integrated, large-scale portal solutions.

Introduction


Windows SharePoint Services delivers the engine for creating SharePoint sites that enable information sharing and document collaboration, increasing individual and team productivity and synchronization with Office System applications. It is a key piece of the Information Worker Infrastructure delivered in Windows Server 2003, and provides additional team services and sites that Office and other desktop applications can leverage, while also serving as a platform for application development.

SharePoint Products and Technologies provide a secure business platform that integrates information from various systems and sources into one solution. SharePoint Portal Server allows you to create Web sites based on Windows SharePoint Services directly from the portal. SharePoint Portal Server 2003 enables organizations to create and manage team and personal sites, seamlessly integrating with previously disconnected sites. These sites provide a place on the intranet where your team can communicate, share documents, and work together on projects. Customers will be able to locate and organize applications, teams, and people, as well as integrate and provision collaboration sites from one place.

The search and indexing capabilities in SharePoint Products and Technologies enable users to quickly find relevant information (such as documents, people, and sites) through customization and personalization of content and layout in the portal. These features are also supported and available in Windows SharePoint Services.

Windows SharePoint Services

SharePoint Products and Technologies


Design Goals


The overall design goal for SharePoint Products and Technologies was to unify and integrate Windows SharePoint Services as a technology platform on which to build products such as SharePoint Portal Server.

The most obvious change and improvement in the latest version of SharePoint Products and Technologies is the creation of a single, integrated technology platform named Windows SharePoint Services. SharePoint Portal Server is a server product based on Windows SharePoint Services. SharePoint Products and Technologies provide a consistent experience for users as they work with both Windows SharePoint Services-based sites and SharePoint Portal Server-based portal sites.

! Solution developers for SharePoint Products and Technologies only need to know one user interface technology (ASP.NET Web pages and controls), one data storage technology (Microsoft SQL Server�), and one SharePoint Products and Technologies object model to create advanced sharing solutions with SharePoint Products and Technologies. Developers can use their choice of Microsoft .NET Framework development and database tools to develop, test, and tune their SharePoint Products and Technologies solutions.

! Network administrators are able to leverage their existing knowledge by using well-known tools and procedures based on Windows Server 2003 and Microsoft SQL Server to deploy and manage SharePoint Products and Technologies.

Introduction

Consistent experience


The strategy of using the Microsoft .NET Framework, Web services, Microsoft BizTalk® Server, Microsoft Visual Studio® .NET, and Windows Server 2003 to build SharePoint Products and Technologies is part of Microsoft's technology strategy for connecting people, information, applications, and devices. The first advantage of using the Microsoft .NET Framework is that it is the most scalable, flexible, and secure foundation for building, deploying, and managing enterprise Web applications, including SharePoint Products and Technologies work sharing sites and portal sites. Additionally, integrating SharePoint Products and Technologies with information from virtually any enterprise application is easy with the support for Web services included in the Microsoft .NET Framework.

The long-term strategy for storage technology at Microsoft is to take advantage of SQL Server relational database technology and XML data storage technology wherever possible, and SharePoint Products and Technologies are a showcase example. Except for the full-text search indices created by Microsoft Search technologies, all content, configuration information, and other SharePoint Products and Technologies data is stored in SQL Server databases. The backward compatible document management system is not stored on SQL Server.

Using a single, consistent, integrated data storage platform creates significant advantages for IT professionals and developers by increasing their productivity and reducing their day-to-day development, deployment, and management costs.

The secure, reliable operation of everyday computer systems is at the heart of the Trustworthy Computing initiative at Microsoft. All new Microsoft products, including SharePoint Products and Technologies, adhere to these Trustworthy Computing principles and take advantage of the security and reliability engineering that is part of Windows Server 2003 and the Microsoft .NET Framework.

All developers at Microsoft take extensive software security training and apply their knowledge by performing security audits of each Microsoft software component for which they are responsible.

The development teams for SharePoint Products and Technologies groups took advantage of the built-in security and reliability of Windows Server 2003 and the Microsoft .NET Framework when they designed, implemented and tested the new version of SharePoint Products and Technologies.

Integration with the Microsoft .NET Framework

Integrated storage strategy

Trustworthy computing: security and reliability


Lesson: Features and Terminology for SharePoint Products and Technologies


In addition to understanding the technical design of SharePoint Products and Technologies, it is also important to understand the new and changed terminology introduced in the latest version of SharePoint Products and Technologies.

The capabilities of SharePoint Products and Technologies have greatly increased in the latest product release. There are many terms and components that may be new or different over past editions of the technology. Familiarizing yourself with the new and different terms of SharePoint Products and Technologies will enable you to understand the enhanced features and new functionality of SharePoint Portal Server 2003.


! Explain the new features of SharePoint Products and Technologies. ! Define the key terms that will enable you to effectively work with

SharePoint Products and Technologies.

Introduction

Lesson objectives


Instructor-Led Practice: Features of SharePoint Products and Technologies


This topic summarizes the main features of SharePoint Products and Technologies, which deliver new or enhanced capabilities.

In this instructor-led practice, use the following values:

Variable Value Virtual Computer Cardiff

Virtual Computer - Domain controller

Glasgow

user ADVWORKS\administrator

password P@ssw0rd

You can divide site content into two types of distinct, separately manageable SharePoint sites: top-level sites and subsites.

A top-level SharePoint site is the parent site of all sites in a site collection. Top-level sites can contain multiple subsites, and subsites can also contain multiple subsites, continuing for as many levels as your users require. Top-level sites enable administrators to have full control over the site collection. Subsites inherit permissions from their top-level site, and are therefore subject to the top-level set of permissions.

You can configure only one portal site for each IIS virtual Web server. The portal site corresponds to the SharePoint Products and Technologies top-level site for the virtual server and the site collection published to the virtual server.

Introduction

SharePoint sites and site collections

Portal sites


The Portal Framework and Web Parts manage all browser functions of the portal site. Web Parts display the user interface and enable portal site customization for administrators and coordinators. In addition, the Portal Framework run-time component displays requests from Web Parts on the portal site. The Portal Framework presents content in a customizable way, to suit the needs and preferences of your group. The framework also allows addition of Web Parts from many other sources. Web Parts can plug into existing back-end systems, such as Siebel or SAP, to present customized views to the desktops, enabling employees to access internal data, external feeds, and collaboration tools from a single interface.

Members of the Administrator site group for a top-level Web site can control settings and features for the top-level Web site and any subsites. A member of the Administrator site group for a subsite can control settings and features only for that particular subsite, and the administrator of a site under that subsite can control settings and features for only that particular second-level subsite.

A workspace is a site created using the Document Workspace or Meeting Workspace site templates. Typically, a workspace serves as a place in which teams go to collaborate on specific documents. You could think of a SharePoint workspace as a drafting area.

! Site Groups and Rights - SharePoint Products and Technologies use a security model based on site groups and rights. A site group is a collection of NT Users and Groups. Security rights are assigned to each security group. You can customize the rights assigned to these site groups or add new site groups to combine different sets of rights. By default, Windows SharePoint Services includes six site groups: Administrator, Web Designer, Content Manager, Contributor, Reader, and Member.

! Cross-Site Groups, Local Groups, and Domain Groups - Cross-site groups are collections of users who can be managed as a single group across multiple SharePoint Products and Technologies site collections. Cross-site groups can be members of a site group. Domain groups and local groups can also be members of site groups; however, domain groups are preferred over local groups.

Authentication is the process of verifying the identity of user or a process. Microsoft Internet Information Services (IIS) handle authentication for SharePoint Products and Technologies. To be authenticated, you need a local user account or, if in a networked domain, a domain user account. In most cases, a domain account is a better choice than a local account.

SharePoint Products and Technologies store all security metadata, groups and rights, in SQL Server content stores. User security metadata for SharePoint Products and Technologies is not stored in IIS or anywhere else in Windows.

After IIS uses a local computer account or a domain account to authenticate a user, SharePoint Products and Technologies compare the rights assigned to the user by IIS with the access control information for the SharePoint site from the site group to determine which SharePoint site resources the user is permitted to use.

Portal Framework and Web Part components

Site administration

Workspace

Security

Authentication

Authorization


The primary content store for SharePoint Products and Technologies is SQL Server. The SQL Server content store provides a single, consistent data storage solution for document content, list content, and metadata. You can use common Windows and SQL Server management tools and development tools to easily manage, tune, back up, and enhance SQL Server content stores.

The primary interfaces for the document management features in SharePoint Products and Technologies are document libraries, which you can add to any SharePoint site. A document library consists of the virtual folder where the files are stored, the files themselves, and the user-definable descriptive information (metadata) associated with each item in the document library.

With SharePoint Products and Technologies, you can associate documents and other content in a site with one or more hierarchical areas. Areas provide an alternative way to navigate and search content in a SharePoint Portal Server portal site. SharePoint Portal Server default top-level areas include Topics, News and Sites.

SharePoint Products and Technologies use the latest version of Microsoft Search technology to index both local and external document collections and Web sites. SharePoint Products and Technologies can now index and search approximately 20 million documents and support load-balanced queries across multiple catalog servers.

! Virtual computer set-up

1. Keep the Glasgow virtual computer running for use in the next lab. 2. Shut down the Cardiff virtual computer. 3. Start up the Dublin virtual computer.

Document and content storage

Organizing documents and other content

Search configuration and usage


SharePoint Products and Technologies Terminology


This topic defines the terminology that is new or has been changed for SharePoint Products and Technologies.

Alerts notify you when information that interests you is added or updated on the portal site and associated content sources. You can define your areas of interest and identify how and when you want to be told about something new or updated that you may want to investigate. You can add an alert to track new matches to a search query, changes to content in an area, or a new site added to the Site Directory.

An area is a location where content that relates to an individual subject can be aggregated. Content can be lists, documents, links, people, sites, etc. Areas are implemented as sites.

A subarea exists beneath areas and breaks down areas into a more specific content focus.

SharePoint Products and Technologies use protocol handlers and the gatherer to crawl and provide search over data from diverse content sources.

By using discussion lists, you can conduct online discussions about a document without modifying the document. Instead of using e-mail to discuss a document or trying to capture conversations about a document, authors and reviewers can now communicate with each other through threaded discussions. Simultaneous discussions about a document can occur even if one person has the document checked out. Comments are stored as threaded conversations, grouping together comments and replies.

Alerts

Area

Subarea

Crawler

Discussions


SharePoint Products and Technologies include a document library that supports versioning, routing and approval functionality. Users can check documents in and out, as well as revert to previous document versions all from their familiar productivity applications.

This type of site facilitates collaboration between multiple Microsoft technologies (Office.NET users) by providing a central location to share and work on documents, track document status, and take advantage of Office integration with Windows SharePoint Services.

This feature allows you to use groups to control access to content. Items only appear to users that have the appropriate permissions to view them.

A site is a group of related Web pages that is hosted by an IIS server on the World Wide Web or an intranet. The pages in a Windows SharePoint Services Web site generally cover one or more topics and are interconnected through hyperlinks. All Windows SharePoint Services sites have a home page as their starting point.

This type of site helps meeting organizers plan meetings, share information with other attendees, use features to capture meeting information, and then post notes and track action items.

This type of site provides personalized and customized information for you. You can set up your personal site (called My Site) to provide quick access to links and content you need to do your work. This may include links to documents, people, or Web sites as well as personal alerts you create to track changes to content within the portal and your organization. From My Site, you can also update your public profile and share collections of links with other portal users.

You can find, centralize and categorize Web-based SharePoint sites from across the enterprise and integrate information from various systems into one solution.

A site collection is a set of Web sites on virtual servers that have the same owner and share administration settings. Each site collection contains a top-level Web site and can contain one or more subsites. There can be multiple site collections on each virtual server.

A subsite is a named subdirectory of the top-level Web site that is a complete Web site. Each subsite can have independent administration, authoring, and browsing permissions from the top-level Web sites and other subsites.

A personal view is a view of a list, SharePoint document library, or Web Part Page that is available only to a particular user. The personal view of a Web Part Page uses a combination of shared property values and personalized property values. Changes made to a personal view apply only to the list, library, or page in that view and therefore are visible to that user only.

Individuals can customize any existing team site, and their individual changes are stored as part of their user profile and will be available during subsequent visits to the site.

Document library

Document workspace site

Group based security

Site

Meeting workspace sites

My Site

Portal site

Site collection

Subsite

Personal view


A shared view is a view of a list, document library, or Web Part Page that every user with the appropriate permissions on a site can see. The shared view of a Web Part Page uses shared property values. Changes made to a shared view apply to the list, library, or page as it appears to all users.

SharePoint Portal Server 2001 provided categories in which to organize and discover content. This is enhanced in SharePoint Products and Technologies with Topics that provide intuitive navigation for finding and browsing all types of content, from documents to people to sites based on Windows SharePoint Services. A document can appear in several different topics and topics can include documents stored in SharePoint Portal Server and links to information from additional content sources. Topic security is distributed and granular.

Shared view

Topic


Lab A: Installing SharePoint Products and Technologies on a Single Server


After completing this lab, you will be able to install a portal using the Microsoft Office SharePoint Portal Server Wizard.

This lab is included at this point due to the time required for SharePoint Products and Technologies to install on the Dublin virtual computer.

Before working on this lab, you must have introductory-level knowledge of:

! Microsoft Windows. ! Networking fundamentals. ! DNS/DHCP. ! TCP/IP. ! Active Directory®.

The Adventure Works Company is deploying SharePoint Products and Technologies to develop an intelligent portal that seamlessly connects users, teams, and knowledge so that people can take advantage of relevant information across business processes to help them work more efficiently.

You are Suzan Fine, a server administrator at Adventure Works. As the server administrator responsible for the SharePoint Portal Server computer, you are responsible for installing SharePoint Products and Technologies at the Adventure Works headquarters building.

Objective

Note

Prerequisites

Scenario


You should have the following virtual computers running:

1. 2012_0-Glasgow_DomainController. 2. 2012_1-Dublin_Simple SPS Server.

Lab Setup

Estimated time to complete this lab: 45 minutes


Exercise 1 Installing SharePoint Products and Technologies

In this exercise, you will install SharePoint Products and Technologies on a single computer using a simple scenario�setup SharePoint Products and Technologies with the MSDE database engine on virtual computer Dublin. The site you are creating will be the primary site for Adventure Works.

! Change your default Web site (virtual server) on IIS

1. If you have not already done so, log the Dublin virtual computer on to the DUBLIN (this computer) as Administrator with a password of P@ssw0rd.

2. Rename the Default Web Site description to Adventure Works Group Intranet: a. Click Start, point to All Programs, point to Administrative Tools, and

then click Internet Information Services (IIS) Manager. b. In IIS Manager, DUBLIN (local computer) should already be expanded;

if it is not, click on the plus (+) sign to expand it. Expand the Web Sites folder and then click Default Web Site.

c. On the Action menu, click Properties. d. On the Web Site tab, in the Web site identification section, in the

Description box, type Adventure Works Group Intranet as the name of your Web site.

e. Click OK. The name of the new site appears in IIS Manager. f. Close Internet Information Services (IIS) Manager. g. Log off the Dublin local computer.

! Install SharePoint Products and Technologies with the database engine

1. If you have not already done so, log the Glasgow virtual computer on to the ADVWORKS domain as Administrator with a password of P@ssw0rd.

2. Log the Dublin virtual computer on to the ADVWORKS domain as Administrator with a password of P@ssw0rd.

3. Verify the Dublin virtual computer is the active window, then insert the SharePoint Portal Server CD into your CD-ROM drive.

4. Click Install Microsoft Office SharePoint Portal Server 2003 components.

5. On the Install Microsoft Office SharePoint Portal Server 2003 page, click Next.

6. Click OK if the following dialog displays: �Setup will stop the following services to install Microsoft Office SharePoint Portal Server 2003.� Setup installs Windows SharePoint Services, and then the Welcome to the Microsoft Office SharePoint Portal Server 2003 Setup Wizard page appears.

7. On the Welcome to the Microsoft Office SharePoint Portal Server 2003 Setup Wizard page, click Next.


8. On the End-User License Agreement page, select the I accept all of the terms in the license agreement check box, and then click Next.

9. On the Product Key page, type the product key in the spaces provided (if necessary), and then click Next.

10. Ensure the Install with database engine radio button is selected, and then click Next. Setup installs SharePoint Portal Server and the SQL Server Desktop Engine.

After completing the last step in this exercise, the computer will take about 20 minutes to install SharePoint Portal Server and the SQL Server Desktop Engine. This delay is due to the virtual computer configuration on the student computer and is not typical for real deployments. DO NOT use the computer until this installation is complete, and do not minimize or click away from the Dublin virtual computer, as this can significantly increase the install time and possibly corrupt the SharePoint Products and Technologies installation.

! Virtual computer set-up

• Keep the Glasgow and Dublin virtual computers running for use in the next module.

DO NOT shut down the Dublin virtual computer, as it will be necessary to complete the SharePoint Products and Technologies installation in the next module.

Warning:

Warning:


Lesson: Types of Servers


There are several server types that you will need to be familiar with to understand and best configure your SharePoint environment.


! Explain the various server types and their functions. ! Explain the back-end database server options.

Introduction

Lesson objectives


Front-End Servers


The servers required to set up the SharePoint Products and Technologies environment can be divided into two classes: front-end servers and back-end servers. Within this dichotomy are further divisions that pertain to the server�s specific purpose and function.

The following servers fall under the front-end server category.

! Web Server: Microsoft IIS is a Web server that is capable of hosting several IIS Web sites underneath it. These Web sites are referred to as Virtual Servers.

! Index and Job Server: In a server farm deployment, SharePoint Portal Server stores data in SQL Server, and stores full-text indexes in the file systems on search and index servers.

! Search Server: In a server farm deployment, the search indexes are propagated to the search servers. Search requests are balanced across search servers by SharePoint Products and Technologies.

A Web server is a program that uses the client/server model and the World Wide Web's Hypertext Transfer Protocol (HTTP) to serve the files that form Web pages for Web users (whose computers contain HTTP clients that forward their requests). Every computer on the Internet that contains a Web site must have a Web server program. In a SharePoint Products and Technologies scenario, Microsoft ISS is the Web server running on the platform of Windows Server operating system and has Windows SharePoint Services installed on it.

Introduction

Front-end servers

Web server


Microsoft Index Server is integrated with Microsoft Internet Information Server (IIS) and the Windows Server operating system to allow Web searching on corporate intranets and Internet sites. SharePoint Products and Technologies include index services.

Once installed, it automatically builds an index of your Web server that can be easily searched from any Web browser with the sample query forms. Indexing maps words to documents, and to locations within documents.

The same way that an index in a book maps an important word to a page inside the book, content indexing on a computer takes a word within a document and maps it back to that document. Where other Web Servers are limited to searching only HTML pages, Microsoft Index Server uses open standard content filters to index any file type, including Microsoft Word and Microsoft Excel documents. There is no need to change the way your business works just to share documents over an intranet.

The job server is the local host computer running Windows Server 2003 and SharePoint Portal Server 2003. One notable function of the job server is the single sign-on feature. Single sign-on is a session / user authentication process that permits a user to enter one name and password in order to access multiple applications. The single sign-on, which is requested at the initiation of the session, authenticates the user to access all the applications they have been given the rights to on the server, and eliminates future authentication prompts when the user switches applications during that particular session.

Single sign-on authenticates using an encryption key as part of the encryption process for verifying credentials. The encryption key helps to decrypt encrypted credentials stored in the single sign-on database.

Administrators need to log onto the configuration account on the computer running as the job server to enable single sign-on or manage the encryption key.

The search server is responsible for full-text and keyword search functionality. In a SharePoint Portal Server scenario, the search server is based on the Windows Server operating system, and is integrated with IIS Web server. The search server enables users to search for people, sites, documents, or other information stored in many different locations and in a variety of formats.

Index server

Job server

Search server


Back-end Servers


In SharePoint, information is stored in the form of content which is then stored in back-end servers commonly referred to as Databases. An entire SharePoint Portal Server portal site collection must be contained in one database.

Optionally, you can cluster the database servers on which the configuration database resides to enable server farm configuration maps and site collection-to-content database maps.

SharePoint Portal Server stores data in SQL Server, and stores full-text indexes in the file systems on search and index servers. The computer running SQL Server must have sufficient disk space to store 200 percent of the total size of all documents stored within the portal site. Each search server must have sufficient disk space to store 50 percent of the total size of all documents included in the portal site index. Each index server must have sufficient disk space for 25 percent of the total size of all documents included in the indexes on that server.

In a server farm deployment, SharePoint Portal Server stores data in the SQL Server, and stores full-text indexes in the file systems on search and index servers.

Introduction

SQL Server

Index and job server


Microsoft SQL Server 2000 Desktop Engine (MSDE) provides the ability to store data, personal settings and configurations on your local computer. In a single-server, stand-alone deployment scenario, MSDE is running on the same computer as SharePoint Portal Server.

! Using MSDE does not reduce or eliminate the need for client access licenses (CALs) when interacting with SQL Server 2000 Standard Edition or SQL Server 2000 Enterprise Edition in a production environment.

! MSDE cannot be used to create applications that substantially duplicate the capabilities of Microsoft Access or, in the reasonable opinion of Microsoft, compete with Microsoft Access.

MSDE cannot be used to create an integrated work or product suite whose components include a general purpose word processing, spreadsheet, or database management software product except for the exclusive use of importing data to the various formats supported by Microsoft Office.

The SQL Server or MSDE database that contains the configuration information for a Windows SharePoint Services server or server farm is referred to as the Configuration Database. The Configuration Database is used to store configuration and site mapping information for the servers in the server farm. There can be only one configuration database for each server farm.

The Web store is used only for document management-related functionality. In SharePoint Products and Technologies, document library functionality includes document storage, workflow processes, and security management.

Microsoft SQL Server 2000 Desktop Engine

Configuration database

Web Storage System


Lesson: SharePoint Products and Technologies Installation Options


SharePoint Products and Technologies support single server solutions and server farm solutions. You can install Microsoft Office SharePoint Products and Technologies on one or more servers to provide a scalable, customized solution for your organization. SharePoint Products and Technologies are flexible, offering a variety of deployment configuration options. The configuration you choose depends on a number of factors, including your hardware and your performance, expansion, and scalability needs.


! Explain when a single server installation is appropriate. ! Explain when a server farm installation is appropriate.

Introduction

Lesson objectives


Single Server Scenario


When you install SharePoint Products and Technologies, you have two single server configuration options.

! Stand-alone. ! Single server with SQL server.

The stand-alone configuration uses SQL Server Desktop Engine, which is not as robust as SQL server. If your deployment requires significant scalability or must store a large number of documents, it is recommended that you use SQL Server in your deployment.

A stand-alone configuration has the following characteristics:

! It consists of only a single computer. ! This single computer runs the:

• Web component.

• Index component.

• Search component. ! This computer operates as the job server. ! This computer does not have Microsoft SQL Server 2000 installed. ! The setup wizard installs the SQL Server Desktop Engine to store the

databases:

• The SQL Server Desktop Engine has limited throughput ability and supports databases with a maximum size of two gigabytes (GB).

! This computer can optionally run the components for backward-compatibility with Microsoft SharePoint Portal Server 2001 document libraries.

Introduction

Stand-alone


The single server with SQL server configuration has the following characteristics:

! It consists of only a single computer. ! This single computer runs the:

• Web component.

• Index component.

• Search component. ! This computer operates as the job server. ! This computer has SQL Server 2000 installed. ! SQL Server is used to store the databases. ! This computer can optionally run the components for backward-

compatibility with Microsoft SharePoint Portal Server 2001 document libraries.

• You can also install the components for backward-compatible document libraries on another server.

Single server with SQL server


Server Farm Scenario


In a server farm scenario, the terminology remains the same, and the requirement that all SharePoint sites use the same SQL Server content database and provide fault-tolerant fail-over. Optionally, you can cluster the database since the top-level site remains the same. However, you can use multiple, stateless, front-end Web servers to support a large number of user connections and to render ASP.NET Web pages. Logically located behind these front-end Web servers, the SharePoint Products and Technologies configuration can use many back-end database servers.

You can use multiple content database servers to support multiple site collections servers on which the configuration database resides to enable server farm configuration maps and site collection-to-content database maps.

You can deploy three server farm configurations:

! Small server farm. ! Medium server farm. ! Large server farm.

You must configure the servers in the small server farm as follows:

! One computer running the Web component, index component, and search component, as well as running as the job server. This computer can optionally run the components for backward-compatibility with Microsoft SharePoint Portal Server 2001 document libraries.

! One or more computers running Microsoft SQL Server 2000.

Server farm deployments

Small server farm


You must configure the servers in the medium server farm as follows:

! One or two front-end Web servers with the search component enabled. ! One index management and job server. ! One or more computers running SQL Server 2000.

Optional: One computer running the components for backward-compatibility with Microsoft SharePoint Portal Server 2001 document libraries.

You must configure the servers in the large server farm as follows:

! Two or more front-end Web servers. ! Two or more search servers. It is recommended that you have no more than

four search servers. ! One or more index management servers, one of which is the job server. It is

recommended that you have no more than four index management servers. ! One or more computers running SQL Server 2000.

Optional: One computer running the components for backward-compatibility with Microsoft SharePoint Portal Server 2001 document libraries.

! Small to medium organization ( < 10,000 users):

• Throughput generally not an issue.

• Availability, data protection, and IT standards are not issues. ! Large organization (tens of thousands):

• Throughput will require small farm (3-5 servers).

• Availability, data protection, and IT standards may play a role. ! Largest organizations (hundreds of thousands):

• Throughput will require large farm (10-20 servers), or multiple farms.

• Data protection, and IT standards may play a role. ! Business structure may require shared services for SharePoint Portal Server. ! Custom Web parts can significantly change CPU/memory requirements. ! Millions of documents stored, > 10,000,000 documents indexed (SharePoint

Portal). THIS PAGE INTENTIONALLY LEFT BLANK

Medium server farm

Large server farm

Deployment decision points

Documents

2423301.pdf