Tài liệu Module 9: Managing SharePoint Portal Server docx

Explain the document management capabilities of the Web Storage System, including the differences between the Microsoft Exchange 2000 Server and SharePoint Portal Server implementations

Contents

Overview 1

Examining the Web Storage System 2

Managing SharePoint Portal Server 6

Monitoring SharePoint Portal Server 22

Backing Up SharePoint Portal Server 27

Restoring SharePoint Portal Server 35

Lab A: Backing Up and Restoring

Review 47

Module 9: Managing SharePoint Portal

Server

Information in this document is subject to change without notice The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended

to represent any real individual, company, product, or event, unless otherwise noted Complying with all applicable copyright laws is the responsibility of the user No part of this document may

be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation If, however, your only means of access is electronic, permission to print one copy is hereby granted

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

 2001 Microsoft Corporation All rights reserved

Microsoft, Active Directory, Active X, FrontPage, JScript, MS-DOS, NetMeeting, Outlook, PowerPoint, SharePoint, Windows, Windows NT, Visio, Visual Basic, Visual SourceSafe, Visual Studio, and Win32 are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A and/or other countries

Other product and company names mentioned herein may be the trademarks of their respective owners

Instructor Notes

This module is intended to help the server administrator perform the day-to-day administration of Microsoft® SharePoint™ Portal Server 2001

After completing this module, students will be able to:

Locate and manage files and folders in the Microsoft Web Storage System

Manage the computer running SharePoint Portal Server

Monitor SharePoint Portal Server by using System Monitor

Back up SharePoint Portal Server

Restore SharePoint Portal Server

Materials and Preparation

This section provides the materials and preparation tasks that you need to teach this module

Required Materials

To teach this module, you need the following materials:

Microsoft PowerPoint® file 2095A_09.ppt

Module 9, “Managing SharePoint Portal Server,” in Course 2095A,

Implementing Microsoft ® SharePoint ™ Portal Server 2001

Preparation Tasks

To prepare for this module, you should:

Read all of the materials for this module

Read the instructor notes and margin notes for this module

Complete the labs

Presentation:

135 Minutes

Lab:

30 Minutes

Module Strategy

Use the following strategy to present this module:

Examining the Web Storage System Explain the fundamental properties of the Web Storage System Explain how to remount the installable file system (IFS) drive (drive M) Explain how to use the Public Folders store in SharePoint Portal Server Explain the document management capabilities of the Web Storage System, including the differences between the Microsoft Exchange 2000 Server and

SharePoint Portal Server implementations of that technology

Managing SharePoint Portal Server Describe the various management functions of the administrator role in SharePoint Portal Server, including managing configuring server settings, workspace settings, resource usage, server load options, and file locations,

as well as administering services

Monitoring SharePoint Portal Server Explain and demonstrate how to monitor SharePoint Portal Server by viewing the Microsoft Windows® 2000 event log, the application log in Windows 2000 Event Viewer Explain how to use the Performance Microsoft Management Console in Windows 2000 to monitor performance

counters of the DMX Knowledge Management Server, MSExchange OLEDB Resource, and Exchange Server HTTP Extensions objects

Backing Up SharePoint Portal Server Explain that administrators can use backup and restore procedures on SharePoint Portal Server in order to recover an entire server Explain how to plan a backup operation and then perform the operation by using the

msdmback.vbs utility Describe the causes and resolution of common backup problems

Restoring SharePoint Portal Server Explain how to plan a restore operation for SharePoint Portal Server Explain how to perform a restore operation by using the msdmback.vbs utility Explain how to use a restore operation to recover from a server failure Describe the cause and resolution of common restore problems

Customization Information

This section identifies the lab setup requirements for a module and the configuration changes that occur on student computers during the labs This information is provided to assist you in duplicating or customizing Training and Certification courseware

The lab in this module is also dependent on the classroom configuration that is specified in the Customization Information section at the

end of the Classroom Setup Guide for Course 2095A, Implementing Microsoft® SharePoint ™ Portal Server 2001

Overview

Examining the Web Storage System

Managing SharePoint Portal Server

Monitoring SharePoint Portal Server

Backing Up SharePoint Portal Server

Restoring SharePoint Portal Server

