By default, some HTTP ports are used by SuperMap iPortal. When you start the service, please make sure that these ports are not occupied and can pass through the firewall. Otherwise, this may cause some features unavailable.
Port overview
The default ports used by iPortal include:
Port | Use | Can be modified or not? |
8190 | Start Tomcat service | Yes |
8115 | Stop Tomcat service | Yes |
1947 | License service | No |
8195 | The proxy service port when the service proxy is started | Yes |
8192 | The global search port when the built-in global search service is started | Yes |
8292 | The port used to receive saved messages from the collaborative backend | Yes |
38193 | Third-party database query service | Yes |
38194 | Collaboration port | Yes |
39200 | The HTTP protocol port of the built-in Elasticsearch when the built-in global search service is started | Yes |
39300 | The TCP protocol port of the built-in Elasticsearch when the built-in global search service is started | Yes |
Tomcat port
The build-in Tomcat in iPortal defaults to use 8190 to start service, and use 8115 port to shut down service. If these ports are occupied by other processes, the service cannot be started or stopped. At this point, you can modify them in the configuration file.
To modify the default port for starting the service, open configuration file located in [SuperMap iPortal directory]\conf\server.xml, as shown below:
- Service starting port: 8190
<Connector port="8190" 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"
/>
- Service stopping port: 8115
<Server port="8115" shutdown="SHUTDOWN">
Proxy service port
The service proxy function of iPortal takes 8195 as the proxy service port by default. The proxy GIS services will not be able to be accessed if the port is occupied. You can modify the configuration file [SuperMap iPortal directory]\webapps\iportal\WEB-INF\iportal.xml according to requirements.
...
<serviceProxy>
<enable>true</enable>
<enableBuiltinProxy>true</enableBuiltinProxy>
<port>8195</port>
<rootUrlPostfix>portalproxy</rootUrlPostfix>
<httpConnPoolInfo>
<maxTotal>100</maxTotal>
<defaultMaxPerRoute>10</defaultMaxPerRoute>
<connectionTimeout>30000</connectionTimeout>
<socketTimeout>30000</socketTimeout>
</httpConnPoolInfo>
...
</serviceProxy>
...
Global search port
By default, iPortal uses Elasticsearch as the global search engine. It takes port 8192 as the port of the global search service, and respectively takes ports 39200 and 39300 as the HTTP and TCP protocol communication ports of Elasticsearch. You can modify it in the global search configuration file as needed. See: Global Search Configuration.
Database port
If you use MySQL/Oracle/PostgreSQL database to store portal information,security information, and so on, you also need to open the port that the database requires. The default port for MySQL is: 3306; for Oracle, 1521; for PostgreSQL, 5432. For database configuration, please refer to Database configuration
RabbitMQ message server port
If you use server monitoring, you also need to open the RabbitMQ message server port. The default port is: 5672. You can modify in the configuration file rabbitmq-env.conf of RabbitQ according to requirements.
Collaboration port
If you want to start multiple instances of the iportal service on one machine, you need to set the IPORTAL_SUBSCRIBER-PORT and IPORTAL-COLLABORATION-PORT variables to different ports.
IPORTAL_SUBSCRIBER_PORT: The port used by iPortal to receive save messages from the collaborative backend.
IPORTAL-COLLABORATION PORT: The port used by the iportal collaborative service.
Disable Collaboration Services: When set to true, collaboration related services will not be started.