AEM Assets HTTP API Postman collection

Introduction

Adobe Experience Manager (AEM) is a leading content management system that empowers enterprises to efficiently manage their digital assets. Whether it's images, videos, documents, or other media files, AEM provides a robust and scalable platform for organizing and delivering assets across various channels. In this blog post, we'll explore the AEM Asset HTTP API, a powerful tool that enables seamless integration with AEM's asset management capabilities.

What is the AEM Asset HTTP API?

The AEM Asset HTTP API is a RESTful API that allows developers to interact with AEM's Digital Asset Management (DAM) system programmatically. It provides a set of HTTP endpoints to create, retrieve, update, and delete digital assets, folders, and collections within the AEM DAM.

Key Benefits of Using the AEM Asset HTTP API:

1. Automation and Integration: The API facilitates integration with third-party applications, marketing automation platforms, and other systems, streamlining asset management workflows.

2. Customization: Developers can build custom asset management solutions tailored to specific business needs using the API.

3. Batch Operations: The API supports batch operations, allowing multiple asset operations to be performed in a single request, optimizing performance.

4. Enhanced Performance: By utilizing the API, asset operations can be executed remotely, reducing the load on the AEM server.

Getting Started with the AEM Asset HTTP API:

Before diving into the API, you need to ensure you have the necessary access and authentication to interact with AEM programmatically. AEM provides various authentication mechanisms, including OAuth2 and basic authentication. Once authenticated, you'll receive an access token that needs to be included in your API requests as the "Authorization" header.

To access the API:

1. Open the API service document at https://[hostname]:[port]/api.json.
2. Follow the Assets service link leading to https://[hostname]:[server]/api/assets.json.

I have created a postman collection for most of the operations on the assets, folders and renditions.

I have published the postman collection here.

AEM WCM Component Core bundle is not active

I am trying to run WKND site on AEM 6.5.12. Created AEM Project using below archetype command.

mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate \
 -D archetypeGroupId=com.adobe.aem \
 -D archetypeArtifactId=aem-project-archetype \
 -D archetypeVersion=41\
 -D aemVersion=6.5.12 \
 -D appTitle="WKND App" \
 -D appId="wknd-app" \
 -D groupId="com.adobe.aem.guides.wkndapp" -D frontendModule="decoupled"

I am getting below error when loading the WKND home page properties.

Compilation errors in org/apache/sling/scripting/sightly/apps/core/wcm/components/commons/editor/dialog/inherited/v1/inherited/render_html.java: Line 39, column 2543 : com.adobe.cq.wcm.core.components.commons.editor.dialog.inherited.InheritedField cannot be resolved to a type.

To fix this error, check the core component bundle status.

 If bundle is not active then check the AEM version and Core component compatibility at here. 

After installing 2.19.2 version for AEM 6.5.12 then bundle status is changed to active.

HTTP ERROR 503 AuthenticationSupport service missing. Cannot authenticate request.

 I was not able to login to local AEM instance and figured out instance is working after removing the repoint folder under path "crx-quickstart/launchpad/config/org/apache/sling/jcr/repoinit".

java.nio.file.FileSystemException: dispatcher\src\conf.d\enabled_vhosts\aem_author.vhost: A required privilege is not held by the client.

When creating new AEM Project using maven archetype version 41, I was getting below error.

"[ERROR] Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate (default-cli) on project standalone-pom:  java.nio.file.FileSystemException: C:\Kishore\aem-nextjs\dispatcher\src\conf.d\enabled_vhosts\aem_author.vhost: A required privilege is not held by the client."

Below is the command to create AEM Project using Maven Archetype 41

mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate \

 -D archetypeGroupId=com.adobe.aem \

 -D archetypeArtifactId=aem-project-archetype \

 -D archetypeVersion=41\

 -D aemVersion=6.5.17 \

 -D appTitle="WKND App" \

 -D appId="wknd-app" \

 -D groupId="com.adobe.aem.guides.wkndapp" \

 -D frontendModule="decoupled"

To avoid this, run the command prompt or terminal as Administrator.

AEM as a Cloud Service: Local Setup

Adobe is providing AEM SDK to install it locally.

Follow below steps to install SDK locally and install WKND site.

Navigate to Experience Cloud Software Distribution

Go to the General tab, download the latest Java version.

AEM as a Cloud Service: Dispatcher Setup

Local Dispatcher Setup

The AEM as a Cloud Service SDK includes a validator tool and docker image for simulating it locally.

 Dispatcher Tools is comprised of:

• a baseline set of Apache HTTP Web server and Dispatcher configuration files, located in .../dispatcher-sdk-x.x.x/src
• a configuration validator CLI tool, located at .../dispatcher-sdk-x.x.x/bin/validator
• a configuration deployment CLI tool, located at .../dispatcher-sdk-x.x.x/bin/docker_run
• a Docker image that runs Apache HTTP Web server with the Dispatcher module