Skip to main content

Post Upgrade Activities

Finishing upgrade process on each of the instances is the first part of the upgrade execution.


The next important thing is to perform all post-upgrade activities. This checklist should be prepared before the upgrade depending on the AEM version, service packs, hotfixes, project specific changes done.
The major activities that we did as a part of post-upgrade activities are - 
  1. Post upgrade tasks like 
    1. disabling online compaction from operation dashboard
    2. Cleanup repository folder
    3. Felix Http Jetty Upgrade
    4. Increase ulimit
  2. Configuring Cold standby - 
    1. Here is how to deploy it - https://docs.adobe.com/docs/en/aem/6-2/deploy/recommended-deploys/tarmk-cold-standby.html
    2. Some of the important things that needs to be taken care here are - 
      1. Do not run offline compaction on the standby. It is not needed and it will not reduce the segmentstore size.
      2. In case the primary instance fails for any reason, you can set the standby instance to take the role of the primary by changing the start runmode of standby to primary. Before this, make sure to remove the current primary from the load balancer
      3. Size on repository in the standby instance should be twice the size on the primary
      4. Once the primary instance fails and standby is made as new primary, consider creating a new standby instance for the new primary.
  3. Delta content migration
    1. All paths that needs to participate in delta content migration should be planned well before
    2. Delta content migration is exactly similar to normal AEM migration




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