how to view/modify OSGi configs in cloud, as /system/console/configMgr is blocked? | Community
Skip to main content
T
TB3dock
Level 8
May 7, 2021

how to view/modify OSGi configs in cloud, as /system/console/configMgr is blocked?

  • May 7, 2021
  • 5 replies
  • 5105 views

We have built our app to be configurable via OSGi configurations, which is th AEM way.

This works great locally against the cloud SDK.

However, when we deploy to the cloud, the configMgr seems to be blocked.  This means we cant edit any of the critical run time variables, such as timeouts, switching features on off etc.

This is a huge problem. It would mean we have to re-write our services to read config from pages of the CMS or similar, which is a significant re-write.

Is there any work around to being able to view and edit our OSGi configs at runtime?

Adobe MUST remove these features from the cloudSDK if they are not available on any cloud env, otherwise we are developing for a completely different system.  this also includes the excellent i18n translation system, which is now removed on the cloud, but is still present in the SDK. This also required a significant rewrite, and is a very poor solution now.

 

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

5 replies

Pawan-Gupta
Pawan-Gupta
Level 8
May 7, 2021

i don't think there is anything apart from trying through curl. refer below if it works for you.

 

https://sourcedcode.com/blog/aem/tool-generate-curl-command-to-update-osgi-configurations

    arunpatidar
    Community Advisor
    arunpatidarCommunity Advisor
    Community Advisor
    May 8, 2021

    curl will also not work because it will try to save config inside /apps/ which is immutable

    Arun Patidar
      Asutosh_Jena_
      Community Advisor
      Asutosh_Jena_Community Advisor
      Community Advisor
      May 8, 2021

      Hi @tb3dock 

       

      As per AEM as Cloud service, all content and code persisted in the immutable repository must be checked into git and deployed through Cloud Manager.

      As an example, OSGI configuration should be committed to source control rather than managed at runtime via the AEM web console’s configuration manager.

       

      So you need to make the necessary changes on the developer’s local AEM environment with the AEM web console’s configuration manager and then exporting the results to the AEM project on the local file system. You need to ensure all the OSGi configurations are verified on local environment and commited to source control.

       

      If you want to keep any functionality that needs to be updated during runtime, you can keep those as part of Context aware config which will reside under /conf and can be updated during runtime.

       

      As you said the Cloud and local SDK are not in sync which is really an issue but if we are working on AEM as Cloud environment we need to ensure we follow the concept of mutable and immutable section in AEM and design the application accordingly to overcome these challenges during development.

       

      Please refer the below article which speaks about the different ares of AEM with mutable and immutable concept:

      https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/aem-project-content-package-structure.html?lang=en#mutable-vs-immutable

      https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/developing/basics/mutable-immutable.html?lang=en#developing

       

      Hope this helps!

      Thanks

        T
        TB3dockAuthor
        Level 8
        May 8, 2021
        Hi, for osgi configs, we have not seen a way to export them to file. It is generally very difficult to figure out exactly what the file name should be, and what the contents need to be to match a config setup in the configmgr, sometimes taking days of trial and error.
          Prince_Shivhare
          Community Advisor
          Prince_ShivhareCommunity Advisor
          Community Advisor
          May 8, 2021

          Yes, we cannot do any changes related to config manager in higher environment.

          We can push it  only by code repo.

          however you can verify it by developer console and select option as a text.

          and search the config name.

           

          Thanks,

          Prince

            Ritesh_Mittal
            Community Advisor and Adobe Champion
            Ritesh_MittalCommunity Advisor and Adobe Champion
            Community Advisor and Adobe Champion
            May 8, 2021
             

            Hi @tb3dock ,

             

            I do not think there is a way (only through GIT) as per documentation-

             

            https://experienceleague.adobe.com/docs/experience-manager-cloud-service/release-notes/aem-cloud-changes.html?lang=en#osgi

              arunpatidar
              Community Advisor
              arunpatidarCommunity Advisor
              Community Advisor
              May 8, 2021

              You can view the OSGi config from the cloud manager but there is no way to modify it manually in order to prevent inconsistency among instances.

              Arun Patidar
                T
                TB3dockAuthor
                Level 8
                May 8, 2021
                Hi, when I try to view the /system/console/configMgr on any of our cloud instances, it gives 403, even though I am logged in and can see the crxde console, and have all admin permissions, including admin of the Adobe subscription.
                  Terms & ConditionsAccessibility statement

                  Loading footer...