# Sisense

This article outlines the integration with the Sisense connector, enabling streamlined metadata management through features such as crawling, report preview, and lineage building (Auto and Manual). It also ensures secure authentication via Credential Manager.

<figure><img src="https://1813356899-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhTnkoJQml0pok9awFDhx%2Fuploads%2Fr9fNtZorHtAclMSyRKv8%2Funknown.png?alt=media&#x26;token=44584137-68d7-4849-b873-f86e55814db5" alt=""><figcaption></figcaption></figure>

## Overview

### Connector Details

| Connector Category                                                          | Reporting Tools |
| --------------------------------------------------------------------------- | --------------- |
| Connector Version                                                           | Release7.2      |
| <p>Connectivity</p><p>\[How the connection is established with Sisense]</p> | REST APIs       |
| Verified Sisense Version                                                    | 7.4.3 - L2025.2 |

{% hint style="info" %}
The Sisense connector validates with the listed “Verified Sisense Version” and supports other compatible Sisense versions. If there are any issues with validation or metadata crawling, please submit a support ticket for investigation and feedback.
{% endhint %}

### Connector Features

| Feature                                      |                                                                 Availability                                                                 |
| -------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------: |
| Crawling                                     |                                                                       ✅                                                                      |
| Profiling                                    |                                                                      NA                                                                      |
| Query Sheet                                  |                                                                      NA                                                                      |
| Report Preview                               |                                                                       ✅                                                                      |
| Auto Lineage                                 | <p>✅<br>To learn more, click <a href="https://docs.ovaledge.com/connectors/data-lineage-extraction/sisense-lineage-extraction">here</a>.</p> |
| Manual Lineage                               |                                                                       ✅                                                                      |
| Secure Authentication via Credential Manager |                                                                       ✅                                                                      |
| Data Quality                                 |                                                                      NA                                                                      |
| DAM (Data Access Management)                 |                                                                      NA                                                                      |
| Bridge                                       |                                                                       ✅                                                                      |

{% hint style="info" %}
'NA' indicates that the respective feature is 'Not Applicable.'
{% endhint %}

### Metadata Mapping

The following objects are crawled from Sisense and mapped to the corresponding UI assets.

<table><thead><tr><th>Sisense Object</th><th width="163.6666259765625">Sisense Attribute</th><th width="179.3333740234375">OvalEdge Attribute</th><th width="176.3333740234375">OvalEdge Category</th><th width="149.3333740234375">OvalEdge Type</th></tr></thead><tbody><tr><td>Folders</td><td>Name</td><td>Report Group</td><td>Reports</td><td>Report Group</td></tr><tr><td>Folders</td><td>-</td><td>Report Group</td><td>Reports</td><td>-<br></td></tr><tr><td>Folders</td><td>-</td><td>Source Description</td><td>Descriptions</td><td>-<br></td></tr><tr><td>Sub Folders</td><td>Name</td><td>Report Group</td><td>Reports</td><td>Report Group</td></tr><tr><td>Sub Folders</td><td>-</td><td>Source Description</td><td>Descriptions</td><td>-<br></td></tr><tr><td>Dashboards</td><td>Title</td><td>Report</td><td>Reports</td><td>Report Name</td></tr><tr><td>Dashboards</td><td>Literal “Dashboard”</td><td>Report Type</td><td>Reports</td><td>Dashboard</td></tr><tr><td>Dashboards</td><td>-</td><td>Source Description</td><td>Descriptions</td><td>Source Description</td></tr><tr><td>Visuals/Widget</td><td>Title</td><td>Report Name</td><td>Reports</td><td>Report Name</td></tr><tr><td>Visuals/Widget</td><td>Type</td><td>Report Type</td><td>Reports</td><td>Bar Chart, Pie chart, etc.</td></tr><tr><td>Visuals/Widget</td><td>Description</td><td>Source Description</td><td>Descriptions</td><td>Source Description</td></tr></tbody></table>

