Overview of a Junos XML Protocol Session

Communication between the Junos XML protocol server and a client application is session based. The two parties explicitly establish a connection before exchanging data and close the connection when they are finished. Each request from the client application and each response from the Junos XML protocol server constitutes a well-formed XML document, because the tag streams obey the structural rules defined in the Junos XML protocol and Junos XML DTDs for the kind of information they encode. Client applications must produce a well-formed XML document for each request by emitting tag elements in the required order and only in the legal contexts.

The following list outlines the basic structure of a Junos XML protocol session. For more specific information, see the Junos XML Management Protocol Guide

1. The client application establishes a connection to the Junos XML protocol server and opens the Junos XML protocol session.
2. The Junos XML protocol server and client application exchange initialization information, which is used to determine if they are using compatible versions of the Junos OS and the Junos XML management protocol.
3. The client application sends one or more requests to the Junos XML protocol server and parses its responses.
4. The client application closes the Junos XML protocol session and the connection to the Junos XML protocol server.