Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

After installation of the NuGet package, a new "digizuite" element has been added to your web.config's "configuration" element. It has been added as the last child element of "configuration".
The digizuite element has some attributes and some child elements. Each of these are described below.

digizuite:


The root element of the DFE configuration.
Its attributes are

baseGuid

entryPoint

autowarmup

redirectvideostream

cache:

folderName

tempFolderName

mediaManager:

url

The mediaManager element only has one attribute: "url".
This URL should point to a Digizuite Media Manager or simply be left with no value.
If a Media Manager URL is specified, DFE can provide links to assets in said Media Manager. This may be desirable, as there are some features in MM, which DFE deosn't support, or aren't as mature. This may be editing more complex meta data types like Tree or Master/Slave item references.
If the "url" attribute is left blank, then no such link will appear.

connection:

This element tells DFE how to communicate with your DAM Center.

baseUrl

The base URL of your DAM Center, e.g. "https://dam-dfe.digizuite.com".

user

The DAM Center user, which is responsible for creating, retrieving, updating, and deleting DAM Center assets and related data in DFE.

secret

An MD5 hash of the user's password.

versionId

A DAM Center can have many different products: Media Manager, DAM for Sitecore, Adobe Connector, Office Connector, etc. Each of these can have many versions. These versions facilitate having different configuration, searches, and other things, which can change the experience for the end user. These various versions are defined by their versionId. If the original version has versionId "/1/", then its first child will have "/1/0/". The versionId is an SQL data type called hierarchy ID. It is a tree structure.
A use case may be that you want to experiment with some configuration, so you create a new version of DFE in the DAM Center.
Then you can alter the versionId attribute on your EPi Server site to "/1/0/", and do your tests, while your public DFE integration still use the "/1/" versionId.

roleMappings:

Each of the child "add" elements have 2 attributes:

DigizuiteRole

A comma separated list of DAM Center user groups to map to EPi Server roles.

EpiserverRoles

A comma separated list of the EPi Server roles, which should be applied to the Digizuite user groups.

fallbackIconMappings

Each of the child "add" elements have 2 attributes:

documentType

extensions

Example configurations:




  • No labels