This article describes a process required to establish a connection from SAP to Azure Data Lake Storage Gen2.

Azure storage configuration

This section describes the steps needed for the preparation of the landing area on the Azure side.

Creating Mirrored database

In Microsoft Fabric go to Data Factory. Either use already existing workspace or create a new one. Reference to Microsoft documentation: https://learn.microsoft.com/en-us/fabric/get-started/create-workspaces

After the workspace is ready, create a Mirrored database. Reference to Microsoft documentation, section “Create mirrored database“: https://learn.microsoft.com/en-us/fabric/database/mirrored-database/open-mirroring-tutorial .

Authentication

Authentication to ADLS can be delivered by two methods:

• SAS Token: Recommended for Proof of Concepts, faster setup, but provides fewer security management options.

• OAuth 2.0: Recommended for production deployment, fully manageable, but requires application registration and detailed permission setup.

SAS Token

Microsoft documentation regarding the creation of SAS tokens https://learn.microsoft.com/en-us/fabric/onelake/how-to-create-a-onelake-shared-access-signature#specify-the-signature.

OAuth 2.0 Authentication

OAuth 2.0 required application registration. To create a new registration, follow these steps:

1. Go to Azure Active Directory > App registrations > New application registration.

Open

2. Fill in the required fields and click Create.

Open

3. Write down Application ID and Directory ID, as it will be required later during the Storage management configuration.

Open

4. Click Certificates & secrets and generate a New client secret. Write down the secret, which will be used later during the configuration.

   Open

   

5. Grant Contributor authorization to the application in the workspace the mirrored database is located in.

   1. Go to Manage access->+ Add people or groups

   2. Search for the registered application by its display name and set its authorization to Contributor

SAP system configuration

After preparation is complete on the Azure side, fill in the required information on the SAP side to establish a connection.

Java Connector Setup

First Java connector needs to be setup. In detail guide can be found here (SM-2502) Java Connector Setup.

Storage Management

In this step, the actual connection to the landing area is created.

1. Execute transaction /DVD/SM_SETUP.

2. Switch to Edit Mode and click New Storage.

3. Choose storage type FABRIC and specify Storage ID.

4. Specify the following parameters:

   1. Java connector RFC: RFC that points to running JCo Instance.

   2. Landing zone: Landing zone of the mirrored databases.

      Open

      

      Following parameters are automatically parsed from the Landing zone once the storage is saved.

      1. Target host: URL of the Fabric host.

      2. Container: ID of the Fabric container. It is concatenated from workspace ID and mirrored database ID.

      3. Path prefix: Path after the Container. Must be “Files/LandingZone“. In case it differs, check if Landing zone is correct.

5. Java Call Repeat: Specify the number of times the HTTP request will be retried in case of failure (0 = no repetition).

6. Repeat Delay (seconds): Seconds between repetitions - if not filled, the default value will be set to 3 seconds (instead of 0).

Open

The bottom part of the storage connection configuration depends on the authentication method chosen.

a) If a SAS token is used, either insert it directly to the respective field, or you can insert it into the field next to Hash button and by clicking Hash, convert it into a hashed string to prevent plain text visibility.

Open

SAS token value alerts:

• Remove a question mark ? character at the beginning of the generated SAS token.

b) If the OAuth authentication method is chosen, fill in the OAuth profile with information recorded during application registration:

OAuth 2.0 profile: The ID of the profile.
Client ID: Application ID created in the section Creating Application Registration.
Client secret: Key created in the section Creating Application Registration.
Resource: Static address https://storage.azure.com/.
Tenant: Part of the URL identifier is described in the section Tenant.

Open

Confirm storage creation by saving the information (Ctrl+S).

To check the connection click Check button.

Use compute hash to calculate the hash of data.

Open