Example Origin-Escalation-Map Dtd; Nfs-Map Xml File - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Server Map Configuration
•
Important!
explicit, new instructions. These values must be present or the XML file will be rejected.

Example origin-escalation-map DTD

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

nfs-map XML File

Use the server-map format-type nfs-map XML file to provide a list of NFS mount-points;
mainly, hostname and publishing point, and some other information. The XML file must
provide the following tags.
Sample nfs-map XML file:
<response scode="0" scode_description="success!">
<PUBLISHINGPOINTS INTERVAL-SEC="3600">
<MISSINGFILE PATH="C:\path1\path2\path3\FileNotFound.wma"/>
<INVALIDPUBLISHINGPOINT PATH="C:\path1\path2\path3\StorageOffline.wma"/>
<PUBLISHINGPOINT NAME="name1" PATH="\\<name>.<name>.<name>.com\name1"/>
<PUBLISHINGPOINT NAME="name2" PATH="\\<name>.<name>.<name>.com\name2"/>
<PUBLISHINGPOINT NAME="name3" PATH="\\<name>.<name>.<name>.com\name3"/>
<PUBLISHINGPOINT NAME="name4" PATH="\\<name>.<name>.<name>.com\name4"/>
</PUBLISHINGPOINTS>
</response>
Note! For Release 2.0.4, Media Flow Controller NFS origin server map uses a proprietary
parser to extract data from the XML file; the file must use the tags and format described.
248 nfs-map XML File
Options
−
heartbeatpath = Relative URI to use to heart beat node.
−
http_response_failure_codes = Which codes trigger escalation.
−
weight=<integer> = Order of escalation; highest priority is the lowest value.
Do not change the Version from 1.0 or the Application from MapXML without
Media Flow Controller Administrator's Guide
for details.
Copyright © 2010, Juniper Networks, Inc.