To access your data in MicroStrategy, create a connection asset for it.
MicroStrategy is a reporting and data analytics platform.
Supported versions
MicroStrategy 11.3.6 (2021 Update 6)
Create a connection to MicroStrategy
To create the connection asset, you need the following connection details:
- MicroStrategy Library URL address: The URL used to access the MicroStrategy Library. For example,
http://microstrategy.server.com:8080/MicroStrategyLibrary. - Username: The username used to connect to the MicroStrategy server. This user must have administrator privileges.
- Password: The password associated with the specified username.
- SSL certificate (if required by the database server)
Other properties
- Extracted projects: A list of projects to extract. To identify the names of projects to extract, specify regular expressions and separate them by semicolons. To extract all projects, leave the field empty. Example value:
Sales.*;Human Resources Project. - Excluded projects: A list of projects to exclude from extraction. To identify the names of the projects to exclude from extraction, specify regular expressions and separate them by semicolons. Example value:
Sales.*;Human Resources Project.
Choose the method for creating a connection based on where you are in the platform
- In a project
- Click Assets > New asset > Connect to a data source. See Adding a connection to a project.
- In a catalog
- Click Add to catalog > Connection. See Adding a connection asset to a catalog.
- In the Platform assets catalog
- Click New connection. See Adding platform connections.
Next step: Add data assets from the connection
Where you can use this connection
You can use the MicroStrategy connection in the following workspaces and tools:
Projects
Metadata import (data assets) and Metadata import (external lineage) (IBM Knowledge Catalog) Advanced metadata import must be enabled. For lineage imports, a MANTA Automated Data Lineage license key must be installed. See Installed features and license requirements and Enabling lineage import in the IBM Software Hub documentation.
Catalogs
- Platform assets catalog
- Other catalogs (IBM Knowledge Catalog)
Data lineage
- Metadata import (lineage) (IBM Knowledge Catalog and IBM Manta Data Lineage)
Restrictions
- You can connect only to the on-premises MicroStrategy servers.
- You can use this connection only for source data. You cannot write to data or export data with this connection.
Configuring lineage metadata import for MicroStrategy
When you create a metadata import for the MicroStrategy connection, you can set options specific to this data source, and define the scope of data for which lineage is generated. For details about metadata import, see Designing metadata imports.
To import lineage metadata for MicroStrategy, complete these steps:
- Create a data source definition. Select MicroStrategy as the data source type. In the hostname/IP address skip the library path for example
12.345.678.90. - Create a connection to the data source in a project.
- Create a metadata import. Learn more about options that are specific to MicroStrategy data source:
- When you define a scope, you can analyze the entire data source or use the include and exclude options to define the exact projects that you want to be analyzed. See Include and exclude lists.
- Optionally, you can provide external input. You add this file in the Add inputs from file field. The file must have a supported structure. See External inputs.
Include and exclude lists
You can include or exclude assets up to the project level. Assets which are added later in the data source will also be included or excluded if they match the conditions specified in the lists. Example values:
myProject: all reports inmyProject
External inputs
You can provide an exported MicroStrategy project as external input. The file can have the following structure:
<project_id> - A folder with the project ID.
cubes - A folder with cubes.
[cube_id].json - A file with an exported cube.
datasets - A folder with datasets.
[dataset_id].json - A file with an exported dataset.
dossiers - A folder with dossiers.
[dossier_id] - A folder with dossier ID.
dossierDefintion.json - A file with an exported definition of the dossier.
visualisations - A folder with dossier visualisations.
[visualisation_key].json - A file with an exported visualisation.
reports - A folder with reports.
[report_id].json - A file with an exported report.
attributes.json - A file with attributes.
facts.json - A file with facts.
logicalTables.json - A file with logicalTables.
metrics.json - A file with metrics.
project.json - A file with project information.
Learn more
Parent topic: Supported connections