aem

AEM Digital Assets Installation

Evgeniy Fitsner Software Engineer
2 min read
AEM Digital Assets Installation

Introduction

When you need to install a large number of digital assets on AEM, the straightforward approach of creating a content package and deploying it through Package Manager can become problematic. The asset rendition workflows trigger for each asset during installation, which can cause the process to hang or take an extremely long time.

The Solution

Temporarily stop the workflow bundles during package installation to prevent rendition workflows from blocking the import process.

Steps

  1. Create a content package containing the digital assets you want to install.

  2. Stop the workflow bundles to prevent launchers from firing.

    On classic AEM (6.x, on-premise/AMS), stop:

    1

    com.day.cq.workflow.cq-workflow-console

    On AEMaaCS (AEM as a Cloud Service), stop both:

    1
2

    com.adobe.granite.workflow.core
com.day.cq.workflow.cq-workflow-console

    You can do this through the Felix console at http://localhost:4502/system/console/bundles or via curl:

    1

    curl -u admin:admin -X POST -d "action=stop" "http://localhost:4502/system/console/bundles/com.day.cq.workflow.cq-workflow-console"

    For AEMaaCS, repeat for the second bundle:

    1

    curl -u admin:admin -X POST -d "action=stop" "http://localhost:4502/system/console/bundles/com.adobe.granite.workflow.core"

  3. Install the content package from step 1 — either through Package Manager, or by copying it into crx-quickstart/install/ for automatic deployment.

  4. Re-enable the workflow bundles by starting the same bundles again:

    1

    curl -u admin:admin -X POST -d "action=start" "http://localhost:4502/system/console/bundles/com.day.cq.workflow.cq-workflow-console"

    For AEMaaCS, repeat for the second bundle:

    1

    curl -u admin:admin -X POST -d "action=start" "http://localhost:4502/system/console/bundles/com.adobe.granite.workflow.core"

Why This Works

By stopping the workflow bundles, AEM imports the asset nodes directly without triggering the DAM Update Asset workflow for each file. Once the bundles are re-enabled, any new assets uploaded through the normal UI will process renditions as expected.

This approach is particularly useful when migrating assets from another system or restoring a large asset library from backup.

Contents