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.

ModulePort #ProtocolDescription/Purpose
Web Server8081(*) HTTPSisense Web Server
Sisense.Orchestrator445, 137-139SMBUsed 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.Orchestrator22(*) SSHUsed 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 7077HTTPUsed 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.

ModulePort #ProtocolDescription/Purpose
ElastiCube Management Service, QueryServiceTcpPort812TCPIn high-availability, it's the Elasticube query end point
ElastiCube Management Service, QueryServiceHttpPort16162HTTPIn high-availability, it's the Elasticube query end point
ElastiCube Management Service, ManagementServiceTcpPort811TCPElasticube Management Service endpoint
ElastiCube Management Service, ManagementServiceHttpPort16161HTTPElasticube Management Service endpoint
Oxygen31112TCP
MongoDB27018(*) 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.

ModulePort #ProtocolDescription/Purpose
MontoriongMongoDB27019TCP
Sisense.CLRConnectorsContainer Server8090TCPCLR container server: Data transport between EC and data sources
Sisense.JVMConnectorsContainer ServerDynamically allocatedTCPJVM container server: Data transport between EC and data sources
Sisense.JVMConnectorsContainer Management8095TCPContainer management - e.g. Adding/Removing/Updating connectors
Sisense.Discovery2181TCPDiscovery service for connectors (Zookeeper)
CustomREST MongoDB27077(*) TCPIntermediate and cache db for CustomREST: connector results

(*) Indicates that the port is configurable.