Windows Port Settings
  • 29 Mar 2022
  • 2 Minutes to read
  • Dark
    Light

Windows Port Settings

  • Dark
    Light

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 server deployment, ports used for communication between Sisense modules are considered internal ports. They must be available for the application to use, but do not need to be open in the external network firewall. When Sisense is installed in a Multi-Node 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.

Note :

Sisense uses the WebSocket protocol for communication between services.

Open Ports

To allow your users to access Sisense, your firewall must allow inbound traffic to your web application port.

The web application port can be one of the following:

  • 8081 : Default Sisense web application port
  • 443 : Default port for secure communication
  • A custom web application port. For information on defining a custom web application port, see the description of the Port field in the Configuration Manager.

Communication Ports

The table below lists the ports on which Sisense listens for communication in a single server deployment. For a Multi-Node deployment, see Communication Ports for Multi-Node Deployments.

ServiceDescriptionProtocol Ports/RangeDirectionProcess Name
Sisense.Oxygen Product licensing managementHTTP31112InboundSisense.Oxygen.exe
HTTP443Outbound
Product tracking managementHTTP443Outbound
Sisense.Orchestrator ElastiCube distributionSMB445, 137-139InboundSisense.Service.exe
Build/Attach/Detach ElastiCube commandsTCP811, 812Outbound
Sisense.Broker

Message Bus (RabbitMQ)

  • Interprocess communication
  • Pulse notifications
  • Build Logs
AMQPDefault: 5672, 15672TLS: 5671,15671
Dist: 25672Discovery (ERL): 4369
Inbound

Sisense.AlertingMQ.exe

epmd.exe

erl.exe

Sisense.DiscoveryConfiguration storage and service discovery managementTCP2181, 2888, 3888InboundSisense.Discovery.exe
Sisense.RepositoryApplication metadata databaseTCP27018InboundRepository.Service.exe
Sisense.Collector

Monitoring Files Manager

  • Collects data about the machine, for example, hard drive, cores number, RAM size, etc.
  • Collects data about processes performances CPU usage, Memory consumption , etc.
  • Deletes old monitoring files
  • Writes data to C:\ProgramData\Sisense\Monitoring\logs
N/AN/AN/A Sisense.Collector.exe
Sisense.Shipper

Monitoring Files Sender

  • Reads C:\ProgramData\Sisense\Monitoring\logs folder and ships it to Sisense logging service
  • Reads IIS logs and ships it to Sisense logging service
  • Truncates long logs
  • Encrypts sensitive fields
TCP5052Outbound

Sisense.Shipper.exe

External Address:

listener.logz.io

Sisense.HouseKeeperApplication monitoring services watchdogN/AN/AN/ASisense.HouseKeeper.exe
Sisense.CLRConnectorsContainerSisense Connectors framework (.NET)TCP8090, 8098InboundSisense.JVMConnectorsContainer.exe
Sisense.JVMConnectorsContainerSisense Connectors framework (JAVA)TCP8095, 9000-9010InboundSisense.Connectors.Container.exe
Sisense.ECMServer

ECM 2.0 API Server:

  • ElastiCubes management
  • Schema management
  • Builds management
HTTP15000-15050InboundSisense.Service.exe
Sisense.ECMLogs

ECM 2.0 Build Logs Service:

  • Builds messages and status channel
  • Build messages and status persistent
HTTP15000-15050InboundECMLogsPersistenceService.exe
Sisense.ECMS

Elasticube Managment Services:

  • Query pipeline to MonetDB
TCP811, 812Inbound ElastiCube.ManagementService.exe
IIS

Backend Services APIs:

  • ElastiCube metadata
  • Query (JAQL) endpoint
  • Query translation
  • Pivot 1.0 generator (query+UI)
  • CSV export
  • Data Security
  • ACL's
HTTP14996, 15000-15050Inboundw3wp.exe
Sisense.Galaxy Application general APIs serviceHTTP15000-15050InboundSisense.Service.exe
Sisense.Gateway

Main entry point and API router:

  • APIs discovery
  • APIs internal load balancer and routing
  • SSL termination
  • Protocols translation (HTTP/AMQP/Websockets)
  • Static assets handler (JS/CSS/HTML/IMG)
HTTP8081Inbound
Sisense.ConfigurationConfiguration Manager API Service and API server for system settings and configurationHTTP15000-15050Inbound
Sisense.Identity

Identity APIs and Management:

  • SSO
  • Login
  • Users
  • Roles
  • Groups
HTTP15000-15050Inbound
Sisense.Jobs

Jobs trigger and scheduler

  • Email reporting
  • Maintenance/migrations
N/AN/AN/A
Sisense.Plugins

Client side plugins manager:

  • Plugins administration
  • Plugins serving
HTTP15000-15050Inbound
Sisense.SPE

Data streaming engine:

  • Export to Excel
  • Table preview
HTTP15000-15050Inbound
Sisense.StorageManager

Sisense files uploader/manager

  • Upload Excel/CSV
HTTP15000-15050Inbound
Sisense.Usage

Usage analytics service

  • Usage data collection
  • Usage data file management/rotation
HTTP15000-15050Inbound
Sisense.Pivot2Pivot 2.0 serviceHTTP15000-15050Inbound
Sisense.QueryProxyIIS Proxy service
Internal proxy to IIS APIs
N/AN/AInbound 
Note:

When trying to add an ElastiCube server to a web server, Sisense pings the web server. If it cannot successfully ping the server, the error message "The Elasticube server is not reachable" is returned. Make sure that ICMP communication is enabled on the web server.

The table above describes the communication ports in a single server environment. If you have a Multi-Node deployment, see Communication Ports for Multi-Node Deployments.


Was this article helpful?