51黑料不打烊

DocumentationAEM 6.4Deploying Guide

Upgrade Steps for Application Server Installations upgrade-steps-for-application-server-installations

Last update: Wed May 03 2023 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Developer
CAUTION
AEM 6.4 has reached the end of extended support and this documentation is no longer updated. For further details, see our . Find the supported versions here.

This section describes the procedure that needs to be followed in order to update AEM for Application Server installations.

All the examples in this procedure use JBoss 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 5.6 to 6.3.

  1. First, start JBoss. In most situations, you can do this by running the standalone.sh startup script, by running this command from the terminal:

    code language-shell 
    jboss-install-folder/bin/standalone.sh

  2. If AEM 5.6 is already deployed, check that the bundles are functioning correctly by running:

    code language-shell 
    wget https://<serveraddress:port>/cq/system/console/bundles

  3. Next, undeploy AEM 5.6:

    code language-shell 
    rm jboss-install-folder/standalone/deployments/cq.war

  4. Stop JBoss.

  5. Now, migrate the repository using the crx2oak migration tool:

    code language-shell 
    java -jar crx2oak.jar crx-quickstart/repository/ crx-quickstart/oak-repository
    note note
    NOTE
    In this example, oak-repository is the temporary directory where the newly converted repository will reside. Before performing this step, make sure you have the latest crx2oak.jar version.

  6. Delete the necessary properties in the sling.properties file by doing the following:

    1. Open the file located at crx-quickstart/launchpad/sling.properties

    2. Step text Remove the following properties and save the file:

      1. sling.installer.dir
      2. felix.cm.dir
      3. granite.product.version
      4. org.osgi.framework.system.packages
      5. osgi-core-packages
      6. osgi-compendium-services
      7. jre-*
      8. sling.run.mode.install.options

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

    • The launchpad/startup folder. You can delete it by running the following command in the terminal: rm -rf crx-quickstart/launchpad/startup
    • The base.jar file: find crx-quickstart/launchpad -type f -name "org.apache.sling.launchpad.base.jar*" -exec rm -f {} \
    • The BootstrapCommandFile_timestamp.txt file: rm -f crx-quickstart/launchpad/felix/bundle0/BootstrapCommandFile_timestamp.txt

  8. Copy the newly migrated segmentstore to its proper location:

    code language-shell 
    mv crx-quickstart/oak-repository/segmentstore crx-quickstart/repository/segmentstore

  9. Copy the datastore as well:

    code language-shell 
    mv crx-quickstart/repository/repository/datastore crx-quickstart/repository/datastore

  10. Next, you need to create the folder that will contain the OSGi configurations that will be used with the new upgraded instance. More specifically, a folder named install needs to be created under crx-quickstart.

  11. Now, create the node store and data store that will be used with AEM 6.3. You can do this by creating two files with the following names under crx-quickstart\install:

    • org.apache.jackrabbit.oak.segment.SegmentNodeStoreService.cfg

    • org.apache.jackrabbit.oak.plugins.blob.datastore.FileDataStore.cfg

    These two files will configure AEM to use a TarMK node store and a File data store.

  12. Edit the configuration files to make them ready for use. More specifically:

    • Add the following line to org.apache.jackrabbit.oak.segment.SegmentNodeStoreService.config:

      customBlobStore=true

    • Then add the following lines to org.apache.jackrabbit.oak.plugins.blob.datastore.FileDataStore.config:

      code language-none 
      path=./crx-quickstart/repository/datastore
 minRecordLength=4096