Skip to content

What Is the AEM Pattern Detector? Its Role in Upgrading to AEM 6.4

By Arjun Menon··1 min read
On this page
  1. How it works
  2. Why it helps
  3. Installing and configuring it
  4. Reading the report
  5. Some of the report codes
  6. Where to run it

The Pattern Detector helps assess the complexity of an AEM upgrade.

How it works

Before an upgrade, the Pattern Detector scans the existing code base for anything that would break. It then produces a list of action items for the issues it finds, with a detailed explanation of each violation and guidance on fixing it.

Why it helps

AEM 6.4 reserves some paths and Granite code for internal AEM use. The Pattern Detector checks for anything at those paths that the upgrade would overwrite, and for any API use that is not compatible with 6.4. Running it is a mandatory step when upgrading to AEM 6.4.

AEM Pattern Detector

Installing and configuring it

The Pattern Detector is available for AEM 6.1, 6.2 and 6.3 and is downloaded with an Adobe ID. It is installed through the AEM Package Manager. Adobe's AEM 6.4 documentation on the Pattern Detector has the full installation and configuration steps.

Reading the report

In the web console, open Status > Pattern Detector. Reports are available as plain text or JSON.

Some of the report codes

OCUDeprecated usages
ECUSuspicious overlays, overrides and references
LOCPPackages that overwrite /libs
NBCCNon-backward-compatible changes
CAVAdvises reducing overlaid content in general, for security reasons

Where to run it

Run the Pattern Detector on a stage environment rather than production, to avoid slowing production down.

Moving from another CMS rather than an older AEM? See steps to migrate a third-party CMS website to AEM.

More in Operations, SEO and upgrades