Junos 10.3 Junos XML Management Protocol Guide
Requesting a Subset of Objects by Using Regular Expressions
90
Client Application
<rpc>
<get-configuration>
<configuration>
<routing-options>
<multicast>
<scope>
<name>local</name>
</scope>
</multicast>
</routing-options>
</configuration>
</get-configuration>
</rpc>
To request information about only those instances of a configuration object type that
have a specified set of characters in their identifier names, a client application includes
the
attribute with a regular expression that matches the identifier name. For
matching
example, the application can request information about just the SONET/SDH interfaces
at the
[edit interfaces]
hierarchy level by specifying the characters
regular expression.
Using the
attribute enables the application to represent the objects to return
matching
in a form similar to the XML Path Language (XPath) representation, which is described
in XML Path Language (XPath) Version 1.0, available from the World Wide Web Consortium
(W3C) at
http://www.w3.org/TR/xpath
parent levels are an ordered series of tag element names separated by forward slashes.
The angle brackets around tag element names are omitted, and the opening tag is used
to represent the entire tag element. For example, the following XPath:
configuration/system/radius-server/name
is equivalent to the following tagged representation:
<configuration>
<system>
<radius-server>
<name/>
</radius-server>
</system>
</configuration>
Junos XML Protocol Server
<rpc-reply xmlns:junos="URL ">
<configuration junos:changed-seconds=" seconds " \
junos:changed-localtime="timestamp">
<routing-options>
<multicast>
<scope>
<name>local</name>
<prefix>239.255.0.0/16</prefix>
<interface>ip-f/p/0</interface>
</scope>
</multicast>
</routing-options>
</configuration>
</rpc-reply>
. In an XPath representation, an object and its
so-
at the start of the
Copyright © 2010, Juniper Networks, Inc.