<get-configuration>

Usage

<rpc>
    <get-configuration [database="(candidate|committed)"] [format="(text|xml)"]/>

    <get-configuration [database="(candidate|committed)"] [format="(text|xml)"]>
        <!-- tag elements representing hierarchy level or object to display -->
    </get-configuration>
</rpc>

Description

Request configuration data from the JUNOScript server. The database and format attributes specify the source and formatting of the data to display. To display the entire hierarchy, emit the empty <get-configuration/> tag. To display one hierarchy level or a single configuration object, emit tag elements within the <get-configuration> tag element to represent all levels of the configuration hierarchy from the root (represented by the <configuration> tag element) down to the level or object to display. To represent the requested level, emit it as an empty tag. To represent the requested object, emit its container tag element and identifier tag element only, not any tag elements that represent other characteristics.

Attributes

database—Specifies the configuration hierarchy from which to display data. There are two acceptable values:

• candidate—The current candidate configuration
• committed—The currently active (most recently committed) configuration on the router

format—Specifies the format in which the JUNOScript server returns the configuration data. There are two acceptable values:

• text—Configuration statements are formatted as ASCII text, using the newline character, tabs and other white space, braces, and square brackets to indicate the hierarchical relationships between the statements. This is the format used in configuration files stored on the router and displayed by the JUNOS CLI show configuration command.
• xml—Configuration statements are represented by the corresponding JUNOScript tag elements. This is the default value if the format attribute is omitted.

See Also

<rpc>