Model 1: 1 Application Node, 1 Query Node/Build Node

Previous

Model 1 Architecture, Services, Ports

In Model 1, your application node is on a separate server from the query/ build node. The benefit of Model 1 over a single node is that by separating the nodes, your data can be secured on a different node than your application node. In addition, you can utilize your hardware to support more different tasks; one node for queries and builds, and one node for supporting the Sisense application.

The disadvantage of Model 1 compared to other models is that high availability is not supported and workloads for the application and query nodes cannot be scaled. If your query/ build node fails, the Sisense application will not be usable as the data models cannot be queried.

To learn how to implement this model in the Deployment Wizard, see Deploying Model 1.

Limitations

Components High Availability Load Distribution

App Node

No

No

Query Node

No

No

Build Node

No

No

Application Database

Yes

No

Services Mapping

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.

The table below describes the ports used for communication between the Sisense modules that need to be opened in a firewall to support this architecture.

Note: "N/A" means the ports are not relevant (internal process).

Service Type Service Ports Query/Build Application Directions
Infra Sisense.Oxygen 31112 Yes Yes Inbound
Sisense.Orchestrator 445, 137-139

N/A

N/A Inbound

Infra - Core

Sisense.Broker

5672,15672 ,25672,4369

 

  Inbound
Sisense.Discovery 2181,2888,3888  

 

Inbound

Sisense.Repository 27018

 

 

Inbound
Infra - Logs Sisense.Collector N/A Yes Yes N/A
Sisense.Shipper 5052 Yes Yes Outbound
Sisense.HouseKeeper N/A Yes Yes N/A
Infra - Connectors Sisense.CLRConnectorsContainer

8090,

8098

Yes   Inbound
Sisense.JVMConnectorsContainer

8095

9000-9010

Yes   Inbound
App - ECM Sisense.ECMServer 15000-15050 Yes   Inbound
Sisense.ECMLogs N/A Yes   Inbound
App - Elasticube Sisense.ECMS 811,812 Yes

 

Inbound
App IIS 14996 Yes

 

Inbound
Sisense.Galaxy 15000-15050   Yes Inbound
Sisense.Gateway 15000-15050   Yes Inbound
Sisense.Configuration 15000-15050 Yes Yes Inbound
Sisense.Identity 15000-15050   Yes Inbound
Sisense.Jobs N/A   Yes N/A
Sisense.Plugins 15000-15050 Yes   Inbound
Sisense.SPE 15000-15050 Yes   Inbound
Sisense.StorageManager 15000-15050 Yes   Inbound
Sisense.Usage N/A Yes   Inbound
Sisense.Pivot2 15000-15050 Yes

 

Inbound
Sisense.QueryProxy N/A Yes   Inbound

Deploying Model 1

Note: If you are expanding a single-node deployment to a multi-node deployment, see Expanding Single-Node Deployments to Multi-Node Deployments.

After you have installed the Multi-Node Deployment Wizard, you can log in with your Sisense credentials and begin configuring your nodes to implement a Model 1 deployment. In the Multi-Node Deployment Wizard, you define which servers act as build/query nodes and application nodes. The Multi-Node Deployment Wizard then configures the nodes for you.

In addition, you can define advanced settings for determining where to host the Sisense infrastructure, which includes the following components: 

To deploy Model 1:

  1. After installing the Deployment Wizard, in your High Availability Configuration directory, run SisenseHAWizard.exe. If you are setting up your deployment behind a firewall, see Offline Multi-Node Deployments.
  2. Enter your Sisense login credentials and click Sign In.
  3. If you are installing a multi-node deployment, select Install New Deployment, and click Next. If you are modifying an existing deployment, select Upgrade Existing Deployment and click Next. If you are upgrading, see Upgrading Multi-Node Deployments.
  4. Click Download Agent Installation to install the Sisense Agent. This agent must be installed on all the Sisense servers that are part of your deployment. It allows Sisense to communicate with each of the other machines in your deployment. To install the agent, right-click on the file and select Run with PowerShell. Click Next.
  5. Select the version of Sisense you are using. You can view your version of the Sisense Server by clicking in the top right corner of Sisense.

  6. Select Model 1 and click Next.
  7. In the Multi-Node Deployment Wizard, enter your Windows server credentials. These credentials will be used to connect to each of the servers in your environment, so the user name and password should be the same for each server and the user must have Admin privileges for each machine.
    Note: The password should not contain any special characters.
  8. In App, enter the IP address of your application server.
  9. In Query/Build, enter the IP address of your query/build server.
  10. (Optional) Click Advanced to configure the support the Sisense infrastructure.

    1. Select Long Index Edition to install the Long Index version of Sisense. Long Index determines how Sisense transforms your data when loading it in to an ElastiCube. For more information, see Long Index.
    2. In the Infra Configuration area, select additional servers to define where Sisense hosts additional copies of the Sisense Message Broker, Sisense configuration database, and Sisense application database.
    3. In the Application Database Configuration area, select Read Strategy to define the read preferences of each member of your application database's replica set. The default is primaryPrefered, which means that Sisense reads are sent to the primary, but if it is unavailable, the reads come from secondary members instead. If your application databases are geographically spread out, you may want to select Nearest where reads are performed on the nearest available node, disregarding if it is a primary or secondary member. The nearest node is determined by sending pings to all members and measuring the response time.
      OR
      Select Use External Application Database if you host your Sisense application database externally on a separate machine. In the Connection String area, create a replica set for supporting your application database. This ensures that each application database has the same metadata about ElastiCubes, dashboards, and filters. Modify the value of Connection String to:

      mongodb://AppUser:[email protected]:27018,XX.XX.XX.XX:27018,XX.XX.XX.XX:27018/?replicaSet=<replicasetname>&readPreference=primaryPreferred

      replacing ‘@localhost:27018/’ with the IP addresses of each of your nodes in the replica set separated by a comma and replacing <replicasetname> with the name of your replica set.

  11. Click Install. Sisense will automatically complete the setup of your Multi-Node environment. Close the Deployment Wizard once the setup is complete. After you have created your environment, the next step is to define how builds are distributed across all your servers.

Next Steps