This page identifies the versions of Adobe Experience Manager with which a particular version of ACS AEM Commons is compatible. In general, we strive to be compatible with the current version and the last prior version. For the purpose of this page, compatible means that the package is install-able. Individual features may require a higher version. Please refer to the individual feature documentation pages for more details.
|CQ 5.5||CQ 5.6||AEM 5.6.1||AEM 6.0||AEM 6.1||AEM 6.2||AEM 6.3||AEM 6.4||AEM 6.5||AEM as a Cloud Service|
AEM as a Cloud Service Feature Incompatibility
ACS AEM Commons 5.0.0 and greater can be deployed to AEM as a Cloud Service. While the ACS AEM Commons package itself is deployable to AEM as a Cloud service, this does NOT mean that all features work or should be used on AEM as a Cloud Service. The table below calls out the known problematic features categorizing them by “Incompatibility Level”
- INCOMPATIBLE indicates the features that should not, and may not be possible to use in AEM as a Cloud Service. This classification is broken into two sub-classifications:
- MISSING DEPENDENCY: Features that depend on API or integrations that do not exist in AEM as a Cloud Service, and thus cannot work on AEM as a Cloud Service.
- ANTI-PATTERN: Features that are implemented using an anti-pattern in AEM as a Cloud Service.
- WARN: While not technically incompatible, this ACS AEM Commons feature is often used to perform work that is an ANTI-PATTERN (for example, using Bulk Workflow Manager to generate renditions for assets using AEM Workflow Processes, instead of Assets microservices).
- REPLACED: AEM as a Cloud Service now provides a better version of this feature that more closely aligns w/ the overall AEM as a Cloud Service infrastructure.
All features classified as INCOMPATIBLE (MISSING DEPENDENCY), INCOMPATIBLE (ANTI-PATTERN), and REPLACED have (or will have) an internal kill-switch in the in ACS AEM Commons code-base that prevent them from functioning on AEM as a Cloud Service (these features will continue to function on the supported AEM 6.x installs).
As new features are found to be incompatible with AEM as a Cloud Service, they will be added to this list, and disabled via the kill-switch in ACS AEM Commons code base.
|Audio Component||INCOMPATIBLE (ANTI-PATTERN)||Streaming binary data through AEM memory is an anti-pattern.|
|Bulk Workflow Manager||WARN||Bulk workflow manager can be used to execute Workflows as long as they those workflows do not violate AEM as a Cloud Service’s best practices. Commonly, Bulk Workflow Manager is used to process asset binaries; this is not longer allowed in AEM as a Cloud Service|
|Ensure Oak Index||INCOMPATIBLE (ANTI-PATTERN)||Oak index definition are considered immutable and not manage-able at runtime.|
|Healthchecks - SMTP Healthcheck||INCOMPATIBLE (MISSING DEPENDENCY)||SMTP is not supported. Healthcheck results are not available, rendering running them moot.|
|Healthchecks - Healthecheck Status e-mailer||INCOMPATIBLE (MISSING DEPENDENCY)||SMTP is not supported.|
|JSON Event Logger||INCOMPATIBLE (MISSING DEPENDENCY)||Only Adobe provided loggers and logging is supported.|
|MCP - File Fetcher||INCOMPATIBLE (ANTI-PATTERN)||Streaming binary data through AEM memory is an anti-pattern.|
|MCP - Asset Ingestor||INCOMPATIBLE (ANTI-PATTERN)||Streaming binary data through AEM memory is an anti-pattern.|
|MCP - S3 Asset Ingestor||INCOMPATIBLE (ANTI-PATTERN)||Streaming binary data through AEM memory is an anti-pattern.|
|MCP - URL Asset Ingestor||INCOMPATIBLE (ANTI-PATTERN)||Streaming binary data through AEM memory is an anti-pattern.|
|MCP - Refresh Folder Thumbnails||INCOMPATIBLE (ANTI-PATTERN)||Streaming binary data through AEM memory is an anti-pattern.|
|OnDeploy Scripts||INCOMPATIBLE (ANTI-PATTERN)||OnDeploy Scripts runs its scripts very early in the deploy lifecycle (approximately when the OSGi bundle starts). In AEM as a Cloud Service, this is still in the Deploy phase, and long running scripts running at this time can result failed deployments, or mis-reported failed deployments. Instead use repoinit or Sling Pipes (triggering the Sling Pipe after the Deployment is complete and the new code base is fully active)|
|Syslog Appender||REPLACED/INCOMPATIBLE||AEM CS can stream logs to customer’s Splunk. AEM CS does not support emitting logs over syslog as UDP or TCP.|
|Version Clientlibs||REPLACED||This has been superseded with superior OOTB AEM as a Cloud Service functionality.|
|Workflow - Assets Rendition Matter||INCOMPATIBLE (ANTI-PATTERN)||Streaming binary data through AEM memory is an anti-pattern.|
|Workflow - Brand Portal Sync||INCOMPATIBLE (MISSING DEPENDENCY)||Brand Portal integration no longer user replication agents.|
|Workflow - Rendition Watermarker||REPLACED / INCOMPATIBLE (ANTI-PATTERN)||Streaming binary data through AEM memory is an anti-pattern. AEM as a Cloud Service has asset watermarking OOTB|
|Redirect Map Manager||INCOMPATIBLE (MISSING DEPENDENCY)||AEM as a Cloud Service manages its Apache Web Server in a way that does not allow this to work.|
|Remote Assets||INCOMPATIBLE (ANTI-PATTERN)||Streaming binary data through AEM memory is an anti-pattern.|
|Sitemap Generator||REPLACED||Feature is superseded by AEM Core WCM Components Sitemaps. ACS AEM Commons Sitemap Generator will still work, however it is preferred to use the AEM Core WCM Component’s provided Sitemaps.|