We have released new versions of the SAP Cloud SDK. Before taking a closer look into what's new, there are a few other exicting topics to mention.
We have announced that the out-of-the-box continuous delivery pipeline of the SAP Cloud SDK for continuous d.... This allows you to start continuously delivering your CAP projects as easy as never before, without writing a single line of pipeline code. Visit us at SAP TechEd to try this hands-on.
In further news, we have relaunched our community page. The SAP Cloud SDK community page serves as your entry point to learn more about the SDK and to join the community. At the same time, the SAP Cloud SDK is also Topic of the Month of SAP Community.
Also noteworthy is this blog post about certification options for solutions on SAP Cloud Platform. The SAP Cloud SDK helps you on your path to a certified solution. In particular, the SAP Cloud SDK for continuous delivery supports you in achieving the Cloud qualities checked as part of the certification, and provides a corresponding report about qualities considered by the pipeline. Look for the corresponding artifact in your Jenkins job. Please note that this is only an indication for the qualities considered as part of the certification. It will help you demonstrate the Cloud readiness of your processes, but provides no guarantee and is no prerequisite for certification.
After these news, back to the new version released today. In detail, the following components are now available in new versions:
In this blog post, we will walk you through the highlights of the new 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.
You can update your dependencies of the SAP Cloud SDK for Java to version 3.3.1 and consume the new version from Maven Central.
We have updated our tutorials to version 3 of the SAP Cloud SDK for Java. You find the updated versions in the tutorial navigator on developers.sap.com. For your reference, the previously existing blog posts describe the state as of version 2 and will not be updated going further.
In the tutorial navigator, you also find a new mission that encompasses the most important steps using the SAP Cloud SDK.
Furthermore, we have published a brand-new tutorial on migrating to version 3. At the example of the address manager application known from our book and tutorials, the tutorial explains step-by-step how to move this application to version 3. Migrating any other application will follow similar patterns, so this tutorial will prove helpful for everyone, in addition to our migration guide.
The OData VDM Generator now constructs the service URL based on the service name from the namespace provided in the metadata file. The previously used filename is only considered as the service name in case the namespace does not not provide the information.
We have updated the dependency to the Java libraries of SAP Cloud Application Programming Model (
Several further improvements are listed in the full release notes.
We have also released the SDK for Java in a new maintenance version 2.20.2. Everyone who did not yet migrate to version 3 of the SDK for Java can consume that version from Maven Central.
For a complete view on what has changed, take a look at the full release notes.
The JavaScript libraries of the SAP Cloud SDK are now available in version 1.9.0.
The OData client now supports sending update request to OData APIs with
The SAP Cloud SDK for JavaScript now supports destinations with authentication type
You can instruct delete OData requests to ignore version identifiers and force deletion independent of the entity state in the target system by using the
Version 1.9.0 introduces support for the "Location ID" property of the Cloud Connector in on-premise destinations.
We have fixed several issues with overly strict expectations regarding CSRF token handling.
As usual, the full release notes contain a list of all improvements in this release.
To update the version of the SAP Cloud SDK Java libraries used in an existing project, proceed as follows:
With this, you are already done thanks to the "bill of material" (BOM) approach. Your dependency should look like this:
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
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.3.1.
Of course, you can also generate a new project that uses version 3.3.1 from the start by running the Maven archetypes for Neo or Cloud Foundry with
To update the version of the SAP Cloud SDK JavaScript libraries used in an existing project, use the command
We have announced that the out-of-the-box continuous delivery pipeline of the SAP Cloud SDK for continuous d.... This allows you to start continuously delivering your CAP projects as easy as never before, without writing a single line of pipeline code. Visit us at SAP TechEd to try this hands-on.
In further news, we have relaunched our community page. The SAP Cloud SDK community page serves as your entry point to learn more about the SDK and to join the community. At the same time, the SAP Cloud SDK is also Topic of the Month of SAP Community.
Also noteworthy is this blog post about certification options for solutions on SAP Cloud Platform. The SAP Cloud SDK helps you on your path to a certified solution. In particular, the SAP Cloud SDK for continuous delivery supports you in achieving the Cloud qualities checked as part of the certification, and provides a corresponding report about qualities considered by the pipeline. Look for the corresponding artifact in your Jenkins job. Please note that this is only an indication for the qualities considered as part of the certification. It will help you demonstrate the Cloud readiness of your processes, but provides no guarantee and is no prerequisite for certification.
After these news, back to the new version released today. In detail, the following components are now available in new versions:
- Java libraries in version 3.3.1
- Java libraries in version 2.20.2
- JavaScript libraries in version 1.9.0
In this blog post, we will walk you through the highlights of the new 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.
Less than two weeks to go until SAP TechEd 2019. Learn more about the sessions featuring the SAP Cloud SDK in our dedicated blog post.
Java Libraries: Release Highlights 3.3.1
You can update your dependencies of the SAP Cloud SDK for Java to version 3.3.1 and consume the new version from Maven Central.
New and updated tutorials
We have updated our tutorials to version 3 of the SAP Cloud SDK for Java. You find the updated versions in the tutorial navigator on developers.sap.com. For your reference, the previously existing blog posts describe the state as of version 2 and will not be updated going further.
In the tutorial navigator, you also find a new mission that encompasses the most important steps using the SAP Cloud SDK.
Furthermore, we have published a brand-new tutorial on migrating to version 3. At the example of the address manager application known from our book and tutorials, the tutorial explains step-by-step how to move this application to version 3. Migrating any other application will follow similar patterns, so this tutorial will prove helpful for everyone, in addition to our migration guide.
Further improvements
The OData VDM Generator now constructs the service URL based on the service name from the namespace provided in the metadata file. The previously used filename is only considered as the service name in case the namespace does not not provide the information.
We have updated the dependency to the Java libraries of SAP Cloud Application Programming Model (
com.sap.cloud.servicesdk.*) from version 1.32.5 to 1.33.0.Several further improvements are listed in the full release notes.
Java Libraries: Release Highlights 2.20.2
We have also released the SDK for Java in a new maintenance version 2.20.2. Everyone who did not yet migrate to version 3 of the SDK for Java can consume that version from Maven Central.
For a complete view on what has changed, take a look at the full release notes.
JavaScript Libraries: Release Highlights 1.9.0
The JavaScript libraries of the SAP Cloud SDK are now available in version 1.9.0.
Replace entity on update
The OData client now supports sending update request to OData APIs with
PUT semantics (replace). While PATCH remains the default, you can now control the HTTP method and strategy to use for update requests. To use HTTP method PUT and send the full entity that is meant to replace the current state of the entity, call the replaceWholeEntityWithPut method on any update request builder.Further improvements
The SAP Cloud SDK for JavaScript now supports destinations with authentication type
ClientCertificateAuthentication.You can instruct delete OData requests to ignore version identifiers and force deletion independent of the entity state in the target system by using the
ignoreVersionIdentifier method.Version 1.9.0 introduces support for the "Location ID" property of the Cloud Connector in on-premise destinations.
We have fixed several issues with overly strict expectations regarding CSRF token handling.
As usual, the full release notes contain a list of all improvements in this release.
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-bomdependency. - Update the version of that dependency to
3.3.1.
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.3.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-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.3.1.
Of course, you can also generate a new project that uses version 3.3.1 from the start by running the Maven archetypes for Neo or Cloud Foundry with
-DarchetypeVersion=3.3.1 (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.
- SAP Managed Tags:
