Communication Ports

Sisense utilizes multiple communication ports. Some of the ports are used for communication between Sisense modules, and others are used for communication with remote locations.

When Sisense is installed as part of a Single machine deployment, ports used for communication between Sisense modules are considered internal ports, and do not need to be open in the firewall. When Sisense is installed in a Clustered deployment, where Sisense modules installed on different computers communicate with each other, ports used for communication between Sisense modules may need to be opened in the firewall. This depends on the specific deployment implemented in your environment.

The tables below lists the ports on which Sisense listens for communication.

Ports for External Communication

The following table list ports used for communication with external locations. These ports should be open on your firewall to allow for this communication.

Module Port Number Protocol Description
Web Server 8081(*) HTTP Sisense Web Server
Sisense.Orchestrator 445, 137-139 SMB

Used in high availability deployments. Otherwise, not used.

In high-availability, it copies DB farm to query nodes.

The Sisense Orchestrator Service generates inbound (query nodes) and outbound (build node) traffic.

Sisense.Orchestrator 22(*) SSH

Used in high availability deployments. Otherwise, not used.

In high-availability, it copies DB farm to query nodes.

The Sisense Orchestrator Service generates inbound (query nodes) and outbound (build node) traffic.

OAuth2 server

7077

In Sisense V6.7, port 7043 is also used.

HTTP

In Sisense V6.7, HTTPS is also used.

Used by GenericREST connectors that use oAuth authentication. Otherwise, not used.

(*) Indicates that the port is configurable.

Ports for Internal and External Communication

The following table lists all ports in which the type of communication, internal or external, depends on your deployment. In a single deployment, Sisense communicates internally to other services. These ports do not need to be open on your firewall. In a clustered deployment, Sisense communicates across your deployment to other Sisense services. These ports should be open on your firewall to allow for this communication.

Module Port Number Protocol Description
ElastiCube Management Service, QueryServiceTcpPort 812 TCP In high-availability, it's the ElastiCube query end point
ElastiCube Management Service, QueryServiceHttpPort 16162 HTTP In high-availability, it's the ElastiCube query end point
ElastiCube Management Service, ManagementServiceTcpPort 811 TCP Elasticube Management Service endpoint
ElastiCube Management Service, ManagementServiceHttpPort 16161 HTTP Elasticube Management Service endpoint
Oxygen 31112 TCP  
MongoDB 20718(*) TCP  

(*) Indicates that the port is configurable.

Ports for Internal Communication

The following table lists all ports on which Sisense communicates internally. These ports do not need to be open on your firewall.

Module Port Number Protocol Description
MontoriongMongoDB 27019 TCP  
Sisense.CLRConnectorsContainer Server 8090 TCP CLR container server: Data transport between EC and data sources
Sisense.JVMConnectorsContainer Server Dynamically allocated TCP JVM container server: Data transport between EC and data sources
Sisense.JVMConnectorsContainer Management 8095 TCP Container management - e.g. Adding/Removing/Updating connectors
Sisense.Discovery 2181 TCP Discovery service for connectors (Zookeeper)
Sisense WebServer (Node.JS) 40001 HTTP Webserver Note: This module is relevant fro, Sisense V6.7 onwards.
Sisense.WebQueryService (.Net) 40002 HTTP WebQueryService Note: This module is relevant fro, Sisense V6.7 onwards.
Streaming Processing Engine 40003 HTTP Processing Engine (Node.js)
CustomREST MongoDB 27077(*) TCP Intermediate and cache db for CustomREST: connector results
Sisense.ECMLogsPersistenceService 5672 and 27018 AMQP Reads build logs and saves them on the application database

(*) Indicates that the port is configurable.