Configure Sling Mappings for Resource Resolution in Adobe Experience Manager(AEM) — Deep Dive

This tutorial explains the complete details on configuring sling mapping for resource resolution in Adobe Experience Manager(AEM).

Resource mapping is used to define the content mapping and redirects in AEM. This will helps us to define user-friendly shortened URLs to the website.

I have enabled two sample domains and pointing to /content/wknd/us/en and /content/wknd/ca/en nodes respectively(sample wknd website nodes).

The flow is as below

The user request for and, the Apache redirects the user to the domain-specific landing pages and also redirects the user to the shortened URL(hide/content/wknd/<country code> if user access the page with full content path). The dispatcher passes through(PT) the shortened content URL’s to publisher by appending the full content path /content/wknd/<country code>. This will help us to manage the dispatcher cache and cache invalidation optimally.

As the first step, let us enable the virtual host configurations for and in Apache(Dispatcher)

“DispatcherUseProcessedURL on” configuration should be enabled in dispatcher configuration to enable the Pass-Through URL’s to work e.g

Now both the domains and are accessible, this will display the mapped landing page content but the internal page links still point to the complete URL(/content/wknd/<<country code>>)

ResourceResolver configuration

Let us now enable the run mode-specific(my case the server is enabled with additional run mode “dev”) ResourceResolver configuration — “Apache Sling Resource Resolver Factory” to reverse map the internal full content path to the shortened URL.

Enable the mapping for all the required content paths to the “resource.resolver.mapping” configuration, Incoming mappings are applied to request paths to map to resource paths, outgoing mappings are applied to map resource paths to paths used on subsequent requests. Form is <internalPathPrefix><op><externalPathPrefix> where <op> is “>” for incoming mappings, “<” for outgoing mappings and “:” for mappings applied in both directions. Mappings are applied in configuration order by comparing and replacing URL prefixes.

Now the internal page links are transformed to shortened URL based on the URL mappings in the Resource Resolver.

Validate the mapping through jcrresolver — http://localhost:4503/system/console/jcrresolver, the incoming URL’s will be resolved without any issue as the dispatcher always sends the complete path(e.g /content/wknd/us/en.html) to the publisher

The content path is not reversed mapped to the shortened domain URL — the content path is shortened based on the resource mapping but not mapped to the domain URL

This approach has multiple drawbacks —

  • the mapping doesn’t support the regex expressions
  • it doesn’t support cross-site links because this rewriting method is not domain-aware
  • reverse map the content path to the corresponding domain won’t work

This will create issues while supporting multiple domains in the AEM platform and need to link the pages between sites(the components should not be able to identify the domain corresponding to the content path while linking the pages from different sites —…))

Enable etc mapping

We should use the etc mapping to enable the forward resolving(resolve the incoming URL to the content path) and reverse mapping (map the content path to the domain). The mapping of request URLs to resources is mainly configured in a configuration tree which is (by default) located below /etc/map. The actual location can be configured with the property of the configuration. That way you can even make it run mode-specific, by taking advantage of the Sling OSGi Installer's run mode awareness.

As a first step create an environment-specific mapping folder (sling:Folder) — /etc/, the etc mapping configurations won’t honor the run mode but it is possible to enable the environment-specific configuration by enabling different folders e.g, map.uat.publish, map.stage.publish, and and configure the folder to the run mode specific JCR Resolver configuration( “Apache Sling Resource Resolver Factory”).

Create a folder http or https(sling:Folder) under based on the protocol used to communicate to the publisher, use https even the SSL is terminated at load balancer level — the mapping details can be stored to the code repository for better management.

Remove the content mappings from “resource.resolver.mapping” property added in the earlier step and configure the resolver map location to “”

Enable the below Sling Mappings under /etc/ /http(s) based on the protocol used — this will enable the forward mapping(resolve), map the incoming URL to the content path(forward mapping is optional as the dispatcher is already sending the complete content path to the publisher) and reverse mapping (map) — map the content path to shortened DNS URL.

Now the forward and reverse mapping works as expected, validated the mapping through jcrresolver.

The shortened Domain URL also displayed to the internal page links.

The resolve and map methods of interface can be used to resolve/map the resources in java services/components.

Let us now enable some additional sling mappings

Resolve(Forward Mapping) the specific incoming URL to a different content path.

e.g the incoming request to the sitemap.xml file should be internally mapped to a different location where the file is located(under /content/wknd)

Create a node sitemap_mapping of type “sling:Mapping” under /etc/ and add the below properties

Now the request to sitemap.xml — displays the content from /content/wknd/sitemap.xml(enabled sample sitemap.xml file under /content/wknd)

Multiple forward mappings can be created as required for the specific domain.

Reverse Map the URLs to remove the .html extension from the page links

Let us now enable additional reverse mapping to remove the html extension from internal page links.

Create a node reverse_no_html of type “sling:Mapping” under /etc/ and add the below properties

Validate the mapping through jcrresolver

The shortened Domain URL without the html extension is now displayed to the internal page links.

Multiple reverse mappings can be created as required for the specific domain.

Enable external redirects for specific URL’s

Let us now enable an external redirect, redirect the request with string “test” to an external URL —

Create a node external_redirect of type “sling:Mapping” under /etc/ and add the below properties

sling:status – This property defines the HTTP status code sent to the client with the sling:redirect response. If this property is not set, it defaults to 302 (Found). Other status codes supported are 300 (Multiple Choices), 301 (Moved Permanently), 303 (See Other), and 307 (Temporary Redirect).

Now the URL will be redirected to

This concludes all the resource mapping scenarios, the completed Sling Mappings can be reviewed through the following URL— http://localhost:4503/etc/

The JCR package can be downloaded from the below link


The sling mapping helps us to map the incoming request to the internal content path and at the same time map, the internal content path to the complete DNS based shortened URL. This will enable the AEM platform to support multi-tenants and allows the author to cross-link the websites just through the content path(AEM automatically maps the content path to the domain URL)

Working as a Software Architect on Marketing Technologies. Reach out to me on Linkedin:

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store