System console configMgr is not accessible in higher environments | Community
Skip to main content
aem-enthu27
Level 4
Mar 17, 2022 8:55 AM UTC
Solved

System console configMgr is not accessible in higher environments

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.
joerghoh
joerghohAccepted solution
Employee
Mar 18, 2022 10:06 AM UTC

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.

View reply

6 replies

joerghoh
joerghoh
Employee
Mar 17, 2022 11:50 AM UTC

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.

Translate
    aem-enthu27Author
    Level 4
    Mar 18, 2022 5:17 AM UTC

    What is the reason for blocking write operations ?

    That means OSGI configurations are as good as constants right?

    Translate
      joerghoh
      joerghohAccepted solution
      Employee
      Mar 18, 2022 10:06 AM UTC

      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.

      Translate
        Himanshu_Jain
        Himanshu_Jain
        New Participant
        Mar 17, 2022 9:16 AM UTC

        Check from developer console .

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

         

         

        Translate
        Himanshu Jain
          aem-enthu27Author
          Level 4
          Mar 17, 2022 10:07 AM UTC

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

          Then we can't call them as configurable anymore.

          Translate
            Terms & ConditionsAccessibility statement

            Loading footer...