Pattern Detector helps in assessing the complexity of AEM upgrades.
How the Pattern Detector works?
Pattern detector scans the existing code base before upgrade to ensure that there are no code breakers involved in the current codebase. After scanning, the Pattern Detector provides a set of action items to fix if any issues found. This includes a detailed report of violation explanations and remediation guidance.
How this is helpful?
AEM 6.4 reserves some of the paths and reserved granite codes for internal AEM use only. So Pattern Detector checks any such paths which may be overwritten by the upgrade, also any API which may not be compatible with 6.4 version. Pattern detection is a mandatory step for upgrading to AEM 6.4
Install & configure Pattern Detector:
The installation & configuration steps can be found here
The Pattern detector is available for versions AEM 6.1, AEM 6.2, AEM 6.3, which is downloadable using Adobe Id. This needs to be installed through the AEM package manager.
Access & Analysis of report:
Go to configrMgr and select 'Status'> Pattern Detector. The reports are available in normal text or JSON formats.
Some of the Pattern detector sample codes are
OCU - Depicts Deprecated usages
ECU - Suspicious overlays, overrides, references
LOCP - Any packages that overwrite '/libs'
NBCC - non-backward compatible changes
CAV - Directs to reduce the amount of overlayed content in general due to security problems
Usage Recommendations:
Pattern detector is recommended to use at stage environments to avoid any slowness in production environments.
No comments:
Post a Comment
If you have any doubts or questions, please let us know.