- Java libraries in version 2.13.3,
- Continuous delivery toolkit in version v17.
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 2.13.3
You can update your dependencies of the SAP S/4HANA Cloud SDK for Java to version 2.13.3 and consume the new version from Maven Central.
This is a maintenance release with the improvements and fixes listed in the full release notes.
Additionally, we have published a blog post on how to access any REST service with the help of the SAP S/4HANA Cloud SDK (and OpenAPI). An accompanying step-by-step tutorial helps you put this into practice to easily consume REST services described using OpenAPI with the type-safety and convenience of the SAP S/4HANA Cloud SDK.
The release notes contain a list of the major features in this first release.
Continuous Delivery Toolkit: Release Highlights v17
We have also released version v17 of our out-of-the-box continuous delivery offering consisting of a ready-made Jenkins server and a complete delivery toolkit.
As before, you can set up and manage the Jenkins build server using the tools provided by the continuous delivery toolkit, as explained in the general tutorial. The approach to configuring the pipeline to your project remains the same as well.
Sidecar containers for integration tests
Integration tests have the goal to test the working-together of different components of a system. Depending on the nature of your application, this can include a database or other backend systems. For making integration tests reliable, it is good practice to start from a clean slate and do as much as reasonable locally. This can be done by starting backing systems required for integration tests as a container.
With version v17, we enable integration tests which in this manner rely on other systems that can be started as a local container. For this,you can now specify a sidecar image. The pipeline will start a container for this image before executing the integration test. For more details, consult the documentation on how to configure this feature.
We have set the Chromium browser used during end-to-end tests to the older version 70 to mitigate issues with end-to-end tests.
You can find further fixes and improvements in the complete release notes.
How to Update
To update the version of the SAP S/4HANA 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.s4hana</groupId> <artifactId>sdk-bom</artifactId> <version>2.13.3</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> <!-- possibly further managed dependencies ... --> </dependencyManagement>
If you are using the SAP S/4HANA 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 S/4HANA Cloud SDK in version 2.13.3.
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