This content is archived. See latest version here

Last updated: Oct 21 2014


This topic describes legacy features still available in the Commerce Manager back-end system. The legacy asset management in Commerce Manager has been disabled and replaced with the EPiServer asset system.

In order for the asset management to function properly, you need to configure the library storage and download, as well as the IIS. These configurations are managed in library.Storage.config and library.Download.config. You can also use the Amazon S3 service for storage. The various configuration options are described below.

Setting up IIS for virtual oaths

Method 1: IIS path rewriter

Paths to a file is created using the real extension. For example: "Library/Folder1/Folder2/File1.txt". In IIS the Path Rewriter is installed which changes requests to FileLibrary/Download.axd?path=Library/Folder1/Folder2/File1.txt or adds extra extention ".axd" to all the requests. In ASP.NET, HttpHandler is configured for FileLibrary/Download.axd. Handler intercepts requests and processes them.

Method 2: All files with extention ".axd"

Paths to the file are not original, for example: Library/Folder1/Folder2/File1.txt.axd. ASP.NET HttpHandler is configured for all .axd types which intercepts requests.

Configuring assets for Amazon storage

"Amazon S3" is a widely used internet based storage. Do the following to set up this type of storage:

  1. Obtain an account from Amazon.
  2. Enter the access key and secret access key into the library.Storage.config file located under ConsoleManager and FrontEnd IIS websites.
  3. Specify which files should be stored in the cloud using library.Folders.config file. By default it is configured to store all files under the cloud directory using the S3 Service. You can define that files of a certain size or type will be stored in the cloud.

Do you have feedback on this documentation? Send an email to For development-related questions and discussions, refer to our Forums on