Skip to Content
Technical Articles

SAP Data Intelligence 3.0 – implement with slcb tool

Last changed 21st of March, 2020

SAP Data Intelligence 3.0 – implement with slcb tool

a

The Blog – Unified Data Integration for SAP gives an Overview of the current SAP Datahub 2.7

Overview SAP Data Intelligence 3.0

 

Blog: SAP Data Intelligence: Next evolution of SAP Data Hub
Blog: SAP Data Intelligence – Development News for 3.0

Note 2866310 – SAP Data Intelligence, on-premise edition 3.0 Release Note
Note 2820555 – SAP Data Intelligence support procedure

SAP Help: New Features in SAP Data Intelligence
SAP Help: Changed Behaviors in SAP Data Intelligence 2.7 => 3.0
SAP Help: SAP Data Intelligence, on-premise edition 3.0.0 (final)

Data Intelligence 3.0 comes in three different flavours:

 


click on the Picture to see the optional Installation Deployments


Beta Program Data Intelligence 3.0 ended.
the mayor Version Data Intelligence 3.0 on-premise is available

  • SLPLUGIN00_32-70003322.SAR
  • MP_Stack_2000810166_20191128_CNT_301_18122019.xml
  • DIFOUNDATION00_0-80005064.ZIP (3.0.1)

Upgrade to Version 3.0.7 (4th of March 2020)

  • SLPLUGIN00_41-70003322.EXE
  • MP_Stack_1000907257_2020034_04032020.xml
  • DIFOUNDATION00_0-80005064.ZIP (3.0.7)

Upgrade to Version 3.0.10 (10th of March 2020)

  • SLPLUGIN00_42-70003322.EXE
  • MP_Stack_2000874416_20200310_10032020.xml
  • DIFOUNDATION00_0-80005064.ZIP (3.0.10)

Final (GA) Version 3.0.12* (20th of March 2020)

  • SLPLUGIN00_43-70003322.EXE => 1.044
  • MP_Stack_2000878621_20200317_17032020.xml
  • DIFOUNDATION00_0-80005064.ZIP (3.0.12)


sidenote: the slcb screens are not differ between Version 2.x.y or 3.0x


the slcb tool

a

SAP Data Intelligence 3.0 (aka as SAP Datahub 2.7.x) introduces an additional option to install the images on the Hyperscaler, i.e. Azure AKS with an own Installation Pod now.
the Setup of the SAP Hostagent is not necessary anymore, and the images will be written from the SAP Repository directly into the Container Registry of the connected AKS Cluster.


for the complete picture, please click on the image

Blog: prepare the Installation Host for the SLC Bridge

 

the Blog mentions also now the usage of the slcb tool according to kubectl or helm.

  • initialize slcb to enable the container bridge
  • execute slcb with stack.xml provided by the Maintenance Planer
server:~ # slcb init -u web 
server:~ # slcb execute --useStackXML /sapmnt/SDH/MP/MP_Stack_1000907257_2020034_04032020.xml -u web

 


when you use the new slcb Bridge the first time, you will be asked twice for the Container Registry Address: one for the slcb tool itself and secondly for the Data Intelligence Product.

When you want to upgrade the slcb tool to a higher version, then you have to re-init the slcb tool, as the individual settings are overwritten by the tool upgrade. see also the Troubleshooting section.

Please choose your slcb hostname and port wisely. You may not use the default values.



Once the slcb tool is initialized, there is also a public IP created which can be configured (DNS)

server:~ # kubectl get pods -n sap-slcbridge
NAME                             READY   STATUS      RESTARTS   AGE
slcbridgehead-56bbf476d5-qdgq5   2/2     Running     0          7d3h
server:~ #  kubectl -n sap-slcbridge get service
NAME                    TYPE           CLUSTER-IP    EXTERNAL-IP      PORT(S)          AGE
slcbridgehead-service   LoadBalancer   <SLC Bridge Base IP>           1128:30701/TCP   7d3h

 

Default slcb URL: https://<SLC Bridge Base IP>:9000/docs/index.html

Example slcb URL: https://slcb-bridge.<region>.<area>.azure.com:1128/docs/index.html


Install SAP Data Intelligence 3.0 (3.0.10) or Upgrade (3.0.12)

a

Blog: Maintenance Planer and the SLC Bridge for Data Hub


Note: the slcb tool screens are not differ between Version 2.7.x and 3.0.x, refer to the
Blog: SAP DataHub 2.7 Installation with SLC Bridge


The Prerequisite Check is now reduced with the DI 3.0 Implementation


Optional screens are only opened, if they are marked


Once the Installation started, the images are copied directly to the Container Registry without temporary storing them to the Installation host.


Log Files are now accessible from the slcb UI


Some of these Post Steps are also improved with SAP DI 3.0 on-premise, as only the second statement is necessary. The third statement is optional.

kubectl patch statefulsets.apps -n $NAMESPACE vsystem-vrep -p '{"spec":{"template":{"spec":{"containers":[{"name":"vsystem-vrep","resources":{"limits":{"cpu":"4", "memory":"8Gi"}}}]}}}}'

kubectl patch deploy vsystem -n $NAMESPACE -p '{"spec":{"template":{"spec":{"containers":[{"name":"vsystem","resources":{"limits":{"memory":"2Gi"}}}]}}}}'

rpc.mountd -N2 -N3 -V4 -V4.1 -V4.2 -t20

 


SAP Data intelligence 3.0 Logon Pad

a


the strategy management is redefined with two new entries mapping the latest strategy from the system and default tenant to “sdi-<tenant>-extension-strategy“.

Blog: Data Intelligence Hub – connecting the Dots …

Presentation: What’s new with SAP BW/4HANA 2.0

Blog: SAP Data Intelligence Tips & Tricks


Creating Dockerfiles – For security reasons, the Modeler application has stopped supporting images that run with a root user. Non-Root Enforcement for Docker Creation

please Note the full SAP DI 3.0 Platform Version contains the Jupyter Notebook. and can be configured directly in the Application Settings of the default tenant.

 


 

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

2 Comments
You must be Logged on to comment or reply to a post.
  • Dear Roland,

    I have some question.

    1. How to participate in SAP Data Intelligence, on-premise edition 3.x beta program? I want to configure and test the demo environment.
    2. Can SAP Data Intelligence be installed in a minikube kubernetes environment for demo?

    Best regards,

    Wonseok

  • Hello Wonseok

    Answer 1.) the Beta Program started already in December 2019 and GA is planned for Q1/2020, so the Product will be released soon.

    Answer 2.) as SAP Data Intelligence 3.0 runs on AK8 Clusters with lots of Pods, of course one minicube will not hold the Software, similar to the fact that you cannot install BWoH on a personal HANA dev edition.

    Best Regards Roland