Requesting A Specified Number Of Configuration Objects - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Junos 10.3 Junos XML Management Protocol Guide

Requesting a Specified Number of Configuration Objects

84
</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. For information about the attributes in the opening
"Requesting Information from the 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>
<!-- child tag elements for the first object -->
</first-object>
<second-object>
<!-- child tag elements for the second object -->
</second-object>
<!-- additional instances of the object -->
<!-- closing tags for each parent of the object type -->
</configuration>
</rpc-reply>
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 <junoscript> tag, or both. For more information, see "Specifying the Source
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.
To request information about a specific number of configuration objects of a specific
type, a client application emits the
tag elements that represent all levels of the configuration hierarchy from the root
(represented by the
<configuration>
for the object type. An empty tag represents the requested object type, and the following
attributes are included in it:
, to specify the number of objects to return
count
, to specify the index number of the first object to return (
start
the second, and so on)
(If the application is requesting only the first object in the hierarchy, it includes the
attribute and omits the
count="1"
request in an tag element:
<rpc>
<rpc>
<get-configuration>
<configuration>
<configuration>
tag element and encloses the
<get-configuration>
tag element) down to the immediate parent level
attribute.) The application encloses the entire
start
Copyright © 2010, Juniper Networks, Inc.
and tag
<rpc-reply>
tag, see
<configuration>
tag,
<get-configuration>
tag
<get-configuration>
for the first object, for
1 2