0 / 0

IBM Cognos Analytics lineage configuration

Last updated: Jun 27, 2025
IBM Cognos Analytics lineage configuration

To import lineage metadata from IBM Cognos Analytics, create a connection, data source definition and metadata import job.

To import lineage metadata for Cognos Analytics, complete these steps:

  1. Create a data source definition.
  2. Create a connection to the data source in a project.
  3. 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 name MyReport that are in any folder with a name that starts with Sales. 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

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