Bulk Import tool - AEM

The Bulk Import tool in Adobe Experience Manager (AEM) as a Cloud Service to import assets in bulk from cloud storage providers like Azure Blob Storage and Amazon S3. The tool allows administrators to efficiently migrate large volumes of assets without custom coding. Key features include:

• Configuration: Save import configurations for single or repeated use.
• Filtering: Optionally filter assets by file size or MIME type.
• Import Modes: Define how to handle existing assets during import.
• Scheduling: Schedule imports for single or periodic execution.
• Job Status: Monitor the status and details of import jobs.

This tool is particularly useful for large-scale migrations and occasional bulk asset ingestions.

Where to find the log for asset compute workers | AEM Processing Profile | Asset Compute

In Adobe Experience Manager as a cloud service (AEM aa cloud service) when someone use asset compute worker (custom or ootb) via AEM Assets processing profile, a developer has to debug and find the issue when processing is getting fail. In this situation, where a developer will find or access the log for Adobe IO runtime or Asset compute worker, whether in AEM logs or IO runtime logs.

Image 1: Asset processing failed

Finding error

1. First, we need to look the AEM error log file and see if processing is trigger and any error printed in the log file.
   
2. Second, specially for asset compute worker, go to your local machine, open the terminal and get the logs using aio command "aio app logs". After that you will get the log from Adobe IO runtime and one can easily access the log and find the cause of failure.

Image 2: aio logs showing failure message

Note: To access the Adobe IO runtime logs, your machine should have the adobe aio installed. 

References

1. Debug an Asset Compute worker | Adobe Experience Manager

Add a custom action/option in AEM Assets

AEM Assets browser or asset editor have too many options to quickly perform the action like publish, edit, properties, download and many more. Today in this blog we will explore and implement how we could customoze this ribbon add a similar action in asset editor.

All these action items are coming from the libs path  /libs/dam/gui/content/assets, if a developer wants to add a custom action then developer have to create the same overlay assets directory so sling merger will read the custom action and load with the other options in Assets editor.  

Libs directory

Apps directory

Under the assets >> jcr:content >> actions >> selection add a node of type nt:unstructure, as shown here in below image.

Here we have added the action Translation as option, and this is how it will appear in the AEM Assets browser.

References:

AEM adding a button to a touchui toolbar

What is processing profile in AEM

AEM cloud service supports processing profiles feature, using this we can create custom renditions for assets. This rendition could be the predefined as well as renditions craeted or generated by third party application or system.

To integrate the third party generated rendition we need to integrate with the AEM asset compute feature that is avaialble in Adobe I/O runtime and easily connect with AEM a a cloud serivce. 

Note: Processing profile option is not avaiable in local AEM cloud service SDK.

References:

• https://experienceleague.adobe.com/docs/experience-manager-learn/assets/configuring/processing-profiles.html 
• https://github.com/adobe/asset-compute-sdk
• https://experienceleague.adobe.com/docs/asset-compute/using/home.html

How to start AEM with Dynamic Media

Dynamic media work as a run-mode in AEM and default it is disabled in AEM. When we start AEM using command we need to add "-r dynamicmedia_scene7" in the command line to start the AEM with dynamic media.

We could also set this run-mode in start file along with other run-modes separated by comma(,).

set CQ_RUNMODE=author,dynamicmedia_scene7

References

Setup and Configuration Dynamic Media