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
- Create a new JSON configuration file in the lineage harvester config folder.
- Give the JSON file the same name as the value of the
Idproperty in the lineage harvester configuration file.Example The value of theIdproperty in the lineage harvester configuration file isiics-source-1. Therefore, the name of your JSON file should be iics-source-1.conf. - 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
useCollibraSystemNameis set to true in your lineage harvester configuration file, then you must specify the system name in this section.connectionsThis section contains the system connection information. This is required to reference to the system or server of the connection.
connectionNameThe name of the connection.
collibraSystemNameThe 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
connectionssection.connectionNameThe name of the connection. The name must match with the name in a connection name in the
connectionssection.databaseNameThe name of your database.
schemaNameThe name of your schema.
dialectThe 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
See an example.
{ "collibraSystemNames": { "connections": [ { "connectionName": "DG_con_standby_cmdm_clientors", "collibraSystemName": "PUBLIC", }, { "connectionName": "DG_con_dev_dg_dgiauser_su", "collibraSystemName": "PUBLIC", } ] }, "connectionDefinitions": [ { "connectionName": "DG_con_standby_cmdm_clientors", "databaseName": "main", "schemaName": "dbo", "dialect": "oracle", }, { "connectionName": "DG_con_dev_dg_dgiauser_su", "databaseName": "main", "schemaName": "dbo", "dialect": "oracle", } ] }Tip Click
to copy the example to your clipboard. - Save the configuration file.