Managing OSGi configurations and /system/console/configMgr access in AEM as a Cloud Service
This article describes the limitations of accessing and modifying OSGi configurations through /system/console/configMgr in Adobe Experience Manager as a Cloud Service and outlines the recommended approach for configuration management.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS) (all versions)
Issue/Symptoms
- Unable to access or modify OSGi configurations through
/system/console/configMgron managed Author and Publish environments. - Uncertainty about required permissions, configuration persistence, and recommended configuration management practices.
- Configuration changes made through
/system/console/configMgrdo not persist or are not reflected across all instances.
Cause
AEM as a Cloud Service treats application code and configuration as immutable at runtime. Adobe supports and recommends managing OSGi configurations through source control and deployment pipelines instead of modifying them through the Web Console at runtime.
Resolution resolution
Follow these steps to resolve the issue:
- Do not attempt to make OSGi configuration changes directly through
/system/console/configMgron managed Author and Publish environments because Adobe does not support this approach. - Maintain all OSGi configurations in source control as part of your codebase.
- Deploy configuration changes through the supported Cloud Manager deployment process to ensure consistency and persistence across all instances.
- Refer to the Configuring OSGi for Adobe Experience Manager as a Cloud Service documents for details about deploying and managing OSGi configurations.
recommendation-more-help
experience-cloud-kcs-help-kbarticles