We have released new versions of the SAP Cloud SDK. In detail, the following components are now available in new versions:
At the end of the article, you will find a set of instructions on how to update to the new versions.
SAP Cloud SDK User Survey Q3/2020
As part of our continuous effort to improve the SAP Cloud SDK, we’d like to ask you to participate in a 10-minute survey. This is the link to the survey.
The survey is anonymous. Feel free to forward this link to other members of your team who are also using the SAP Cloud SDK.
Thank you for your participation! Your answers will help us to make the SAP Cloud SDK even better.
Java Libraries: Release Highlights 3.29.1
You can update your dependencies of the SAP Cloud SDK for Java to version 3.29.1 and get the new version from Maven Central.
New and improved OData v2 Client
After we released the OData v4 support earlier this year, it is time to improve and optimize the way to consume OData v2 services too. The improved client for OData v2 is released as generally available and from now on the recommended approach for OData API consumption. In the same time we implemented some new functionality, such as better control over ETag handling. Refer to the documentation for more details on the usage of the new client.
DefaulErptHttpDestination can use a
java.security.KeyStore and a key store password for HTTP communication. This is especially useful when utilizing mutual TLS (mTLS) for the communication with a remote system.
Use the builder methods to set the desired values.
DefaultHttpDestination destination = DefaultHttpDestination.builder(uri).keyStore(keyStore).keyStorePassword(keyStorePassword).build();
We also updated the newly released support for SAP Cloud Platform Workflow to reflect the latest API features.
Several further improvements are listed in the full release notes.
In this version we are adding the possibility to mute and unmute loggers.
As usual, the full release notes contain a list of all improvements in this release.
How to Update
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
- Update the version of that dependency to
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.29.1</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-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.29.1.
Of course, you can also generate a new project that uses version 3.29.1 from the start by running the Maven archetypes for Neo or Cloud Foundry with
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
Learn more about SAP Cloud SDK
To learn how others in the community use SAP Cloud SDK you can check out more related blog posts.
Are you interested in a particular topic? It might be helpful to search the Q&A place? Feel free to ask your question there and do not 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.