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".
...
| Type | Name | Required | Default | Description | |||||
|---|---|---|---|---|---|---|---|---|---|
| string | baseGuid | No | (a hardcoded guid) | A guid that is used as the 'foundation' to generate all the assets Content Guid. Usually you won't have to change this. | |||||
| string | name | No | "" | The name with which the integration identifies itself - for example when sending editor notifications | |||||
| bool | redirectvideostream | No | false | Default behavior is to have Episerver act as a video proxy for video assets. If this is set to true, Episerver will instead redirect the video streams to the DAM directly. | |||||
| bool | disablenotifications | No | false | If set to true, will supress editor notifications from the integration. | |||||
| bool | autoattach | No | true | Controls if the Digizuite Content Provider should automatically attach after initialization to an entry point automatically created. If this is false, you will need to manually configure the content provider. | |||||
| string | autoattachname | No | "Digizuite" | The name of the entry point automatically created in Auto Attach mode. | bool | disableresilientassets | No | false | By default image assets are stored locally for resilience when used on published content. This can however slow down the publish process. If resilience is not required you can disable it here. |
| string | validFullSearchNamespaces | No | EPiServer.Find.Cms.ContentIndexer,EPiServer.Find.Cms.IndexingJobService | Comma-separated list of valid namspaceses. Here you add the valid namespaceses that are allowed to do a full search and requesting all assets from Digizuite through our DigizuiteContentProvider. By default is is only the Find indexing that are allowed. | |||||
| bool | preventdigizuitemediatypesinepiserverfolder | No | true | Prevent that Digizuite media types can be uploaded to a Episerver media folder. |
Child element: connection
...
| Type | Name | Required | Default | Description | |||||
|---|---|---|---|---|---|---|---|---|---|
| string | baseUrl | Yes | Base url to the DAM Center | ||||||
| string | user | Yes | Sync user that the integration can use in the DAM Center | ||||||
| string | secret | Yes | The hashed secret that the integrations sync user should use. | ||||||
| string | versionId | Yes | 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. | bool | readOnly | No | false | Indicates if the integration should act as if it is in read only mode. |
Child element: cache
The cache element controls the caching - both binary on-disk caching as well as some of the in-memory asset meta-data caching.
...