Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Upgrade from 6.3 to 6.5

mick_jagger
Level 1
Level 1

Hi all. 
I hope the best during this time.

Well.. 
I'm new to adobe (and programming in general), I started last month on AEM 6.4.0 practicing with components, templates and more on my project.

My tutor has 6.3 and he would like to migrate to 6.5.
So just few days ago he told me to find out what are the steps to "convert" a project developed in 6.3 to 6.5.

In addition, we are working with Java 8 on eclipse.. do we have to change something there too?
So.. I would like to understand what are the steps to achieve the purpose.

 

And an other question.. what is the purpose of pattern detector? 
I looked for documentation but I'm more confused than before because I don't understand what exactly needs to be done.

Thank you very much in advance to all and sorry for my English.

1 Accepted Solution
Nirmal_Jose
Correct answer by
Community Advisor
Community Advisor

Hi,

Adobe documentation captures all the scenarios for AEM upgrade. Please refer to it at [1]. On a high level, the changes are

1. Upgrading the AEM instance - you can do either in-place upgrade or fresh install approach based on your content size and 
2. Upgrade your artefacts by compiling against 6.5 uber jar.
3. Test and fix any issues due to deprecated features/overlaid capabilities change.
4. From 6.4, as part of sustainable upgrades process, there is a repository restructuring that can be done (not mandatory). Refer to it at [2]
5. Process on how to rollout the changes to production.

 

If this is hard, adobe offers a backward compatibility mode from 6.3 with which you can run a 6.3 aem artefact on a 6.5 instance. Read more at [3]

 

Pattern detector is a mechanism provided by Adobe to easy identify of possible problems that will come up during upgrade by validating against deprecated features and overlays. Refer more at [4]

 

AEM 6.5 is compatible with Java 8. Refer to [5]

[1] - https://docs.adobe.com/content/help/en/experience-manager-65/deploying/upgrading/upgrade.html
[2] - https://docs.adobe.com/content/help/en/experience-manager-65/deploying/restructuring/repository-rest... 
[3] - https://docs.adobe.com/content/help/en/experience-manager-65/deploying/upgrading/backward-compatibil... 
[4] - https://docs.adobe.com/content/help/en/experience-manager-65/deploying/upgrading/pattern-detector.ht... 
[5] - https://docs.adobe.com/content/help/en/experience-manager-65/deploying/introduction/technical-requir... 

View solution in original post

4 Replies
Nirmal_Jose
Correct answer by
Community Advisor
Community Advisor

Hi,

Adobe documentation captures all the scenarios for AEM upgrade. Please refer to it at [1]. On a high level, the changes are

1. Upgrading the AEM instance - you can do either in-place upgrade or fresh install approach based on your content size and 
2. Upgrade your artefacts by compiling against 6.5 uber jar.
3. Test and fix any issues due to deprecated features/overlaid capabilities change.
4. From 6.4, as part of sustainable upgrades process, there is a repository restructuring that can be done (not mandatory). Refer to it at [2]
5. Process on how to rollout the changes to production.

 

If this is hard, adobe offers a backward compatibility mode from 6.3 with which you can run a 6.3 aem artefact on a 6.5 instance. Read more at [3]

 

Pattern detector is a mechanism provided by Adobe to easy identify of possible problems that will come up during upgrade by validating against deprecated features and overlays. Refer more at [4]

 

AEM 6.5 is compatible with Java 8. Refer to [5]

[1] - https://docs.adobe.com/content/help/en/experience-manager-65/deploying/upgrading/upgrade.html
[2] - https://docs.adobe.com/content/help/en/experience-manager-65/deploying/restructuring/repository-rest... 
[3] - https://docs.adobe.com/content/help/en/experience-manager-65/deploying/upgrading/backward-compatibil... 
[4] - https://docs.adobe.com/content/help/en/experience-manager-65/deploying/upgrading/pattern-detector.ht... 
[5] - https://docs.adobe.com/content/help/en/experience-manager-65/deploying/introduction/technical-requir... 

View solution in original post

mick_jagger
Level 1
Level 1
Thank you very much. I have a starting point now 🙂
mick_jagger
Level 1
Level 1
Thank you very much. I have a starting point now 🙂 So the first step that is recommended is to detect the pattern with the pattern detector?