ÃÛ¶¹ÊÓƵ

Upgrading to ÃÛ¶¹ÊÓƵ Experience Manager (AEM) 6.5 upgrading-to-aem

This section covers upgrading an AEM installation to AEM 6.5:

For easier reference to the AEM instances involved in these procedures, the following terms are used throughout these articles:

What Has Changed? what-has-changed

The following are major changes of note over the last several releases of AEM:

AEM 6.0 introduced the new Jackrabbit Oak repository. Persistence Managers were replaced by Micro Kernels. Starting from version 6.1, CRX2 is no longer supported. A migration tool called crx2oak must be run to migrate CRX2 repositories from 5.6.1 instances. For more information, see Using the CRX2OAK Migration Tool.

If Assets Insights is being used and you are upgrading from a version older than AEM 6.2, assets must be migrated and have IDs generated through a JMX bean. For ÃÛ¶¹ÊÓƵ’s internal tests, 125K assets on a TarMK environment were migrated in an hour, but your results may vary.

6.3 introduced a new format for the SegmentNodeStore, which is the basis of the TarMK implementation. If you are upgrading from a version older than AEM 6.3, this requires a repository migration as part of the upgrade, involving system downtime.

ÃÛ¶¹ÊÓƵ Engineering estimates this to be around 20 minutes. Reindexing is not necessary. Also, a new version of the crx2oak tool has been released to work with the new repository format.

This migration is not required if upgrading from AEM 6.3 to AEM 6.5.

The pre-upgrade maintenance tasks have been optimized to support automation.

The crx2oak tool command-line usage options have been changed to be automation-friendly and support more upgrade paths.

The post-upgrade checks have also been made automation friendly.

Periodic garbage collection of revisions and data store garbage collection are now routine maintenance tasks that must be performed periodically. With the introduction of AEM 6.3, ÃÛ¶¹ÊÓƵ supports and recommends Online Revision Cleanup. See Revision Cleanup for information on how to configure these tasks.

AEM recently introduces the Pattern Detector for assessment of complexity of the upgrade as you start planning for the upgrade. 6.5 also has a strong focus on backward compatibility of features. Finally, best practices for sustainable upgrades are also added.

For more details about what else has changed in recent AEM versions, see the complete release notes:

Upgrade Overview upgrade-overview

Upgrading AEM is a multi-step, sometimes multi-month process. The following outline has been provided as an overview of what is included in an upgrade project and the content that has been included in this documentation:

Upgrade Flow upgrade-overview-1

The diagram below captures the overall recommended flow highlight the upgrade approach. Note the reference to the new features that ÃÛ¶¹ÊÓƵ has introduced. The upgrade should start with the Pattern Detector(see Assessing the Upgrade Complexity with Pattern Detector) which should let you decide the path you want to take for compatibility with AEM 6.4 based on the patterns in the generated report.

There was a significant focus in 6.5 to keep all the new features backward compatible, but in cases where you still see some backward compatibility issues, the compatibility mode lets you temporarily defer development to keep your custom code compliant with 6.5. This approach helps you avoid development effort immediately after the upgrade(see Backward Compatibility in AEM 6.5).

Finally, in your 6.5 development cycle, features introduced under Sustainable Upgrades(see Sustainable Upgrades) help you follow best practices to make future upgrades even more efficient and seamless.