 | Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
The JUNOScript server communicates with client applications within the context of a JUNOScript session. The server and client explicitly establish a connection and session before exchanging data, and close the session and connection when they are finished. The streams of JUNOScript and JUNOS XML tag elements emitted by the JUNOScript server and a client application must each constitute a well-formed XML document by obeying the structural rules defined in the document type definition (DTD) for the kind of information they are exchanging. The client application must emit tag elements in the required order and only in the allowed contexts.
Client applications access the JUNOScript server using one of the protocols listed in Supported Access Protocols. To authenticate with the JUNOScript server, they use either a JUNOScript-specific mechanism or the protocol’s standard authentication mechanism, depending on the protocol. After authentication, the JUNOScript server uses the JUNOS login usernames and classes already configured on the routing platform to determine whether a client application is authorized to make each request.
For information about establishing a connection and JUNOScript session, see the following sections:
For an example of a complete JUNOScript session, see Example of a JUNOScript Session.
| Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |