What is the process of running AEM 6.5 LTS Analyzer to check readiness of my system for upgrade?

[Rajumuddana]

Hi All,

I need to check readiness of my AEM applications/code to upgrade to AEM 6.5 LTS by running AEM 6.5 LTS Analyzer.

I have gone through this page https://experienceleague.adobe.com/en/docs/experience-manager-65-lts/content/implementing/deploying/... and understand that analyzer tool would generate a report which prepares issues from different categories

• Application functionality that must be refactored
• Repository items that must be moved to a supported location
• Configuration issues
• AEM 6.5 features that have been removed by new functionality or that are currently not supported on AEM 6.5 LTS
• Remove Java and Guava API usage

later, there is another section talking about 'Content Transformer', what i understood from this is, it removes/delete typically JCR nodes by packaging under '/etc/packages/modernizer-content-transformation' as a backup, but the goal (checking readiness) is not fulfilled yet, I wonder what will be the next steps?

Need to go through individual items in analyzer report and do appropriate correction manually?

or how it goes?

Thanks,

Raju.

[giuseppebag]

hi @Rajumuddana,

the Analyzer highlights what needs fixing, Content Transformer helps partially clean up, but manual refactoring and thorough testing are essential next steps to complete your upgrade readiness for AEM 6.5 LTS.

Here are the typical steps for upgrading:

1. After running the Analyzer on your AEM instance, you get a detailed report highlighting:

   • Application functionality that needs refactoring.

   • Repository items to relocate.

   • Configuration issues.

   • Deprecated or removed AEM 6.5 features.

   • Java and Guava API usage that should be removed.

2. Content Transformer

   • It is bundled with the Analyzer and automates cleanup tasks like removing or relocating deprecated JCR nodes.

   • It creates backup packages under /etc/packages/modernizer-content-transformation before changes.

   • This step is partly automated remediation based on Analyzer findings but does not cover all upgrade readiness requirements.

3. Manual Review and Fixes Are Needed

   • The Analyzer and Content Transformer assist with identification and partial cleanup but do not fully automate the upgrade.

   • You must review the Analyzer’s findings carefully.

   • You should manually refactor code and configuration for any compatibility issues.

   • Test thoroughly for removed or changed APIs and features.

You can find all the necessary steps for a complete upgrade on the left sidebar of the official documentation page. I recommend following the order suggested by Adobe.

Summary Table

Phase	Role	Tool/Action
Assessment	Identify upgrade blockers and deprecated usage	AEM 6.5 LTS Analyzer
Partial Cleanup	Apply content/node removals with backup	Content Transformer
Manual Refactoring & Fixes	Code and configuration remediation based on findings	Developer review & fixes
Verification	Validate fixes with repeated analysis	Rerun Analyzer
Testing & Deployment	Ensure stability and compliance on upgraded AEM	QA & regression testing

[Rajumuddana]

Hi @giuseppebag ,

Thanks for your detailed explanation.

As I’m continuing my quest i referred

• https://experienceleague.adobe.com/en/docs/experience-manager-65-lts/content/implementing/deploying/...
• https://experienceleague.adobe.com/en/docs/experience-manager-65-lts/content/implementing/deploying/...,

and i have a question,

1. To upgrade to AEM 6.5 LTS from AEM 6.5.x, do we need to setup new environments with Java 17 or 21 (as my current application/system is on Java11), as the new(AEM 6.5 LTS) system is built on top of 6.5 LTS Uber jar?

Thanks,

Raju.

[Lokesh_Vajrala]

@Rajumuddana  You don't need to setup new environments for Java upgrade. You can install Java 21 on existing environments/hosts along with Java 11 and update the JAVA_HOME or other property you're using to point to Java 21. 

[AEM_Dan]

I have similar questions about the analyzer.  It seems like it's just identifying obsolete bundles (listed here: https://experienceleague.adobe.com/en/docs/experience-manager-65-lts/content/implementing/deploying/...) and removed jcr paths that exist in the system.  Not necessarily ones being utilized in custom code.  Is that right?

I'm not sure how to line that up with our code.  Maybe just stop those bundles and test?