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

Copyright © 2010, Juniper Networks, Inc.
When the application requests formatted ASCII output, the Junos XML protocol server
formats its response in the same way that the CLI
configuration data—it uses the newline character, tabs, braces, and square brackets to
indicate the hierarchical relationships between configuration statements. The server
encloses formatted ASCII configuration statements in
tag elements:
<configuration-text>
<rpc-reply xmlns:junos="URL">
<configuration-text>
<!-- formatted ASCII configuration statements -->
</configuration-text>
</rpc-reply>
The attribute can be combined with one or more of the following other attributes
format
in the <get-configuration/>
, which is described in "Requesting Information from the Committed or
database
Candidate Configuration" on page 65
inherit and optionally groups
for Configuration Groups" on page 74
It does not make sense to combine the
(described in "Requesting a Change Indicator for Configuration Elements" on page 70)
or to include it after requesting an indicator for identifiers (described in "Requesting an
Indicator for Identifiers" on page 73). The change and identifier indicators appear only in
Junos XML-tagged output, which is the default output format.
An application can request Junos-XML tagged output or formatted ASCII text for the
entire configuration or any portion of it. For instructions on specifying the amount of data
to return, see "Specifying the Scope of Configuration Information to Return" on page 81.
The following example shows how to request formatted ASCII output from the
hierarchy level in the candidate configuration.
[edit policy-options]
show configuration
tag or opening <get-configuration>
, which are described in "Specifying the Output Format
attribute with the
format="text"
Chapter 4: Requesting Information
command displays
and
<rpc-reply>
tag:
attribute
changed
69