Informatica PowerCenter Integration Requirements
The following are the prerequisites necessary for IBM Automatic Data Lineage to connect to this third-party system, which you may choose to do at your sole discretion. Note that while these are usually sufficient to connect to this third-party system, we cannot guarantee that the connection or integration will be successful since we have no control, liability, or responsibility for third-party products or services, including for their performance.
- Informatica PowerCenter: version 9.x or 10.x (remote)
- User having 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. Check Types of Connection Permissions for more details.
- Read privileges for integration service settings
- Connection parameters:
- Domain name
- Repository name

- Host of the PowerCenter server for the repository
- Port of the PowerCenter server for the repository

- User name
- User password
- Security domain

- PowerCenter must be accessible via network.
- PowerCenter client tools must be properly installed and configured on the same machine as Automatic Data Lineage.
- The installed version of the client tools must be of the same version as the IPC instance that will be used for connections. If you plan to make connections to repositories running on different versions of Informatica PowerCenter, multiple versions of the client tools must be installed.
- For Windows implementations, this includes a complete Informatica PowerCenter and Developer Client installation.
- For Linux implementations, this includes either a full installation of PowerCenter and Developer Client or the PowerCenter Command Line Utilities package.
- Note that Manta Flow only uses the following two command line tools (the full installs noted above are required to properly utilize these components):
Pmreptool for workflow and connection setting extractionInfacmdtool for integration service setting extraction
- Path for
LD_LIBRARY_PATH,INFA_HOMEdirectories as per Informatica PowerCenter Command Line Tool Installation
- Parameter and indirect files must be available on the Automatic Data Lineage machine local filesystem in the form of files
For more details about extraction via Manta Flow Agent, see Manta Flow Agent Configuration for Extraction.
PowerCenter Scanner Overview
The PowerCenter scanner extracts XML specifications for workflows and mappings from the PowerCenter repository as well as connection
definitions and integration service parameters. It analyzes workflows and all the objects they depend on and produces data lineage. If the PowerCenter scanner and relevant database scanners are configured properly, Manta Viewer can display lineage starting at the source databases/files/applications and flowing through all the transformations to the target databases/files/applications.
Supported Features
- 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
- Source definitions
- File Reader — direct, indirect, command only via 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 — does not support SQL query override
- Teradata Fast Export Reader - as of R42.13
- MQ Reader - as of R42.13
- Target definitions
- File Writer — supports different merge types and external loaders, doesn't support dynamic filename
- Relational Writer — supports pre/post SQL attributes
- 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 (supports lookup SQL override), file (direct, indirect)
- Source qualifier — supports SQL query and pre/post SQL attributes
- MQ Source qualifier - as of R42.13
- Application source qualifier
- App multi-group source qualifier
- XML source qualifier
- Stored procedure — no stored procedure parsing
- External procedure — no stored procedure parsing
- Expression
- Joiner
- Aggregator
- Router
- Sorter
- Filter
- Normalizer — does not support VSAM Normalizer
- Rank
- Sequence
- Transaction control
- Update strategy
-
Custom transformations
- Union
- HTTP transformation — partial support
- SQL transform — does not support the SQL query attribute
- XML generator
- XML parser
- Consolidate — only selected versions
- ExternalChecker — only selected versions
- Manual definition for data lineage supported
Known Unsupported Features
Automatic Data Lineage does not support the following Informatica PowerCenter features. This list includes all of the features that IBM is aware are unsupported, but it might not be comprehensive.
- Source/Target definitions
- WebServices Consumer Reader/Writer
- WebServices Provider Reader/Writer
- Transformations
- Java
- Salesforce
- Unstructured data
- Data masking
- Variables
- Resolving non-expression variables (Variables marked as non-expression resolve only to text without any reference to ports. This means these variables don't have any impact on data lineage, so we don't resolve them)
Matrix of supported and unsupported data sources
| DBMS (Database Management System) | Is supported |
|---|---|
| DB2 | Yes |
| Netezza | Yes |
| Oracle | Yes |
| MS SQL | Yes |
| Sybase | Yes |
| PostgreSQL | Yes |
| Snowflake | Yes |
| Vertica | Yes 1 |
| Teradata | Yes |
| Informix | Yes 1 |
| ODBC | Yes |
| JDBC | Yes |
| FTP/Filesystem | Yes 1 |
| Message queue | Yes 1 |
| MSMQ | Yes 1 |
| Web Services Consumer | Yes 1 |
| JMS Connection | Yes 1 |
| JNDI Connection | Yes 1 |
| SAP R3 | Yes 1 |
| Salesforce | Yes 1 |
| SAP BW | Yes 1 |
Notes: 1 No OOTB connector for this source/target; will be handled via deduction only