Explaining Licensing, Versioning, Third-Party Compatibility, and Maintenance

Objective

After completing this lesson, you will be able to explain licensing, versioning, third-party compatibility, and maintenance information of SAP Commerce Cloud.

Licensing

SAP Commerce Cloud uses standard SAP license management. A valid license is required to start the application and unlock its features. When a license is installed, the system stores the details in a file located at <SAP_COMMERCE_HOME>/config/license/installedSaplicenses.properties.

SAP Commerce Cloud provides three types of licenses:

  1. Temporary License: It is available for test and demonstration purposes. An initial 30-day temporary license is automatically applied during installation. Once the initial 30 days expire, you can use the command-line license tool to generate an additional 90-day license. After this, a regular license must be obtained.
  2. Development License: It is more permanent and is obtained by generating and downloading a license file from the SAP ONE Support Portal’s internal license key generation tool, then installing it on your development machine. This provides up to two years for development and testing in a local environment.
  3. Regular License: It is generated during the automated provisioning process when deploying SAP Commerce Cloud using the Cloud Portal. No additional steps are required to install the license.

To view your installed license details, navigate to the SAP Commerce Cloud Administration Console, select Platform, and then License.

Versioning

SAP Commerce Cloud follows a continuous innovation model centered on version 2211, which will not change. This version receives monthly update releases that introduce new features and maintenance fixes. A significant recent change is the transition from JDK 17 to JDK 21.

JDK 17-Based Naming Convention
Monthly updates follow the 2211.x pattern, where x is an incremental number (not month-specific). After the end of August 2026, all JDK 17-based releases reached their end of validity.
JDK 21-Based Naming Convention
Monthly updates follow the 2211-jdk21.x pattern, where x is an incremental number (not month-specific). This is the sole active version pattern for SAP Commerce Cloud.
Naming ConventionSAP Commerce ReleaseValid as Of
JDK 21-Based2211-jdk21.18September 9, 2026
2211-jdk21.17August 11, 2026
2211-jdk21.15July 14, 2026
JDK 17-Based2211.55August 11, 2026
2211.54July 14, 2026
2211.53June 9, 2026

Each monthly update is cumulative and backward compatible. Its content includes:

  • Patches, bug fixes, and security updates
  • New features and innovations (not included in every monthly update): To ensure these updates can be adopted with the same ease and low risk as a patch, some new features and innovations are delivered in a disabled state. To enable a new feature or innovation, follow its instructions in the Upgrade Guide.

Each monthly update is supported for exactly six months from its release date. To safeguard security and stability, the Cloud Portal blocks builds and deployments for any version older than six months. This means you must upgrade to a newer monthly update at least once every six months. For example, if you are on the January update, you must upgrade to a version released between February and June before July.

Third-Party Compatibility

SAP Commerce Cloud incorporates a variety of third-party software and tools into its core architecture to provide essential functionality like search indexing, application hosting, and security. Ensuring compatibility with these embedded components is critical, as the platform’s stability, performance, and security depend on the specific library and engine versions it uses.

The following table provides an example of supported third-party software versions for SAP Commerce Cloud 2211.17 (local installation):

Software and ToolsVersions
JavaSAP Machine 21.0
Apache Tomcat10.1.55 bundled
Operating SystemsMicrosoft Windows: Any version that supports SapMachine 21
Linux: Any version that supports SapMachine 21
macOS: For development purposes only
Spring LibrariesSpring 6.2.19
Spring Security 6.5.11
Search EnginesSolr 9.10

Because SAP Commerce Cloud follows a Continuous Innovation model, third-party library updates (such as Spring, Search Engine, or Apache Tomcat) are released monthly. Developers must regularly check the Third-Party Compatibility page on the SAP Help Portal.

Maintenance

In SAP Commerce Cloud, extension deprecation serves as an early warning system to help businesses plan their long-term architecture. When an extension is marked as deprecated, SAP continues to provide support and security fixes, but no new features are developed for it. This grace window allows customers to continue using the extension while they migrate to a recommended alternative, such as moving from legacy Accelerators to SAP Commerce Cloud Composable Storefront.

Maintenance support for a deprecated extension continues until it reaches its official "deleted" status or until its SAP Commerce Cloud version reaches End of Main Maintenance (EOMM). While maintenance is provided, using deprecated extensions in new projects is strongly discouraged, they are slated for removal in future releases.

Following is a sample list of deprecated extensions. For a complete list, please check SAP Help Portal - Deprecation Status.

ExtensionModuleAnnounced Deprecation WithPlanned DeletionReason for DeprecationMitigation Plan
addonsupportCore-accelerator2205Q2 2024The deprecation of the Accelerator UI and older OCC template extensions is aligned with the SAP Commerce Cloud vision to provide a modern and headless commerce experience.For information on how to start the mitigation process, see Changes to Planned Removal Date for Deprecated Accelerator UI and Extensions
eventtrackingmodelevent-tracking2011Q4 2028The Event Tracking module is an old implementation using outdated libraries. Sending a large number of customer interactions through the SAP Commerce Cloud back end does not scale.In SAP Commerce Cloud, Composable Storefront, the event service does what the Event Tracking module extensions did.
y2ysyncplatform1905To be determinedDependency on deprecated parts of the product. 

Extension deprecation is component-specific, meaning it applies at the individual extension level. In contrast, End of Main Maintenance (EOMM) is version-specific and applies to the entire software release. Once a release reaches EOMM (such as SAP Commerce Cloud 2105), it is no longer covered by standard maintenance, regardless of whether its extensions are active or deprecated. To remain compliant with your support agreement, you must run a supported SAP Commerce Cloud version:

 Bug Fixes (maintenance release)Security Vulnerability (maintenance release)Technical Support
Supported version with a valid subscriptionYesYesYes
EOMM versionsNoNoPartly supported

Key Takeaways

  • SAP Commerce Cloud provides three license types: Temporary (for testing), Development (up to two years for local environments), and Regular (auto-provisioned in cloud deployments).
  • The platform follows a continuous innovation model on version 2211, with monthly cumulative updates using JDK 21-based naming (2211-jdk21.x), each supported for exactly six months.
  • Third-party library versions are updated monthly and must be regularly verified on the SAP Help Portal, while deprecated extensions remain supported until deleted or until its SAP Commerce Cloud version reaches End of Main Maintenance (EOMM).