Specifications
2-16
Cisco TV CDS 2.5 ISA Software Configuration Guide
OL-24788-01
Chapter 2 Network Design
Vault Virtualization
The DNS server typically runs on the BMS server. The Naming Service is part of the video backoffice
(VBO). All CORBA components, including the AMS, Stream Service, and Content Store, need to
register with the Naming Service. The catcher receives or “catches” new content assets from an external
communication device such as a satellite transmission or FTP server. After the package is received
completely by the catcher, it sends the package by way of FTP to the AMS. The package consists of video
and image content assets, as well as ADI metadata.
Following are the requirements for the SCS feature:
• Single, shared DNS server with all devices registering their hostnames to it. A central, shared DNS
is required to resolve multiple Naming Services belonging to the different VHOs.
• Hostnames must be unique for all devices. This is required for the Naming Service discovery.
• Each VHO has its own Naming Service to which the ISA components of the VHO register.
• AMS controls the ingest and deletion of content.
• The Vault array has one SCS.
• SCS registers with each Naming Service.
A VVI with SCS must be initialized in the following order:
1. The shared DNS server must be up and running before starting up the shared AMS, SCS, and VHO
devices.
2. SCS successfully registers with the Naming Service for each VBO.
3. Each VHO Stream Service registers with its respective Naming Service.
Ingesting Content with the Shared Content Store
Upon receiving the content package, the AMS schedules it for ingest by informing the Package Factory
in each participating VBO of the content package, and passing the pertinent information (the ADI
metadata, the URL where the content package can be accessed in the AMS, and the verb ingest).
The SCS creates one interoperable object reference (IOR) for each content package. The IOR is returned
to all VBO Package Factories that request it, including any that requested it at the time the IOR was being
created.
Deleting Content with the Shared Content Store
To delete content that was ingested for more than one VBO, the AMS is used to send the export package
delete request to each VBO. The content is deleted from the Vault array only when all VBOs have
requested the deletion. If one or more VBOs have not requested that the content be deleted, the content
remains in the Vault array.
Virtual Content Store
The Virtual Content Store feature in an ISA environment replaces the Shared Content Store feature
introduced in Release 2.1. The Shared Content Store (SCS) feature is the ability of several local sites
(video hub offices [VHOs]) to ingest content at a central location and share that content with the other
VHOs. The SCS feature eliminated ingesting multiple copies of the same content.
Release 2.2 and later releases offered Multi-Screen Video (MSV) support for ISA environments
configured with SCS. An MSV Asset Deletion script ran nightly by default. The script identified the
VOD assets that were removed by the backoffice and deleted them from the Vaults. If the asset was found
in any one of the VHOs, the asset was not deleted. Only when the asset was not found in all VHOs was
the asset deleted from the Vaults.