Informatica PowerCenter Resource Configuration

Before you configure your scanner, make sure you meet the prerequisites. Read our guide on Informatica PowerCenter integration requirements to double-check.

Source System Properties

This configuration can be setup by creating a new connection on Admin UI > Connections tab or editing an existing connection in Admin UI / Connections / Data Integration Tools / Informatica PowerCenter / specific connection. New connection can also be created via Manta Orchestration API.

One IBM Automatic Data Lineage connection for Informatica PowerCenter corresponds to one PowerCenter repository and a list of its folders that will be analyzed. The configuration for each source system can be copied from the file ifpc/template.properties.

Property name

Description

Example

ifpc.extractor.domain.name

Domain name of the Informatica PowerCenter server

Domain_NAME

ifpc.extractor.host

Host of the Informatica PowerCenter server

ifpc_host

ifpc.extractor.port

Port of the Informatica PowerCenter server

6005

ifpc.extractor.user

User for the connection to the Informatica PowerCenter server

manta_user

ifpc.extractor.password

Password for the connection to the Informatica PowerCenter server

manta_password

ifpc.extractor.domain

Security domain of the user that is used to connect to the Informatica PowerCenter server; for native security domains, the parameter should be empty

manta_domain

ifpc.extractor.repository

Informatica PowerCenter server repository to connect to

ifpc_repo

ifpc.server.default.name

Enter the name of the default server the PowerCenter Integration Service runs on if not specified in the workflow, or leave blank if it is always specified

is_dev

ifpc.extractor.folders

Folders in the repository that workflows will be extracted from, delimited by commas, or leave blank if all folders should be extracted

Folder1,Folder2,Folder3

ifpc.extractor.workflows.include

Enter a regular expression for workflow full names that should be extracted in the format folder/workflow, or leave blank to ignore this parameter

Folder1/wf_loadCrm|Folder2/exportIntoDatalake

ifpc.extractor.workflows.exclude

Enter a regular expression for workflow full names that should NOT be extracted in the format folder/workflow, or leave blank to ignore this parameter

Folder1/wf_loadCrm|Folder2/exportIntoDatalake

ifpc.extraction.method

Set to Agent:default when the desired extraction method is the default Manta Extractor Agent, set to Agent:{remote_agent_name} when a remote Agent is the desired extraction method, set to Git:{git.dictionary.id} when the Git ingest method is the desired extraction method. For more information on setting up a remote extractor Agent please refer to the Manta Flow Agent Configuration for Extraction documentation. For additional details on configuring a Git ingest method, please refer to the Manta Flow Agent Configuration for Extraction:Git Source documentation.

default

Git

agent

ifpc.extractor.executer

Path on the Automatic Data Lineage machine to the executable pmrep application file that connects to the Informatica PowerCenter server

c:/Informatica/10.4.1/clients/ tools/utils/pmrep.exe (path for full install of client tools on Windows)
c:\programs\informatica_1053_cmd_utilities_winem-64t\PowerCenter\server\bin\pmrep.exe (path for command line tools only)

ifpc.extractor.cmd

Path on the Automatic Data Lineage machine to the executable infacmd.[bat|sh] application file that connects to the Informatica PowerCenter server

c:/Informatica/10.4.1/clients/DeveloperClient/infacmd/infacmd.bat (path for full install of client tools on Windows)
c:\programs\informatica_1053_cmd_utilities_winem-64t\PowerCenter\isp\bin\infacmd.bat (path for command line tools only)

ifpc.extractor.domains.file

Path on the Automatic Data Lineage machine to the Informatica PowerCenter Client domains.infa file

c:/Informatica/10.4.1/clients/
PowerCenterClient/domains.infa
c:\programs\informatica_1053_cmd_utilities_winem-64t\PowerCenter\domains.infa

ifpc.extractor.ldLibraryPath

Path on the Automatic Data Lineage machine to the LD Library; overrides the LD_LIBRARY_PATH environment variable (Unix only)

/opt/informatica_1053_cmd_utilities_linux-64t/PowerCenter/server/bin/

ifpc.extractor.infaHome

Path on the Automatic Data Lineage machine to the home directory of Informatica Powercenter; overrides the INFA_HOME environment variable

/opt/informatica_1053_cmd_utilities_linux-64t/PowerCenter/server/bin/

ifpc.node.name

Name of the node the PowerCenter Integration Service runs on

If you don’t use sections of the Informatica PowerCenter parameter files in the format [Service:service name.ND:node name], you can leave it blank

ifpc_node

ifpc.input.encoding

Encoding of extracted Informatica PowerCenter workflows. See Encodings for applicable values.

UTF-8

ifpc.parameter.files.dirs

Single relative path to input directory root, where Informatica PowerCenter parameter files are stored, or leave blank if their absolute paths can be used

${manta.dir.input}/ifpc/<repository_name>/parameterfiles/

ifpc.indirect.files.dirs

Single relative path to input directory root, where Informatica PowerCenter indirect files are stored, or leave blank if their absolute paths can be used

${manta.dir.input}/ifpc/<repository_name>/indirectfiles/

ifpc.extractor.infaTruststorePath (as of R42.7)

Path on the Automatic Data Lineage machine to the directory that contains the infa_truststore.jks and infa_truststore.pem files for the SSL certificates. This is same value as INFA_TRUSTSTORE environment variable per Informatica documentation.

