Skip to main content

AEM 5.6 to 6.1 Upgrade

AEM upgrade - CQ 5.6.1 to AEM 6


Prerequisites
•        You must have new AEM 6.X installation jar
•        Create a production Server Replica with similar content and configurations to existing CQ 5.6.1 environment so that you can test the upgrade changes.
•        Create a seperate new Code branch for 6.X code.
•        Make performance testing scripts ready .


Steps to Upgrade
1.      Repository Upgrade
AEM 6.1 doesn't support crx2 and requires content migration to Oak repository.
There are several ways to do it
Package deployment. – If repository volume is not too high (up to 30 GBs), package deployment is the most easy and simple way to migrate content.
Use crx2oak tool - Use this if content volume is high. Will cover steps for this tool in another post. For this post I'll assume that repository migration is done using packages.

2.      Cleanup before starting the upgrade
•        Backup and delete workflow launchers and sling Jobs - This will prevent workflows and jobs from getting triggered during the upgrade process. Deploy the backup package after the
•        Remove version history - This will reduce the number of nodes that needs to be processed during the upgrade.
•        Data Store garbage collection- It will reduce the disk space.
Clean up any other unused data from repository.
•        Disable custom login modules
 
3.      Java Upgrade
Upgrade to JAVA8 for optimized performance with AEM 6.X

4.      Hot fixes
Find the exhaustive list of hotfixes at below links, and install required the hotfixes.
 
5.      Code base changes
Remove deprecated APIs
Check your code base and see if you are using any APIs listed in above links and replace them with their alternative APIs.
Resource resolver API changes – Using admin resolver is deprecated in AEM 6 and we should use Service Resource Resolver API in 6.X to get the session. Below is the link which talks about getting service resource resolver in AEM 6-
 
6.      Indexing
AEM 6 doesn't automatically index the whole content like old versions.
Logs needs to be reviewed for indexing warnings.
Use AEM explain query tool to analyze queries you are using in code base.

 

Comments

Post a Comment

Popular posts from this blog

AEM 6.3 - How to extend Granite UI

Here in this article, I am going to explain how to extent Granite UI that is basically used to create AEM 6.x consoles. There can be various use cases where in you may need that. In our case, author wants to take all the page creation requests through AEM instead of email communication. Authors are basically looking for a form in AEM authoring console so that requestor can login and submit page creation/Asset upload request. Overall requirement is - Need a link in Navigation so that author can click on it and go to a Intake form. Author must be able to fill and save the intake requests. Author must be able to see the history of submitted intake requests Able to see the details of submitted intake requests. Solution - 1. Create a following structure - /apps/cq/core/content/nav/form and add the details given in below screenshot - You basically need to add - href, title and icon. Href is the path of page where user will land on clicking it.  Af...
Post a Comment
Read more

CQ Page Properties from Javascript

To get CQ page properties inside javascript you can use core CQ JS API. It can be convenient if you need to get this information inside your custom JS widgets.              var pageData = CQ.HTTP.get(CQ.HTTP.externalize(CQ.utils.WCM.getPagePath() + "/jcr:content.json")); After that you can retrieve any property you need (assuming it's present in JCR):              var resourceType = pageData ? CQ.Util.formatData(CQ.HTTP.eval(pageData))['sling:resourceType'] : null; Please do not overuse it because it invokes additional ajax call to server. It's OK to use it in edit mode on author instance. Copied from -  http://adobecms.blogspot.com/2014/04/cq-page-properties-in-javascript.html
Post a Comment
Read more

AEM 6.3 - Check if page is published or not

If you want to know if the page is published or not you can use the below utility method to know if the page is published or not. Steps - Take Resource Object. Adapt it to Page Adapt page to ReplicationStatus, you will get the status Here is the code - public static Boolean isPublished(Resource resource) { Boolean activated; ReplicationStatus status = null; activated = false; if (resource != null) { try { Page page = resource.adaptTo( Page.class ); status = page.adaptTo( ReplicationStatus.class ); } catch (Exception e) { LOG.debug(e.getMessage (), e); } if (status != null) { activated = status.isActivated(); } } return activated; }
Post a Comment
Read more