Domain Spatial Service Extension(DSSE) |
SuperMap iServer classifies spatial services into two categories: 1. Generic Spatial Services (GSS), e.g. map services, spatial data services, spatial analysis services, network analysis services, etc., and SuperMap iServer provides this type of services by default; 2. Domain Spatial Services (DSS), which are spatial information related services constructed by the user according to domain-specific professional logics.
SuperMap iServer provides a flexible mechanism for constructing and publishing services that applies to both GSS and DSS.
Server service framework is a three-layer architecture, that is, GIS service provider layer, GIS service component layer, and GIS service interface layer. For more details, please refer to Architecture. DSSE can be performed on any of the three layers.
Service providers in iServer indicates the sources GIS capabilities. By extending service providers, the sources of GIS capabilities can be expanded. For instance, a map service provider can be extended to read iServer 2008 map caches, therefore publishing map caches from iServer 2008 as different types of services, like REST services, WMS services, etc., in iServer. Also, a map service provider can be extended to realize the capability of getting GoogleMaps map services, therefore publishing map services from GooleMaps as different types of services, like REST services, WMS services, etc., in iServer.
Meanwhile, new types of service providers can be defined to realize capabilities for certain domains. Domain service providers can be combined and encapsulated on the component layer with other service providers as more coarse-weight module, realizing the integration of domain capabilities and GIS capabilities.
Please refer to Extension for Provider Layer.
The service component layer is resonsible for the combination and encapsulation of capabilities provided by service providers.
When the capabilities of the current service components cannot satisfy the needs, we can extend the existing service components to encapsulate more capabilities.
Meanwhile, the extension of the service component layer can be combined with the service interface layer extension. The newly extended service component can be published as Web service through the extended service interface, which is got from defining new resource in the JAX-RS mechanism, customizing new service interface, etc.
For instance, for the applications in the Meteorological field, to integrate weather forecast and weather alterting services into iServer, the service component layer needs to be extended accordingly.
Please refer to Extension for Component Layer.
The service interface layer is the layer for the display of capabilities. By extending service interfaces, the formats in which services are provided by iServer can be enriched (please refer to ), therefore better satisfying the needs of users.
Besides, by extending existing service interfaces, such as JaxrsServletForJersey and RestServlet, to customize new REST reource implementations, the capabilities of the domain components can better match the service interfaces.
Please refer to Extension for Interface Layer.
Besides, domain modules extended based on iServer can be integrated into iServer WebManager (Please refer to Integrating Domain Module into WebManager). Also, clusters can be built based on domain domain spatial services (please refer to Building DSS Cluster).
Other overall sample about domain service expansion please refer to：3 levels structure expansion overall sample.