# SAP BODS

OvalEdge connects to the SAP Business Object Data Services (BODS) Oracle database using the JDBC driver to crawl metadata, execute queries, and create lineage.

<figure><img src="https://content.gitbook.com/content/hTnkoJQml0pok9awFDhx/blobs/YvGtOhnP47YzKWYuHcqg/SAP%20BODS.webp" alt=""><figcaption></figcaption></figure>

## **Overview**&#x20;

### **Connector Details**

<table data-header-hidden><thead><tr><th width="506.5"></th><th></th></tr></thead><tbody><tr><td>Connector Category</td><td>ETL System</td></tr><tr><td><p>Connector Version</p><p><em>[OvalEdge Connector Version Information]</em></p></td><td>Release6.3.1</td></tr><tr><td><p>Connectivity</p><p><em>[How OvalEdge connects to SAP BODS ]</em></p></td><td>JDBC </td></tr><tr><td><p>SAP BODS Versions Supported </p><p><em>[SAP BODS Version from which OvalEdge started providing support]</em></p></td><td>4.2 Onwards</td></tr><tr><td><p>OvalEdge Releases Supported (Available from)</p><p><em>[OvalEdge Release Version in which the SAP BODS was included in the OvalEdge Application]</em></p></td><td>Release5.2 Onwards</td></tr></tbody></table>

### **Connector Features**

| Crawling of Metadata Objects          | Supported                                    |
| ------------------------------------- | -------------------------------------------- |
| Query Sheet                           | Supported                                    |
| Lineage                               | Supported                                    |
| Lineage                               | **Auto Lineage Sources**                     |
| Lineage                               | Parsing Source Code of Data Flows XML Files. |
| Authentication via Credential Manager | Supported                                    |
| Data Quality                          | Not Supported                                |
| DAM (Data Access Management)          | Not Supported                                |
| Bridge                                | Supported                                    |

## **Getting ready to establish a connection**&#x20;

### **Prerequisites**&#x20;

The following are the prerequisites required for establishing a connection: &#x20;

### **Whitelisting Ports**

Ensure the inbound port “1521” is whitelisted for OvalEdge to connect to the Oracle database.

### **Service Account Permissions**

| Administrator privileges are required to run these commands. |
| ------------------------------------------------------------ |

Administrators can use existing users or create new users and then grant the necessary privileges.

| **SQL**                                                                                                                                                                                                                                                                              |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <p>-- Create a user </p><p>CREATE USER oesauser IDENTIFIED BY oesauser; </p><p>-- Grant permissions </p><p>GRANT CONNECT TO oesauser; </p><p>GRANT EXECUTE ON SCHEMA INFORMATION\_SCHEMA TO oesauser; </p><p>GRANT SELECT, REFERENCES ON SCHEMA INFORMATION\_SCHEMA TO oesauser;</p> |

| Replace "**INFORMATION\_SCHEMA**" with your actual schema name before executing the command in production. |
| ---------------------------------------------------------------------------------------------------------- |

### **Validating Service Account Permissions**&#x20;

1. Using the service account credentials created, connect to any third-party tool that supports Oracle connections, such as DBeaver.
2. Using the service account details, create a new connection in the tool.
3. Test the connection. Once it is successful, click **Ok** to save the connection.
4. The connection will be added and displayed in the DBeaver navigation pane, showing all the databases and schemas to which the user has access.

## **Setup a connection**

| Only a user with a Connector Creator role can set up a connection in OvalEdge. |
| ------------------------------------------------------------------------------ |

1. Log into OvalEdge, go to Administration > Connectors, click **+ (New Connector)**, search for **SAP BODS**, and complete the specific parameters.

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

