Outbound Integration Endpoints enables Digizuite to seamlessly integrate with external systems by pushing data (assets, metadata or just a notification) to any external system based on events happening in the Digizuite DAM.using message-based communication. It pushes data to by pushing data in
Integration Endpoints are push-based as opposed to API integration which are always pull. Integration Endpoints are build on top of an integration architecture that will always handle exporting assets and their metadata but with the following variables:
- How should the metadata look? Out of the box, we deliver Excel, XML and standard JSON. Do the receiving system expect a certain format? If so then Digizuite must be involved to create the transformation component.
- How should data be pushed to the external system? Digizuite have all the assets and metadata ready but should this be pushed to FTP, to a REST endpoint, using a 3rd party API or something completely different. Digizuite can accommodate most.
- What events should trigger the data to be pushed. Metadata changes, folder changes and different events are optionable.
An overview of the architecture can be seen below:
An Integration Endpoint can be created via settings in the Media Manager 5 (there is a link from DC) or from the Sitecore administration portal.
Endpoint Configuration Options:
- Integration Endpoint Name
- Channel Folder that it should be linked to
- Define what events to subscribe
- Folder, Metadata, Profile and Delete change events
- Should metadata be exported and how should it be transformed (As stated above, if not standard excel or xml, then Digizuite would have to create the transformation).
- Delivery Mechanism for the assets + metadata. Where and how should it be delivered.
- Examples could be Youtube, Sitecore, FTP or one of your own downstream systems (Digizuite would have to add the delivery mechanism as stated above if not out of box)