Port introduction |
SuperMap iServer uses some HTTP ports by default. When starting service, please make sure that these ports are not occupied and can pass through the firewall. Otherwise, some functions may not be available.
The default ports used by iServer are shown in the following table:
Port description | Port number |
Bind IP |
Set the method |
Enable the Tomcat service | 8090 |
0.0.0.0 |
Modify the Tomcat config file 【SuperMap iServer product directory】\conf\server.xml. For the modification method, please refer to Tomcat port |
Stop the Tomcat service | 8015 |
127.0.0.1 |
Modify the Tomcat config file 【SuperMap iServer product directory】\conf\server.xml. For the modification method, please refer to Tomcat port |
Licensing Services | 1947 |
0.0.0.0 |
Not modifiable |
Daemon at iServer startup, used to restart the iServer after a crash | Random port |
127.0.0.1 |
Not modifiable |
When multiple processes are enabled, interprocess communication | 8100 | 0.0.0.0 | Modify on the multi-process configuration page. For the modification method, please refer to " Configure to use multiple processes ". It can also be modified through the system config file ( iserver-system.xml ). |
Enable the process node when multiple processes are enabled | 8900-9000 | 0.0.0.0 | Modify on the multi-process configuration page. For the modification method, please refer to " Configure to use multiple processes ". It can also be modified through the system config file ( iserver-system.xml ). |
The RMI port served by each process when multiple processes are started | 8101-8199 | 0.0.0.0 | Modify on the multi-process configuration page. For the modification method, please refer to " Configure to use multiple processes ". It can also be modified through the system config file ( iserver-system.xml ). |
When multiple processes are enabled, temporary resource storage is used when HSQLDB storage is used | 10070 | 0.0.0.0 | After starting multiple processes, modify them on the global settings->repository setting page |
Spark is built into iServer and is used when tasks are submitted through Spark's REST API | 6066 | 0.0.0.0 | Not modifiable |
Spark is built in iServer, which is used to join cluster and submit tasks to the cluster | 7077 | 0.0.0.0 | Cannot be modified. If 7077 is occupied, iServer will try 7077 + 1 until 9999 |
Spark is built in the iServer and is used when accessing the Web UI of the master node | 8080 | 0.0.0.0 | Not modifiable |
Spark is built in the iServer and is used when accessing the Web UI of the worker node | 8081 | 0.0.0.0 | On the worker node, set the spark.worker.ui.port in the spark-defaults.conf. |
iServer built-in Spark, the port bound to the worker node | Random port | Native IP | On the worker node, set the environment variable: SPARK_WORKER_PORT. |
The port used by the Web UI of the Application when the spark cluster is running | 4040 | 0.0.0.0 | Set the spark.ui.port in the master node, spark-defaults.conf. |
iServer and distributed analyst service internal communication port | 6765 | 127.0.0.1 | Modify on the startup distributed analysis service pack |
Spark's driver listening port is used to communicate with executors and independent Master | Random port | Native IP | Set the spark.driver.port in the spark-defaults.conf. |
The blockManager module in the master and worker nodes of Spark listens to the port (see Note 1) | Random port | Native IP | Set the spark.blockManager.port in the master node, spark-defaults.conf. |
When the master node of spark cluster executes each distributed analysis task, it will bind two random ports and unbind them after the task is finished | Random port | 0.0.0.0 | Not modifiable |
Start the datastore service | 8020 | 0.0.0.0 | Set the server.port in 【iserver_datastore】\conf\application.properties. |
Default port for the enabled tile database (MongoDB) when using the datastore service | 27017 | 0.0.0.0 | Not modifiable |
The default port for the enabled relational database (PostgreSQL) when using the datastore service | 5432 | 0.0.0.0 | Not modifiable |
The default port (HTTP protocol, external communication port) of the enabled spatio-temporal database (Elasticsearch) when using the datastore service | 9200 | 0.0.0.0 | Not modifiable |
The default port (TCP protocol, internal communication port) of the enabled spatio-temporal database (Elasticsearch) when using the datastore service | 9300 | 0.0.0.0 | Not modifiable |
start geoprocessing server | 8097 | 127.0.0.1 | iserver-geoprocessing.xml in 【SuperMap iServer product directory】\webapps\iserver\WEB-INF directory. Set port in the file |
The processing automation services monitoring module is used to detect the status of the processing automation services | 18097 | 127.0.0.1 | iserver-geoprocessing.xml in 【SuperMap iServer product directory】\webapps\iserver\WEB-INF directory. Set socketListenPort in the file |
Stream processing modelWeb Socket client communication port | 8800 | 0.0.0.0, support configuration | Modify on the data flow services details page. If the port is occupied, iServer will try port number + 1 until an available port is obtained. In addition, you can set the port and bound ip in the iserver-dataflow.xml under [SuperMap iServer Directory]\webapps\iserver\WEB-INF directory. |
When processing automation services executes a model and submits a task in spark cluster cluster mode, it communicates with the cluster | 18098 | 127.0.0.1 | iserver-geoprocessing.xml in 【SuperMap iServer product directory】\webapps\iserver\WEB-INF directory. Set the clusterRPCPort in the file |
When processing automation services executes a Python tool, it communicates with a Python proces | 18099 | 127.0.0.1 | iserver-geoprocessing.xml in 【SuperMap iServer product directory】\webapps\iserver\WEB-INF directory. Set python SocketPort in the file |
Note
Tomcat uses 8090 and 8015 ports by default. If the two ports are occupied, the Tomcat service cannot be started/stopped normally. You can make modifications in the config file as needed.
If the default port of start service needs to be modified, please modify the Tomcat config file 【SuperMap iServer product directory】\conf\server.xml as follows:
<Connector port="8090" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8453"
executor="tomcatThreadPool"
enableLookups="false"
URIEncoding="utf-8"
compression="on"
compressionMinSize="2048"
compressableMimeType="text/html,text/xml,text/plain,text/javascript,application/xml,application/json,application/rjson"
/>
<Server port="8015" shutdown="SHUTDOWN">
The iServer provides a multi-process architecture based on microservices. By default, port 8100 is used to start the RMI service for inter-process communication, as well as ports 8900-9000 and 8101-8199 RMI used by each process. Please ensure that these ports are not occupied, otherwise the multi-process cannot be enabled normally.
Among them, the communication port and each sub-process port can be modified on the multi-process configuration page. For the modification method, please refer to " Configure to use multi-process ". It can also be modified through the system config file ( iserver-system.xml ).
SuperMap iServer provides the cluster technology to improve the service performance and enhance the stability of the server. After the server is clustered, the port of the parent node is used to provide services externally. Please ensure that the port used by the parent node of the cluster can pass through the firewall.
For the construction and use of the cluster, please refer to: Precautions for Construction of the Cluster .
If you use an enginetype data source, such as SQL Server, Oracle, etc., you also need to open the port required by the database.
In addition, when using iServer, it may also be used with other software, and the ports that may be called are shown in the following table:
Port description | Port number |
Web browsing port, used by HTTP service by default | 80 |
Web browsing port, used primarily for HTTPS services (provides encryption and an alternative to HTTP over a secure port) | 443 |
Default port for RabbitMQ messaging middleware | 5672 |
Enable default port for Tomcat service for SuperMap iPortal | 8192 |
In the whole GIS system, each node server (such as sub-nodes a and B) and database (such as database C) participating in the cluster have their own ports, and the external port is only the default port 8090 required for accessing the service, that is, the firewall only needs to open the port 8090.