Configuration Manager

You can use the Configuration Manager to configure and administer a variety of functionality and services in Sisense.

For example, you can use the Configuration Manager to perform the following tasks:

  • Configure SSL in your Sisense environment
  • Configure your application database for high availability
  • Define where log files are stored and how detailed your logs are

The Configuration Manager can be accessed from your browser at http://localhost:3030.

Below you can find descriptions of the fields that appear in the Configuration Manager and how they relate to tasks you can perform in Sisense. When relevant, links are provided to topics that provide a more in depth explanation of the field and the tasks you typically use the field for.

Web Server

The following fields are used to configure SSL for your Sisense environment. You should enable SSL if you have configured your web environment with SSL security (HTTPS) and certificates. This will enable HTTPS in the URLs of shared dashboards. For a complete explanation of these fields and their purpose, see Setting Up SSL for Sisense Windows.

  • Enable SSL: Toggle to enable/disable SSL.
  • Enforce TLS V1.2: Toggle to force traffic to Sisense through TLS 1.2.
  • Use X-Frame-Options: sameorigin header : Toggle to include the X-Frame Options header of the dashboard web page. For more information, see Allowed Domains for Embedded Dashboards.
  • CSRF Protection: Toggle to enable CSRF protection. See Cross-Site Request Forgery for more information.
  • Upload Certificate: Select the type of SSL certificate you are using.
  • SSL Certificate: Enter your SSL certificate.
  • SSL Key: Enter your SSL key.

Port: The port to be used when connecting to Sisense. The default value is 8081. For traffic over a secure connection, typically, this port is 443.

After setting a new port, restart the following services in Windows Services:

  • Sisense.Identity
  • Sisense.Galaxy
  • Sisense.ECMServer
  • Sisense.Gateway

Proxy URL: This field is used for implementing Base URLs. See Configuring Base URLs for more information.

Domain Binding: This field is used to allow external domains to access Sisense, for example, if you have implemented iFrames. You can add multiple domains separated by a comma and click Save to save your changes.

Build Node Server: When implementing a multi-node configuration, for example for high availability, you must define which node is your build node in the Configuration Manager. The address of the build node should be the server IP address and not the server name.

Application Database

The following fields are used to communicate with your Sisense application database. Typically, this is only necessary when implementing a high availability environment. For more information, see Multi-Node Deployments.

Connection String: The connection string contains all the necessary attributes for accessing the Sisense application database.

Encryption Key: The value of this field is the encryption key used by Sisense to encrypt your application database users. This value is used when you need to create users for your application database.

Logs

Sisense stores logs locally on your Sisense server. These logs are typically used by Sisense Support when troubleshooting any issues with your Sisense environment. You can define the location of these logs and the level of logging.

Path: The current path when Sisense stores logs. You can enter a new path for your logs on your Sisense server. The log path must contain / at the end of the path.

Level: Select the level of logging.

General

The following fields are used to communicate with your Sisense Configuration database and the Sisense Message Broker. Typically, this is only necessary when implementing a high availability environment. For more information, see Multi-Node Deployments.

ZooKeeper Connection String: The connection string to the configuration database. Click Test to verify the connection.

RabbitMQ Connection String: The connection string to the Sisense message broker. Click Test to verify the connection. See Replicating the Message Broker for more information.

Apply Strict Data Security on Filters: Controls whether or not to apply data security on collapsed filters that have a relationship to a restricted field. By default, data security is always applied. Data security will still be applied when the filter is expanded and for all widgets.

.r.