Specifications
B-29
Cisco Internet Streamer CDS 2.0-2.3 Software Configuration Guide
OL-13493-04
Appendix B Creating Manifest Files
Manifest File Structure and Syntax
<server name="ultra-server">
<host name="http://ultra-server" />
</server>
<item src="RemAdmin/InternalReview/firstpage.htm"
cdn-url="RemAdmin/Production/firstpage.htm" />
</CdnManifest>
In the preceding example, src is the content acquisition URL and cdn-url is the publishing URL.
Note The content item file path (RemAdmin/InternalReview/firstpage.htm) is controlled by the
Manifest file. The cdn-url attribute associates a file path with the content item in the
Manifest file. The Manifest file allows the file path for the cdn-url attribute to be specified
independently of the file path from which the content items are to be acquired from the
origin server (src attribute), allowing the publishing URL to differ from the content
acquisition URL.
If the content requires playback authentication or is live content, the origin server from which the
content is acquired has to be contacted. Therefore, two URLs must exist for the same content item,
and the URL specified in the cdn-url attribute must exist on the origin server at all times.
For example, if the content item “RemAdmin/Production/firstpage.htm” in the preceding example
requires playback authentication, this content must exist on the “ultra-server” origin server.
Otherwise, prefetched content playback will fail.
In general, you should not use the cdn-url, cdnPrefix, or srcPrefix attributes if playback
authentication is required or if the content is live.
If you use FTP to acquire content and the content type is not specified in the Manifest file and the
cdn-url attribute is specified to alter your publishing URL, the cdn-url attribute must have the
correct file path extension. Otherwise, the incorrect content type will be generated and you cannot
play the content.
The following example correctly shows the publishing URL with the same file path extension (.jpg)
as the origin server URL.
<item src="ftp://ftp-server.abc.com/pictures/pic.jpg" cdn-url="pic.jpg" />
The following example is incorrectly written, because it does not specify the file path extension
(.jpg) in the cdn-url attribute.
<item src="ftp://ftp-server.abc.com/pictures/pic.jpg" cdn-url="pic" />
• type
The type attribute is optional and defines whether content is to be prefetched or live on the CDS
network. The three type attributes are prepos, cache, and wmt-live. The wmt-live type attribute is
used to deliver live content. The cache type corresponds to hybrid ingest method. If this field is left
blank, the default type is prepos.
Note For type="cache", <host> and <server> tags are not used.
Note Currently, only serveStartTime and serveStopTime are supported for the type="cache"
attribute.
• playServer