Leveraging Dynamic Media with OpenAPI using wcm.io Media Handler

Dynamic Media with Open API (formerly known as Next Generation Dynamic Media, Codename “Polaris”) is the next generation of Adobe Dynamic Media, with a much more robust and modern integration into AEMaaCS.

The talk will give a brief overview of the different capabilities in AEM to handle image renditions and binary assets in your AEM application, and about the possibilities and limitations of the out-of-the-box features with AEMaaCS and AEM WCM Core Components.

Then we will focus on getting the most out of Dynamic Media with Open API using wcm.io Media Handler and its unified API, which acts as single entry point into all custom component requirements for handling assets. It provides transparent fallback to other capabilities e.g. when running the same code in the cloud environment and local AEMaaCS SDK instances. Make use of AI-based smart cropping for all your assets.

Will customers with existing Dynamic Media license be able to use DM with OpenAPI support?
(see answer in talk video)

Konrad Windszus

How does that approve flag work with together with updates (metadata and/or renditions). Do you have to reset it while the updates are happening? What happens to the original URL?

(see answer in talk video)

Vugar Aghayev

In AEM, when you publish a page all the referenced assets and pages replicated as well by default. How this work with the approved flag? It will be a tedious task to flag each asset one by one.

(see answer in talk video)

Beo

Will this be supported along with graphQL with _dmS7Url?

Stefan Seifert

I do not have an authorative answer for this - but i'm quite sure Adobe will support the DM with Open API there as well.

Is there a way to have protected assets when using the assets outside AEM pages? So for example only authorized customers can access some assets in a external app.

Georg Henzler

So this is the `dam:roles` property that you can set on the metadata of an asset

Fabian

To make smart crops available, processing profiles need to be created, that are usually used to define static rendition generation. How does it work, will the Asset Compute workers extract and upload the smart crop information to AEM or directly to Dynamic Media?

Stefan Seifert

The Dynamic Media "Image Profiles" are something diffrent then the "Processing Profiles". The former are only available if you have activated/licensed DM for your environment. If an DM Image Profile is assigned to an asset folder, all assets uploaded are automatically processed with this profile. Or, if assets are already uploaded, you can reprocess them.

Beo

Core component still uses "img" tag with sourceset instead of picture tag? And still insert all Crops as sourceset?

Stefan Seifert

Core Components does not have a concept for supporting different apsect ratios. They support different widths depending on screen size, but not different aspect ratios. Picture tag is not used. Smart Crops can be used, but you have to pick a single one for each place you have inserted an image.