Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
Marco_Dorn
Advisor
Advisor
633

When you are extending SAP Customer Experience solutions, you were able to find the API and Event metadata of your tenant inside the service catalog of SAP BTP, Kyma runtime. With its announced deprecation, a new place is required for this and it’s now available: The “System Landscape” view inside the SAP BTP global account cockpit. The whole area of the cockpit improved tremendously lately.




Finding the metadata


Once you registered an SAP CX solution, the “System Landscape“ view will tell you how many “Consumption Bundles“ are provided by the connected tenant. Opening the details of a registered system shows the complete list.



System Landscape view




In the details of a bundle, the “Actions” button will show you the metadata of the API bundle.




How to make use of that information


Inside SAP BTP, Kyma runtime, there are two major use cases:



Subscribing to events


When you want to subscribe your function or microservice to events, you need to know the event name and version. It’s a free text input field inside Kyma Dashboard (to allow subscription to in-cluster events, too). Now you can copy paste the information form “System Landscape” into the Kyma pop-up. E.g.


Copying event name to Kyma pop-up


Further read: Eventing – Whats new in SAP BTP, Kyma runtime?



Consumption of APIs


With the newly introduced application connectivity via a central gateway, the URLs of the API bundles inside Kyma runtime became predictable. Now you have the API metadata in the central place to better start programming against these APIs.

Further read: What’s new with Application connectivity in SAP BTP Kyma runtime?

What else is new in the landscape of systems


The former two menu items below “System Landscape” got merged into one flow. You can see in the details of each registered “System” which “Formations” it belongs to. This lets you clean up more easily as it’s only possible to remove a system when it’s de-registered from all Formations.


The usability and structure of the “Formations” tab was improved, too. It’s much easier to get an overview of all Formations, the included Systems, and its management.


PS: Wait for more improvements on their way particularly about the rendering of API and Event metadata!