Multitenant SaaS apps on SAP BTP using CAP? Tried-and-True! – The Advanced Version
SAP BTP, Cloud Foundry Runtime scenario
SAP BTP, Kyma Runtime scenario
Hello and welcome again to the third part of the blog post series on building your own multitenant SaaS application on SAP BTP using CAP. The third blog post of the series will summarize the Advanced Version.
In the overview blogpost you have learned the general idea and motivation of developing multitenant SaaS applications in SAP BTP, in the basic version blog post you learned the fundamental implementation details of the multitenant SaaS application. In this blog post you will learn about the Advanced Version, which will take you one step closer to production readiness.
You will first grasp the scenario and the advanced version requirements for this SaaS application from the SAP sample partner, CaveStone. You will then see the architectural solution diagram before moving on to the solution’s implementation overview.
Scenario & Requirements
In this scenario our SAP Partner, has successfully completed and deployed the basic version, then they decided to take their solution to the next step. Of course, the next step has its own requirements. In addition to the basic version, the necessity of implementing the following requirements was determined because of the analysis. At the end there are only three additional requirements this time as described below.
- Having a central identity provider (IDP) for SaaS provider that is highly configurable
- In addition to have a multitenant SaaS API, the relevant API should have enterprise-level security, traceability, and monetisation. Also, the multitenant SaaS API should offer different request limits for different service plans.
- The capability for various clients to transfer data through the multi-tenant API from their SAP systems to the SAP Partners multitenant SaaS solution
Next, you might want to look over the architectural diagram now that you have a better understanding of the requirements.
Advanced Version- Solution Architecture
The first requirement is a centralized user storage. Software service providers naturally desire to manage their customers independently from the global SAP ID service, which is the major justification for this requirement. Additionally, it is typical for a software service provider to desire to change their multitenant application’s login interface. Given that the SAP IAS (Identity Authentication Service) satisfies all these criteria; you will configure the SAP IAS service in this sample application as the primary identity provider for your multitenant SaaS application. Relevant documentation can be found on this section of repository.
The last requirement is pushing data from different SAP systems of the clients (tenants) to your multitenant SaaS API to convert data into value. In this sample, you will learn how to push data from an SAP S/4HANA system. You will be implementing your ABAP program, and after that, you will be pushing data to your multitenant SaaS solution over your multitenant SaaS API endpoint. Implementation and details can be found here.
With this blog post, you have continued your journey, which you started with the overview blog post and the basic version blog post. You have seen how to integrate helpful SAP BTP services such as SAP IAS and SAP API Management. Following that, you learned how to use the ABAP stack to implement a push approach in the SAP S/4HANA system. Overall, you got one step closer to production readiness. With all the implementation details and step-by-step guide, feel free to try out the advanced version with your free-tier accounts and share your feedback! We are looking forward to hearing from you.
Feel free to follow me from here: SAP Community profile.
You might find following documentations, blog posts enlightening. Feel free to read them for detailed information.