Hi, my name is Denys van Kempen, SAP HANA Academy and SAP’s Partner Innovation Lab.
In this video tutorial series we are going to explore the Kyma runtime
of the SAP Business Technology Platform. This video was recorded in January 2022.
For the latest tutorials on the topic, please check the playlist.
In this video, we are going to show you how we can integrate the Business Technology Platform
and SAP S/4HANA Cloud. The steps are documented here on the
SAP Help Portal, Extensions, Extending SAP S/4HANA Cloud in the Cloud Foundry and Kyma environment.
Most tasks are common to both environments. We need to register a system in a global account,
using the SAP BTP cockpit and SAP S/4HANA Cloud Communication Management.
Then we need to configure the entitlements for the SAP S/4HANA Cloud Extensibility service
for a subaccount, to allow the registration to be used.
Next, we are going to create service instance for the API plan, using the Kyma Dashboard and,
or, in case we want to enable the consumption of SAP S/4HANA Cloud events, we also need to create
a service instance for the messaging plan, a topic we will cover in part two of this video tutorial.
Those are the administration steps. If we go back to the illustration, once you have
developed a function or microservice application, you would then need to bind it to the service,
with or without credentials, and we will see where in the Kyma dashboard this can be done,
although we won’t go into much detail about developing extensions.
We mostly concerned here with the setup. Okay, I am connected here to SAP BTP cockpit,
at the global account level, not connected to any subaccount.
Under System Landscape we find the Systems entry. Select Register System.
Takes a few seconds. Type is SAP S/4HANA Cloud.
System name. You can use any name you want.
If you have a lot of tenants, you might want to include some sort of tenant identifier, but here
we are going to keep it simple using sample. The registration action generates
an integration token. Copy to clipboard.
Switch to S/4HANA Cloud. Communication Management
Maintain Extensions on SAP BTP Select New
Paste in the token. Add a description, and save.
Status is Enabling for a few seconds and then Enabled (assuming all is well).
If we then return to the BTP cockpit, and close the Register System dialog, refresh the page,
the status will have changed from Pending to Registered.
Okay, that’s step 1. Next we need to
entitle a subaccount to access the system we just registered.
When we take a look at Service Assignments, filter on ex or exten, we can see the SAP S/4HANA Cloud
Extensibility service listed with an api-access and a messaging plan,
unlimited quota, resource provider SAMPLE. This service entry is automatically created
when we register an SAP S/4HANA Cloud system and then it’s up to us to assign the api-access or
messaging plan, or both, to a subaccount. Go to Entity Assignments.
Select one or more subacount (entities). Go.
Configure Entitlement (filter with ex). Select the entitlement, select the plan.
There is only one resource provider in our case (SAMPLE) but if you have registered
multiple systems you first need to select the one you want to use, add 2 Service Plans, save,
and here we have the entry listed; the resource provider is the system we just registered.
Okay, step 2. Done. Next, we need a
service instance in the Kyma environment. Navigate to the Kyma Dashboard,
We are limited to a single service instance per namespace, so typically,
you would first create a new namespace. Give it a nameand
then go to Service Management, Catalog (filter on ex).
Select SAP S/4HANA Cloud Extensibility, add. The name will be made unique with a random suffix,
flawless-experience this time, but you can change this as needed.
Select the plan: api-access or messaging Optionally
add filter label for the service instance and provide the parameters in JSON format
I will be using here the sample configuration from the documentation, with a few modifications.
The communication system host name is the one of the system just registered.
Systen name SAMPLE and also SAMPLE appended to the arrangment name, to make it a little easier
to find the arrangement. The scenario is 219.
If you are new to communication system, arrangements, scenarios,
there is a link in the description below pointing to a blog post where we cover this in more detail.
Create Status is provisioning for a few seconds
and then should change to running. If we briefly switch to the documentation,
the illustration, this is for the Cloud Foundry environment but the same principle aplies to Kyma.
We need to bind an application to a service before we can use the destination.
This where we can bind applications and create credentials, the
equivalent of the service key in Cloud Foundry. Under Workloads, Pods, a gateway should be
running, and the pod is part of a deployment, standard Kubernetes concepts.
Now, a service instance may or may not create a destination.
For scenario ID SAP_COM_0219, communication arrangement with an outbound connection
with authentication type OAuth2ClientCredentials,
no destination is created, but when we switch to our S/4HANA Cloud tenant,
Communication Management, Communication Arrangements, we can see the arrangement listed.
Select, display, and here we have all the details, which can be edited if needed.
Okay, let’s do one more, another example from the documentation.
New namespace, Service Management, Catalog, S/4HANA Cloud Extensibility, Add.
This time for scenario 13, Launch Web IDE. Paste that in and create.
Wait until the status is running and if we now go to the destinations view, and refresh the page,
we can see that a destination has been created, which we can edit, upload and delete certificates,
and when we return to our list of communication arrangements, we can see it listed.
The scenario is obsolete, by the way, the objective here was just to show how creating
a service instance using the Kyma Dashboard triggers the creating of a destination in the
associated SAP BTP subaccount, again, as illustrated in the documentation.
Creating a service instance of the messaging plan will be covered in the next video.
This video tutorial was recorded by Denys van Kempen,
SAP HANA Academy / SAP Partner Innovation Lab Any good? Give us a like, and for updates,
don’t forget to subscribe. Thanks for watching.