- SAP Managed Tags
We are excited to announce that the integration between SAP Datasphere and Collibra Data Intelligence Platform is now generally available. This integration enables an end-to-end data catalog across SAP and non-SAP sources for a business data fabric, allowing customers to do more with trusted data.
This blog describes the integration and how it enables metadata to be exchanged between SAP Datasphere catalog and Collibra Data Catalog. The integration facilitates efficient metadata exchange, ensuring robust data governance across your entire data ecosystem with SAP and non-SAP data.
Configuring SAP Datasphere catalog
First let’s have a look at how we configure SAP Datasphere to expose the published assets in the Catalog so it can be consumed in the Collibra Data Catalog.
Within SAP Datasphere, we have access to our comprehensive catalog. This catalog is our gateway to various assets that are readily available. We can start right from the home page, navigate to the catalog, and directly access all the available SAP metadata that were harvested and enriched.
In the SAP Datasphere catalog, we find assets from different connected systems, including terms, KPIs, and other asset types. These assets come from a variety of connected systems from which we harvest the metadata.
We can navigate to the monitoring associated to the catalog to see a list of systems we are able to connect and harvest the metadata from. This includes creating new connections to SAP systems such as SAP Analytics Cloud, SAP Datasphere, or SAP Datasphere BW bridge.
To ensure the metadata in SAP Datasphere can be consumed in Collibra, we need to create an OAuth client application integration entry point.
To create a new OAuth client, access System, then App Integration and click “Add a New OAuth Client”.
We can create a new OAuth client, which will allow us to expose the various types of metadata available in our system to Collibra through APIs.
The OAuth Client requires a Name, the Purpose must be “API Access” with a “Catalog User API” Access.
When the OAuth client is created, it will generate an OAuth Client ID and a secret that we can use in Collibra as an entry point to access the available APIs.
Importing SAP Analytics Cloud Metadata into Collibra Data Catalog
With the OAuth Client ID and secret in hand, we can now switch to Collibra to define the entry point to the SAP Datasphere catalog.
In Collibra, we go to Edge and create a connection using the OAuth details.
We set up an SAP Datasphere catalog connection by entering the name, description, and the URL of the Datasphere tenant catalog. Then, we use the OAuth Client ID and secret generated earlier.
Once these details are filled in, the connection between Collibra and SAP Datasphere will be established.
Now it's time to create capabilities such as retrieval of metadata related to SAP Analytics Cloud assets, or different capabilities for other SAP Datasphere asset types.
This flexibility allows retrieval of metadata per asset type, tailoring it to your needs.
Once a capability is created, we simply hit refresh to pull the metadata from SAP Datasphere into Collibra, making them accessible in the Collibra catalog.
Once synchronized, all the metadata are available now in the Collibra Data Catalog to consume.
Checking available Metadata in Collibra Data Catalog
We can now check that the metadata were retrieved from SAP Datasphere and verify that all information is available by searching, for example, a specific SAP Analytics Cloud model in SAP Datasphere.
Let’s search for a particular model and then let’s examine all the information for this asset.
When we look at the lineage, we can see how the model is used by different SAP Analytics Cloud stories. One might be in the public folder while another is in the system folder.
We can now switch to Collibra to confirm that the same information for this asset is now available in the system.
We search for the asset by its name and access the detailed metadata including the lineage graph, which will display the same information as the one that was available in the SAP Datasphere catalog.
In this lineage graph, we retrieve the information about the model we searched for, and we also see that the model is used by the different SAP Analytics Cloud stories that are in the public folder and in the system folder.
Additionally, Collibra was able to retrieve the available column details for the SAP Analytics Cloud model asset and integrate these details directly in the lineage graph allowing end users a better and more detailed view of the object in the lineage graph.
In summary, we've shown how SAP delivers robust data governance with Collibra and how SAP Datasphere empowers you to harness the full potential of your business data to derive critical business decisions. The integration between the SAP Datasphere catalog and the Collibra Data Catalog streamlines data management, enabling users to efficiently oversee the entire data lifecycle across both platforms, helping to increase data governance within organizations.
For an in-product tour of this functionality go to the Collibra Data Intelligence Platform with SAP Datasphere product tour available here.
| User | Count |
|---|---|
| 40 | |
| 22 | |
| 16 | |
| 13 | |
| 8 | |
| 7 | |
| 7 | |
| 7 | |
| 6 | |
| 6 |
