Setup AEM Assets

Setup AEM Assets for your site.

Site Config

Adding AEM integration

The AEM integration provides an out of the box way to work with your AEM assets. It also allows you to use the DA App SDK to build rich applications that leverages any content stored on your AEM as a Cloud Service instance.

Prerequisites

You have AEMaaCS with either a publish instance or Dynamic Media.
You can change configurations in Cloud Manager.
You can change configurations in DA.

Step 1 - AEM as a Cloud Service

An AEM environment config will need to be set. Details in the screenshot below. Expect a full restart (~10-20 minutes) when this is saved.

Environment Configuration: ADOBE_PROVIDED_CLIENT_ID | darkalley

Step 2 - Document Authoring

Visit: https://da.live/config#/{{name-of-da-org}}/
Add key | value if it doesn't exist already.
Add aem.repositoryId | sub.youraemcloud.com
- Set aem.repositoryId as author-pxxxx-eyyyy.adobeaemcloud.com to select assets from author
- Set aem.repositoryId as delivery-pxxxx-eyyyy.adobeaemcloud.com to select assets from dynamic media delivery
Optional configurations
- Add aem.assets.prod.origin | https://mysite.com to load assets from mysite.com
- Add aem.assets.image.type | link to insert links to the images instead of copying them into the doc
- Add aem.assets.renditions.select | on to allow the author to select any available renditions from the selected asset.
- Add aem.asset.dm.delivery | on to use AEM Author for browsing, but Dynamic Media images.
- Add aem.asset.smartcrop.select | on to use Dynamic Media Smart Crop.
Paper plane > Save

Step 3 - Use it

Open any page and notice you have a new image icon in your toolbar. This will open a modal to your AEM Assets.
Select the asset you want and it will import into your document.
The asset must be published for DA & Edge Delivery Services to see it.

FAQ / Troubleshooting

The assets pane pulls up in DA, but I get an error inside it.
1. Wait an 5-10 minutes from when Cloud Manager tells you the variable is saved on your instance.
2. Make sure the org you are logged into on DA is the same org that is allowed on AEM.
When I select an image, it is broken in DA.
1. Ensure that you have a publish server (author only is not supported).
2. Ensure that the asset is published.
I don't see any folders in the asset picker.
1. You're pointing to a Dynamic Media instance and these do not support folders.
2. You can use an author hostname + aem.asset.dm.delivery to browse your assets hierarchy but use Dynamic Media URLs for delivery.

Use cases

In addition to having all the existing benefits of AEM Assets (governance, etc.), there are a couple use cases that can be unlocked related to DA:

Swapping an existing asset with an updated version.
Bulk replacing an image.

It's important to know that even if you change a single asset, if that asset is used on 1000 pages, you will need to re-preview and re-publish those 1000 pages for Edge Delivery Services to ingest the new image and update the references on aem.page and aem.live.

Use case 1: Swap an existing asset

User story: As an author, I would like to update an existing asset with more vibrant colors without having to change every page the asset is currently used on.

On da.live, use the side navigation panel to navigate to your assets using the "files" icon.
In Adobe Experience Manager Assets, navigate to the folder that contains the asset you want to replace.
Replace the asset and re-publish it.
Navigate to a page in DA that uses the asset in question.
Due to caching constraints, it may take up to a few minutes for the asset to update.
Once you can see your changes reflected, Edge Delivery is ready to ingest it. Copy the asset publish URL.
Paste the asset publish URL into DA's search. This will list every page on DA that is using the asset.
Use the the share button (action bar > share icon) to copy the AEM URLs.
Paste the URLs into DA's bulk preview & publish tool (da.live/apps/bulk). Run a preview & publish on these URLs.