Specifications

B-1
Cisco Internet Streamer CDS 2.0-2.3 Software Configuration Guide
OL-13493-04
APPENDIX
B
Creating Manifest Files
This appendix describes the process for creating Manifest files used to acquire and distribute content
within the CDS network. This appendix includes the following topics:
• Introduction, page B-1
• Working with Manifest Files, page B-2
• Manifest Validator Utility, page B-14
• Manifest File Structure and Syntax, page B-17
• XML Schema, page B-44
• Manifest File Time Zone Tables, page B-50
For information about using a Manifest file in a delivery service, see the ““Identifying Content Using a
Manifest File” section on page 5-22.
Introduction
The CDS is used to ingest, distribute, and deliver multi-format content to different client devices. In
order to specify the content to be prefetched and to control the delivery of the prefetched content, an
XML file called a Manifest file is used. Third-party asset management systems can interoperate with the
CDS by using this Manifest file interface. Each delivery service in the CDS can be configured with or
without a Manifest file. The Manifest file can also be automatically generated by using the CDSM. The
Manifest file is primarily used in prefetch ingest and hybrid ingest.
The Manifest file is specified in the CDSM in the following ways:
• External Manifest File Specification—The Manifest file is hosted on an external server and a URL
pointing to that server is configured in the delivery service. The Manifest file can be fetched using
FTP, HTTP, HTTPS and CIFS protocols.
• GUI Configured—The CDSM GUI can generate a Manifest file. The CDSM provides the required
elements for the user to create a Manifest file and to specify the attributes in the Manifest file. Only
commonly used attributes are supported by the CDSM.
The Manifest file is processed by the Content Acquirer. The Content Acquirer parses the Manifest file,
creates the metadata based on the attributes in the file, and prefetches the content specified. For live
content and content that is ingested on demand, the Content Acquirer creates the metadata and does not
fetch the actual content. The metadata created by the Content Acquirer is propagated to all the Service
Engines participating in the delivery service.