<table data-header-hidden><thead><tr><th width="220.25"></th><th></th></tr></thead><tbody><tr><td><strong>Field Name</strong></td><td><strong>Description</strong></td></tr><tr><td>Connector Type</td><td>By default, "SAP BODS" is displayed as the selected connector type.</td></tr><tr><td><strong>Connector Settings</strong></td><td></td></tr><tr><td>Credential Manager<strong>*</strong></td><td><p>Select the desired credentials manager from the dropdown list. Relevant parameters will be displayed based on your 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>OvalEdge connectors have a default license add-on for data crawling and profiling.</p><ul><li>Select the checkbox for <strong>Auto Lineage Add-On</strong> to build data lineage automatically.</li></ul></td></tr><tr><td>Connector Name<strong>*</strong></td><td><p>Enter a unique name for the SAP BODS connection.</p><p>(Example: "SAPBODS_Prod").</p></td></tr><tr><td>Connector Environment</td><td><p>Select the environment (Example: PROD, STG) configured for the connector. </p><p>Refer to the "Connector Environment" document for more details.</p></td></tr><tr><td>Server<strong>*</strong></td><td>Enter the Oracle database Server name or IP address (Example: oracle.example.com or 192.168.1.10).</td></tr><tr><td>Port<strong>*</strong></td><td>By default, the port number for the Oracle database "1521" is auto-populated. If necessary, you can change this to a different port number.</td></tr><tr><td>Database<strong>*</strong></td><td>Enter the database name to which the service account user has access within the Oracle server.</td></tr><tr><td>Database Type</td><td><p>Select the database type from the dropdown list. These database types are static values set by OvalEdge.</p><ul><li><strong>Use SID</strong> if you're working with a single Oracle instance.</li><li><strong>Use SERVICE_NAME</strong> in distributed environments with high-availability setups (like Oracle RAC).</li></ul></td></tr><tr><td>Driver*</td><td><p>By default, the Oracle driver details (Example: oracle.jdbc.driver.OracleDriver) are auto-populated. OvalEdge artifacts include the required drivers for supported databases.</p><p>If needed, you can download the jar file from the following link and place it in the external jar folder:</p><p><a href="https://ovaledge-jars.s3.amazonaws.com/third_party_jars/third_party_jars_latest/ojdbc8.jar">https://ovaledge-jars.s3.amazonaws.com/third_party_jars/third_party_jars_latest/ojdbc8.jar</a></p></td></tr><tr><td>Schema<strong>*</strong></td><td>Enter the schema name from the provided database with which the OvalEdge should connect.</td></tr><tr><td>Username<strong>*</strong></td><td>Enter the service account username set up to access the Oracle database (Example: "<em>oesauser</em>").</td></tr><tr><td>Password<strong>*</strong></td><td>Enter the password associated with the service account user (Example: "<em>password</em>").</td></tr><tr><td>Connection String</td><td><p>Configure the connection string for the Oracle database:</p><ul><li><p><strong>Automatic Mode:</strong> The system generates a connection string based on the provided credentials.</p><ul><li>Example (Oracle): </li></ul></li></ul><p>jdbc:oracle:thin:@{server}:{port}:{sid}</p><ul><li><p><strong>Manual Mode:</strong> Manually enter a valid connection string.</p><ul><li>Example (Oracle): jdbc:oracle:thin:@{server}:{1521}:{sid}</li></ul></li></ul><p>Replace placeholders with actual database details.</p><p>{sid} refers to <strong>Database Name</strong></p></td></tr><tr><td><strong>Default Governance Roles</strong></td><td></td></tr><tr><td>Default Governance Roles<strong>*</strong></td><td>Select the appropriate users or teams for each governance role from the dropdown list. All users and teams configured in OvalEdge Security are displayed for selection. </td></tr><tr><td><strong>Admin Roles</strong></td><td></td></tr><tr><td>Admin Roles<strong>*</strong></td><td>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.</td></tr><tr><td>No Of Archive Objects<strong>*</strong></td><td><p>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 <strong>Archive</strong> button and specifying the number of objects to archive.</p><p><strong>Example:</strong> Setting it to 4 retrieves the last 4 changes, shown in the 'version' column of the 'Metadata Changes' module.</p></td></tr><tr><td><strong>Bridge</strong></td><td></td></tr><tr><td>Select Bridge<strong>*</strong></td><td>The dropdown displays all the active and inactive bridges configured in the OvalEdge. Select the appropriate bridge that enables seamless connectivity between data sources without altering firewall rules.</td></tr></tbody></table>