*****************************I LLEGAL FOR N ON -T RAINER U SE *****************************

After completing this module, you will be able to:

Locate and manage files and folders in the Microsoft® Web Storage System

Manage the computer running Microsoft SharePoint™ Portal Server 2001

Monitor SharePoint Portal Server by using System Monitor

Back up SharePoint Portal Server

Restore SharePoint Portal Server

In this module, you will learn

how to manage, monitor,

back up, and restore a

SharePoint Portal Server

Examining the Web Storage System

Mounting the IFS Drive (Drive M)

To remount drive M

To permanently enable drive M

The Public Folders Store in SharePoint Portal Server

SharePoint Portal Server Setup installs a Public Folders store during the installation process

Document Management and the Web Storage System

Differences between Web Storage System implementations

*****************************I LLEGAL FOR N ON -T RAINER U SE *****************************

SharePoint Portal Server uses the same Web Storage System technology that is used by Microsoft Exchange 2000 Server However, SharePoint Portal Server does not mount drive M by default the way Exchange 2000 Server does The Web Storage System provides SharePoint Portal Server with an efficient and highly accessible data storage facility Understanding the underlying architecture of the Web Storage System and the methods for accessing stored components will help you to manage, maintain, and troubleshoot a SharePoint Portal Server computer

The Web Storage System combines the features and functionality of the file system, the Web, and a collaboration server in a single location The Web Storage System comes with both Exchange 2000 Server and SharePoint Portal Server You can use the Web Storage System for storing, accessing, and managing data, as well as for building and running programs

Mounting the IFS Drive (Drive M)

The installable file system (IFS) drive is not mounted by default when you install SharePoint Portal Server However, you may want to use IFS access for the following tasks:

Read-only access to the document library

Microsoft FrontPage® Server Extensions

Web Storage System development by means of IFS

Topic Objective

To present the function of

the Web Storage System in

SharePoint Portal Server

Lead-in

The Web Storage System in

SharePoint Portal Server

supports only one database

per server, a Public Folders

store

Let your students know that

if they want more

information about the

departmental Web Storage

System that ships with

SharePoint Portal Server,

they can refer to the

located under Additional

Reading on the Web page

on the Student Materials

compact disc

To remount drive M:

1 Open a Command Prompt

2 Type SUBST M: \\.\backofficestorage

Note that SharePoint Portal Server Setup still uses drive M during setup and repair This has the following issues:

• Drive M is added to the backup exclusion list for Microsoft Windows NT® backup You will not see any drives mounted as M under the Windows NT backup utility You can reset this by using the backup utility for Windows NT

• If there are no free drive letters, the repair option of Setup will not succeed Unmap another drive in order for repair to succeed

To permanently enable drive M:

• In Registry Editor, set the following registry key:

HKLM\System\CurrentControlSet\Services\EXIFS\Parameters and set the DriveLetter value to M

To temporarily enable drive M:

• In the Registry Editor, set the following registry key:

SUBST M: \\.\backofficestorage

For more information about the IFS drive, see the Readme.doc file on the SharePoint Portal Server compact disc

The Public Folders Store in SharePoint Portal Server

The top-level unit of storage in the Web Storage System is a database The database file is a Joint Engine Technology (JET) database (.mdb) that efficiently provides access to the information that is stored in it Although the Web Storage System in Exchange 2000 supports multiple databases, the Web Storage System in SharePoint Portal Server only supports one database per server, a Public Folders store

Note

Let students know that

administrators should not

use the Exchange System

Manager to manage the

SharePoint Portal Server

Web Storage System

You may also want to

mention the Eseutil and

Isinteg utilities Both will

work with the SharePoint

Portal Server Web Storage

System, but they are not

currently supported

The Eseutil utility can

perform an offline

defragmentation, which

releases unused hard disk

space from the SharePoint

Portal Server database to

the file system

For more information, direct

students to the MSDN Web

site

SharePoint Portal Server Setup installs a Public Folders store during the installation process This process is summarized as follows:

1 SharePoint Portal Server Setup creates a public virtual root in the Microsoft Internet Information Services (IIS) metabase

The metabase functions as a registry for IIS Use the Internet Services Manager, an IIS snap-in, to manage the metabase

