Specifications

2-5
Cisco Internet Streamer CDS 2.0-2.3 Software Configuration Guide
OL-13493-04
Chapter 2 Network Design
Delivery Service
Origin Servers
Content is stored on origin servers. Each delivery service is configured with one content origin. The
same origin server can be used by multiple live delivery services. However, only one prefetch/caching
delivery service is allowed per content origin. Each Content Origin is defined in the Internet Streaming
CDSM by the following:
• Origin server
• Service routing domain name
The origin server is defined by the domain name that points to the actual origin server. The origin server
domain name is used to fetch content that resides outside the delivery service, and to request redirection
in case of a failure. The origin server must support at least one of the following protocols in order for
the CDS to be able to ingest content:
• HTTP
• HTTPS
• FTP
• CIFS
• SMB
Content can also originate from a local file on the CDS.
The service routing domain name is an FQDN and is used for content redirection. Each content that is
ingested by means of the Manifest file is published using the service routing domain name. The service
routing domain name configured for the Content Origin must also be configured in the DNS servers, so
client requests can be redirected to a Service Router for request mediation and redirection.
Proxy Server
When the Content Acquirer cannot directly access the origin server because the origin server is set up to
allow access only by a specified proxy server, a proxy server can be configured. The proxy server is
configured through the Internet Streaming CDSM for fetching the Manifest file, and through the
Manifest file for fetching the content. Proxy configurations made in the Manifest file take precedence
over proxy configurations in the CLI.
Manifest File
The Manifest file contains XML tags, subtags, and attributes used to define how content is ingested and
delivered. Each delivery service has one Manifest file. The Manifest file can specify attributes for
content playback and control. Attributes for specifying metadata only, without fetching the content, are
supported. If special attributes are set, only the metadata and control information are propagated to the
Service Engines. The control data is used to control the playback of the content when it gets cached by
dynamic ingest. The Manifest file format and details are described in Appendix B, “Creating Manifest
Files.”
Crawling
For HTTP, HTTPS, FTP, SMB, or CIFS, a single item can be fetched by specifying a single URL in the
CDSM or Manifest file, or content can be fetched by using the crawler feature. The crawler feature
methodically and automatically searches acceptable websites and makes a copy of the visited pages for