Parameters for configuring data service provider |
SuperMap iServer supports the following types of data service providers:
Local data service provider encapsulates the data functionality from SuperMap workspaces.
Table 1. Configuration parameters of local data service provider
| Parameter name | Description | ||
General settings |
Service provider name | [Required parameter]
Uniquely identifies this service provider. The prefix of the default name is "ugcDataProvider-". |
|
Basic settings |
Workspace type | [Required parameter]
The types of workspaces are divided into file type and database type (SQL Server, Oracle workspace). The SQL Server workspace indicates the workspace is stored in the SQL Server database. The Oracle workspace indicates the workspace is stored in the Oracle database. |
|
| Workspace path | Remote file system | Required while the workspace is of the file
type. Please refer to Table
2 Parameter of database workspace information settings
if the database is of the database type. While the server
is not at local, select "Remote browse" to use files
on the server or local files uploaded to the server; while
the server is at local, select "Local browse" .
SuperMap workspaces (*.smwu, *.sxwu, *.smw, *.sxw) store the GIS data information. |
|
| Local file system | |||
| Workspace password | The password of the workspace. When there is no password for the workspace, you can have it blank or enter any characters. | ||
| Enable delay commit | Data edit operation supports delayed submission. When it's disabled, the current operation can take effect immediately. | ||
| Record detailed log | Whether to open the console error log. When this setting is turned on, the detailed error message will be displayed on the console panel. | ||
| Commit type | Set the submission method, including timing submission SPECIFICTIME and the interval submission INTERVALUPDATE. Timing submission means batch submission at specific time point. Interval submission means that a batch submission is made at regular intervals. | ||
| Max requests | Maximum number of requests. This parameter is valid only when the commit mode is INTERVALUPDATA. For example, the value is 1000, before reaching the specified time, if the number of data editing requests has reached 1000, the system will automatically submit these operations. | ||
| Interval(s) | Commit interval in seconds. For example, 300 means that data is updated every 300 seconds. This parameter is valid when the commit mode is IntervalUpdate. | ||
| Commit time | Time to submit. This parameter is valid when the commit mode is SpecificTime. | ||
| Commit period | Submit cycle. This parameter is valid when the commit mode is SpecificTime. | ||
| Select datasets to be published | When not enabled, it will publish all datasets; when enabled, it will publish the selected datasets. | ||
Advanced settings |
Datasource names |
The data service provider can use the data source and add more than one data source to the "existing project" list. When do not specify a data source name, the default is to use the all data source in workspace. | |
| Enable attachement service | When enabled, you can attach attachments for geographic features. Attachments can be pictures, documents, videos and any other format files. | ||
| Whether to record geographic feature meta information | When enabled, the system automatically records the meta information of the geographic feature, including the creator, the creation time, the last editor, the last edit time. If the current service is anonymous accessible, the creator and the last editor information are not logged. | ||
WFS data service provider encapsulates the data functionality from remote WFS services.
Table 2. Configuration parameters of WFS data service provider
| Parameter name | Description | |
General settings |
Service provider name | [Required parameter] Uniquely identifies this service provider. The prefix of the default name is "wfsDataProvider-". |
Basic settings |
WFS service root URL |
[Required parameter] Root directory address of remote WFS service. The SuperMap iServer now supports the remote WFS service of version 1.0.0 and 2.0.0 as a source. |
| User name | Authorized user name to access. Provided by the WFS map service publishing server. | |
| Password | Authorized user password. Provided by the WFS map service publishing server. | |
Advanced settings |
FeatureID converter class | The rules of conversion of feature ID are different for different WFS services implementation. When access to a WFS service, you need to provide a FeatureID converter for create the one-to-one mapping between the element ID of the WFS service ID and the integer. By default, the SuperMap iServer change the last number of WFS service feature ID into integer as the feature ID of the SuperMap iServer. User need to implement the FeatureIDMapping interface when define the conversion rules by self. |
REST data service provider encapsulates the GIS functionality from remote SuperMap iServer REST data services.
Table 3. Configuration parameters of REST data service provider
| Parameter name | Description | ||
| General settings | Service provider name | [Required parameter] Uniquely identifies this service provider. The prefix of the default name is "restDataProvider-". | |
| Basic settings | REST service root URL | [Required parameter] The root directory address of the remote SuperMap iServer map REST service, such as: http://supermapiserver:8090/iserver/services/data-world/rest . | |
| Advanced settings | Token/API-Key | When enabling the security mechanism, visiting the protected REST resource needs to provide Token or API-Key. | |
| HTTP referer | If the obtained Token is generated in HTTP Referer mode, you need to fill in the corresponding HTTP Referer. | ||
| Enable caching | Whether to use caches. Default is true. After opening the REST cache, the REST request to the resource will be cached locally. For the later same requests will be read directly in the cache. | ||
| Cache policy | Maximum capacity of disk | The maximum capacity of the disk. Unit is MB, and default is 2048MB. | |
| Survival time | Sets the upper limit for the survival of the cache, beginning at the creation of the record. The cache is automatically removed after the limit. Unit is second. Default is 0, denoting permanent survival. | ||
| Idle time | Sets the upper limit for the idle time of the cache, beginning at the last visit. The cache is automatically removed after the limit. Unit is second. Default is 0, denoting permanent survival. | ||
ArcGIS REST data service provider encapsulates the GIS functionality from remote ArcGIS REST feature services.
Table 4. Configuration parameters of ArcGIS REST feature service provider
| Parameter name | Description | |
| General settings | Service provider name | [Required parameter]
Uniquely identifies this service provider. The prefix of the default name is "arcgisRestDataProvider-". |
| Basic settings | ArcGIS REST element service URL | [Required parameter]
The root directory address of the remote ArcGIS REST element service. For example: http://localhost:6080/arcgis/rest/services/sample/FeatureServer. |
| Advanced settings | Token | When enabling the security mechanism, visiting the protected REST resource needs to provide Token. |
| HTTP referer | If the obtained Token is generated in HTTP Referer mode, you need to fill in the corresponding HTTP Referer. |
The data service provider with aggregation capabilities.
See: Configuration for Data Aggregation.
GeoPackage data service provider encapsulates the GIS related functions provided by GeoPackage data package (*.gpkg).
Table 5. Configuration parameters of GeoPackage data service provider
| Parameter name | Description | |
| General settings | Service provider name | [Required parameter] Uniquely identifies this service provider. The default name prefix is "geopkgDataProvider-". |
| Basic Settings | GeoPackage file directory | [Required parameter] GeoPackage file directory. |
Shape data service provider encapsulates the GIS related functions provided by Shape data file (*.shp). The related parameters are shown in the following table.
Table 6. Configuration parameters of Shape data service provider
| Parameter name | Description | |
| General settings | Service provider name | [Required parameter] Uniquely identifies this service provider, such as: "shapeDataProvider-". |
| Basic Settings | Shape directory | [Required parameter] The Shape data file path. |
| Shape file charset | [Required parameter]
The encoding format of the Shape file. |
PostGIS data service provider encapsulates the GIS related functions provided by PostGIS service. The related parameters are shown in the following table.
Table 7. Configuration parameters of PostGIS data service provider
| Parameter name | Description | |
| General settings | Service provider name | [Required parameter]
Uniquely identifies this service provider, such as: "postgisDataProvider-". |
| Basic Settings | Service address |
[Required parameter]
The address of the PostGIS server. |
Port |
[Required parameter]
The port number of the PostGIS server. |
|
Database |
[Required parameter]
The database used to store the data to be published. |
|
Username |
[Required parameter]
The name of the user who have the permission to access dababase. |
|
Password |
[Required parameter]
The password of the user. |
HBase data service provider encapsulates the GIS related functions provided by HBase service. The related parameters are shown in the following table.
Table 8. Configuration parameters of HBase data service provider
| Parameter name | Description | |
| General settings | Service provider name | [Required parameter]
Uniquely identifies this service provider, such as: "hbaseDataProvider-". |
Basic Settings |
DataCatalog |
[Required parameter]
The storage directory of Hbase data. |
Service address list |
[Required parameter]
zookeeper address, you can set multiple values, separated by commas. |