16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 8: Planning Your Information Structure 165<br />

site or sites. If you’re planning to have multiple portal sites, you should also plan to<br />

propagate your scopes across all your portal sites unless you have a specific reason<br />

for not doing this.<br />

Note If you want to see changes to a search-scope definition immediately,<br />

you must reset Internet Information Services (IIS) by using the IISRESET<br />

comm<strong>and</strong>. This should be done only during the setup process <strong>and</strong> not when<br />

the system is live in production.<br />

Planning Content Sources<br />

When operating a corporate portal site with multiple divisional portal sites, you<br />

should, at a minimum, configure content sources as follows:<br />

■ One content source for the corporate portal site.<br />

■ One content source for each divisional portal site.<br />

■ One content source for the people in your organization. This content source is<br />

set up by default. It returns matches based on entries in the profile database as<br />

well as content from a user’s personal site.<br />

■ One content source for each divisional Windows SharePoint Services virtual<br />

server in your organization.<br />

You’ll also need to remember the old adage “garbage in, garbage out.” The<br />

tighter <strong>and</strong> more defined your content sources are, the leaner <strong>and</strong> more meaningful<br />

the data in the result set will be. For example, if you need to crawl five documents<br />

on a given website that hosts 200 documents, it would not be a best practice to<br />

crawl the entire website. Your index would end up with 195 unneeded documents.<br />

In a situation like this, you might consider creating one content source to crawl all<br />

five documents or even five content sources, one for each document, depending on<br />

their location in the directory structure <strong>and</strong> if they are shared via the same share or<br />

different shares.<br />

The point here is to remember that what you crawl gets placed in your index<br />

<strong>and</strong> you should crawl only information that is required to be in your index. This gets<br />

back to our earlier discussion about where your information is <strong>and</strong> what it consists<br />

of. Knowing this will help you build a tight list of content sources that will, in turn,<br />

give you a tight index that will return highly meaningful results to your users when<br />

they issue a query in the Search Web Part. Good planning is paramount to a successful<br />

deployment.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!