Informatica PowerCenter lineage configuration

Connect to Informatica PowerCenter to scan metadata and display it on lineage. To import lineage metadata, create data source definition, a connection, and metadata import job.

Supported Informatica PowerCenter versions

  • Informatica PowerCenter 9.x or 10.x (remote)

Processed metadata

The following Informatica PowerCenter metadata is processed and displayed on lineage:

  • Workflows, worklets, including workflow variables, integration service parameters, and parameter files (also multiple parameter files for one workflow)
  • Sessions, mappings, mapplets, including mapping parameters and parameter files
  • SQL overrides
  • Source definitions: File Reader (direct, indirect, command only by using customization), Relational Reader, XML Reader, Teradata Parallel Transporter Reader, JMS Reader (as an application), JDBC Reader, (Netezza Bulk Reader), PowerExchange Reader for sequential files (as an application), PowerExchange Batch Reader for VSAM files (as an application), Salesforce Reader (as an application), PowerExchange CDC Reader for ORACLE (SQL query override is not supported), Teradata Fast Export Reader, MQ Reader
  • Target definitions: File Writer (different merge types and external loaders are supported, dynamic filename is not supported), Relational Writer (pre and post SQL attributes are supported), XML Writer, Teradata Parallel Transporter Writer, JMS Writer, JDBC Writer, Vertica Bulk Writer, Netezza Bulk Writer, PowerExchange Writer for sequential files (as an application), Salesforce Writer (as an application)
  • Standard transformations: Lookup procedure (relational (lookup SQL override is supported), file (direct, indirect)), Source qualifier (SQL query and pre and post SQL attributes are supported), MQ Source qualifier, Application source qualifier, App multi-group source qualifier, XML source qualifier, Stored procedure (stored procedure parsing is not supported), External procedure (stored procedure parsing is not supported), Expression, Joiner, Aggregator, Router, Sorter, Filter, Normalizer (VSAM Normalizer is not supported), Rank, Sequence, Transaction control, Update strategy
  • Custom transformations: Union, HTTP transformation (partially supported), SQL transform (SQL query attribute is not supported), XML generator, XML parser, Consolidate (selected versions are supported), ExternalChecker (selected versions are supported), Manual definition for data lineage

Limitations

The following data is not processed:

  • Source/Target definitions: WebServices Consumer Reader/Writer, WebServices Provider Reader/Writer
  • Transformations: Java, Salesforce, Unstructured data, Data masking
  • Non-expression variables. Variables that are marked as non-expression resolve only to text without any reference to port and have no impact on data lineage.

Prerequisite configuration

Before you import lineage metadata, ensure that the following prerequisites are met:

  • You must have the following rights:
    • READ privileges for all folders and workflows in the repository
    • READ privilege for all connections defined in Informatica PowerCenter to access their definitions. See Types of Connection Permissions for more details.
    • READ privileges for integration

Creating a metadata import asset

Data source connection

To connect to the data source from which you want to import lineage metadata, you need to select a data source definition and a connection. You can create them before you start creating the metadata import, or you can create them when you create and configure the metadata import asset.

Data source definition

Select Informatica PowerCenter as the data source type.

Connection

To create the connection asset, you need the following connection details:

  • Informatica PowerCenter server host
  • Informatica PowerCenter server port
  • Informatica PowerCenter domain name
  • Repository name
  • Credentials: username and password

For connection details, see Informatica PowerCenter connection.

Include and exclude lists

You can include or exclude assets up to the workflow level. Provide folders and workflows in the folder/workflow format.

Example values:

  • myFolder/: all workflows in myFolder
  • myFolder3/myWorkflow: myWorkflow from myFolder3
  • Dataflow/MyWorkflow,Dataflow2/.*: MyWorkflow from folder Dataflow and all workflows from folder Dataflow2

External inputs

You can provide additional or all Informatica PowerCenter project files as external inputs. You can add the following files:

  • workflow - This directory contains the Informatica PowerCenter workflows.
  • ifpcServiceSettings.prm - This file contains the integration service settings.
  • ifpcConnectionDefinition.prm - This file contains the connection definition settings.
  • parameterfiles - This directory contains the Informatica PowerCenter parameter files.
  • indirectfiles - This directory contains the Informatica PowerCenter indirect files.
  • ifpcParameterFileMapping.csv - This file contains the parameter overrides.

The external input file can have the following format:

  • <project_export.zip>
  • workflow
    • individual workflow XML exports
  • ifpcServiceSettings.prm
  • ifpcConnectionDefinition.prm
  • parameterfiles
  • indirectfiles
  • ifpcParameterFileMapping.csv

Advanced import options

Transform file paths to lowercase
Set this option to true if you want the paths to files to be transformed to lowercase.
Override session parameter files
When you use the ifpcParameterFileMapping.csv file to override parameter values, set this option to true to override also session-level parameter files.
Export command calls
Set this optiont to true to export a list of command calls from all command tasks.
Ignore filename field​
Use this option to determine how to process dynamically-provided filenames for lineage, specifically the field ISFILENAMEFIELD in the target definition. By default, target file is not created because its name is determined dynamically from data at runtime. A target definition transformation is created. When you set this option to true, the ISFILENAMEFIELD field is ignored, and a target file is created. A static value of the filename from a mapping is used, if it is available.

Learn more