Skip to Content

Expose Your ABAP OData Services with the SAP Cloud Connector

0 %
Expose Your ABAP OData Services with the SAP Cloud Connector

Expose Your ABAP OData Services with the SAP Cloud Connector

November 8, 2021
Created by
November 8, 2021
Expose services created from CDS views in your ABAP Developer Edition so that your SAP Conversational AI Enterprise Edition can call them.

You will learn

  • How to create CDS views
  • How to expose CDS views as OData Services
QR code

A cloud connector comes pre-installed in the ABAP Developer Edition, so that you can expose what you create to the cloud, especially to SAP Business Technology Platform, where our SAP Conversational AI Enterprise Edition instance resides.

Our chatbot in the SAP Conversational AI Enterprise Edition will want to call the OData services from our CDS views within our ABAP Developer Edition on-premise system (i.e., that is, on our laptop).

Step 1: Start the cloud connector
  1. Open a command prompt and run the following:

    docker exec -it a4h bash
  2. Now run the following:

    /usr/local/sbin/rcscc_daemon start

    It may take a few minutes for the cloud conector to start. You will get a message when it starts:

Cloud connector started

When it is ready, go to the following URL to open the browser interface:

Cloud connector login screen
Log on to answer question
Step 2: Log into cloud connector

Log into the cloud connector.

Out of the box, the user is Administrator and password is manage. You will have to change this after your first login.

Log on to answer question
Step 3: Add subaccount to cloud connector

You will now specify the SAP BTP subaccount to which you want to expose your on-premise system.

  1. Click Add Subaccount.

  2. Fill out the subaccount details.

    You will need the subaccount ID (not name), which you can find on the subaccount Overview page.

    Subaccount ID

    You will have to be an administrator in the subaccount.

    Add subaccount

    If you have 2-factor authentication enabled for your SAP ID account, you will have to append your token to your password.

  3. Click Save.

Your subaccount will be added to the left menu.

Subaccount in menu
Log on to answer question
Step 4: Add system mapping
  1. On the menu, click your subaccount, and then select Cloud to On-Premise.

    Access control
  2. In the Access Control tab, click the + sign next to Mapping Virtual to Internal System.

  3. Go through the wizard and fill out the following details:

    Field Name Value
    Back-end Type ABAP System
    Protocol HTTP
    Internal Host
    Internal Port 50000
    Virtual Host mydevedition
    Virtual Port 50000

    Fill the other fields with the defaults, and at the end, click Finish.

  4. Select your system mapping, and then click the + sign to add a resource.

    Fill in the following:

    Field Name Value
    URL Path /
    Access Policy Path and All Sub-Paths

    You can make the resource more restrictive.

    Click Save.

Log on to answer question
Step 5: Test yourself
The cloud connector allows who to access our on-premise service?

Next Steps

Back to top