Store Asset binary data outside AEM, and still reference it from within AEM | Community
Skip to main content
N
NitroHazeDev
Level 9
October 16, 2015
Solved

Store Asset binary data outside AEM, and still reference it from within AEM

  • October 16, 2015
  • 11 replies
  • 4764 views

Hello,

Is there a way one could have the binary data of an asset stored elsewhere(outside of AEM, say CDN) and have a reference say a url , stored in metadata property in AEM,  pointing to where the asset is stored in CDN. The asset in CDN has the binary data.

Thus the asset in AEM has the refernce to the asset and its binary data in CDN. Is it possible to go about this approach?

Please suggest.

Regards,
NZ

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by PaulMcMahon

Ah I misunderstood your use case. There is no way use the DAM and store the binary somewhere else. Realistically you have 3 options in my opinion:

  1. Follow AEM standard and store and serve the binary from AEM. 
  2. Store the binary somewhere else and in the image components that render image on pages you store a reference to the binary in that other system and your image components point to that URL at run time. 
  3. Store the binary in AEM DAM and in the other system. One of the pieces of meta-data you store in AEM is a pointer to the binary in the other system. Then at runtime your image components use that point rather than the AEM URL. Depending on your process for creating these images you create a custom workflow that would publish and image to the other system. This is similar to how the Scene 7 integration works - http://dev.day.com/docs/en/cq/current/administering/integrating_with_adobe_marketing_cloud/scene7.html. 

11 replies

Show previous replies
A
Anonymous
October 16, 2015

Hi,

CDNs are used for caching. You need to follow a particular convention

& process to achieve this after agreeing with your CDN provider. It is immaterial

if CDNs store in binary format or not. On a global scale you need to determine

from which geographic location your (browser) request is coming from.With more than

one CDN, fixing a url is probably not a good idea. If your CDN is finalized, I'd recommend

running through their manuals.

- Venu Gummadala

Terms & ConditionsAccessibility statement

Loading footer...