Unlocking The Candidate Configuration; Creating A Private Copy Of The Configuration - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Junos 10.3 Junos XML Management Protocol Guide

Unlocking the Candidate Configuration

Creating a Private Copy of the Configuration

54
The candidate configuration already includes changes that have not yet been
committed. To commit the changes, see "Committing a Configuration" on page 133. To
roll back to a previous version of the configuration (and lose the uncommitted changes),
see "Rolling Back to a Previous or Rescue Configuration" on page 109.
Only one application can hold the lock on the candidate configuration at a time. Other
users and applications can read the candidate configuration while it is locked, or can
change their private copies. The lock persists until either the Junos XML protocol session
ends or the client application unlocks the configuration by emitting the
<unlock-configuration/> tag, as described in "Unlocking the Candidate Configuration"
on page 54.
If the candidate configuration is not committed before the client application unlocks it,
or if the Junos XML protocol session ends for any reason before the changes are
committed, the changes are automatically discarded. The candidate and committed
configurations remain unchanged.
As long as a client application holds a lock on the candidate configuration, other
applications and users cannot change the candidate. To unlock the candidate
configuration, the client application includes the
tag element:
<rpc>
<unlock-configuration/>
</rpc>
To confirm that it has successfully unlocked the configuration, the Junos XML protocol
server returns an opening
<rpc-reply>
them:
<rpc-reply xmlns:junos="URL">
</rpc-reply>
If the Junos XML protocol server cannot unlock the configuration, the
element instead encloses an
To create a private copy of the candidate configuration, a client application emits the
tag enclosed in
<private/>
<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"
on page 103.
After making changes to the private copy, the client application can commit the changes
to the active configuration on the device running Junos OS by emitting the
tag element, as for the regular candidate configuration. However,
<commit-configuration>
<unlock-configuration/>
and closing
</rpc-reply>
<xnm:error> tag element explaining the reason for the failure.
and
<rpc> <open-configuration>
tag in an
tag with nothing between
<rpc-reply>
tag elements:
Copyright © 2010, Juniper Networks, Inc.
<rpc>
tag