Export (0) Print
Expand All

Web content management default settings (Office SharePoint Server)

Office 2007

Applies To: Office SharePoint Server 2007

In this article:

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.

NoteNote:

Disk-based caching is referred to as BLOB (binary large object) caching within the Web.config file.

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

Parameter name Parameter description Default setting

Location

Directory specified for the cache element.

%Installdrive%\blobCache

Path

To add new file types to the BLOB cache.

\.(gif|jpg|png|css|js)

maxSize

To change the size of the cache.

10 gigabytes (GB)

enabled

For enabling the disk-based cache.

false

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.

Property name Property description Field Field description Default setting

Output Cache

Output cache stores rendered output of all controls on a given page, and then stores several different variations of this pre-rendered page.

Enable output cache

Select to enable the output cache.

Clear

Default Page Output Cache Profile

A cache profile specifies how long items can be held in the cache. It also describes how the caching system determines whether a cached page element is valid for other requests for the same element from different users.

Anonymous Cache Profile

Select this option to provide this property to anonymous users. You can select the Disabled, Extranet, Public Internet, or Intranet cache profile.

Disabled profile

Authenticated Cache Profile

Select this option to provide this property to authenticated users. You can select the Disabled, Extranet, or Intranet cache profile.

Disabled profile

Page Output Cache Policy

Allows administrators and page layout designers to choose a different page output cache profile from the profile specified in the default Page Output Cache Profile.

Publishing sites can use a different page output cache profile

Select this option to use a different page output cache profile for Publishing sites.

Clear

Page layouts can use a different page output cache profile

Select this option to use a different page output cache profile for Page layouts.

Clear

Debug Cache Information

Displays additional cache information about pages in the site collection. This includes the date and time that the page contents were last rendered.

Enable debug cache information on pages

Select to enable debug cache information on pages.

Clear

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.

Property name Property description Field Field description Default setting

Page Output Cache Policy

Specify a cache profile for caching page output for anonymous users, and a cache profile for caching page output for authenticated users.

Anonymous Cache Profile

Select the inherit option to inherit the settings applied at the site collection level, or select a pageoutput cache profile option.

Inherit is selected by default

Authenticated Cache Profile

Select the inherit option to inherit the settings applied at the site collection level, or select a page output cache profile option.

Inherit is selected by default

Apply these settings to all subsites

Select this option to apply the cache profile settings to all the subsites.

Clear

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.

Property name Property description Field Field description Default setting

Object cache size

The object cache is used internally to optimize page rendering by storing properties of sites, page layouts, and pages.

Max. Cache Size (MB)

Set the maximum size for the object cache, in megabytes (MB).

100 MB

Object Cache Reset

Specify settings for flushing the entries in the object cache.

Object Cache Flush

Set this option to flush all entries in the object cache.

Clear

Force all servers in the farm to flush their object cache

Set this option to flush the object cache of all the servers in the farm.

Clear

Disk Based Cache Reset

Specify settings for flushing entries in the disk cache.

Force this server to reset its disk-based cache

Set this option to flush all entries in the disk cache. Otherwise, the expiration of items is managed with items being removed as they are changed in the site or when the disk size is exceeded.

Clear

Cross List Query Cache Changes

Checking the server each time a cross-list query runs produces the most accurate results at the possible cost of slower performance across the site. Cross-list queries initiated by the Content Query Web Part, or other custom implementations, can use up server resources. Specifying the time to cache the results of a cross-list query can positively impact cross-list query performance, but may display results that do not reflect the most recent changes to the items returned by the query.

Check the server for changes every time a cross-list query runs

Select to check server for changes.

Selected

Use the cached result of a cross list query for this many seconds

Select this option when changes are not frequent on the server and you want to use the cache result of the cross-list query.

60

Cross List Query Results Multiplier

Retrieves data from the server for a cross-list query. Specify a large number to retrieve more data from the server; this is ideal for site collections that have unique security applied on many lists and sites. Specify a small number to consume less memory per cross-list query; this is ideally suited for site collections that do not have unique security on each list or site.

Cross-list query multiplier

Set the value of the multiplier.

3

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.

Property Description Default setting

Title

Title for the cache profile.

Display Name

Display name is used to populate the list of available cache profiles for site owners and page-layout owners.

Display Description

Display description is used to populate the list of available cache profiles for site owners and page-layout owners.

Perform ACL Check

