Contribute in GitHub:
Edit online
MicroStrategy Resource Configuration
Before you configure your scanner, make sure you meet the prerequisites. Read our guide on MicroStrategy integration requirements to double-check.
Source System Properties
This configuration can be setup by creating a new connection on Admin UI > Connections tab or editing an existing connection in Admin UI > Connections > Reporting & BI > Microstrategy > specific connection. New connection can also be created via Manta Orchestration API General Walkthrough Example.
One Manta Data Lineage connection for MicroStrategy corresponds to one MicroStrategy server that will be analyzed.
| Property name | Description | Example(s) |
|---|---|---|
microstrategy.extractor.server |
Enter an arbitrary name that identifies this MicroStrategy instance for you. The name will be used in the viewer and might affect the paths of extracted and input files for this connection. Do not use URLs. Dots are not allowed in the name. | microstrategy_instance |
microstrategy.extractor.url |
MicroStrategy Library URL address | http://microstrategy.server.com:8080/MicroStrategyLibrary |
microstrategy.extractor.user |
User for the connection to the MicroStrategy server | mstr_user |
microstrategy.extractor.password |
Password for the connection to the MicroStrategy server | mstr_password |
microstrategy.extractor.projects.include |
A semicolon-separated list of regular expressions describing project names that should be extracted. Leave blank to extract all projects that do not match the microstrategy.extractor.projects.exclude property. |
Sales.*;Human Resources Project |
microstrategy.extractor.projects.exclude |
A semicolon-separated list of regular expressions describing project names that should not be extracted. Leave blank to extract all projects that match the microstrategy.extractor.projects.include property. |
Sales.*;Human Resources Project |
microstrategy.extractor.include |
Enter a semicolon-separated list of regular expressions describing the paths that should be extracted. The full path contains names of all parent folders. Leave blank to extract all objects that do not match the microstrategy.extractor.exclude property. |
^Sales Module/Public Objects.*;^Sales Module/My Objects/Dossiers.* |
microstrategy.extractor.exclude |
Enter a semicolon-separated list of regular expressions describing the paths that should not be extracted. The full path contains names of all parent folders. Leave blank to extract all objects that match the microstrategy.extractor.include property. |
^Sales Module/Public Objects.*;^Sales Module/My Objects/Dossiers.* |
Common Scanner Properties
This configuration is common for all Microstrategy source systems and for all Microstrategy scenarios, and is configure in Admin UI > Configuration > CLI > Microstrategy > Microstrategy Common. It can be overridden on individual connection level.
| Property name | Description | Example(s) |
|---|---|---|
microstrategy.input.dir |
Path to the directory with extracted files from the MicroStrategy server | ${manta.dir.temp}/microstrategy/${microstrategy.extractor.server} |
microstrategy.extractor.rootSubFolders.exclude |
A semicolon-separated list of project root sub-folder names that will not be extracted | System Objects;Object Templates |
microstrategy.extractor.verifyHostname |
When using HTTPS, whether the hostname of the server's certificate should be validated to match the hostname of the server | true / false |
filepath.lowercase |
Whether paths to files should be lowercase (false for case-sensitive file systems, true otherwise) | true / false |