Develop a Multitenant Extension Application in SAP BTP, Kyma Runtime

Alexander Rieder, Matthieu Pelatan

Introduction

Basis Mission

Identity Management Mission

Day2 Operations Mission

Q&A

Step-by-step guide

Code in GitHub

Mock Server included

btp-setup-automator

Coaching, troubleshooting & FAQ

As soon as a customer is onboarded, the SaaS Registry triggers the onboarding process. A request with all information about the new tenant (for example, tenant ID and subdomain) in the body is sent to the application broker.
The broker extracts the tenant ID and the subdomain out of the request body and triggers actions defined in the callbacks. In our case, the DB service is informed about the new onboarding.
The Database service creates a new schema/user for the new customer. Standard tables and default configuration are automatically generated.

An end user opens the application in a browser. The browser sends a request to the Approuter.
The end user is redirected to the SAP Authorization and Trust Management service to log in.
After a successful login, the SAP Authorization and Trust Management service sends a JWT token to Approuter, which extracts the tenant ID. The tenant ID will be needed later to call the data from the right tenant.
The Approuter redirects to UI.
The UI sends a request to backend API via the Approuter.
The Approuter injects the tenant ID in the request as a header and forwards the request to the Easy Franchise service.
The Easy Franchise service receives request as an orchestrator and forwards it to the respective microservice including the tenant ID. Here, it's part of the URL, which makes it simpler to log or debug at development time.
The Database service requests data from the respective tenant.
The Business Partner service gets information from the destination in the respective subaccount and calls the SAP S/4HANA Cloud system.