Elements - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Defining Configuration Data as Formatted ASCII Text or Junos XML Tag Elements
Copyright © 2010, Juniper Networks, Inc.
<load-configuration format="text">
<configuration-text>
/* formatted ASCII configuration data */
</configuration-text>
</load-configuration>
</rpc>
For information about the syntax for Junos XML tag elements and formatted ASCII text,
see "Defining Configuration Data as Formatted ASCII Text or Junos XML Tag Elements"
on page 107.
As discussed in "Providing Configuration Data in a File" on page 105 and "Providing
Configuration Data as a Data Stream" on page 106, a client application can provide new
configuration data to the Junos XML protocol server either in a file or as a data stream
emitted during the Junos XML protocol session. In both cases, it can use either Junos XML
tag elements or formatted ASCII text to define the new configuration data.
If the application uses Junos XML tag elements, it includes the tag elements representing
all levels of the configuration hierarchy from the root (the
down to each new or changed element. The notation is the same as that used to request
configuration information, and is described in detail in "Overview of Configuration Changes"
on page 103.
<configuration>
<!-- tag elements representing the configuration data -->
</configuration>
If the application provides the new data as formatted ASCII text, it uses the standard
Junos OS CLI notation to indicate the hierarchical relationships between configuration
statements—the newline character, tabs and other white space, braces, and square
brackets. For each new or changed element, the complete statement path is specified,
starting with the top-level statement that appears directly under the
level.
When ASCII text is provided as a data stream, it is enclosed in the
tag element:
<configuration-text>
/* formatted ASCII configuration statements */
</configuration-text>
When ASCII text is provided in a previously saved file, the
is not included in the file.
When providing new data as ASCII text, the application also includes the
attribute in the
<load-configuration/>
<rpc>
<load-configuration url="file-location" format="text"/>
</rpc>
<rpc>
<load-configuration format="text">
<configuration-text>
Chapter 5: Changing Configuration Information
<configuration>
<configuration-text>
tag or opening
<load-configuration>
tag element)
[edit] hierarchy
<configuration-text>
tag element
format="text"
tag.
107