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

Copyright © 2010, Juniper Networks, Inc.
<!-- opening tags for each parent of the object -->
<object-type count="count" start="index"/>
<!-- closing tags for each parent of the object -->
</configuration>
</get-configuration>
</rpc>
When the application requests Junos XML-tagged output (the default), the Junos XML
protocol server returns the requested objects in
elements, starting with the object specified by the
running consecutively. In the opening container tag for each object, it includes
two attributes:
junos:position , to specify the object's numerical index
, to report the total number of such objects that exist in the hierarchy
junos:total
In the following, the identifier tag element is called
attributes in the opening
<configuration>
Committed or Candidate Configuration" on page 65.)
<rpc-reply xmlns:junos="URL">
<configuration attributes>
<!-- opening tags for each parent of the object type -->
<first-object junos:position="index1" junos:total="total">
<name>identifier-for-first-object</name>
<!-- other child tag elements of the first object -->
</first-object>
<second-object junos:position="index2" junos:total="total">
<name>identifier-for-second-object</name>
<!-- other child tag elements of the second object -->
</second-object>
<!-- additional objects -->
<!-- closing tags for each parent of the object type -->
</configuration>
</rpc-reply>
The junos:position and junos:total
ASCII output by including the
element (as described in "Requesting Output as Formatted ASCII Text or Junos XML Tag
Elements" on page 68).
To specify the source of the output (candidate or active configuration) and request
special formatting of the output (for example, formatted ASCII text or an indicator for
identifiers), the application can include attributes in the opening
its opening tag, or both. For more information, see "Specifying the Source
<junoscript>
and Output Format of Configuration Information" on page 65.
The application can also request additional configuration elements of the same or other
types by including the appropriate tag elements in the same
element. For more information, see "Requesting Multiple Configuration Elements
Simultaneously" on page 93.
<configuration>
start
<name>. (
tag, see "Requesting Information from the
attributes do not appear if the client requests formatted
attribute in the
format="text"
Chapter 4: Requesting Information
and <rpc-reply> tag
attribute and
For information about the
tag
<get-configuration>
<get-configuration>
tag
<get-configuration>
tag,
85