Maintenance activities for AEM 6.x

 

Maintenance activities for AEM 6.x

 

AEM project management is very crucial activity as lack of maintenance causes instability, performance issues and disk space outages.

 

The following factors influence performance problems in AEM:

·         Improper design

·         Application code

·         Lack of caching

·         Bad disk I/O configuration

·         Memory sizing

·         Network bandwidth and latency

·         AEM installed on some select windows 2008 and 2012 version where memory management is an issue

·         Modifying out-of-the-box configurations as described below can help improve performance in AEM

 

 

Following activities need to be scheduled for proper maintenance:

·         Install the recommended AEM service packs, cumulative fix packs and hot fixes.

 

·         Revision Cleanup – Persistance layer writes data to tar files under crx-quickstart/repository/segmentstore. Over time, this can affect performance and stability of AEM. To reclaim disk space and improve performance, you need to run online tar compaction.

 

·         Workflow Purge Maintenance - Whenever a workflow is started in AEM, a workflow history is created under /etc/workflow/instances in the Oak repository.  Over time, workflow history nodes can pile up and affect system performance.  To avoid this situation, you need to run Workflow Purge Maintenance.

 

·         Version Purge Maintenance - Versions are created when you publish or unpublish pages or assets, upload or replace assets.  Versions are stored as nodes under /jcr:system/jcr:versionStorage in the Oak repository. To reclaim the disk space and gain back system performance you need to run Version Purge.

 

·         Lucene Binaries Cleanup - By using the Lucene Binaries Cleanup task, you can purge lucene binaries and reduce the running data store size requirement.

You can access the Lucene Binaries Cleanup task from: AEM > Tools > Operations > Maintenance > Daily Maintenance Window > Lucene Binaries Cleanup.

 

·         Audit Log Purge maintenance - Audit logs are stored as nodes under /var/audit in the Oak repository.  Over time, these nodes pile up and affect system performance.  To avoid that situation you need to run Audit Log Maintenance.

·         Request.log - This is very vital tool if you want to analyze the request time for various requests. It would help you know which request is taking max time and how often the request is occurring with max time. Request logs are stored at crx-quickstart\logs

 

·         Disk Usage – Goto this link http://localhost:4502/etc/reports/diskusage.html and you will find which folder is taking the maximum space.

    

 

·         JMeter - A 100% pure Java application designed to load test functional behavior and measure performance. It was originally designed for testing Web Applications but has since expanded to other test functions.

 

·         AEM In-built Profiler - This is OOTB provided by AEM

References:

https://helpx.adobe.com/in/experience-manager/kb/AEM6-Maintenance-Guide.html