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
(BTP) and SAP SuccessFactors, for creating extensions in the Kyma environment.
The steps are documented here on the SAP Help Portal, SAP Business Technology Platform documentation,
Extensions, Extending SuccessFactors in the Cloud Foundry and Kyma environment.
Most tasks are common to both environments.
We need to register a system at the global account level, using the SAP BTP cockpit and
the SAP SuccessFactors Extension Center Then we need to add entitlements to a subaccount,
to allow this registration to be consumed.
Next, we need to create service instance.
In the Cloud Foundry environment you would do this using the Service Marketplace, we
have seen this in a previous video when instantiated the Kyma runtime.
However, in the Kyma environment, we are going to use the Kyma Dashboard for this.
Using the same api-access plan, and the end-result will be the same.
A destination will have been created, containing all the required configuration
to make Odata API calls to our SuccessFactors system.
Finally, we cover also how to configure single sign-on.
Those are the administration steps.
Once you have developed a function or microservice application, you would then need to bind it
to the servcie, using credentials, and we will also show where in the Kyma dashboard,
this can be done.
Okay, I am connected here to SAP BTP cockpit, at the global account level, not connected
to any subaccount.
We are not concerned here with regions and cloud providers, or environments.
We are not consuming any resources, we are just working with metadata at this stage.
Under System Landscape we find the Systems entry.
Select Register System.
wWe need to provide a system name and type.
These are the available types, time of recording, and for this video, we will select SuccessFactors.
You can use any name, here I’ll be using the SuccessFactors company code, the tenant.
The registration action generates an integration token, which we can copy to clipboard, and
then close.
Status is now pending.
Now we need to switch to the SuccessFactors Admin Center, to finish the pairing.
Go to the Extension Center and then here, it is a bit hard to read, select extensions
for SAP BTP, and paste the integration token (Add).
Status is integrating, and if you refresh, after a couple of seconds it will change to
integrated.
Note that the system name corresponds to the one we just entered.
If we then return to the BTP cockpit, and refresh the page, or switch views, the status
will also have changed to Registered.
That’s step 1.
Next we need to entitle a subaccount to access this system.
This will be familiar, same steps as for the Kyma runtime: Entitlements, Entity Assignments.
Select one or more entities, the subacount that is (Go).
Configure Entitlement, Add Service Plan, search for SuccessFactors.
The entitlement has been added automatically by the previous task.
All we need to do is select the available plan: api-access,
Access for the SuccessFactors HXM Suite OData API
Add Service Plan, save.
Here we have the entry listed; the resource provider is the system we just registered.
Okay, step 2.
Check.
Next, we need a service instance in the Kyma environment, which will setup a destination
for us to our SuccessFactors system.
Navigate to the Kyma Dashboard, There are different ways how you can access
the dashboard.
You may have bookmarked it.
Go to the namespace where your extension will be hosted: Service Management, Catalog.
This is the equivalent of the Service Management for Cloud Foundry.
Search for SuccessFactors Provision the service class, as described,
once instance per namespace.
The name will be made unique with a random suffix, you probably have seen this before,
you can change this as needed.
There is only a single plan: api-access.
Optionally add some labels, maybe to tag the service to your app and add parameters.
This is required, the creation will fail otherwise.
We need to add the system name, same one you use for the registration in step one.
Optionally, you can also specify the name to be used for the technical user, which will
then be included in the destination configuration (Create).
Status is provisioning and after a few seconds this 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.
And this where you can perform this task.
Should the binding require credentials, you can configure this here as well.
When we take a look at the workloads, we can see that we now have a pod and a deployment.
The pod is a default gateway, using Istio, so microservices and functions can use the
BTP destination.
Should there be any issue, you can access the logs here.
Or take a look at configuration, edit if required, or just enjoy this piece of Kyma plug and
play automation.
Same for deployment, the pod comes as part of deployment,
Okay, back to the BTP Cockpit, Connectivity, Destinations, and here we have the generated
entry using Oauth2SAMLBearerAssertions as authentication and here we have our technical
user as additional property of the configuration.
You can check the configuration and this should return a 200 OK.
That’s step 3.
Single sign-on will be covered in the next video, part two.
This video tutorial was recorded by Denys van Kempen, SAP HANA Academy / SAP Partner
Innovation Lab For updates, don’t forget to subscribe.
Thanks for watching.