# Informatica PowerCenter

This article outlines the integration with the Informatica PowerCenter connector, enabling streamlined metadata management through features such as crawling and lineage building (both automatic and manual). It also ensures secure authentication via Credential Manager.

<figure><img src="https://1813356899-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhTnkoJQml0pok9awFDhx%2Fuploads%2FlT4kcPBmUpvpi5KDgRxj%2Funknown.png?alt=media&#x26;token=bed69c96-526e-432f-b151-8277acb4682a" alt=""><figcaption></figcaption></figure>

## Overview

### Connector Details

<table data-header-hidden><thead><tr><th width="400.666748046875"></th><th></th></tr></thead><tbody><tr><td>Connector Category</td><td>ETL Tool</td></tr><tr><td>Connector Version</td><td>Release7.2.3</td></tr><tr><td>Releases Supported (Available from)</td><td>Release5.3</td></tr><tr><td><p>Connectivity</p><p>[How the connection is established with Informatica PowerCenter]</p></td><td>REST APIs</td></tr><tr><td>Verified Informatica PowerCenter Version</td><td>10 and above</td></tr></tbody></table>

{% hint style="info" %}
The Informatica PowerCenter connector has been validated with the mentioned "Verified Informatica PowerCenter Versions" and is expected to be compatible with other supported Informatica PowerCenter versions. If there are any issues with validation or metadata crawling, please submit a support ticket for investigation and feedback.
{% endhint %}

### Connector Features

| Feature                                      | Availability |
| -------------------------------------------- | :----------: |
| Crawling                                     |       ✅      |
| Delta Crawling                               |       ❌      |
| Data Preview                                 |       ❌      |
| Auto Lineage                                 |       ✅      |
| Manual Lineage                               |       ✅      |
| Secure Authentication via Credential Manager |       ✅      |
| Data Quality                                 |       ❌      |
| DAM (Data Access Management)                 |       ❌      |
| Bridge                                       |       ✅      |

#### Metadata Mapping

The following objects are crawled from Informatica PowerCenter and mapped to the corresponding UI assets.

<table><thead><tr><th width="264">Informatica PowerCenter Object</th><th width="269.3333740234375">Informatica PowerCenter Attribute</th><th width="206.6666259765625">OvalEdge Attribute</th><th width="182.333251953125">OvalEdge Category</th><th width="197">OvalEdge Type</th></tr></thead><tbody><tr><td>WorkFlows</td><td>Workflow Name</td><td>Code Name</td><td>Codes</td><td>IPC_Workflow</td></tr><tr><td>Worklets</td><td>Worklet Name</td><td>Code Name</td><td>Codes</td><td>IPC_Task_Worklet</td></tr><tr><td>Sessions</td><td>Session Name</td><td>Code Name</td><td>Codes</td><td>IPC_Task_Session</td></tr><tr><td>Mappings</td><td>Mapping Name</td><td>Code Name</td><td>Codes</td><td>IPC_Mapping</td></tr><tr><td>Transformation</td><td>Transformation Name</td><td>Code Name</td><td>Codes</td><td>IPC_Transformation_&#x3C;Transformation_Type></td></tr><tr><td>Many other types from IPC_TASK_&#x3C;Tasks> and IPC_Transformation_&#x3C;types></td><td>-</td><td>-</td><td>-</td><td><p>IPC_Task_&#x3C;type></p><p>IPC_Transformation_&#x3C;type></p></td></tr></tbody></table>

## Set up a Connection

### Prerequisites

The following are the prerequisites to establish a connection:

#### **Whitelisting Ports**

Make sure that inbound port is whitelisted to enable successful connectivity with the Informatica PowerCenter database.

{% hint style="warning" %}
Ensure that the updated port number is specified during connection setup, the port is whitelisted, and communication between the system and Informatica PowerCenter is properly established.
{% endhint %}

#### **Service Account User Permissions**

{% hint style="warning" %}
It is recommended to use a separate service account to establish the connection to the data source, configured with the following minimum set of permissions.
{% endhint %}

{% hint style="info" %}
👨‍💻Who can provide these permissions? These permissions are typically granted by the Informatica PowerCenter administrator, as users may not have the required access to assign them independently.
{% endhint %}

