> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/connectors/connector-repositories/reporting-tool/sap-bo-universe.md).

# SAP BO Universe

This article outlines the integration with the SAP BO Universe connector, enabling streamlined metadata management through features such as crawling and lineage building (both automatic and manual).

This connector supports connectivity to SAP BusinessObjects Universe from OvalEdge deployments on Windows and Linux/MacOS using SAP BI Platform RESTful Web Services (REST APIs). It provides authentication using Enterprise Authentication (secEnterprise) and Windows Active Directory Single Sign-On (secWinAD) to access the CMS repository and retrieve Universe metadata.

<img src="/files/ddi7cBtKqbJWotE7lyfy" alt="" height="316" width="624">

## Overview

### Connector Details

<table data-header-hidden><thead><tr><th width="466"></th><th></th></tr></thead><tbody><tr><td>Connector Category</td><td>Application</td></tr><tr><td>OvalEdge Release Supported</td><td>Release6.x and later</td></tr><tr><td><p>Connectivity</p><p>[How the connection is established with SAP BO Universe]</p></td><td>REST APIs</td></tr></tbody></table>

### Connector Features

| Feature                                      | Availability |
| -------------------------------------------- | :----------: |
|                                              |              |
| Crawling                                     |       ✅      |
| Delta Crawling                               |       ❌      |
| Profiling                                    |       ❌      |
| Sample 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 SAP BO Universe and mapped to the corresponding UI assets.

<table><thead><tr><th width="166">SAP BO Universe Object</th><th width="159">SAP BO Universe Attribute</th><th>OvalEdge Attribute</th><th>OvalEdge Category</th><th>OvalEdge Type</th></tr></thead><tbody><tr><td>Schema</td><td>SI_NAME~SI_ID</td><td>schemaName</td><td>Schema</td><td>Schema</td></tr><tr><td>Table</td><td>table_name</td><td>tablename</td><td>Tables</td><td>table</td></tr><tr><td>Table</td><td>table_desc</td><td>comment</td><td>Tables</td><td>table</td></tr><tr><td>Columns</td><td>column_name</td><td>name</td><td>columnname</td><td>Columns</td></tr><tr><td>Columns</td><td>column_type</td><td>type</td><td>oecolumntype</td><td>Columns</td></tr><tr><td>Columns</td><td>column_desc</td><td>name</td><td>columntitle</td><td>Columns</td></tr><tr><td>Columns</td><td>column_code</td><td>description</td><td>wiki -> srcText</td><td>Columns</td></tr><tr><td>Columns</td><td>Array index + 1</td><td>columnPosition</td><td>columnposition</td><td>Columns</td></tr></tbody></table>

## Set up a Connection

### Prerequisites

The following are the prerequisites to establish a connection:

#### **External Supporting Files**

{% hint style="info" %}
The required external JAR files are included as part of the OvalEdge installation artifacts. Please contact the OvalEdge Team for assistance related to the driver files and configuration setup.
{% endhint %}

#### **Service Account User Permissions**

{% hint style="warning" %}
It is recommended to use a dedicated 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 SAP BO Universe administrator, as users may not have the required access to assign them independently.
{% endhint %}

<table><thead><tr><th width="158">Operations</th><th width="208">Source System</th><th>Access Permissions</th></tr></thead><tbody><tr><td>Connection Validation</td><td>SAP BusinessObjects BI Platform REST (biprws)</td><td>Valid SAP BO user account with Enterprise Authentication (secEnterprise) or Windows AD SSO (secWinAD) and CMS logon rights</td></tr><tr><td>Crawling</td><td>CMS Repository (CI_APPOBJECTS)</td><td>Read access to Universe and DSL.Universe objects with Universe listing privileges</td></tr><tr><td>Crawling</td><td>Target UNV / UNX Universes</td><td>Universe Design / Export permissions to extract Universe metadata</td></tr><tr><td>Metadata Extraction (Linux)</td><td>RPT Remote Service</td><td>Network access from the OvalEdge server to the configured RPT Remote Base URL</td></tr></tbody></table>

{% hint style="info" %}

* The connector authenticates with the SAP BusinessObjects BI Platform RESTful Web Services (biprws) and uses the configured service account to discover Universes and extract metadata.
* For Linux deployments, Universe metadata extraction is performed through the configured RPT Remote Service.
  {% endhint %}

### API Details

<table><thead><tr><th width="147">Operation</th><th width="140">HTTP Method</th><th width="184">APIs</th><th width="445">Description</th></tr></thead><tbody><tr><td>Connection Validation</td><td>POST</td><td>{baseUrl}/logon/long</td><td>Authenticates the connector using Enterprise Authentication (secEnterprise) and establishes a session with the SAP BO Universe Platform for subsequent operations.</td></tr><tr><td>Connection Validation (Windows AD SSO)</td><td>POST</td><td>{baseUrl}/logon/adsso</td><td>Authenticates the connector using Windows Active Directory Single Sign-On (secWinAD) and establishes a session with the SAP BO Universe Platform for subsequent operations.</td></tr><tr><td>Crawling (Schema)</td><td>POST</td><td>{baseUrl}/v1/cmsquery?page=1&#x26;pagesize=2000</td><td>Queries the CMS repository to retrieve the list of available Universes and their associated metadata required for metadata discovery.</td></tr><tr><td>Logoff</td><td>POST</td><td>{baseUrl}/logoff</td><td>Ends the active SAP BO Universe Platform session after connector operations are completed.</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 **SAP BO Universe,** 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="220">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "<strong>Sapbo_universe</strong>" is displayed as the selected connector type.</td></tr><tr><td>OvalEdge Installed Environment</td><td><p>Select the operating system where OvalEdge is installed.</p><ul><li><strong>Windows</strong></li><li><strong>Linux/MacOS</strong></li></ul></td></tr></tbody></table>

