Use the SAP Cloud SDK in the SAP Cloud Application Programming Model

For local development, you need to do the following:

1. Install Node.js from https://nodejs.org (use the latest LTS release).

2. Install the cds development kit globally:

   npm i -g @sap/cds-dk
   

3. Now, run:

   mvn archetype:generate -DarchetypeArtifactId=cds-services-archetype -DarchetypeGroupId=com.sap.cds -DarchetypeVersion=RELEASE \
   -DartifactId=cap-business-service
   

   This will initialise the application using the maven archetype cds-services-archetype and create your project as follows:

   • The project is named cap-business-service.
   • The db folder stores database-related artifacts.
   • The srv folder stores your Java application.

   

Find more information about the SAP Cloud Application Programming Model in its documentation.

CAP applications use Core Data Services (CDS) to describe:

• Data structures by using entity definitions
• How data structures are consumed by using service definitions

In this step, you’ll define a data model, which defines the entity.

1. Right-click on the db folder and choose New File.

   

2. Call it datamodel.cds and click OK to create the file.

3. Add the following service definition to the file.

   namespace my.bookshop;
   
   entity CapBusinessPartner {
     key ID : String;
     firstName  : String;
     surname  : String;
     sourceDestination: String;
   }
   

In this step, you’ll define a simple service, which exposes a projection on the entity defined in the data model.

1. Right-click the srv folder and choose New File.

   

2. Call the file cat-service.cds and click OK.

3. Add the following service definition to the cat-service.cds:

   using my.bookshop as my from '../db/datamodel';
   
   service cloud.sdk.capng {
        entity CapBusinessPartner as projection on my.CapBusinessPartner;
   }
   

4. Run the following command in the terminal to trigger the maven build process:

   mvn clean install
   

In your project directory, the data model has auto-generated the classes.

For integrating the SAP Cloud SDK in SAP Cloud Application Programming Model, you need to add the following dependency in your parent POM, which you find in the root directory of your project:

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>com.sap.cloud.sdk</groupId>
            <artifactId>sdk-bom</artifactId>
            <version>use-latest-version-here</version>
            <type>pom</type>
            <scope>import</scope>
        </dependency>
    </dependencies>        
</dependencyManagement>

Please make sure to always use the latest version available on Maven Central. Check out the release notes.

Since your application is running on SAP Cloud Platform Cloud Foundry, include the following dependencies to your pom.xml in the srv directory:

<dependency>
    <groupId>com.sap.cloud.sdk.cloudplatform</groupId>
    <artifactId>scp-cf</artifactId>
</dependency>

<dependency>
    <groupId>com.sap.cloud.sdk.s4hana</groupId>
    <artifactId>s4hana-all</artifactId>
</dependency>

<dependency>
  <groupId>com.sap.cds</groupId>
  <artifactId>cds-integration-cloud-sdk</artifactId>
</dependency>

For more information, visit the documentation of the SAP Cloud SDK.

1. Create a new Java class BusinessPartnerReadListener with the following content:

@Component
@ServiceName("cloud.sdk.capng")
public class BusinessPartnerReadListener implements EventHandler {

    private final HttpDestination httpDestination = DestinationAccessor.getDestination("MyErpSystem").asHttp();

    @On(event = CdsService.EVENT_READ, entity = "cloud.sdk.capng.CapBusinessPartner")
    public void onRead(CdsReadEventContext context) throws ODataException {

        final Map<Object, Map<String, Object>> result = new HashMap<>();
        final List<BusinessPartner> businessPartners =
                new DefaultBusinessPartnerService().getAllBusinessPartner().top(10).execute(httpDestination);

        final List<CapBusinessPartner> capBusinessPartners =
                convertS4BusinessPartnersToCapBusinessPartners(businessPartners, "MyErpSystem");
        capBusinessPartners.forEach(capBusinessPartner -> {
            result.put(capBusinessPartner.getId(), capBusinessPartner);
        });

        context.setResult(result.values());
    }

    @On(event = CdsService.EVENT_CREATE, entity = "cloud.sdk.capng.CapBusinessPartner")
    public void onCreate(CdsCreateEventContext context) throws ODataException {
        final BusinessPartnerService service = new DefaultBusinessPartnerService();

        Map<String, Object> m = context.getCqn().entries().get(0);
        BusinessPartner bp = BusinessPartner.builder().firstName(m.get("firstName").toString()).lastName(m.get("surname").toString()).businessPartner(m.get("ID").toString()).build();

        service.createBusinessPartner(bp).execute(httpDestination);
    }

    private List<CapBusinessPartner> convertS4BusinessPartnersToCapBusinessPartners(
            final List<BusinessPartner> s4BusinessPartners,
            final String destinationName) {
        final List<CapBusinessPartner> capBusinessPartners = new ArrayList<>();

        for (final BusinessPartner s4BusinessPartner : s4BusinessPartners) {
            final CapBusinessPartner capBusinessPartner = com.sap.cds.Struct.create(CapBusinessPartner.class);

            capBusinessPartner.setFirstName(s4BusinessPartner.getFirstName());
            capBusinessPartner.setSurname(s4BusinessPartner.getLastName());
            capBusinessPartner.setId(s4BusinessPartner.getBusinessPartner());
            capBusinessPartner.setSourceDestination(destinationName);

            capBusinessPartners.add(capBusinessPartner);
        }

        return capBusinessPartners;
    }
}

