...
The siteUrl is the URL to your Episerver’s site. The guid is used as an identifier, when creating a new endpoint in Digizuite. The default value is empty so you have to generate a new one.
In guid, you input the same GUID which is found in the customHeaders field inside Media Manager → General settings → Integrations → Your Episerver integration → Custom headers. In here - the header should be formatting something like this “Authorization:e01553bd-f66a-4fba-8b6b-884133d8ae80“, where the GUID is just a random one you generate. The GUID is used to validate that the notifications come from the correct sender.
The parameter subscriptions indicates which “change type” you want to listen for. The possible values can be found here DFE 2.1.0 - 3 Setting up Episerver. The default value is 1 - that being the ID of the “AssetChanged” event.
The last parameter deleteBlob indicates whether we should delete blobs of the asset. In a load balanced environment, where you have multiple instances in which each of the instances contains its own local blob storage, this should be set to true. If the blob storage is shared between instances, leave it as false.
Once the change has been made, reload the site. You will now see the following log statement in the file Digizuite.log (Of course, this will only appear if Digizuite logging has been enabled):
| Code Block |
|---|
2020-05-14 08:22:33,529 [1] INFO DigizuiteProviderInit::Initialize: DigizuiteIntegration has been setup and configured |
2. Verify the connection
If Once you have access to the Digizuite server. Open a 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.
...