## Set up a Connection

### Prerequisites

The prerequisites to establish a connection:

### **Whitelisting Ports**

Whitelist the inbound port to allow OvalEdge to connect to the Sisense Server.

{% hint style="warning" %}
When a port is configured, specify the updated port number during connection setup, whitelist the port, and establish proper communication between the system and the Sisense Server.
{% endhint %}

### Service Account User Permissions

{% hint style="warning" %}
It is recommended to use a separate service account to establish the connection to the data source, configured with the following minimum set of permissions.
{% endhint %}

{% hint style="info" %}
**👨‍💻 Who can provide these permissions?** The Sisense administrator grants these permissions, since users may not have sufficient access to assign them.
{% endhint %}

<table><thead><tr><th width="220.666748046875">Objects</th><th>Access Permission</th></tr></thead><tbody><tr><td>Connector Validation</td><td>Username and Password with REST API access</td></tr><tr><td>Crawling</td><td>Read access to Folders and Dashboards</td></tr><tr><td>Lineage</td><td>Read access to Datasets, Elasticubes, Connections, Dashboard Widgets</td></tr><tr><td>Dashboards</td><td>Viewer Access to Dashboards</td></tr><tr><td>Visuals Objects</td><td>Viewer Access to the Parent Dashboard</td></tr></tbody></table>

### Connection Configuration Steps

{% hint style="warning" %}
Users must have the Connector Creator role to configure a new connection.
{% endhint %}

1. Log into OvalEdge, go to Administration > Connectors, click + (**New Connector**), search for **Sisense**, and enter the required parameters.

{% hint style="info" %}
Fields marked with an asterisk (\*) are mandatory for establishing a connection.
{% endhint %}

<table><thead><tr><th width="220.6666259765625">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "Sisense" is displayed as the selected connector type.</td></tr><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selection.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp</li><li>Azure Key Vault</li></ul></td></tr><tr><td>License Add-On</td><td><p></p><p></p><ul><li>Select the Auto Lineage Add-On checkbox to automatically build data lineage.</li></ul></td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the Sisense connection              </p><p>(Example: "Sisense_Prod").</p></td></tr><tr><td>Connector Environment</td><td>Select the environment (Example: PROD, STG) configured for the connector.</td></tr><tr><td>Connector Description</td><td>Enter the description related to the connector.</td></tr><tr><td>Host Name*</td><td>Enter the Sisense server’s fully qualified domain name (FQDN) or IP address in the Host Name field.</td></tr><tr><td>Port</td><td>Enter the required port number to connect with the Sisense server.</td></tr><tr><td>Connection String* </td><td><p>Configure the connection string for the Sisense server:</p><ul><li>Automatic Mode: The system generates a connection string based on the provided credentials.</li><li>Manual Mode: Enter a valid connection string manually.</li></ul><p>Replace placeholders with actual server details:</p><ul><li>{server} refers to the Sisense host or IP address.</li><li>{port} refers to the Sisense service port</li></ul><p>Authentication Plugins:<br>http://{server}:{port}</p><p>This is the default connection string used for connecting to Sisense. </p></td></tr><tr><td>Username*  </td><td>Enter the Sisense Username</td></tr><tr><td>Password* </td><td>Enter the Password associated with the Sisense Username.</td></tr><tr><td>Proxy Enabled*</td><td>Select Yes to route the connection through a configured proxy, or No to connect directly without a proxy.</td></tr></tbody></table>

**Default Governance Roles**

<table data-header-hidden><thead><tr><th width="220.6666259765625"></th><th></th></tr></thead><tbody><tr><td>Default Governance Roles*</td><td>Select the appropriate users or teams for each governance role from the drop-down list. All users and teams configured in OvalEdge Security are displayed for selection.</td></tr></tbody></table>

**Admin Roles**

