Specifications

2-14
Cisco TV CDS 2.5 ISA Software Configuration Guide
OL-24788-01
Chapter 2 Network Design
Vault Virtualization
• IngestDriverHost
• IngestDriverPort
• IngestDriverNoOfThreads
The Ingest Driver server logs events to the IngestDriver.log file located in the /arroyo/log directory.
Ingest Driver Client
The Ingest Driver client is used by the local Content Store to send requests to the Ingest Driver server
and receive responses from the server. When a provision call from the local Content Store is received
from the backoffice, the Ingest Driver client establishes a TCP connection with the Ingest Driver server,
sends the request, and closes the connection once the response is received.
The local Content Store reads the isa.cfg file and incorporates the following Ingest Driver configuration
parameters for the Ingest Driver client set on the CDSM GUI:
• IngestDriverEnabled=1
• IngestDriverRole=0 (for client)
• IngestDriverHost
• IngestDriverPOrt
• IngestDriverTimeout
• MarketId
Ingest Driver Content Management
The local Content Stores at the remote sites perform content management of the content at the central
facility by interfacing with the Ingest Driver. The Ingest Driver compares the requested content identifier
of each content ingestion and deletion request to the CDS repository to determine if the content exists.
If the content does not exist, it is ingested using FTP and the FTP URL provided by the remote site. If
the content already exists, the repository is updated to maintain the reference between the requesting site
and the content. The Ingest Driver returns the CDS internal representation of the content bundle and
associated content information, such as file size and bit rate.
When the Ingest Driver receives a deletion request, it determines if the request is for the last reference
to the content. If it is the last reference, the Ingest Driver requests that the central Content Store delete
the content and associated MPEG files. If it is not the last reference for the content, the Ingest Driver
just removes the reference of the requesting site for that content in the repository.
Remote Ingests
At each headend, the external ISA interfaces to the backoffice do not change, and call flows remain the
same. The remote CDSM is extended to identify a site as part of a regionalization grouping, and specify
the communication information of the Ingest Driver. Internally, the local Content Store application is
modified to check for this setting. If regionalization is turned on, the local Content Store application
directs VOD (provision) requests to the Ingest Driver and RTA (provisionForPush) requests are directed
to the local Vaults.
The local Content Store performs the createServant call locally, thus ensuring that each remote site has
its own IOR representing the content object. If the request is distributed, the local repository is updated
with the content-specific information, such as the content bundle, file size, and bit rate returned by the
Ingest Driver. This allows the remote site to have local representation of centrally stored content.