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.

Overview
Connector Details
Connector Category
Other
Connector Version
Release7.2
Releases Supported (Available from)
Release6.3
Connectivity
[How the connection is established with Other]
JDBC
Connector Features
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
Table Name
Table
Tables
table
Table
Table Data Type
Table Type
Tables
table_type
Table
Table Comments
Description
Tables
description
Column
Column Name
Column
Columns
column
Column
Column Data Type
Data Type
Columns
data_type
Column
Column Length
Length
Columns
length
Column
Column Position
Position
Columns
position
Column
Column Comments
Description
Columns
description
Column
Nullable
Nullable
Columns
nullable
Schema
Schema Name
Schema
Schemas
schema
Schema
Schema Comments
Description
Schemas
description
Relationship
Foreign Key Table
Source Table
Relationships
source_table
Relationship
Foreign Key Column
Source Column
Relationships
source_column
Relationship
Referenced Table
Target Table
Relationships
target_table
Relationship
Referenced Column
Target Column
Relationships
target_column
Relationship
Constraint Name
Relationship Name
Relationships
relationship_name
User
User Name
User
Users
user
User
Schema Permissions
Schema Permissions
Users
schema_permissions
User
Table Permissions
Table Permissions
Users
table_permissions
User
Permission Types
Permission Types
Users
permission_types
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.
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.
Service Account User Permissions
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.
Schema
DataContext.getSchemaNames()
Select
Tables
DataContext.getSchema().getTables()
Select
Columns
DataContext.getSchema().getTable().getColumns()
Select
Relationships
DataContext.getTable().getRelationships()
Select
Schema Users
Information_Schema.Schema_Privileges
Select
Table Users
Information_Schema.Table_Privileges
Select
Connection Configuration Steps
Users are required to have the Connector Creator role in order to configure a new connection.
Log into OvalEdge, go to Administration > Connectors, click + (New Connector), search for Other, and complete the required parameters.
Connector Type
By default, "Other" is displayed as the selected connector type.
Credential Manager*
Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selection.
Supported Credential Managers:
OE Credential Manager
AWS Secrets Manager
HashiCorp Vault
Azure Key Vault
License Add Ons
Auto Lineage
Supported
Data Quality
Not Supported
Data Access
Not Supported
Select the checkbox for Auto Lineage Add-On to build data lineage automatically.
Connector Name*
Enter a unique name for the Other connection
(Example: "Other_Prod").
Connector Environment
Select the environment (Example: PROD, STG) configured for the connector.
Connector description
Enter a brief description of the connector.
Server*
Enter the Server name or IP address of the Other instance.
Port*
Enter the port number of the Other instance.
Database*
Enter the database name to which the service account user has access within the Other database.
Driver*
Enter the JDBC driver required to establish the connection with the Other database.
Username*
Enter the service account username set up to access the Other database (Example: "oesauser").
Password*
Enter the password associated with the service account user.
Connection String*
Configure the connection string for the DB2 database:
Automatic Mode: The system generates a connection string based on the provided credentials.
Manual Mode: Enter a valid connection string manually
Replace placeholders with actual database details.
{sid} refers to Database Name.
Plugin Server
Enter the server’s name when running as a plugin server.
Plugin Port
Enter the port number on which the plugin is running.
Default Governance Roles
Default Governance Roles*
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.
Admin Roles
Admin Roles*
Select one or more users from the dropdown list for Integration Admin and Security & Governance Admin. All users configured in OvalEdge Security are available for selection.
No of Archive Objects
No Of Archive Objects*
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.
Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.
Bridge
Select Bridge*
If applicable, select the bridge from the drop-down list.
The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering firewall rules.
After entering all connection details, the following actions can be performed:
Click Validate to verify the connection.
Click Save to store the connection for future use.
Click Save & Configure to apply additional settings before saving.
The saved connection will appear on the Connectors home page.
Manage Connector Operations
Crawl/Profile
To perform crawl and profile operations, users must be assigned the Integration Admin role.
The Crawl/Profile button allows users to select one or more schemas for crawling and profiling.
Navigate to the Connectors page and click Crawl/Profile.
Select the schemas to crawl.
The Crawl option is selected by default. Click the Crawl & Profile radio button to run both operations.
Click Run to collect metadata from the connected source and load it into the OvalEdge Data Catalog.
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.
Click the Schedule checkbox to enable the Select Period drop-down.
Select a time period for the operation from the drop-down menu.
Click Schedule to initiate metadata collection from the connected source.
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.
Last updated
Was this helpful?

