After installation of the NuGet package, it's time to setup the connection to you Digizuite DAM instance. Add the DAMIntegrationConfiguration to your startup class. The configuration should be added after the AddCms due to TinyMCE initialization. Here is an example. The paramaters in the connection, will be delivered by Digizuite.
| Code Block |
|---|
|
services.AddDigizuiteDAM(dc =>
new Digizuite.Optimizely.Configuration.DAMIntegrationConfiguration()
{
dc.DatabaseName = "[ConnectionString]",;
dc.Connection = new Digizuite.Models.DigizuiteConfiguration()
{
BaseUrl = new Uri("https://[DAM url]"),
SystemUsername = "Episerver",
SystemPassword = "55f2f63f09ff4f73f75fbb7d7e6e69b0",
ConfigVersionId = "/51/"
};
}); |
| Info |
|---|
|
For testing the connector, you can use the demo environment. Be aware that this environment is controlled by Digizuite and willl be reset occasionally. Meaning content you upload will be delete. Connection = new Digizuite.Models.DigizuiteConfiguration() {
BaseUrl = new Uri("https://dam-dfo.digizuite.com"),
SystemUsername = "Episerver",
SystemPassword = "55f2f63f09ff4f73f75fbb7d7e6e69b0",
ConfigVersionId = "/1/"
} |
...
| Name | Type | Required | Default | Description |
|---|
| DatabaseName | string | Yes |
| The databaseName is the name of the database that you are running your Optimizely application in. We have experienced in some applications that it is not enougt to only add the name of the database, but it should have the hole connection string. You can get the connection string like this: _configuration.GetConnectionString("EPiServerDB") |
| Connection | DigizuiteConfiguration | Yes |
| This object contains the connection parameters to the Digizuite DAM instance. |
RoleMappings | List<RoleMappingElement> | No |
|
|
FallbackIconMappings | List<IconMappingElement> | No |
|
|
VideoPlaybackType | VideoPlaybackType | No | VideoPlaybackType.Streaming | The connector comes with 3 different option for video playback. You can read about the it at DFO 3.1.0 - 16 Video playback |
DigizuiteWebhookElement | DigizuiteWebhookElement | No |
| Listening for Digizuite asset update events. When someone make a change to an asset in Digizuite DAM and event is raised which your Optimizely instanc gets and all cached data about the asset will be cleared. |
...
| Name | Type | Required | Default | Description |
|---|
| DigizuiteRole | string | Yes |
| The name of the role in Digizuite to map. |
| EpiserverRoles | List<string> | Yes |
| A list of Episerver roles that be given similar permissions to the Digizuite Role. |
...
| Name | Type | Required | Default | Description |
|---|
| DocumentType | string | Yes |
| The icon for the document type - for instance "video" for a video icon. |
| Extensions | List<string> | Yes |
| A list of file extensions to map for the above document type. |
...
| Name | Type | Required | Default | Description |
|---|
| SiteUrl | string | Yes |
| This is the url that Digizuite use to send the notification to. We will append the routing to the controller to the url. [siteUrl]/episerver/digizuite/DigizuiteWebhook/Update |
| Guid | string | Yes |
| This is the unique identifier for the endpoint in Digizuite DAM. Just generate a new guid. |
| Subscriptions | List<int> | No | new List<int> { 1 } | A list of changeTypes. Possible values are: AssetChanged = 1, MetafieldChanged = 2, TreeValueChanged = 4, ComboValueChanged = 8 |
DeleteBlob | bool | No | False | By default this is false. Enable this if each instance of a loadbalanced enviroment has its own local blob storage. |