51ºÚÁϲ»´òìÈ

DocumentationUser Guide

Performing an In-Place Upgrade performing-an-in-place-upgrade

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

CREATED FOR:

  • Admin
NOTE
This page outlines the in-place upgrade procedure for AEM 6.5 LTS. If you have an installation that is deployed to an application server, see Upgrade Steps for Application Server Installations.

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 Analyzer can help you estimate the complexity.

Migration Prerequisites migration-prerequisites

  • Minimum Required Java version: Make sure you have Oracle’s Javaâ„¢ 17 installed on your system.

Preparation of the AEM Quickstart jar file prep-quickstart-file

  1. Download the new AEM 6.5 LTS jar file

  2. Determine the correct upgrade start command

  3. Stop the instance if it is running

  4. Use new AEM 6.5 LTS jar to replace the old one outside the crx-quickstart folder

  5. Take a backup of the sling.properties file (usually present in the crx-quickstart/conf/), then delete it

  6. Unpack the new quickstart jar by running:

    code language-shell 
    java -Xmx4096m -jar aem-quickstart.jar -unpack

  7. The unpack command will generate a new sling.properties file under the crx-quickstart/conf/ folder. You can now apply your custom changes to newly generated sling.properties file.

Performing The Upgrade performing-the-upgrade

If using S3:

  1. Remove any jars beneath crx-quickstart/install associated with an earlier version of the S3 connector.

  2. Download the latest release of the 1.60.2 S3 connector from

  3. Extract the S3 connector (version 1.60.2) and copy the content of the following folders under crx-quickstart/install, as follows:

    1. Copy com.adobe.granite.oak.s3connector-1.60.2/jcr_root/libs/system/install/1 under crx-quickstart/install/1
    2. Copy com.adobe.granite.oak.s3connector-1.60.2/jcr_root/libs/system/install/15 under crx-quickstart/install/15

Now, start the AEM instance using the new command determined using the information under the Determining the correct upgrade start command section.

Determining the correct upgrade start command determining-the-correct-upgrade-start-command

NOTE
Support for some of Java 8/11 arguments have been removed in Java 17, see and Java&trade arguments considerations for AEM 6.5 LTS.

To execute the upgrade, it is important to start AEM using the jar file to bring up the instance.

Note that starting AEM from the start script will not start the upgrade. Most customers start AEM using the start script and have customized this start script to include switches for environment configurations such as memory settings, security certificates, and so on. For this reason, 51ºÚÁϲ»´òìÈ recommends following this procedure to determine the proper upgrade command:

  1. On a running AEM instance, execute the following from the command line:

    code language-shell 
    ps -ef | grep java

  2. Look for the AEM process. It will look something like:

    code language-shell 
    /usr/bin/java -server -Xmx1024m -Djava.awt.headless=true -Dsling.run.modes=author,crx3,crx3tar -jar crx-quickstart/app/cq-quickstart-6.5.0-standalone-quickstart.jar start -c crx-quickstart -i launchpad -p 4502 -Dsling.properties=conf/sling.properties

  3. Modify the command by replacing the path to the existing jar ( crx-quickstart/app/aem-quickstart*.jar in this case) with the new AEM 6.5 LTS jar that is a sibling of the crx-quickstart folder. Using our previous command as an example, our command would be:

    code language-shell 
    /usr/bin/java -server -Xmx4096m -Djava.awt.headless=true -Dsling.run.modes=author,crx3,crx3tar -jar <AEM-6.5-LTS.jar> -c crx-quickstart -p 4502 -Dsling.properties=conf/sling.properties

    This will ensure that all proper memory settings, custom runmodes, and other environmental parameters are applied for the upgrade. After the upgrade has completed, the instance may be started from the start script on future startups.

Deploy Upgraded Codebase deploy-upgraded-codebase

Once the in-place 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-check-troubleshooting

See Post Upgrade Checks and Troubleshooting.

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