AEM Pages movement which are in MSM - Recommendations | Community
Skip to main content
Level 3
October 18, 2021
Solved

AEM Pages movement which are in MSM - Recommendations

  • October 18, 2021
  • 3 replies
  • 2316 views

We are in process of migrating site to AEM. We are trying to figure  out the content (pages) structure in AEM and below is the multi site structure we are planning:

 

(Global International Core - Language Masters) - Blue Print

/content/LanguageMaster/internation_core/Products/tv

                                                                                         /washingmachine

                                                                                        /refrigerator.  

 

(Live copy from global international core -Language master) 

  /content/LanguageMaster/en_us/Products/tv

                                                                        /washingmachine

                                                                        /refrigerator

 

(Live copy from Language Master/en_us)

            /content/Sits/us/en_us/Products/tv

                                                                 /washingmachine

                                                                 /refrigerator

 

The Initial structure will be something like this, but In future there is plan to organise the pages in more specific where we have to introduce more levels in between or might need to move pages from one level to another and should be roll out across all.

 

I’ve tested below use case on AEM 6.5 + Service Pack 9:

 

Moved the page on Internation_core level (which is initial source of content) , the moment I moved source page using OOTB Move option from sites, a cq:LiveSyncConfig Node is created under /jcr:content of target page (in Live copy) and q:master & ca:moveTarget properties got added where we can see info of moved master path. 

 

Will there be problem of having additional cq:LiveSyncConfig nodes under target incase of source page movement?  Any performance issues due to additional cq:LiveSyncConfig nodes under Live copy level ? 

Is it advisable to move pages to introduce new categorisation which is already rolled out to multiple locales? 

Any issues with SEO side?

 

Looking for recommendations if any one has similar use cases in production? 

 

thanks in advance.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sanjay_Bangar

Hi @sonur1 ,

       Yes we don't have any issues while restructuring MSM but some times we got msm_moved issue faced.

Regards,

Sanjay

3 replies

Ankur_Khare
Community Advisor
Community Advisor
October 18, 2021

In my opinion- I don't see any issue with respect to movement causing any issue.

But for proper structuring do refer weretail or wknd site structure for locales and all-

 

 

SonuR1Author
Level 3
October 18, 2021

Thanks for the reply Ankur, Technically I don't see any challenges in moving but was thought of checking if any one has similar uses case on production so that we will come to know the challenges/limitations upfront and plan accordingly. 

Ankur_Khare
Community Advisor
Community Advisor
October 18, 2021

I have used MSM heavily in one of our projects thats why i don't feel any issue.

FYI The pages we rolled out were more than 5- 10 k.

Siva_Sogalapalli
Community Advisor
Community Advisor
October 18, 2021

The below link might be interesting to you and give some idea on content restructure: 

 

https://experienceleague.adobe.com/docs/experience-manager-65/administering/introduction/msm-best-practices.html?lang=en 

 

 

Also, it would be good to check on URLs redirection and retaining SEO ranking when you plan to move pages which are already in live.

Thanks

Sanjay_Bangar
Community Advisor
Sanjay_BangarCommunity AdvisorAccepted solution
Community Advisor
October 18, 2021

Hi @sonur1 ,

       Yes we don't have any issues while restructuring MSM but some times we got msm_moved issue faced.

Regards,

Sanjay

SonuR1Author
Level 3
October 18, 2021

Hi Sanjay,

Thanks for reply, which version of AEM were you using? 

 

Sanjay_Bangar
Community Advisor
Community Advisor
October 18, 2021

We were using 6.5.5