Juniper MEDIA FLOW CONTROLLER 2.0.4 -, Administrator'S Manual

Page: 247 / 400

Creating the origin-escalation-map XML File 247
Media Flow Controller Administrator’s Guide Server Map Configuration
Creating the origin-escalation-map XML File
The origin-escalation-map functionality determines which defined origins are online; if an
origin is not online, it automatically moves to the next defined origin, based on defined weight.
Under origin escalation, the specified weight each origin defined in the map denotes the order
in which requests are tried until a success is received or all nodes have been tried. Escalation
occurs when a network connectivity error is encountered, or when an origin returns an HTTP
return code specified in the XML file configuration.
Sample origin-escalation-map XML file:
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE OriginEscalationMap SYSTEM "OriginEscalationMap.dtd">
<OriginEscalationMap>
<Header>
<Version>1.0</Version>
<Application>MapXML</Application>
</Header>
<OriginEscalationMapEntry>
<Origin>dest.xxx.com</Origin>
<Port>80</Port>
<Options>heartbeatpath=/hello.html,weight=1,
http_response_failure_codes=404;500</Options>
</OriginEscalationMapEntry>
<OriginEscalationMapEntry>
<Origin>dest.yyy.com</Origin>
<Port>81</Port>
<Options>heartbeatpath=/hello2.html,weight=2,
http_response_failure_codes=404;500</Options>
</OriginEscalationMapEntry>
<OriginEscalationMapEntry>
<Origin>dest.zzz.com</Origin>
<Port>82</Port>
<Options>heartbeatpath=/hello3.html,weight=3,
http_response_failure_codes=404;500;503</Options>
</OriginEscalationMapEntry>
</OriginEscalationMap>
Tags:
•
OriginEscalationMap—Parent tag for Header and OriginEscalationMapEntry tags.
• Header—Parent tag for Version and Application tags.
•
Version—MapXML utility version:1.0.
•
Application—Type of Media Flow Controller application: MapXML.
• OriginEscalationMapEntry—Parent tag for Origin, Port, and Options tags.
•
Origin—Domain Name or IP address of origin server.
•
Port—TCP port of origin server.