Introduction

The Adobe Experience Manager (AEM) Aspire connector will crawl content from an Adobe Experience Manager server.

Environment and Access Requirements

Repository Support

The Adobe Experience Manager connector supports crawling the following the repositories:

Account Privileges

For the Adobe Experience Manager connector to be able to crawl content, the Aspire Worker nodes must be run with an account with (Permissions).

• Due to API limitations, the AEM connector requires the JSON API to be enabled in the server for the connector to work.
• In order to access AEM, a user account with sufficient read privileges to access the content to crawl must be supplied.
• Before installing the AEM connector, make sure that the AEM server is up and running.

Framework and Connector Features

Framework Features

Connector Features

The Adobe Experience Manager connector has the following features:

• <Connector Feature 1>

Content Crawled

The Adobe Experience Manager connector is able to crawl the following objects:

Some of the features of the AEM connector include:.

• Fetches access control lists (ACLs) for document level security. For the current implementation only Closed Users Groups are supported as ACLs.
• Search engine independent.
• Can filter content based on properties using expected values or patterns.
• Filter pages base on the scheduled on and off time.
• Runs from any machine with access to the given to the AEM server.
• Supports optional content fetching.

Content Crawled

The AEM connector retrieves several types of documents from:

• Page objects
• Asset objects

Limitations

The Adobe Experience Manager Connector has the following limitations:

• <Limitation 1>