SAP Hybris Commerce Cloud – What, Why and How?

After Hybris version 6.7, SAP rebranded it’s Hybris e-commerce suite as SAP Hybris Commerce Cloud and released the package with a new versioning strategy naming it as Hybris 1808 version (using year and month to define a version)

After that there has been two more major releases as Hybris 1811 and Hybris 1905. In this article, we will not be getting into the offering details. Rather, we will focus on the cloud offering and support under it’s version 1 and version 2 respectively named as SAP Commerce Cloud on SAP Infrastructure and SAP Commerce Cloud

SAP partnered with Microsoft Azure to support Cloud Services

SAP partnered with Microsoft to provide SAP cloud solutions on Microsoft Azure.

Saying that, SAP leverages the Microsoft Azure services to offer SAP Hybris an end-to-end cloud managed solution where customers doesn’t need to manage the infrastructure on-premise.

One can choose various options of available databases, services, storage options etc offered by Microsoft Azure. System scalability, extensibility, security, elasticity and performance is much more easier to support and track as we go along in an increasing e-commerce customer base.

Once can create various managed environments like Development, Test, Stage and Production by simply following easy-to-use configuration web console UI.

With old SAP Commerce Cloud (CCv1)

In below image (courtesy SAP), it shows interaction and system management by all three parties (i.e., External, SAP, Customer/Partner) within and outsize cloud.r

SAP Hybris Commerce Cloud
SAP Commerce Cloud Version 1 (CCV1) – Image courtesy SAP
  • It is your (Customer or development parter) responsibility to build packages for deployment
  • Deployments and maintenance of the environments are managed by SAP Cloud Services
  • A VPN tunnel was required to access Hybris Backoffice nodes
  • Customers had to create all the code package (platform, custom etc) and share with the SAP Cloud Services team along with Deployment request form in PDF (replaced by Manifest.json with CCv2, covered in next section)
  • SAP HCS team runs the deployment as per provided code package and deployment request form

In simple terms, Development team used to write and commit the code in self-managed repository (on-premise or cloud based). Build Manager, used to use this code to prepare a build package in compliance with Deployment Package Guidelines and Deployment request form (a PDF) was with SAP customer support team to perform deployment. Clumsy… Right???

With new SAP Commerce Cloud (CCv2)

Hybris Commerce Cloud Version 2 - Image Courtesy SAP
Hybris Commerce Cloud Version 2 – Image Courtesy SAP
  • SAP Automated Deployment Request – Provide all the artifacts and allow cloud based system to perform build for you
  • Customer admin needs to provide build related details in form of Manifest.json (covered next) which self-drives the deployment
  • The process to provision environments, build the code, and deploy to public cloud infrastructure is self-managed through the SAP Commerce Cloud Portal
  • That means, an integrated simple access to code repository, CI/CD implementation for Customer System Admin over Commerce cloud portal
  • Customer system admin can manage and build resource using Commerce Cloud Portal
  • Also, Customer Staff does not need a VPN tunnel to access backoffice portal

What it changes for a Hybris developer?

More or less NOTHING.

From a developer’s point of view, it really changes nothing and you would continue developing your code as you used to do it for on-premise version.

But, you must be aware of the Commerce Cloud Extension Pack and offerings.

You will still create your localextensions.xml, items.xml, extension-info.xml etc. etc. etc. exactly in the same way you used to do it before.

Is there no changes for build package and deployment too?

Not really!!! While working on Hybris Commerce cloud, it doesn’t takes care of what you define in your localextensions.xml.

Rather, it uses Manifest.json file which must be created in compliance with Deployment Manifest Guidelines

What is Manifest.json?

Manifest JSON allows Customer Admin to give details around the build package and deployment? such as

  • Project Information : Client / Partner / Project Details
  • Package Information : Name of package file (zip file), Commerce suite version, server and path to find the package etc.
  • Deployment Information : Target environment information, Database Action (init/update/none) etc
    "manifestSpecificationVersion": "1.0",
    "projectInformation": {
        "customerName": "Customer ABC Inc.",
        "customerId": "ABC",
        "projectName": "XYZ Stores North America",
        "projectId": "XYZ",
        "partnerName": ""
    "packageInformation": {
        "packageName": "",
        "commerceSuiteVersion": "6.7",
        "packagingSpecificationVersion": "2.3",
        "packageSourceServer": "dc-abc-xyz-d1-app-001",
        "packagePath": "/NFS_DATA/deployment"
    "deploymentInformation": {
        "targetEnvironment": "stag",
        "deploymentComponents": {
            "hybris": {
                "oldPackagesToKeep": 2,
                "rollingDeployment": true,
                "maintenancePageEnable": false,
                "buildType": "ant clean all",
                "buildAddOns": [
                "databaseOperation": "none"
            "datahub": {
                "databaseOperation": "ignore"
            "cis": {}
    "addtionalInformation": {
        "knownErrors": "",
        "releaseNotes": ""
    "manualIntervention": {
        "additionalInstructions": "",
        "maintenancePageSpecialInstructions": "",
        "hybrisDatabaseOperationSpecialInstructions": "",
        "dataHubDatabaseOperationSpecialInstructions": ""

Important Note

SAP Commerce Cloud relies on the Manifest.json file to configure the build. It does not support alternative recipes or custom recipes like those found for on-premise installations of SAP Commerce Cloud. Users of recipes will need to adapt their recipe to the Manifest file

I will be covering the concepts, offerings and limitations of Manifest.json file and migration technique from on-premise version to cloud in a next article.

Hope above article gives you a basic understanding of the Hybris Commerce Cloud offerings and support. Also, the difference between the earlier release and CCv2.

Thanks once again for reading the article.

Related Topics

3550cookie-checkSAP Hybris Commerce Cloud – What, Why and How?

4 thoughts on “SAP Hybris Commerce Cloud – What, Why and How?

  • Next time I read a blog, Hopefully it does not disappoint me just as much as this particular one. I mean, Yes, it was my choice to read through, nonetheless I actually believed you would have something useful to say. All I hear is a bunch of complaining about something that you could fix if you weren’t too busy searching for attention.

    • I apologize for your loss of time on this post if it really was that bad. I appreciate your writing down the feedback but at the same time I would request you to point out the things you found not inline with your expectations so that I could improve this post.

      Thanks for your time to writing this note. Good luck and success to you.

Leave a Reply

Your email address will not be published.