OAS7
OvalEdge uses Greenplum JDBC to connect to the OAS7 data source. It allows users to crawl data objects (Reports, Report Columns, Folders).
Overview
Connector Details
Connector Category
Reporting Systems
Current Connector Version
6.3.1.2
Connectivity
[How OvalEdge connects to OAS7]
Greenplum JDBC
OAS7 Versions
Not Applicable
OvalEdge Releases Supported (Available from)
Release6.3.x onwards
Connector Capabilities
The connector capabilities are shown below.
Crawling
Feature
Supported Objects
Crawling
Analysis Report
Subject Area Report
Publisher Report
Data Model
Dashboard
Profiling
Feature
Supported Objects
Table Profiling
Not supported
View Profiling
Not supported
Column Profiling
Not supported
Full Profiling
Not supported
Sample Profiling
Not supported
Lineage Building
Lineage entities
Details
Table Lineage
NA
Column Lineage
NA
Lineage Sources
Auto Lineage via parsing JSON File
Querying
Operation
Details
Select
NA
Insert
NA
Update
NA
Delete
NA
Joins within database
NA
Joins outside database
NA
Aggregations
NA
Group By
NA
Order By
NA
Union
NA
Prerequisites
The following are the prerequisites to establish a connection between OAS7 and OvalEdge:
Whitelisting Ports
Ensures that the inbound port “5432” is whitelisted to allow OvalEdge to connect to the OAS7 database.
Important:
The default port number for the OAS7 data source is 5432. If a different port is used, ensure it is whitelisted and that communication is established between OvalEdge and the OAS7 source.
Service Account User Permissions
Important: OvalEdge recommends a dedicated service account for the system's operation.
Operation
Minimum Access Permission
Connector Validation
READ Role Access to the Schema miskw_metadata,miskw_repository
Crawling
READ Role Access to the Schema miskw_metadata,miskw_repository
Lineage
READ Role Access to the Schema miskw_metadata,miskw_repository,md_obiee_repository
Delta Crawl
Not Applicable
Setup a Connection
Important: You must have the Connector Creator role to set up a connection in OvalEdge.
Log into OvalEdge, go to Administration > Connectors, click + (New Connector), search for OAS7, and complete the specific parameters.
Note: Fields marked with an asterisk (*) are mandatory for establishing a connection. In the OvalEdge application, the OAS7 connector allows you to crawl the data using Basic Authentication(User Name & Password).
Authentication
Basic Authentication
Connector Settings
Credential Manager*
Select the desired credentials manager from the dropdown list. Relevant parameters will be displayed based on your 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.
Auto Lineage
Supported
Data Quality
Not Supported
Data Access
Not Supported
Connector Name
Enter a unique name for the OAS7 connection.
(Example: "OAS7_Prod").
Connector Environment
Select the environment (e.g., PROD, STG) configured for the connector.
Server*
Enter the OracleAnalytics Server name or IP address (Example: oracle.example.com or 192.168.1.10).
Port*
By default, the port number for the OAS7 "5432" is auto-populated. If necessary, you can change this to a different port number.
Database*
Enter the OAS7 database name.
Driver*
By default, the OAS7 driver details (Example: com.pivotal.jdbc.GreenplumDriver) are auto-populated. OvalEdge artifacts include the required drivers for supported databases.
Username*
Enter the OAS7 Username
Password*
Enter the OAS7 Password
Connection String
Configure the connection string for the OAS7 database:
Automatic Mode: The system generates a connection string based on the provided credentials.
Example (OAS7):
jdbc:pivotal:greenplum://{server}:5432;database={sid}
Manual Mode: Manually enter a valid connection string by enabling the toggle.
Example (OAS7): jdbc:pivotal:greenplum://{server}:5432;database={sid}
Replace placeholders with actual database details.
{sid} refers to Database Name.
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 and Governance Admin. All users configured in OvalEdge Security are available for selection.
No Of Archive Objects*
It indicates the number of recent metadata changes to a dataset at the source. By default, it is off. You can enable it by toggling the Archive button and specifying the number of objects to archive.
Example: Setting it to 4 retrieves the last 4 changes, shown 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, you can perform the following actions:
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.
Connectivity Troubleshooting
If incorrect parameters are provided, you may encounter error messages. To resolve these issues, ensure all input is correct. If problems persist, contact your assigned OvalEdge support team.
S.No.
Error Message(s)
Error Description/Resolution
1
Connection Timeout
Error Description: Getting timeout exception or firewall
Resolution: Ping or use telnet to check the server and port. If you encounter a timeout issue, make sure to open port 5432 for the OvalEdge server.
Example: ping 18.19.29.12 telnet IP address port
2
Not able to reach the server
Error Description: Error while validating the connection.
Resolution: Need to check the communication between the Greenplum and the OvalEdge server.
Connector health status
Health status of connectors can be identified using the colour code available under the Connector Health.
If the connector is not validated the error message will be displayed in the details section.
Manage Connector Operations
Configure Settings for Connector Operations
The OAS7 connector offers various settings to customize metadata cataloging and access. These include:
Crawler: Configure metadata that needs to be extracted.
Access Instructions: Specify how data can be accessed as a note.
Business Glossary Settings: Manage term associations at the connector level.
Lineage: This option allows configuring multiple dialects (by selecting Source Server Type for lineage) and connection priority lists for selecting tables to build a lineage.
Others: Configure notification recipients for metadata changes.
Connector Settings:
To view or edit the settings after the connector establishment follow the below screenshot and navigate to the settings of the selected connector.
Crawler Setting:
The crawler settings applied for the OAS7.
Business Glossary Setting:
The business glossary setting initially done at the connector level.These settings will also be available at the term level.
Lineage setting The lineage setting is crucial and helps in mapping the lineage within OAS7 with the RDBMS / Warehouse associated.
Crawl/Profile
Important: You must have the Integration Admin role in OvalEdge for crawl/profile operations.
A Crawl/Profile button allows you to select one or more Report Groups for crawling.
Navigate to the Connectors page and click Crawl/Profile. It allows you to select the Report Groups that need to be crawled.
The crawl option is selected by default.
Click on the Run button, which gathers all metadata from the connected source and puts it into the OvalEdge Data Catalog. After a successful crawl, all the information is displayed in the Data Catalog > Report / Report Column Tab.
Build Lineage:
Build lineage will allow the Users to build the lineage.
Additional Settings (Custom Fields):
In order to fetch and show the extended metadata information OvalEdge uses custom fields.Based on the requirement on the connector the shown custom fields are added and metadata information is shown in the data catalog object level.
The custom fields added to the OAS7 on Report.
Note: All the custom fields added will be at Connector level only.
Catalog of OAS7:
Report View
The ideal Report crawled and metadata information shown on the summary page.
Report Columns View
The columns metadata shown in the column summary page.
Lineage View
Lineage view at Report level.
Column mapping at report level graphical view. Code/Query view Lineage at column level. 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 performance with a green (active) or red (inactive) icon, helping monitor data flow and address issues early.
Viewing: Shows connector details (e.g., Domains, Reports, Report Columns, etc) via the View icon.
Nine Dots Menu Options:
You can view, edit, validate, and delete connectors using the Nine Dots menu.
Edit Connector: Update and revalidate the data source.
Validate Connector: Check the connection's integrity.
Settings: Modify connector settings.
Build Lineage: Automatically build data lineage using source code parsing.
Delete Connector: Remove connectors with confirmation.
What Metadata does OvalEdge Crawl
Source Object Naming
OvalEdge Naming
OvaEdge Category
OvalEdge Type
Folder
Report Group
Report Group
-
Publisher Report
Report Name
Reports
Publisher Report
Analysis Report
Report Name
Reports
Analysis Report
Subject Area Report
Report Name
Reports
Subject Area Report
Data Model
Report Name
Reports
Data Model
Dashboard
Report Name
Reports
Dashboard
Column_Name
Column
Report Columns
Report Column
Queries
The following queries are required to crawl, fetch remote reports, and report source code to build lineage for the OAS7.
Crawling
This requires Access to rpt_catalog_fold_data_table
SQL
select folder, STRING_AGG(type, ', ') AS type FROM (select rptfold.folder, 'Catalog Folder' AS type
from miskw_metadata.rpt_catalog_fold_data_table rptfold
union select rptanal.folder, 'Catalog Analysis Folder' AS type
from miskw_metadata.rpt_catalog_analy_data_table rptanal) AS combined
GROUP by folder
This requires Read Access to catalog_dashboardpages_data table.
SQL
select distinct rcfdt.folder,'Dashboard' as type from
miskw_repository.catalog_dashboardpages_data rcfdt
Fetching Remote Reports This requires Read Access to rpt_catalog_analy_data_table table
SQL
select CONCAT(name, '.', subject_area) AS subject_area, folder, path,
acl from miskw_metadata.rpt_catalog_analy_data_table
where folder = 'folderPath'
select distinct folder from
miskw_repository.catalog_dashboardpages_data db where db.folder = ?
Lineage Building
The source code is fetched using the queries below, which are responsible for building the lineage.
This requires Read access to the following tables to get the source code.
rpt_catalog_analy_data_table
md_obiee_repository
catalog_dashboardpages_data
vw_publisher_reports_data
rpt_catalog_fold_data_table
SQL to Fetch Subject Area Source code
SQL
select rcadt.name,rcadt.path, CONCAT(rcadt.name, '.',
rcadt.subject_area) AS subject_area,
mor.presentation_table,array_agg(distinct mor.presentation_column) AS
presentationcolumns,
mor.logical_table, array_agg(distinct mor.logical_column) as
logicalcolumns,array_agg(distinct mor.physical_column) as
physicalcolumns,
mor.md_database as diaelecttype, mor.physical_catalog as
physicaldatabase, mor.physical_schema,
mor.physical_table
from miskw_metadata.rpt_catalog_analy_data_table rcadt
join miskw_repository.md_obiee_repository mor on mor.subject_area =
rcadt.subject_area
join miskw_repository.catalog_dashboardpages_data db on
db.bippath_rpt= rcadt.path
where db.folder = ''
group by mor.presentation_table, mor.logical_table,
mor.physical_table,
mor.md_database,
mor.physical_catalog,mor.physical_schema,rcadt.name,rcadt.subject_area
,rcadt.path
SQL to Fetch Analysis SourceCode
SQL
select distinct rcadt.name, rcadt.subject_area as subject_area,
rcadt.path from miskw_metadata.rpt_catalog_analy_data_table rcadt
join miskw_repository.md_obiee_repository mor on mor.subject_area =
rcadt.subject_area
join miskw_repository.catalog_dashboardpages_data db on
db.bippath_rpt= rcadt.path
where db.folder = 'reportfolderpath'
SQL to fetch Publisher Reports Source Code
SQL
select vwpubrep.*, cfd.path as report_path from
miskw_repository.vw_publisher_reports_data vwpubrep
join miskw_metadata.rpt_catalog_fold_data_table cfd on cfd.name =
vwpubrep.report_name
join miskw_repository.catalog_dashboardpages_data db on
db.bippath_rpt= REGEXP_REPLACE(cfd.path, '^/shared', '')
where db.folder = 'reportfolderpath'
Limitations
Category
Description
Crawling
Not Identified
Profiling
Not Applicable
Lineage
Not Identified
Data Quality
Not Applicable
Report Preview
Unable to view the Report Preview
Was this helpful?