Network ports for Presentation Server
The following table lists the default configurations of protocols and ports for different services used by TrueSight Presentation Server.
Tip
Press F to view the table in full-screen mode.
Component | Service | Default port number | Protocol | Flow | Function | Default state | Port configurable |
---|---|---|---|---|---|---|---|
High Availability | |||||||
Cache Replication Port | HTTPS | 7800 | TCP | Inbound | Cache replication from primary to secondary TrueSight Presentation Server, used for high availability | Enabled | Yes |
Control Port | HTTPS | 8800 | TCP | Inbound | Communication between the primary and secondary TrueSight Presentation Server, used for high availability | Enabled | Yes |
Secondary Server Database Port | HTTPS | 5432 | TCP | Inbound | Communication between the PostgreSQL datastore and the secondary TrueSight Presentation Server core | Enabled | Yes |
Secondary Cache Replication Port | HTTPS | 7800 | TCP | Inbound | Cache replication from secondary to primary TrueSight Presentation Server, used for high availability | Enabled | Yes |
Secondary Control Port | HTTPS | 8800 | TCP | Inbound | Communication between the primary and secondary TrueSight Presentation Server, used for high availability | Enabled | Yes |
HTTP connector port | HTTP | (Windows) 80 | TCP | Inbound | HTTP communication between the primary and secondary TrueSight Presentation Server, used for high availability | Enabled | Yes |
HTTPS connector port | HTTPS | (Windows) 443 | TCP | Inbound | HTTPS communication between the primary and secondary TrueSight Presentation Server, used for high availability | Enabled | Yes |
Tomcat Apache server | |||||||
HTTP connector port | HTTP | (Windows) 80 (Linux) 8080 | TCP | Inbound | HTTP communication to the TrueSight Presentation Server from the TrueSight console or web services | Enabled | Yes |
HTTPS connector port | HTTPS | (Windows) 443 (Linux) 8043 | TCP | Inbound | HTTPS communication to the TrueSight Presentation Server from the TrueSight console or web services. Requirement for deploying packages through the TrueSight console The KM deployment feature through the TrueSight console uses the HTTPS connector port. Ensure this port is directly accessible from the Integration Service. | Enabled | Yes |
Elasticsearch | |||||||
Java/Node Client | HTTPS | 9300 | TCP | Inbound | Communication between the Elasticsearch datastore and the Presentation Server core | Enabled | Yes |
Cell Gateway | |||||||
Event Ingress (TrueSight Infrastructure Management) | HTTPS | 1900 | TCP | Inbound | Communication to the TrueSight Presentation Server gateway from Infrastructure Management | Enabled | Yes |
PostgreSQL | |||||||
PostgreSQL | HTTPS | 5432 | TCP | Inbound | Communication between the PostgreSQL datastore and the TrueSight Presentation Server core | Enabled | Yes |
Comments
Log in or register to comment.