Overview of a JUNOScript Session

Communication between the JUNOScript 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 JUNOScript server constitutes a well-formed XML document, because the tag streams obey the structural rules defined in the JUNOScript 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 JUNOScript session. For more specific information, see the JUNOScript API Guide.

1. The client application establishes a connection to the JUNOScript server and opens the JUNOScript session.
2. The JUNOScript server and client application exchange initialization information, used to determine if they are using compatible versions of the JUNOS Software and the JUNOScript API.
3. The client application sends one or more requests to the JUNOScript server and parses its responses.
4. The client application closes the JUNOScript session and the connection to the JUNOScript server.