SAP BTP · Cloud Connector & Connectivity

Beyond avoiding hardcoded endpoints, what does using one fixed destination name (say, ERP) across your dev and prod tenants buy you organizationally?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Cloud Connector & Connectivity

You're installing a shadow Cloud Connector alongside a running master on the same host. What are the easy-to-miss differences from a normal install?

After you enable HA on the master, it warns 'No Shadow Host Restrictions.' What's the security implication, and how do you lock it down correctly?

You need a second person to administer the Cloud Connector. Why isn't just adding another account in the UI enough, and what does multi-user actually require?

Your destinations are modeled and visible in the space, but a cloud app fails to use them at runtime. What prerequisite is missing?

Your app calls a public internet REST API and also an on-premise ABAP system. Which needs the Connectivity service and which only needs the Destination service?

Before installing a newer Cloud Connector, why must you check the host's JVM version first?

Start learning today

Free to start — download the app or use it in your browser.