A: There are possible reasons:(1) If iServer services crash when use large file caches on AIX, because the file cache is beyond the memory size that AIX system allows processes to use. On AIX, the data segment allowed processes to use limits the available memory size. The number of data segment is controlled by LDR CNTRL environment variables. If you set the process data segment number to 8, the memory size is: 8*256MB=2GB export LDR_CNTRL=MAXDATA=0x80000000(2) If it crashes when using a map ser…
08 July,2019 iServerA: In the iServer homepage, select service list>account name>tokens, and you can set the client type, and the token expiration date.
08 July,2019 iServerA: Gaia only recognizes the node and does not recognizes the node. The GetCapabilities of WMTS100 interface contains the node corresponding to 3857. So WMTS100 service can not opened in Gaia. To solve this problem, users should customize WMTS interface, and the scale set should be select the scale set corresponding to 4326: GlobalCRS84Scale, GlobalCRSPixel, GooleCRS84Quad and ChinaPublicServices. When the projection of data is 4326, it can select Custom.
08 July,2019 iServerA: Modify the time that iServer interacts with the database: in iserver-system.xml, add/modify the node check Datasource Connection Interval (Unit is second, defaults is 30 seconds). Then restart the iServer service.
08 July,2019 iServerA: If the CAS authentication server and the GIS server are not on the same machine, because of the time difference between the two machines, sometimes it would result in unsuccessful logon verification. In this case it is required to adjust the time of these two machines to the same, or enlarge the fault tolerance of time difference, of which the default value is 3 minutes in iServer(or iProtal, iExpress). The way to modify the tolerance of time difference is to edit shiro.ini (under WEB-INF) an…
08 July,2019 iServerA: (1) See it on the file name of the zip package; (2) Open home page of SuperMap iServer (http://localhost:8090/iserver), you will the version at the bottom of the page.
08 July,2019 iServerA: No, it is not necessary. You just need to modify the cached map in the pre-cached list, manually add 2 levels and click OK, then start the task.
08 July,2019 iServerA: To find the nearest position, using the method findNearest.
08 July,2019 iServerA: SuperMap iServer is deployed in Tomcat, and its initial heap size of Java VM is 256M, which is not enough for some services. To solve the problem, modify the Java VM memory size: open %SuperMap iServer Java_HOME%/bin/catalina.bat, find %_EXECJAVA%, append "-Xms1024m -Xmx1024m"(Set VM initial memory to 1024M), then restart SuperMap iServer.
08 July,2019 iDesktopA: When Supermap iServer is started as a Windows service, you need to configure the Java properties Diserver.home and -Diserver.output, and -Diserver.home to specify the startup directory of Supermap iServer. Also you need configure -Diserver.output to specify the output location of the cache tiles, which is relative to iserver.home. For example, if you deploy war of SuperMap iServer to Tomcat, and tomcat is running as Windows service, you need to add these two Java VM parameters. To ensur…
08 July,2019 iServerA: When SuperMap iServer is started in the form of Windows service, in Tomcat for instance, \Tomcat 6.0\webapps\iserver\WEB-INF\config\ log4j.properties file specifies where to place the log file: log 4j . appender.F.File=../logs/iserver.log. Therefore, the logs folder is placed in the parent directory of service startup file (cmd.exe). That is to say, the log file is placed in C:\Windows\logs\. In addition, you can modify the the log4j.properties file, and specify the path as an absolute path, …
08 July,2019 iServerA: In the configuration file of SuperMap iServer, the default URI where the cached picture access is the {IP} placeholder. And it is replaced automatically by server address when SuperMap iServer is started. If there are two or more network adapters, or there is virtualization software, the server will has multiple IPs. In this case, SuperMap iServer reads one of the IPs, and maybe is not expected. It is recommended that users use fixed IP and port when using custom cache URI.
08 July,2019 iServerA: If there are Chinese characters in the url, they must be encoded, e.g., varmapName= encode URI (“WorldMap_day”). An encoded url is varuri = " http :// 192 .168 .115 .68:8 090/ iserver / services/ maps/rest/maps/"+mapName+".json".
08 July,2019 iServerA: Upgrade SuperMap iServer to the latest version or configure Traffic network analysis service provider via XML file. Please reference to the help document: Start > Configuration and management > Configuration and managing GIS Services > Configuration for each layer of iServer architecture > Configuration for service provider layer > Configuring service providers through XML file > Configuring transportation analyst provider.
08 July,2019 iServerA: You can modify the parameter weightFieldName in TransportationAnalystParameter to the time cost of each route (You need set the map and time cost in the Supermap Desktop)
08 July,2019 iServerA: You can use POST request to simulate GET request, just add "_method=GET" to the requesting body.
04 July,2019 iServerA: This may be because of wrong URL of map service, or it was unable to connect. Please check whether the source service and URL are correct.
04 July,2019 iServerA: You can send the get request, and the request address is as follows: http: //IPaddress:8090 /iserver / manager/serverstatus/requests/statistics.json. Then take the token value and resolve the json result.
04 July,2019 iServerA: You can send the GET request through iServer REST API. The request address is: http://supermapiserver:8090/iserver/services/map-world/rest/maps/WorldMap/layers.rjson. The WorldMap is the map name. The sub-Layers is the sub-layer set information. You can refer to iServer help REST API>services>root>maps>map>layers for specific return result structure.
04 July,2019 iServerA: Please select Services Manager>Security>Security Configuration to configure in iServer homepage.
04 July,2019 iServer