Connected assets is a long-awaited feature by many enterprise customers of AEM. Customers that have their separate central DAM (Digital asset Management) for assets and different instance for Sites. Connected assets also called as remote dam allows seamless access to a centralized DAM for search, drag & drop, save and publish remote assets from your AEM sites instance. Connected Assets feature is well suited for both AMS hosted instances as well as on premise instance, for this tutorial i am going to use on premise instances.
In this tutorial we will see :-
- Connected Assets Overview.
- What customer problem is solved using Connected Assets.
- Integrate connected asset instance in aem.
- Important points to Note.
- Limitations
Read more at AEMCQ5Tutorials:: Connected Assets – AEM 6.5
Important Points to Note:
Recently I got a chance to attend AEM Meetup 2019, Below are few of the questions that are asked during the session on connected asset and answered by the experts.
- How Network structure is optimized to support assets from remote dam across geographical locations?
- As per the test records, it took around 1 sec without noise to fetch 100 mb file without original asset (only metadata and renditions ) asynchronously and 10 sec with noise.
- Does connected DAM supports both upstream and downstream? Means can we upload asset to third party like adobe stock from sites instance or it can only download from remote instance?
- Currently it can only supports downstream means we can only download remote assets, upload is not supported.
- How connected asset is different from dynamic media in aem?
- Connected assets is used for authoring where as dynamics media is used as a means for delivering content.
- When connected asset creates local copy of asset ? When as soon as we we see them in content finder or when we drag and drop them onto the page?
- Local copy of assets is created when we drag and drop the asset on the page.
- How custom rendition are handled in case of connected assets on site instance?
- We can restrict custom renditions by modifying the launchers for DAM Update Asset and DAM Metadata Writeback under Tools > Workflow > Launchers.
- If i move an connected asset local copy from one place to another then will it update all page reference of all image reference?
- Yes it will update all existing image references on the pages.
Limitation
- Local assets are not synchronized with the original assets on the remote instance. Any edits, deletions, or revoking of permissions on the DAM instance are not propagated downstream.
- Local assets are read-only copies. Only non-destructive edits are permitted that are allowed by the Sites components.
- Locally fetched assets are available for authoring purposes only. Asset update workflows cannot be applied and metadata cannot be edited.
- Only image formats are supported. Dynamic Media, documents, content fragments, and experience fragments are not supported.
- Metadata schemas are not fetched.
- All Sites Authors have read permissions on the fetched copies, even if they do not have access to the remote DAM instance.
- No API support to customize the integration.
