Post Migration Considerations for Commerce Server 2009 R2 Features

The following optional features require manual configuration after migrating to Microsoft Commerce Server 2009 R2.

  • Support for Non-Root Collections

  • Support for Cache Refresh Polling (Pull or Polling Model)

Support for Non-Root Collections

Commerce Server Settings introduces the ~home token which is used to derive the correct path of your Commerce site.

Installing Commerce Server Settings

The Commerce Server Settings feature is hidden and must be installed using Windows PowerShell.

  1. Open the SharePoint 2010 Management Shell.

  2. Enter Install-SPFeature CommerceServerSettings, and then press Enter.

  3. Enter Enable-SPFeature CommerceServerSettings -Url [url of site], and then press Enter.

Activating Commerce Server Settings

Activate the Commerce Server Settings feature to create new link under Site Administration called Commerce Server Settings.

  1. Login as a site collection administrator.

  2. Navigate to the Solution Storefront. Click Site Administration->Site Actions > Site Settings > Commerce Server Site Settings.

  3. Define the home Web URL by assigning a value to the ~home token.

  4. Modify your master page and pages to include ~home in the URL such that it resolves the correct path of resources in non root-site collections.

Cache Refresh Polling (Pull or Polling Model)

Commerce Server 2009 R2 supports two approaches to refreshing caches:

  • Push method: With this method, the servers refresh their caches when they receive a command to do so (used prior to for two-tier deployments).

  • Pull or Polling method (Recommended): With this method, each server in the deployment must check (poll) at regular intervals to determine if its cache is out of date. This method is supported for both two-tier and three-tier deployments.

When you migrate your site from Commerce Server 2009 to Commerce Server 2009 R2, the cache refresh method remains the push method. If you want to implement the cache refresh pull or polling method, you must do the following:

  1. Remove the CommerceCacheRefresh HTTP handler from the Handlers section of Web.config for both the business user/intranet facing zone (default zone) and shopper/external facing zone (internet zone).

    The CommerceCacheRefresh HTTP handler listens for cache refresh request message according to the "Push" model.

    The HTTP handler to remove is shown below:

    <add name="CommerceCacheRefresh" verb="*" path="SiteCacheRefresh.axd" type="Microsoft.Commerce.SequenceComponents.Extensions.SharePointSiteCacheRefresh, Microsoft.Commerce.SequenceComponents.Extensions, Version=9.0.0.0, Culture=neutral,PublicKeyToken=31bf3856ad364e35" />
    
  2. Enable cache refresh polling and adjust the polling interval. For more information, see Modifying the Cache Refresh Configuration.

See Also

Other Resources

Working with Cache Refresh (Pull or Polling Model)