JMX, A ton of stability increases. (Replication / Clustering / Platform / DataStore - see release notes), Removal of /var/dam for the DAM.
I'm sure others will chip in with their favourite related features.
Also worth noting from your maintenance perspective, CQ 5.4 has the following EOL shedule :
Available: 2/22/2011 EOL: 2/22/2014 Extended Support: 2/22/2016
Thanks for the quick response dcollie. Can you direct me to a page that has info about what JMX is and how it helps in increasing stability especially with Replication / Clustering?
1 person found this helpful
It doesn't help Stability in Replication / Clustering, all those types of fixes can be found in the release notes for CQ.
JMX provides a rich, defined interface that you can build Java Beans to manage and monitor your CQ instance, and create your own services that help in a Production environment to perform maintenance. CQ ships with some OOTB JMX MBeans.
Thanks dcollie for the additional info. I will go through them.
Yes I was going through the release notes for 5.6 and I see a huge list of fixes and a one line description of each. For instance the following ones I am interested upon.
GRANITE-1215 - Workflow Monitoring via JMX
CRX-4167 - Improved handling for backup procedure on ""listDir = /""
GRANITE-877 - Fixed ""Too many open files"" issue in monitoring
GRANITE-741 - Replication can handle missing content in the activation queue
GRANITE-1090 - Configure exclusion of publish instances for activation status updates
CRX-2943 - Cluster: Enable audit log on workspaces
But where can I find detailed information on each of these like what was the bug about and how is it fixed in the current release? To be precise, Im looking for some sort of KB article that discusses this information.
Any info that you can provide regarding this would be of great help.