Enterprise Data Catalog Scanner Configuration Guide > Configuring Data Integration Resources > Informatica Platform

Informatica Platform

Create a resource based on the Informatica Platform resource type to extract metadata from the Model repository. You need to specify the Data Integration Service connection details when you configure the resource.

Objects Extracted

Enterprise Data Catalog extracts only mapping metadata from Informatica Platform.

Prerequisites

If the domain is SSL-enabled and cluster is Kerberos enable, perform the following steps:

•Copy the SSL certificate in all the cluster machines. Ensure that the infa_truststore.jks file path is common across all the cluster machines.
•To get the encrypted password, navigate to <Informatica installation directory>/server/bin file path, and then type pmpasswd <Truststore Password> in the command line.
•Configure the following JVM parameters for the resource:

- -DINFA_TRUSTSTORE=<trust store path>
- -DINFA_TRUSTSTORE_PASSWORD=<trust store encrypted key>

Source and Target Objects for Mapping

The Informatica Platform resource can use the following source and target objects:

•Flat file
•Oracle
•Amazon Redshift
•Amazon S3
•Microsoft SQL Server
•Sybase
•Hive
•IBM DB2
•Teradata JDBC
•Teradata ODBC
•HDFS
•Azure Data Lake Store
•Microsoft Azure Blob Storage
•Azure Microsoft SQL Data Warehouse
•SAP HANA

Basic Information

The General tab includes the following basic information about the resource:

Information	Description
Name	The name of the resource.
Description	The description of the resource.
Resource type	The type of the resource.
Execute On	You can choose to execute on the default catalog server or offline.

Resource Connection Properties

The following table describes the Data Integration Service connection properties:

Property	Description
Target version	The version number of the Informatica platform. You can choose any of the following Informatica versions: - 10.2 - 10.2 HF1 - 10.2 HF2 - 10.2.1 - 10.2.2 - 10.2.2 HF1 - 10.4 - 10.4.1 - 10.5 - 10.5.1 - 10.5.2
Domain Name	Name of the Informatica domain.
Data Integration Service Name	Name of the Data Integration Service.
Username	Username for the Data Integration Service connection.
Password	Password for the Data Integration Service connection.
Security Domain	Name of the LDAP security domain if the Informatica domain contains an LDAP security domain.
Host	Host name for the informatica domain.
Port	Port number of the Informatica domain.
Application Name	Name of the Data Integration Service application. By default, all the application names are selected. To select a single application name, click Select... to select the name of the application from the Select Application Name dialog box. Note: This property applies to target versions 10.2 or later.
Param Set for Mappings in Application	Parameter set for mappings configured for the Data Integration Service application. Click Select... to select the parameter set from the Select Param Sets for Mappings in Application dialog box. Note: This property applies to target version 10.2.
Parameter Set or Parameter File	Specify whether you want to use a parameter set or parameter file in the Data Integration Service application. Note: This property is applies to target versions 10.2.1 or later.
Parameter Sets	Parameter set for mappings or workflows configured for the Data Integration Service application. The Data Integration Service application can contain a single parameter set or multiple parameter sets based on the parameter sets configured for the Data Integration Service application. You can use this property if you select a single Data Integration Service application. Click Select... to select the parameter set from the Select Param Sets dialog box. Note: This property is applies to target versions 10.2.1 or later.
Parameter Sets File	A ZIP file that contains all the parameter sets for mappings or workflows configured for the Data Integration Service applications in a .config file. Use a text editor to create the parameter sets file and name the file as ApplicationParameterSet.config, and then zip the .config file. In the <Parameter Sets> file, define the parameter sets that you want to configure for the selected Data Integration Service applications. Use a comma as a delimiter to separate the parameter sets in the file. Note: This property is applies to target versions 10.2.1 or later.
Parameter File	An XML file that lists user-defined parameters and their assigned values for mappings or workflows configured for the Data Integration Service applications. To create a parameter file, create a folder with the name of the Data Integration Service application and move the XML files that contain the mapping or workflow parameters to the folder, and then zip the folder. Note: This property applies to target versions 10.2.1 or later.

The following table describes the Additional and Advanced properties for source metadata settings on the Metadata Load Settings tab:

Property	Description
Enable Source Metadata	Extracts metadata from the data source.
Auto assign Connections	Indicates that the connections are automatically assigned.
Enable Reference Resources	Extracts metadata about assets that are not included in this resource, but referred to in the resource. Examples include source and target tables in streaming mapping, streaming sources such as Apache Kafka, and source tables and files from Tableau reports.
Retain Unresolved Reference Assets	Retains unresolved reference assets in the catalog after you assign connections. Retaining unresolved reference assets help you view the complete lineage. The unresolved assets include deleted files, temporary tables, and other assets that are not present in the primary resource.
Detailed Lineage	Enables detailed lineage for the resource. Select to extract and ingest metadata related to transformation logic for assets that include transformations. A transformation indicates generation, modification, or passage of data between source and target connections. A transformation logic displays the mappings or data flow relation types between source assets and target assets related to the asset you select in Enterprise Data Catalog.
Memory	The memory value required to run a scanner job. Specify one of the following memory values: - Low - Medium - High Note: For more information about the memory values, see the Tuning Enterprise Data Catalog Performance article.
Custom Options	JVM parameters that you can set to configure scanner container. Use the following arguments to configure the parameters: - Dscannerloglevel=<DEBUG/INFO/ERROR>. Changes the log level of scanner to values, such as DEBUG, ERROR, or INFO. Default value is INFO. - Dscanner.container.core=<No. of core>. Increases the core for the scanner container. The value should be a number. - Dscanner.yarn.app.environment=<key=value>. Key pair value that you need to set in the Yarn environment. Use a comma to separate the key pair value. - Dscanner.pmem.enabled.container.memory.jvm.memory.ratio=<1.0/2.0>. Increases the scanner container memory when pmem is enabled. Default value is 1. - -DINFA_TRUSTSTORE=<trust store path>. Path to the Informatica truststore file. - -DINFA_TRUSTSTORE_PASSWORD=<trust store encrypted key>. Encrypted truststore password.

Sample Parameter Set File

The following example shows a sample parameter set file:

Application_Map_rel_conn_param,Parameter_Set_Rel_Conn,Parameter_Set_Rel_Conn1
Application_Map_rel_schema_param,Parameter_Set_Rel_Schema
Application_Map_rel_srctable_param,Parameter_Set_Rel_ScrTblname
Application_Map_rel_conn_param

Parameter File Requirements

A parameter file is an XML file that lists user-defined parameters and their assigned values for mappings or workflows configured for the Data Integration Service applications. Use a text editor or the Informatica Developer Client to create a parameter file. To enable the Informatica Platform resource to read parameter values from a parameter file, the file must have a .xml extension. You can group parameters and variables in different sections of the parameter file.

Note: A parameter file must include only one workflow or mapping. Enterprise Data Catalog does not support parameter files that include multiple workflows or mappings.

Creating a Parameter File

To create a parameter file, perform the following steps:

1. Create a folder with the same name as the Data Integration Service application.
2. Create parameter files in the following format <file name>.xml.

Note: Each parameter file should include a specific workflow or mapping.

3. Place all the parameter file definitions of the workflow or mapping within the folder.
4. Zip the folder. The zip file can contain multiple folders containing parameter files.

Sample Parameter File

The following example shows a sample parameter file that contains a workflow:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<root>
<project name="ABC">
<workflow name="Name1">
<parameter name="Param1">Parameter1</parameter>
</workflow>
</project>
</root>

Scanner Binaries File

The ScannerBinaries.zip file only includes the Informatica Platform resource binary files for the current release. The binary files for earlier Informatica versions are included in the ExtendedScannerBinaries.zip file.