Configuration and Management of Service Instance

View Service Instance

A service instance is a specific service on the server. Open the service management server (see: Login Service Manager), and click "Service" and "Service Management" on the page, you can view the service instances on the current server and perform operations such as starting, stopping, deleting, and authorizing.

From this page you can:

To quickly create a service instance, click on "Quickly Create Service" on the page to enter the Service Quick Release Wizard. Please refer to the Quick Publish GIS Service for the specific process.
Conveniently control the status of each service, and can start or stop one or multiple service instances at any time. You can also delete one or more service instances. The status column provides the status of each service instance. The green icon indicates that the service instance is currently available, while the red icon indicates that the service instance is unavailable and waiting to be started.
Select to view a specific type of service through the drop-down boxes in the service interfaces column, the service component(set)s column, and the service status column.
When the server-side data changes, you can restart the service through "Restart All Services" to complete the data update in the service.
Control the service access and authorize the service access permission to the specified role. For details, see: Service Authorization

You can also view the configuration information for the service instance. Click the service instance alias you want to view to enter the service instance configuration information page. This page displays the basic configuration information of the service instance. Includes the service instance name, the used components (collection), the service interfaces used, whether the service instance is available, and the URI address.

Configuartion Service

Open the service management server, and click the "Services" and "Service Management" pages in turn to view the service instances on the current server, and pause, start and delete the service instances. You can quickly publish service or restart all services. Click the link of the service name, such as "map-changchun", to view more detailed information of the service or perform management configuration. Configurable items include: basic information, service providers, service interfaces, cache, and security. Where cache configuration is used only for map services.

Basic information

Service name: The name of the service components .

Service type: The service type divided according to the service component type. Include map services, data services, spatialanalyst service, transportation analyst service, traffic transfer analyst service, 3D service, service set, etc.

Service address: address of service access, such as http://localhost:8090/iserver/services/map-changchun/rest, structure is http://<server>:<port>/iserver/services/<servicecomponent>/<serviceinterface>, each service address corresponds to the service interfaces of the current service components binding. See the URI of the service for details.

Map list: All map lists in map services.

Enable editable: Data services whether to enable data editing, please be careful when enabling, because if editing is supported, the data source may be changed.

Service providers

In Service provider, you can view the service providers bound to the current map services and their related information. For example, for the bound UGC map provider ugcMapProvider-Changchun, You can view and set the workspace type, path, password, and advanced setting.

Different types of services can only be bound to corresponding service providers, for example, map services can be bound to map service providers. Specific options: UGCMapProvider, RestMapProvider, CloudMapProvider, GDPMapProvider, SMTilesMapProvider, SVTilesMapProvider, WMSMapProvider, BingMapsMapProvider, ect. For detailed description of provider type, please refer to Service Providers . The parameter settings for each service provider are also different. For the supported provider type and its detailed parameter settings, please refer to the Parameter Description of Service Providers Configuration .

Service interfaces

In service interfaces, you can view the bindable and bound interfaces of the current service components, and different service components have different bindable interfaces. For example, the service interfaces that can be bound to the map component are rest, wms111, wms130, wmts100, and wmts-china.

For the correspondence between service components and service interfaces, please refer to the Comparison Table of Service Components and Service Interfaces .

Cache

Cache configuration is used to configure caching for map services and 3D services.

The cache types supported by map services include map tiles, attribute tiles, and vector tiles, and map tiles include UGC, SMTiles, MBTiles, FastDFS and MongoDB format and storage types. When the tile format is selected, the storage location of the tile needs to be specified. The map services will find the tile in the specified location. If there is no tile or the contents are inconsistent, a new tile will be dynamically generated and stored. For a detailed introduction to the tile format and storage, please refer to: Tile Format . In addition, the cache of map services also supports setting read-only and cache survival time parameters.

For a detailed introduction to the map cache, please refer to: Map Cache .

The cache configuration of 3D service mainly refers to setting the 3D service cache directory.

Safe

The security of service is realized through Role-based Access Control . After the security module is enabled, the specific operation of service authorization can be performed on this page.

You can view and set the service authorization status. If the lock ID is gray, it means that the service instance can be accessed anonymously, that is, it is not locked. If the lock ID is blue, the service can be accessed only after login verification.

Click the lock ID or the "Authorize" button to view and modify the authorization information of this service instance. You can also select multiple service instances and click the "Batch Authorize" button.

The service author ization has two options:

Anonymously accessible, that is, accessible by any anonymous user. The demonstration services provided by SuperMap iServer are available to all anonymous users can access by default.
Specified users can access, that is, only the users associated with the specified role can access this service. Select the required role in the table to specify. In addition, there are three additional options when the service is only accessible to designated users:
Accessible by any logged in user: All logged in users can access the current service after checking.
Set the role that can access the service instance: This only works when the "Any Login User Can Access" button is not checked. It is used to bind the role to the service instance. Only the users and user groups associated with the role (mainly the users belonging to the user group) have access to the service
Prohibit access to role: if checked, the specified role will be prohibited from accessing the current service. The service authorization mechanism uses a forbidden priority policy, so as long as a role is in the forbidden access list, the associated user cannot access the service until the role is removed from the forbidden list.