| Operations | Objects       | Access Permission |
| ---------- | ------------- | ----------------- |
| Crawling   | Datasets      | Select            |
| Lineage    | Schema        | -                 |
| Lineage    | Tables        | -                 |
| Lineage    | Table Columns | -                 |

### Connection Configuration Steps

{% hint style="warning" %}
Users are required to have the Connector Creator role in order to configure a new connection.
{% endhint %}

1. Log into OvalEdge, go to Administration > Connectors, click + (New Connector), search for Informatica PowerCenter, and complete the required parameters.

{% hint style="info" %}
Fields marked with an asterisk (\*) are mandatory for establishing a connection.
{% endhint %}

<table><thead><tr><th width="219.3333740234375">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "Informatica PowerCenter" is displayed as the selected connector type.</td></tr><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selection.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp</li><li>Azure Key Vault</li></ul></td></tr><tr><td>License Add Ons</td><td><p></p><ul><li>Select the checkbox for the Auto Lineage Add-On to build data lineage automatically.</li></ul></td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the Informatica PowerCenter connection              </p><p>(Example: "IPCdb").</p></td></tr><tr><td>Connector Environment</td><td>Select the environment (Example: PROD, STG) configured for the connector.</td></tr><tr><td>Connector Description</td><td>Enter a brief description of the connector.</td></tr><tr><td>Informatica Database</td><td><p>The following four types of Informatica Database are supported for Informatica PowerCenter:</p><ul><li>SQL Server</li><li>Oracle</li><li>DB2</li><li>Postgres</li></ul></td></tr></tbody></table>

{% tabs %}
{% tab title="SQL Server" %}

<table><thead><tr><th width="190.6666259765625">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Authentication*</td><td><p>The following two types of Authentication are supported for Informatica PowerCenter:</p><ul><li>SQL Server Authentication</li><li>Windows Authentication</li></ul></td></tr><tr><td>OvalEdge Installed Environment</td><td><p>The following two types of Environment are supported for Informatica PowerCenter:</p><ul><li>linux/unix</li><li>Windows</li></ul><p><strong>Note</strong>: This field appears only when Authentication is selected as Windows Authentication.</p></td></tr><tr><td>Server*</td><td>Enter the Server name or IP address of the Informatica PowerCenter instance.</td></tr><tr><td>Port*</td><td>Enter the port number of the Informatica PowerCenter instance.</td></tr><tr><td>Database*</td><td>Enter the database name to which the service account user has access within the Informatica PowerCenter Database.</td></tr><tr><td>Domain</td><td><p>Enter the verified Informatica PowerCenter Database domain name.</p><p><strong>Note</strong>: This field is enabled only when the application is installed in a Linux/UNIX environment.</p></td></tr><tr><td>Repository Schema</td><td>Enter the name of the Repository Schema.</td></tr><tr><td>Driver*</td><td>By default, the Informatica PowerCenter driver details are auto-populated.</td></tr><tr><td>Username*</td><td>Enter the service account username set up to access the Informatica PowerCenter (Example: "oesauser").<br><strong>Note</strong>: This field is disabled only when the OvalEdge Installed Environment is selected as windows environment.</td></tr><tr><td>Password*</td><td>Enter the password associated with the service account user.<br><strong>Note</strong>: This field is disabled only when the OvalEdge Installed Environment is selected as windows environment.</td></tr><tr><td>Connection String</td><td><p>Configure the connection string for the Azure SQL database:</p><ul><li><strong>Automatic Mode</strong>: The system generates a connection string based on the provided credentials.</li><li><strong>Manual Mode</strong>: Enter a valid connection string manually.</li></ul><p>Replace placeholders with actual database details.</p><p>{sid} refers to Database Name</p></td></tr><tr><td>Parameter Files Directory</td><td>Enter the path to Parameter Files.</td></tr><tr><td>Parameter Files Root Directory Path</td><td>Enter the path to Parameter Files Root Directory.</td></tr></tbody></table>
{% endtab %}

{% tab title="Oracle" %}

