Skip to main content
kurtl91408195
Mar 31, 2017 7:25 PM UTC
Solved

AEM Configuration and Troubleshooting

What's on the horizon for debugging of configuration issues in an AEM instance? Say your facility has more than a single AEM instance and the current health checks don't reveal what's changed in the instance state. Is there any type of audit trail, utility or technique that can track what's changed (configuration wise) to an AEM instance?

    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
    Adobe Employee
    Apr 1, 2017 7:24 PM UTC

    Hi,

    You should not change the configuration of production instances manually, but only through content packages (holding the OSGI configuration). Build this package by your regular build jobs out of a content repository, then you can be sure that the configuration is versioned and reproducible.

    Jörg

    View in thread

    3 replies

    vjetty
    vjetty
    Level 4
    Mar 31, 2017 8:58 PM UTC

    Hi Kurtl

    Do you mean you want check what felix configurations have been changes and when? If this is the case you can check the access.log of your aem server. It give you who changed what configuration and when. 

    hope this helps! 

    Translate
    MC_Stuff
    MC_Stuff
    Level 10
    Apr 1, 2017 6:57 AM UTC

    Hi,

    On every release store the status configuration. Then make use of [A] to compare. More details at http://www.aemstuff.com/blogs/nov/osgiconfigcompare.html

    [A] http://www.aemstuff.com/tools/osgiconfigdiff.html

    Thanks,

    Translate
    joerghoh
    Adobe Employee
    joerghohAdobe EmployeeAccepted solution
    Adobe Employee
    Apr 1, 2017 7:24 PM UTC

    Hi,

    You should not change the configuration of production instances manually, but only through content packages (holding the OSGI configuration). Build this package by your regular build jobs out of a content repository, then you can be sure that the configuration is versioned and reproducible.

    Jörg

    Translate
      Terms & ConditionsAccessibility statement

      Loading footer...