Solved

AEM Configuration and Troubleshooting

Forum|Forum|8 years ago
March 31, 2017
3 replies
1041 views

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.

Best answer by joerghoh

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

vjetty

Level 4

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!

MC_Stuff

Level 10

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,

joerghoh

Accepted solution

Adobe Employee

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

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded