Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

External DAM integration with AEM 6.x

Avatar

Level 2

Dear All,

What will be the best approach to take when you choose to use external DAM to integrate with AEM, while keeping the same user experience for author to drag & drop the images (Assets), set metadata etc., please share your thoughts and experience.

1 Accepted Solution

Avatar

Correct answer by
Level 4

The central DAM should be configured similar to cloud service configuration (like Marketing Cloud, Brand Portal etc.) at AEM. Then replication sync (on demand or cache) is something consider to get all assets from central DAM to AEM. Then rest of the flow/experience works same since assets are now duplicated and works as local in AEM. But keeping the local copy in sync with central DAM would be a challenge and you can check if that is the use case or not.

Please share the exact use case to talk more on this, especially the lifecycle of assets fetched from central DAM. are they going to be used for Page authoring?

Thanks,

Ashutosh

View solution in original post

4 Replies

Avatar

Level 10

Best practice is to use the AEM DAM. I am not aware of getting the same functionality using another DAM system.

Avatar

Community Advisor

Hi,

I agree with Scott.

Why you use external DAM when we have AEM DAM. I didn't see anywhere that integrating External DAM with AEM. You can achieve any functionality using AEM DAM.

Thanks,

Ratna Kumar.

Avatar

Level 2

Hi Scott,

Completely agreed. The use case here is to have centralized DAM repository, shares assets with other applications and AEM is one of them.

Avatar

Correct answer by
Level 4

The central DAM should be configured similar to cloud service configuration (like Marketing Cloud, Brand Portal etc.) at AEM. Then replication sync (on demand or cache) is something consider to get all assets from central DAM to AEM. Then rest of the flow/experience works same since assets are now duplicated and works as local in AEM. But keeping the local copy in sync with central DAM would be a challenge and you can check if that is the use case or not.

Please share the exact use case to talk more on this, especially the lifecycle of assets fetched from central DAM. are they going to be used for Page authoring?

Thanks,

Ashutosh