Selecting this option ensures that all items in the cache are appropriately security-trimmed. If you do not select this option, performance is better, but you should limit the Not selected option to sites or page layouts that do not have information that needs security-trimming.

Not selected

Enabled

Selecting this option turns caching on. If you do not select this option, caching will not take place anywhere this profile is selected.

Not selected

Duration

The duration, in seconds, to keep the cached version available.

Check for Changes

When this option is selected, each page request is validated for site changes; when changes are detected, the cache is flushed. If you do not select this option, performance is better, but there will be no check for updates to the site for the number of seconds specified in Duration.

Not selected

Vary by Custom Parameter

As specified by HttpCachePolicy.SetVaryByCustom in ASP.Net 2.0.

Vary by HTTP Header

As specified by HttpCachePolicy.VaryByHeaders in ASP.Net 2.0.

Vary by Query String Parameters

As specified by HttpCachePolicy.VaryByParams in ASP.Net 2.0.

Vary by User Rights

Selecting this option ensures that users must have identical permissions on all securable objects to see the same cached page as any other user.

Not selected

Cacheability

As specified by HttpCacheability in ASP.Net 2.0.

There are six types of cacheability:

  • NoCache

  • Private

  • Server

  • ServerAndNoCache

  • Public

  • ServerAndPrivate

Safe for Authenticated Use

Select this option for only those policies that you want to allow to be applied to authenticated scenarios by administrators and page layout designers.

Not selected

Allow writers to view cached content

Select this option only for scenarios that apply to a page that you know will be published and that do not have any content that might be checked out or in draft format.

Not selected

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.

Property name Property description Field Field description Default setting

Variation Home

Specify the site address from which you want variation. Variation of the specified site includes its subsite also.

Location

Specify the address of the site that is the starting location for creating the variations of this site.

NoteNote:

For a site collection, precede the address with ‘/.

Automatic Creation

Automatically create variations when the site is created or a new page is published.

Automatically create site and page variations

This option is used when you want automatic creation.

Selected

Do not automatically create site and page variations

This option is used when you don’t want automatic creation.

Recreate Deleted Target Page

A new target page should be re-created when the source page is republished if the previous target page has been deleted.

Re-create a new target page when the source page is republished

This option is used to re-create a deleted target page.

Selected

Do not recreate a new target page when the source page is republished

This option is used when you don’t want to re-create a deleted target page.

Update Target Page Web Parts

Web Part changes from the source page should be updated to existing target pages. Note that personalization will be lost during the update.

Update Web Part changes to target pages when variation source page update is propagated

This is used when you want to enable the update to the target page Web Part.

Selected

Do not update Web Part changes to target pages when variation source page update is propagated

Select this option when you do not want to enable the update to the target page Web Part.

Notification

Sends an e-mail to the contact person for the welcome page of the target site when a new subsite or page is created, or the contact person for a target page when this page is updated with revisions from the source variation.

Send e-mail notification to owners when a new site or page is created or a page is updated by the variation system

Select this option when you want to send an e-mail notification.

Selected

Resources

Describes whether a new page variation uses the same resource as the original page or uses a copy of these resources created in the location of the new page.

Reference existing resources

Select this option when you want to use the resources of the original page for new page variations.

Selected

Copy resources

Select this option when you want to copy the resources of original page to the location of the new page.

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.

Property name Property description Field Field description Default setting

Label and Description

Specify the name and description for the new variation label.

Label Name

Name of the new variation label.

Description

Description of the new variation label.

Display Name

Set display name for the label. Most display names are localized versions or user-friendly versions of the label.

Display Name

Select this option to show the name to the user.

Locale

Select a locale value, such as Arabic, Chinese, or English.

Locale

Select locale for the variation.

Hierarchy Creation

This label's structure will be built based on the source hierarchy during Hierarchy Creation.

Publishing Sites and All Pages.

This option is used for publishing sites and all pages.

Selected

Publishing Sites Only

This option is applicable only for publishing sites.

Root Site Only

This option is applicable only for the root site.

Source Variation

Set the variation label for source variation. If you select this option, then you must select the Publishing site template you want to use.

Set this variation as the source variation

Not selected

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.

Converters Default status

From InfoPath Form to Web Page

Selected

From Word Document to Web Page

Selected

From Word Document with Macros to Web Page

Selected

From XML to Web Page

Selected

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft