Having
deployed my SAP Data Hub Distributed Runtime to the Google Cloud Platform manually and
connected the first SAP Data Hub, developer edition to my SAP Data Hub Cockpit, in this blog I will show how to make the Full System Landscape
SAP Data Hub 1.0 SPS 03, trial edition work for you.
The SAP Data Hub 1.0 SPS 03, trial edition is delivered via the
SAP Cloud Appliance Library and deployed to the
Google Cloud Platform. If you preferred an installation on
Microsoft Azure, you could have a look at my blog how to
Deploy your SAP Data Hub Distributed Runtime to the Microsoft Azure Container Service.
To start with, I chose the SAP Data Hub 1.0 SPS 03, trial edition from the SAP Cloud Appliance Library:
In preparation for creating an instance, I need to create a project in my Google Cloud Platform account and within that a service account with the respective roles so that the SAP Cloud Appliance Library can access it as described in
Getting Started with SAP Data Hub, trial edition:
- Compute Instance Admin (v1)
- Compute Network Admin
- Compute Security Admin
- Kubernetes Engine Admin
- Service Account User
- Storage Admin
In addition, I also need to activate the:
- Cloud Resource Manager API
- Compute Engine API
- Kubernetes Engine API
With this I export my service account key in JSON format and create my instance:
After a while my instance is ready and I connect to my SAP Data Hub Cockpit to check the connection to my SAP Data Hub Distributed Runtime:
Finally, for Kubernetes Dashboard access, I copy the Kubeconfig file from the Jump Box to a local machine, create a Proxy and retrieve a valid Bearer Token to sing in:
While this is a so called Full System Landscape, out of the box it is missing the Hadoop integration, which would have to be added manually. These are the respective
Architectural changes with SAP Data Hub 1.3.0.