Version
4.0
A SOAP compliant programming environment will parse the WSDL files to
determine which remote methods can be called, and will then allow the
application to call these methods much as if they were local functions.
The SOAP environment insulates the application developer from the
underlying complexity network connectivity, XML formatting, cross
platform compatibility, etc. The application developer can concentrate on
implementing the ZXTM control logic required to support the application
they are building.
The ZXTM Control API can be used by any programming language and
application environment that supports SOAP services. C#, Perl, Java and
Python are commonly used.
The ZXTM Control API is not available on all versions of ZXTM. Please
refer to your product specifications for details.
1.3 Code
samples
The following code samples demonstrate how to call the ZXTM Control
API from several different application environments. They are intended
to illustrate the similarities, rather than the best practice for each
language.
The examples connect to a ZXTM system, retrieve a list of the virtual
servers and then query whether each virtual server is enabled (i.e.
running). They then print out the running virtual servers.
The code structure is as follows:
Specify the location of the admin server, and the username and
password of an account in the `admin' group.
If necessary, configure the HTTPS layer to accept the Admin Server's
self signed certificate.
Instantiate a means of calling the SOAP methods, generally with
reference to the WSDL specification
1
.
Invoke the VirtualServer:getVirtualServerNames() method, which
returns an array of string values.
Invoke the VirtualServer:getEnabled() method, providing an array of
string values (the names) and obtaining an array of Boolean values.
Iterate through the arrays, printing the names of the virtual servers
which are enabled.
1
Some environments, such as Perl's SOAP::Lite do not validate method calls
against the WSDL specification.
19
New Page 1