Client Application’s Role in a Junos XML Protocol Session

To create a session and communicate with the Junos XML protocol server, a client application performs the following procedures, which are described in the indicated sections:

1. Establishes a connection to the Junos XML protocol server on the routing platform, as described in Connecting to the Junos XML Protocol Server.
2. Opens a Junos XML protocol session, as described in Starting the Junos XML Protocol Session.
3. (Optional) Locks the candidate configuration or creates a private copy, as described in Exchanging Information with the Junos XML Protocol Server. Locking the configuration prevents other users or applications from changing it at the same time. Creating a private copy of the configuration enables the application to make changes without affecting the candidate or active configuration until the copy is committed.
4. Requests operational or configuration information, or changes configuration information, as described in Requesting Information and Changing Configuration Information.
5. (Optional) Verifies the syntactic correctness of a configuration before attempting to commit it, as described in Verifying a Configuration Before Committing It.
6. Commits changes made to the configuration, as described in Committing a Configuration.
7. Unlocks the candidate configuration if it is locked, as described in Unlocking the Candidate Configuration.
8. Ends the Junos XML protocol session and closes the connection to the device, as described in Ending a Junos XML Protocol Session and Closing the Connection.