Page Comparison

3.1 Changes to web.config

Open your Sitecore's web.config file. Before you start making changes, it is advised that you make a copy of the web.config file, so you always will have the ability to fully recover.

3.1.1 Add handler

DFS has its own handler for serving media files. To enable the handler:

• Navigate to the section "/configuration/system.webServer/handlers".

• Now add the following handler, inside the handlers section.
  

  Code Block
  language xml linenumbers true
  <add name="MediaHandler" verb="GET" path="dfsmedia/*/*-*" type="DFS.Services.Handlers.MediaHandler"/>

  
  

3.1.2 Assembly bindings

• Navigate to the section "/runtime/assemblyBinding".

• Add this dependentAssembly:
  

  Code Block
  language xml
  <dependentAssembly> <assemblyIdentity name="Microsoft.Extensions.Http" publicKeyToken="adb9793829ddae60"/> <bindingRedirect oldVersion="0.0.0.0-3.1.14.0" newVersion="3.1.14.0"/> </dependentAssembly>

  
  

• Change the version of the following assembly:
  

  Code Block
  language xml
  <dependentAssembly> <assemblyIdentity name="Microsoft.Bcl.AsyncInterfaces" publicKeyToken="cc7b13ffcd2ddd51"/> <bindingRedirect oldVersion="0.0.0.0-1.0.0.0" newVersion="1.0.0.0"/> </dependentAssembly>

  to

  Code Block
  language xml
  <dependentAssembly> <assemblyIdentity name="Microsoft.Bcl.AsyncInterfaces" publicKeyToken="cc7b13ffcd2ddd51"/> <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0"/> </dependentAssembly>

  
  

• Change the version of the following assembly:

  Code Block
  language xml
  <dependentAssembly> <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a"/> <bindingRedirect oldVersion="0.0.0.0-4.0.6.0" newVersion="4.0.6.0"/> </dependentAssembly>

  to

  Code Block
  language xml
  <dependentAssembly> <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a"/> <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0"/> </dependentAssembly>

  
  

3.2 Setting up the connection to Digizuite™

DFS synchronizes data from Digizuite™ DAM Center (DC) into Sitecore. Data is stored in a silo (item bucket). Before we can begin synchronizing, we have to fill out some config parameters telling Sitecore which DAM to fetch data from. There are 3 parameters in this file \App_Config\Include\damforsitecore\DFS.Settings.config. 

<setting name="DFS.AssetSiloSettings.Default.BaseAddress" value="{URL TO THE DAM SERVER}" />
<setting name="DFS.Digizuite.MediaManagerUrl" value="{URL TO MEDIA MANAGER}" />
<setting name="DFS.Digizuite.ChannelFolderId" value="{ID OF THE CHANNEL FOLDER}" />

We do not recommend that you change these parameters in this file. Instead create a new config file where you patch the parameters (This is best practice). Here is an example of the patch config file. It is important that the file is loaded after DFS.Settings.config, otherwise the patch file won't have any effect. If you name the config file z.DFS.Settings.config and place it in the folder \App_Config\Include\damforsitecore\ you should be safe.

<?xml version="1.0" encoding="utf-8"?>
<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/">
	<sitecore>
		<settings> 
			<setting name="DFS.AssetSiloSettings.Default.BaseAddress">
				<patch:attribute name="value">https://dam.digizuiteexample.dk/<com</patch:attribute>
			</setting>
			<setting name="DFS.Digizuite.MediaManagerUrl">
        		<patch:attribute name="value">https://mm.digizuiteexample.dk<com</patch:attribute>
      		</setting>
      		<setting name="DFS.Digizuite.ChannelFolderId">
        		<patch:attribute name="value">134</patch:attribute>
      		</setting>
		</settings>
	</sitecore>
</configuration>

• Edit the values in the file to match your site (use the below table):

Once the config file is in place, reload the site.