Skip to main content

Go - Live & Cutover

Depending on the size of your repository and shutdown window available, you need to plan your go -live and cutover plan very carefully.




Go-live plan  -  Go-live plan should capture each and every activity in hours and days. The high-level categories that are recommended are

  1. Pre-requisite phase
    1. Notifying editors
    2. Cloning of unique instances
    3. Run maintenance activities etc
  2. Upgrade phase
    1. Upgrade author
    2. Upgrade publish
    3. Upgrade dispatcher
  3. Post upgrade phase
    1. Undertake post-upgrade activities
    2. Undertake post upgrade performance tunings
    3. Undertake post upgrade validations
    4. Build code
    5. Configure dispatcher with DNS and sling mappings
    6. Configure ELB
    7. Setup Akamai CDN
    8. Configure cold standby
    9. Backup instances
    10. Run the sanity test
  4. Delta content migration
    1. Get a production clone 
    2. Run the delta content migration using it
    3. verify delta content
  5. Verification w/o ELB
    1. Run sanity validation on each site
  6. Cutover
    1. Run delta content migration again (if system was not shut down for above steps)
    2. Copy it to all clones
    3. Validate delta content
    4. Enable ELBs with multiple nodes
    5. Switch DNS to production
    6. Go Live
Cutover - Cutover normally is the time during which system is switched from beta to production. Systems are shutdown during this time. Normally, authors will be shut down but few publish systems will be on so that there is no impact on the end sites.

Cutover should be planned for each minute, since shutdown times are always limited. Owners should be clearly mentioned against each activity.

It should typically comprise of -

  1. Notifying production downtime
  2. Configure ELB to have one publish
  3. Shutdown cold standby
  4. Shutdown all production systems
  5. Run delta content migration
  6. Configure runmodes and other configuration needed
  7. Switch production sling mappings
  8. Switch dispatcher to production DNS
  9. Deploy Replication agents 
  10. Configure to have all publish in ELB
  11. Configure CDN
  12. Final validation
You may start parallel authoring between 62 and 561 for some time to have the option of rollback.

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

A case for 'strategy' in Digital Strategy...

I recently finished a book named 'Digital Strategy' by Alexander Rauser. Alexander has given current day problems during any Digital transformation and pragmatic solutions for that. Having worked in the IT industry for 17 years and last 10 years mostly into Digital Transformations for most of the fortune 500 companies, it was quite relevant to me. If you are also part of any digital transformation of any organization in any capacity, you will find it helpful too. Over the last decade, companies have thought of digital strategy as a means to market new technology or recognize upcoming trends. However, today few of those companies do realize that Digital Strategy is all about continuously improving your business to stay ahead in the curve, but some are still stuck in the old mindset. It's surprising to see  'Strategy' is missing from the Digital Strategy for many of the transformations happening, rather the focus is just on 'Marketing' (Digital Marketing...
Post a Comment
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