Skip to Content
Technical Articles

Maintenance Planer and the SLC Bridge for SAP Data Hub

Last Changed: 21st of August 2019

Maintenance Planer and the SLC Bridge for SAP Data Hub

to improve the complete Installation process, SAP Software Logistic (SL) introduced a new way of Implementation which can be triggered from the Maintenance Planer (MP): the SLC Bridge

 


SAP SL Container Bridge (SLC Bridge)

 

Note 2589449 – Software Lifecycle Container Bridge 1.0 (aka SL Plugin) – Release Note
Note 2687666 – Installing Container-based Software using Maintenance Planner, Host Agent and SL Plugin – Troubleshooting Note
Note 2727204 – How to troubleshoot SAP Data Hub docker registry issues
Note 2731062 – Enabling communication between Maintenance Planner and SAP Host Agent
Note 2751127 – Support information for SAP Data Hub

 

(click on the graphic to enlarge the overall procedure …)

As you can see (hopefully), this is really a Jumpstart into several known and a lot of new topics about software logistic and Container based software distribution.

So I was a bit overwhelmed by the amount of new terms and procedures which will come across the SAP Data Hub Implementation.


Setting the Scene and start (slowly) …

 

  • the default SAP Data Hub System Landscape leverages Kubernetes as the Container Platform. This allows an elastic and flexible way to scale vertically the Implementation.
  • Kubernetes is offered by several IaaS providers, e.g. Azure. Some of them already deliver a complete Service like Azure Kubernetes Services (AKS)
    to get familiar with Azure you can also check the Document – SAP First Guidance – Implement SAP BW/4HANA in the Azure Cloud
  • the Docker Kubernetes Service is used to securely run and manage Kubernetes. To access the Kubernetes Cluster from the “Installation Host” several executables, e.g. kubectl will be introduced.
  • the “Installation Host” is a dedicated Linux VM within the Cloud Environment (everything from now is referring to Azure Cloud). To access the AKS service in your subscription you will need to install the Azure Cloud Shell (azure-cli) here as well.
  • furthermore on the Installation Host, you will install the latest Version of the SAP Host Agent (at least 7.21 PL42) and also activate the CORS usage for the Maintenance Planner (MP). this will later allow you run the SLC Bridge on the SAP Host Agent against the Maintenance Planer Service.
  • kubectl introduces it’s own package tool in a client (helm) / server (tiller) environment, similar to the zypper/rpm tool. Tiller runs inside of your Kubernetes cluster, and manages releases (installations) of your charts. Versions higher than 2.13.x are not supported, yet.
    I like the Version: Helm v2.11.0 – Pumpkin Spice Latte Edition => now 2.13 Tango Edition.
    please avoid any additional packaging tools for kubectl/helm/tiller mentioned on the GitHub.
  • The easiest way to install tiller into the cluster is simply to run helm init. This will validate that helm’s local environment is set up correctly (and set it up if necessary). Then it will connect to whatever cluster kubectl connects to by default (kubectl config view). Once it connects, it will install tiller into the kube-system namespace. this will be explained later.

 

Ok, complex enough? we are not configuring the (cool) stuff, yet …

the complete Jump Server Configuration is explained here
prepare the Jump Server for the SLC Bridge


the Maintenance Planner (MP) Part …

A

You open your browser, then you connect to the Maintenance Planner (MP). From the Maintenance Planner UI, you download and deploy the SLC Bridge (SL Plugin) and the Stack XML file with the SAP Data Hub product information to the installation host. Having done this, you access the URL of the running SLC Bridge (SL Plugin).

When you login to the Maintenance Planner (MP) it can happen that depending you are a customer/partner/employee you already have different user assigned to your email address, as this is your unique entry point to the SAP ID Service.

Now you start with “Plan a new System” => “CONTAINER BASED” 
(choosing a <SID> will not work, as it will be replaced by “CNT”)

 

 

There is only one Option to Select: “SAP DATA HUB“.

Depending on your permission with your S-USER Status you can select different Versions.

next, you select OS/DB dependent files …
Note 2589449 – Software Lifecycle Container Bridge 1.0 (aka SL Plugin) – Release Note

 

and finally save your MP transaction …

you can either directly continue with “Execute Plan” or save the Transaction ID for the later usage.

As the Installation Procedure via the SLC Bridge is the same for SAP Employee’s or Customer/Partner, only the Transaction ID differs at the first digits:

  • 10007xxxxx Customer/Partner
  • 20007xxxxx SAP Employee

You also be reminded to activate the CORS option for the SLC Bridge, otherwise the upload to the SAP Host Agent will not work … (can be deactivated afterwards again)

Even that the SLC Bridge allows you to upload the files automatically, you will need to download them manually anyway … (German spell: Keine Hände, keine Kekse … ;-))

Note 2731062 – Enabling communication between Maintenance Planner and SAP Host Agent

Now, this can be tricky depending your SAP Host Agent Setup was successful before.
Then you only have to authenticate yourself once against the SAP Host Agent, otherwise you will be prompted to manually apply the SLC Bridge Add-On (currently 1.25) to the SAP Host Agent.

the second upload (the stack XML file for the Data Hub) will now directly authenticated …

finally the necessary files are applied the the SAP Host Agent …

by now there is an additional directory available at /usr/sap/hostctrl

logiles for the Installation can be found then under /usr/sap/hostctrl/slplugin/work

hmm: this sounds like “Q – The easy Installer for SAP IQ“, right? Yes … 😉

Now, the stage is set for the SAP Data Hub Installation via the SLC Bridge

 

 


Blog: prepare the Jump Server for the SLC Bridge

Blog: Install SAP Data Hub on Azure Kubernetes Service (@Bartosz Jarkowski)
the first part of the Blogs describes the necessary Azure activities and the Documentation to create an AKS Cluster can be found here

Blog: Installing SAP Data Hub (@ThorstenSchneider)

Blog: SAP DataHub 2.6 Installation with SLC Bridge


yet, another run on 16th of August 2019 …

 

 

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

 

 

 

 

A

 

 

2 Comments
You must be Logged on to comment or reply to a post.