Learn how to configure the Core Component Image and Teaser Components to support remote Next Generation Dynamic Media assets.
Support for Next Generation Dynamic Media remote assets requires:
It is generally recommended to run all of your production AEM instances using HTTPs. However your local development environments may not be set up as such. However, Next Generation Dynamic Media remote assets requires HTTPS in order to function.
Use this guide to configure HTTPS wherever you wish to use remote assets, including development environments.
The location of the remote assets must be defined in an OSGi configuration. Configure the Next Generation Dynamic Media Config OSGi configuration as follows, replacing the values with those of your remote asset environment.
imsClient="<ims-client-name>" enabled=B"true" imsOrg="<ims-org>@AdobeOrg" repositoryId="<repo-id>.adobeaemcloud.com"
For details on how to configure OSGi, please see the following documents:
Now you can verify that the Next Generation Dynamic Media remote assets feature is working. To do this, you can install the WKND sample site and Core Components.
Once the Core Components and WKND site are installed, you can test the feature on any WKND page.
Access the AEM instance using HTTPS.
Open a WKND demo page in the page editor such as
Add an image component to the page.
In the Configure dialog of the component, uncheck the option Inherit featured image from page on the Asset tab and click Pick.
If the configuration is correct, a drop-down will appear with the options Local and Remote. Select Remote.
A dialog will open and you will need to authenticate to the remote service.
Once authenticated, an asset browser of the remote service will open. Select the desired asset and tap or click Select.
The remote asset is added to your local AEM page and you have verified that the feature is correctly configured.