Cloud Connector Subaccount Connection
The concept name provided is "undefined," and the supplied sources do not contain enough grounded detail to produce an accurate, source-supported definition for a specific SAP developer concept. A reliable definition cannot be written without a valid concept name and corresponding source content. Please provide a valid concept name and relevant source snippets so a precise definition can be generated.
Tutorials that teach this
Docs explaining this concept
Prerequisites
- Concept SAP BTP Account Model (Global Accounts, Subaccounts, Spaces) The concept name provided is "undefined," which does not correspond to a identifiable SAP developer concept. Based on the available sources — which cover topics such as global account administration, subaccount creation, the Cloud Foundry environment, and SAP BTP account management — there is insufficient information to produce a grounded definition for a concept labeled "undefined." Please provide a valid SAP concept name so an accurate and source-grounded definition can be written.
- Concept SAP BTP Subaccount and Entitlement Setup The provided sources do not contain sufficient information to define this concept. The concept name is "undefined" and none of the source snippets supply grounded content that could be used to write an accurate, sourced definition.
- Concept On-Premise Connectivity on SAP BTP **On-Premise Connectivity** on SAP Business Technology Platform refers to the capability that allows cloud applications to communicate securely with systems running in an on-premise landscape. Developers use it by [creating HTTP and RFC destinations](https://help.sap.com/docs/btp/sap-business-technology-platform/9b6510edf4d844a28f022b3db41f3202?locale=en-US&state=PRODUCTION&version=Cloud) to enable communication between SAP BTP and on-premise systems. Tools such as the Cloud Connector can be used to bridge on-premise databases or services — for example, connecting an SAP HANA on-premise system to SAP HANA Cloud — and trust configurations can be established between on-premise systems like SAP S/4HANA and SAP BTP to support secure integration scenarios.
- Concept SAP BTP Cockpit The concept name was not provided and the supplied source snippets do not define or describe a single, identifiable SAP developer concept — they cover a range of unrelated SAP BTP topics such as Kyma environment setup, Cloud Foundry org deletion, subaccount management, and service instances. A focused definition cannot be grounded solely in these sources without a clearly stated concept to define.
- Concept Cloud Connector Network Prerequisites The Cloud Connector requires specific network configuration to establish a secure tunnel between an on-premise network and SAP BTP. Developers and administrators must ensure that the Cloud Connector can reach the correct regional API endpoints for the [Cloud Foundry environment](https://help.sap.com/docs/btp/sap-business-technology-platform/f344a57233d34199b2123b9620d0bb41?locale=en-US&state=PRODUCTION&version=Cloud), as these endpoints vary by region. Proper firewall and proxy settings must allow outbound connectivity to the relevant SAP BTP region hosts so that the Cloud Connector can successfully connect to the platform.
- Concept SAP BTP Fundamentals and Platform Navigation
- Concept On-Premise Connectivity via Connectivity Service The concept name is not defined in the provided sources, so a grounded definition cannot be written. The sources discuss related topics such as [integrating on-premise systems](https://help.sap.com/docs/btp/sap-business-technology-platform/c95327fbed6c4efeb1855f12f826301d?locale=en-US&state=PRODUCTION&version=Cloud) via the Cloud Connector and the [SAP Connectivity ApiExt](https://help.sap.com/docs/btp/sap-business-technology-platform/4ed6d63105bd45578f73d7cf8c05d05c?locale=en-US&state=PRODUCTION&version=Cloud) feature provided by SAP Java Buildpack, but none of them define a concept identified as "undefined." No definition can be produced without a valid concept name and supporting source content.