Viz Multichannel

Version 4.0 | Published January 23, 2019 ©

Direct Integration Architecture Overview

Direct Integration (DI) can be used with automation systems that provides a API to read/receive schedules, events and so forth. The backend that receives data from the automation system is the Integrations Hub component or service, part of Multichannel. The Integrations Hub component is a REST webservice.

The DI will receive data (“talk to”) a specific automation system using a custom Integration Module. The integration module will handle all details about interfacing a specific automation system and forward the required data (schedules etc.) to the Integrations Hub in a standardized form using the REST interface. The specific integration module could be provided by Vizrt, but it is also possible for vendors and 3. parties to develop integration modules. As the Integrations Hub has an open and easily accessible REST interface, integration modules can be written in a wide range of programming and scripting languages.

images/download/attachments/28396537/integrationservices_directintegration_overview.png
The Integrations Hub service is responsible for receiving requests for additions/deletions/updates of elements in playlists and to carry out these adjustments in the Multichannel playlist (VDOM). It is also responsible for running the Rules Engine for adding pages to groups as defined by rules. The Integrations Hub server will also handle refresh of content using the Multichannel component Promo Server. The Integrations Hub server communicates with the Media Sequencer via the Peptalk protocol.

See Also