Brocade Virtual ADX XML API Programmer’s Guide (Supporting ADX v03.1.00) - Manual (Page 13)

Brocade Virtual ADX XML API Programmer’s Guide 3
53-1003248-01
WSDL location
1
Users have access to documented input and output characteristics for each XML SOAP method, the
data types, and their values in a platform-independent way. The platform independence is achieved
through use of XML (SOAP over HTTP) as the medium for information exchange. One major
advantage of the XML-API is significant improvement in latency for accessing information from your
ADX devices. The reason for this advantage is that HTTP is optimized for bulk data transfer, unlike
SSH or Telnet, which are traditionally used for data access. Latency is measured as the time
difference between a request sent to the ADX and a meaningful response becoming available at
the client for further action. Such low latency environments are extremely useful in large
application delivery deployments, where latency is expected to be as low as possible.
WSDL location
You can obtain the four WSDL files by accessing a Brocade Virtual ADX through the HTTP interface
using the following URLs:
http://<device-ip>/wsdl/sys_service.wsdl
http://<device-ip>/wsdl/network_service.wsdl
http://<device-ip>/wsdl/slb_service.wsdl
http://<device-ip>/wsdl/security_service.wsdl
http://<device-ip>/wsdl/gslb_service.wsdl
The <device-ip> variable in the URL refers to the IP address of the management port on the
Brocade Virtual ADX.
Accessing the client API using SOAP
NOTE
The client application must send an HTTP authentication header before invoking every SOAP
request. The username and password in the authentication header must have super user privileges
on the Brocade Virtual ADX. The HTTP authentication header must also contain context information
along with the username and password.
Creating client-specific APIs from client stubs
Use cases
The following examples provide a framework for developing ADX-specific programs.
Adding and binding a real server and a VIP
1. Add a real server.
2. Add a real server port.
3. Add a virtual server and virtual server port.