> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/connectors/connector-repositories/reporting-tool/microstrategy.md).

# MicroStrategy

The MicroStrategy connector integrates MicroStrategy with OvalEdge to enable metadata management through crawling, report preview, and lineage building (automatic and manual). It crawls metadata from MicroStrategy projects, reports, dossiers, documents, pages, and visualizations, and maps these objects to the corresponding OvalEdge assets for governance and lineage analysis.

The connector connects to MicroStrategy using REST APIs and JDBC. REST APIs retrieve metadata from the MicroStrategy Library, while JDBC provides access to the MicroStrategy Metadata Repository for object definitions and dependencies. An optional Intelligence Server connection through MSTR.jar extracts metric formulas and SQL from reports, cubes, and dossiers to support complete lineage generation. Authentication uses MicroStrategy user credentials for REST API access and Metadata Repository database credentials for JDBC connectivity.

<img src="/files/VjEI1vYqphbxv1GWQDnd" alt="" height="329" width="624">

## Overview

### Connector Details

| Connector Category                                                                | Reporting Tools                             |
| --------------------------------------------------------------------------------- | ------------------------------------------- |
| OvalEdge Release Supported                                                        | Release7.2.x and later                      |
| <p>Connectivity</p><p>\[How the connection is established with MicroStrategy]</p> | REST APIs and JDBC                          |
| Verified MicroStrategy Version                                                    | MicroStrategy 10.11 and later (on-premises) |

{% hint style="info" %}
The MicroStrategy connector validates with the listed “Verified MicroStrategy Version” and supports other compatible MicroStrategy 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                                 |       ✅      |
| Manual Lineage                               |       ✅      |
| Secure Authentication via Credential Manager |       ✅      |
| Data Quality                                 |       ❌      |
| DAM (Data Access Management)                 |       ❌      |
| Bridge                                       |       ✅      |

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

### Metadata Mapping

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

| MicroStrategy Object | MicroStrategy Attribute | OvalEdge Attribute | OvalEdge Category | OvalEdge Type      |
| -------------------- | ----------------------- | ------------------ | ----------------- | ------------------ |
| Project              | Name of the Project     | Report Group       | Report Group      | Report Group       |
| Report               | name                    | Report             | Report            | Report Name        |
| Report               | Type                    | Report Type        | Report            | Report             |
| Report               | description             | Source Description | Report            | Source Description |
| Dossier              | name                    | Report             | Report            | Dossier Name       |
| Dossier              | Type                    | Report Type        | Report            | Dossier            |
| Dossier              | description             | Source Description | Report            | Source Description |
| Chapters             | name                    | Report             | Report            | Chapter Name       |
| Chapters             | Type                    | Report Type        | Report            | Chapter            |
| Pages                | name                    | Report             | Report            | Page Name          |
| Pages                | Type                    | Report Type        | Report            | Page               |
| Visualizations       | name                    | Report             | Report            | Visualization Name |
| Visualizations       | Type                    | Report Type        | Report            | Page               |
| Documents            | name                    | Report             | Report            | Document Name      |
| Documents            | Type                    | Report Type        | Report            | Document           |
| Documents            | description             | Source Description | Report            | Source Description |

## Set up a Connection

### Prerequisites

The prerequisites to establish a connection:

#### **External Supporting Files**

