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 disable the workflow launcher 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 launcher by disabling the OSGi component:

1

com.day.cq.workflow.launcher.impl.WorkflowLauncherImpl

You can do this through the OSGi console at http://localhost:4502/system/console/components.

  1. Install the content package from step 1 through Package Manager.

  2. Re-enable the workflow launcher by starting WorkflowLauncherImpl again.

Why This Works

By disabling the workflow launcher, AEM imports the asset nodes directly without triggering the DAM Update Asset workflow for each file. Once the launcher is 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