An AEM application has a Header and Footer authored on every page.
The customer asks for the following:
1. A centralized Header and Footer
2. The ability to create a variation for both the Header and Footer
3. Change the Header and Footer for specific time periods
4. The ability to restore a previous version for both the Header and Footer
What should the developer use to meet the requirements?
For AEM as a Cloud Service, the correct format to use for OSGi configuration files is .cfg.json. This format is specifically designed for use in AEM as a Cloud Service and supports both structured and unstructured data, making it versatile for various configuration needs.
Steps to create and deploy OSGi configurations in .cfg.json format:
Create Configuration File: Create a .cfg.json file in your codebase, typically under the apps directory, for example:
/apps/myproject/config/org.apache.sling.commons.log.LogManager.cfg.json
Define Configuration: Add your configuration properties in JSON format:
{
'org.apache.sling.commons.log.level': 'debug',
'org.apache.sling.commons.log.file': 'logs/error.log'
}
Deploy to AEM: Deploy the configuration along with your code package to AEM as a Cloud Service. The configuration will be applied automatically.
Minna
3 days ago