IBM Cognos Analytics lineage configuration
To import lineage metadata from IBM Cognos Analytics, create a connection, data source definition and metadata import job.
This information applies to IBM Manta Data Lineage service.
Lineage import from IBM Cognos Analytics data source is available in Cloud Pak for Data 5.1.1 and later.
To import lineage metadata for Cognos Analytics, complete these steps:
- Create a data source definition.
- Create a connection to the data source in a project.
- Create a metadata import.
Creating a data source definition
Create a data source definition. Select Cognos Analytics as the data source type.
Creating a connection to IBM Cognos Analytics
Create a connection to the data source in a project. For connection details, see Cognos Analytics connection.
Only connections for which SSL is configured can be used to import metadata.
Creating a metadata import
Create a metadata import. Learn more about options that are specific to Cognos Analytics data source:
Connection mode
In the Connection mode option, only agents can be used to connect to Cognos Analytics. For more information, see Configuring agents for lineage metadata import.
Include and exclude lists
You can include or exclude assets up to the report 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:
Sales.*/MyReport
: all reports with a nameMyReport
that are in any folder with a name that starts withSales
. When you paste the path value, a leading slash (/) might be added. Remove the leading slash, as in the example.
External inputs
You can provide exported Cognos project files as external input.
This is an example structure of extraxcted Cognos project file:
cubeProject - A folder with dynamic cubes.
searchPathMappingManual.csv
[dynamic_cube_project_file].fmd
dataSet - A folder with datasets.
<cognos_namespace>
<user>
<exact folder hierarchy under user root folder>
[dataset_file].xml
team content
<exact folder hierarchy under content root folder>
[dataset_file].xml
dataSourceConnection - A folder with data source connections.
<datasource_name> - A folder with data source connections for a single data source.
[datasource_connection_name].txt
model - A folder with models.
<cognos_namespace>
<user>
<exact folder hierarchy under user root folder>
[model_file].xml
team content
<exact folder hierarchy under content root folder>
[model_file].xml
module - A folder with modules.
<cognos_namespace>
<user>
<exact folder hierarchy under user root folder>
[module_file].xml
team content
<exact folder hierarchy under content root folder>
[module_file].xml
report - A folder containing reports
<cognos_namespace>
<user>
<exact folder hierarchy under user root folder>
[report_name].xml
team content
<exact folder hierarchy under content root folder>
[report_name].xml
localeMapping.xml - An XML file with mapping of objects between different locales.
You can also add the following input files:
- Dynamic cubes - This file contains manually extracted Cognos Analytics Dynamic Cubes.
searchPathMappingManual.csv
- This CSV file contains mappings between report search paths and dynamic cubes.
Advanced import options
- Performance profile
- For selected data sources you can choose a performance profile. Depending on your current needs, the lineage metadata import might be faster or more complete. You can choose between the following profiles:
- Fast: Low time and memory consumption are the priorities in this profile. If your input is large, lineage might not be complete.
- Balanced: Both performance and lineage completness are important. It is a compromise bewteen the lineage completness and time and memory that is spent on lineage import.
- Complete: The completness for lineage is the priority in this profile. If your input is large, the lineage import might take a significant amount of resources and time.
- Custom profile: You can create your own performance profile by providing values for the following properties:
- Dataflow Analysis Timeout Limit: Specifies the maximum estimated time (in seconds) after which the dataflow analysis of a single input is stopped. The time is checked when each node is added, or in some cases when
edges are created. Therefore, in some cases, the timeout might slightly exceed the specified limit. If you set the value to 0, the analysis is not stopped. Example value:
60
. - Dataflow Analysis Edge Limit: Specifies the maximum number of edges that are allowed for a single input during the dataflow analysis. If this limit is exceeded, all filter edges are removed and no more filter edges
are added. If the limit is still exceeded even after that, the analysis is stopped and the input fails. To disable the limit, set the value to 0. Example value:
2500
.
- Dataflow Analysis Timeout Limit: Specifies the maximum estimated time (in seconds) after which the dataflow analysis of a single input is stopped. The time is checked when each node is added, or in some cases when
edges are created. Therefore, in some cases, the timeout might slightly exceed the specified limit. If you set the value to 0, the analysis is not stopped. Example value:
- Primary locale identifier
- Specify the identifier of the main language locale in which your objects are displayed, for example "en" for English, "de" for German etc. If no value is provided, the user account locale is used.
- Identifiers of other locales
- Specify a comma-separated list of identifiers of all language locales that are used in your Cognos Analytics environment, except the main locale. If no value is specified, only the main locale is processed.
Learn more
Parent topic: Supported connectors for lineage import