{% hint style="info" %}
The required external JAR files are included as part of the OvalEdge installation artifacts. For driver installation and configuration details, refer to the [Connector Drivers Setup Guide](https://docs.ovaledge.com/connectors/additional-requirements/connector-drivers-setup-guide). Please contact the OvalEdge Team for assistance related to the driver files and configuration setup.
{% 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 MicroStrategy administrator grants these permissions, since users may not have sufficient access to assign them.
{% endhint %}

<table><thead><tr><th width="115.3333740234375">Operation</th><th width="112">Objects</th><th width="230.6666259765625">Sys Tables</th><th width="195.98944091796875">Access Permissions</th></tr></thead><tbody><tr><td>Connector Validation</td><td>-</td><td>None - only JDBC connectivity test (SELECT 1 / SELECT 'Hello world' FROM DUAL); no DSSMD* tables queried</td><td>Valid Library user; login to MicroStrategy Library; list projects (GET /api/projects); read access to Metadata Repository DB (JDBC SELECT)</td></tr><tr><td>Crawling</td><td>-</td><td>DSSMDOBJDEPN, DSSMDOBJINFO - used for dependencies, document fields, and source code during crawl</td><td>All validation permissions; access to each target project; browse/search objects in project; read object definitions (Reports, Cubes, Dossiers, Documents); answer dossier prompts if prompted dossiers exist; Metadata DB read for Documents and source code; IServer access if MSTR.jar is used for metric formulas</td></tr><tr><td>Lineage</td><td>-</td><td>DSSMDOBJDEPN, DSSMDOBJINFO - used during crawl to build source code; lineage runs on stored source code (no additional metadata tables at lineage time)</td><td>Same as crawl for objects being processed; Metadata DB read for dependencies; crawled source code must exist; IServer + MSTR.jar for full metric SQL lineage</td></tr><tr><td>-</td><td>Reports</td><td>DSSMDOBJDEPN, DSSMDOBJINFO (dependencies + source code); report/cube definition comes from REST API, not metadata tables</td><td>Project access; Browse and View/Execute (read definition) on reports and intelligent cubes; REST search (type=768,769,774,3) and /api/v2/reports/ or /api/v2/cubes/</td></tr><tr><td>-</td><td>Dossiers</td><td><p><br></p><p>DSSMDOBJDEPN, DSSMDOBJINFO (dependencies + source code); dossier structure/fields from REST API</p></td><td>Project access; Browse and View dossiers; create dossier instance and read visualizations (prompted dossiers need prompt answer rights); REST /api/dossiers, /api/v2/dossiers/{id}/definition, instance APIs</td></tr><tr><td>-</td><td>Documents</td><td>DSSMDOBJDEPN, DSSMDOBJINFO (fields + dependencies); document list from REST API</td><td>Project access; Browse and View documents via Library API (/api/documents); Metadata DB read for fields and dependencies</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 **MicroStrategy**, 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.33331298828125">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "MicroStrategy" 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><p>For more details, click <a href="https://docs.ovaledge.com/connectors/additional-requirements/credential-manager-configuration">here</a>.</p></td></tr><tr><td>License Add-On</td><td><p>Select the Auto Lineage Add-On checkbox to build data lineage automatically.</p><p>For more details, click <a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/license-types-and-add-ons">here</a>.</p></td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the MicroStrategy connection              </p><p>(Example: "MicroStrategy_Prod").</p></td></tr><tr><td>Connector Environment</td><td><p>Select the environment (Example: PROD, STG) configured for the connector.</p><p>For more details, click <a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/prerequisites#connector-environment">here</a>.</p></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 hostname or IP address of the MicroStrategy Library or Web server used to establish REST API communication with MicroStrategy.</td></tr><tr><td>Alias Host Name</td><td>Enter an alternate public hostname used to open reports in the MicroStrategy Library web application. If left blank, the value specified in Host Name is used.</td></tr><tr><td>Connection String*</td><td><p>Configure the connection string for the Oracle database:</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 database details.</p><p>{sid} refers to the database name.</p></td></tr><tr><td>Username*</td><td>Enter the username of the MicroStrategy account used to authenticate with the MicroStrategy Library REST API.</td></tr><tr><td>Password*</td><td>Enter the password associated with the specified MicroStrategy user account. This password is used to authenticate REST API requests to the MicroStrategy Library.</td></tr><tr><td>IServer</td><td>Enter the MicroStrategy Intelligence Server connection string. This is used to extract metric formulas and SQL from reports, cubes, and dossiers, enabling complete lineage generation.</td></tr><tr><td>MetaDB URL*</td><td>Enter the JDBC connection URL for the MicroStrategy Metadata Repository database. Supported databases include SQL Server, MySQL, and Oracle JDBC URLs.</td></tr><tr><td>Database Name*</td><td>Enter the name of the MicroStrategy Metadata Repository database (catalog, SID, or service name). This value is appended to the JDBC URL if it is not already included.</td></tr><tr><td>MetaDatabase UserName*</td><td>Enter the username for the MicroStrategy Metadata Repository database. This account is used to connect to the metadata repository through JDBC.</td></tr><tr><td>MetaDatabase Password*</td><td>Enter the password associated with the specified Metadata Repository database user account.</td></tr><tr><td>Proxy Enabled*</td><td>Select Yes to enable proxy settings or No to connect directly without a proxy.</td></tr></tbody></table>

<table data-header-hidden><thead><tr><th width="220.33331298828125"></th><th></th></tr></thead><tbody><tr><td><strong>Default Governance Roles</strong></td><td></td></tr><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><tr><td><strong>Admin Roles</strong></td><td></td></tr><tr><td>Admin Roles*</td><td>Select one or more users from the drop-down list for Integration Admin and Security &#x26; Governance Admin. All users configured in OvalEdge Security are available for selection.</td></tr><tr><td><strong>No of Archive Objects</strong></td><td></td></tr><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><tr><td><strong>Bridge</strong></td><td></td></tr><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 Report Groups/Reports for crawling.&#x20;

1. Navigate to the Connectors page and click **Crawl/Profile**.
2. Select the report groups/Reports 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.

For more details on connector settings, click [here](https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/connector-settings).

***

Copyright © 2025, OvalEdge LLC, Peachtree Corners GA USA


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.2/connectors/connector-repositories/reporting-tool/microstrategy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.