Page Comparison

...

1. Java Connector: (SM-Latest) Java Connector Setup

   1. Creation of SNP_JAVA_CONN RFC:

      1. Connection type: TCP/IP Connection.

      2. Activation type: Registered Server Program.

      3. Fill in the Program ID (e.g.): SNP_JAVA_CONNECTOR.

   2. Creation of Technical SAP user for ABAP->JCO RFC Communication:

      1. In transport, you are provided with a template role with name /DVD/JCORFC(if you will use this role, do not forget to generate the profile in transaction PFCG).

      2. Create System user, with role /DVD/JCORFC.

   3. Granting access for external program SNP_JAVA_CONN to SAP gateway:

      1. Check SMGW > GoTo > Expert Functions > External Security > Maintenance of ACL files whether external programs are allowed (=* or ProgramID).

2. SAP system: (SM-22112305) Azure Data Lake Gen2 | id (SM 2305)AzureDataLakeGen2 SAPsystemconfiguration

   1. Uploading certificates to STRUST for secure SSL connection between SAP and Microsoft services (into SSL client Anonymous PSE).

   2. Creation of storage RFC and configuration of the RFC are dependent on the type of Authentication chosen (more details can be found in

      (SM-22112305) Azure Data Lake Gen2 | id (SM 2305)AzureDataLakeGen2 StorageRFC).

Networking team:

1. Enabling outbound communication from the SAP system to ADLS Gen 2

...

1. Azure storage: (SM-Latest) MS Azure

   1. Storage account is needed (more details in (SM-22112305) Azure Data Lake Gen2 | id (SM 2305)AzureDataLakeGen2 Azurestorageconfiguration).

   2. Preparation of Landing area (container/directory).

   3. Authentication to ADLS, there are two possible options possible - SAS token or OAuth 2.0 (more details can be found in (SM-22112305) Azure Data Lake Gen2 | id (SM 2305)AzureDataLakeGen2 Authentication).