Web Services and XML
Web Services are implemented using a SOAP remote procedure call interface.
The WebService module links together a WSDL document, a VTS Realm, and a set of project-defined VTS modules. This linkage allows VTS to accept SOAP messages directed at specific VTS Realms via the network and translate those messages into procedural requests for VTS applications. The results of these requests can then be compiled back into SOAP message format and returned to the network entities that made the requests.
Each VTS Realm can expose a single WSDL and connect it to a specific module within a single application. All VTS modules to be called via that Realm must be direct sub-modules of the connected module, so that the WebService functions can locate them.
Subsequent WSDL attachments to the same Realm will supersede existing attachments, not aggregate with them.
Once a Realm is attached to a WSDL it can start accepting SOAP messages immediately and will continue to accept them until the attachment is removed. The individual calls can accept up to 30 parameters each.
The parameters must be provided as defined by the WSDL and passed via the SOAP message. In the case that a complex type is sent as a parameter in the message, that parameter will be passed to the module as a representative VTS module tree generated by the XML API Classfactory feature (see the section: VTS Engine XML API).
Module and Parameter Naming