AEM 6.5 Upgrade Part 1: Discovery and pattern detector analysis | AEM Community Blog Seeding

[kautuk_sahni]

AEM 6.5 Upgrade Part 1: Discovery and pattern detector analysis by Taqalytics

Abstract

AEM upgrade is a multi-step process that depends on scope of the upgrade and requirements defined in the discovery phase.

Adobe documentation has covered various steps on how to upgrade, but the code upgrade process itself isn’t discussed in much detail and is different for each project.

We will be covering a few topics related to code and customizations for the AEM 6.5 upgrade from the lower version.

List down the AEM Upgrade Scope and Requirements
During the discovery phase, identify key elements and make an inventory of existing code repositories. This list must have adobe standard requirements for upgrade and any custom requirements from the customer.

Here are some prerequisites to consider –

Technical requirements: Adobe supports Adobe Experience Manager (AEM) on the platforms as detailed in the following information – https://experienceleague.adobe.com/docs/experience-manager-65/deploying/introduction/technical-requirements.html?lang=en
List of AEM Components / Templates
Dialog conversion from classic to touch
OSGI and Declarative Services
Custom Application Services/REST API calls
POM structure and multi-module dependencies
Cq overlays
Workflows and Launchers
Foundation to core components
Static to editable templates
ACS commons dependency
Pattern Detector Analysis
Pattern Detector helps you to predict issues that are critical that would cause major issues down the line by giving warning messages during the upgrade process. It also helps you in closely monitoring certain aspects of the upgrade process.

Pattern Detector Analysis report are suggestions and improvements based on

Deprecated and removed features: Adobe constantly evaluates product capabilities, to over time reinvent or replace older features with more modern alternatives to improve overall customer value, always under careful consideration of backward compatibility.
Content Repository restructuring: Content is being restructured out of /etc to other folders in the repository. AEM product code will always be placed in /libs, which must not be overwritten by custom code. Custom code should be placed in /apps, /content, and /conf
Adobe’s recommendation for Best Practices: Deploying best practices describe how to deploy or maintain AEM in the most efficient and most effective way possible
Good luck on your Upgrade!

Are you thinking about upgrading the existing AEM environment? Taqalytics would love to help. Please touch base with us at https://taqalytics.com/contact/

References:

https://www.tothenew.com/blog/how-to-upgrade-existing-code-base-to-latest-aem-version/

https://experienceleague.adobe.com/docs/experience-manager-65/release-notes/deprecated-removed-features.html?lang=en

Read Full Blog

AEM 6.5 Upgrade Part 1: Discovery and pattern detector analysis

Q&A

Please use this thread to ask the related questions.