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
Context Aware Configuration - is it even being used? and what kind of information would we like to store?
Hello @AEMWizard
Content-aware configurations are an easy way to store configs that dependent on page hierarchy. Specially if a customer has multiple sites on AEM, it can be really useful to drive site-specific configs.
1. Are you even using this feature with AEM? - Yes. In multiple projects
2. I'm very use to AEM OSGI configurations, which configuration for each env can be used for our backend services, but like Context Aware Configuration is not by environment... so how can this be useful?
OSGi
- OSGi is a good option, when some is runmode driven. Or a config thats applicable for an entire/all env.
- It is recommended to be deployed via code base.
- In case of AEM as a cloud service, you need deployment to update OSGi configs
Context-aware configs:
- the configurations can easily be accessed/updated/maintained by authors via Content-aware pages
- Since, they are created at the same level in hierarchy, where they are supposed to take effect, its easy understand.
- Good way to maintain site specific configs
3. Can you please give me a scenario for what kind of configuration we would store in the Context Aware Configuration
- Covered in the above comments
Aanchal Sikka
