Adobe Developers Live, May 2023 | Seamless Integration of Experience Manager Assets with Applications

[kautuk_sahni]

Session Details

Does your organization want to deliver Adobe Experience Manager (AEM) hosted assets from your non-Adobe CMSes? Do you want to know how to write stable, testable, and maintainable AEM Assets Integrations in minutes instead of hours/days?
In this session, we will introduce next-generation integration capability from Experience Manager Assets, a brand-new innovation for Asset Delivery which, purpose-built to increase development velocity (faster TTV) enables super-low maintenance overhead (lower TCO). The innovation allows for the consumption and delivery of brand-approved assets hosted on AEM Assets Cloud Service, empowering organizations to govern asset availability (for content-authoring and delivery) and get insights about their consumption.

Session Recording

Session Schedule

23rd May, 2023 | 10:30-11:15 PST OR 18:30-19:15 UTC OR 19:30-20:15 CET

Speaker(s)

Harsh Chiki, Sr. Computer Scientist, Adobe & Somya Jain, Computer Scientist, Adobe

Moderator(s)

Adobe

Service(s)

Composability & Productivity Services

Full Schedule

Check Here

Q&A

Please use this thread to ask the question related to this Session.

Don't forget to register yourself for this session using the registration link shared above. 

[VedGSingh]

Hi @kautuk_sahni 

What is the recommended integration pattern ( Asset selector UI or the API based) and Why?

Thanks

Ved

[kautuk_sahni]

Reply from Speaker:

• for headless (no UI), use search API
• for UI - you have a ready UI pluggable - so use Asset Selector

[kautuk_sahni]

@VedGSingh The Reply I have got from the speaker is

When to pick Search API

• When integration is headless. (AS UI can’t surface)
• Nested filters (AS UI, supports or across filter values from one group of filter criteria, and and across filter groups) At times the combination of and and or across multiple properties can be required (though complex) but supported by Search API
• Facilitates custom page sizes, and lets one access a random page. (Asset Selector UI always starts with the first page and is of fixed 50-page size)

When to pick Asset Selector UI

• “Seamless and quick” Frontend integration - readily available - modern standard state-of-the-art UI. Support various modes, like modal, rail etc.
• Read-only filters can be qualified, and thus metadata-based restriction can be achieved apart from secure search (role-based)
• Support rail mode (drag and drop) and a mode that supports “select-ability”

HTH

[VedGSingh]

Thanks @kautuk_sahni for the detailed response.

So for integrating AEM DAM with other headless CMS solutions, Search API is the way to go. 

Regards,

Ved

[vgsingh]

Hi @kautuk_sahni 

This was a wonderful presentation. I have a couple of questions though -

1) Is the Search and Delivery API available in the AEM CS or is it still in the experimental phase?

2)The document (Approved assets delivery - Capability and API Preview.pdf) reference in the demo mentions that the approved assets are searched and delivered via the delivery domain url which is of the form https://delivery-pXXX-eYYY.adobeaemcloud.com (substitute XXX => program ID and YYY => environment ID from Cloud Manager).

Is this domain available OOTB in AEM CS for all environments that are enabled for approved asset delivery or are specific configurations required?

Thanks

Ved

Thanks

Ved