Publish a Knowledge Catalog (formerly Dataplex Universal Catalog) data product to SAP Business Data Cloud (BDC) using BigLake Delta Sharing.
Publishing a data product to SAP enables users within the SAP ecosystem to discover and consume Google Cloud data assets seamlessly. This integration leverages Delta Sharing to expose underlying data assets such as Apache Iceberg REST catalog tables as read-only federated tables. Because the data remains in its original location, there is no data movement or replication, ensuring lower latency and maintaining a single source of truth.
Overview
The integration between Knowledge Catalog and SAP BDC relies on an open-protocol approach using Delta Sharing. When you publish a data product to SAP, Knowledge Catalog facilitates the creation of a secure sharing link.
Key technical aspects of this integration include the following:
- Federated access: Assets are presented in SAP as federated tables, meaning they are queried in real-time from Google Cloud storage.
- Delta Sharing: Knowledge Catalog acts as a Delta Sharing server, providing a standard interface for external clients like SAP to access BigLake and Iceberg tables.
- No data movement: Your data stays in Google Cloud. Only the metadata and secure access protocols are shared with the SAP environment.
- Security: Authentication and authorization are handled using Workload Identity Federation, ensuring that only authorized SAP users can access the data based on the permissions granted in Google Cloud.
Before you begin
Before you publish a data product to SAP BDC, complete the following prerequisites:
Enable APIs
Enable the BigLake API on your Google Cloud project.
Delta Sharing and catalog requirements
Ensure that your environment meets the following requirements:
| Requirement | Details | Reference |
|---|---|---|
| Delta Sharing catalog | You must have a BigLake Delta Sharing catalog created and enrolled with your SAP BDC environment in the same project and region as your data product. | See Set up borderless Lakehouse for SAP Business Data Cloud. |
| Workload Identity Federation | You must configure a Workload Identity Pool and Provider to trust the SAP BDC OIDC issuer. | See Configure Workload Identity Federation. |
| Data product assets |
The data product must contain at least one supported data asset
(such as an Apache Iceberg REST catalog table) and a maximum of 50
tables. All Iceberg tables in the data product must meet the following
constraints:
|
See About data products. |
Required roles
To get the permissions that you need to manage and publish a data product to SAP BDC, ask your administrator to grant you the following IAM roles on the Google Cloud project:
-
Manage data products in the Google Cloud console:
Dataplex Data Products Editor (
roles/dataplex.dataProductsEditor) -
Publish data products to SAP BDC:
BigLake Admin (
roles/biglake.admin)
For more information about granting roles, see Manage access to projects, folders, and organizations.
You might also be able to get the required permissions through custom roles or other predefined roles.
Publish a data product to SAP BDC
Console
In the Google Cloud console, go to the Knowledge Catalog Data products page.
Click the name of the data product that you want to publish.
On the data product details page, click Share, and then select Publish to SAP.
In the Publish data product to SAP pane, specify the following:
- Share name: Enter a unique name for the share to be created in SAP.
- Delta catalog: Select the enrolled Delta Sharing catalog from the list.
- Workload identity: Enter the full resource name of the Workload Identity Provider configured for SAP BDC. Use the following format:
projects/PROJECT_NUMBER/locations/global/workloadIdentityPools/POOL_ID/providers/PROVIDER_IDReplace the following:
PROJECT_NUMBER: your Google Cloud project numberPOOL_ID: the ID of your Workload Identity PoolPROVIDER_ID: the ID of your Workload Identity Provider.
Click Publish.
Knowledge Catalog initiates the publishing process using the BigLake API. Once successful, the data product is discoverable as federated tables within SAP BDC.
gcloud
What's next
- Learn more about managing Knowledge Catalog data products.
- Learn how to set up cross-cloud lakehouse for SAP BDC.
- Learn more about configuring Workload Identity Federation.