2. After entering all connection details, you can perform the following actions:
   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.

## **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.

**Authentication Errors**

<table data-header-hidden><thead><tr><th width="77.75"></th><th width="282.5"></th><th></th></tr></thead><tbody><tr><td><strong>S. No.</strong></td><td><strong>Error Description</strong></td><td><strong>Resolution</strong></td></tr><tr><td>1</td><td>"Invalid username or password."</td><td>Verify that the correct username and password are entered. Ensure the service account has the necessary permissions, and the credentials are up-to-date.</td></tr><tr><td>2</td><td>"Authentication failed for the user."</td><td>Confirm that the service account has the correct privileges to access the repository database. Check that the account is not locked or disabled.</td></tr></tbody></table>

**Datasource Errors**

<table data-header-hidden><thead><tr><th width="80.25"></th><th width="284.25"></th><th></th></tr></thead><tbody><tr><td><strong>S. No.</strong></td><td><strong>Error Description</strong></td><td><strong>Resolution</strong></td></tr><tr><td>1.</td><td>"Could not establish a connection to the database."</td><td>Check that the server address, port number, and connection string are correctly specified. Ensure the database is running and accessible from the OvalEdge server. Verify network connectivity and firewall settings.</td></tr><tr><td>2.</td><td>"Database server not reachable."</td><td>Ensure that the database server is up and running. Verify that the correct server address and port are used and that no network issues or firewall restrictions prevent access.</td></tr><tr><td>3.</td><td>"Oracle connection failed."</td><td>Verify that the correct Oracle driver is used and that the server address, port, and database name are correctly specified. Check that the Oracle instance is up and accessible.</td></tr></tbody></table>

## **Manage Connector Operations**

### **Configure Settings for Connector Operations**

**Lineage Settings for ETL Connectors:** Lineage settings are enabled by default, allowing you to select multiple sources for lineage building. Choose server dialects for parsing source codes, ensuring at least one is selected. Configure table priority to specify the order in which tables with the same name or signature are considered for lineage.

### **Crawl/Profile**

| Integration Admin privileges are required for Crawl/Profile operations. |
| ----------------------------------------------------------------------- |

Crawl and Profile operations enable you to select one or more jobs from a list of all available jobs within a specific database. This allows you to customize the selection of crawling operations according to your requirements. Furthermore, it provides the option to schedule crawling.

### **Other Operations**

The **Connectors page** in OvalEdge provides a centralized view of all configured connectors, including their health status. You can view, edit, validate, build lineage, and delete connectors using the **Nine Dots** menu.

#### 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., Databases, Tables, Table Columns, and Codes) via the **View** icon.

#### **Nine Dots Menu Options**:

* **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 by parsing source code of data flows XML files.
* **Delete Connector**: Remove connectors or schemas with confirmation.

## **Limitations**

| **S.No.** | **Description** |
| --------- | --------------- |
| **None**  |                 |

## **FAQs**

* **What is the current SSL/TLS version used for OvalEdge connectors?**&#x20;
  * **OvalEdge uses the TLS 1.2/1.3 version.**
* **Is everything crawled using https TLS 1.2?** \
  \&#xNAN;**(Do all OvalEdge connectors use HTTPS/TLS 1.2?).**<br>
  * Support for SSL/TLS is not mandated in the JDBC specification. So, we cannot expect it from every driver. PostgreSQL and Redshift do have SSL support. Other connectors mentioned in your list use HTTPS.

## **Planned Upgrades**

| **S.No.** | **Expected Date** | **Upgrade Version** | **Description** |
| --------- | ----------------- | ------------------- | --------------- |
| **None**  |                   |                     |                 |

***

Copyright © 2025, OvalEdge LLC, Peachtree Corners GA USA