Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Understanding the 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. Satisfies any prerequisites required for a connection, as described in Satisfying the Prerequisites for Establishing a Connection to the Junos XML Protocol Server.

  2. Establishes a connection to the Junos XML protocol server on the routing, switching, or security platform, as described in Connecting to the Junos XML Protocol Server.

  3. Starts a Junos XML protocol session, as described in Starting Junos XML Protocol Sessions.

  4. Optionally locks the candidate configuration, creates a private copy of the configuration, or opens an instance of the ephemeral configuration database.

    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 configuration until the copy is committed. For more information, see Locking and Unlocking the Candidate Configuration or Creating a Private Copy Using the Junos XML Protocol.

    For information about the ephemeral configuration database, see Understanding the Ephemeral Configuration Database and Enabling and Configuring Instances of the Ephemeral Configuration Database.

  5. Requests operational or configuration information, or changes the configuration, as described in Sending Requests to the Junos XML Protocol Server.

  6. (Optional) Verifies the syntactic correctness of the candidate configuration or private copy before attempting to commit it, as described in Verifying Configuration Syntax Using the Junos XML Protocol.

  7. Commits changes made to the candidate configuration or private copy, as described in Committing the Candidate Configuration Using the Junos XML Protocol, or commits changes made to an open instance of the ephemeral configuration database, as described in Committing and Synchronizing Ephemeral Configuration Data Using the NETCONF or Junos XML Protocol.

  8. Unlocks the candidate configuration if it is locked or closes a private copy of the configuration or an open instance of the ephemeral configuration database.

    Other users and applications cannot change the candidate configuration while it remains locked. For more information, see Locking and Unlocking the Candidate Configuration or Creating a Private Copy Using the Junos XML Protocol.

  9. 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.