CDS Query Notation (CQN) is the common language in CAP to run queries against services. It can be used to talk to the services defined by your model, but also remote services, such as the database.

The event handler uses the following APIs, which are available for service providers in CAP Java:

• Event handler classes have to implement the marker interface EventHandler and register themselves as Spring Beans (@Component). The marker interface is important, because it enables the CAP Java runtime to identify these classes among all Spring Beans.
• Event handler methods are registered with @On, @Before, or @After annotations. Every event, such as an entity creation, runs through these three phases. Each phase has a slightly different semantic.
• The annotation @ServiceName specifies the default service name all event handler methods apply to. Here this is cloud.sdk.capng, as this was also the name when defining the service in the CDS model.

In order to make a call to an OData service, there needs to be a service to call. You can set up a local mock server that mimics the business partner and a custom service by following the instructions at Extending SAP S/4HANA. This mock server does not support all the features of the actual OData services, but it suffices to try it out locally.

Once it is up and running, you should see the list of services at http://localhost:3000/.

set destinations=[{name: "MyErpSystem", url: "https://URL", username: "USER", password: "PASSWORD"}]

set destinations

export destinations='[{name: "MyErpSystem", url: "https://URL", username: "USER", password: "PASSWORD"}]'

echo $destinations

1. Go to the root of your project by running the following command in the terminal:

   cd ~/projects/cap-business-service
   

2. Start the application:

   mvn clean spring-boot:run
   

   A notification message saying “A service is listening to port 8080” will appear in the bottom right.

3. Go to http://localhost:8080.

4. Choose $metadata from the welcome page to inspect the OData metadata that is automatically served by the CAP Java runtime.

Do the GET request on http://localhost:8080/odata/v4/cloud.sdk.capng/CapBusinessPartner from Postman. It fetches the businessPartner data from the mock server.

Try to insert some data into the running application. For example, use Postman to do the following post request on same link.

The POST request causes an OData Insert on the entity CAPBusinessPartner.

The response will be the created record and should look similar to this output:

{
  "@context": "$metadata#CapBusinessPartner/$entity",
  "ID": "1003764",
  "firstName": "abc",
  "surname": "xyz",
  "sourceDestination": "MyErpSystem"
}

You can read the data by doing the GET request on same URL .

You can configure a mock server instance to Cloud Foundry by going inside the mock server directory and pushing the instance to cloud. Do this by running:

cf push

Now configure the mock server destination in Cloud Foundry.

1. Navigate to the Cloud Foundry subaccount.

2. In the menu on the left, go to Connectivity > Destinations.

3. Click New Destination and enter the following values into the input fields:

   • Name: MyErpSystem
   • URL: URL to your mock server
   • Authentication: choose BasicAuthentication
   • Provide credentials of your technical user in the User and Password fields.
   • Leave the other fields unchanged.

4. Click Save.

You can get mock server URL by running:

cf app odata-mock-server

You need to bind destination service to your application in order to use it.

Use the Cloud Foundry CLI to create the destination service instance:

cf create-service destination lite MyErpSystem

1. Go to the ~/projects/cap-business-service folder and create a new file called manifest.yml.

   Save the file.

2. Add the following code to the newly created file:

     ---
     applications:
       - name: cap-business-service
         path: srv/target/cds-services-archetype-exec.jar
         random-route: true
     services:
       - MyErpSystem
   

   The manifest describes the name of the application and the path where the application archive can be found. Spring Boot applications can be deployed from a single JAR archive, which is what you are making use of here.

3. Open the pom.xml file in the srv directory.

4. Add the following dependency under the dependencies tag:

     <dependency>
       <groupId>com.sap.cds</groupId>
       <artifactId>cds-feature-cloudfoundry</artifactId>
     </dependency>
     <dependency>
       <groupId>com.sap.cds</groupId>
       <artifactId>cds-feature-hana</artifactId>
     </dependency>
   

5. Add the following annotation to your Application class:

   @EnableAutoConfiguration(exclude = DataSourceAutoConfiguration.class)
   

   This will allow you to deploy to Cloud Foundry without any database service binding.

6. Build your application once by running:

   mvn clean
   install
   

7. Push the application to the cloud by running:

   cf push
   

   The manifest will be automatically picked up.

   Provide the credentials you usually log in to SAP Cloud Platform if you are asked to log in.

   You can see the following, if the application was successfully deployed.

   

8. To retrieve the application URL run the following command:

   cf app cap-business-service
   

   You can find URL, next to routes.

   

Now you can do the GET / POST request in the same way as described in step 9.