Notable changes to Experience Manager Assets as a Cloud Service
Adobe Experience Manager as a Cloud Service brings many new features and possibilities to manage your AEM projects. However, there are many differences between Experience Manager Assets on-premise or in Adobe Managed Service as compared to Experience Manager as a Cloud Service. This document highlights the important differences for Assets capabilities.
The main differences as compared to Experience Manager 6.5 are in the following areas:
This document highlights the notable changes to AEM Assets. For changes general to AEM as a Cloud Service, and other modules, see:
- The Architecture of Adobe Experience Manager as a Cloud Service
Asset ingestion and upload
Asset upload has been optimized for efficiency by enabling better scaling of asset ingestion and faster uploads. Product capabilities (web user interfaces, desktop clients) have been updated. However, this may impact some existing customization.
- Experience Manager uses direct binary access principle for upload and download and asset microservices for asset processing. See overview of asset ingestion .
- The default workflow DAM Asset Update in previous versions of AEM is no longer available. Instead, asset microservices provide a scalable, readily available service that covers most of the default asset processing (renditions, metadata extraction, text extraction for indexing).
- To have customized workflow steps in the processing, post-processing workflows can be used.
- Assets that come in via Package Manager require manual reprocessing using the Reprocess Asset action in the Assets interface.
Standard renditions generated with asset microservices are stored in a backwards-compatible way in the asset repository nodes (same naming conventions).
Develop and test asset microservices
Asset microservices provide a scalable and resilient processing of assets using cloud services. Adobe manages the cloud services for optimal handling of different asset types and processing options. Asset microservices help to avoid the need for third-party rendering tools and methods (like ImageMagick) and simplify configurations, while providing out-of-the-box functionality for common file types. You can now process a broad range of file types covering more formats out-of-the-box than what is possible with previous versions of Experience Manager. For example, thumbnail extraction of PSD and PSB formats is now possible that previously required third-party solutions like ImageMagick. You cannot use the complex configurations of ImageMagick for the Processing Profiles configuration. Use Dynamic Media for FFmpeg transcoding of videos and use processing profiles for basic transcoding of MP4 videos .
Asset microservices is a cloud-native service that is automatically provisioned and wired to Experience Manager in customer programs and environments managed in Cloud Manager. To extend or customize Experience Manager, the developers can use the existing content or assets with renditions generated in a cloud environment, to test and validate their code using, displaying, downloading assets.
To do an end-to-end validation of the code and process including asset ingestion and processing, deploy the code changes to a cloud-dev environment using the pipeline and test with full execution of asset microservices processing.
Removal of Classic UI
The Classic UI is no longer available in Experience Manager as a Cloud Service. The standard interface is the Touch-enabled UI.