2 The public virtual root points to the root of the Public Folders store in the Web Storage System Setup also creates a workspace and a corresponding folder in the Public Folders tree in the Workspaces folder, along with a virtual root of the workspace name that points directly to the workspace

Although you can use IFS to view the workspace structure, you should refrain from doing so You should always use Hypertext Transfer Protocol (HTTP) to display and manage the contents of your workspace by using Web folders Using IFS bypasses the HTTP protocols upon which many SharePoint Portal Server services are built; therefore, you will not be able to perform specific SharePoint Portal Server actions or set security by using roles

Document Management and the Web Storage System

The Web Storage System provides an HTTP/Distributed Authoring and Versioning (HTTP/DAV) server component that resides in the IIS process and exposes a high-performance HTTP/DAV protocol in the Web Storage System The HTTP/DAV component allows a client to perform file-system type operations on a remote server

The SharePoint Portal Server client-side OLE-DB 2.5 implementation, Microsoft OLE DB Provider for Internet Publishing (MSDAIPP), communicates with the Web Storage System by using HTTP/DAV These two components provide document management functions to Web browser clients and SharePoint Portal Server Web folder clients

Note

Differences Between Web Storage System Implementations

SharePoint Portal Server uses the Exchange 2000 departmental Web Storage System for document storage, and its schema infrastructure uses the

Exchange 2000 schema as part of its base schema SharePoint Portal Server also uses the Exchange mechanism for schema discovery

Some differences between the Exchange Server implementation and the SharePoint Portal Server implementation are:

The Exchange schema is primarily targeted at serving Exchange and messaging tasks It includes a long list of messaging and calendaring document profiles that motivate Exchange-specific functionality but are not used by SharePoint Portal Server However, the schema cache is still aware

of the entire Exchange schema

Unlike the static schema in Exchange, SharePoint Portal Server delivers much of the schema functionality to users The user extends the SharePoint Portal Server System schema to create document profiles and define properties to shape the space of document management and search

SharePoint Portal Server code therefore relies heavily on this user-extended schema

Each item in the Web Storage System has a schema pointer to the location

of its defining schema entry in the Active Directory™ directory service SharePoint Portal Server uses the same mechanism; however, the SharePoint Portal Server schema is located in a central location in the Web Storage System and is scoped to a workspace SharePoint Portal Server does not require or make use of the Active Directory All items in a workspace

share the same value for the schema pointer, schema-collection-ref, or SCR, which points to the location of the schema for a given item

SharePoint Portal Server implements its own models for versioning, workflow, and security

For more information about programmatically accessing the Web Storage System, see Appendix A, “Developing with SharePoint Portal Server,” in

Course 2095A, Implementing Microsoft® SharePoint™ Portal Server 2001, and Course 2019A, Building Solutions in Microsoft Exchange 2000 With the Web Storage System

Note

Managing SharePoint Portal Server

Configuring Server Settings

Balancing Resource Usage

Setting Load Options

Defining File Locations

Administering Services

Configuring Workspace Settings

*****************************I LLEGAL FOR N ON -T RAINER U SE *****************************

As an administrator, you are responsible for managing SharePoint Portal Server Managing the server involves configuring server settings, balancing resource usage, setting server load options, defining file locations, configuring workspace settings, and administering services

Topic Objective

To outline this topic

Lead-in

The administrator uses

SharePoint Portal Server

Administration to manage

the server

Configuring Server Settings

*****************************I LLEGAL FOR N ON -T RAINER U SE *****************************

SharePoint Portal Server Administration is used to manage the SharePoint Portal Server computer SharePoint Portal Server Administration includes some workspace-specific configuration pages, but it is intended primarily for

managing configuration settings that affect the entire server, such as defining load options and component file locations

For example, SharePoint Portal Server Administration is the only place where you can create and delete workspaces, configure access accounts used for creating indexes, relocate the Web Storage System files, and specify a Simple Mail Transfer Protocol (SMTP) server to be used by all workspaces to send subscription and approval notifications

After installing SharePoint Portal Server, open SharePoint Portal Server

Administration by clicking Start, pointing to Programs, pointing to Administrative Tools, and then clicking SharePoint Portal Server Administration

Click the name of the SharePoint Portal Server computer in the console tree,

