Default Configuration of Root Mapping
In Adobe AEM, when you hit http://<host>:<port>/ by default it is redirected to
Author: /projects.html (AEM 5.6.1 and above)
How it works ?
“com.day.cq.commons.servlets.RootMappingServlet” – is responsible to redirect to the set root URL configure using the property called “rootmapping.target”
If you go to http://<host>:<port>/system/console/configMgr in each of the instance, you would see the above mentioned paths and hence the behaviour.
In author instance its straight forward but if you see publish instance, though its configured as ‘/content.html’ it redirects to ‘geometrixx-outdoors’ hompage reason being the 2 properties which is set for the node ‘/content’.
sling:resourceType as sling:redirect and
sling:target as /geohome (/geohome is the vanityURL for /content/geometrixx-outdoors)
How to change ?
Most likely, we would want to change the root mapping from /geohome to our own application in the publish instance and the same can be done in below mentioned ways
We know, in publish instance root mapping is set to /content.html. So go to /content node in crx de. Change the URL for the property sling:target to map to your own application content node and save. Package the same from the author instance and deploy it on the publish instance.
Note: when you package it and add the /content as the filter, make sure you add ‘exclude’ rule as ‘/content/*’ so that it doesnt include the child pages of the content node.
Login to the config manager console directly either in author or publish which you want to change, search for ‘Day CQ Root Mapping’ and change the ‘Target Path’ and click on Save. Next time when you access instance, it should redirect to the configured path.
custom config :
- Create /apps/<projectname>/config.<runmode>/com.day.cq.commons.servlets.RootMappingServlet (runmode = author or publish)
- Add a property rootmapping.target with value equal to home page path.
- Activate or deploy /apps/<projectname>/config.<runmode>/com.day.cq.commons.servlets.RootMappingServlet
Refer OSGi Configuration to understand how to create the config files for each runmode
This approach would be best as it does not need any manual configuration across your instances and it get deployed to any instance as part of your project deployment.