As we all know, there are two upgrade paths from CQ5.3 to CQ5.4.
1. Upgrading the jar file - This is the usual upgrade path but comes with its own challenges.
2. Fresh installation – I prefer this most of the time if version history is not very important.
Recently, we did an upgrade (i.e. replacing the jar file) for one of our customers moving from CQ5.3 to CQ5.4. One of the issue we faced was ‘Internal server error’ in CRX explorer, and other inconsistencies in CRX like package manager not showing the list of packages and overall slowness of the system.
So, the first thing we did was “cleanup” – which I would recommend for any CQ5.4 upgrades.
Here are the steps:
1. Re-build the crx runtime directory
- Stop the server
- Delete CRX runtime directory: /crx-quickstart/server/runtime/0/_crx
- Delete the contents inside tmp folder /crx-quickstart/server/tmp
- Start the server.
- Go to Felix console http://host:port/system/console and verify all bundles are in ‘Active’ state. If any of the bundles are in ‘Resolved’ or ‘Installed’ state, start them manually.
2. Delete all the class files (under /var/classes/org/apache)
- Go to Content explorer: http://host:port/crx/index.jsp and delete the “jsp” folder shown below:
Don’t forget to hit the ‘Save All’ icon on top left corner.
Have you recently upgraded from 5.3 to 5.4 and want to share your experience, please leave a comment below. To keep it relevant, lets talk only about the overall product upgrade experience excluding the custom developed components/templates.
Comments