and then use the Action menu to access the New Workspace Wizard and the Properties page of the SharePoint Portal Server computer You can also right-

click the name of the computer to access the same features

configure settings that affect

the entire server, such as

load options and file

locations

The Properties page of the SharePoint Portal Server computer contains seven

tabs that are used to display configuration data These tabs and their functions are described in the following table

Tab Use this tab to General Identify the SMTP server, set the e-mail address of the

administrator, and establish the level of resources to use for searching and creating an index

Load Create site hit frequency rules that are used when creating an index

of linked content

Proxy Server Specify proxy server settings

Accounts Configure the accounts to use when creating and updating indexes

Data Specify the location of data and log files that are created by

SharePoint Portal Server

Exchange 5.5 Enable and configure searches of Exchange 5.5 content

Other Restrict Web discussions to items that are stored in workspaces on

the server

For more information about using the Proxy Server tab and the Accounts tab, see Module 6, “Adding and Managing External Content,” in

Course 2095A, Implementing Microsoft® SharePoint™ Portal Server 2001

Use SharePoint Portal

Server Administration to

open the Properties page

of the server and display the

seven tabs that it contains

Note

Balancing Resource Usage

*****************************I LLEGAL FOR N ON -T RAINER U SE ****************************

The General tab on the Properties page of SharePoint Portal Server

Administration includes resource usage controls for the two resource-intensive processes that are commonly performed on SharePoint Portal Server computers: searching and index creation You can configure the server so that it gives each process a higher or a lower priority By default, SharePoint Portal Server configures the resource usage controls so that resources are distributed evenly You can balance resource usage to optimize performance according to the configuration of your SharePoint Portal Server computer If you plan to distribute searching and index creation across multiple servers, you must dedicate resources on one or more servers to searching and dedicate resources

on another server or servers to index creation If you are using one server to accomplish both tasks, you must balance your settings, based on your own performance requirements

For more information about multi-server implementations, see Module 10, “Examining an Enterprise-Level Implementation,” in

Course 2095A, Implementing Microsoft® SharePoint ™ Portal Server 2001

Use the resource usage controls as follows to set the priority of each process:

Background Move the slider control toward Background to configure the server to give

higher priority to other applications

Dedicated Move the slider control toward Dedicated to configure the server to apply

most of the system resources to searching or creating an index

Topic Objective

To present the resource

usage controls that are

available in SharePoint

Portal Server

Administration

Lead-in

You can use either of these

resource usage controls to

optimize the performance of

the SharePoint Portal

Server computer

You may also mention that

the e-mail address box and

the SMTP server box are

also included on this tab

These settings were

discussed in Module 2,

“Installing and Configuring

SharePoint Portal Server,”

Demonstrate how to open

SharePoint Portal Server

Administration by using both

the Action menu and a

right-click on the server

name to access the

Properties page After the

General tab is displayed,

point out the two slider

controls, one for search and

one for index

For example, if the server is primarily dedicated to indexing, move the search

resource usage closer to Background and the indexing resource usage closer to Dedicated

If you use the SharePoint Portal Server computer to run other applications, such as Exchange 2000 Server or Microsoft SQL Server™, avoid

adjusting the controls to Dedicated or near-Dedicated usage for either

searching or index creation because this setting may affect resources that are dedicated to those applications Exchange 2000 Server performance is

particularly affected if you adjust the controls to Dedicated or near-Dedicated

usage

Note

Setting Load Options

*****************************I LLEGAL FOR N ON -T RAINER U SE *****************************

Creating an index requires resources from both the SharePoint Portal Server computer that is creating the index and the servers that are storing the content

that is included in the index Use the Load tab on the Properties page of the

SharePoint Portal Server computer to specify the settings that SharePoint Portal Server will use to create indexes

Load options are used to ensure that the load on the computers being crawled is manageable Load options consist of site hit frequency rules and time-out settings

Site hit frequency rules Use these rules to specify how many documents are requested from a Web site simultaneously and what the time interval is between consecutive requests By default, the site hit frequency is limited to five simultaneous document requests Use the site hit frequency rule to modify demands on specific sites

If you require a higher document request frequency for creating or updating

an index of your own intranet, specify a lower frequency for external Web sites so that you do not overload the sites with document requests Web sites can identify you from the e-mail address you provide when creating an index If you overload a site with requests, you could be denied access to that site in the future

