Specifying The Source And Format Of New Configuration Data; Providing Configuration Data In A File - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Specifying the Source and Format of New Configuration Data

Providing Configuration Data in a File

Copyright © 2010, Juniper Networks, Inc.
Unlocks the candidate configuration if it is locked, as described in "Unlocking the
8.
Candidate Configuration" on page 54. Other users and applications cannot change
the configuration while it remains locked.
Ends the Junos XML protocol session and closes the connection to the device, as
9.
described in "Ending a Junos XML Protocol Session and Closing the Connection" on
page 55.
A client application can provide new configuration data either in a file or as a data stream,
and as either Junos XML tag elements or formatted ASCII text. See the following sections:
Providing Configuration Data in a File on page 105
Providing Configuration Data as a Data Stream on page 106
Defining Configuration Data as Formatted ASCII Text or Junos XML Tag
Elements on page 107
To provide new configuration data in a file, a client application encloses the
tag with the
<load-configuration/>
Junos XML tag elements, it either includes the
attribute:
<rpc>
<load-configuration url="file-location"/>
</rpc>
If the data is formatted ASCII text, the
<rpc>
<load-configuration url="file-location" format="text"/>
</rpc>
Before loading the file, the client application or an administrator saves either Junos XML
tag elements (enclosed in a
contents of the file (formatted ASCII text is not enclosed in a
element in the file). For information about the syntax for the data in the file, see "Defining
Configuration Data as Formatted ASCII Text or Junos XML Tag Elements" on page 107.
The value of the url attribute can be a local file path, an FTP location, or a Hypertext
Transfer Protocol (HTTP) URL:
A local filename can have one of the following forms:
—File on a mounted file system, either on the local flash disk or on
/path/filename
hard disk.
or
a:filename a:path/filename
root-level directory). The removable media can be in MS-DOS or UNIX (UFS) format.
A filename on an FTP server has the following form:
Chapter 5: Changing Configuration Information
attribute in an
url <rpc>
format="xml"
attribute is included:
format="text"
<configuration> tag element) or formatted ASCII as the
—File on the local drive. The default path is
tag element. If the data is
attribute or omits the format
tag
<configuration-text>
(the
/
105