<table><thead><tr><th width="192">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Server*</td><td>Enter the Server name or IP address of the Informatica PowerCenter instance.</td></tr><tr><td>Port*</td><td>Enter the port number of the Informatica PowerCenter instance.</td></tr><tr><td>Database*</td><td>Enter the database name to which the service account user has access within the Informatica PowerCenter Database.</td></tr><tr><td>Repository Schema</td><td>Enter the name of the Repository Schema.</td></tr><tr><td>Driver*</td><td>By default, the Informatica PowerCenter driver details are auto-populated.</td></tr><tr><td>Username*</td><td>Enter the service account username set up to access the Informatica PowerCenter (Example: "oesauser").</td></tr><tr><td>Password*</td><td>Enter the password associated with the service account user.</td></tr><tr><td>Connection String</td><td><p>Configure the connection string for the Azure SQL database:</p><ul><li>Automatic Mode: The system generates a connection string based on the provided credentials.</li><li>Manual Mode: Enter a valid connection string manually.</li></ul><p>Replace placeholders with actual database details.</p><p>{sid} refers to Database Name</p></td></tr><tr><td>Parameter Files Directory</td><td>Enter the path to Parameter Files.</td></tr><tr><td>Parameter Files Root Directory Path</td><td>Enter the path to Parameter Files Root Directory.</td></tr></tbody></table>
{% endtab %}

{% tab title="DB2" %}

<table><thead><tr><th width="192">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Server*</td><td>Enter the Server name or IP address of the Informatica PowerCenter instance.</td></tr><tr><td>Port*</td><td>Enter the port number of the Informatica PowerCenter instance.</td></tr><tr><td>Database*</td><td>Enter the database name to which the service account user has access within the Informatica PowerCenter Database.</td></tr><tr><td>Repository Schema</td><td>Enter the name of the Repository Schema.</td></tr><tr><td>Driver*</td><td>By default, the Informatica PowerCenter driver details are auto-populated.</td></tr><tr><td>Username*</td><td>Enter the service account username set up to access the Informatica PowerCenter (Example: "oesauser").</td></tr><tr><td>Password*</td><td>Enter the password associated with the service account user.</td></tr><tr><td>Connection String</td><td><p>Configure the connection string for the Azure SQL database:</p><ul><li>Automatic Mode: The system generates a connection string based on the provided credentials.</li><li>Manual Mode: Enter a valid connection string manually.</li></ul><p>Replace placeholders with actual database details.</p><p>{sid} refers to Database Name</p></td></tr><tr><td>Parameter Files Directory</td><td>Enter the path to Parameter Files.</td></tr><tr><td>Parameter Files Root Directory Path</td><td>Enter the path to Parameter Files Root Directory.</td></tr></tbody></table>
{% endtab %}

{% tab title="Postgres" %}

<table><thead><tr><th width="193.3333740234375">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Server*</td><td>Enter the Server name or IP address of the Informatica PowerCenter instance.</td></tr><tr><td>Port*</td><td>Enter the port number of the Informatica PowerCenter instance.</td></tr><tr><td>Database*</td><td>Enter the database name to which the service account user has access within the Informatica PowerCenter Database.</td></tr><tr><td>Repository Schema</td><td>Enter the name of the Repository Schema.</td></tr><tr><td>Driver*</td><td>By default, the Informatica PowerCenter driver details are auto-populated.</td></tr><tr><td>Username*</td><td>Enter the service account username set up to access the Informatica PowerCenter (Example: "oesauser").</td></tr><tr><td>Password*</td><td>Enter the password associated with the service account user.</td></tr><tr><td>Connection String</td><td><p>Configure the connection string for the Azure SQL database:</p><ul><li>Automatic Mode: The system generates a connection string based on the provided credentials.</li><li>Manual Mode: Enter a valid connection string manually.</li></ul><p>Replace placeholders with actual database details.</p><p>{sid} refers to Database Name</p></td></tr><tr><td>Parameter Files Directory</td><td>Enter the path to Parameter Files.</td></tr><tr><td>Parameter Files Root Directory Path</td><td>Enter the path to Parameter Files Root Directory.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

**Default Governance Roles**

<table data-header-hidden><thead><tr><th width="219.3333740234375"></th><th></th></tr></thead><tbody><tr><td>Default Governance Roles*</td><td>Select the appropriate users or teams for each governance role from the drop-down list. All users configured in the security settings are available for selection.</td></tr></tbody></table>

**Admin Roles**

