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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

472 Part VI: Administration of <strong>Microsoft</strong> Office SharePoint Portal Server 2003<br />

this feature will work only if the usage analysis processing is turned on at the portal<br />

site level.<br />

Security Settings<br />

This area of the SharePoint Portal Central Administration page, depicted previously<br />

in Figure 17-8, is used to configure the list of available rights for any sites hosted by<br />

a particular server, as well as how to h<strong>and</strong>le Web Part Pages. Details follow for each<br />

of the two links.<br />

Manage User Rights for the Virtual Server<br />

This link is also referred to as the Virtual Rights Mask. It is used if you want to make<br />

sure that certain rights are not available to anyone using any of the site collections<br />

hosted by the virtual server, regardless of site group membership. You can disable<br />

those rights by deselecting the rights you want to block.<br />

A situation in which you’d use this setting is when you want to ensure that<br />

users cannot change the themes to their sites. You can disable the Apply Themes<br />

right at the virtual server level so that users must use the default theme of the site<br />

template when any site or workspace is created.<br />

Manage Security Settings for Web Part Pages<br />

Web Parts are the main programming mechanism through which the portal site Web<br />

pages provide their functionality. A Web Part has server-side code, client-side code,<br />

or both that eventually translates to user-viewable rendered HTML. The code behind<br />

these Web Parts can pass parameter values <strong>and</strong> other data to other Web Parts that<br />

have been written by the programmer to receive that data. Web Parts that have been<br />

written with this kind of functionality are called “Connected” Web Parts because<br />

they use the Web Part Connections programming feature.<br />

Connected Web Parts pass data to each other, <strong>and</strong> therefore might expose that<br />

data <strong>and</strong> violate existing security policy constraints. Also, these kinds of Web Parts<br />

tend to have more code running either at the client or server to support the connections.<br />

As an administrator, you can turn off Web Part Connection support at the<br />

virtual server level to improve security or to improve the performance of the server.<br />

The other configuration you might want to set on this page pertains to whether<br />

or not you want to have your user community see Web Parts that have been<br />

published on the <strong>Microsoft</strong> website. The feature is turned on by default, but if it’s<br />

disabled, it will cause the site pages to show only the default Web Parts created at<br />

install time as well as those posted by the administrator.<br />

Virtual Server Management<br />

Because <strong>Microsoft</strong> SharePoint Portal 2003 is based on Windows SharePoint Services,<br />

which in turn h<strong>and</strong>les all Web requests through an ISAPI filter in IIS, it follows that<br />

some virtual server configuration tasks are required. The settings for these tasks are

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

Saved successfully!

Ooh no, something went wrong!