ÃÛ¶¹ÊÓƵ

DocumentationUser Guide

Upgrade Steps for Application Server Installations (Tomcat) upgrade-steps-for-application-server-installations-tomcat

Last update: Fri Mar 07 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Admin
NOTE
This page outlines the upgrade procedure for the AEM 6.5 LTS on Tomcat.

Pre-Upgrade Steps pre-upgrade-steps

Before executing your upgrade, there are several steps that must be completed. See Upgrading Code and Customizations and Pre-Upgrade Maintenance Tasks for more information. Additionally, make sure that your system meets the requirements for AEM 6.5 LTS and see upgrade planning considerations and how the Analyzer can help you estimate the complexity.

Migration Prerequisites migration-prerequisites

  • Minimum Required Java version: Make sure you have installed Oracle® JRE 17 on your Tomcat server.
  • Tomcat server: The version of the Tomcat server required for 6.5 LTS is 11.0.x.

Performing the Upgrade performing-the-upgrade

All the examples in this procedure use Tomcat as the Application Server and imply that you have a working version of AEM already deployed. The procedure is meant to document upgrades performed from AEM version 6.5 to 6.5 LTS.

  1. If AEM 6.5 is already deployed, check that the bundles are functioning correctly by accessing: https://<serveraddress:port>/system/console/bundles

  2. Next, stop AEM 6.5. This can be done from the Tomcat App Manager at: https://<serveraddress:port>/manager/html

  3. Make sure that you have completed the pre-upgrade activities like backup of AEM 6.5 server before performing any upgrade activity

  4. Install Java 17 and make sure that it is correctly installed by running the command:

    code language-none 
    java –version

  5. Set up an AEM 6.5 LTS compatible Tomcat server

  6. Review the start parameters for the AEM server and make sure to update the parameters accoding to the system requirements. See Java 17 Considerations for more information

  7. Deploy the newly downloaded 6.5 LTS war on the Tomcat server using Java 17 and start AEM 6.5 LTS Tomcat server by running:

    code language-none 
    $CATALINA_HOME/bin/catalina.sh start

  8. Once the AEM is up and running, make sure all the bundles are in running state by accessing: https://<serveraddress:port>/cq/system/console/bundles

  9. Stop the AEM 6.5 LTS Tomcat server. In most situations, you can do this by running the ./catalina.sh script, by running this command from the terminal:

    code language-none 
    $CATALINA_HOME/bin/catalina.sh stop

  10. Now migrate your content from AEM 6.5 to AEM 6.5 LTS by following the steps here: AEM 6.5 to AEM 6.5 LTS Content Migration Using Oak-upgrade

  11. Once the content has been migrated, apply any custom changes required in the sling.properties file

  12. Start the AEM 6.5 LTS Tomcat server by running:

    code language-none 
    $CATALINA_HOME/bin/catalina.sh start

  13. Monitor the error logs while AEM starts up to check that there are no errors and AEM is running smoothly

  14. Once AEM 6.5 LTS has started, check that the bundles are functioning correctly by accessing: https://<serveraddress:port>/cq/system/console/bundles

Deploy Upgraded Codebase deploy-upgraded-codebase

Once the upgrade process has been completed, the updated code base should be deployed. Steps for updating the code base to work in the target version of AEM can be found in Upgrade Code and Customizations page.

Perform Post-Upgrade-Checks-And-Troubleshooting perform-post-upgrade-checks-and-troubleshooting

See Post Upgrade Checks and Troubleshooting for more information.

recommendation-more-help
51c6a92d-a39d-46d7-8e3e-2db9a31c06a2