Service instances introduction

Viewing service instance

A service instance is a specific service. In iServer Manger, you can configure all service instances on the Service/Service Instances page (See Logging in iServer Manager). A service instance corresponds to a GIS service. For the information about the access address for the GIS service, see Setting the service URI.

There are some details about the current default service instances listed on the service instance page, including service instance alias, service interface, service component (set), state, etc.

You can quickly create a service by clicking Quickly publish services on the Service/Service Instances page. For the specific process, see Quickly publishing GIS service.
You can easily control the state of each service to start or stop a service. You can start a current service instance by clicking Start. You can stop a current service instance by clicking Stop. The state column lists the state of each service instance. Green represents that the service instance is available while red represents not available.
If the data on the server are changed, you can update all of your service data by clicking Restart All Services.
But this operation will not change the original service state.
Control the service access. Authorize the access permission of service to the specified role, please refer to Specify access permissions for roles

In addition, you can view the configuration information of the service instance. Enter the service instance configuration page by clicking the service instance alias. This page shows the basic configuration information for the service instance that you selected, including the service instance name, service component (set), service interface, the use of this service instance, as well as service URI address.

Configuring service

Open iServer WebManager, click the Services and Service Management tabs. You will see all the instances on the current server. You can pause, start, delete, etc. the instances. You can also quickly create or restart all services. Click any service name, e.g. "map-changchun", and you can check more detailed info about that service and configure the management, e.g., basic info, service provider, service interfaces, caches, and security. The cache configuration can only be used for map services.

Basic info

Service Name: the name of the Service component.

Service Type: Including map service, data service, spatial analysis service, tranfer network analysis servcie, etc.

Service Address: the address to access the service, e.g. http://localhost:8090/iserver/services/map-changchun/rest. The address follows the form: http://<server>:<port>/iserver/services/<servicecomponent>/<serviceinterface>. Each address corresponds with a servcie interface bound with the current service component. For more info, check Service URI.

Map list: The list of all the maps in the map service.

Enable Editing: whether to enable the data editing option. Be aware that once the option is enable, your data source might be changed from user editing.

Service provider

You can check all the service providers and their info that are bound with the current map service. E.g. by ugcMapProvider-Changchun, you can check and sets its workspace type, path, password, and advanced settings.

Different types of services can only be bound to their corresponding service providers. E.g. map service can be bound to map service providers from GCMapProvider, RestMapProvider, CloudMapProvider, GDPMapProvider, SMTilesMapProvider, SVTilesMapProvider, WMSMapProvider, BingMapsMapProvider, etc. For details on the providers, see Service provider. The parameters for each provider may vary. For details, see Provider configuration parameters.

Service interface

You can check the interfaces that are bound or can be bound with the current service components. Different service components can bind with different interfaces. E.g. the map service component can bind interfaces like: rest, wms111, wms130, wmts100, wmts-china。

For details, refer to Component andinterface reference table.

Cache

It is used to configure the caches from map service and 3D service.

The types of map caches can be map tile, attribute tile, vector tile. Map tile can be any format from UGC, SMTiles, MBTiles, FastDFS, and MongoDB. Once the tile format is set, you need to specify the storage path for the caches. The map service will look for the caches in the specified path. If none is found, new caches will be generated and stored dynamically. For details, see Cache format.

For details on map caches, see Map cache.

3D service configuration is mainly used to set the directory of 3D service caches.

Security

Service security is administerd through Access control based on role. When the security module is enabled, the service authorization can be performed on the current page.

You can check and set the service authorization status. If the lock symbol is greyed, it means the service instance is accessible anonymously. If the symbol is blue, it means the service is accesible only when the login is valid.

Click the lock symbol or the "Authorize" button to check and modify the authorization. You can also authorize multiple instances in batch by using the Batch Authorize button.

There are two options for service authorization:

Anonymous Access: Any one can access the service. This is the default setting for all iServer samples.
Specified Access: Specify the users who can access the service by selecting their role. When this option is enable, the following three sub options are available:
Any login user can access: Any users that log in can access the current service.
Set the roles that can access: Specify the role of the users that can access. Only the users or user groups of this role can access the service. This option is only active when the "Anonymous Access" option is not checked.
Prohibited Roles: Specify the role of the users that are prohibited from accessing the service. .The users or user groups of this role cannot access the service.