|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (10)
View Page History
...
h3. Overview h3. Configuration
*Option 1. Using .xsd extension*
*Using .xsd extension*
The ECF is configured out of the box to use the .xsd http handler. To allow for Assets to display using the .xsd http handler, you will need to add a .xsd Application extension in IIS and configure it the same way as the .axd Application extension. To do this, follow these steps.
\\
{color:#000000}{*}Windows 7 (IIS 7)*{color}
{color:#000000}{*}IIS 6-7{*}{color}
# Go to your Internet Information Services (IIS) Manager.
# Right click on your web site and select "Add Virtual Directory..."
# Right click on your web site and select "Add Virtual Directory..."
...# Next, double click on the "Handler Mappings" icon under "IIS" in the main screen. Once the Handler Mappings screen opens, check if "EcfLibraryHandler" name with a path of "*.xsd" is listed. Its handler should be set to "Mediachase.Commerce.Assets.LibraryRequestHandler, Mediachase.Commerce."
!Handler Mappings.png|border=1!
!Handler Mappings.png|border=1!
#
# If not select "Add Managed Handler..." located in the "Actions" column on the upper right corner.
!AddManagedHandler.png|thumbnail,border=1!
!AddManagedHandler.png|thumbnail,border=1!
...\\
*XP (IIS 5)*
*IIS 5 (Windows XP)*
# UsersGo to your Internet Information Services (IIS) Manager.
# Right click on your web site and select "New" and then "Virtual Directory..."
# Right click on your web site and select "New" and then "Virtual Directory..."
...The asset files should now work.
To confirm this, access the Asset Management in Commerce Manager and select any of the files that you have saved in the folders.
You should either be prompted with a location to the save the file to or a new window that displays the image selected.
You should either be prompted with a location to the save the file to or a new window that displays the image selected.
...You can read more about this here - [http://technet.microsoft.com/en-us/library/cc730923(WS.10).aspx]. If you are having trouble getting the box file-based storage providers with .axd (DiskBlobStorageProvider or PublicDiskStorageProvider) to work correctly, we've listed some configuration steps you should review to ensure your assets are available the Asset Management subsystem in your front-end or back-end site.
*Option 2. Using .axd extention*
1. Open the web.config file located at the root folder of your front-end or back-end site. Insert the following 2 lines at the end of the **<httpHandlers>*\* section.
{code:XML}
<add path="WebResource.axd" verb="GET" type="System.Web.Handlers.AssemblyResourceLoader" validate="true" />
<add verb="*" path="*.axd" type="Mediachase.Ibn.Library.LibraryRequestHandler, Mediachase.AssetLibrary"/>{code}
2. Add an .axd Value in the appSettings.config
Go to your front-end folder and open a file called appSettings.config -- on the second line of this file, you should see:
{code:XML}
<add key="LibraryHandlerExtension" value=".xsd"/>{code}
Replace the ".xsd" to ".axd" and save the change.
3. Verify the Virtual Path in library.Download.config
Open the library.Download.config file. Check the attribute **virtualPath*\* and make sure it has the value "/FileLibrary"
Example:
{code:XML}
<add name="iis" type="Mediachase.Ibn.Blob.BlobProfileDownload.IISAccesProfile, Mediachase.Ibn.Blob" virtualPath="/FileLibrary"/>{code}
4. Point your BlobStorage Folders in the library.Storage.config
Open library.Storage.config file to check the basePath attribute values for your DiskBlobStorageProvider and PublicDiskBlobStorageProvider providers. They should map correctly to the physical location of your \BlobStorage and \Blobstorage\Public folders, respectively.
Example:
{code:XML}
<?xml version="1.0"?>
<storageProvider defaultProvider="DiskBlobStorageProvider">
<providers>
<add name="DiskBlobStorageProvider" type="Mediachase.Ibn.Blob.DiskBlobStorageProvider, Mediachase.Ibn.Blob" allowSearch="False" basePath="c:\Clients\Mediachase.Library\BlobStorage"/>
<add name="PublicDiskBlobStorageProvider" type="Mediachase.Ibn.Blob.PublicDiskStorageProvider, Mediachase.Ibn.Blob" allowSearch="False" basePath="c:\Clients\Mediachase.Library\BlobStorage\Public"/>
</providers>
</storageProvider>
{code}
5. Create a Virtual Directory for your BlobStorage in Front-end and Back-end
Go to your IIS Manager snap-in. Under both your admin (Commerce Manager site) and B2CSample site, create a new virtual directory named "FileLibrary" (the virtualPath attribute value in library.Download.config) pointed at the same physical directory referenced in the basePath attribute in library.Storage.config for the chosen Storage Provider (e.g., <yourpath>\Blobstorage\public for defaultProvider="DiskBlobStorageProvider").
Open up the Command Prompt and reset IIS (e.g., enter iisreset and hit enter). Wait until IIS restarts, then access your Commerce Manager from a fresh browser session.
h3. ECF Controls
ECF Includes two controls that can be used for displaying assets :
\\
h3. Without ECF Controls\\