Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

In-place upgrade from Author to Publisher

Avatar

Level 4

Hi all,

I am planning to upgrade from AEM 6.2 to 6.4. Below are the steps to perform in Author server.

 

  1. Stop the instance if it is running
  2. Download the new  AEM6.4 jar file and use it to replace the old one outside the crx-quickstart folder.
  3. Unpack the new quickstart jar by running:
  4.     java -jar AEM_6.4_author-p4504.jar –unpack
  5.     java -server -Xmx1024m -XX:MaxPermSize=256M -Djava.awt.headless=true -Dsling.run.modes=author,crx3,crx3tar -jar cq-author-p4504.jar -c crx-quickstart -p 4504 -Dsling.properties=conf/sling.properties
  6. Start AEM either using start.bat or the jar

 

 

Do we need to perform the exact steps for the remaining Publisher servers? or Is there anyone to replicate to Publisher after upgrading in Author server?

 

 

Thanks,

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Upgrade needs to be run on each instance separately and make sure you are starting the instance with the correct run mode. EX: Starting author with "author" runmode

 

That said, you need to run repository migration between step 4 and 5. See detailed steps at [1]

 

[1] https://experienceleague.adobe.com/docs/experience-manager-65/deploying/upgrading/in-place-upgrade.h...

 

View solution in original post

5 Replies

Avatar

Community Advisor

Hi @ariesyinn 

 

Each of the instances (author and publish) needs to be upgraded separately and the same steps needs to be performed across all the instances. The only difference with the command will be file name and run mode i.e. author vs publish and the port number.

 

java -server -Xmx1024m -XX:MaxPermSize=256M -Djava.awt.headless=true -Dsling.run.modes=author/publish,crx3,crx3tar -jar cq-author/publish-p4504.jar -c crx-quickstart -p 4504 -Dsling.properties=conf/sling.properties

 

Thanks!

Avatar

Community Advisor

Hi @ariesyinn,

Below link details the sequential steps for Author, Publish - TarMK/MongoMK with sample scenario.

https://experienceleague.adobe.com/docs/experience-manager-64/deploying/upgrading/upgrade-procedure....

Also, take care of repository migration using crx2oak tool (to accommodate the changes in Segment Node store introduced in AEM 6.3)

 

Avatar

Correct answer by
Employee Advisor

Upgrade needs to be run on each instance separately and make sure you are starting the instance with the correct run mode. EX: Starting author with "author" runmode

 

That said, you need to run repository migration between step 4 and 5. See detailed steps at [1]

 

[1] https://experienceleague.adobe.com/docs/experience-manager-65/deploying/upgrading/in-place-upgrade.h...