Configuring 3D service provider

SuperMap iServer supports the following types of 3D providers:

• Configuring local 3D service provider
• Configuring REST 3D service provider
• Configuring MongoDB 3D service provider

Configuring local 3D service provider

Configure a local 3D service provider as illustrated below:

<!--  UGC 3D service provider-->
<provider class="com.supermap.services.providers.UGCRealspaceProvider" name="3DProvider">
        <config class="com.supermap.services.providers.UGCRealspaceProviderSetting">
                <workspacePath>../../samples/data/Realspace/RealspaceSample.sxwu</workspacePath>
                <xmlParse>false</xmlParse>
        </config>
</provider>

Where the class of <provider> identifies the implementation class of the UGC 3D service provider, the class of <config> identifies the UGCRealspaceProviderSetting, and the content of <config> is its corresponding configuring items:

<workspacePath> represents the path of the workspace used by the service provider. In addition, the workspace path supports reading from environment variables and system configuration files. It can be written as:

<workspacePath>${datapath1}/World.sxwu</workspacePath> 

Configuring REST 3D service provider

Configure a REST 3D service provider as illustrated below:

<!-- REST 3D service provider-->
<provider class="com.supermap.services.providers.RestRealspaceProvider" enabled="true" name="rest3DProvider-test">
        <config class="com.supermap.services.providers.RestRealspaceProviderSetting">
                <restServiceRootURL>http://localhost:8090/iserver/services/3D-sample/rest</restServiceRootURL>
                <restProviderCacheConfig>
                        <maxElementsInMemory>1</maxElementsInMemory>
                        <maxSizeOnDisk>2048</maxSizeOnDisk>
                        <timeToLiveSeconds>0</timeToLiveSeconds>
                        <timeToIdleSeconds>0</timeToIdleSeconds>
                </restProviderCacheConfig>
                <useCache>true</useCache>
        </config>
</provider>

Where the class of <provider> identifies the implementation class of the REST 3D service provider, the class of <config> identifies the RestRealspaceProviderSetting, and the content of <config> is its corresponding configuring items:

• <restServiceRootURL>: REST 3D service address, pointing at the root resource path, such as http://localhost:8090/iserver/services/realspace-sample/rest.
• <useCache>: Whether to use caches. Default is true. After opening the REST cache, the REST request to the resource will be cached locally. For the later same requests will be read directly in the cache.
• <restProviderCacheConfig>: The storage settings about the historical request cache of the provider in the memory, including
• <maxElementsInMemory>: The maximum of records in the memory. 0 denotes unlimited; 1 denotes not to use the cache of the memory. Default is 1. If not 1, then the request will be stored in the memory in precedence.
• <maxSizeOnDisk>: The maximum capacity of the disk. Unit is MB, and default is 2048MB.
• <timeToLiveSeconds>:Sets the upper limit for the survival of the cache, beginning at the creation of the record. The cache is automatically removed after the limit. Unit is second. Default is 0, denoting permanent survival.
• <timeToIdleSeconds>:Sets the upper limit for the idle time of the cache, beginning at the last visit. The cache is automatically removed after the limit. Unit is second. Default is 0, denoting permanent survival.
• <token>: When enabling the security mechanism, visiting the protected REST resource needs to provide Token .

Configuring MongoDB 3D service provider

Configure a MongoDB 3D service provider, as shown below:

<!-- MongoDB 3D service provider-->
<provider class="com.supermap.services.providers.MongoDBRealspaceProvider" enabled="true" name="mongoDB3DProvider-scene"> 
      <config class="com.supermap.services.providers.MongoDBRealspaceProviderSetting"> 
        <serverAdresses> 
          <string>192.168.120.47:27017</string> 
        </serverAdresses>  
        <database>smtiles</database>  
        <username>iserver</username>  
        <password>iserver</password>  
        <tilesetNames> 
          <string>1181328118</string> 
        </tilesetNames> 
      </config> 
</provider> 

Where the class identifies the implement class of MongoDB 3D service provider in <provider>. The class identifies the configuration class of MongoDB 3D service provider in<config>, namely, the MongoDBRealspaceProviderSetting, the contents in <config> are corresponding configuration items, including:

• <serverAdresses>：MongoDB service address.
• <tilesetNames>: Tile set array. If the parameter is null, publish all 3D tile sets in the MongoDB server.
• <database>：database which is used to store the map tiles, it's default name is smtiles
• <username>：user name who has the authority to access this database.
• <password>：password of this user.