Default Ports Used by the Denodo Platform Modules¶
The table below lists the TCP/IP ports that each module of the Denodo Platform listens for incoming connections.
Consider this:
These ports need to be free (not used by other applications).
If the Denodo Platform is behind a firewall, open the appropriate ports (see the list below the table).
These are the default port numbers. They can be changed during the installation process or later, in the administration tool of each module.
Server |
Default Port |
|---|---|
Virtual DataPort and ITPilot Wrapper Server |
|
Server ports (for Virtual DataPort administration tools and JDBC clients) |
9999 |
ODBC port |
9996 |
Monitoring ports (JMX) |
Primary port: 9997 (the JMX connection is established with this port) Secondary port: 9995 |
Shutdown port (only reachable from localhost) |
9998 |
ITPilot Browser Pool |
|
Server ports |
6001 and 6003 |
Shutdown port (only reachable from localhost) |
6002 |
Initial Microsoft Internet Explorer browser port |
6100 The Browser Pool listens to this port to communicate with the first opened browser. The consecutive ascending port numbers will be used when additional browsers are requested. For example, if the size of the Browser Pool is set to 30, the Browser Pool will listen in the port range from 6001 to 6030. |
ITPilot Verification Server |
|
Server ports |
7001 and 7003 |
Shutdown port (only reachable from localhost) |
7002 |
ITPilot PDF Conversion Server |
|
Server port |
8448 |
Scheduler Server |
|
Server ports |
8000 and 7998 |
Shutdown port (only reachable from localhost) |
7999 |
Scheduler Index Server |
|
Server ports |
9000 and 8998 |
Shutdown port (only reachable from localhost) |
8999 |
Denodo Platform Web container (Scheduler and ITPilot Administration Tools, Virtual DataPort Web services, Data Catalog and Diagnostic & Monitoring Tool) |
|
Web container port |
9090 for HTTP connections 9443 for HTTPS connections |
Shutdown port (only reachable from localhost) |
9099 |
Monitoring ports (JMX) |
9098 and 9097 |
Several components of Denodo use two ports to listen to connections. Both are necessary and if the server is behind a firewall, both need to be opened in the firewall so the client applications can successfully connect to both.
The monitoring interface of the Denodo components uses JMX. This Java technology uses the JRMP protocol, which opens an ephemeral port for internal use. This port cannot be disabled but if a client tries to connect to it from a another computer, the connection will be rejected.
Ports to Open on a Firewall
If the Denodo Platform runs behind a firewall, open the following ports in the firewall. If the Denodo Platform runs on Windows, remember to open the ports on the Windows Firewall as well.
9999: to allow connections from JDBC clients and the Administration Tool of Virtual DataPort. The developers can use the Design Studio to create views in Denodo instead of using the Administration Tool. In that case, they only need access to the ports 9090 and/or 9443, and not to 9999.
9996: to allow connections from ODBC clients of Virtual DataPort.
9997 and 9995 to allow connections to the monitoring interface of Virtual DataPort (JMX). This is necessary so the Diagnostic & Monitoring Tool of the Solution Manager can connect and also for JMX clients like Oracle Java Mission Control or JVisualVM.
9090: to allow HTTP connections from client applications/browsers to the web applications and web services.
9443: to allow HTTPS connections from client applications/browsers to the web applications and web services. HTTPS is disabled by default but we strongly suggest enabling it and using it instead of HTTP.
7998 and 8000: to allow connections to the Denodo Scheduler server (for example from the Solution Manager Administration Tool or Solution Manager server running in another machine).
In addition, you may consider opening the following ones:
9098 and 9097: to monitor - from another computer - the web container of Denodo.