<table data-header-hidden><thead><tr><th width="220.6666259765625"></th><th></th></tr></thead><tbody><tr><td>Admin Roles*</td><td>Select one or more users from the dropdown list for Integration Admin and Security &#x26; Governance Admin. All users configured in OvalEdge Security are available for selection.</td></tr></tbody></table>

**No of Archive Objects**

<table data-header-hidden><thead><tr><th width="220.6666259765625"></th><th></th></tr></thead><tbody><tr><td>No Of Archive Objects*</td><td><p>This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive.</p><p>Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.</p></td></tr></tbody></table>

**Bridge**

<table data-header-hidden><thead><tr><th width="220.6666259765625"></th><th></th></tr></thead><tbody><tr><td>Select Bridge*</td><td><p>If applicable, select the bridge from the drop-down list.</p><p>The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering firewall rules.</p></td></tr></tbody></table>

2. After entering all connection details, the following actions can be performed:
   1. Click **Validate** to verify the connection.
   2. Click **Save** to store the connection for future use.
   3. Click **Save & Configure** to apply additional settings before saving.
3. The saved connection will appear on the Connectors home page.

## Manage Connector Operations

### Crawl

{% hint style="warning" %}
To perform crawl operations, users must be assigned the Integration Admin role.
{% endhint %}

The **Crawl/Profile** button allows users to select one or more schemas for crawling.&#x20;

1. Navigate to the **Connectors** page and click **Crawl/Profile**.
2. Select the schemas to crawl.
3. Click **Run** to collect metadata from the connected source and load it into the Data Catalog.
4. After a successful crawl, the information appears in the **Data Catalog > Report / Report Column** tab.

The **Schedule** checkbox allows automated crawling for a selected timeframe, from a minute to a year.

1. Click the **Schedule** checkbox to enable the **Select Period** drop-down.
2. Select a time period for the operation from the drop-down menu.
3. Click **Schedule** to initiate metadata collection from the connected source.
4. The system will automatically execute the crawl operation at the scheduled time.

### Other Operations

The Connectors page provides a centralized view of all configured connectors and their health status.

**Managing connectors includes:**

* **Connectors Health**: Displays the current status of each connector, with a **green** icon for active connections and a **red** icon for inactive connections, helping monitor connectivity to data sources.
* **Viewing**: Click the **Eye** icon next to the connector name to view connector details, including Reports, Report Columns, and Report Group.

**Nine Dots Menu Options:**

To view, edit, validate, build lineage, configure, or delete connectors, click on the Nine Dots menu.

* **Edit Connector**: Update and revalidate the data source.
* **Validate Connector**: Check the integrity of the connection.
* **Settings**: Modify connector settings.
  * **Crawler**: Configure data extraction.
  * **Access Instructions**: Add notes on how data can be accessed.
  * **Business Glossary Settings**: Manage term associations at the connector level.
  * **Lineage**: Select server dialects for parsing and setting connector priority for table lineage.
  * **Others**: Configure notification recipients for metadata changes.
* **Build Lineage**: Automatically build data lineage using source code parsing.
* **Delete Connector**: Remove a connector with confirmation.

### Connectivity Troubleshooting

If incorrect parameters are entered, error messages may appear. Ensure all inputs are accurate to resolve these issues. If issues persist, contact the assigned support team.

<table><thead><tr><th width="86.333251953125">S.No.</th><th width="214">Error Message(s)</th><th>Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>Error while validating SISENSE connection Could not establish connection, please check all the fields entered are correct and Valid. Error: sag: Temporary failure in name resolution</td><td><p>Error Description: The system could not validate the Sisense connection because the hostname could not be resolved. This occurred due to a temporary DNS or network lookup failure.</p><p>Resolution: Verify the Sisense server hostname, DNS configuration, and network connectivity. Retry after ensuring the domain resolves correctly and all connection fields are valid.</p><p><br></p></td></tr></tbody></table>

***

Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.