How to bulk import of assets uploded in dynamic media server to AEM?

⚙️ Adobe I/O and Asset Compute Worker Overview

The Adobe Asset Compute Service is designed primarily to process assets that come into AEM, not to pull assets from external systems. Typically, you use it to generate thumbnails, previews, metadata, etc., for assets uploaded to AEM.

However, syncing assets from DM to AEM is a different challenge and requires integrating Adobe APIs differently.

🔄 Your Requirement: Sync assets from DM to AEM

There are two likely scenarios here:

✅ Scenario 1: DM Hosted on Scene7 (Dynamic Media Classic)

If your DM assets are hosted in Scene7, you can access them via Scene7 APIs:

📌 Steps:

1. Use Scene7 REST APIs:

   • Scene7 Publishing System API Docs

   • Authenticate via OAuth or IMS.

   • Get a list of assets via getAssets or similar endpoints.

   • Download the asset (usually by building a Scene7 URL).

2. Push to AEM DAM:

   • Use the AEM HTTP API (Assets HTTP API or custom servlet).

   • Upload the assets to the DAM via AEM endpoints.

Example:

POST https://<aem-host>/api/assets/<path>
Authorization: Bearer <token>
Content-Type: multipart/form-data

✅ Scenario 2: DM on AEM as a Cloud Service (integrated with Scene7 backend)

If you're using Dynamic Media with AEMaaCS, the assets are generally uploaded to AEM first and then published to DM.

But if assets are exclusively uploaded to Dynamic Media (not AEM), you may need to:

• Query Adobe Experience Platform Assets APIs if available.

• Or use Adobe I/O Events + custom Asset Compute worker to listen for DM uploads, and sync to AEM.

However, Adobe does not expose a direct API to pull assets from DM into AEM via Asset Compute workers.

💡 Better Approach: Use Adobe I/O Runtime Custom App

Rather than relying on Asset Compute, build a custom Adobe I/O Runtime action or Adobe App Builder app to:

1. Query Dynamic Media (Scene7) using its API.

2. Download the asset file.

3. Upload to AEM via HTTP API (Assets API or Sling POST Servlet).

4. (Optional) Schedule or trigger this via Adobe I/O Events or webhooks.

📄 Useful Links

• Adobe Scene7 (DM) API Docs

• AEM Assets HTTP API

• Adobe App Builder

• Adobe I/O Runtime

🚫 Limitations of Asset Compute Workers

Asset Compute workers are triggered by asset uploads to AEM, not designed to pull assets into AEM. So it’s not the right tool for DM → AEM syncing.

Hi @keerthana_h_n 

You can go through this article on accessing DM APIs - https://medium.com/@bsaravanaprakash/programmatic-crud-operations-on-adobe-dynamic-media-2e0eae67f40e 

Hope this helps!

Thanks

Narendra

Hi @keerthana_h_n ,

Adobe Asset Compute Workers are designed to enhance assets after they are uploaded to AEM not to pull assets from external systems like DM into AEM.

So, to sync DM => AEM, you must use:

  - Adobe I/O Runtime App (via Adobe App Builder)

  - Scene7 API (Dynamic Media Classic) or other DM APIs
  - AEM Assets HTTP API or Sling POST endpoint

Regards,
Amit

@keerthana_h_n Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!