Viz Social Deployment Guide
Version 1.0 | Published June 22, 2021 ©
Context and Architecture
Viz Social runs in Amazon Cloud. The frontend is available on HTTPS, open for specific IPs only (client IPs and support IPs).
DCS is installed locally (usually in a DMZ zone) to be able to serve files and interact with devices and systems that are normally firewalled. To fetch content from the internet (social images/videos), DCS must be able to download/make request outwards.
Viz Social connects to DCS and all communication is done over this channel. It requires opening some firewall ports (default 8099 and 10000) on the DCS for incoming TCP requests from Viz Social in the cloud.
Viz Trio Workflow
DCS talks to the MSE REST API for listing shows and templates, etc. and creates pages and other resources using the same API. In addition, any images/video attachments are saved to a shared folder that Viz Trio clients and the Viz Engines can read from. This is typically either a UNC path, or a mapped network drive that is the same across all machines.
Pilot Edge Workflow
DCS creates ATOM feeds to be used by Pilot Edge.
DataHub Workflow
DCS talks to the Viz DataHub REST API for creating and populating sources. In addition, any images/video attachments are saved to a shared folder that the Viz Engines (and Feed Streamer) can read from. This is typically either a UNC path, or a mapped network drive that is the same across all machines.
