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 Extension Suite certification.
The topic of this tutorial is SAP BTP Connectivity This video was recorded in May 2022.
For the latest tutorials on the topic, please check the playlist.
As mentioned in the previous video, when we discussed the SAP Cloud Connector, this concerns
the certification topic area: Connectivity; 6% weight; about 5 questions. Minor topic.
Documented in the SAP BTP Connectivity Guide. There are two connection types:
internet and cloud to on-premises. In the Cloud Foundry environment, there are
two services: Destination and Connectivity. The Destination service allows us to store
technical information about a target resource, which we can then use inside
our business application. Here we see this illustrated.
To connect our application to another service or system, we read credentials from
environment variables. These become accessible
when we bind the application to an instance of the xsuaa service, acting as an OAuth client.
How to connect to the service or system, the endpoint (virtual host and port), accessible
URL paths, authentication type, and so on is the kind of information stored in a destination.
We can create destinations manually using the web UI of the SAP BTP cockpit,
using a REST API, for this we can use the SAP API Business Hub, we covered this in a previous video,
using a multi-target application (MTA) descriptor, when we deploy applications,
also covered in another video in this series or by creating a service instance
of the destination service. There are pro’s and con’s
to each approach, so .. it depends. Here we are connected to the SAP BTP cockpit.
At the global account level, we can see that the service has been assigned to the subaccount.
Same for the Connectivity Service. This is not configurable.
When we navigate to our subaccount, Role Collections, note that there are also
Administrator roles and role collections for Destination, Cloud Connector,
and Connectivity and Destination, which are granted automatically
to the subaccount administrator, but you can fine tune this as needed.
The Connectivity service manages connectivity to Cloud Connectors,
we saw this in the previous video. We can create destinations here at
the subaccount level or by entering the space and accessing the service marketplace
create a new service instance of the destination service.
This can be done programatically, using the Cloud
Foundry CLI, but comes, as we just saw, with some limitations.
Back to the Destination menu at the subaccount level.
Here we can create destinations from scratch using a wizard,
import destinations, the configuration, the metadata that is, and establish trusts between
this SAP BTP subaccount as identity provider, IdP, and the source system, the targeted destination,
as service provider for single sign-on (SSO). For this we use X.509 certificates,
which we need to exchange and we can find the details in the documentation,
but this is beyond the scope of the exam. There are four types: HTTP, LDAP, MAIL, and RFC,
remote function calls, for use with ABAP. We have several authentication options:
basic (username, password), using certificates, using OAuth or SAML. and for proxy type we can
indicate whether this is a public service, or an on-premises system requiring the Cloud Connector.
To create a new destination, give it a name, optionally, a description, URL,
and, any optional properties which might be relevant for your scenario
Save You can edit and clone the configuration,
export, and check the availability of the destination connection:
200 OK the same menu is also presented here,
delete the destination , and import, plain text file, and voila. That’s it, for destinations
You can find the links to the resources mentioned in the description of this video below.
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.