We have multiple ways for customers to get assets into AEM and process them once in AEM Assets. How do customers pick the right approach for their use case? How can they leverage the import & processing capabilities of the platform to maximize the value of their investment and reduce their time to value? Learn how the new capabilities of the AEM Assets Cloud Service platform
10/5/21 10:15 PDT 10/5/21 19:15 CEST
Daniel Klco and Tania Mathern
Speaker team
Experience Manager Assets
These tools are meant only for getting binaries into AEM ? Then have post processing steps to extract metadata ? |
Bulk Ingestion Tooling can ingest any file (image, document, binary). The default AEM processing and/or processing profiles will take care of generating renditions and extracting metadata as configured. There is also a Bulk metadata import tool: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/assets/admin/metadata-impor... |
When we do bulk ingestion, is it recommended to disable workflows? or do we follow any other best practice to generate renditions while doing bulk asset ingestion? | You don't need to disable workflows in Cloud Service anymore. But, please keep in mind that there is no DAM Update Asset Workflow and all custom workflows should be configured as a post processing workflow as opposed to a launcher. https://experienceleague.adobe.com/docs/experience-manager-cloud-service/assets/manage/asset-microse... |
How are failed events tracked? Can events get lost as well, specially in case of high processing? | Events are tracked using a journal, which is polled to know rendition status. Events usually don't get lost, and even if it would happen, the AEM watchdog would retry failed or unresponsive renditions. |
can you discuss any advantages to using the AEM desktop manager for uploads? | I am assuming they meant AEM Desktop App, it's a different tool that does similar things, but really for a different persona who doesn't want to log in to AEM Web UI and prefers to work on their desktop as a native experience |
Currently we have custom process to purge image cache on DM CDN post smart crop edits. Will we be able to hook this process/job on CS setup/events available for same? | This might be possible using a post processing workflow, but we need more details on the use case |
Please use this thread to ask the question related to this Session.
Views
Replies
Total Likes
Great session. Dan Klco & Tania -I am following this doc but facing an issue while moving assets to AEM assets - https://github.com/adobe/aem-upload#background. You shown a script to move assets from local file system to AEM Assets. Can you share the node js code to move assets from local to AEM Assets cloud ?
Thanks @Mario248!
Here's a Gist with the code: https://gist.github.com/klcodanr/933c757e758a707a2280a0d1d05e0c68
I also demonstrate the AEM AIO CLI plugin which can do recursive imports as well: https://github.com/adobe/aio-cli-plugin-aem
Awesome. It worked very well. Moved 3.5 GB from local files system to cloud in ~10 mins. Of course it depend on network speed.
Thank you so much for sharing the script.
Hi @klcodanr & Tania, Thanks for the wonderful session!
We are looking to migrate assets from multiple 3rd party cloud-based content management systems to AEM Assets as a Cloud Service.
The AEM Upload Tool or AIO CLI plugin seems the be a good way to migrate all assets to AEM.
However, I have few queries for the same -
1. The session mentioned the metadata migration won't be part of the upload tool. What then is the recommended way to migrate metadata to AEM?
2. The session walkthrough showed the files in local system being migrated to the cloud instance. Is there a way via upload tool to directly migrate from one system to another without having local involved?
3. The AEM Assets Bulk Import can it be configured to extend beyond S3 or Azure Blob Storage? (Source DAM Systems are Kapost and Box)
Views
Replies
Total Likes
@Rohan_Garg Thanks! Glad you enjoyed the session.
1. The recommendation would be to use the Metadata Import tool in AEM Assets CS: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/admin/metada...
2. Not without the files landing in some intermediate location. You could for example download them to an EC2 or use an EC2 to fetch the files and then re-upload them to AEM, but currently there's no support for importing remote files.
3. Not at the moment. You could open a feature request, but the quickest solution would be to export from those systems to an S3 or similar and bulk import from there.
Thank you for the prompt reply @klcodanr!
For point 2 & 3, the data set is 6.5 TB and we will check with the client to see if they allow for a temporary storage in S3 or use EC2 for migration.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies