System console configMgr is not accessible in higher environments | Community
Skip to main content
A
aem-enthu27
Level 4
March 17, 2022
Solved

System console configMgr is not accessible in higher environments

  • March 17, 2022
  • 2 replies
  • 1799 views

Hi ,

 

In AEM as a cloud service, system console configMgr access is not allowed, If this is the case then what is the point of OSGI configurations?

 

It is as goog as having constants rights? because we can not change the values directly from the console.

 

If I want to check any OSGI configuration values, How would I check ?

In my case I need to check 'Adobe Granite HTML Library Manager' OSGI configuration.

 

Thanks,

Ganesh

+91-9380201140

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

OSGI settings always were deployment settings, and you should version-control them.

 

Runtime settings should be set in different ways, e.g. using Context Aware Configuration.

2 replies

Himanshu_Jain
Community Advisor
Himanshu_JainCommunity Advisor
Community Advisor
March 17, 2022

Check from developer console .

Ref : https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/developing/development-guidelines.html?lang=en

 

 

Himanshu Jain
    A
    aem-enthu27Author
    Level 4
    March 17, 2022

    Yes, we can check it from developer console but we can't change the values.

    Then we can't call them as configurable anymore.

      joerghoh
      Adobe Employee
      joerghohAdobe Employee
      Adobe Employee
      March 17, 2022

      You have read-only access to certain functionality via the Developer Console, but never write access. This is by design to avoid adhoc changes, which are almost impossible to trace.

      If you want to change OSGI configuration, you have to deploy them via a run of pipeline.

        A
        aem-enthu27Author
        Level 4
        March 18, 2022

        What is the reason for blocking write operations ?

        That means OSGI configurations are as good as constants right?

          joerghoh
          Adobe Employee
          joerghohAdobe EmployeeAccepted solution
          Adobe Employee
          March 18, 2022

          OSGI settings always were deployment settings, and you should version-control them.

           

          Runtime settings should be set in different ways, e.g. using Context Aware Configuration.

            Terms & ConditionsAccessibility statement

            Loading footer...