Getting Started with SAP Commerce Cloud
12 min read
The SAP Commerce Cloud in the Public Cloud solution features the same great industry leading commerce solution as our SAP Commerce core solution, along with some new features. However, with new features, come different ways of doing things compared to an on-premises instance. This section is the starting point for anyone that is working on an SAP Commerce Cloud solution project for the first time.
Table of Contents
Why SAP Commerce Cloud?
Before we begin, it is important to differentiate between the SAP Commerce Cloud in the Public Cloud, released on the 4th of June 2018, and the previous version of SAP Commerce Cloud, which we will refer to in this document as "SAP Commerce Cloud on SAP Infrastructure".
If you are currently using an on-premise version of SAP Commerce or you are on SAP Commerce Cloud on SAP Infrastructure, you may be wondering what has changed in the newest version of SAP Commerce Cloud. The following videos provide an introduction to SAP Commerce Cloud (video link) as well as a walkthrough of several self-service features in SAP Commerce Cloud (video link).
With SAP Commerce Cloud on SAP Infrastructure, it is your responsibility to build packages for deployment (following the latest Deployment Package Guidelines). Deployments and maintenance of the environments are then managed by SAP Cloud Services. Additionally, a VPN tunnel is required to reach backoffice nodes, as outlined in the diagram below.
With the SAP Commerce Cloud in the Public Cloud, the process to provision environments, build the code, and deploy to public cloud infrastructure is self-managed through the SAP Commerce Cloud Portal.
If you are interested in learning how to migrate from SAP Commerce Cloud on an SAP infrastructure to a public infrastructure, please see the article "Migrate to SAP Commerce Cloud".
The Build Process
The SAP Commerce Cloud build process uses the standard commerce build process. However, if the build process is customized (for example, using build callbacks), there is a possibility that these customizations will be incompatible with the SAP Commerce Cloud build process. A larger degree of customization will increase the risk of build incompatibilities. Therefore any customizations, like the build callback logic, should be kept to a minimum and should be thoroughly tested on SAP Commerce Cloud.
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 (see the Code Repository section below). You may wish to set up your manifest.json file for Configuration Reuse in order to make Developing Locally simpler.
Additionally, the SAP Commerce Cloud build process cannot be customized beyond the configuration options available in the Manifest.json file, as well as the configuration and customization options that the standard commerce build process supports. Failures in the build process are reported in the build log which is available as part of the build details in Cloud Portal.
The following diagram outlines the high level build process: