# Other

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

<figure><img src="https://content.gitbook.com/content/ztcvwwOJCeaE1n6oHp4C/blobs/oBUBaddQtQwwdmhDvUVl/unknown.png" alt=""><figcaption></figcaption></figure>

## Overview

### Connector Details

| Connector Category                                                        | Other      |
| ------------------------------------------------------------------------- | ---------- |
| Connector Version                                                         | Release7.2 |
| Releases Supported (Available from)                                       | Release6.3 |
| <p>Connectivity</p><p>\[How the connection is established with Other]</p> | JDBC       |

### Connector Features

| Feature                                      | Availability |
| -------------------------------------------- | :----------: |
| Crawling                                     |       ✅      |
| Delta Crawling                               |       ❌      |
| Profiling                                    |       ✅      |
| Query Sheet                                  |       ✅      |
| 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 Other and mapped to the corresponding UI assets.

<table><thead><tr><th width="148.44451904296875">Other Object</th><th width="153.77777099609375">Other Attribute</th><th width="178.3333740234375">OvalEdge Attribute</th><th width="178.4444580078125">OvalEdge Category</th><th width="154.888916015625">OvalEdge Type</th></tr></thead><tbody><tr><td>Table</td><td>Table Name</td><td>Table</td><td>Tables</td><td>table</td></tr><tr><td>Table</td><td>Table Data Type</td><td>Table Type</td><td>Tables</td><td>table_type</td></tr><tr><td>Table</td><td>Table Comments</td><td>Description</td><td>Tables</td><td>description</td></tr><tr><td>Column</td><td>Column Name</td><td>Column</td><td>Columns</td><td>column</td></tr><tr><td>Column</td><td>Column Data Type</td><td>Data Type</td><td>Columns</td><td>data_type</td></tr><tr><td>Column</td><td>Column Length</td><td>Length</td><td>Columns</td><td>length</td></tr><tr><td>Column</td><td>Column Position</td><td>Position</td><td>Columns</td><td>position</td></tr><tr><td>Column</td><td>Column Comments</td><td>Description</td><td>Columns</td><td>description</td></tr><tr><td>Column</td><td>Nullable</td><td>Nullable</td><td>Columns</td><td>nullable</td></tr><tr><td>Schema</td><td>Schema Name</td><td>Schema</td><td>Schemas</td><td>schema</td></tr><tr><td>Schema</td><td>Schema Comments</td><td>Description</td><td>Schemas</td><td>description</td></tr><tr><td>Relationship</td><td>Foreign Key Table</td><td>Source Table</td><td>Relationships</td><td>source_table</td></tr><tr><td>Relationship</td><td>Foreign Key Column</td><td>Source Column</td><td>Relationships</td><td>source_column</td></tr><tr><td>Relationship</td><td>Referenced Table</td><td>Target Table</td><td>Relationships</td><td>target_table</td></tr><tr><td>Relationship</td><td>Referenced Column</td><td>Target Column</td><td>Relationships</td><td>target_column</td></tr><tr><td>Relationship</td><td>Constraint Name</td><td>Relationship Name</td><td>Relationships</td><td>relationship_name</td></tr><tr><td>User</td><td>User Name</td><td>User</td><td>Users</td><td>user</td></tr><tr><td>User</td><td>Schema Permissions</td><td>Schema Permissions</td><td>Users</td><td>schema_permissions</td></tr><tr><td>User</td><td>Table Permissions</td><td>Table Permissions</td><td>Users</td><td>table_permissions</td></tr><tr><td>User</td><td>Permission Types</td><td>Permission Types</td><td>Users</td><td>permission_types</td></tr></tbody></table>

## Set up a Connection

### Prerequisites

The following are the prerequisites to establish a connection:

#### **Whitelisting Ports**

Make sure that the inbound port is whitelisted to enable successful connectivity with the Other 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 the Other 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 Other administrator, as users may not have the required access to assign them independently.
{% endhint %}

<table><thead><tr><th width="145.888916015625">Objects</th><th width="405">Sys Tables</th><th>Access Permissions</th></tr></thead><tbody><tr><td>Schema</td><td>DataContext.getSchemaNames()</td><td>Select</td></tr><tr><td>Tables</td><td>DataContext.getSchema().getTables()</td><td>Select</td></tr><tr><td>Columns</td><td>DataContext.getSchema().getTable().getColumns()</td><td>Select</td></tr><tr><td>Relationships</td><td>DataContext.getTable().getRelationships()</td><td>Select</td></tr><tr><td>Schema Users</td><td>Information_Schema.Schema_Privileges</td><td>Select</td></tr><tr><td>Table Users</td><td>Information_Schema.Table_Privileges</td><td>Select</td></tr></tbody></table>

### 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 Other, 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></th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "<strong>Other</strong>" 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 Vault</li><li>Azure Key Vault</li></ul></td></tr><tr><td>License Add Ons</td><td><p></p><ul><li>Select the checkbox for 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 Other connection              </p><p>(Example: "Other_Prod").</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>Server*</td><td>Enter the Server name or IP address of the Other instance.</td></tr><tr><td>Port*</td><td>Enter the port number of the Other instance.</td></tr><tr><td>Database*</td><td>Enter the database name to which the service account user has access within the Other database.</td></tr><tr><td>Driver*</td><td>Enter the JDBC driver required to establish the connection with the Other database.</td></tr><tr><td>Username*</td><td>Enter the service account username set up to access the Other database (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 DB2 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>Plugin Server</td><td>Enter the server’s name when running as a plugin server.</td></tr><tr><td>Plugin Port</td><td>Enter the port number on which the plugin is running.</td></tr></tbody></table>

**Default Governance Roles**

<table data-header-hidden><thead><tr><th width="220.22222900390625"></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 and teams configured in OvalEdge Security are displayed for selection.</td></tr></tbody></table>

**Admin Roles**

<table data-header-hidden><thead><tr><th width="220.2222900390625"></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 OvalEdge Security 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="221.11114501953125"></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 configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering 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/Profile

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

The **Crawl/Profile** button allows users to select one or more schemas for **crawling** and **profiling**.

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

The **Schedule** checkbox allows automated crawling and profiling 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 selected operation (**Crawl** or **Crawl & Profile)** at the scheduled time.

#### Other Operations

The **Connectors** page in OvalEdge provides a centralized view of all configured connectors, including their health status.

**Managing connectors includes:**

* **Connectors 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 databases, tables, columns, and codes.

**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.
  * **Crawler**: Configure data extraction.
  * **Profiler**: Customize data profiling rules and methods.
  * **Query Policies:** Define query execution rules based on roles.
  * **Access Instructions:** Add notes on how data can be accessed.
  * **Business Glossary Settings:** Manage term associations at the connector level.
  * **Others**: Configure notification recipients for metadata changes.
* **Build Lineage:** Automatically build data lineage using source code parsing.
* **Delete Connector:** Remove a connector with confirmation.

***

Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.