Publish the blockchain service

Feedback


SuperMap iServer supports the direct publishing of blockchain service as a data source to data services, data history service, and map services, such as REST data services、REST map services.

Publish data stored in the blockchain network

You can publish the data stored in the service blockchain network as data services, data history service, and map services through the following steps:

  1. Click "publish service" on the "service management homepage" or click "quickly publish service" on the "service-service management" page to enter the publishing wizard;
  2. The selected data source is "blockchain service", and click "Next";
  3. For information about configuartion service data, click "Next":
  1. Select the published service type, such as rest data service, and click Next.
  1. Configure the corresponding service according to the selected service type, and click Publish to complete the publishing process;
    1. After publishing, you can see the name and link of the currently published service. Click it to access the service directly.

    Note 1: Before selecting the. yaml configuration file, it is necessary to check whether there are IPFS and PostGIS instructions in the configuration file. If not, the IP and port of the IPFS network node, PostGIS domain name, and other information need to be inserted at the end of the. yaml file. The example is as follows.

    ipfs:

    address:

    192.168.11.86

    port:

    5001

    cacheserver:

    # postgis connection fixed ID: domain name: port: database name: username: password (separated by:)

    postgis:postgis.orga.example.com:5432:blockchain:postgres:supermap

    Note 2: When publishing services, it is necessary to add the IP and domain names of the machines where each node in the blockchain network is located to the hosts file of the machine where the iServer service is located. An example is shown below.

    # server1

    192.168.11.86 orderer0.example.com

    192.168.11.86 peer0.orga.example.com

    192.168.11.86 couchdb.orga.example.com

    192.168.11.86 ca.orga.example.com