Manta Flow IBM IGC Client Configuration
IBM IGC Connection 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, IBM cannot guarantee that the connection or integration will be successful since IBM has no control, liability, or responsibility for third-party products or services, including their performance.
- IBM InfoSphere Governance Catalog (IGC) Version 11.5.0.1 Governance Rollup 4 or newer must be installed.
- A user in the Information Governance Catalog Information Asset Administrator role needs to perform the integration with Automatic Data Lineage.
IBM IGC Connection Properties
This configuration is common for all source systems and is stored in the
igcExport.properties file.
|
Property name |
Description |
Example |
|---|---|---|
| manta.igc.apiUrl | Base URL of the REST API of the integrated IGC server | https://192.168.62.100:9445/ibm/iis/igc-rest/v1/ |
| manta.igc.loginName | User name for the IGC server | isuser |
| manta.igc.loginPassword | Password for the IGC server | password |
| manta.exportIgc.batchSize |
Exported asset count per batch ( |
10000 |
| manta.exportIgc.sourceCode.enabled | Flag whether source code should be exported to IGC | true, false |
| manta.exportIgc.transformationLogic.enabled | Flag whether or not to export the transformation logic (calculation formulas) for individual fields | true, false |
|
manta.igc.mantaLineageLink.baseUrl |
Base URL of links to Manta lineage in the format Leave empty if the Manta Server URL (the property manta.repository.url) should be used. Only applicable when
|
|
|
manta.igc.mantaLineageLink.type |
Type of link to the Manta lineage exported to IGC A Permalink (the original one, being the default option now) always points to the latest revision. This is useful as there is always an up-to-date link pointing to the very latest revision available in Manta. Revision-based links point to the exact revision from which the export was made. This is desirable in cases where the latest revision may have different content, making the permalink invalid. Default value: Permalink |
Permalink |
|
manta.igc.exportMantaDirectLineageLink |
Flag whether or not to export a link to Manta direct lineage into IGC as an attribute of a respective node in MantaModel (transformation objects, not IGC assets such as tables, views) |
true |
|
manta.igc.directLineageFilter |
Only applicable when Filter applied to Manta direct lineage referenced by the link; filter name from Manta UI should be used |
Everything |
|
manta.igc.directLineageInitialDepth |
Only applicable when Initial depth of Manta direct lineage referenced by the link |
3 |
|
manta.igc.directLineageDirection |
Only applicable when Direction of Manta direct lineage referenced by the link |
Both |
|
manta.igc.exportMantaIndirectLineageLink |
Flag whether or not to export a link to Manta indirect lineage into IGC as an attribute of a respective node in MantaModel (transformation objects, not IGC assets such as tables, views) |
true false |
|
manta.igc.indirectLineageFilter |
Only applicable when Filter applied to Manta indirect lineage referenced by the link; filter name from Manta UI should be used |
Everything |
|
manta.igc.indirectLineageInitialDepth |
Only applicable when Initial depth of Manta indirect lineage referenced by the link |
3 |
|
manta.igc.indirectLineageDirection |
Only applicable when Direction of Manta indirect lineage referenced by the link |
Both |
Certificate for HTTPS Connection to IBM IGC
IBM IGC uses a secure HTTPS connection for the REST interface by default. To establish the secure connection from Manta Flow to IBM IGC, IGC's signer certificate needs to be added to the list of Automatic Data Lineage trusted certificates. The easiest way to do it is to:
- Go to Admin UI > Configuration > CLI > Common > Common Config > Advanced > Manta Flow CLI System Connectors Truststore.
- Select *Provide a Link from the Page.
- Paste the IGC URL.
- Import the certificate that is loaded from it.
Alternatively, you can get the certificate directly from IGC as follows.
- WebSphere Administration Console
- Locate WAS Admin Console > Security > SSL certificate and key management > Key stores and certificates > NodeDefaultTrustStore > Signer certificates.