Time-out settings Use these settings to determine how long SharePoint Portal Server will wait for either a connection to, or a response from, a site Use these settings to minimize wasted connection time

Topic Objective

To introduce the load

options that you can

configure by using either the

Properties page of the

SharePoint Portal Server

computer or SharePoint

Portal Server

Administration

Lead-in

It is important to ensure that

the load on the computers

being crawled is

manageable To configure

the load of a computer, use

the Load tab on the

Properties page of the

server

Display the Load tab on the

Properties page of the

SharePoint Portal Server

computer by using

SharePoint Portal Server

Administration while you

discuss the settings that are

associated with indexes

If you haven't already done

so, point out that in addition

to using the Action menu to

access the server properties

page, you can right-click the

server name and then click

Properties on the shortcut

menu

Adding a Site Hit Frequency Rule

To add a site hit frequency rule, use SharePoint Portal Server Administration to complete the following steps:

1 Open the Properties page of the server

2 On the Load tab, click Add

3 In the Site name box, type the site name

You can specify rules for individual sites You can also use wildcard characters

in site names to specify rules for multiple sites, as shown in the following table

Use To

* as the site name Apply the frequency rule to all sites

*.* as the site name Apply the rule to sites with dots in the

name

*.site name.com as the site name Apply the rule to all sites in the site

name.com domain For example,

*.adventure-works.com

*.top-level domain name (such as *.com

or *.net) as the site name

Apply the rule to all sites that end with a specific top-level domain name, for example, com, net

4 Select one of the following frequency options:

• Request documents simultaneously SharePoint Portal Server uses all of the allocated system resources to request as many documents as possible with no delay between document requests This setting is usually too resource intensive for Internet sites but can be acceptable for intranet sites

• Limit the number of simultaneous document requests Use this option to specify the maximum number of documents that SharePoint Portal Server can request at one time from the site The default setting for all sites is five simultaneous document requests

• Wait a specified amount of time after each document request You can specify a delay between document requests SharePoint Portal Server requests one document per site at one time, and then waits for the amount of time specified before making additional requests

5 Click OK

You can create a frequency

rule for *.com that applies to

all Internet sites ending in

.com For example, a

coordinator at the

workspace level might add a

content source for

samples.microsoft.com The

rule for *.com would apply to

this site unless you add a

frequency rule specifically

for samples.microsoft.com

If the frequency value is too

high, SharePoint Portal

Server can overload some

Web sites with requests

Consider specifying lower

frequency rates for Internet

sites over which you may

have no control, and

increasing the frequency for

intranet sites over which you

do have control

Specifying a Connection Wait Time

Use a connection wait time to specify how long to wait for an established connection with a Web site or server by adjusting the number of connection time-out seconds By default, the wait time is 20 seconds Before you specify the wait time, consider the following:

If a wait time setting is greater than two minutes, SharePoint Portal Server will spend a significant amount of time waiting while trying to crawl nonexistent sites, bad links, and servers that are unavailable

If the wait time setting is less than 10 seconds, a lot of content may not be included in the index because SharePoint Portal Server will bypass the busier servers

If, during index creation, SharePoint Portal Server encounters 32 consecutive time-outs related to one server, SharePoint Portal Server designates the server as unavailable and does not process any requests to that server for the next 10 minutes

If you are building an index from content that is stored in Exchange public folders, the wait time must be greater than 10 seconds The recommended wait time is 60 seconds

Specifying a Request Acknowledgement Wait Time

You can specify how long to wait for a requested Web page or file by adjusting the number of seconds to wait for a request acknowledgement

If, during index creation, SharePoint Portal Server encounters 32 consecutive time-outs related to one server, SharePoint Portal Server designates the server

as unavailable and does not process any requests to that server for the next 10 minutes SharePoint Portal Server records an access error in the gatherer log

By default, the wait time is 20 seconds

If students are interested in

knowing an acceptable

range for acknowledgement

wait times, let them know

that a wait time of less than

10 seconds is considered to

be low, whereas 2 minutes

is considered high

Defining File Locations

*****************************I LLEGAL FOR N ON -T RAINER U SE *****************************

