Skip to Content
Technical Articles

Data Intelligence Hub – connecting the Dots …

Last changed: 23rd of January 2020

Blog: prepare the Installation Host for the SLC Bridge
Blog: Maintenance Planer and the SLC Bridge for Data Hub
Blog: SAP DataHub 2.7 Installation with SLC Bridge
Blog: Data Intelligence Hub – connecting the Dots …

Data Intelligence Hub – connecting the Dots …

once your SAP Datahub is up and running, you want to add several System types for the central Orchestration of the Intelligent Data.

BlogWhat’s New in SAP Data Hub 2.7 Release
online help – Using SAP Data Hub Connection Management


SAP Datahub Integration scenarios – a selection

 

 

 

Blog ABAP Integration for SAP Data Hub and SAP Data Intelligence – Overview Blog
Blog Connect SAP BW/4 HANA to SAP Data Hub
BlogOrchestrierung von HANA SDI mit SAP Data Intelligence
BlogData Intelligence integration with SAP Analytics Cloud
BlogApplication Integration Example Scenario on SAP Data Hub GitHub Repository
BlogPush Data from SAP Cloud Foundry to Data Hub or Data Intelligence
BlogStream SAP data into Azure Event Hub using SAP Data Hub
BlogDancing with Data Intelligence – (aka DI 3.0 on premise)


 


Important: with SAP Datahub 2.7.x the Application Setting for the Flowagent is set by Default to accept only ABAP connections from Release 1909 and higher.
To enable the original behaviour, you have to change back the ABAP Connector to false.

Note 2849542 – ABAP RFC Connection Check with Data Hub 2.7/Data Intelligence 1909 failed

 

 


General Recommendations

Note 2838751 – Release Restrictions for SAP Data Hub 2.7
Note 2836631 – Known and Fixed Issues in Self-Service Data Preparation in SAP Data Hub and SAP Data Intelligence
Note 2739161 – Replacements for Deprecated Operators and Dockerfiles in SAP Data Hub and SAP Data Intelligence Modeler

Note 2775549 – Release-independent ODP interface for SAP Data Hub
Note 2711139 – SAP Data Hub 2.x: Limit. and prereq. BW Dataset & BW Data Transfer
Note 2727180 – Connecting SAP Data Hub to SAP BW or SAP BW/4HANA
Note 2731192 – SAP Data Hub – ABAP connection type for SAP Data Hub
Note 2854358 – SAP Data Hub/ Data Intelligence ABAP Integration-ODP reader
Note 2851248 – Bad Gateway when testing HDFS connection – SAP Data Hub

 

S/4 Integration from 1909 onwards

Note 2814951 – SAP Data Hub/ Data Intell. ABAP Integration – DMIS 2011 SP17/ DMIS 2018 SP02
Note 2830276 – SAP Data Hub/ Data Intelligence ABAP Integration – S4 OP1909
Note 2835207 – SAP Data Hub – ABAP connection type for SAP Data Hub/ Data Intelligence
Note 2849542 – ABAP RFC Connection Check with Data Hub 2.7/Data Intelligence 1909 failed
Note 2854358 – SAP Data Hub/ Data Intelligence ABAP Integration-ODP reader

 

Applying necessary Certificates for Backend Connections


Please note that only plain types of cer/crt Certificates are accepted.
Sometimes the Certificates are only available as binary files. These type of files are not accepted by the Certificate STore of the SAP Datahub.

Note 2631190 – Download location of SSL certificates required for Support Hub Connectivity configuration

openssl allows you to convert the files from binary format to plain format and vice versa.

openssl x509 -in DigiCertGlobalRootCA.crt -inform der -outform pem -out DigiCertGlobalRootCA.pem
openssl x509 -in DigiCertGlobalRootG2.crt -inform der -outform pem -out DigiCertGlobalRootG2.pem
openssl x509 -in DigiCertHighAssuranceEVRootCA.crt -inform der -outform pem -out DigiCertHighAssuranceEVRootCA.pem

 

 

X509 File Extensions

The first thing we have to understand is what each type of file extension is.   There is a lot of confusion about what DER, PEM, CRT, and CER are and many have incorrectly said that they are all interchangeable.  While in certain cases some can be interchanged the best practice is to identify how your certificate is encoded and then label it correctly.  Correctly labeled certificates will be much easier to manipulate.

Encodings (also used as extensions)

  • .DER = The DER extension is used for binary DER encoded certificates. These files may also bear the CER or the CRT extension.   Proper English usage would be “I have a DER encoded certificate” not “I have a DER certificate”.
  • .PEM = The PEM extension is used for different types of X.509v3 files which contain ASCII (Base64) armored data prefixed with a “—– BEGIN …” line.

Common Extensions

  • .CRT = The CRT extension is used for certificates. The certificates may be encoded as binary DER or as ASCII PEM. The CER and CRT extensions are nearly synonymous.  Most common among *nix systems
  • CER = alternate form of .crt (Microsoft Convention) You can use MS to convert .crt to .cer (.both DER encoded .cer, or base64[PEM] encoded .cer)  The .cer file extension is also recognized by IE as a command to run a MS cryptoAPI command (specifically rundll32.exe cryptext.dll,CryptExtOpenCER) which displays a dialogue for importing and/or viewing certificate contents.
  • .KEY = The KEY extension is used both for public and private PKCS#8 keys. The keys may be encoded as binary DER or as ASCII PEM.

The only time CRT and CER can safely be interchanged is when the encoding type can be identical.  (ie  PEM encoded CRT = PEM encoded CER)

 



Roland Kramer, SAP Platform Architect for Intelligent Data & Analytics
@RolandKramer

Be the first to leave a comment
You must be Logged on to comment or reply to a post.