AEM 6.5 Migration Initiative Overview

This initiative aims to resolve the compaction issue in AEM 6.5, reduce system locking time, and provide uninterrupted access to editorial teams. The primary goal is to eliminate compaction time and upgrade to the latest AEM version to benefit from security patches and new features. Main stakeholders include editorial teams, IT departments, and marketing teams. A successful POC migration to 6.5 in April-May boosted confidence in the migration process. The scope includes upgrade planning, development, QA, maintenance, upgrade procedures, and post-upgrade checks. Out-of-scope tasks involve evaluating new features and stakeholder training unless necessary due to procedural changes post-migration.

• AEM migration
• Compaction issue
• Upgrade planning
• Stakeholders
• POC migration

leea_5 Follow

Uploaded on Sep 26, 2024 | 0 Views

Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

Presentation Transcript

1. Migration to AEM 6.5 July 19, 2021

2. What problem we want to solve? Resolve compaction issue Compaction takes now more than 3 hours every night. Time when it will be finished - unpredictable (sometimes it takes 3 hours and sometimes 4+). During this time Editorial team is not able to work with Author Server (backend part of AEM). This situation impact our ability to prepare morning editions, newsletters and new articles.

3. What are goals of the Initiative? Primary goal Eliminate compaction time AEM version 6.5 supports on-fly compaction. Compaction is running as background process. This solution eliminate system s locking time and provide our editorial team with 24/7 access to the tool. Secondary goal Upgrade our AEM system to the latest available version Version 6.5 is the latest AEM version. It contains security patches, new features, performance improvements and bug fixes.

4. Who are main stakeholders? Editorial teams The Star Regional dailies Teams created sponsors' content Teams created special articles Marketing team (work with Smart assets) Data Team Group IT Digital department

5. POC: Migration to 6.5 POC was done in April May by Reza, Neil and Will Following tasks were completed: Server with AEM 6.5 was set by Will Our production code and content were added to the server We checked all core areas. We ran test of core functionality All found issues were documented and requested effort to fix it was estimated Results of the POC: It went better than we expected This exercise has increased our confidence that the migration will be successful. POC helped us estimate effort and identify areas requested more attention .

6. What is the scope of the Initiative? Upgrade planning Development and QA Pre-upgrade Maintenance Upgrade Procedure Post Upgrade Checks What is out of scope (will be done later): Evaluation and using of new features (except features related to compaction) Training for stakeholders (except situations when/if migration will change current work procedures)

7. What is the scope of the Initiative? Upgrade planning Identify upgrade s scope and areas Estimate level of Effort Review architecture Create environment(s) for development and migration Create plan for Developers Create test plan Development and QA Pre-upgrade Maintenance Upgrade Procedure Post Upgrade Checks

8. What is the scope of the Initiative? Upgrade planning Development and QA Test communication AEM-NG Test AEM functionality Test AEM Jobs Test Web Test APPs Smart assets test Test import/export feeds Test Newsletters Test communications with other applications and servers Loading testing Stress Testing Performance testing Fixing of all issues Compaction testing Pre-upgrade Maintenance Upgrade Procedure Post Upgrade Checks

9. Roadmap

10. Proposed Team Structure Sponsor Core Team Angus Frame Lead Members Dmitry Firer Monica Ionel Reza Tayefi BorisSinder Eugenie Badorov Neil O Conner Priyanka Chauhan QA Will Johnson Brett Smith Bill Angus PM DM Dev. Lead Dev. Dev. QA Lead DevOps Lead AEM specialist support for editorial teams AEM specialist support for editorial teams

11. Key Stakeholders Editorial Christine Loureiro Tim Munroe Rod Frketich Angus Scott Kennedy Gordon Fadi Yaacoub Sponsors team Kendra Schumacher Marketing Team (smart assets) Gord Bennett Michael Bates IT department Jay Shervill Ryan Roach, Ross Roach Data Team Edward Galutan Matthew Cole Digital Jason Antheunis

12. Key areas to address Communication with applications supported by IT Environments Dev. Plan QA Plan Editorial testing and signoff Pre-migration activities Rollback plan Migration procedure Post-migration cleaning Monitoring and Alarming

13. Plan for IT Provide access to Staging NG Create accounts for Brett Bill Neil

14. Detailed Plan

15. Plan for DevOPS Identify potential architecture changes Create requirements For developers QA Pre-production (will become production at the end of the project) Should be identical to our production environment Provide connection to NG TSS/Emma Create automated scripts for environments Establish alarms and monitoring systems for new environments Prepare migration night plan Prepare Rollback plan Prepare post-implementation plan

16. Plan for Editorial testing Determine all of the customizations that have been made to the system so that they can be included in a test plan Test all functionality by Brett and Bill (confirmation that all elements work as expected) Quick training for Editorial team How to work with AEM 6.5 Intensive test by dedicated Editorial group Test all work processes and templates Confirm that all is working as expected Post-migration activities Review new features in AEM 6.5 Analyze what features can eb used Create training plan to address new and changed features/flows (Brett and Bill)

17. Plan for Developers Create dedicated code branch Test on-fly compaction to confirm that it will work as expected Fix bugs identified in POC

18. Plan for QA Compaction testing Test communication AEM-NG and TSS-EMMA Test it for different types and different sizes of packages Test AEM functionality make sure to cover all customizations that have been made to the system in addition to out of the box UIs and workflows that are leveraged in your day to day operations. Verify that all activities in AEM are working as expected Test preview functionality test Queries ability to query by section/subsection ability to query based on tags Test time bombs and off time Test functionality that can be set on Folder level Test Sharing between dailies Test My Local activities Test Work with fixed containers Test Ads settings Test Viafoura settings Test STN player settings Test AEM Jobs Job for Feeds Jobs for LiftIgniter (catalogue update) Check synchronization between Web and APP

19. Plan for QA (continuation) Test Web Test APPs Test AMP Smart assets test Test import/export feeds import Export Test Newsletters Test communications with other applications and servers The Kit Food syndication Loading testing Stress Testing Performance testing Test Automation feeds system (CP, Tyee, WFP) Test feeds from WSJ, NYT, etc Sync Job for DNN local Test all RSS feeds Test Feed to Apple News Test Facebook Instant articles Test feeds to Communities Test communication with Data team Test feeds to DNN