Requesting Identifiers Only - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Junos 10.3 Junos XML Management Protocol Guide

Requesting Identifiers Only

86
The following example shows how to request the third and fourth Junos user accounts
at the hierarchy level. The output is from the candidate configuration
[edit system login]
and is tagged with Junos XML tag elements (the default).
Client Application
<rpc>
<get-configuration>
<configuration>
<system>
<login>
<user count="2" start="3"/>
</login>
</system>
</configuration>
</get-configuration>
</rpc>
To request just the identifier tag element for configuration objects of a specified type in
a hierarchy, a client application emits a
the tag elements representing 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
attribute is included. The entire request is enclosed in an
recurse="false"
element.
To request the identifier for all objects of a specified type, the client application includes
only the recurse="false" attribute:
<rpc>
<get-configuration>
<configuration>
<!-- opening tags for each parent of the object type -->
<object-type recurse="false"/>
<!-- closing tags for each parent of the object type -->
</configuration>
</get-configuration>
</rpc>
Junos XML Protocol Server
<rpc-reply xmlns:junos="URL ">
<configuration junos:changed-seconds=" seconds " \
junos:changed-localtime="timestamp">
<system>
<login>
<user junos:position="3" junos:total="22">
<name>barbara</name>
<uid>1423</uid>
<class>operator</class>
</user>
<user junos:position="4" junos:total="22">
<name>carlo</name>
<uid>1426</uid>
<class>operator</class>
</user>
</login>
</system>
</configuration>
</rpc-reply>
<get-configuration>
tag element) down to the immediate parent level
tag element that encloses
tag
<rpc>
Copyright © 2010, Juniper Networks, Inc.