Upload and Format Configuration Data in a Junos XML Protocol Session
In a Junos XML protocol session with a device running Junos
OS, a client application uses the <load-configuration> tag element to upload configuration data to the candidate configuration
or open configuration database on the device. By setting the <load-configuration> attributes to the appropriate
values, the client application can specify the source and format of
the configuration data to upload. A client application can provide
new configuration data using a text file or streaming data, and the
data can be formatted as Junos XML tag elements, formatted ASCII text,
JSON data, or a series of Junos OS configuration mode commands.
You can choose to stream your configuration changes within your session or reference data files that include the desired configuration changes. Each method has advantages and disadvantages. Streaming data allows you to send your configuration change data inline, using your Junos XML protocol connection. This is useful when the device is behind a firewall and you cannot establish another connection to upload a data file. With text files you can keep the edit configuration commands simple; with data files, there is no need to include the possibly complex configuration data stream.
The delivery mechanism and the format are discussed in detail in the following topics: