Skip to main content

AEM Connector

The Adobe Experience Manager (AEM) connector allows Turing ES to index content from AEM author and publish instances. The connector runs as a separate process (Dumont DEP) and communicates with Turing ES via REST. Turing ES acts as a proxy — the API path /api/v2/integration/{integrationId}/** forwards requests to the configured connector endpoint.

For general integration management — creating instances, monitoring, statistics, and system information — see Integration.


Overview

The AEM connector is a two-part system:

ComponentWhere it runsDocumentation
AEM Event ListenerInside AEM (OSGi bundle) — sends indexing events to the connectorDumont DEP — AEM Event Listener
AEM Connector PluginDumont DEP process — fetches content from AEM and indexes it into Turing ESDumont DEP — AEM Connector
Integration InstanceTuring ES admin console — proxy configuration and monitoringIntegration

Configuration

All AEM-specific source configuration — connection details, root paths, content types, author/publish environments, locale mappings, delta tracking, indexing rules, and the Indexing Manager — is documented in the Dumont DEP — AEM Connector page.

The Turing ES admin console provides the UI for managing these settings under Enterprise Search → Integration → [your AEM instance].


Monitoring & Diagnostics

The following features are available in the Turing ES admin console for each AEM integration instance (see Integration for details):

FeatureDescription
MonitoringReal-time dashboard for tracking indexing events with filters and auto-refresh
Indexing StatsTable of completed bulk indexing operations with throughput metrics
Double CheckValidates consistency between the connector's content and the Turing ES search index
System InformationLive status, version, memory, and disk information from the connector
AEM LoggingAEM-specific logs in Logging → AEM (see Logging)

PageDescription
IntegrationGeneral integration management — instances, monitoring, statistics, and system information
Semantic NavigationConfigure the SN Sites that receive indexed content
Architecture OverviewEnd-to-end indexing flow from connector to Solr
REST API ReferenceAPI endpoints for programmatic indexing
Dumont DEP — AEM ConnectorHow the AEM connector works — source configuration, indexing flow, event listeners, API triggering
Dumont DEP — AEM Event ListenerInstall the OSGi event listener bundle inside AEM for real-time indexing
Dumont DEP — Extending AEMCustom attribute extractors, content processors, and configuration JSON reference