c:/Informatica/truststore

ifpc.extractor.infaTruststorePassword (as of R42.7)

Encrypted password for the provided truststore. This is same value as INFA_TRUSTSTORE_PASSWORD environment variable per Informatica documentation

encrypted_truststore_password

It is necessary to have read rights for the entire Informatica PowerCenter repository when the workflows and connection definitions are automatically extracted and for its integration service when the service settings are automatically extracted.

Common Scanner Properties

This configuration is common for all Informatica PowerCenter source systems and for all Informatica PowerCenter scenarios, and is configure in Admin UI / Configuration / CLI / Informatica PowerCenter / Informatica PowerCenter Common. It can be overridden on individual connection level.

Property name

Description

Example

ifpc.input.dir

Directory for/with automatically extracted Informatica PowerCenter workflows

${manta.dir.temp}/ifpc/
${ifpc.extractor.repository}/workflow

ifpc.input.manual.dir

Directory for/with manually provided Informatica PowerCenter workflows by the user

${manta.dir.input}/ifpc/
${ifpc.extractor.repository}/workflow

ifpc.extractor.connection.parameters.file

Path to the connection parameter mapping file

${manta.dir.scenario}/etc/
ifpcConnectionParameters.prm

ifpc.extractor.connection.parameters.encoding

Encoding of the connection parameter mapping file. See Encodings for applicable values.

utf-8

ifpc.connection.definition.file

Path to the connection definition settings file

${manta.dir.temp}/ifpc/
${ifpc.extractor.repository}/
ifpcConnectionDefinition.prm

ifpc.connection.definition.encoding

Encoding of the connection definition settings file. See Encodings for applicable values.

UTF-8

ifpc.connection.definition.manual.file

Path to the manual connection definition settings file

This file has the same format as the ifpc.connection.definition.file and should be used to override automatically extracted connection definitions with different values for existing connections, to add new values to existing connections, or to add additional connection definitions manually.

${manta.dir.input}/ifpc/
${ifpc.extractor.repository}/
ifpcConnectionDefinition.prm

ifpc.connection.definition.manual.encoding

Encoding of the manual connection definition settings file. See Encodings for applicable values.

UTF-8

ifpc.service.settings.file

Path to the integration service settings file

${manta.dir.temp}/ifpc/
${ifpc.extractor.repository}/
ifpcServiceSettings.prm

ifpc.service.settings.encoding

Encoding of the integration service settings file. See Encodings for applicable values.

UTF-8

ifpc.connection.definition.batchsize

Number of connection definitions that should be extracted at once (recommended values 1–100)

100

ifpc.extractor.workflows.batchsize

Number of workflows that should be extracted at once (recommended values 1–100)

1

ifpc.parameter.files.encoding

Encoding of Informatica PowerCenter parameter files. See Encodings for applicable values.

UTF-8

ifpc.indirect.files.encoding

Encoding of Informatica PowerCenter indirect files. See Encodings for applicable values.

UTF-8

ifpc.parameter.file.mapping.file

Use the file specified in this property to specify the parameter file(s) to be used when analyzing specific workflows. This is needed in cases where the parameter file is not specified in the workflow/session itself but is passed during execution only.

Enter a path to the custom parameter file CSV mapping file (separated by commas) with the columns:

  1. folder.workflow

  2. Path to the parameter filename

  3. Suffix to be used for the workflow

For example:

SALES_ORDERS.wf_DEAL,c:/mantaflow/cli/input/ifpc/INFA_REP/ParameterFiles/wf_DEAL_PDO.parm,PDO

${manta.dir.input}/ifpc/
${ifpc.extractor.repository}/
ifpcParameterFileMapping.csv

ifpc.parameter.file.mapping.encoding

Enter an encoding of the custom parameter files mapping file. See Encodings for applicable values.

UTF-8

ifpc.parameter.file.mapping.session

Enter true if you also want to override session-level parameter files, false otherwise (default)

false

true

ifpc.command.call.enabled

Enter true if you want to export a list of command calls from all command tasks, false otherwise (default)

false
true

ifpc.command.call.file

Enter a path to the output command list file

${manta.dir.temp}/ifpc/
${ifpc.extractor.repository}/
ifpcCommands.lst

ifpc.custom.transformation.mapping.file

Enter a path to the custom transformation mapping file

The format of the CSV is:

"Full path to Transformation Instance";"Input Port";"Output Port";"Edge Type (DIRECT | FILTER)";"Description (optional)"

${manta.dir.input}/ifpc/

${ifpc.extractor.repository}/

ifpcCustomTransformationMapping.csv

ifpc.extractor.repository.encoding

Enter an encoding of the IPC repository that will be set to LANG and LC_ALL variables when calling pmrep, or leave it blank for the default (Linux only). See Encodings for applicable values.

en_US.ISO-8859-1

filepath.lowercase

Whether paths to files should be lowercase (false for case-sensitive file systems, true otherwise)

false
true

ifpc.ignore.filename.field

Controls handling of dynamically-provided filenames for lineage, and specifies whether the field ISFILENAMEFIELD in the target definition should be ignored, if present.

If set to false, no target file is created because its name is set dynamically by the value in it that comes from the data during runtime. Instead, a target definition transformation is created.

If set to true, the ISFILENAMEFIELD field is ignored and a target file is created as usual. The static value of the filename specified in the mapping (if any) will be used.

false
true