To provide the new configuration data in a file, a client application emits the <url> and <edit-config> tag elements in an<rpc> tag element:
<rpc>
<edit-config>
<target>
<candidate/>
</target>
<url>
<!- - location of file containing configuration data - ->
</url>
<!- - other child tag elements of the <edit-config> tag element - ->
</edit-config>
</rpc>
]]>]]>
Before loading the file, the client application or an administrator saves XML tag elements as the contents of the file. The file includes the tag elements representing all levels of the configuration hierarchy from the root (represented by the <configuration> tag element) down to each element to change. The notation is the same as that used to request configuration information, as described in Requesting Information. For more detailed information about the XML representation of configuration statements, see Mapping Configuration Statements to SRC XML Tag Elements.
The file named by the <url> tag element can be specified as a local file path, an FTP location, or a Hypertext Transfer Protocol (HTTP) URL:
-
ftp://username:password@hostname/path/filename
-
http://username:password@hostname/path/filename
The default value for the path variable is the home directory for the username. To specify an absolute path, the application starts the path with the characters %2F, as in ftp://username:password@hostname/%2Fpath/filename.
The following example shows how to incorporate configuration data stored in the file /var/configs/user-accounts on the FTP server called cfg-server.mycompany.com.