Hi, my name is Denys van Kempen, SAP HANA Academy.
You are watching a video tutorial that is part of a series about the SAP Business Technology
Platform, SAP Integration Suite certification, covering API Management concepts.
This video was recorded in March 2022.
For the latest tutorials on the topic, please check the playlist.
This video will be a bit of a bonus video.
The concepts of SAP API Management are not in scope of the exam (not in any depth).
But for those new to API Management, it might help to distinguish the different portals
and understand how the pieces fit together.
SAP API Management has been around for some time and goes back to a partnership agreement
from 2014 with a company called apigee, which in the mean time acquired by Google.
The techology powering API Management “under the hood” is apigee’s, not SAP,
like Cloud Elements for SAP Open Connectors, and this explains some of the differences
and terminology between API Management compared to the other capability of the Integration
Suite.
We already briefly looked at both portals, the API Portal, where we develop, analyze
and monetize APis and some of the objects, the artifacts, APIs,
API providers, products and the developer portal, the API Business
Hub Enterprise, which application developers can use to discover
and subcribe (consume) API As illustrated
the API provider is the source (here system).
So, we start with adding API providers to the API portal.
For this, we are going to use the Configure menu
Next, we are going to create the API (here API proxy)
referencing an endpoints, a specific path, a URL, to a system and hence the many to one
relation API proxies are fairly complicated artifacts,
as we will see This is where all the magic happens, all the
metering, security, mappings, and so on.
In order to make APIs accessible, we create a product,
and a product contains one or more APIs and this would typically correspond to a business
scenario.
A product includes a rate plan and access permissions, although both are optional, they
are not required and we need to publish a product to a catalog
before it can be used.
To recap, we start with adding a system, the API provider
next, we create, develop, and deploy the API (API Proxy in apigee terminology)
and to make the API accessible, we create and publish a product
This is what we can do in the API portal of API management.
We create APIs and products from the Develop menu but not applications,
as you can see there is no create button For this, we need to switch to the Dev Portal
and switch roles, switch persona we are no longer concerned with API development
or API management but with application development, and as application developer we need subscribe
to a product before we can access, before we use the APIs
inside, and this subscription is called an application.
The terminology is apigees’ but if you have worked with APIs development before,
this will not be new Here we have, for example, the Twitter Developer
Portal, same name and here we also create an app
which corresponds to a subscription, with a API key and token
enabling Twitter to track, authorize,
and monetize our API consumption.
we also see the concept of products here we have the apigee documentation, fundamentals,
explaining organizations, showing the major components
the developer, the app, the subscription with API key, the product, the API proxy
and here we have the concepts of API management, showing the same picture.
Here is another illustration, with the two portals, one for API development,
one for application development with the product as bridge,
we publish a product containing one or more APIs, API proxies
and as app developer we subscribe to these products and this subcription is called an
application and is identified with a key, which makes it possible to track API usage,
to manitor and to monetize.
here is another view, from the documentation of API Management
with the different roles, you may recall that enabling API management
added 11 role collections, 4 for the API portal,
7 for the developer portal, the API Business Hub Enterprise
and you may also recall that after we added the API management capability to the suite
and added the API Portal onboarding role collection to our user
upon first access of the API portal app it took another 3, 4 minutes to provision
the application, that is, to create the API runtime and set
everything up.
If you have a little time, suggest to scan the Concepts and Components sections of the
documentation There is also a tutorial on the SAP Developer
Center, covering API Management in depth, and also many articles on the SAP community,
should you wish to learn more.
Now, as mentioned at the start, what we covered is all beyond the scope of the exam.
For the certification, there are only a couple of things you need to know about API Management,
which we will cover in the next video.
That’s it for API Management concepts.
This video tutorial was recorded by Denys van Kempen, SAP HANA Academy.
Any good?
Give us a like, and for updates, don’t forget to subscribe.
Thanks for watching.