SSAS Resource Configuration

Note: Before you configure your scanner, make sure you meet the prerequisites. Read our guide SSAS 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 > SSAS > specific connection. New connection can also be created via Manta Orchestration API General Walkthrough Example.

One IBM Automatic Data Lineage connection for SSAS (that means one input directory) corresponds to one SSAS server that will be analyzed, and inside this directory, one input *.xmla or *.bim file corresponds to one database. For one input directory, there can be multiple databases, but all databases placed in one input directory must have unique names (the input file name does not matter; the database name is specified inside the input file). If there are multiple databases with the same name, they must be placed in separate directories (that means they are stored on different servers).

Property name

Description

Example

ssas.dictionary.id

Name of the target SSAS server which identifies this source system

SSAS

ssas.properties.processHiddenAttributes

Whether hidden attributes should be processed

true
false

ssas.input.encoding

Encoding of the input files. See Encodings for applicable values.

utf8

ssas.properties.hostname

Name of the top-level object in the Filesystem hierarchy
for any files the SSAS instance integrates with

localhost

Common Scanner Properties

This configuration is common for all SSAS source systems and for all SSAS scenarios, and is configure in Admin UI > Configuration > CLI > SSAS > SSAS Common. It can be overridden on individual connection level.

Property name

Description

Example

ssas.input.dir

Directory where input SSAS project files are expected to be stored

${manta.dir.temp}/ssas/${ssas.dictionary.id}

ssas.dictionary.dir

Directory with data dictionaries extracted from SSAS

${manta.dir.temp}/ssas

filepath.lowercase

Whether paths to files should be lowercase (use false for case-sensitive file systems, true otherwise)

true
false

ssas.dictionary.mappingFile

Path to automatically generated mappings for SSAS databases

${manta.dir.temp}/ssas/

ssasDictionaryMantaMapping.csv

ssas.dictionary.mappingManualFile

Path to mappings provided manually for SSAS databases

${manta.dir.scenario}/conf/

ssasDictionaryMantaMappingManual.csv

Manual Mapping Properties

It is possible to manually configure mappings for SSAS databases in the file ${ssas.dictionary.mappingManualFile} listed in the table above. This is necessary when multiple databases with the same name exist on different servers or no Initial Catalog property is set in a connection string. In order to configure manual mapping, copy a relevant line from the automatically generated file ${ssas.dictionary.mappingFile} and modify the Connection ID column with the external connection identifier.

Each mapping has its own row with the following parts separated by semicolons.

Property name

Description

Example

Dictionary ID

The name of a resource representing this SSAS database server (also known as the dictionary ID); it is used as an input subdirectory name for database description files and an output subdirectory name for the extracted database dictionary

SSAS_Server1

Data source

The name of the data source used to connect to the SSAS server, usually a server name or IP address

localhost
127.0.0.1

Database instance name

The name of the instance of Microsoft Analysis Services running on the server

instance_1

Initial catalog

The name of the catalog extracted from a single input file (this is the only one of these properties extracted during SSAS analysis) or the initial catalog name used to connect to the SSAS server

db1

User ID

The user ID used to connect to the SSAS server

user1

Connection ID

ID of the connection

conn1