Skip to Content
Product Information

New Versions of SAP Cloud SDK: 3.31.0 for Java, 1.30.0 for JavaScript, v43 for Continuous Delivery

We have released new versions of the SAP Cloud SDK. In detail, the following components are now available in new versions:

In this blog post, we will walk you through the highlights of these releases. For a complete overview, visit our release notes for the Java libraries, for the JavaScript libraries, and for the continuous delivery toolkit. The release notes also include the change log of all our releases so far.
At the end of the article, you will find a set of instructions on how to update to the new versions.

Java Libraries: Release Highlights 3.31.0

You can update your dependencies of the SAP Cloud SDK for Java to version 3.31.0 and get the new version from Maven Central.

Client Libraries for SAP S/4HANA On-premise

We released new pre-generated type-safe client libraries (also known as Virtual Data Model – VDM) for the latest RTC release 2020 of SAP S/4HANA On-Premise. The supported services and business objects are described in the SAP API Business Hub for SAP S/4HANA On-Premise 2020.

Improving the Consistency between OData v2 and v4 Clients

We are working to unify the client libraries for OData v2 and OData v4 APIs as much as possible. Since SAP Cloud SDK version 3.30.0, the API for custom header configuration has been simplified and partially deprecated. This applies to the OData v2 client library only.

requestV2
    .withHeader("Authorization", "Basic user:secret")
    .onRequestAndImplicitRequests() // deprecated
    .withHeader("User-Agent", "Robot")
    .onRequestOnly() // deprecated
    .execute(httpDestination);

// the above code still works, but should be changed to:

requestV2
    .withHeader("Authorization", "Basic user:secret")
    .withHeader("User-Agent", "Robot")
    .executeRequest(httpDestination);

Don’t worry if you don’t have time to adjust your coding right now. The deprecated code is still usable. No breaking changes in code or behavior are introduced.

Further improvements

Generated OData V4 client library service types provide a new method batch() to conveniently create instances of BatchRequestBuilder. It can be used to combine multiple reading and modifying OData operations into one OData Batch request.

Several further improvements are listed in the full release notes.

JavaScript Libraries: Release Highlights 1.30.0

The JavaScript libraries of the SAP Cloud SDK are now available in version 1.30.0.

We added support for batch requests on OData v4 services.

Starting from version 1.29.0, SAP Cloud SDK supports the usage of $count in getAll requests. For example you can do the following:

Entity.requestBuilder().getAll().count().execute()

Further improvements

As usual, the full release notes contain a list of all improvements in this release.

Continuous Delivery Toolkit: Release Highlights v43

We have also released version v43 of our out-of-the-box continuous delivery offering consisting of a ready-made Jenkins server and a complete delivery toolkit.

In the recent releases we keep consolidating the configuration format in alignment with the related services offered on SAP Cloud Platform.

You can find further fixes and improvements in the complete release notes.

How to Update

Java libraries

To update the version of the SAP Cloud SDK Java libraries used in an existing project, proceed as follows:

  • Open the pom.xml file in the root folder of your project.
  • Locate the dependency management section and therein the sdk-bom dependency.
  • Update the version of that dependency to 3.31.0.

With this, you are already done thanks to the “bill of material” (BOM) approach. Your dependency should look like this:

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>com.sap.cloud.sdk</groupId>
            <artifactId>sdk-bom</artifactId>
            <version>3.31.0</version>
            <type>pom</type>
            <scope>import</scope>
        </dependency>
    </dependencies>
    <!-- possibly further managed dependencies ... -->
</dependencyManagement>

If you update from a version prior to 3.0.0, have a look at our migration guide.

If you are using the SAP Cloud SDK in a project of the SAP Cloud Application Programming Model, replace sdk-bom with sdk-modules-bom to only update the version of SDK modules, not further dependencies.
You can now recompile your project (be aware of the compatibility notes, though) and leverage the new features of the SAP Cloud SDK in version 3.31.0.

Of course, you can also generate a new project that uses version 3.31.0 from the start by running the Maven archetypes for Neo or Cloud Foundry with -DarchetypeVersion=3.31.0 (or RELEASE).

JavaScript libraries

To update the version of the SAP Cloud SDK JavaScript libraries used in an existing project, use the command npm update in the root folder of your module. Note that this will also update other modules, unless you explicitly specify which packages to update. If you want to check beforehand what will change, use npm outdated.

Continuous Delivery Toolkit

If you are using the pipeline with a fixed version (as recommended since v7), update the continuous delivery toolkit with the following command, that you run on the server hosting the cx-server:

./cx-server update image

Learn more about SAP Cloud SDK

Are you interested in details about a particular topic? Have a look at the SAP Cloud SDK documentation portal.

To ask a question or learn how others in the community use SAP Cloud SDK you can check out the Q&A place. Don’t forget to select the tag SAP Cloud SDK

If you are new to SAP Cloud SDK, get started and gain first hand-on exercise by following our tutorials.

/
Be the first to leave a comment
You must be Logged on to comment or reply to a post.