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.
Overview
Connector Details
Connector Category
Reporting Tools
OvalEdge Release Supported
Release7.2.x and later
Connectivity
[How the connection is established with MicroStrategy]
REST APIs and JDBC
Verified MicroStrategy Version
MicroStrategy 10.11 and later (on-premises)
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.
Connector Features
Crawling
✅
Profiling
NA
Query Sheet
NA
Report Preview
✅
Auto Lineage
✅
Manual Lineage
✅
Secure Authentication via Credential Manager
✅
Data Quality
❌
DAM (Data Access Management)
❌
Bridge
✅
'NA' indicates that the respective feature is 'Not Applicable.'
Metadata Mapping
The following objects are crawled from MicroStrategy and mapped to the corresponding UI assets.
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
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. Please contact the OvalEdge Team for assistance related to the driver files and configuration setup.
Service Account User Permissions
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.
👨💻 Who can provide these permissions? The MicroStrategy administrator grants these permissions, since users may not have sufficient access to assign them.
Connector Validation
-
None - only JDBC connectivity test (SELECT 1 / SELECT 'Hello world' FROM DUAL); no DSSMD* tables queried
Valid Library user; login to MicroStrategy Library; list projects (GET /api/projects); read access to Metadata Repository DB (JDBC SELECT)
Crawling
-
DSSMDOBJDEPN, DSSMDOBJINFO - used for dependencies, document fields, and source code during crawl
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
Lineage
-
DSSMDOBJDEPN, DSSMDOBJINFO - used during crawl to build source code; lineage runs on stored source code (no additional metadata tables at lineage time)
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
-
Reports
DSSMDOBJDEPN, DSSMDOBJINFO (dependencies + source code); report/cube definition comes from REST API, not metadata tables
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/
-
Dossiers
DSSMDOBJDEPN, DSSMDOBJINFO (dependencies + source code); dossier structure/fields from REST API
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
-
Documents
DSSMDOBJDEPN, DSSMDOBJINFO (fields + dependencies); document list from REST API
Project access; Browse and View documents via Library API (/api/documents); Metadata DB read for fields and dependencies
Connection Configuration Steps
Users must have the Connector Creator role to configure a new connection.
Log into OvalEdge, go to Administration > Connectors, click + (New Connector), search for MicroStrategy, and enter the required parameters.
Fields marked with an asterisk (*) are mandatory for establishing a connection.
Connector Type
By default, "MicroStrategy" is displayed as the selected connector type.
Credential Manager*
Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selection.
Supported Credential Managers:
OE Credential Manager
AWS Secrets Manager
HashiCorp
Azure Key Vault
For more details, click here.
License Add-On
Select the Auto Lineage Add-On checkbox to build data lineage automatically.
For more details, click here.
Connector Name*
Enter a unique name for the MicroStrategy connection
(Example: "MicroStrategy_Prod").
Connector Environment
Select the environment (Example: PROD, STG) configured for the connector.
For more details, click here.
Connector Description
Enter the description related to the connector.
Host Name*
Enter the hostname or IP address of the MicroStrategy Library or Web server used to establish REST API communication with MicroStrategy.
Alias Host Name
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.
Connection String*
Configure the connection string for the Oracle database:
Automatic mode: The system generates a connection string based on the provided credentials.
Manual mode: Enter a valid connection string manually.
Replace placeholders with actual database details.
{sid} refers to the database name.
Username*
Enter the username of the MicroStrategy account used to authenticate with the MicroStrategy Library REST API.
Password*
Enter the password associated with the specified MicroStrategy user account. This password is used to authenticate REST API requests to the MicroStrategy Library.
IServer
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.
MetaDB URL*
Enter the JDBC connection URL for the MicroStrategy Metadata Repository database. Supported databases include SQL Server, MySQL, and Oracle JDBC URLs.
Database Name*
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.
MetaDatabase UserName*
Enter the username for the MicroStrategy Metadata Repository database. This account is used to connect to the metadata repository through JDBC.
MetaDatabase Password*
Enter the password associated with the specified Metadata Repository database user account.
Proxy Enabled*
Select Yes to enable proxy settings or No to connect directly without a proxy.
Default Governance Roles
Default Governance Roles*
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.
Admin Roles
Admin Roles*
Select one or more users from the drop-down list for Integration Admin and Security & Governance Admin. All users configured in OvalEdge Security are available for selection.
No of Archive Objects
No Of Archive Objects*
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.
Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.
Bridge
Select Bridge*
If applicable, select the bridge from the drop-down list.
The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering firewall rules.
After entering all connection details, the following actions can be performed:
Click Validate to verify the connection.
Click Save to store the connection for future use.
Click Save & Configure to apply additional settings before saving.
The saved connection will appear on the Connectors home page.
Manage Connector Operations
Crawl
To perform crawl operations, users must be assigned the Integration Admin role.
The Crawl/Profile button allows users to select one or more Report Groups/Reports for crawling.
Navigate to the Connectors page and click Crawl/Profile.
Select the report groups/Reports to crawl.
Click Run to collect metadata from the connected source and load it into the Data Catalog.
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.
Click the Schedule checkbox to enable the Select Period drop-down.
Select a time period for the operation from the drop-down menu.
Click Schedule to initiate metadata collection from the connected source.
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.
Copyright © 2025, OvalEdge LLC, Peachtree Corners GA USA
Was this helpful?