We have released new versions of the SAP Cloud SDK. In detail, the following components are now available in new versions:
- Java libraries in version 3.16.1
- Continuous delivery toolkit in version v30
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.16.1
You can update your dependencies of the SAP Cloud SDK for Java to version 3.16.1 and consume the new version from Maven Central.
Java 11 Support
SAP Cloud SDK can now be used with Java 11. To try out if your project works with Java 11, you can update the Java version in the
pom.xml and recompile. If everything compiles and behaves as expected locally, you can configure Cloud Foundry to use Java 11 too. See this page for more details how to do that.
Note that with this release we removed the Olingo dependency from the Virtual Data Model (VDM). Olingo types are now set as custom fields and can be accessed by the method
As of this version, JSON Web Tokens (JWT) are validated using their
jku properties. Public keys for signature verification are fetched from the URL specified by the
jku property. This only works if the
issuer domain matches the domain of the XSUAA service. In case this fails or if the properties are not set, the implementation falls back to the previous validation mechanisms (e.g. verification key of XSUAA service binding, XSUAA token endpoint provider).
This version fixes an issue with a missing authorization header when using
Principal Propagation for on-premises connectivity on Cloud Foundry.
We also fixed some special characters escaping and encoding issues in the OData v4 support.
Several further improvements are listed in the full release notes.
In this SAP Cloud SDK release, we introduced validation of the destinations configuration. Due to this change, destinations of type
HTTP are expected to contain a
URL property. Note that when retrieving a destination from the
destinations environment variable, all destinations are validated. This validation applies even to destinations that are not read and can lead to unexpected failure messages.
Further, we fixed the destination processing so that
Principal Propagation can be used as an authentication scheme for on-premises connectivity.
As usual, the full release notes contain a list of all improvements in this release.
Continuous Delivery Toolkit: Release Highlights v30
We have also released version v30 of our out-of-the-box continuous delivery offering consisting of a ready-made Jenkins server and a complete delivery toolkit.
With our release v30, we added support for configuring the Cloud Foundry Service Broker for SAP HANA Deployment Infrastructure (HDI) containers on SAP Cloud Platform. Read the documentation for details.
As of release v30, the pipeline is more lenient with regards to the MTA project structure. The existence of an
integration-tests module is not enforced anymore.
You can find further fixes and improvements in the complete release notes.
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.16.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.16.1.
Of course, you can also generate a new project that uses version 3.16.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
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
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.