get the <\/strong>address and port settings to be filled \u2013 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:<\/p>\n <\/p>\n
[\/et_pb_text][et_pb_image src=“https:\/\/www.bix-consulting.com\/wp-content\/uploads\/2021\/01\/DatahubInstallPart2.4.png“ align=“center“ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][\/et_pb_image][et_pb_text _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“]<\/p>\n
<\/p>\n
As you can see, the XML from the MP is transferred, and the selected version is displayed with its patch level.<\/p>\n
We can now start the process of installation using the Next Button.<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row column_structure=“1_2,1_2″ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][et_pb_column type=“1_2″ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][et_pb_text _builder_version=“4.16″ _module_preset=“default“ custom_padding=“|144px||||“ global_colors_info=“{}“]<\/p>\n
The first step is to provide the S-User and this will be needed to download the files from SAP\u2019s Launchpad needed for the installation media for DH and later \u2013 for the Docker image repository, to download the images to our local Docker registry.<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
[\/et_pb_text][et_pb_image src=“https:\/\/www.bix-consulting.com\/wp-content\/uploads\/2021\/01\/DatahubInstallPart2.6.png“ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][\/et_pb_image][\/et_pb_column][et_pb_column type=“1_2″ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][et_pb_image src=“https:\/\/www.bix-consulting.com\/wp-content\/uploads\/2021\/01\/DatahubInstallPart2.5.png“ _builder_version=“4.16″ _module_preset=“default“ width=“100%“ global_colors_info=“{}“][\/et_pb_image][et_pb_text _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“]<\/p>\n
<\/p>\n
The process is pretty quick, since it now only downloads the needed ZIP archive. Alternatively, this can be done manually and the files can be uploaded in the SLC bridge folder. However, we have internet access, therefore we will use the option of automatic download.<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][et_pb_column type=“4_4″ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][et_pb_text _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“]<\/p>\n
Successful download is confirmed by the version info of the file:<\/p>\n
[\/et_pb_text][et_pb_image src=“https:\/\/www.bix-consulting.com\/wp-content\/uploads\/2021\/01\/DatahubInstallPart2.7.png“ align=“center“ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][\/et_pb_image][\/et_pb_column][\/et_pb_row][et_pb_row column_structure=“1_2,1_2″ _builder_version=“4.16″ _module_preset=“default“ locked=“off“ global_colors_info=“{}“][et_pb_column type=“1_2″ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][et_pb_image src=“https:\/\/www.bix-consulting.com\/wp-content\/uploads\/2021\/01\/DatahubInstallPart2.8.png“ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][\/et_pb_image][\/et_pb_column][et_pb_column type=“1_2″ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][et_pb_text _builder_version=“4.16″ _module_preset=“default“ custom_padding=“|||18px||“ global_colors_info=“{}“]<\/p>\n
<\/p>\n
We confirm by clicking \u2018Next\u2019 and find ourselves in the step of the verification. By using the KC config file, the prerequisites are checked and if there are problems with the version compatibility there will be a warning. In our case it is all good, so we can continue.<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][et_pb_column type=“4_4″ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][et_pb_text _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“]<\/p>\n
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:<\/p>\n
<\/p>\n
[\/et_pb_text][et_pb_image src=“https:\/\/www.bix-consulting.com\/wp-content\/uploads\/2021\/01\/DatahubInstallPart2.9.png“ align=“center“ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][\/et_pb_image][et_pb_text _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“]<\/p>\n
<\/p>\n
After selecting I authorize, we can proceed to the next step:<\/p>\n
<\/p>\n
[\/et_pb_text][et_pb_image src=“https:\/\/www.bix-consulting.com\/wp-content\/uploads\/2021\/01\/DatahubInstallPart2.10.png“ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][\/et_pb_image][et_pb_text _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“]<\/p>\n
\n
We can select Advanced installation and after this we have to select \u201cDo Not use\u201d 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.<\/p>\n
After this we have to provide the local Registry\u2019s address.<\/p>\n
[\/et_pb_text][et_pb_image src=“https:\/\/www.bix-consulting.com\/wp-content\/uploads\/2021\/01\/DatahubInstallPart2.11.png“ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][\/et_pb_image][et_pb_text _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“]<\/p>\n
<\/p>\n
Next we have to choose the certificate domain for the installation.<\/p>\n
<\/p>\n
[\/et_pb_text][et_pb_image src=“https:\/\/www.bix-consulting.com\/wp-content\/uploads\/2021\/01\/DatahubInstallPart2.12.png“ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][\/et_pb_image][et_pb_text _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“]<\/p>\n
\n
On the next steps contain the required tenant name and admin details for it. Two tenants will be created \u2013 one system and one user\u2019s tenant. The system one can be used for creating more client\u2019s tenants. In our case we will create a tenant with the name \u201cbix-consulting\u201d and we will set username for administration to be admin with a strong password.<\/p>\n
The next prompts are for Cluster proxy settings \u2013 we are not going to use ones, so we can select \u201cDo not configure\u201d and also, we will not use checkpoint storage configuration.<\/p>\n
After this, we will be prompted for the Storage Class used for the installation. In our case we have configured the KC to have a default one, so we will let the setup to detect the default one and use it for the persistent volumes:<\/p>\n
[\/et_pb_text][et_pb_image src=“https:\/\/www.bix-consulting.com\/wp-content\/uploads\/2021\/01\/DatahubInstallPart2.13.png“ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][\/et_pb_image][et_pb_text _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“]<\/p>\n
<\/p>\n
On the next step, we can set the Docker registry used for the Data Hub Modeler. It can be different from the one used for the installation, but in our case, we will use the same one:<\/p>\n
<\/p>\n
[\/et_pb_text][et_pb_image src=“https:\/\/www.bix-consulting.com\/wp-content\/uploads\/2021\/01\/DatahubInstallPart2.14.png“ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][\/et_pb_image][et_pb_text _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“]<\/p>\n
<\/p>\n
Then we select to Load the NFS modules (default selection) and set custom parameters. They are available in the SAP\u2019s DH installation guide. In our case we will use only one parameter:<\/p>\n
<\/p>\n
[\/et_pb_text][et_pb_image src=“https:\/\/www.bix-consulting.com\/wp-content\/uploads\/2021\/01\/DatahubInstallPart2.15.png“ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][\/et_pb_image][et_pb_text _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“]<\/p>\n
<\/p>\n
After this we can review our input and start the process if we don\u2019t have to make any changes. It will begin with copying the Docker images into the local Repository (catalog):<\/p>\n
<\/p>\n
[\/et_pb_text][et_pb_image src=“https:\/\/www.bix-consulting.com\/wp-content\/uploads\/2021\/01\/DatahubInstallPart2.16.png“ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][\/et_pb_image][et_pb_text _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“]<\/p>\n
\n
And then it will start to deploy the images on the KC:<\/p>\n
[\/et_pb_text][et_pb_image src=“https:\/\/www.bix-consulting.com\/wp-content\/uploads\/2021\/01\/DatahubInstallPart2.17.png“ align=“center“ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][\/et_pb_image][et_pb_text _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“]<\/p>\n
<\/p>\n
If everything is running fine, the setup will have the following result:<\/p>\n
<\/p>\n
[\/et_pb_text][et_pb_image src=“https:\/\/www.bix-consulting.com\/wp-content\/uploads\/2021\/01\/DatahubInstallPart2.18.png“ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][\/et_pb_image][et_pb_text _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“]<\/p>\n
<\/p>\n
After this, we have to expose the web service to the nodes and login into the system:<\/p>\n
<\/p>\n
[\/et_pb_text][et_pb_image src=“https:\/\/www.bix-consulting.com\/wp-content\/uploads\/2021\/01\/DatahubInstallPart2.19.png“ title_text=“DatahubInstallPart2.19″ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][\/et_pb_image][et_pb_text _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“]<\/p>\n
<\/p>\n
We can test the installation by starting a demo application for generating random numbers. It should bring up a pod and start the code there. It is important to note, that after completing a task, we should stop it and then delete the pod from the web interface, otherwise the pod will stay in the KC with status Completed.<\/p>\n
<\/p>\n
[\/et_pb_text][et_pb_image src=“https:\/\/www.bix-consulting.com\/wp-content\/uploads\/2021\/01\/20-1.png“ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][\/et_pb_image][et_pb_text _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“]<\/p>\n
<\/p>\n
By completing the Modeler test, the SAP Datahub installation is finished successfully. We would appreciate any kind of comments and hope, you enjoyed reading. See you soon!<\/p>\n
<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=“4.16″ _module_preset=“default“ locked=“off“ global_colors_info=“{}“][et_pb_column type=“4_4″ _builder_version=“4.16″ _module_preset=“default“ global_colors_info=“{}“][et_pb_text _builder_version=“4.16″ _module_preset=“default“ text_font=“Roboto|300|||||||“ text_font_size=“30px“ locked=“off“ global_colors_info=“{}“]<\/p>\n
Ansprechpartner<\/span><\/p>\n[\/et_pb_text][et_pb_image src=“https:\/\/www.bix-consulting.com\/wp-content\/uploads\/2020\/08\/Oliver-Ossenbrink-e1598705178874.png“ align=“center“ _builder_version=“4.16″ _module_preset=“default“ transform_translate=“-4px|22px“ locked=“off“ global_colors_info=“{}“][\/et_pb_image][et_pb_text _builder_version=“4.16″ _module_preset=“default“ text_font=“Roboto|300|||||||“ text_font_size=“16px“ transform_translate=“-3px|30px“ locked=“off“ global_colors_info=“{}“]<\/p>\n