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

Copyright © 2010, Juniper Networks, Inc.
When the client application requests Junos XML-tagged output (the default), the Junos
XML protocol server returns the requested object 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 -->
<object>
<!-- child tag elements of the object -->
</object>
<!-- closing tags for each parent of the object -->
</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.
The following example shows how to request the contents of one multicasting scope
called , which is at the
local
desired object, the client application emits the
element as the innermost tag element. The output is from the candidate configuration
and is tagged with Junos XML tag elements (the default).
<configuration>
[edit routing-options multicast]
<name>local</name>
Chapter 4: Requesting Information
and tag
<rpc-reply>
tag, see
<configuration>
tag,
<get-configuration>
tag
<get-configuration>
hierarchy level. To specify the
identifier tag
89