This Blog describes the capabilities to share a single HANA Cloud DB-Tenant for both SAP SQL data warehousing and SAP Data Warehouse Cloud (DWC) scenarios, by leveraging the SAP Data Warehouse Cloud consumable models as a source for the SAP IDE (here: WebIDE) artefacts, like: Synonym, Flowgraph, Calculation-View ....
SAP Data Warehouse Cloud provides the capability to connect the HDI-container, artefacts and loaded data to a DWC Space from the DWC Data-Builder Editors (graphical View and SQL View) for immediate access without data transfer.
In preparation to enable SAP WebIDE / SAP Business Application Studio to deploy HDI-container + database artefacts to the HANA Cloud instance powering your DWC instance, it's required in a first place to establish a service broker mapping to connect your customer owned BTP Account / Sub-Account / BTP Space to the SAP managed HANA Cloud instance powering your DWC instance.
Pls find here the relevant steps to create a SAP ticket to initiate the service broker mapping process.
Once the SAP ticket / BTP Account mapping has been successfully completed, you're enabled to deploy SAP WebIDE / SAP Business Application Studio projects as HDI-container + database artefacts (-> SAP SQL Data Warehousing) directly to the SAP managed HANA Cloud instance powering your DWC instance.
The created HDI-container can be connected to a SAP DWC Space and the SAP DWC Data-Builder Editors get direct access to the HDI container database artefacts + data without further data movement required.
Connection to Source systems / Sources need to be established by leveraging the variety of SAP Data Warehouse Cloud provided connectivity options, as SAP DWC come as a SaaS application / SAP managed, not granting HANA Cloud Admin privileges to directly connect a SAP DP-Agent / SAP Cloud Connector to the HANA Cloud instance powering SAP DWC. It's required to proxy the DWC connection by creating a simple DWC-model + flag "consumable" (-> "DWC consumable model").
The access from your customer managed BTP-account to the "DWC consumable model(s)" is managed via a BTP User-Provided Service (UPS), where DWC is providing the UPS configuration details once you create a DB-User and flag "Enable Read access (SQL)" AND "Enable HDI consumption" within the according DWC Space where the "DWC consumable model(s)" are located.
Pls find below additional information to enable SAP SQL Data Warehousing on your DWC tenant to exchange data between your HDI containers and your DWC spaces without the need for data movement by accessing Exchanging Data with SAP SQL Data Warehousing HDI Containers
Below TechEd Session material is providing further documentation / steps as a walk through: https://github.com/SAP-samples/teched2020-ANA369
This scenario describes a close-loop-integration between external consumable DWC models as a source for SAP WebIDE / SAP Business Application Studio projects - who are connecting to the according connectivity adapter & partner - and the according HDI-container created from WebIDE / BAS projects, to be assigned to a DWC Space for immediate access by the Data-Builder Editors.
Please treat this Blog-Post as a follow-up to the previous shared BLOG: https://blogs.sap.com/2020/07/01/sap-data-warehouse-cloud-integrated-with-sap-sql-data-warehousing-s....
In case you're interested to leverage SAP Business Application Studio instead of SAP WebIDE to access DWC consumbale models, I'd like to guide you to below Blog we created in our group:
Blog 2: Access the SAP HANA Cloud database underneath SAP Data Warehouse Cloud: how to create an SAP HANA Deployment Infrastructure (aka HDI) container on SAP HANA Cloud, and persist actual sales data originated from an external system in the same SAP Data Warehouse Cloud’s existing persistence area. We will show how to provide bi-directional access between SAP Data Warehouse Cloud and SAP HANA Cloud’s managed datasets. You will also see how to expose SAP HANA Cloud & SAP Data Warehouse Cloud’s artifacts, like a table or a Graphical View, as oData services. You should also take a look on this additional blog, which provides hands-on instructions for exposing SAP Data Warehouse Cloud artifacts as oData services and a complete Git repository to kick-start implementation.
I also like to point you to our group Blog Landings page, where we constanly enhance and share new Content: SAP Business Technology Platform: End-to-End Data & Analytics Scenarios , also visible on the different SAP Community pages like SAP Data Warehouse Cloud Community Page
SAP Data Warehouse Cloud provides the capability to connect the HDI-container, artefacts and loaded data to a DWC Space from the DWC Data-Builder Editors (graphical View and SQL View) for immediate access without data transfer.
In preparation to enable SAP WebIDE / SAP Business Application Studio to deploy HDI-container + database artefacts to the HANA Cloud instance powering your DWC instance, it's required in a first place to establish a service broker mapping to connect your customer owned BTP Account / Sub-Account / BTP Space to the SAP managed HANA Cloud instance powering your DWC instance.
Pls find here the relevant steps to create a SAP ticket to initiate the service broker mapping process.
Once the SAP ticket / BTP Account mapping has been successfully completed, you're enabled to deploy SAP WebIDE / SAP Business Application Studio projects as HDI-container + database artefacts (-> SAP SQL Data Warehousing) directly to the SAP managed HANA Cloud instance powering your DWC instance.
The created HDI-container can be connected to a SAP DWC Space and the SAP DWC Data-Builder Editors get direct access to the HDI container database artefacts + data without further data movement required.
Connection to Source systems / Sources need to be established by leveraging the variety of SAP Data Warehouse Cloud provided connectivity options, as SAP DWC come as a SaaS application / SAP managed, not granting HANA Cloud Admin privileges to directly connect a SAP DP-Agent / SAP Cloud Connector to the HANA Cloud instance powering SAP DWC. It's required to proxy the DWC connection by creating a simple DWC-model + flag "consumable" (-> "DWC consumable model").
The access from your customer managed BTP-account to the "DWC consumable model(s)" is managed via a BTP User-Provided Service (UPS), where DWC is providing the UPS configuration details once you create a DB-User and flag "Enable Read access (SQL)" AND "Enable HDI consumption" within the according DWC Space where the "DWC consumable model(s)" are located.
Pls find below additional information to enable SAP SQL Data Warehousing on your DWC tenant to exchange data between your HDI containers and your DWC spaces without the need for data movement by accessing Exchanging Data with SAP SQL Data Warehousing HDI Containers
Below TechEd Session material is providing further documentation / steps as a walk through: https://github.com/SAP-samples/teched2020-ANA369
This scenario describes a close-loop-integration between external consumable DWC models as a source for SAP WebIDE / SAP Business Application Studio projects - who are connecting to the according connectivity adapter & partner - and the according HDI-container created from WebIDE / BAS projects, to be assigned to a DWC Space for immediate access by the Data-Builder Editors.
Please treat this Blog-Post as a follow-up to the previous shared BLOG: https://blogs.sap.com/2020/07/01/sap-data-warehouse-cloud-integrated-with-sap-sql-data-warehousing-s....
In case you're interested to leverage SAP Business Application Studio instead of SAP WebIDE to access DWC consumbale models, I'd like to guide you to below Blog we created in our group:
Blog 2: Access the SAP HANA Cloud database underneath SAP Data Warehouse Cloud: how to create an SAP HANA Deployment Infrastructure (aka HDI) container on SAP HANA Cloud, and persist actual sales data originated from an external system in the same SAP Data Warehouse Cloud’s existing persistence area. We will show how to provide bi-directional access between SAP Data Warehouse Cloud and SAP HANA Cloud’s managed datasets. You will also see how to expose SAP HANA Cloud & SAP Data Warehouse Cloud’s artifacts, like a table or a Graphical View, as oData services. You should also take a look on this additional blog, which provides hands-on instructions for exposing SAP Data Warehouse Cloud artifacts as oData services and a complete Git repository to kick-start implementation.
I also like to point you to our group Blog Landings page, where we constanly enhance and share new Content: SAP Business Technology Platform: End-to-End Data & Analytics Scenarios , also visible on the different SAP Community pages like SAP Data Warehouse Cloud Community Page
- SAP Managed Tags:
6 Comments