{% tabs %}
{% tab title="Windows" %}

<table><thead><tr><th width="191">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down 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><p>For more details, click<a href="https://docs.ovaledge.com/connectors/additional-requirements/credential-manager-configuration"> here</a>. </p></td></tr><tr><td>License Add Ons</td><td><ul><li>Select the checkbox for Auto Lineage Add-On to build data lineage automatically.</li></ul><p>For more details, click<a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/license-types-and-add-ons"> here</a>. </p></td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the SAP BO Universe connection              </p><p>(Example: "SAP BO Universe_Prod").</p></td></tr><tr><td>Connector Environment</td><td><p>Select the environment (Example: PROD, STG) configured for the connector.</p><p>For more details, click<a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/prerequisites#connector-environment"> here</a>. </p></td></tr><tr><td>Connector description</td><td>Enter a brief description of the connector.</td></tr><tr><td>Base URL*</td><td>Enter the SAP BusinessObjects BI Platform REST API URL, including the protocol, host name (or IP address), and port. Example: http://&#x3C;host>:6xx5/biprws.</td></tr><tr><td>Username*</td><td>Enter the service account username used to authenticate with the SAP BusinessObjects BI Platform. The account must have the required permissions described in the Service Account User Permissions section.</td></tr><tr><td>Password*</td><td>Enter the password associated with the specified SAP BusinessObjects service account.</td></tr><tr><td>Authentication Type*</td><td>Select the authentication type used to connect to SAP BusinessObjects. The default value is secEnterprise.</td></tr><tr><td>Filter</td><td>Enter a filter expression to limit the Universes included during metadata crawling. Leave this field blank to crawl all available Universes.</td></tr><tr><td>SAP Universe file path*</td><td>Enter the local directory path where the connector stores the extracted SAP BO Universe metadata files during processing.</td></tr><tr><td>CMS Server Name*</td><td>Enter the SAP BusinessObjects CMS server name, including the port number. Example: cmsserver:6xx0.</td></tr><tr><td>Proxy Enabled*</td><td>Select Yes to route API calls through a proxy server. Select No to bypass the proxy and connect directly.</td></tr></tbody></table>
{% endtab %}

{% tab title="Linux/MacOS" %}

<table><thead><tr><th width="191">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down 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><p>For more details, click<a href="https://docs.ovaledge.com/connectors/additional-requirements/credential-manager-configuration"> here</a>. </p></td></tr><tr><td>License Add Ons</td><td><ul><li>Select the checkbox for Auto Lineage Add-On to build data lineage automatically.</li></ul><p>For more details, click<a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/license-types-and-add-ons"> here</a>. </p></td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the SAP BO Universe connection              </p><p>(Example: "SAP BO Universe_Prod").</p></td></tr><tr><td>Connector Environment</td><td><p>Select the environment (Example: PROD, STG) configured for the connector.</p><p>For more details, click<a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/prerequisites#connector-environment"> here</a>. </p></td></tr><tr><td>Connector description</td><td>Enter a brief description of the connector.</td></tr><tr><td>Base URL*</td><td>Enter the SAP BusinessObjects BI Platform REST API URL, including the protocol, host name (or IP address), and port. Example: http://&#x3C;host>:6xx5/biprws.</td></tr><tr><td>Username*</td><td>Enter the service account username used to authenticate with the SAP BusinessObjects BI Platform. The account must have the required permissions described in the Service Account User Permissions section.</td></tr><tr><td>Password*</td><td>Enter the password associated with the specified SAP BusinessObjects service account.</td></tr><tr><td>Authentication Type*</td><td>Select the authentication type used to connect to SAP BusinessObjects. The default value is secEnterprise.</td></tr><tr><td>Filter</td><td>Enter a filter expression to limit the Universes included during metadata crawling. Leave this field blank to crawl all available Universes.</td></tr><tr><td>SAP Universe file path*</td><td>Enter the local directory path where the connector stores the extracted SAP BO Universe metadata files during processing.</td></tr><tr><td>CMS Server Name*</td><td>Enter the SAP BusinessObjects CMS server name, including the port number. Example: cmsserver:6xx0.</td></tr><tr><td>Universe Remote installation path*</td><td>Enter the installation directory of the SAP BusinessObjects client components on the remote Linux/MacOS server.</td></tr><tr><td>SAP BO RPT Remote Base Url*</td><td>Enter the base URL of the SAP BO RPT Remote Service used for metadata extraction on Linux/MacOS environments. Example: http://&#x3C;host>:&#x3C;port>.</td></tr><tr><td>Proxy Enabled*</td><td>Select Yes to route API calls through a proxy server. Select No to bypass the proxy and connect directly.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

**Default Governance Roles**

<table data-header-hidden><thead><tr><th width="220"></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"></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="220"></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="219"></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

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

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

1. Navigate to the Connectors page and click **Crawl/Profile**.
2. Select the schemas to crawl.
3. The **Crawl** option is selected by default.
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 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 **crawl** operation 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, and columns.

**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.
  * **Access Instructions**: Add notes on how data can be accessed.
  * **Business Glossary Settings:** Manage term associations at the connector level.
  * **Lineage**: Select server dialects for parsing and setting connector priority for table lineage.
  * **Others**: Configure notification recipients for metadata changes.
* **Build Lineage**: Automatically build data lineage using source code parsing.
* **Delete Connector**: Remove a connector with confirmation.

For more details on connector settings, click [here](https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/connector-settings).

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/connectors/connector-repositories/reporting-tool/sap-bo-universe.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.