OSGI Configuration: nt:file or sling:OsgiConfig | Community
Skip to main content
S
SupportMember
Level 6
March 11, 2020
Solved

OSGI Configuration: nt:file or sling:OsgiConfig

  • March 11, 2020
  • 3 replies
  • 4012 views

I've seen OSGI configurations use as nt:file or sling:OsgiConfig interchangeably. What the best practice? Why is nt:files used? Are. there any other variations?

Why does core components. follow the nt:file pattern, /apps/core/wcm/config.author/com.day.cq.wcm.foundation.forms.impl.FormParagraphPostProcessor-core-components.config?

Why does we-retail follow the sling:OsgiConfig pattern, /apps/weretail/config/org.apache.sling.commons.log.LogManager.factory.config-we-retail?

    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

    There are now a few ways how you can configure OSGI configurations via the repository: Using sling:osgiConfig nodes, using an nt:file with the properties (in a ini-style format), and there is/will be a JSON variant ...

     

    In the end it doesn't matter which one to use; when you are going to edit it in the IDE and store it in GIT, dropping a file is probably the easiest because you don't have the overhead of XML (as you have in the case of using sling:osgiConfig). Storing it as JSON is part of the latest AEM versions, so not yet widespread, thus I wouldn't recommend it today for general use.

     

    regards

    Jörg

    3 replies

    arunpatidar
    Community Advisor
    arunpatidarCommunity Advisor
    Community Advisor
    March 12, 2020

    If you are creating repository based config then use sling:OsgiConfig

    If you want to manage configurations using web console then you can use nt:file.

     

    As soon as you update sling:OsgiConfig type config from web console, it converts into nt:file.

     

     

     

    Arun Patidar
      joerghoh
      Adobe Employee
      joerghohAdobe EmployeeAccepted solution
      Adobe Employee
      March 13, 2020

      There are now a few ways how you can configure OSGI configurations via the repository: Using sling:osgiConfig nodes, using an nt:file with the properties (in a ini-style format), and there is/will be a JSON variant ...

       

      In the end it doesn't matter which one to use; when you are going to edit it in the IDE and store it in GIT, dropping a file is probably the easiest because you don't have the overhead of XML (as you have in the case of using sling:osgiConfig). Storing it as JSON is part of the latest AEM versions, so not yet widespread, thus I wouldn't recommend it today for general use.

       

      regards

      Jörg

        U
        Adobe Employee
        user05162Adobe Employee
        Adobe Employee
        March 16, 2020

        Sharing the doc[1] where everything is explained in detail.

         

        [1] https://docs.adobe.com/content/help/en/experience-manager-65/deploying/configuring/configuring-osgi.html

          Terms & ConditionsAccessibility statement

          Loading footer...