Data Service Provider Configuration Parameter |
SuperMap iServer supports the following types of data service provider:
The UGC data provider encapsulates the data functionality from the SuperMap workspace.
Table 1 UGC Data Provider Configuration Parameter
| Parameter Name | Description | ||
|
Common Info |
Provider Name | 【Required】 Uniquely identifies the service provider. The default name prefix is "ugcData Provider-". |
|
|
Basic Setting |
Workspace Type | The workspace type is divided into file type and database type (SQL Server, Oracle, DM workspace). SQL Server Workspace means that the workspace is stored in a SQL Server database, and Oracle workspace means that the workspace is stored in Oracle database, DM workspace indicates that the workspace is saved in the DM database. | |
| Workspace Path | Remote server file system | When workspace is file type, it is required; when it is database type, please refer to workspace information of database type to set parameters . When the server is not local, select "Remote Browse" to use the files on the server or upload the local files to the server for use; when the server is local, select "Local Browse". SuperMap workspace (*.smwu, *.sxwu, *.smw, *.sxw ) stores information about the GIS data. |
|
| Local File System | |||
| Workspace Password | The password of the workspace used can be left blank or input any character when it does not exist. | ||
|
Choose Datasets to Publish |
Select the dataset to be published. If not checked, all the datasets will be published by default. If checked, the selected dataset will be published. |
||
|
Enable Delay Commit |
Data editing operation supports deferred submission, that is, the current operation can be deferred according to the setting. When not checked, the current operation can take effect immediately and the editing effect can be viewed. |
||
|
Enable Detailed Information Log |
Whether to open the console error log. When enabled, the detailed error message will be displayed on the console when an error occurs during an operation. |
||
|
Commit Type |
Set submission methods, including timed submission of SPECIFICTIME and intermittent submission of INTERVALUPDATE. Timed submission refers to batch submission at specific time points; Interval submission refers to batch submissions made at regular intervals. |
||
|
Max Requests |
max requests. Valid when commit type is interval commit. For example, set to 1000. If the number of data editing requests has reached 1000 before the specified time, the system will automatically submit these operations. |
||
|
Time Interval |
Commit time interval. The unit is seconds. Valid when commit type is interval commit. For example, 300 indicates that the data is updated every 300 seconds. |
||
|
Commit Time |
Commit time point. Valid when commit type is specific time commit. |
||
|
Commit Period |
Commit period. Valid when commit type is specific time commit. |
||
| Choose Datasets to Publish |
Publish all data sets when not enabled. Publish selected data sets by data source after enabling. If no data set is selected for a data source, all data sets in the data source will be published |
||
| Whether to Enable Dataset Verification | After it is enabled, if the data set specified for publication is not compliant (for example, the data source does not contain a data set, the data set under the data source does not contain a spatial table, and the data set name specified by the user does not exist), the data verification fails. | ||
|
Datasource Names |
The data sources that data service provider can use. After selecting a workspace, click the "Automatically retrieve relevant settings from workspace" link, and all data sources under that workspace will be listed in the "Used Data Source Name List". Multiple data sources can be added to the "Existing Projects" list. When no data source name is specified, all data sources in the workspace are used by default. | ||
| Enable Attachment Service | When enabled, you can associate attachments for geographic features. Attachments can be pictures, documents, videos and other files in any format. | ||
| Whether to Record Geographic | After enabling, the system will automatically record the meta information of geographic features, including creator, creation time, last editor, and last editing time. If the current service is anonymously accessible, creator and last editor information is not recorded. |
||
WFS data service provider encapsulate data functionality from a remote WFS service.
Table 2 Configuration Parameters of WFS Data Service Provider
| Parameter Name | Description | |
|
Common Info |
Provider Name | 【Required】 Unique identification of the service provider. The default name prefix is "wfsDataProvider- ". |
|
Basic Setting |
Root directory URL of WFS service |
【Required】 Remote WFS service root directory address. SuperMap iServer currently supports remote WFS services as sources in versions 1.0.0 and 2.0.0. |
| User Name | The user name authorized for access. Provided by the server that publishes WFS services. | |
| Access Password | Authorize the user with the corresponding password. Provided by the server that publishes WFS services. | |
|
Advanced Setting |
Feature ID Converter Class Name | The conversion rules for element IDs vary depending on the implementation of different WFS services. Therefore, when accessing a WFS service, a featureID converter is required to establish a one-to-one mapping between the element IDs of the WFS service and integers. SuperMap iServer defaults to converting the last digit of the WFS service element ID to an integer as the element ID value. When customizing conversion rules, it is necessary to implement the FeatureIDMapping interface. |
The REST data service provider encapsulates the GIS functionality obtained from the remote SuperMap iServer data REST service.
Table 3 REST Data Service Provider Parameter
| Parameter Name | Description | ||
| Common Info | Provider Name | 【Required】 Unique identification of the service provider. The default name prefix is "restDataProvider-". |
|
| Basic Setting | Root directory URL of REST service | 【Required】 The root directory address of the remote SuperMap iServer data REST service. For example: http://supermapiserver:8090/iserver/services/data -world/rest. |
|
| Advanced Setting | Token or API-Key | When security mechanisms are enabled, accessing protected REST resources requires providing a Token or API-Key. | |
| HTTP referer | If the obtained token is generated in the form of an HTTP Referer, the corresponding HTTP Referer needs to be filled in. | ||
| Enable Cache | Whether to use cache. The default is true. After enabling caching, REST requests for resources will be cached locally, and the next time the same request is received, it will be read directly from the cache without the need to send it to the server again. | ||
| Cache Policy | Max Disk Capacity | The maximum capacity of the disk. The unit is MB, and the default size is 2048MB. | |
| Survival Time | Set the upper limit of cache survival time, and the cache will be automatically cleared after timeout. Starting from the creation of the record, the unit is seconds and defaults to 0, indicating that the cache is permanently alive. | ||
| Idle Time | Set a maximum time limit for cache idle, and the cache will be automatically cleared after timeout. Calculated from the last access, in seconds, default to 0, representing cache permanently alive. | ||
ArcGIS REST data service provider encapsulate the GIS functionality obtained from remote ArcGIS REST feature services.
Table 4 ArcGIS REST Data Service Provider Parameter
| Parameter Name | Description | |
| Common Info | Provider Name | 【Required】 Unique identification of the service provider. The default name prefix is "arcgisRestDataProvider-". |
| Basic Setting | Root directory URL of ArcGIS REST | 【Required】 The root directory address of the remote ArcGIS REST feature service. For example: http://localhost:6080/arcgis/rest/services/sample/FeatureServer . |
| Advanced Setting | Token | When security mechanisms are enabled, accessing protected REST resources requires providing a Token or API-Key. |
| HTTP referer | If the obtained token is generated in the form of an HTTP Referer, the corresponding HTTP Referer needs to be filled in. |
Aggregation-capable data service provider.
See: Configuration of Data Function Aggregation.
The GeoPackage data service provider encapsulates the GIS functionality provided by the GeoPackage data package (*.gpkg), with the relevant parameters shown in the table below.
Table 5 GeoPackage Data Service Provider Parameter
| Parameter name | Description | |
| common info | provider name | 【Required】 Uniquely identifies the service provider. The default name prefix is "geopkgDataProvider-". |
| basic setting | GeoPackage file directory | 【Required】 GeoPackage file directory. |
The Shapefile data service provider encapsulates the GIS functionality provided by Shapefile data files (*. shp), with the relevant parameters shown in the table below.
Table 6 Shapefile Data Service Pprovider Parameter
| Parameter Name | Description | |
| common info | provider name | 【Required】 Uniquely identifies the service provider. For example, "shapefileData-". |
| Basic Setting | Shapefile file directory | 【Required】 Shapefile data file directory. |
| Shapefile file encoding | 【Required】 Sets the encoding format for the Shapefile file. |
PostGIS data service provider encapsulate the GIS functions provided by the PostGIS service, and the relevant parameters are shown in the following table.
Table 7 PostGIS Data Service Provider Parameter
| Parameter Name | Description | |
| common info | provider name | 【Required】 Uniquely identifies the service provider. For example, "postgisDataProvider-". |
| Basic Setting |
Service Address |
【Required】 PostGIS service address. |
|
Port |
【Required】 The service port number of PostGIS. |
|
|
Database |
【Required】 A database used to store data to be published. |
|
|
User name |
【Required】 Users who have access to the database. |
|
|
Password |
【Required】 The password for this user. |
|
|
Choose Datasets to Publish |
Select the dataset to be published. If not checked, all the datasets will be published by default. If checked, the selected dataset will be published. | |
| Whether to Enable Dataset Verification | After it is enabled, if the data set specified for publication is not compliant (for example, the dataset is null, the dataset name is incorrect, etc.), the data verification fails. |
The blockchain data provider encapsulates the GIS functions provided by the blockchain service, and the relevant parameters are shown in the following table.
Table 9 Blockchain Data Provider Parameter
| Parameter Name | Description | |
|
Common Info |
Provider Name | 【Required】 Uniquely identifies the service provider. For example, "BlockchainData Provider-". |
| Basic Setting | Config File | 【Required】 Blockchain the network.yamlconfig file storage directory. |
| Datasource Alias | 【Required】 The user names the alias of the blockchain data source, such as "BlockchainData". |
|
| Editable | Unchecked by default | |
| Enable Delay Commit | Unchecked by default | |
| Modifyusers | The default is blank, providing the iServer user name for editing permission |