Using The Same Configuration Tag Elements In Requests And Responses - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Junos xml management protocol guide
Hide thumbs Also See for JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010:
Table of Contents

Advertisement

Using the Same Configuration Tag Elements in Requests and Responses

Copyright © 2010, Juniper Networks, Inc.
Chapter 2: Using Junos XML Management Protocol and Junos XML Tag Elements
The Junos XML protocol server encloses its response to each configuration request in
and
<rpc-reply>
<configuration>
within a
<configuration>
tag element contrasts with how the server encloses each different
operational response in a tag element named for that type of response—for example,
the
tag element for chassis information or the
<chassis-inventory>
tag element for interface information.
The Junos XML tag elements within the
configuration hierarchy levels, configuration objects, and object characteristics, always
ordered from higher to deeper levels of the hierarchy. When a client application loads a
configuration, it can emit the same tag elements in the same order as the Junos XML
protocol server uses when returning configuration information. This consistent
representation makes handling configuration information more straightforward. For
instance, the client application can request the current configuration, store the Junos
XML protocol server's response to a local memory buffer, make changes or apply
transformations to the buffered data, and submit the altered configuration as a change
to the candidate configuration. Because the altered configuration is based on the Junos
XML protocol server's response, it is certain to be syntactically correct. For more
information about changing routing platform configuration, see "Changing Configuration
Information" on page 103.
Similarly, when a client application requests information about a configuration element
(hierarchy level or configuration object), it uses the same tag elements that the Junos
XML protocol server will return in response. To represent the element, the client application
sends a complete stream of tag elements from the top of the configuration hierarchy
(represented by the
<configuration>
innermost tag element, which represents the level or object, is either empty or includes
the identifier tag element only. The Junos XML protocol server's response includes the
same stream of parent tag elements, but the tag element for the requested configuration
element contains all the tag elements that represent the element's characteristics or
child levels. For more information, see "Requesting Configuration Information" on page 64.
tag elements. Enclosing each configuration response
<configuration>
tag element represent
tag element) down to the requested element. The
<interface-information>
21

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junos os

Table of Contents