Go to: Part 1 | Part 2 | Part 3 | Part 4
Step 14: Perform the upgrade
Finally, here you go… Go-ahead and execute the migration as
you have defined in the migration document in step 7 and validated on a test
environment in step 8, 9.
Do not experiment or take any deviation when running the
migration in production, especially when you are handling a complex
installation with large repository and voluminous content.
Stick to the tested process, making sure you are not
skipping or missing out on anything.
If something goes wrong or you get into a scenario which did
not occur in the test configuration, assess the situation and kick off the
rollback process if needed.
And if everything goes fine, well your migration gets
complete and you are ready to expose it to the world!!!
Just hold on... not before its tested and certified
Step 15: Test and certify
Make sure your application is sanity tested after the
migration. Certify that the application is working fine and open it up to the
world.
Step 16: The new normal
Embrace the new normal. Adopt the changes in development,
operations and dev ops processes. And somewhere down the line, you will be in
for another upgrade!!!
Disclaimer
This is a generalization based on my experience with
handling AEM upgrades. Please do check the official documentation for upgrade
available (it’s at https://helpx.adobe.com/experience-manager/6-5/sites/deploying/using/upgrade.html for AEM6.5) which contains version specific
instructions and points to check for performing the upgrade
Go to: Part 1 | Part 2 | Part 3 | Part 4
No comments:
Post a Comment