Informatica PowerCenter source configuration

Updated:

The Source configuration field in the Informatica PowerCenter technical lineage Edge capability allows you to:

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

Source configuration is case-sensitive. Enter system, database, and schema names using consistent casing based on the source.

  • If the name contains uppercase characters, enter it in uppercase. For example, enter RAW when the source uses Raw.
  • If the name is lowercase, enter it in lowercase.

Tip If you previously integrated Informatica PowerCenter via the lineage harvester (deprecated), you can copy and paste the JSON code from your <source ID> configuration file into the Source configuration field.

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

Copy 
{
    "connectionDefinitions": {
        "oracle_source": {
            "dbname": "oracle-source-database-name1",
            "schema": "my Oracle source schema",
            "dialect": "oracle"
        },
        "oracle_target": {
            "dbname": "oracle-target-database-name2",
            "schema": "my other oracle target schema",
            "dialect": "oracle"
        }
    },
    "collibraSystemNames": {
        "databases": [
            {
                "dbname": "oracle-source-database-name1",
                "collibraSystemName": "oracle-system-name1"
            },
            {
                "dbname": "oracle-target-database-name2",
                "collibraSystemName": "oracle-system-name2"
            }
        ],
        "connections": [
            {
                "connectionName": "oracle-source",
                "collibraSystemName": "oracle-system-name1"
            },
            {
                "connectionName": "oracle-target",
                "collibraSystemName": "oracle-system-name2"
            }
        ]
    }
}

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

If the connection definitions are provided but certain properties are not specified, an analyze error called CONFIGURATION is displayed in the transformations table on the Sources tab page when the technical lineage is created. The unspecified properties are marked as UNDEFINED in the analyze error. For more information about the analyze errors, go to Analyze errors and possible solutions in Technical lineage Sources tab page.

Property

 Description

connectionDefinitions

This section contains the connection properties to a source in Informatica PowerCenter.
<connectionName>

The type of your source or target data source.

This section contains the connection properties to a source or target in Informatica PowerCenter.

Note Define a connection in the JSON file only once; specifically, define a data source with the <connectionName> property specified only once in the JSON file. If you define a connection multiple times, unexpected lineage and stitching issues might occur.
dbname

The name of your source or target database.

When you specify the dbname and schema properties, Collibra Data Lineage can stitch the data objects to the assets in Data Catalog. If the properties are not specified, the data objects are not stitched.
schema

The name of your source or target schema.

When you specify the dbname and schema properties, Collibra Data Lineage can stitch the data objects to the assets in Data Catalog. If the properties are not specified, the data objects are not stitched.
dialect

The dialect of the referenced database.

If you specify a dialect for a database, the value overrides the dialect that you specify in the lineage harvester configuration file for this database.

For any databases that do not have a dialect specified in the source ID file, the dialect that you specify in the lineage harvester configuration file is used as a global dialect.

You can enter one of the following values:

  • azure, for an Azure SQL Server data source.
  • bigquery, for a Google BigQuery data source.
  • db2, for an IBM DB2 data source.
  • hana, for an SAP HANA data source.
  • hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source.
  • hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source.
    Important 

    To get technical lineage including calculated views, you must harvest SAP HANA by specifying two data sources in the lineage harvester configuration file. In one data source, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect.

  • hive, for a HiveQL data source.
  • greenplum, for a Greenplum data source.
  • mssql, for a Microsoft SQL Server data source.
  • mysql, for a MySQL data source.
  • netezza, for a Netezza data source.
  • oracle, for an Oracle data source.
  • postgres, for a PostgreSQL data source.
  • redshift, for an Amazon Redshift data source.
  • snowflake, for a Snowflake data source.
  • spark, for a Spark SQL data source.
  • sybase, for a Sybase data source.
  • teradata, for a Teradata data source.

collibraSystemNames

This section contains the system or server name that is specified in your database and referenced in your connection.

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.

The following rules apply when you specify the collibrasystemname properties in this file and the lineage harvester configuration file:

  • If you specify this property for a database or connection, the value of this property overrides the value in the lineage harvester configuration file for the database or connection.
  • For any databases or connections that do not have a Collibra system name specified in the source ID file, the value of the collibrasystemname property in the lineage harvester configuration file is used as a global value.
databases

This section contains the database information. This is required to connect directly to the system or server of the database.
dbname
 The name of the database. The database name is the same as the name you entered in the <connectionName> section.
collibraSystemName

The system or server name of the database.
connections

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

The name of the connection.
collibraSystemName

The system or server name of the connection.
Important If you are using variables in Informatica PowerCenter, add the value of the variable instead of the name in the connection definitionsJSON file. For example, if the parameter file contains $DBConnection_dwh=DWH_EXPORT, add the following connection definitions to the JSON file: 
{
	"DWH_EXPORT":

		{ "dbname": "DWH", "schema": "DBO" }
}