Versions Compared

Old Version 12

changes.mady.by.user Martin Ulisse

Saved on

compared with

New Version 13

changes.mady.by.user Martin Ulisse

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If you have access to the Digizuite server. Åben 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 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.