Configurations for AEM WCM Core Components

February 13, 2024 ยท View on GitHub

OSGi Configurations

AEM uses OSGi configurations to drive how its internals work and WCM Core Components leverage the following:

General Configurations:

ConfigurationDescription
ComponentConfigImplEnables Content Fragment management for Content Fragment component. Reference documentation: https://experienceleague.adobe.com/docs/experience-manager-65/developing/extending-aem/content-fragments-config-components-rendering.html
RTEFilterServletFactoryEnables usage of RTE (Rich Text Editor) with Text component. Reference documentation: https://experienceleague.adobe.com/docs/experience-manager-65/administering/operations/rich-text-editor.html
OEmbedClientImplConfigurationFactoryEnables out-of-the-box OEmbed configurations for several services, with Embed component
AdaptiveImageServletMappingConfigurationFactoryEnables adaptive image support for Image component
MailServletEnables email support for user-submitted information in Core Form container
ServiceUserMapperImplEnables access rights for ClientLibraries and ComponentFiles helpers

author Configurations

ConfigurationDescription
FormParagraphPostProcessorEnables functionality of Core Form container
MobileEmulatorProviderEnables mobile devices emulation in the editor for Page component

Context-Aware configurations

The following context-aware configurations are defined by the AEM WCM Core Components:

ConfigurationDescription
HtmlPageItemsConfigHolds information on items to be included by Page component: scripts, links, meta elements
PdfViewerCaConfigHolds configuration for PDF Viewer component
DataLayerConfigToggles and configures the Adobe Client Data Layer and Google Data Layer integrations

At the moment, there is no editing UI for context-aware configuration available out-of-the-box. Developers can either: