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.

166 Part III: Planning <strong>and</strong> Deployment<br />

Planning Source Groups<br />

As a starting point, you should define your source groups as follows:<br />

■ Use one source group for each index. Doing this allows you to broadly define<br />

search scopes for each portal site. For example, if your organization chose to<br />

hold all its indexed content in a single content index, the source group<br />

assigned to that index would allow you to easily define a search scope on all<br />

content managed by that index.<br />

■ Use one source group for each content source. Doing this allows you to more<br />

narrowly define search scopes for each portal site. For example, defining a<br />

separate content source for the corporate portal site <strong>and</strong> one for each divisional<br />

portal site would allow you to easily define a search scope on the portal<br />

site content that each source group crawls.<br />

Note SharePoint Portal Server does not allow spaces in content index<br />

names. Spaces are supported in source group names.<br />

When you select the content source as SharePoint Portal Server Site<br />

Directory, define the address of the portal site for the content source (for<br />

example, http://sales/*), <strong>and</strong> then save definitions of content source<br />

parameters, the address of the content source automatically changes—for<br />

example, it changes to sps://sales/site$$$site/scope=*.<br />

There is no way to directly crawl the virtual server of another team<br />

site. If you want to have certain site collections indexed, you have two<br />

options. The first is to add the site collection to another site directory manually.<br />

The second option—which is less optimal—is to add a separate content<br />

source for each site collection. The first option is the preferred <strong>and</strong><br />

recommended approach.<br />

Planning Deltas Between Source Groups <strong>and</strong> Content Indexes<br />

A best practice is to create a source group for each content index so that you’ll have<br />

maximum flexibility in creating the search scopes. To use the example from the preceding<br />

sections, you’d create a content source to each document group for each<br />

team (chemicals, data modeling, <strong>and</strong> quality). You would assign each content source<br />

to its own source group, such as Chemicals Source Group, Data Modeling Source<br />

Group, <strong>and</strong> Quality Source Group. Then, for the research search scope, you’d select<br />

all three source groups to offer portal site users the ability to search documents<br />

across the research department.

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

Saved successfully!

Ooh no, something went wrong!