Dynamic Media allows to customize and deliver interactive multimedia experiences across all devices. It is often used with AEM, to accelerate content creation and delivery. Please visit link, for information on key benefits and capabilities
In this article, I would share few optimizations that should be performed when integrating AEM and Dynamic Media.
Note: Some of the steps might be common for all AEM asset projects.
Observation: With a Dynamic Media Integration, the OOTB DAM Update Asset workflow behaves as a non-transient workflow. This is due to the external steps required for processing. In such cases the runtime history is needed for status confirmation. The UI would still continue to show it as a transient workflow, but all history will be retained.
Implement Performance tuning guidelines
Assure that all performance tuning guidelines published by Adobe have been implemented. Example: JVM params, temp folder, datastore configs etc.
The details can be found on link
Upload only the required assets to Dynamic Media
Uploading an asset to Dynamic Media consumes:
- Space on Dynamic Media
- AEM resources while the upload is performed.
By assuring that only required assets are uploaded, we can reduce the processing of DAM Update Workflow.
This can be achieved by assuring only required assets are enabled for upload under the Dynamic Media Cloud Config. Visit child nodes of “/conf/global/settings/cloudconfigs/dmscene7/jcr:content/mimeTypes” in CRXDE to enable/disable asset uploads to Dynamic Media.
Filter what goes to Dynamic Media or AEM Publish
In a non-Dynamic Media Environments, all assets are replicated to AEM Publish instance. When using Dynamic Media, few assets types are served from Dynamic Media and others from Publish Instance. This segregation allows us to exclude publishing DM assets (ones served from Dynamic Media) to publish server. It would save storage costs and resources spent in replicating an assets.
To achieve this, refer to link
Disable subasset generation
Evaluate if you really need subassets for Word documents, PDF or Adobe Photoshop files. OOTB sub assets are created only for word documents. Consider disabling the following launchers, if sub-assets are not required.
- DAM Process Sub-Asset
- DAM Parse Word Documents
Minimize the Number/Scope of Workflow Launchers
This is one of the best practices recommended by Adobe. It helps optimize the evaluation process of the listener for workflow launchers. It will comprise of 2 activities:
- Turn off the OOTB workflow launchers that are not needed.
- Minimise the scope (Globbing path) of a workflow launcher.
For details, refer to link
Use “Scene7 Direct Binary Upload” for assets > 2GB
AEM 6.5 SP3 provides a new Workflow Step “Scene7 Direct Binary Upload” for assets > 2GB. It will be added automatically to the OOTB DAM Update Asset Workflow on installing SP3 and above in AEM 6.5.
Consider adding this step manually, if you are using a custom workflow in place of OOTB DAM Update Asset Workflow.