With Kyma 2.0, there will be significant improvements in how one can access the data and update the state for connected SAP Solutions.
These improvements make the whole flow not only simpler but also reduce the number of components deployed thus improving the efficiency.
Disclaimer: This blog post focuses on Kyma runtime version 2.0 on SAP BTP. Keep in mind that adjustments might be needed at a higher release of Kyma.
How was it in pre-Kyma 2.0?
For every connected SAP Solution via application connector, as a developer you were
- Creating a Binding to the namespace from where you wanted to make API calls
- In the Bounded namespace, you will need to create instances of the API plans which you would like to consume.
- Then create service binding with a function or a microservice to access the gateway URL.
- Write code to make the API calls.
A gateway component was created in every namespace. The component acted as a proxy and also took care of injecting the credentials when making API calls to connected SAP Systems
With Kyma 2.0
To achieve the same result, you will
- Copy the Central Gateway URL of the API you would like to consume
- Use it in your business logic to make the API calls
That’s it. No more bindings or service instance creations.
This central application gateway acts as a proxy and takes care of injecting the credentials when making API calls to connected SAP Systems
- Fewer steps to consume APIs of connected SAP Solutions
- For now, Kyma will support both old and new models
Looking forward to your feedback and comments here.
If you have further questions about Kyma, feel free to post them in the answers area of the SAP Community, here is a link.
To stay up to date with everything in Kyma, make sure to visit our Kyma topic page.