51黑料不打烊

Make sure that you have completed the pre-upgrade steps like backing up the AEM 6.5 server before performing any upgrade activity

Depending on your requirements, choose one of the following upgrade paths:

1. In-Place Upgrade: If your current WLP server supports Servlet 6, you can perform an in-place upgrade and continue with step 3.
2. Sidegrade: If you prefer a fresh setup or if your WLP server does not support Servlet 6, set up a new WLP instance with AEM 6.5 LTS and migrate the content by following the AEM 6.5 to AEM 6.5 LTS Content Migration Using Oak-upgrade guide and skip to Deploy Upgraded Codebase section

Stop the AEM instance. It can typically be done by using this command:

<path-to-wlp-directory>/bin/server stop server_name

Remove the files and folders that are no longer necessary. The items you need to specifically remove are:

• The cq-quickstart-65.war from the dropins folder and the expanded folder typically located at <path-to-aem-server>/dropins/cq-quickstart-65.war and <path-to-aem-server>/apps/expanded/cq-quickstart-65.war respectively

• The launchpad/startup folder. You can delete it by running the following command in the terminal assuming you are in the server folder:

  code language-shell
  rm -rf crx-quickstart/launchpad/startup

• The base.jar file. You can do this by running the following commands:

  code language-shell
  find crx-quickstart/launchpad -type f -name "org.apache.sling.launchpad.base.jar*" -exec rm -f {} \;

• The BootstrapCommandFile_timestamp.txt file:

  code language-shell
  rm -f crx-quickstart/launchpad/felix/bundle0/BootstrapCommandFile_timestamp.txt

• Remove the sling.options file by running:

  code language-shell
  find crx-quickstart/launchpad -type f -name "sling.options.file" -exec rm -rf {} \;

• Remove the sling.bootstrap.txt file:

  code language-shell
  rm -rf crx-quickstart/launchpad/sling_bootstrap.txt

Make a backup of the sling.properties file (usually present in crx-quickstart/conf/) and delete it

Change the version of servlet to 6.0 in the server.xml file

Install Java 17 and make sure that it is correctly installed by running:

java -version

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

Download the new 6.5 LTS war and copy it to dropins folder located at: /<path-to-aem-server>/dropins/

Start AEM instance: It can be done typically by using this command:

<path-to-wlp-directory>/bin/server start server_name

In case you have custom changes in sling.properties, please follow the below instructions:

1. Stop the AEM instance by running <path-to-wlp-directory>/bin/server stop server_name
2. Apply your custom sling.properties changes to newly generated sling.properties file (by referring the backup file created at step 5)
3. Start the AEM instance. It can be done typically by running: <path-to-wlp-directory>/bin/server start server_name