Let's now describe the configuration of the data product generator. Detailed installation steps are not covered, because this course is targeted at modelers. However, the set up of the connectivity between SAP BW, private cloud edition in SAP Business Data Cloud and the SAP Datasphere tenant is explained as it makes sense to understand the main steps taken here by the system administrator.
Installation
A system administrator is responsible for the installation of the data product generator and the related components. A detailed document for the system administrator is available through SAP Note 3590400: https://me.sap.com/notes/3590400).
Connectivity Setup
After installation of the data product generator, the system administrator also takes care of the connectivity setup between SAP BW, private cloud edition in SAP Business Data Cloud and the SAP Datasphere tenant.
The connectivity requires:
A connection between SAP BW, private cloud edition in SAP Business Data Cloud and the SAP Datasphere tenant, stored as RFC destination type 'HTTP Connection to External Server'. The authentication against SAP Datasphere is based on OAuth 2.0.
- A connection from SAP BW, private cloud edition in SAP Business Data Cloud to the object store, stored as RFC destination type 'HTTP Connection to External Server'. To authenticate against the object store in SAP Datasphere, SAP BW, private cloud edition in SAP Business Data Cloud uses a self-signed certificate.
A task list, SAP_BW_BDC_CONFIGURATION, is used to perform the following steps:
Configure oAuth client in SAP Datasphere: Manually create a new OAuth 2.0 client in the SAP Datasphere tenant.
Configure oAuth to SAP Datasphere: Manually create the OAuth configuration in SAP BW, private cloud edition in SAP Business Data Cloud.
Configure certificate usage: Manually create a new SSL client identity and add the required certificates (this identity is later used in the RFC connection to the object store).
Create a target space in SAP Datasphere: The task lists creates a RFC destination type 'HTTP Connection to External Server' to SAP Datasphere and a new space with type 'SAP BW' and storage type SAP HANA Data Lake Files in SAP Datasphere (during this process, the self-signed certificate is sent to the SAP Datasphere tenant and stored in the new space).
Configure HANA Data Lake Files connection: This step is automatically started after successful completion of step 4. In this step, the task list creates a RFC destination type 'HTTP Connection to External Server' to the object store in SAP Datasphere.
With the previous steps, the RFC destination to SAP Datasphere uses an OAuth configuration that is linked to an OAuth client in SAP Datasphere with the purpose Interactive Usage. As a result, every user who creates a data subscription must have a user account in the SAP Datasphere tenant and must request an OAuth token as described above. This approach works, but is not ideal from a user experience perspective.
For the time being, this approach is still needed to complete the configuration of the data product generator. However, once the initial configuration is complete, you can switch to an OAuth client in SAP Datasphere with the purpose Technical User. This option simplifies authentication because it relies on a single technical user in the SAP Datasphere tenant to create and deploy local tables (file) and to trigger merge operations in the object store.
Note
To configure and use a technical user in SAP Datasphere, a system administrator has to perform the following steps:
- Create a new OAuth 2.0 client with purpose Technical User in SAP Datasphere.
- Create a new OAuth configuration in SAP BW, private cloud edition in SAP Business Data Cloud.
- Update the RFC destination to replace the currently used OAuth configuration (linked to an OAuth client with purpose Interactive Usage) by the newly created OAuth configuration with purpose Technical User.
Multiple Targets for the Data Product Generator
It is possible to configure multiple targets for the data product generator. The targets can be either different SAP Datasphere tenants or just different spaces in the same SAP Datasphere tenant. This enables you to distribute extracted SAP BW data across multiple spaces or tenants based on functional requirements.
The following rules apply when configuring multiple targets:
- You must request usage permission for each SAP Datasphere tenant via a support ticket.
- To connect SAP BW, private cloud edition in SAP Business Data Cloud to more than one space or SAP Datasphere tenant, you have to run the configuration process separately for each target by starting a new task list run.
- Use a unique target name for each target.
- In a multi-tier SAP BW system landscape, ensure that the target name is identical across all systems. Data subscriptions can only be transported from one system to another if the target name is identical.
- For each target, the task list generates a new set of RFC destinations as the target name is used as a suffix in the RFC destination naming.
- When using multiple spaces within the same tenant as targets, you can reuse the existing OAuth configurations and trust settings when connecting to additional spaces.
Note
Settings for Optimizing Data Subscription Performance
Data subscription runs are handled by the Queued Task Manager (QTM). By default, QTM can use up to 75% of the available batch work processes. This limit is configurable.
The package size for data subscription runs can be adjusted using the RSADMIN parameter RSDDS_PACKSIZE_CSV. The current default value is 50000000 (50 million bytes). Increasing this value, up to ten times the default, results in fewer, but larger data packages.
Starting with data product generator 3.0, parallel processing for data subscription runs is enabled by default. Before, you could set the RSADMIN parameter RSDDS_PARALLEL_LOAD to value X with report SAP_RSADMIN_MAINTAIN.