How to Integrate On-Premise SAP Data with SAP BTP Using SAP Cloud Connector

Integrating on-premise SAP data with SAP Business Technology Platform (BTP) is essential for modern businesses seeking seamless data access across environments. The SAP Cloud Connector is a secure middleware solution that bridges SAP BTP applications and on-premise SAP systems without complex network configurations or VPN setups.

Business Scenario

Consider a scenario where an enterprise needs to access live inventory data from its on-premise SAP ERP system in real-time through a SAP BTP-based Fiori application. Employees can use this app to check stock levels, retrieve supplier information, and monitor product availability. Since this app is cloud-based and the data resides in an on-premise system, a secure and efficient connection is necessary. The SAP Cloud Connector enables this setup by securely exposing the ERP system to SAP BTP without compromising data security.

More Such Questions

Solution: Integrate On-Premise SAP Data with SAP BTP Using SAP Cloud Connector

This solution involves the following steps:

  1. Installing and configuring the SAP Cloud Connector.
  2. Setting up a connection in the SAP BTP Cockpit.
  3. Configuring on-premise system access and exposing necessary resources.
  4. Testing the connection and accessing data through an OData service.

Let’s go through these steps in detail.

Step 1: Install and Configure SAP Cloud Connector

  1. Download the Cloud Connector: Download the SAP Cloud Connector from the SAP Support Portal. Make sure you have the required access to SAP ONE Support.
  2. Install the Cloud Connector: Follow the instructions provided for your operating system (Windows, Linux, etc.). After installation, start the Cloud Connector service.
  3. Access Cloud Connector Admin Interface: Open a web browser and navigate to https://localhost:8443. Log in with the default credentials (Administrator / manage).
  4. Change Default Password: For security reasons, change the default password after your initial login.

Step 2: Connect SAP Cloud Connector to SAP BTP Account

  1. Add a New Subaccount: After logging in, go to the Cloud To On-Premise section. Click Add Subaccount and enter the following details:
    • Region: Select the region of your SAP BTP account (e.g., us10, eu10).
    • Subaccount: Enter the subaccount name from SAP BTP.
    • Display Name: Provide a descriptive name.
    • Subaccount ID: Enter the unique subaccount ID from the SAP BTP Cockpit.
  2. Verify Connection Status: Once saved, the connection status should show Connected. This indicates that the SAP Cloud Connector is now successfully connected to your SAP BTP subaccount.

Step 3: Configure On-Premise System Access

  1. Add On-Premise System: In the Cloud To On-Premise section, click Add System Mapping to configure the on-premise SAP system.
    • Backend Type: Choose ABAP System if your on-premise system is SAP ERP or S/4HANA.
    • Protocol: Select HTTP or HTTPS, depending on your SAP system configuration.
    • Internal Host and Internal Port: Enter the host and port of the on-premise system. For instance, if your system’s IP address is 192.168.1.10 and uses HTTP on port 8000, enter these values.
    • Virtual Host and Virtual Port: This mapping will be used by SAP BTP to access the on-premise system. These values are usually the same as the internal host and port unless specified otherwise.
  2. Define Resource Accessibility: Click + to add accessible resources, such as OData services. In URL Path, specify the resource path, like /sap/opu/odata, which is commonly used for OData services.
    • Set the Access Policy to Path and all sub-paths for comprehensive access to services within the specified path.
  3. Set Principal Propagation (Optional): If using user authentication to access on-premise data, configure Principal Propagation under Principal Type. This enables SAP BTP applications to pass user credentials to the on-premise system.

Step 4: Create Destination in SAP BTP Cockpit

  1. Open SAP BTP Cockpit: Go to the SAP BTP Cockpit and navigate to your subaccount.
  2. Create Destination: Under Connectivity > Destinations, click New Destination and provide the following details:
    • Name: Choose a unique name for this destination (e.g., OnPremiseERP).
    • Type: Set to HTTP.
    • URL: Use the virtual host and port defined in the SAP Cloud Connector (e.g., http://192.168.1.10:8000).
    • Proxy Type: Set to OnPremise to route traffic through the SAP Cloud Connector.
    • Authentication: Select the relevant authentication method (e.g., BasicAuthentication).
    • Additional Properties: Add WebIDEEnabled = true to enable usage in SAP Web IDE, and add TrustAll = true if you’re testing without a full SSL setup.
  3. Test Connection: After saving the destination, use the Check Connection button to ensure it connects to the on-premise system successfully. If configured correctly, you’ll see a Connection successful message.

Step 5: Expose OData Service on SAP BTP

  1. Activate OData Service: In your on-premise SAP system, activate the OData service through Transaction Code /IWFND/MAINT_SERVICE. Here, you can enable and test the OData service required by the BTP application.
  2. Test the OData Service URL: Use SAP Gateway Client (/IWFND/GW_CLIENT) or a tool like Postman to test the OData service. The URL format is:phpCopy codehttp://<virtual_host>:<virtual_port>/sap/opu/odata/sap/<service_name>/
  3. Consume OData Service in SAP BTP Application: With the destination configured and OData service active, use SAP Web IDE, SAP Business Application Studio, or other SAP BTP tools to consume the service in your BTP applications.

Tips and Best Practices

  1. Use System Aliases for Flexibility: If you have multiple SAP systems, system aliases allow easy mapping changes in SAP Gateway.
  2. Monitor Cloud Connector Logs: Regularly check SAP Cloud Connector logs to troubleshoot any connectivity issues.
  3. Secure Principal Propagation: If using Principal Propagation, ensure secure setup with trusted authentication between SAP BTP and on-premise systems.
  4. Optimize OData Services: To improve performance, select only necessary fields and avoid complex calculations in CDS views or OData services.
  5. Use Role-Based Access Controls: Configure appropriate roles and authorizations on both the SAP BTP and on-premise system to restrict data access securely.

By following these steps, you can securely integrate on-premise SAP data with SAP BTP, providing real-time data access in cloud applications. This setup streamlines data sharing, boosts productivity, and enables SAP BTP applications to leverage essential enterprise data directly from on-premise systems.

Leave a Comment