To increase performance or to simplify file management, specify the location of the data store and log files that are associated with SharePoint Portal Server All files must be stored on the same computer as the service, although they can be

on separate partitions For optimal performance, place the log files on dedicated physical volumes and store the workspace indexes on drives that are formatted for the NTFS file system

Specifying Data Store and Log Files Location

To specify the location of the data store and log files, use SharePoint Portal

Server Administration to open the Data tab on the Properties page of the

SharePoint Portal Server computer, and complete the following steps:

1 Click the file whose location you want to modify

2 In the Set location box, type the file path

You can also click Browse to select a location from the Browse for Folder

dialog box

SharePoint Portal Server verifies that the specified location has sufficient space for the file If space is insufficient, an error message appears

3 Click OK

Topic Objective

To explain how to specify

the location of the data store

and log files in SharePoint

Portal Server

Lead-in

SharePoint Portal Server

Administration is used to

specify the location of the

data store and log files

Note

Relocating Workspace Indexes

When a workspace is created, SharePoint Portal Server creates an index under the workspace root SharePoint Portal Server also creates all indexes that are propagated to the SharePoint Portal Server computer under this root To change this path, use SharePoint Portal Server Administration

If the path to the root changes, the existing indexes do not move to the new index location However, SharePoint Portal Server creates subsequent indexes, the indexes created when additional workspaces are created, in the new location If you want to move existing indexes to a new location, see

ToolsHowTo.txt in the Support\Tools folder on the SharePoint Portal Server compact disc

Relocating Temporary Files

SharePoint Portal Server may need to create temporary files for documents being crawled Use SharePoint Portal Server Administration to move the temporary files to a different drive on the same computer

By default, the temporary files for Microsoft Search Service (MSSearch) are stored in the folder that is specified by the system TMP variable, typically WINNT\TEMP on the system drive If this folder does not exist, the temporary files are stored in the folder that is specified by the system TEMP variable For MSSearch to operate correctly, ensure that there is sufficient space on this drive to store the MSSearch temporary files

Improving Performance During Searches

You can use these file-location strategies to improve performance during SharePoint Portal Server searches:

Temporary files location Set the temporary files location to a partition other than the system drive or the drive containing any SharePoint Portal Server data files, including the index files If this location changes, the existing files do not move to the new path However, SharePoint Portal Server creates subsequent files in the new location

Spindle location Ensure that the property store files, the search indexes, the system page files, and the Web Storage System files are stored on spindles (physical drives) that are separate from the MSSearch temporary folder The default for the system TMP variable points to the system drive, which is not the optimal configuration for performance

Important

Relocating Log Files

Each time that SharePoint Portal Server creates a workspace index, it creates a log file for the workspace that contains data about the creation of indexes and that records access errors To change this path, use SharePoint Portal Server Administration

If the root path for the index files changes, the existing indexes do not move to the new index location However, if you create additional workspaces, SharePoint Portal Server creates subsequent indexes in the new location If you want to move existing indexes to a new location, see ToolsHowTo.txt in the Support\Tools folder on the SharePoint Portal Server compact disc

Search Gatherer Logs

The gatherer log contains data about Uniform Resource Locators (URLs) that are accessed while an index is being created The gatherer log can record successful accesses, access errors, and accesses that are disallowed by rules in case the user needs to debug the index restrictions

To view the log, use the Active Server Pages (ASP) page that can be found in the Content Sources folder, which is located under the Management folder in the Web folders view of the workspace

The size of the gatherer log varies depending on the gatherer log settings that are specified in SharePoint Portal Server Administration If you specify that you want to log successes, you can approximate the size of the log by allowing 100 bytes per URL If you specify that you want to log items excluded by rules, the log can be as much as 10 times larger than for logging successes, especially for Web crawls

Logging exclusions generate a significantly larger log than logging successes

Property store log files are shared across all workspaces You cannot modify the location of property store log files by using SharePoint Portal Server Administration To modify the file location, see the file ToolsHowTo.txt in the Support\Tools folder on the SharePoint Portal Server compact disc For best performance, locate the property store and the property store log files on separate dedicated physical volumes

For more information about the property store, see Module 6, “Adding and

Managing External Content,” in Course 2095A, Implementing Microsoft® SharePoint ™ Portal Server 2001

