Ports
Spotfire Server, the node manager, and related services reserve the following ports for various communication tasks.
Name | Default Port and Protocol | Function Description | Secure/Encrypted |
---|---|---|---|
Public HTTP port | 80/tcp, if enabled | Non-secure communication with installed clients and web clients. | No |
Public HTTPS port | 443/tcp, if enabled | Secure communication with installed clients and web clients. | Yes |
The HTTP connector port and the HTTPS connector port are configured independently and are exposed externally for client connection. You can use either of them or, in some cases, both.
Name | Default Port and Protocol | Function Description | Secure/Encrypted |
---|---|---|---|
Back-end registration port | 9080/tcp | Establishing trust between the Spotfire Server and nodes only. | No |
Back-end communication port | 9443/tcp | Monitoring secure traffic between nodes. (Spotfire Server monitors secure traffic from services on the nodes.) | Yes |
First clustering port | 5701/tcp | Secure communication within the environment. This port is the same for all servers in the cluster. | Yes |
Second clustering port | 5702/tcp | A second clustering port for secure communication within the environment. | Yes |
Third clustering port | 5703/tcp | A third clustering port for secure communication within the environment. | Yes |
Fourth clustering port | 5704/tcp | A fourth clustering port for secure communication within the environment. | Yes |
JMX RMI port | 1099/tcp, if enabled | If JMX RMI access is enabled, Spotfire Server opens a separate port for this purpose. Might be considered a "public-facing" port. | See config-jmx |
Name | Default Port and Protocol | Function Description | Secure/Encrypted |
---|---|---|---|
Registration port | 9080/tcp | Establishing trust between node managers and Spotfire Server. | No |
Communication port | 9443/tcp | Secure communication within the environment. | Yes |
Name | Default Port and Protocol | Function Description | Secure/Encrypted |
---|---|---|---|
Communication port (Spotfire Web Player/Spotfire Automation Services) | Next available general purpose 950<x>/tcp. (for example, 9501/tcp, or 9502/tcp, and so on, depending on the other services installed.) | Spotfire Web Player and Spotfire Automation Services for secure communication. | Yes |
Communication port (TERR) | Next available general purpose 950<x>/tcp. (for example, 9502/tcp, or 9503/tcp, and so on, depending on the other data function services installed.) | TERR service, for secure communication. This port assignment is needed internally on the computer that the service is running on, but is not needed on other computers. | Yes |
Communication port (Spotfire Service for Python) | Next available general purpose 950<x>/tcp. (for example, 9502/tcp, or 9503/tcp, and so on, depending on the other data function services installed.) | Spotfire Service for Python, for secure communication. This port assignment is needed internally on the computer that the service is running on, but is not needed on other computers. | Yes |
Communication Port (Spotfire Service for R) | Next available general purpose 950<x>/tcp. (for example, 9502/tcp, or 9503/tcp, and so on, depending on the other data function services installed.) | Spotfire Service for R, for secure communication. This port assignment is needed internally on the computer that the service is running on, but is not needed on other computers. | Yes |
Communication port (Information Services) | 9445 | Internal communication between Information Services and Spotfire Server. | Yes |
TERR engine ports | 61001/tcp -> 62000/tcp, if the TERR service is installed | Host-internal communication between the TERR service and the TERR engines. | No |
Spotfire Service for Python engine ports | 62001/tcp -> 63000/tcp, if the Spotfire Service for Python is installed | Host internal communication between the Spotfire Service for Python and the Python interpreter. | No |
Spotfire Service for R engine ports | 63001/tcp -> 64000/tcp, if the Spotfire Service for R is installed | Host internal communication between the Spotfire Service for R and the R engines. | No |
The back-end ports need exposed only for Spotfire Server connection to services available from the node manager.
Parent topic: Ports and Protocols
Related concepts
Related reference