Dynamic Media Open API option missing after reset or upgrade in AEM RDE
In Adobe Experience Manager as a Cloud Service (AEMaaCS), the Dynamic Media Open API option might not appear in a Rapid Development Environment (RDE) after an environment reset or upgrade. Reset or upgrade operations remove previously enabled Dynamic Media configurations from the environment. To fix this issue, re-enable Dynamic Media Open API and verify that the required configuration exists.
Description description
Environment
Adobe Experience Manager (AEM) Rapid Development Environment (RDE), any version.
Symptoms
- The Dynamic Media Open API option is not available in the AEM RDE environment.
- After an environment reset or upgrade, previously enabled Dynamic Media configurations are lost.
- The enablement tab or indicator for Dynamic Media does not appear in the Cloud Manager UI.
- The repository path
/conf/global/settings/dam/assets-configurations/assetdeliveryis missing or empty. - No specific error messages are displayed; the option simply does not appear.
Cause
Resetting or upgrading the AEM RDE environment removes custom configurations, including the enablement of Dynamic Media Open API. Manual re-enablement is required after such events.
Resolution resolution
Follow the steps below to resolve the issue.
- Confirm whether the AEM RDE environment was recently reset or upgraded.
- Use the repository browser to check whether the configuration exists at
/conf/global/settings/dam/assets-configurations/assetdelivery. If the path is missing or empty, Dynamic Media Open API is not enabled. - Re-enable Dynamic Media Open API for the RDE environment by following the standard enablement process used by your organization. This process typically involves applying the required configuration or requesting enablement through Cloud Manager or an internal process.
- After enablement, test with an asset in the Assets UI to verify that Dynamic Media with Open API is working correctly. Check for the delivery URL to confirm enablement.
- If the environment is reset or upgraded again, repeat these steps because the configuration does not persist through resets.
Related Reading
recommendation-more-help
experience-cloud-kcs-help-kbarticles