[Contents] [Prev] [Next] [Index] [Report an Error]

Creating a Private Copy of the Configuration

To create a private copy of the candidate configuration, a client application emits the <private/> tag enclosed in <rpc> and <open-configuration> tag elements:



<rpc>

     <open-configuration> 


     <private/> 


     </open-configuration> 

</rpc>

The client application can then perform the same operations on the private copy as on the regular candidate configuration, as described in Changing Configuration Information.

After making changes to the private copy, the client application can commit them to the active configuration on the routing platform by emitting the <commit-configuration> tag element, as for the regular candidate configuration. However, there are some restrictions on the commit operation for a private copy. For more information, see Committing a Private Copy of the Configuration.

To discard the private copy without committing it, a client application emits the <close-configuration/> tag enclosed in an <rpc> tag element:



<rpc>

     <close-configuration/> 

</rpc>

Any changes to the private copy are lost. Changes to the private copy are also lost if the JUNOScript session ends for any reason before the changes are committed. It is not possible to save changes to a private copy other than by emitting the <commit-configuration> tag element.

The following example shows how to create a private copy of the configuration. The JUNOScript server includes a reminder in its confirmation response that changes are discarded from a private copy if they are not committed before the session ends.

[Contents] [Prev] [Next] [Index] [Report an Error]