Juniper NETWORK AND SECURITY MANAGER 2010.4 - API GUIDE REV 1, Manual

Page: 26 / 170

Table 5: System Service API Operations (continued)
Reuses the token received in LoginResponse to send a response to the challenge.
Receives a token if the response is successful.
Request: Answer to the challenge question.
Response: Token received.
RespondToChallengeRequest
Logout from the system.
Request: none
Response: none
LogoutRequest
This operation retrieves system information (service list and all accessible domain IDs
and names).
Request: serviceName
Response: serviceDesc, domain name and domain ID.
GetSystemInfoRequest
NOTE: When using the LoginRequest API, enter
global.<subdomain name>
to log in to a particular subdomain. The login fails if just the subdomain name
is used.
Data Centric Service API
The Data Centric Service API provides access to the internal data of NSM. It receives
incoming data access requests, retrieves the data from NSM, conducts any necessary
transformations, and sends the transformed data back as responses. This section
introduces the XML subtree filter used with the service and describes the Data Centric
data elements.
NOTE: In the current release of NSM, write access to the deviceobj and sysvpn
from the Data Centric Service is blocked to protect data integrity.
See “Data Centric API WSDL” on page 135 for a description of the API-defining WSDL file.
Data Centric Service XML Subtree Filter
The filter used in the Data Centric Service API is the XML subtree filter defined by
NETCONF. Subtree filtering is a mechanism that allows an application to select particular
XML subtrees from the configurations from the devices.
A subtree filter consists of zero or more element subtrees, which represent the filter
selection criteria.
Five types of components may be present in a subtree filter:
Copyright © 2010, Juniper Networks, Inc. 8
Network and Security Manager 2010.4 API Guide