Skip to main content
Jun 17, 2021 3:41 AM UTC
Solved

Pattern Detector from AEM 6.2 to 6.5

Hi all,

I am planning to upgrade 6.2 to 6.5. Just want to estimate how much effort need in code merging. May I know is there any package/Pattern Detector to identify the deprecated api, code , function from 6.2 for 6.5.

 

Thank you all.

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Asutosh_Jena_
Asutosh_Jena_Accepted solution
Community Advisor
Jun 17, 2021 6:38 AM UTC

Hi @aries-1 

 

Yes you can use the Pattern Detector tool which is provided by Adobe.

This feature allows you to check existing AEM instances for their upgradability by detecting patterns in use that:

  1. Violate certain rules and are done in areas that will be affected or overwritten by the upgrade
  2. Use an AEM 6.x feature or an API that is not backwards compatible on AEM 6.5 and can potentially break after upgrade.

You can download it from here:

https://experience.adobe.com/#/downloads/content/software-distribution/en/aem.html?package=/content/software-distribution/en/details.html/content/dam/aem/public/adobe/packages/cq650/compatpack/pd-all-aem65

and it should be installed on your Source instance i.e. 6.2 AEM instance.

 

Thanks!

2 replies

Bhuwan_B
Community Advisor
Community Advisor
Jun 17, 2021 3:59 AM UTC

@aries-1 Please refer to below documentation URL:

https://experienceleague.adobe.com/docs/experience-manager-65/deploying/upgrading/pattern-detector.html?lang=en

The Pattern Detector is released separately as a one package working on any source AEM versions from 6.1 to 6.5 targeting AEM 6.5 upgrade. It can be installed using the Package Manager.
Translate
Asutosh_Jena_
Community Advisor
Asutosh_Jena_Community AdvisorAccepted solution
Community Advisor
Jun 17, 2021 6:38 AM UTC

Hi @aries-1 

 

Yes you can use the Pattern Detector tool which is provided by Adobe.

This feature allows you to check existing AEM instances for their upgradability by detecting patterns in use that:

  1. Violate certain rules and are done in areas that will be affected or overwritten by the upgrade
  2. Use an AEM 6.x feature or an API that is not backwards compatible on AEM 6.5 and can potentially break after upgrade.

You can download it from here:

https://experience.adobe.com/#/downloads/content/software-distribution/en/aem.html?package=/content/software-distribution/en/details.html/content/dam/aem/public/adobe/packages/cq650/compatpack/pd-all-aem65

and it should be installed on your Source instance i.e. 6.2 AEM instance.

 

Thanks!

Translate