DTS Webservice Clients are implementations of the Java Client Library that are generated by the system upon request for a given Project and set of resources.
A Webservice Client is tasked with the following responsibilities (in addition to the ones of the base library):
•Provides access to the configured resources via SOAP or REST requests.
•Is packaged as an easily deployable Web ARchive (WAR).
•Is compatible with various Application Servers (e.g. Tomcat, JBoss, Wildfly, etc.)
•Encapsulates arguments and results of targeted routines to ensure they are callable using the configured protocol, but also translate to the native datasource being accessed.
•Provides SOAP/REST operations for creating, managing and consuming data streams.
•Uses standard data formats (XML/JSON) for inputs and outputs.
•Uses standard representations for complex objects (e.g. GeoJson for geometries).
•Can be multiplied and clustered for load balancing.
A Webservice Client must be deployed inside an Application Server. The deployment of the Application Server itself is irrelevant to the system as long as it has access to the Internal Communications Bus.
Multiple identical Webservice Clients can be deployed simultaneously and requests can be routed to them using 3rd party load balancing software, like Nginx.
The Webservice Client itself provides no external security features. To implement authentication, authorization or encryption on the resulting Webservices, an extra layer is required. A tool like Nginx is recommended for this as well.
For more information on the operations and usage of DTS Webservices, please see the dedicated section.