Uploading Assets to AEMaaCS Using "AEM Upload" Library

AEM Upload Library

As explained in the previous section, uploading assets to AEMaaCS involves three steps. This process can be inconvenient or tedious, so Adobe introduced the AEM Upload Library to alleviate that workload. This open-source project streamlines these steps into a single, easy-to-use way for asset uploads. The AEM Upload Library can be utilized as a Node module or as a command-line interface (CLI), enabling you to create your own separate external process outside AEM (JVM) for greater flexibility to meet various scenarios and requirements.

**Disclaimer: You can upload an asset directly using the Adobe APIs. This library is intended to streamline that process. Consider this tool an additional option.

Let’s See It In Action

Now, let’s demonstrate how to upload an asset from the desktop to AEMaaCS via an API. The API will be invoked using Postman and built using Node with Express.

const express = require("express");
const multer = require('multer');
const DirectBinary = require('@adobe/aem-upload');

// Init vars
const targetUrl = 'https://author-xxx-xxx.adobeaemcloud.com/content/dam/demo';
const codes = DirectBinary.DirectBinaryUploadErrorCodes;
const upload = new DirectBinary.DirectBinaryUpload();

// TODO: Make sure to manage your token properly not this way!
const ACCESS_TOKEN = "xxxx";

app.post("/upload", uploadMulter.single('file'), (req, res) => {
    let uploadFiles = [];
    // Access the blob from request
    let assetToUpload = {
        "fileName": req.file.originalname, 
        "fileSize": req.file.size,
        "versionLabel": "original",
        "blob": req.file.buffer,
        "replace": true
    };
    uploadFiles.push(assetToUpload);
    
    const options = new DirectBinary.DirectBinaryUploadOptions()
        .withUrl(targetUrl)
        .withUploadFiles(uploadFiles)
        .withHttpOptions({
            headers: {
                Authorization: `Bearer ${ACCESS_TOKEN}`
            }
        });
        
    upload.uploadFiles(options)
        .then(result => {
            const { errors = [], detailedResult = [] } = result;
            detailedResult.forEach(resultJson => {
                console.log(`Attempting to upload to ${resultJson.fileUrl}`);
                console.log(`With result: ${JSON.stringify(resultJson.result)}`);
            });
            errors.forEach(error => {
                // TODO: Error handling and Re-try as needed
            });
        })
        .catch(err => {
            console.log(`Error ${err}`)
            res.status(500).json({status:500, message: "Oops something goes wrong!"});
        });

    res.status(200).json({status:200, message: "Asset Upload Succesfully"});
});

app.listen(3000);

Let’s highlight the important parts of this code:

• Line 2: Imports Multer, a Node library for uploading files, making it easier to process file uploads in requests.

• Line 3: Imports the aem-upload library (Node module flavor)

• Line 8: Creates an instance of DirectBinaryUpload from the AEM Upload library to manage uploads.

• Line 13: This line defines a POST endpoint /upload that accepts a single file under the field name 'file'

• Line 25: This constructs the upload options, setting the target URL, the files to upload, and the HTTP headers, including the authorization token

• Line 34: This line initiates the upload process using the options defined earlier

Now, we can run the Node server and then invoke a new /upload endpoint using Postman like this:

With that unique call, we can see that the asset has been successfully uploaded to the AEMaaCS instance.

A similar approach can be taken using the AEM Upload CLI, a plugin for the Adobe I/O CLI.

Wrapping Up

AEM Upload makes it easier for developers to migrate a library of content assets to the cloud for use in AEMaaCS. However, companies must also consider other areas.

Oshyn is an Adobe partner that can support you with multiple aspects of your journey with the Adobe DXP suite, including design planning, development, post-launch enhancements, and maintenance. If you're considering migrating to AEMaaCS, starting early can make a massive difference. See our blog for tips on how to get prepared: Start Early for a Successful AEMaaCS Migration.

References

• AEMaaCS Assets Ingestion

• AEM Upload