Contribute in GitHub: Edit online

MicroStrategy Integration Requirements

The following are the prerequisites necessary for IBM Manta Data Lineage to connect to this third-party system, which you may choose to do at your sole discretion. Note that while these are usually sufficient to connect to this third-party system, we cannot guarantee that the connection or integration will be successful since we have no control, liability, or responsibility for third-party products or services, including for their performance.

• The scanner has been developed to accommodate the 2021 Update 6 version.

• The scanner can automatically extract objects from the MicroStrategy server. The following requirements must be met for the scanner to automatically to extract the data.

  • MicroStrategy server accessible via network from the Manta agent / Manta server

  • Known connection parameters

    • MicroStrategy Library URL

    • Username

    • Password

  • User with administrator privileges

The extraction via Manta Flow Agent is supported as of version R41. See Manta Flow Agent Configuration for Extraction for details.

MicroStrategy Scanner Overview

Supported Features

• Dossier sources

  • OLAP cubes

  • Modeled objects (as of R42.4)

  • Reports (as of R42.4)

  • Data import cubes (as of R42.6)

  • Embedded datasets (as of R42.6)

• Reports

  • Intelligent Cube report

  • Data object report

• Intelligent Cubes

• Attributes

• Metrics

• Facts

• Logical tables

• Datasources

  • Connection to a database (e.g., Oracle, Teradata, PostgreSQL, etc.)

  • Data import (as of R42.6)

  • Only live data sources

Known Unsupported Features

IBM Manta Data Lineage does not support the following MicroStrategy features. This list includes all of the features that IBM is aware are unsupported, but it might not be comprehensive.

• Documents

• Free-form SQL

• Datasources

  • Connection to a file

• Embedded metrics

Extraction Process

The extraction process uses the REST API of the MicroStrategy server. It extracts information about stored projects, compares the names with the include/exclude regexes provided by the user, and afterward, extracts all supported objects per project. Token-based authentication is used.

These are some of the REST API endpoints used.

• POST /auth/login

• GET /sessions

• GET /status

• GET /projects

• GET /searches/results

• GET /model/attributes/{0}

• GET /model/facts/{0}

• GET /model/metrics/{0}

• GET /model/tables/{0}

• GET /datasources

• GET /datasources/connections/{0}

• POST /documents/{0}/instances

• GET /documents/{0}/cubes

• GET /v2/dossiers/{0}/instances/{1}/chapters/{2}/visualizations/{3}

• GET /v2/dossiers/{0}/definition

• GET /v2/reports/{0}

• GET /v2/cubes/{0}