<table data-header-hidden><thead><tr><th width="219.3333740234375"></th><th></th></tr></thead><tbody><tr><td>Admin Roles*</td><td>Select one or more users from the dropdown list for Integration Admin and Security &#x26; Governance Admin. All users configured in the security settings are available for selection.</td></tr></tbody></table>

**No of Archive Objects**

<table data-header-hidden><thead><tr><th width="219.3333740234375"></th><th></th></tr></thead><tbody><tr><td>No Of Archive Objects*</td><td><p>This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive.</p><p>Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.</p></td></tr></tbody></table>

**Bridge**

<table data-header-hidden><thead><tr><th width="219.3333740234375"></th><th></th></tr></thead><tbody><tr><td>Select Bridge*</td><td><p>If applicable, select the bridge from the drop-down list.</p><p>The drop-down list displays all active bridges that have been configured. These bridges facilitate communication between data sources and the system without requiring changes to firewall rules.</p></td></tr></tbody></table>

2. After entering all **connection** details, the following actions can be performed:
   1. Click **Validate** to verify the connection.
   2. Click **Save** to store the connection for future use.
   3. Click **Save & Configure** to apply additional settings before saving.
3. The saved connection will appear on the **Connectors home page.**

## Manage Connector Operations

### Crawl

{% hint style="warning" %}
To perform crawl operations, users must be assigned the Integration Admin role.
{% endhint %}

The **Crawl/Profile** button allows users to select one or more **schemas** for crawling.&#x20;

1. Navigate to the **Connectors** page and click **Crawl/Profile**.
2. Select the **schemas** to crawl.
3. The **Crawl** option is selected by default.
4. Click **Run** to collect metadata from the connected source and load it into the **Data Catalog**.
5. After a successful crawl, the information appears in the **Data Catalog > Databases/<>Codes** tab.

The **Schedule** checkbox allows automated crawling at defined intervals, from a minute to a year.

1. Click the **Schedule** checkbox to enable the Select Period drop-down.
2. Select a time period for the operation from the drop-down menu.
3. Click **Schedule** to initiate metadata collection from the connected source.
4. The system will automatically execute the **crawl** operation at the scheduled time.

### Other Operations

The **Connectors** page provides a centralized view of all configured connectors, along with their health status.

**Managing connectors includes:**

* **Connector Health:** Displays the current status of each connector using a **green** icon for active connections and a **red** icon for inactive connections, helping to monitor the connectivity with data sources.
* **Viewing**: Click the **Eye** icon next to the connector name to view connector details, including Codes, Schemas, and Tasks.

**Nine Dots Menu Options:**

To view, edit, validate, build lineage, configure, or delete connectors, click on the Nine Dots menu.

* **Edit Connector**: Update and revalidate the data source.
* **Validate Connector**: Check the connection's integrity.
* **Settings**: Modify connector settings.
  * **Lineage**: Select server dialects for parsing and setting connector priority for table lineage.
* **Build Lineage**: Automatically build data lineage using source code parsing.
* **Delete Connector:** Remove a connector with confirmation.

### Connectivity Troubleshooting

If incorrect parameters are entered, error messages may appear. Ensure all inputs are accurate to resolve these issues. If issues persist, contact the assigned support team.

<table><thead><tr><th width="86.3333740234375">S.No.</th><th width="162">Error Message(s)</th><th>Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>Connection Timeout</td><td><p><strong>Description</strong>:</p><p>The connection attempt fails due to a delayed response from the database service.</p><p><strong>Resolution</strong>:</p><p>Verify that the database service is reachable and adjust the timeout value if required.</p></td></tr><tr><td>2</td><td>Invalid Schema or Database Name</td><td><p>Description:</p><p>The specified schema or database cannot be located.</p><p>Resolution:</p><p>Check that the schema or database name exists and is entered correctly.</p></td></tr><tr><td>3</td><td>Driver Class Not Found</td><td><p><strong>Description</strong>:</p><p>The system cannot locate the necessary driver required to establish a connection.</p><p><strong>Resolution</strong>:</p><p>Confirm that the appropriate JDBC driver is installed and accessible to the application.</p></td></tr></tbody></table>

***

Copyright © 2025, OvalEdge LLC, Peachtree Corners GA USA