Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

http://localhost:4503/editor.html/content/geometrixx/en.html

Avatar

Level 4

Hi,

When we start publish instance how http://localhost:4503/editor.html/content/geometrixx-outdoors/en.html is displayed. Where it is configured ?

1 Accepted Solution

Avatar

Correct answer by
Administrator

HI 

Please refer to this community article written by Lokesh :- 

Link:- http://adobeaemclub.com/root-mapping-configuration-in-adobe-aem/

Root Mapping Configuration in Adobe AEM

//

In Adobe AEM, when you hit http://<host>:<port>/ by default it is redirected to

Author: /projects.html (AEM 5.6.1 and above)

Publish: /content.html


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.

RootMapping Author

RootMapping Author

RootMapping Publish

RootMapping Publish

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

/content :

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.

Package Manager Filter

Package Manager FilterconfigMgr :

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.

More Reference Articles:- 

Link:- http://cq-ops.tumblr.com/post/17381263969/how-do-i-configure-my-own-site-and-not-geometrixx

Link:- http://teknopoint.us/change-start-page-cq5-projects-welcome/

Link:- http://cq-ops.tumblr.com/post/17381263969/how-do-i-configure-my-own-site-and-not-geometrixx

//

How do I Configure My Own Site and not Geometrixx as the Default Site?

In CQ 5.4, the publish instances always load up the /geometrixx website by default if you point your browser at http://server:4503

If you have created your own site and want that one to be the default, there are some tricky things you have to do.

1) In the CQ “author” instance, using CRXDE Lite, navigate to /content and highlight it

2) Set the sling:target property to the root of your website.  Eg: /content/mywebsite/en

3) Click the ‘Save All’ buton (top left) to save the change.

4) Exit CRXDE Lite

5) In CQ\Websites, highlight the root folder (\Websites), and hit the 'Activate’ button.

6) Verify with the CQ “publish” instance (http://server:4503) that what loads up is your website and not geometrixx.

P.S.  You can also try navigating to /libs/cq/core/config.publish/com.day.cq.commons.servlets.RootMappingServlet and changing the rootmapping.target property.

 

 

I hope this would help you.

Thanks and Regards

Kautuk Sahni

View solution in original post

0 Replies

Avatar

Correct answer by
Administrator

HI 

Please refer to this community article written by Lokesh :- 

Link:- http://adobeaemclub.com/root-mapping-configuration-in-adobe-aem/

Root Mapping Configuration in Adobe AEM

//

In Adobe AEM, when you hit http://<host>:<port>/ by default it is redirected to

Author: /projects.html (AEM 5.6.1 and above)

Publish: /content.html


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.

RootMapping Author

RootMapping Author

RootMapping Publish

RootMapping Publish

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

/content :

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.

Package Manager Filter

Package Manager FilterconfigMgr :

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.

More Reference Articles:- 

Link:- http://cq-ops.tumblr.com/post/17381263969/how-do-i-configure-my-own-site-and-not-geometrixx

Link:- http://teknopoint.us/change-start-page-cq5-projects-welcome/

Link:- http://cq-ops.tumblr.com/post/17381263969/how-do-i-configure-my-own-site-and-not-geometrixx

//

How do I Configure My Own Site and not Geometrixx as the Default Site?

In CQ 5.4, the publish instances always load up the /geometrixx website by default if you point your browser at http://server:4503

If you have created your own site and want that one to be the default, there are some tricky things you have to do.

1) In the CQ “author” instance, using CRXDE Lite, navigate to /content and highlight it

2) Set the sling:target property to the root of your website.  Eg: /content/mywebsite/en

3) Click the ‘Save All’ buton (top left) to save the change.

4) Exit CRXDE Lite

5) In CQ\Websites, highlight the root folder (\Websites), and hit the 'Activate’ button.

6) Verify with the CQ “publish” instance (http://server:4503) that what loads up is your website and not geometrixx.

P.S.  You can also try navigating to /libs/cq/core/config.publish/com.day.cq.commons.servlets.RootMappingServlet and changing the rootmapping.target property.

 

 

I hope this would help you.

Thanks and Regards

Kautuk Sahni