Juniper MEDIA FLOW CONTROLLER 2.0.4 -, Administrator'S Manual

Page: 244 / 400

Server Map Configuration Media Flow Controller Administrator’s Guide
244 Creating the host-origin-map XML File Copyright © 2010, Juniper Networks, Inc.
Creating the host-origin-map XML File
Use the server-map format-type host-origin-map XML file to map the incoming (target
origin) HOST header value to a specified origin server (no maximum). No check is made to
determine if an origin is online when requested. The XML file must provide the following tags.
Sample host-origin-map XML file:
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE HostOriginMap SYSTEM "HostOriginMap.dtd">
<HostOriginMap>
<Header>
<Version>1.0</Version>
<Application>MapXML</Application>
</Header>
<HostOriginEntry>
<Host>host1.xxx.yyy.com</Host>
<Origin>host1.com</Origin>
<Port>80</Port>
</HostOriginEntry>
<HostOriginEntry>
<Host>host2.aaa.bbb.com</Host>
<Origin>host2.com</Origin>
<Port>81</Port>
</HostOriginEntry>
<HostOriginEntry>
<Host>host3.ccc.ddd.com</Host>
<Origin>host3.com</Origin>
<Port>82</Port>
</HostOriginEntry>
</HostOriginMap>
Tags:
•
HostOriginMap—Parent tag for Header and HostOriginEntry tags.
•
Header—Parent tag for Version and Application tags.
•
Version—MapXML utility version:1.0.
•
Application—Type of Media Flow Controller application: MapXML.
• HostOriginEntry—Parent tag for Host, Origin, Port, and Options tags.
•
Host—The incoming request HOST header (target origin); may be host: port or
just host.
•
Origin—The origin-server to use to resolve cache misses.
•
Port—The origin server port to use to resolve cache misses.
•
Options—Not supported in Release 2.0.4.
Important! Do not change the Version from 1.0 or the Application from MapXML without
explicit, new instructions. These values must be present or the XML file will be rejected.