Automatic Synchronization of Multi-node Services

With the rapid growth of GIS business and users, SuperMap iServer should not only support massive GIS services, but also support high concurrent access for thousands of users. To this end, iServer provides automatic synchronization of database-based multi-node service configuration information to enable the deployment of multiple iServers node, the service configuration information between nodes is automatically synchronized.

Application scenario

1. • When there are a large number of existing services in a single node, the new node needs to synchronize all services
   • Quickly and efficiently When there are a large number of nodes, the services among the nodes are exactly the same, and the incremental second-level synchronization is realized.
   • In the process of multi-node synchronization, the service is not interrupted and stopped, and the synchronization quality and timeliness

How to use

We recommend you to use the "shared data + shared configuration library" scheme to realize the synchronization of service data and configuration information among multiple nodes, and also realize the real-time synchronization of incremental services to improve the concurrency performance.

1. Shared Data : Refers to multiple Data that can be accessed and used by all iServer nodes. It is recommended that you store the data in a spatial database, NAS storage, or share directory.

Notice

If the data used is not shared data but local data (such as local file workspace), it is necessary to prepare the same data under the same directory of each node and set the shared configuration library to realize the automatic synchronization of services among multiple nodes.

2. Shared Configuration Library : A service configuration library shared by multiple iServer nodes, used to store configuration information for GIS services. IServer provides automatic synchronization capability of multi node service configuration information based on relational databases (PostgreSQL/Oracle), which can realize service configuration information changes, automatic and rapid perception between multiple nodes, and incremental second level synchronization.

On the "global settings-service storage setting" page, you can set the storage of the service configuration information to the same PostgreSQL or Oracle database (the corresponding storage table name, schema name, etc. Should also be consistent). For configuration details, please refer to Service Storage Setting .