Example: Host-Origin-Map Dtd; Validating With The Dtd; Creating The Cluster-Map Xml File - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Administrator's Guide

Example: host-origin-map DTD

Document Type Definition (DTD) for host-origin-map. "PCDATA" indicates data that the XML
parser fills in after reading your file. You can use this to validate your XML; see
the DTD,"
<!-- HostOriginMap 1.0 DTD, Copyright (c) 2010 by Juniper Networks, Inc. -->
<!ELEMENT HostOriginMap (Header*, HostOriginEntry*)>
<!ELEMENT Header (Version, Application)>
<!ELEMENT Version (#PCDATA)>
<!ELEMENT Application (#PCDATA)>
<!ELEMENT HostOriginEntry (Host, Origin, Port)>
<!ELEMENT Host (#PCDATA)>
<!ELEMENT Origin (#PCDATA)>
<!ELEMENT Port (#PCDATA)>
<!ELEMENT Options (#PCDATA)>

Validating With the DTD

When generating server-map XML files, you can validate the XML against the DTD by
running the following under linux (example uses HostOriginMap; for cluster-map use
ClusterMap.dtd, for origin-escalation-map use OriginEscalationMap.dtd):
xmllint --noout --dtdvalid <DTD filename> <XML filename>
Example:
xmllint --noout --dtdvalid ./dtd/HostOriginMap.dtd HostOriginMap.xml
Note! Ignore the following xmllint warning:
HostOriginMap.xml:2: warning: failed to load external entity
"HostOriginMap.dtd"

Creating the cluster-map XML File

The server-map format-type cluster-map calls for specific definition of a consistent hashing
scheme used to bind objects to nodes. For background information on consistent hashing, see
the following:
Sample cluster-map XML file:
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE ClusterMap SYSTEM "ClusterMap.dtd">
<ClusterMap>
<Header>
<Version>1.0</Version>
<Application>MapXML</Application>
</Header>
<ClusterMapEntry>
<Node>NodeName1</Node>
<IP>172.19.172.52</IP>
for details.
http://www8.org/w8-papers/2a-webserver/caching/paper2.html
Server Map Configuration
Creating the cluster-map XML File
"Validating With
245