In place upgrade of Adobe Experience Manager(AEM) to 6.2 version
This post will explain the steps to in place upgrade of Adobe Experience Manager(AEM) server to 6.2 version- Backup the current Adobe Experience Manager(AEM) instance
- Copy aem-quickstart-6.2.0.jar next to current Adobe Experience Manager(AEM) crx-quickstart
- Perform regular maintenance activities - including workflow purge
- Run the Traversal check and Data store consistency check one by one - http://localhost:4502/system/console/repositorycheck
- Disable custom login moduels if any - make sure the default login module is configured as below in crx-quickstart/repository/repository.xml
<LoginModule class="com.day.crx.core.CRXLoginModule">
<param name="anonymousId" value="anonymous"/>
<param name="adminId" value="admin"/>
<param name="disableNTLMAuth" value="true"/>
<param name="tokenExpiration" value="43200000"/>
<!-- param name="trust_credentials_attribute" value="d5b9167e95dad6e7d3b5d6fa8df48af8"/ -->
</LoginModule>
- Stop the Adobe Experience Manager(AEM) server
- Remove all log files under crx-quickstart/logs
- chown -R aem:aem crx-quickstart(this command is required if AEM is running with different user)
- su aem(this commad is required if AEM is running with diffrent user)
- If you are migrating from AEM 5.x or AEM 6.0 with a CRX2 backend then follow URL - https://www.albinsblog.com/2015/09/upgrading-aemadobe-cq5-5.6.1-to-aemadobe-cq5-6.1.html
- If you are migrating from AEM 6.0 with a oak backend or 6.1 then execute java -jar aem-quickstart-6.2.0.jar -r author,crx3,crx3tar
- Monitor error.log and stderr.log – Once the migration is completed stderr.log will show the following message
Startup time:442 seconds
http://localhost:4502/
Quickstart started”
URL to check the version - http://localhost:4502/system/console/productinfo
Check the bundles in Installed state, most of the obsolete bundles will be removed after upgrade but some cases some of the obsolete bundles will not be uninstalled - This can be ignored or uninstalled manually (better to compare the bundles with fresh 6.2 installation).Refer the following URL for details on obsolete bundles https://docs.adobe.com/docs/en/aem/6-2/deploy/upgrade/obsolete-bundles.html
Custom core bundles may not start due to the dependency issues. Refer the following URL for API difference between 6.1 and 6.2 - https://docs.adobe.com/docs/en/aem/6-2/develop/ref/diff-previous/changes/changes-summary.html
Update the maven dependency with correct version by identifying the version through depfinder -
http://localhost:4502/system/console/depfinder
Custom core bundles may not start due to the dependency issues. Refer the following URL for API difference between 6.1 and 6.2 - https://docs.adobe.com/docs/en/aem/6-2/develop/ref/diff-previous/changes/changes-summary.html
Update the maven dependency with correct version by identifying the version through depfinder -
http://localhost:4502/system/console/depfinder
