Let’s install an Open Source infrastructure for the SAP Datahub on-premise – Part 2 of 2
SAP Data Hub 2 installation using Maintenance Planner, SLC bridge and SAP host agent
This is the second part of our article in which we explain, how to install an SAP Data Hub on an Open Source infrastructure. The following expects that you successfully have a Kubernetes cluster running and additionally, fulfill all other requirements for the installation. Not sure? you are welcome to start with part 1 (LINK) at SAP Blogs: Let’s install an Open Source infrastructure for the SAP Datahub on-premise – Part 1 of 2 by my colleague Florian Zimmerman.
Installing and configuring the so called in the installation guide “Jump Host”:
This is a Linux machine with the requirement of at least 50GB for the images (in case you are going to use it also as a registry). However, to be on the safer side, create a bigger volume. Here is the filesystem usage after all steps are completed (to get the estimation for the size):
For this machine I have used CentOS 7, updated to the latest version. As every SAP system that uses SAP Host Agent, it is needed to have the correct record in the DNS and hosts file. After this we will be able to start the setup. Few abbreviations will be used in this document: DH – Data Hub, HA – Host Agent, JH – jump host, Kubernetes Cluster – KC, SAP Maintenance Planner – MP.
JH is going to be used for few things:
- Transfer and execute the MP’s generated XML
- Installation host – where the setup is executed, and commands are sent to the KC
- Registry (as repository), where the Docker images will be downloaded from SAP and stored to be provided to the KC
- Registry for the used apps by DH
Same as any other SAP system installation, we start by logging in MP. We select Plan a new system -> Plan:
After confirming the action, we continue with the standard procedure of pushing the files to the download basket followed by the step of ‘Execute Action’ selection. After clicking on it, we will have to get the address and port settings to be filled – in our case the hostname of the JH and the port of the Host Agent. At this very moment, when selecting Deploy of the XML file from the MP, the feature called CORS (Cross Origin Resource Sharing) will be used. After successful result, when reloading the web of the JH, we will get the following option:
As you can see, the XML from the MP is transferred, and the selected version is displayed with its patch level.
We can now start the process of installation using the Next Button.
The first step is to provide the S-User and this will be needed to download the files from SAP’s
Launchpad needed for the installation media for DH and later – for the Docker image repository, to download the images to our local Docker registry. Here I’m using my personal S-user (Mihail Sevdiev), not the “technical one” that we will need later.
The process is quick since it now only downloads the needed ZIP archive containing the installer. Alternatively, this can be done manually, and the files can be uploaded in the SLC bridge folder. However, we have internet access in our test environment, therefore we will use the option of automatic download.
Successful download is confirmed by the version info of the file:
The next step is to select the name of the KC namespace, that will be used for the DH and after this we have the License Agreement to check:After selecting I authorize, we can proceed to the next step.
We can select Advanced installation and after this we have to select “Do Not use” on the next step for the repository images. This will set the option to download the images. If we use offline installation, we have to select to use the already downloaded images. On the next steps, we have to provide again the S-User that is going to be used for downloading the images for Docker. Then a special “technical” user will be created only for downloads from SAP’s repository.
After this we have to provide the local Registry’s address:
After this, we have to choose the certificate domain for the installation:On the next steps contain the required tenant name and admin details for it. Two tenants will be created – one system and one user’s tenant. The system one can be used for creating more client’s tenants. In our case we will create a tenant with the name “bix-consulting” and we will set username for administration to be admin with a strong password.
The next prompts are for Cluster proxy settings – we are not going to use ones, so we can select “Do not configure”. We will not use checkpoint storage configuration.
With completing the Modeler test, the SAP Data Hub installation is finished successfully. The next steps are to create users and start connecting the systems.
With my colleague Florian Zimmerman, we plan to have more blogs on the topic including: differences in the process of the installation between Data Hub and Data Intelligence, connecting systems and prerequisites, installing custom IDE and many more.
I would appreciate any kind of comments and questions. Hope you enjoyed reading. See you soon!