Oracle Service Cloud
This article outlines the integration with the Oracle Service Cloud connector, enabling streamlined metadata management through features such as crawling, profiling, data preview, and manual lineage building. It also ensures secure authentication via Credential Manager.
Connector Details
Connector Category
Application
Connector Version
Release7.x
Releases Supported (Available from)
Release6.x
Connectivity
[How the connection is established with Oracle Service Cloud]
REST APIs
Verified Oracle Service Cloud Version
All Versions
The Oracle Service Cloud connector has been validated and is expected to be compatible with all Oracle Service Cloud versions. If there are any issues with validation or metadata crawling, please submit a support ticket for investigation and feedback.
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 Oracle Service Cloud and mapped to the corresponding UI assets.
End point: /metadata-catalog
Name
Table
Tables
Table
End point: /metadata-catalog
Label
Table Title
Tables
Table
End point: /metadata-catalog
Description
Source Description
Descriptions
Source Description
End point: /metadata-catalog
inside properties
Property Key
Column
Table Columns
-
End point: /metadata-catalog
inside properties
Description
Source Description
Table Columns
-
End point: /metadata-catalog
inside properties
Label
Column Title
Table Columns
-
End point: /metadata-catalog
inside properties
MaxLength
Data Type Size
Table Columns
-
Set up a Connection
Prerequisites
The following are the prerequisites to establish a connection:
Service Account User Permissions
Use a dedicated service account to establish the connection to the data source, configured with the following minimum set of permissions.
👨💻Who can provide these permissions? The Oracle Service Cloud administrator grants these permissions, as users may not have the required access to assign them independently.
API Level
Connect REST API Access
Endpoint Level
Metadata Catalog Read
Endpoint Level
Query Execution
Resource Level
Resource Read Access
User Level
Basic Authentication
Connection Configuration Steps
Users must have the Connector Creator role to configure a new connection.
Log into OvalEdge, go to Administration > Connectors, click + (New Connector), search for Oracle Service Cloud, and complete the required parameters.
Fields marked with an asterisk (*) are mandatory for establishing a connection.
Connector Type
By default, "OracleServiceCloud" 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
Connector Name*
Enter a unique name for the Oracle Service Cloud connection (Example: "OracleServiceCloud_Prod").
Connector Environment
Select the environment (Example: PROD, STG) configured for the connector.
Connector Description
Enter the description related to the connector.
End Point*
Enter the Oracle Service Cloud domain URL in the End Point field.
Username*
Enter the Oracle Service Cloud account’s login ID configured for API access.
Password*
Enter the password associated with the Oracle Service Cloud Username.
Proxy Enabled*
Select Yes to enable proxy settings or No to connect directly without a proxy.
Default Governance Roles
Default Governance Roles*
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.
Admin Roles
Admin Roles*
Select one or more users from the dropdown list for Integration Admin and Security & Governance Admin. All users configured in the security settings are available for selection.
Bridge
Select Bridge*
Select the bridge from the drop-down list.
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.
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. To perform both operations, select the Crawl & Profile radio button.
Click Run to collect metadata from the connected source and load it into the 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:
Connector Health: Displays the current status of each connector, with a green icon for active connections and a red icon for inactive connections, helping monitor connectivity to data sources.
Viewing: Click the Eye icon next to the connector name to view connector details.
Nine Dots Menu Options:
To view, edit, validate, 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.
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.
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.
1
OSC-CREST-00002An unsupported HTTP method was used.
Description: The request was sent using an HTTP method that is not supported by the target REST API endpoint. Resolution:
Use a supported HTTP method (for example, GET, POST, or PATCH) for the endpoint.
Verify that the configured HTTP method matches the operation supported by the target endpoint.
2
OSC-CREST-00003An unsupported version of Connect REST API was used.
Description: The request was made using a Connect REST API version that is not supported.
Resolution:
Switch to a supported API version.
Verify the API version specified in the request URL and headers.
3
OSC-CREST-00022The limit parameter value has exceeded the permissible limit.
Description: The value specified for the limit parameter exceeds the maximum allowed value. A maximum of 20,000 rows can be returned in a single request. Resolution:
Ensure the limit parameter value does not exceed 20,000.
Use pagination or successive requests to retrieve additional records.
4
OSC-CREST-00035The server is busy. Please try again after some time.
Description: The server is currently busy and unable to process the request.
Resolution:
Retry the request after some time.
Implement retry logic with exponential backoff in the integration.
Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.
Was this helpful?