Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

AEM Run mode

Avatar

Level 2

Hi Everyone,

AEM Run modes configurations are not reading correctly after updating them in the configuration, any idea what's going wrong?

Appreciate your help.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @radhika_k ,

When you configure the component configurations manually in the edit dialog  - the AEM creates another configuration node that has priority over pre defined configurations & those configurations are placed in /apps/system/config - it contains properties those you set in edit dialog. Please delete that and verify.

For more details here I have demoed real time scenario through video please go through it: https://www.techinnovia.com/run-modes/

Hope that helps!

Regards,

Santosh

View solution in original post

6 Replies

Avatar

Community Advisor

Hi,

 

There are different ways to setup the runmode to instance, please check below link for the ways and precedence

https://www.aemcq5tutorials.com/tutorials/set-up-run-modes-in-aem/

 

Avatar

Community Advisor

Hello @radhika_k ,

 

What AEM version are you using? For AEM as cloud service, the supported runmodes are dev, stage and prod. If a custom run mode for eg 'sqa' is set, that won't be recognized.

 

If not, can you provide more details on what was attempted and the issue?

 

Please check these out - https://www.aemtutorial.info/2020/07/faq-on-aem-as-cloud-service.html and https://blog.developer.adobe.com/custom-runmodes-on-aem-as-a-cloud-service-79b757f51a6b

 

Thanks

 

 

Avatar

Level 2

@Shubham_borole @Ravi_Pampana Thanks for your response, to add to your question - When configuration are deployed through code base it is not picking up the deployed configuration rather it is picking up the old which we had configured through configuration (/system/console)

Deployment is successfully done double checked everything.

Avatar

Correct answer by
Community Advisor

Hi @radhika_k ,

When you configure the component configurations manually in the edit dialog  - the AEM creates another configuration node that has priority over pre defined configurations & those configurations are placed in /apps/system/config - it contains properties those you set in edit dialog. Please delete that and verify.

For more details here I have demoed real time scenario through video please go through it: https://www.techinnovia.com/run-modes/

Hope that helps!

Regards,

Santosh

Avatar

Community Advisor

Hi @radhika_k 

Run modes precedence is differ from where they are applied from.

Refer below thread for the same.

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/order-of-precedence-of-sli...

Hope this is helpful.