BTP & Integrationintermediate

BTP Destinations Part 2: Proxy Types, Authentication Methods and Cloud Connector

Key takeaway

Configure destinations for real systems: proxy type Internet vs OnPremise, location ID for multiple Cloud Connectors, virtual host mapping, authentication types (NoAuthentication, BasicAuthentication, OAuth2ClientCredentials, OAuth2SAMLBearerAssertion, PrincipalPropagation, client certificates), and testing.

Explanation

📌 KEY POINTS
✅ Internet: direct HTTPS to cloud targets; OnPremise: routed via connectivity service and Cloud Connector.
✅ OnPremise URLs use the virtual host/port exposed in Cloud Connector, not the real host.
✅ Location ID selects the right Cloud Connector when several are connected to one subaccount.
✅ Authentication type must match what the target expects (technical vs user-based).
⚠️ Check connection success only proves reachability — authentication and authorization must be tested with real calls.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 explained destinations. Now configuration details.

━━━━━━━━━━━━━━━━━━━━
▶ 1. PROXY TYPES

Internet vs OnPremise.

━━━━━━━━━━━━━━━━━━━━
▶ 2. VIRTUAL HOSTS & LOCATION ID

Cloud Connector mapping; multiple connectors.

━━━━━━━━━━━━━━━━━━━━
▶ 3. AUTHENTICATION TYPES

Basic, OAuth2 client credentials, SAML bearer, principal propagation, certificates.

━━━━━━━━━━━━━━━━━━━━
▶ 4. ADDITIONAL PROPERTIES

sap-client, HTML5.DynamicDestination, WebIDEEnabled.

━━━━━━━━━━━━━━━━━━━━
▶ 5. TESTING

Check connection + real request.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Create OnPremise destination to virtual host.
Set location ID if needed.
Test with a real OData call.

✅ CHECKPOINT: call succeeds with expected user context.

Code example

ABAP Code

===== ONPREMISE DESTINATION =====URL: http://s4h-virtual:44300 (virtual host from Cloud Connector)ProxyType: OnPremise | CloudConnectorLocationId: EU_PLANTAuthentication: PrincipalPropagation | sap-client: 100 ===== INTERNET DESTINATION =====URL: https://api.partner.com | ProxyType: Internet | Authentication: OAuth2ClientCredentialsClient ID / secret (or certificate) | Token Service URL

Real project scenario

A company added a second Cloud Connector for another data center; calls randomly failed. Destinations lacked location IDs. Setting location IDs on both connectors and destinations routed traffic correctly.

Common mistakes

Real host instead of virtual host.
Missing location ID.
Dialog user passwords.
Only testing check connection.
No inventory.

Best practices

Use virtual hosts.
Location IDs for multiple connectors.
Technical/propagated users.
Real call tests.
Destination inventory.

Interview angle

Questions: "Internet vs OnPremise?", "What is a location ID?", "Which authentication types exist?"
Strong answer: proxy types, virtual hosts, location ID, auth types, testing.

Practice this lesson

Quick check

1. Which destination type would typically be used to configure a connection from a cloud application to an ABAP system for calling remote function modules over RFC?

2. When multiple Cloud Connector instances are subscribed to the same BTP subaccount, which destination property is used to route an OnPremise destination's traffic to a specific Cloud Connector instance?

3. A developer needs to configure a destination in the SAP BTP cockpit that connects a cloud application to an on-premise SAP system via Cloud Connector. Which Proxy Type must be selected for this destination?

Interview questions

1. How would you apply Destinations in a real SAP project? Walk through the design or implementation approach.

Answer it in your own words first, then compare.

2. What are the most important design decisions, trade-offs, and best practices in Destinations?