Use Connected Assets to share DAM assets in Experience Manager Sites | AEM Community Discussion

[kautuk_sahni]

Use Connected Assets to share DAM assets in Experience Manager Sites by Adobe Docs

Abstract

In large enterprises the infrastructure required to create websites may be distributed. At times the website creation capabilities and digital assets used to create these websites may reside in different deployments. One reason can be geographically distributed existing deployments that are required to work in tandem. Another reason can be acquisitions leading to heterogenous infrastructure that the parent company wants to use together.
Users can create web pages in Experience Manager Sites. Experience Manager Assets is the Digital Asset Management (DAM) system that supplies the required assets for websites. Experience Manager now supports the above use case by integrating Sites and Assets.

Overview of Connected Assets
When editing pages in Page Editor, the authors can seamlessly search, browse, and embed assets from a different Assets deployment. The administrators create a one-time integration of a deployment of Sites with a different (remote) deployment of Assets.
For the Sites authors, the remote assets are available as read-only local assets. The functionality supports seamless search and use of a few remote assets at a time. To make many remote assets available on a Sites deployment in one-go, consider migrating the assets in bulk. See Experience Manager Assets migration guide

Use remote assets
The website authors use Content Finder to connect to the DAM instance. The authors can browse, search for, and drag the remote assets in a component. To authenticate to the remote DAM, keep the credentials of the DAM user provided by your administrator handy.

Read Full Blog

Use Connected Assets to share DAM assets in Experience Manager Sites

Q&A

Please use this thread to ask the related questions.