Skip to main content

Upgrade Execution

Once the Assessment /Discovery phase is complete and you have the understanding of the current system, its time to do the upgrade.


During the dry run upgrade in the assessment phase, it's important that dry run should be done on production replica, to estimate and plan things during upgrade execution phase.
In our case, there were multiple authors and multiple unique publish instances that we had to upgrade (discovered during assessment phase). And upgrade should be done on high-end servers (we leveraged server with16 core CPU, 70 GB RAM, and high IOPS disk mount), to expedite the upgrade duration.
Once the upgrade is done, its should be deployed on Dev servers and required code base should be built over it.
We used dev server for an upgrade and unit testing. Then test machine was used for integration and QA, UAT (business testing) and LT was used for load testing (dev copy can be leveraged here).
Finally, in the production upgrade, we upgraded again for pre-prod and did a mock cutover on it. Once the sanity was done, same was moved to Production servers.
Before upgrade execution, you should have custom upgrade steps for your project both for authors and publish in somewhat following manner 
  1. Upgrade steps for authors
  2. Upgrade steps for publish
  3. Upgrade steps for Dispatcher
  4. Upgrade troubleshooting
The standard steps are mentioned in detail at - https://docs.adobe.com/docs/en/aem/6-2/deploy/upgrade.html

Comments

Post a Comment

Popular posts from this blog

Some SDL Tridion Interview Questions…

Many of my friends keep asking me to provide some interview questions related with SDL Tridion . Surprisingly, there are hardly any site available for questions related with SDL Tridion., though you can find host of sites for other WCMs like AEM and Sitecore. Hence, I thought to put some basic Tridion related questions on the basis of my experience with it. I know it may require several improvements but thought to share something for someone who is looking to get some Tridion related questions to start with. I will be glad to incorporate any suggestion you have. Development phases related questions - What is the development methodology recommended by SDL for development/integration based on SDL Tridion? Have you participated in any Blueprinting workshop, please share the experience? What are the inputs required in BluePrint? How can inheritance of content flow be altered explicitly? What are priority and ranking in Blueprint? What are the inputs required for Content Modeling ...
6 comments
Read more

Campaign Management in Adobe CQ5/AEM

Campaign management provides digital marketers the opportunity to create dedicated experiences for visitors.   We can create content, segment visitors, push and promote targeted content for specific user profiles and manage campaigns across multiple channels. Elements in Campaign Management :- Brands: Brands are the top level unit and form a collection of Campaigns. Campaigns: A campaign is a collection of individual Experiences. Teasers: Teaser Pages / Paragraphs are used to steer specific visitor . Typically a teaser page is a temporary action that will last for a specific period of time, until it is replaced by the next teaser page. Newsletters: E-mail Communications are used to engage users and encourage them to visit your web site. These usually take the form of a newsletter, sent to Leads (which are usually grouped into Lists) Leads: The information that you have collected about your visitors and how to contact them forms the basis for your leads. Lists:Leads are u...
2 comments
Read more

User generated content (UGC) implementation - SoCo or AEM communities or Adobe LiveFyre or Adobe Social

Users are contributing content more than ever before, and it's getting difficult for Enterprise systems to manage it. To cope up with this, Adobe keeps evolving their UGC ecosystem. I think it was called  Social Collaboration tool  before CQ 5.5 After CQ 5.5 it was called  Social Communities  (So-Co),  this was shortened to So-Co. With AEM 6, this was rebranded as AEM Communities. At that point, all UGC components functionality was moved into Communities from AEM. So forums, comments/ratings etc. With 6.2, the concept of a central store was introduced, so content was saved outside of AEM in a central location where all instances would read and write, this can be Mongo, or JCR (but only for single instances) or it can be cloud storage (better name than social storage) which as you know carries a cost. And then Adobe overtook another product named Livefyre which is managed comments and other UGC ...
Post a Comment
Read more