Configuring Data Sources
You use details from the Cloud Connector that you set up in SAP BTP Cockpit to provide information in the data
source configuration in Visualization. Make the following relevant settings in the Connection section of the data
source configuration.
• In URL, specify Host name as the proxy host name (this is also the Virtual Host used in the Cloud
Connector configuration, for example, S4H). Host name is shown in SAP BTP Cockpit for the Cloud
Connector under Exposed Back-End Systems. URL also specifies the service that the data source connects
to in the S/4HANA system.
• Set Proxy Type to On Premise. This makes the connection to the S/4HANA On-Premise system through
the Cloud Connector.
• [optional] If a Location ID was specified when connecting the Cloud Connector to the subaccount, set
Location ID to be the same as the Master Instance name configured in the Cloud Connector in SAP BTP
Cockpit.
• In Authentication, select the authentication method. If you have configured principal propagation, select
Principal Propagation. Otherwise, select Basic Authentication and enter the username and
password of a technical user in the S/4HANA On-Premise system.
For more information about configuring a data source, see Creating a New Data Source.
6.13.2 Configuring Destinations for Visualization APIs
Configure destinations to call the Visualization service APIs from SAP BTP services.
Some BTP services use credentials stored in SAP BTP destination to make API calls to external services. You
can create a destination in your subaccount to allow the Visualization APIs to be called from the BTP services
such as the Workflow service.
Prerequisites
• You've subscribed to Visualization SaaS application in your subaccount.
• You've an instance of the Visualization service in your subaccount that is linked to your Visualization SaaS
subscription, see Configuration for Using APIs [page 558] for details.
• You've created a service key for the Visualization service instance without providing any parameters, see
Creating Service Keys for details .
Authentication Types
The OAuth2UserTokenExchange and OAuth2ClientCredentials authentication types are commonly
used when calling Visualization service APIs via a destination.
When an authentication type of OAuth2ClientCredentials is used, client credentials are used to
authenticate with the Visualization service instance. Client credentials provide access on behalf of a service
Administration Guide
Connectivity PUBLIC 181
(as opposed to access on behalf of a user). Internally, when client credentials are used, Visualization uses
a special user (the Service user). In this case, folder and visualization access is determined by the access
granted to the service user.
When an authentication type of OAuth2UserTokenExchange is used, the user identity that is being used by
the calling SAP BTP service is used for the API calls made to Visualization. This means that the folders and
visualizations access is applied in Visualization for individual users.
An authentication type of OAuth2UserTokenExchange can be used when the service instance that is making
API calls to the Visualization service instance is in the same subaccount as the Visualization service instance or
is in a subaccount that has a trust relationship with the subaccount that the Visualization service instance is in.
A destination with an authentication type of OAuth2UserTokenExchange needs to be used to make an API
call to a Visualization service instance using principal propagation.
For more information about configuring a service task to use principal propagation, seeConfiguring Principal
Propagation for Service Tasks.
Destination Configuration
To create the destination at the subaccount level, enter the destination details as shown in the following table:
Property Description
Name Enter a name of your choice
The destination name is used to find the destination and uniquely identifies it in the subaccount.
Type HTTP
Description Enter a description
URL Enter the url value from the api object within the endpoints object in the service key.
Proxy Type Internet
Authentication Select OAuth2UserTokenExchange or OAuth2ClientCredentials as per your require-
ments
Client ID Enter the client_ID value from the uaa object in the service key
Client Secret Enter the client_secret value from the uaa object in the service key
Token Service URL Enter the url value from the uaa object in the service key and append /oauth/token
Administration Guide
182 PUBLIC Connectivity
