Dynamic Media configuration override behavior with multiple Scene7 domains in Adobe Experience Manager
This article explains how Dynamic Media cloud configuration overrides occur in Adobe Experience Manager (AEM) when multiple Scene7 domains are configured, and provides steps to ensure the correct configuration is applied to your assets.
Description description
Environment
- Adobe Experience Manager (AEM) 6.5 (all versions)
- Dynamic Media - Scene7 mode
Symptoms
- When multiple Dynamic Media cloud configurations are present in a single AEM environment (For example: two different Scene7 domains), the configuration assigned to the root DAM folder is unexpectedly overridden by the most recently saved configuration.
- Assets uploaded to any location in the DAM use the configuration that was last saved, rather than the one assigned to a specific folder.
- Assigning a cloud configuration to a subfolder doesn’t always result in the expected configuration being used; the system may continue to use the global configuration.
- No explicit error messages are logged, but the
cq:confproperty at the DAM root is updated to point to the most recently saved configuration, affecting all asset uploads.
Cause
AEM 6.5 officially supports only one Dynamic Media configuration per environment. When multiple configurations are present, saving any configuration updates the cq:conf property at the DAM root, causing all asset uploads to use the last-saved configuration. Folder-specific assignments may be overridden by this behavior.
Resolution resolution
Follow the steps below to resolve the issue:
-
Review your current Dynamic Media cloud configurations:
- In AEM, navigate to the root DAM folder (For example:
/content/dam) and check the value of thecq:confproperty. This should point to the intended global configuration path (For example:/conf/globalor your chosen configuration path).
- In AEM, navigate to the root DAM folder (For example:
-
Assign configurations explicitly to subfolders:
-
For each subfolder that requires a specific Dynamic Media configuration, set the
cq:confproperty explicitly on that folder’s configuration node (For example:/content/dam//jcr:content). -
Assign the appropriate configuration path (For example:
;/conf/) to each folder as needed. -
In AEM as a Cloud Service (AEMaaCS), direct JCR edits aren’t permitted. Use the AEM user interface to assign cloud configurations to folders:
-
Navigate to the desired folder in the Assets console.
-
Select the folder, open the properties, and assign the required cloud configuration from the available options.
-
-
Avoid unnecessary modifications to the root DAM configuration:
- Don’t repeatedly save or update the global configuration unless necessary, as this will update the
cq:confproperty at the DAM root and may override folder-specific assignments.
- Don’t repeatedly save or update the global configuration unless necessary, as this will update the
-
Test configuration assignments in a non-Production environment:
- Before making changes in Production, validate your configuration assignments in a pre-Production or test environment to ensure the expected behavior.
-
Consider consolidating to a single Dynamic Media account:
- If possible, use a single Dynamic Media account with a generic Scene7 domain to avoid the complexity and potential issues associated with multiple configurations. This is the recommended and supported setup for AEM 6.5 environments.
After making changes, upload assets to different DAM folders, and verify that each asset uses the intended Dynamic Media configuration.