Web content management default settings (Office SharePoint Server)

Applies To: Office SharePoint Server 2007

This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.

In this article:

• Manage cache setting

• Manage page output cache settings at site level

• Manage variation settings

• Document conversion

The Web content management capabilities in Microsoft Office SharePoint Server 2007 can help you communicate more effectively with employees, partners, and customers. By providing easy-to-use functionality to create, approve, and publish Web content, Office SharePoint Server 2007 enables you to get information out quickly to intranet, extranet, and Internet sites, with a consistent look.

You can use Web content management capabilities to create, publish, manage, and control a large, dynamic collection of content. Web content management, as part of Enterprise Content Management (ECM) in Office SharePoint Server 2007, can help streamline the process for creating and publishing Web sites.

You can also use the Web content management features in Office SharePoint Server 2007 to:

• Manage variations of content for different devices.

• Publish content to intranet, extranet, and Internet sites.

• Author Web content in a WYSIWYG (what you see is what you get) environment.

• Manage site content, structure, and deployment.

• Use document converters to convert Microsoft Office InfoPath 2007, Microsoft Office Word 2007, and XML files.

• Establish an approval process to ensure that content is reviewed before it is published.

Manage cache setting

You can manage the following cache settings in Web content management:

• Settings for Page Output Cache Policy property for site collection

• Settings for Page Output Cache Policy property at site level

• Settings for Site Collection Object Cache

• Settings for creating cache profiles

Manage disk-based cache settings for a Web application

Disk-based caching is one way in which you can achieve faster processing of content stored in a Web application database. If your Web application contains large files such as images and multimedia files, enabling disk-based caching improves page delivery time, because the cache stores files on the front-end Web server, thus reducing database traffic.

You can enable disk-based caching in the Web.config file in the Web application to which you want to apply it. For this you need to configure settings in the BlobCache section of Web.config.

The following table lists the default settings for disk-based cache settings for a Web application.

Manage page output cache settings for site collection

The front-end Web server uses the page output cache to store rendered output of all controls for a given page, and then store different variations of this pre-rendered page. After a page is rendered for a user in a given user class, each time the user views that page again, the page loads faster, because the controls on the ASPX page do not need to run again to generate the HTML. Thus, the time required to render the page is reduced. The page output cache can improve server performance, because it reduces server control activities and calls to the database.

The following table lists the default settings for the Page Output Cache Policy property for a site collection.

Manage page output cache settings at site level

The following table lists the default settings for Publishing Sites Output Cache Settings for the Page Output Cache Policy property at the site level.

Manage the object cache

The object cache is used internally to optimize page rendering by storing properties of sites, page layouts, and pages. The object cache reduces the amount of traffic between the Web server and a SQL Server database. This results in higher throughput of rendered pages, thereby increasing the number of pages that can be delivered to clients.

The following table lists the default setting for Site Collection Object Cache Settings.

Manage cache profiles

Cache profiles contain specific cache settings for each type of page output cache. A cache profile determines the following types of cache behavior:

• Length of time that items should be held within the cache

• Security-trimming policy

• Expiration of settings, such as duration and changes

• Partition of a cache based on user permission, user rights, and other custom variables

There are four default cache profiles:

• Disabled

• Public Internet

• Extranet

• Intranet

You can centrally define a cache profile for a site collection; thus, when you update a profile at one place, the change is implemented across the site collection.

The following table lists the settings for creating a new cache profile.

Manage variation settings

In Web content management there are different settings for variation.

Variations

Maintaining a number of different versions or variations of publishing sites or pages is difficult and time-consuming, because it can be difficult to coordinate the creation and updating of content between the variations. To simplify this process, site owners can define a series of site variations and mark one as the primary, or source, and another as the variation.

The following table lists the different settings for variations.

Variation label

Publishing sites can be tailored for different cultures, markets, and languages. Variation settings enable site owners to create and maintain a number of different versions, or variations of publishing sites or pages. Variation labels are the names given to each of the variants. For example, variant labels could be language names — such as English, French, or German — or devices, such as personal digital assistant (PDA).

The following table lists the settings for creating a new label.

Document conversion

Site administrators can enable document conversion so that end users can convert documents from one file format to another. Document conversion for site content types allows site administrators to configure content types to store settings that define which converters are available and how those converters work on documents of that content type. A number of document converters are included with Office SharePoint Server 2007, and your organization might have additional, custom converters as well. After document conversion is enabled in Central Administration, the converters are available by default for all site content types that can be used in a document library. This includes the following content types:

• Document content types, such as Basic Page, Document, Form, and Picture

• Page layout content types, such as Article page, Redirect page, and Welcome page

• Publishing content types, such as Page, Page Layout, Publishing Master Page

A document converter is a custom executable file that takes a document of one file type, and generates a copy of that file in another file type. For example, a document converter might take a Microsoft Office Excel file and use it to generate a Microsoft Office PowerPoint file. Using document converters, you can transform your content into different versions to suit your business needs. Perhaps you want to convert draft documentation into a different, final format for long-term archiving; or perhaps you need to convert your internal documentation to a different format for placement on a customer-facing site.

The following table lists the converters available all site content types that can be used in a document library.