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:
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).
Push to AEM DAM:
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:
Query Dynamic Media (Scene7) using its API.
Download the asset file.
Upload to AEM via HTTP API (Assets API or Sling POST Servlet).
(Optional) Schedule or trigger this via Adobe I/O Events or webhooks.
Useful Links
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.
