Skip to Content
Product Information

SAP Cloud Connector – support approach

The SAP Cloud Connector is the endpoint of SAP Cloud Platform Connectivity in the customer On-Premise landscape. The cloud side is upgraded more often than the SAP Cloud Connector in general and specific customer installations in particular. Therefore you might wonder how long you can run a specific version of the Cloud Connector without having to expect compatibility issues with the cloud side or what distinguishes a specific version from its  predecessor.


Semantics of Cloud Connector versions

The SAP Cloud Connector typically has a version that looks like 2.x.y – very seldom 2.x.y.z, for example 2.6.0

  • Version change from 2.x.y to 2.(x+1).0: (e.g. 2.5.2 to 2.6.0) – a feature release
    Such a version will contain new features compared to the previous version that will allow you to extend the scenarios in which you can use the Cloud Connector. Furthermore, configuration options might have been simplified.
  • Version change from 2.x.y to 2.x.(y+1): (e.g. 2.6.0 to 2.6.1) – a patch release
    Such a version will contain only patches and no new feature. Known bugs have been fixed.
  • Version 2.x.y.z: (e.g. – a release containing late patches detected in last test cycle
    Such a version will not happen too often and might only affect specific platforms. The type of the release (feature or patch) is determined by the version change of the minor and micro version compared to the predecessor version.
  • Version 3.x.y: A change of the major version will only happen, if an incompatible change of the Cloud Connector is required. The clear goal is to avoid such changes as long as possible.


Support, patches and compatibility

Issues will always be fixed on basis of the latest released Cloud Connector version. In case you require a specific fix, you need to migrate to the next version that is released.

Each Cloud Connector version will be supported for 12 months or 3 months after the next release has been published, whatever occurs later, which means it is guaranteed that the cloud side stays compatible with those versions. After that time frame, compatibility is no longer guaranteed and interoperability could be dropped. Furthermore, after an additional 3 month the next feature release that will be published after that period will no longer support an upgrade from the deprecated version as a starting release.

This allows us to streamline the source code by removing code sections that only exist for dealing with older versions.



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