Prepare Informatica Intelligent Cloud Services <source ID> configuration file

You use the lineage harvester configuration file to access Informatica Intelligent Cloud Services Data Integration data objects. The lineage harvester processes the data objects to create a technical lineage. You also have to prepare a specific <source ID> configuration file that defines the Intelligent Cloud Services system name.

Important You must prepare a <source ID> configuration file regardless of whether the useCollibraSystemName property in your lineage harvester configuration files is set to true or false.

Tip The name <source ID> configuration file refers to the value of the Id property in the lineage harvester configuration file.

Prerequisites

You have Admin permission on all objects that you want to harvest.

Steps

  1. Create a new JSON configuration file in the lineage harvester config folder.
  2. Give the JSON file the same name as the value of the Id property in the lineage harvester configuration file.
    Example The value of the Id property in the lineage harvester configuration file is iics-source-1. Therefore, the name of your JSON file should be iics-source-1.conf.
  3. For each Informatica Intelligent Cloud Services connection, you can add the following content to the JSON file:

    Property

    Description

    collibraSystemNames

    This section contains the system information for Informatica Intelligent Cloud Services.

    Important If useCollibraSystemName is set to true in your lineage harvester configuration file, then you must specify the system name in this section.

    connections

    This section contains the system 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.

    connectionDefinitions

    This section contains the database, schema en dialect information for each connection in Informatica Intelligent Cloud Services.

    Note You can add connection information for each connection in the connections section.

    connectionName

    The name of the connection. The name must match with the name in a connection name in the connections section.

    databaseName

    The name of your database.

    schemaName

    The name of your schema.

    dialect

    The dialect of the connection.

    You can enter one of the following values:

    • bigquery
    • db2
    • hana
    • hive
    • greenplum
    • mssql
    • mysql
    • netezza
    • oracle
    • postgres
    • redshift
    • snowflake
    • spark
    • teradata
  4. Save the configuration file.