Checklist for Succeeding with SAP Commerce Cloud
23 min read
Overview

Here you can find all common pitfalls, tips and tricks and other references that ensure a successful migration to SAP Commerce Cloud.
Description | Solution Options | Documentation |
---|---|---|
Preparation - Establish Performance Baseline To ensure a successful migration, establish and provide performance / load testing baseline. |
|
|
Preparation - Clean Up Source Database Clean up all temporary and outdated transactional data. Review your audit log settings and decide what data you actually need to log based on your projects requirements. |
Please clean up at least the following types:
If you require audit logging (due to regulatory compliance), make sure you only audit log the the relevant data (relevant types). Disable audit logging for all types that are not part of the compliance requirements. If you don't have to follow any regulatory compliance, it is highly recommended to disable audit logging completely. You can find an up-to-date lists of types and analysis queries in the sanecleanup GitHub project. |
|
Preparation - Transparent Attribute Encryption (TAE) If custom keys and password are used by your project, extract and migrate all existing keys and passwords to your SAP Commerce Cloud environments. |
|
|
Compatibility - PCI DSS Compliance SAP Commerce Cloud is compliant with the PCI DSS 3.2.1 standard. |
|
|
Compatibility - Data Center Locations SAP Commerce Cloud is constantly re-evaluating the demand to consider additional data centers to host your solution. If you have specific data protection laws and regulations that affect the physical position of the data center, you need to make sure SAP Commerce Cloud offers a data center in a required region. |
|
|
Compatibility - Minimal Supported SAP Commerce Version Your SAP Commerce version must be in Mainstream Maintenance. Minimal version at the time of writing: 2005 |
|
|
Project Setup - Code Repository Setup The build process in the Commerce Cloud expects:
|
|
|
Project Setup -
|
|
|
Project Setup - Additional Build Tools The only additional build tool supported for the Commerce build is the Node.js distribution
provided by the Other tools / executables are not supported. |
|
|
Project Setup - Additional Build Services SAP Commerce Cloud does not provide additional build services like:
|
|
|
Project Setup - Automated CI/CD Pipeline SAP Commerce Cloud does not have the capability to trigger builds on push / pull request / .. |
|
|
Compatibility - Supported Java Runtimes The only supported JVM is sapmachine (see third-party compatibility link for specific versions). |
|
|
Compatibility - Database - Server SAP Commerce Cloud uses Azure SQL as underlying DBMS. |
|
|
Compatibility - Database - Collation By default, SAP Commerce Cloud provides a case sensitive collation for the database. |
|
|
Compatibility - Database - Indexes Any custom indexes must be explicitly transferred from the source database and allow listed. |
|
|
Compatibility - Database - Additional Schemas Additional schemas / database are not supported. SAP Commerce Cloud provides a single schema that must be exclusively used by SAP Commerce. |
|
|
Infrastructure - Customizations of Apache/nginx/... Only a restricted set of customization or configuration of the web tier is supported. Please refer to the documentation for all supported options. |
|
|
Infrastructure - Load Balancing Load balancing is handled automatically by SAP Commerce Cloud. There is no need for manual intervention or custom configuration anymore. |
N/A | |
Infrastructure - Contend Delivery Network (CDN) SAP Commerce Cloud does not come with a bundled CDN. |
|
|
Infrastructure - Web Application Firewall (WAF) SAP Commerce Cloud comes with WAF Lite. |
|
|
Infrastructure - Domain Certificate Management In SAP Commerce Cloud, Domain Certificates are managed by the customer/partner using self-service capabilities of the Cloud Portal. |
|
|
Infrastructure - Virtual Private Network (VPN) Connectivity SAP Commerce Cloud provides a self-service site-to-site VPN with NAT capabilities. |
|
|
Infrastructure - Direct connectivity to specific servers/services Direct connectivity to specific servers or components of a SAP Commerce Cloud subscription (like the database) is not supported. |
N/A | |
Infrastructure - Maximum outbound connection timeout Azure restricts the maximum idle network timeout for all outbound connections to 4 mins. Other than that, SAP Commerce Cloud does not restrict outbound network connectivity in any way. |
|
|
Infrastructure - Additional Infrastructure Components (aka. "Satellite Servers") SAP Commerce Cloud does not support adding any additional infrastructure components to your subscription. Non-exhaustive list of unsupported services:
In short, if it is not part of the official SAP Commerce Cloud service description or is not available as an addon to SAP Commerce Cloud, it is not supported. |
|
|
Infrastructure - SMTP Server SAP Commerce Cloud does not provide an SMTP server for outgoing emails. |
|
|
Infrastructure - File System The local file system of the Commerce instances in SAP Commerce Cloud is limited in size. Overusing the file system will lead to automated restarts to purge the local filesystem. |
|
|
Infrastructure - No shared file system There is no shared file system between the Commerce instances in SAP Commerce Cloud. This also includes Medias. Medias are not stored in the file system in SAP Commerce Cloud. Media should be stored in a Digital Asset Management (DAM) solution or in the Commerce Cloud Storage. |
|
|
Infrastructure - Log Management All logs of all components of SAP Commerce Cloud are centrally collected and stored. Kibana is provided as a central UI to manage, search and configure alerts on logs. Logging to file(s) is not supported in SAP Commerce Cloud. All logging must go to stdout / stderr. Please refer to the documentation about the current retention for logs. (at the time of writing: 90 days or 100GB). |
If your project needs to “mark” or “tag” specific logs per component, integration, … or the project used to write multiple log files: Use Mapped Diagnostic Contexts (MDCs) provided by the SLF4J framework to mark log messages. All MDCs are available in Kibana, field |
|
Infrastructure - Log Export SAP Commerce Cloud ships the raw logs (json format, xz compressed) to an Azure Blob storage from which they can be downloaded for further processing. No other option is supported. |
|
|
Infrastructure - Application Performance Monitoring (APM) Every SAP Commerce Cloud subscription includes Dynatrace for APM. No other option is supported. |
|
|
Compatibility - Unsupported Commerce Modules Please refer to the official documentation for a list of modules that are not supported in SAP Commerce Cloud. |
|
|
Compatibility - Multiple Commerce Tenants Multiple tenants are not supported. |
|
|
Compatibility - Image Resizing / Media Conversion Media Conversion uses a different architecture in SAP Commerce Cloud. |
|
|
Compatibility - Legacy Clustering All nodes in a SAP Commerce Cloud system use dynamic node IDs, therefore all features that rely on static/fixed node IDs are not supported in SAP Commerce Cloud. These features include:
|
|
|
Compatibility - SAP RFC Group Connection Support Group Connections for SAP RFC Connections are not supported. The necessary modifications to Operating System files are not allowed on SAP Commerce Cloud due to security constraints. |
|
|
Compatibility - Solr version You must use a Solr version that is compatible with your SAP Commerce patch release. |
|
|
Compatibility - Supported Solr Customizations Only change configuration related to indexes, fields / field configurations (config sets). Avoid any configurations regarding the server setup, this is managed by SAP Commerce Cloud. SAP Commerce Cloud uses Solr in Cloud Mode. Primary-replica setups are not supported. |
|
|
Compatibility - Solr Server Configuration in SAP Commerce All Facet Search Configurations must use Solr server configuration "Default". |
|
|
Data Hub - Adapt Data Hub Build SAP Commerce Cloud defines a specific process how DH extensions are built. |
|
|
Compatibility - Compatibility with HTTP Session Fail-over Test if your storefront sessions are compatible with HTTP Session Fail-over. |
|
|
Compatibility - Compatibility with Zero Downtime Deployments Test if the project system update is working on SAP Commerce Cloud. |
|
|
Go Live Preparation - Cloud Readiness Check Coordinate with your Cloud Engagement Executive (CEE) or SAP Support to schedule a Cloud Readiness Check (usually ~6 weeks before go-live). |
|
|
Go Live Preparation - Production Data Migration Conduct a Production Data Migration Dry-Run to evaluate the cut-off duration and test for any possible functional/platform issue. |
|
|
Go Live Preparation - Adjust Solr Sharding and Replica Configuration Configure the shards and replica configuration according to your index size, document size, number of attributes, fail-over requirements ... |
|
|
Go Live Preparation - Configure your Endpoints Configure your endpoint(s) according to your requirements. |
Recommendation: Please consider using a Content Delivery Network for production systems |
|
Go Live Preparation - Configure Readiness Check and Node Warmer Configuring the node warmer makes sure that the impact of deployment, auto-scaling and other scenarios on the overall response time remains minimal. |
|
|
Go-Live Preparation - Load Testing Perform performance / load test on production environment with production data. |
Recommendation: Acquire a sandbox to properly load test future development |
|
Go-Live Preparation - Perform Final User Acceptance Test (UAT) Perform a final acceptance test to ensure you have completed the migration successfully and are ready for go-live.
|
|
Conclusion
With this collection of established best practices you should be well equipped for your journey to SAP Commerce Cloud. We will continue to update this page with new insights as soon as we learn them, make sure to check back regularly! In the meantime, feel free to check out the other articles in our series on Migrating to SAP Commerce Cloud.