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 together. Another reason can be acquisitions leading to heterogenous infrastructure, including different Experience Manager versions, that the parent company wants to use together.
Connected Assets functionality supports the above use case by integrating Experience Manager Sites and Experience Manager Assets. Users can create web pages in Sites that use the digital assets from a separate Assets deployments.
When editing pages in Page Editor as target destination, the authors can seamlessly search, browse, and embed assets from a different Assets deployment that acts as a source of assets. The administrators create a one-time integration of a deployment of Experience Manager with Sites capability with another deployment of Experience Manager with Assets capability.
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.
Before you use or configure this capability, ensure the following:
The users are part of the appropriate user groups on each deployment.
For Adobe Experience Manager deployment types, one of the supported criteria is met. Experience Manager as a Cloud Service Assets works with Experience Manager 6.5. For more information about how this functionality works in Experience Manager 6.5, see Connected Assets in Experience Manager 6.5 Assets.
|Sites as a Cloud Service||Experience Manager 6.5 Sites on AMS||Experience Manager 6.5 Sites on-premise|
|Experience Manager Assets as a Cloud Service||Supported||Supported||Supported|
|Experience Manager 6.5 Assets on AMS||Supported||Supported||Supported|
|Experience Manager 6.5 Assets on-premise||Not Supported||Not Supported||Not Supported|
Authors search for images and the following types of documents in Content Finder and use the searched assets in Page Editor. Documents are added to the
Download component and images to the
Image component. Authors also add the remote assets in any custom Experience Manager component that extends the default
Image components. The supported formats are:
The various roles that are involved to configure and use the capability and their corresponding user groups are described below. Local scope is used for the use case where an author creates a web page. Remote scope is used for the DAM deployment hosting the required assets. The Sites author fetches these remote assets.
|Role||Scope||User group||User name in walk-through||Requirement|
|Sites administrator||Local||Experience Manager
||Set up Experience Manager and configure integration with the remote Assets deployment.|
||Used to view and duplicate the fetched assets at
||End users are Sites authors who use this integration to improve their content velocity. Authors can search and browse assets in remote DAM using Content Finder and using the required images in local web pages. The credentials of
|Assets administrator||Remote||Experience Manager
||Configure Cross-Origin Resource Sharing (CORS).|
||Author role on the remote Experience Manager deployment. Search and browse assets in Connected Assets using the Content Finder.|
|DAM distributor (technical user)||Remote||
||This user present on the remote deployment is used by Experience Manager local server (not the Sites author role) to fetch the remote assets, on behalf of Sites author. This role is not same as above two
|Sites technical user||Local||
||-||Allows Assets deployment to search for references to assets in the Sites web pages.|
An Experience Manager administrator can create this integration. Once created, the permissions that are required to use it are established via user groups. The user groups are defined on the Sites deployment and on the DAM deployment.
To configure Connected Assets and local Sites connectivity, follow these steps:
Access an existing Sites deployment. This Sites deployment is used for web page authoring, say at
https://[sites_servername]:port. As the page authoring happens on Sites deployment, let’s call the Sites deployment as local from the page authoring perspective.
Access an existing Assets deployment. This Assets deployment is used to manage digital assets, say at
Ensure that the users and roles with the appropriate scope exist on the Sites deployment and on the Assets deployment on AMS. Create a technical user on Assets deployment and add to the user group mentioned in users and groups involved.
Access the local Sites deployment at
https://[sites_servername]:port. Click Tools > Assets > Connected Assets Configuration and provide the following values:
connectedassetsfolder. The assets that are fetched from DAM are stored in this folder on the Sites deployment.
Figure: A typical configuration for Connected Assets functionality.
The existing digital assets on Assets deployment are already processed and the renditions are generated. These renditions are fetched using this functionality so there is no need to regenerate the renditions. Disable the workflow launchers to prevent regeneration of renditions. Adjust the launcher configurations on the (Sites) deployment to exclude the
connectedassets folder (the assets are fetched in this folder).
On Sites deployment, click Tools > Workflow > Launchers.
Search for Launchers with workflows as DAM Update Asset and DAM Metadata Writeback.
Select the workflow launcher and click Properties on the action bar.
In the Properties wizard, change the Path fields as the following mappings to update their regular expressions to exclude the mount point connectedassets.
All renditions that are available on the remote deployment are fetched, when authors fetch an asset. If you want to create more renditions of a fetched asset, skip this configuration step. The DAM Update Asset workflow gets triggered and creates more renditions. These renditions are available only on the local Sites deployment and not on the remote DAM deployment.
Add the Sites deployment as an allowed origin in the CORS configuration on the Assets deployment. For more information, see understand CORS.
Configure same site cookie support.
You can check the connectivity between the configured Sites deployments and Assets deployment.
Figure: Connection test of Connected Assets configured Sites.
You can configure a connection between Sites deployment and Dynamic Media deployment that allows webpage authors to use Dynamic Media images in their web pages. While authoring webpages, the experience of using remote Assets and remote Dynamic Media deployments remains the same. This allows you to leverage the Dynamic Media functionality via Connected Assets feature, for example smart crop and image presets.
To configure this connection, follow these steps.
Create Connected Assets configuration as described above. When configuring the functionality, select Fetch original rendition for Dynamic Media Connected Assets option.
Configure Dynamic Media on local Sites and remote Assets deployments. Follow the instructions to configure Dynamic Media.
Enable Dynamic Media support in Image Core Component. This feature enables the default Image component to display Dynamic Media images when Dynamic Media images are used by authors in webpages on local Sites deployment.
The website authors use Content Finder to connect to the DAM deployment. 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.
Authors can use the assets available on the local DAM and the remote DAM deployment, in a single web page. Use the Content Finder to switch between searching the local DAM or searching the remote DAM.
Only those tags of remote assets are fetched that have an exact corresponding tag along with the same taxonomy hierarchy, available on the local Sites deployment. Any other tags are discarded. Authors can search for remote assets using all the tags present on the remote Experience Manager deployment, as it offers a full-text search.
Use the above setup to try the authoring experience to understand how the functionality works. Use documents or images of your choice on the remote DAM deployment.
Navigate to the Assets interface on the remote deployment by accessing Assets > Files from Experience Manager workspace. Alternatively, access
https://[assets_servername_ams]:[port]/assets.html/content/dam in a browser. Upload the assets of your choice.
On the Sites deployment, in the profile activator in the upper-right corner, click Impersonate as. Provide
ksaner as user name, select the option provided, and click OK.
We.Retail website page at Sites > We.Retail > us > en. Edit the page. Alternatively, access
https://[aem_server]:[port]/editor.html/content/we-retail/us/en/men.html in a browser to edit a page.
Click Toggle Side Panel on upper-left corner of the page.
Open the Assets tab and click Log in to Connected Assets.
Provide the credentials –
ksaner as user name and
password as password. This user has authoring permissions on both the Experience Manager deployments.
Search for the asset that you added to DAM. The remote assets are displayed in the left panel. Filter for images or documents and further filter for types of supported documents. Drag the images on an
Image component and documents on a
The fetched assets are read-only on the local Sites deployment. You can still use the options provided by your Sites components to edit the fetched asset. The editing by components is non-destructive.
Figure: Options to filter document types and images when searching assets on remote DAM.
A site author is notified if an asset is fetched asynchronously and if any fetch task fails. While authoring or even after authoring, the authors can see detailed information about fetch tasks and errors in the asynchronous jobs user interface.
Figure: Notification about asynchronous fetching of assets that happens in the background.
When publishing a page, Experience Manager displays a complete list of assets that are used on the page. Ensure that the remote assets are fetched successfully at the time of publishing. To check the status of each fetched asset, see asynchronous jobs user interface.
Even if one or more remote assets are not fetched, the page is published. The component using the remote asset is published empty. The Experience Manager notification area displays a notification for errors that show in asynchronous jobs page.
Once used in a web page, the fetched remote assets are searchable and usable by anyone who has permissions to access the local folder. The fetched assets are stored in the local folder (
connectedassets in the above walk-through). The assets are also searchable and visible in the local repository via Content Finder.
The fetched assets can be used as any other local asset, except that the associated metadata cannot be edited.
Experience Manager lets DAM users check all the references to an asset. It helps understand and manage the usage of an asset in remote Sites and in compound assets. Many authors of webpages on Experience Manager Sites deployment can use an asset on a remote DAM in different webpages. To simplify asset management and not lead to broken references, it is important for the DAM users to check use of an asset across local and remote webpages. The References tab in an asset’s Properties page lists the local and remote references of the asset.
To view and manage references on the Assets deployment, follow these steps:
Select an asset in Assets Console and click Properties from the toolbar.
Click References tab. See Local References for use of the asset on the Assets deployment. See **Remote References for use of the asset on Sites deployment where the asset was fetched using Connected Assets functionality.
The references for Sites pages display total count of references for each local Sites. It may take some time to find all the references and display the total number of references.
The list of references is interactive and DAM users can click on a reference to open the referencing page. If remote references cannot be fetched for some reason, a notification is displayed informing the user of the failure.
Users can move or delete the asset. When moving or deleting an asset, the total number of references of all the selected assets/folders are displayed in a warning dialog. When deleting an asset for which the references are not yet displayed, a warning dialog is displayed.
dam:Assetnode, the metadata, and renditions generated by Assets deployment are all fetched on the Sites deployment.
Imagecomponent, can be done on fetched assets. Assets are read-only.
To troubleshoot common errors, follow these steps:
If you are unable to search for remote assets from the Content Finder, then ensure that the required roles and permissions are in place.
An asset fetched from the remote DAM may not be published on a web page for one or more reasons. It doesn’t exist on remote server, lack of appropriate permissions to fetch it, or network failure can be the reasons. Ensure that the asset is not removed from the remote DAM. Ensure that appropriate permissions are in place and the prerequisites are met. Retry adding the asset to the page and republish. Check the list of asynchronous jobs for errors in asset fetching.
If you are unable to access the remote DAM deployment from the local Sites deployment, ensure that cross-site cookies are allowed and same site cookie support is configured. If cross-site cookies are blocked the deployments of Experience Manager may not authenticate. For example, Google Chrome in Incognito mode may block third-party cookies. To allow cookies in Chrome browser, click the ‘eye’ icon in the address bar, navigate to Site Not Working > Blocked, select the Remote DAM URL, and allow login-token cookie. Alternately, see how to enable third-party cookies.
If remote references are not retrieved and results in an error message, check if Sites deployment is available and check for network connectivity issues. Retry later to check. Assets deployment attempts twice to establish connection with Sites deployment and then reports a failure.