Standard Rollout Configurations from old path do not get picked in AEM 6.4 | Adobe Higher Education
Skip to main content
PriyankaBiswal
PriyankaBiswal
Level 2
May 6, 2019

Standard Rollout Configurations from old path do not get picked in AEM 6.4

Hi Team ,

I am working on a migration project from AEM 6.0 to AEM 6.4 , where in we have used the OOTB AEM MSM functionality. Now as per documenation Adobe Experience Manager Help | Common Repository Restructuring in AEM 6.4 , it is not mandatory to move the Rollout Configurations from /etc/msm/rolloutConfigs , However AEM has moved the standard Rollout Configurations for e.g (/etc/msm/rolloutconfigs/default, /etc/msm/rolloutconfigs/activate, /etc/msm/rolloutconfigs/deactivate, /etc/msm/rolloutconfigs/pushonmodify) to their respective new locations i.e /libs/msm/wcm/rolloutconfigs/xxxx. AS a result of which the OOTB standard Rollout Configurations are not being picked in Rollout Configuration of LiveCopy Section of the Page properties and the page  Rollout is also NOT working for that matter.

Any Suggestion ? Apart from Running Content Migration Scripts to correct the property value of /jcr:content/cq:LiveSyncConfig/cq:rolloutConfigs .

Any kind of help is much appreciated.

Ce sujet a été fermé aux réponses.

1 commentaire

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
May 6, 2019

When we did the same migration from AEM 6.0 to AEM 6.4, we adjusted the path for our rollout configs to the new location, while leaving most of the other things still where they were on 6.4. Cleaning up this is planned for the next sprints.

Jörg

M
mohammedb397627
February 28, 2020

hello @joerghoh 

 

is there any documentation to make the custom rollout configs and custom live actions work.

I see that Adobe documentation is still based on /etc/msn where rollout configs are of type cq:page. instead /libs/msn/rolloutconfigs are cq:RolloutConfig

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
February 29, 2020

Please report such discrepancies in the documentation to support, so it can get fixed.

 

To address the issue you described: The only thing I can imagine is that you overlayed or customized some things based on AEM 6.0, which have changed with AEM 6.4, so that the overlays are not working properly anymore.

 

Have you run through the inline upgrade or did you start with a fresh AEM 6.4 instance and deployed your content and application on top of it via packages/grabit/...?

 

 

Conditions d'utilisationAccessibility statement

Loading footer...