Here you can find additional information for the errors and warnings reported by validateManifest
- 🔴 E-001 >extension< not available
- 🔴 E-002 Aspect >aspect< not supported
- 🔴 E-003 Duplicate aspect configuration
- 🔴 E-004 Duplicate extension configuration
- 🔴 E-005 Duplicate context path/webroot configuration
- 🔴 E-006 contextPath must start with /
- 🔴 E-007 Webapps not allowed for aspect admin
- 🔴 E-008 Persona >persona< not supported
- 🔴 E-009 Location >path< is invalid/absolute/...
- 🔴 E-010 >file< is not a valid Java properties file
- 🔴 E-011 >file< is not a valid extensions.xml file
- 🔴 E-012 extension.dir is not supported
- 🔴 E-013 Solr customization folder structure
- 🔴 E-016 Invalid media conversion configuration
- 🔴 E-017 Webroot configured in properties
- 🔴 E-018 Invalid Solr Version
- 🔴 E-019 Invalid Integration Extension Pack Version
⚠️ W-001 Property >property< is a managed property⚠️ W-002 Property file encoding⚠️ W-003 Cloud Hot Folder without configuration for processing nodes⚠️ W-004 Solr customization without pinned Solr version
All extensions (remember, addons are also extensions) referenced in the manifest.json
must be part of the extensions loaded by the platform during build or server startup.
The error indicates that the extension is not loaded by the platform.
- Double-check the name of the extension/addon
- Make sure that the extension is enabled in
manifest.json- Is it configured in extensions.xml file referenced via
useConfig.extensions.location? - Is it listed in the
extensionsarray?
- Is it configured in extensions.xml file referenced via
- Or add the extensions as a dependency to another extensions that is already configured
Only a predefined set of aspects is supported in CCv2.
Configuring the same aspect multiple times leads to undefined behaviour during build and deploy.
Configuring the same extension more than once for the same aspect leads to undefined behaviour during build and deploy.
Using the same contextPath/webroot more than once in the same aspect breaks the server startup.
If the contextPath doesn't start with /, the build will fail (since the server wouldn't start with this configuration).
CCv2 uses the admin aspect to perform system updates and starts it in "headless" mode.
Configuring webapps for it is not supported and may break the deployment process.
Only a predefined set of personas (= environment types) is supported in CCv2
Files and folders referenced in manifest.json must be:
- Not empty (you have to define the
locationattribute!) - Unix-style paths (i.e. use
/as separator) - relative to the folder that contains
manifest.json - in US-ASCII (using special characters may lead to undefined behaviour)
- plain values (no relative paths, no environment variable substitution etc.)
Bad:
❌ /some/path - absolute path
❌ path/../other/path - relative path
❌ $HYBRIS_BIN_DIR/value - variable substitution
❌ folder/file.pröperties - special character
❌ path\to\file.properties - wrong path separator\
Good:
✅ relative/path/to/something
Files referenced in the useConfig.properties array of manifest.json must be readable as Java
properties files.
The file referenced in useConfig.extensions.locations must be a valid extensions.xml file.
The cloud build only supports the name attribute of the <extension> tags in the
useConfig.extensions.locations file.
The Solr customization support for CCv2 expects a specific folder structure to be present.
If the folder structure is incorrect, the customization simply doesn't work.
To use the cloud media conversion feature, you have to configure the cloudmediaconversion extension and enable the image processing
service (enableImageProcessingService)
Do not configure <extension>.webroot in any properties. Only use asepect[].webapps[].contextPath
to configure and enable web extensions.
The Solr version in the manifest must be two numbers separated by a dot (<major>.<minor>).
The Integration Extension Pack must be compatible with SAP Commerce and its version must be fully qualified, i.e. include the patch number.
❌ 2102 - missing patch
✅ 2102.0
The build process preconfigures certain properties with optimal values for a high-performance cloud environments.
Changing their values may have unintended side effects (like breaking the server) and should only be done if recommended by SAP experts or SAP support.
Property files are assumed to be encoded in ISO 8859-1. Using a different encoding might lead to changed/corrupted values after build and deploy.
If you use the Cloud Hot Folders feature of the Commerce cloud, you also have to configure the
backgroundProcessing nodes to process the incoming files.
If you customize your Solr configuration, it is recommended that you pin the Solr version in your manifest.json.
A SAP Commerce patch release may change the default Solr version, leading to deployment errors if your customization is not compatible with the new Solr version.