(Supporting ADX v03.1.00) Owner's manual

Brocade Virtual ADX Graphical User Interface Guide 257
53-1003242-01
Appendix
B
Config Template XML Schema
In this appendix
•Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
•XML schema element reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Overview
The XML Schema for the Config Templates allows you to define the Brocade Virtual ADX
configuration.
NOTE
For information on the System APIs for the Config Template feature, refer to the Brocade Virtual ADX
XML API Programmer’s Guide.
For example, the following defines a few real servers:
This XML Schema is designed with the following goals:
• The feature exists inside the Brocade Virtual ADX and is client-neutral; it is meant to be
multi-purpose for different kinds of clients.
• It is application-neutral; it has flexible settings to support many different applications, including
non-application scenarios like basic load balancing.
• Good templates seek to be as simple as possible. More complex features are designed to be
optional and used when they return enough benefit to justify their added complexity.
• Using a well-defined data model, including an XML schema for expressing it, encourages good
interoperability and clean design.
• User values can be plugged in at runtime, such as name prefixes, IP addresses or ranges.
Additional capabilities include variables and repeaters, as described in the next sections.
<reals>
<real>
<name>rs1</name>
<ip>10.0.1.51</ip>
</real>
<real>
<name>rs2</name>
<ip>10.0.2.52</ip>
</real>
</reals>