Important

Point out to students that by

default the gatherer log only

records errors

Important

Note

Relocating Web Storage System Files

You can use SharePoint Portal Server Administration to specify the path to the Web Storage System files

WSS-Streaming Database

Used for streaming files, the WSS-Streaming Database file (WSS.stm) contains data and is a companion to the WSS-Database file (WSS.mdb) Together these two files form the database

SharePoint Portal Server document streams comprise a sizeable part of the total amount of data Because the file size can increase substantially over time, you can avoid problems by moving this file to a larger drive, ideally a dynamic disk that you can easily resize Use SharePoint Portal Server Administration to change the path to the database If this location changes, the existing file moves

to the new location

WSS-Database Log

The WSS-Database Log contains the log files for the Web Storage System For optimal performance, place the log files on a dedicated physical volume You can use SharePoint Portal Server Administration to change this path If this location changes, the existing files move to the new location

Administering Services

Display Name

Internet Information Services Admin Service

Internet Information Services Admin Service

Service Name

IISAdmin

Microsoft Search Service MSSearch

Microsoft Document Management

Microsoft Document Management Msdmserv

Microsoft Exchange Information Store

Microsoft Exchange Information Store MSExchangeIS

*****************************I LLEGAL FOR N ON -T RAINER U SE *****************************

SharePoint Portal Server uses the following services

Internet Information Services Admin Service IISAdmin Microsoft Search Service MSSearch Microsoft Document Management Msdmserv Microsoft Exchange Information Store MSExchangeIS

If you are experiencing difficulties with SharePoint Portal Server, you can stop one or a combination of these services that you believe to be the source of the difficulties Some services, however, have dependencies; a service may depend

on other services, or other services may depend on it When you stop a service, other services may also be stopped Before stopping or starting a service, view the dependencies

Other applications on your server might use the IISAdmin, MSSearch, and MSExchangeIS services Stopping these services could adversely affect these other applications

To view dependencies, perform the following steps:

1 Click Start, point to Programs, point to Administrative Tools, and then click Services

2 Right-click the service that you want to check, and then click Properties

3 Click the Dependencies tab

Topic Objective

To present the services that

are used by SharePoint

Portal Server

Lead-in

The services that are used

by SharePoint Portal Server

include…

Note

To stop a service on the SharePoint Portal Server computer:

1 Click Start, point to Programs, point to Administrative Tools, and then click Services

2 Right-click the service that you want to stop, and then click Stop

To start a service on the SharePoint Portal Server computer:

1 Click Start, point to Programs, point to Administrative Tools, and then click Services

2 Right-click the service that you want to start, and then click Start

Configuring Workspace Settings

*****************************I LLEGAL FOR N ON -T RAINER U SE *****************************

As an administrator, you can manage workspaces by using Workspace Settings in the Management Web folder To manage subscriptions and discussions, use the Management page of the dashboard site Both Workspace Settings and the Management page can be accessed remotely

Using Workspace Settings to Configure the Workspace

You can use Workspace Settings to access the same workspace configuration

pages that you can access by using SharePoint Portal Server Administration, and you can still manage individual content sources

The major difference is that the Web folders view is the only place where you can perform workspace management for configuring document profiles and properties, creating content sources, and configuring workspace folders, for example, setting security at the folder level, setting folder type, and establishing approval processes

Topic Objective

To present the Properties

page for the workspace, and

the tabs that are used to

configure workspace

settings

Lead-in

To configure workspace

settings, use the tabs that

are available on the

Properties page for the

workspace

To display configuration data, use one of the five tabs that are available on the

Properties page for the workspace

Tab Use this tab to General Set the workspace address, description, and contact information

Security Establish roles-based security at the top-level of the workspace

Index Limit the time allowed for a query

Logging Set the number of index log files and specify the type of events

included in the logs

Subscriptions/

Discussions

Configure subscription and discussion settings

By right-clicking on a workspace name in the console tree of SharePoint

Portal Server Administration, you can access the same workspace Properties page that is displayed by double-clicking Workspace Settings

Double-click Workspace

Settings (under the

Management folder in the

Web folders view of the

workspace) to open the

Properties page for the

workspace and display the

five tabs that it contains

Note