Page Comparison

...

public class UpdateNotification
{
    public int ChangeType { get; set; }
    public ChangeData Data { get; set; }
}
public class ChangeData
{
    public int AssetIdItemId { get; set; }
    public int ComboValueIdBaseId { get; set; }
    public int MetafieldId {
get; set; }
    public int TreeValueId { get; set; }
    public int ItemId { get; set; }
}

The property ChangeType indicates wheter it is and AssetChanged, MetafieldChanged, ComboValueChanged or TreeValueChanged. If it is an AssetChanged we do the following:

1. Delete blobs for the notified assetid.

2. Delete database enties entries for the notified assetid.

...

_eventRegistry.Get(GlobalConstants.ContentEventRegistry.DigizuiteAssetChangeEventId).RaiseAsync(
                GlobalConstants.ContentEventRegistry.DigizuiteAssetChangeRaiserId, updateNotification, EventRaiseOption.RaiseBroadcast);

We also listning for these events the event and for AssetChanged we clear the in-memory cache and if the RaiserId is coming from another instance (broadcast) and the configuration “DeleteBlob” is true, then we delete the blobs and database entries for the notified assetid.

...

As an developer you can also build you own logic around the notifications from Digizuite, as you can listening for the event by register to the eventsevent, just as we do above.

1. Setup the endpoint

Open the web.config and locate the Digizuite node. The sub node “digizuiteIntegration” is the one we should update. Here you see an example where it has been configured.

<digizuiteIntegration siteUrl="http://my.episerverSite.dk" guid="e01553bd-f66a-4fba-8b6b-884133d8ae80" subscriptions="1" deleteBlob="false"/>

The siteUrl is the url to your episerver site. The guid is used as the unique id, when creating a new endpoint in Digizuite. The default value is empty so you have to generate a new one. The parameter subscription indicates which changetypes you want to listning for. The possible values can be found her DFE 2.0.0 - 3 Setting up Episerver. The default value is 1 which is AssetChanged. The last parameter deleteBlob indicates whether we should delete the blobs for the asset or not. In a load balanced invironment where you have multiple instances and each of the instances cantains it own local blob storage, then this should be true. If the blob storage is share between the instances then leave it false.

Once the change has been made and you reload the site, you should see the following log statment in the file Digizuite.log:

2020-05-14 08:22:33,529 [1] INFO DigizuiteProviderInit::Initialize: DigizuiteIntegration has been setup and configured

2. Verify connection

If you have access to the Digizuite server. Open an browser from that server and access your episerver site. If you cannot access the site, Digizuite won't be able to send notifications to it.

If the server can access your site, then the next test would be to change an asset in Digizuite DAM and verify that the notification has been send to Episerver.

1. Change the log level for the logger “Digizuite.Episerver.Helpers.Internal.Logger” to Debug or All.

2. Reload the site.

3. Go to Digizuite and find an asset that is published to the Episerver channel and change some of its metadata for example, the title. Now Digizuite will notify all registret integration endpoints with the update.

4. You should see the following log statment in the log file Digizuite.log. This indicates that digizuite has delivered the notification to the apicontroller in Episerver.
   

   Code Block
   2020-05-15 11:20:45,828 [20] DEBUG DigizuiteIntegrationController::Update: DigizuiteIntegration Event, Type:1 ItemId:395810 AssetId:3247

5. The next thing you can verify is that the metadata that you change is the same in Episerver.