Informatica Intelligent Cloud Services source configuration

Updated:

Note This topic is only relevant if you are creating technical lineage via Edge. If you are using the CLI lineage harvester (deprecated), you need to create a <source ID> configuration file. The CLI harvester will officially reach its End of Life on July 31, 2026.

The Source configuration field in the Informatica Intelligent Cloud Services technical lineage Edge capability allows you to:

  • Map the names of connections in Informatica PowerCenter to the names of System assets in Data Catalog.
  • Define connection properties.

The value of the Source configuration field must be a valid block of JSON code, for example:

Copy 
{
    "collibraSystemNames": {
        "connections": [
            {
                "connectionName": "DG_con_standby_cmdm_clientors",
                "collibraSystemName": "PUBLIC"
            },
            {
                "connectionName": "DG_con_dev_dg_dgiauser_su",
                "collibraSystemName": "PUBLIC"
            }
        ]
    },
    "connectionDefinitions": [
        {
            "connectionName": "DG_con_standby_cmdm_clientors",
            "databaseName": "main",
            "schemaName": "dbo",
            "dialect": "oracle"
        },
        {
            "connectionName": "DG_con_dev_dg_dgiauser_su",
            "databaseName": "main",
            "schemaName": "dbo",
            "dialect": "oracle"
        }
    ]
}

The following table describes the various properties you can use in your JSON code block.

Property

 Description Required?

collibraSystemNames

This section contains the system information for Informatica Intelligent Cloud Services.
connections

This section contains the system connection information. This is required to reference to the system or server of the connection.
connectionName

The name of the connection. The name must match the System asset name in Data Catalog for stitching.

 Yes
collibraSystemName

The system or server name of the data source.

Use this property with the useCollibraSystemName property in the lineage harvester configuration file to override the default Collibra System asset name for this data source.

Specify this property with the same name as the name of the System asset that you create when you prepare the physical data layer in Data Catalog. If you don't prepare the physical data layer, Collibra Data Lineage cannot stitch the data objects in your technical lineage to the assets in Data Catalog.

 No

connectionDefinitions

This section contains the database, schema and dialect information for each connection in Informatica Intelligent Cloud Services.

Note You can add connection information for each connection in the connections section.
connectionName

The name of the connection. The name must match with the name in a connection name in the connections section.

This property is required.

Yes
databaseName

The name of your database. The name must match the Database asset name in Data Catalog for stitching.

 Yes
schemaName

The name of your schema. The name must match the Schema asset name in Data Catalog for stitching.

 Yes
dialect

The dialect of the connection. Specify this property for Collibra Data Lineage to properly extract and parse queries that are related to this connection.

You can enter one of the following values:

  • bigquery
  • db2
  • hana
  • hive
  • greenplum
  • mssql
  • mysql
  • netezza
  • oracle
  • postgres
  • redshift
  • snowflake
  • spark
  • teradata
No