10 things to consider when planning your Mule 4 migration
0 likes1,567 views
The document outlines key considerations for migrating from Mule 3.x to Mule 4.x, focusing on reasons for migration, differences between the versions, and a step-by-step approach for a successful transition. It emphasizes the importance of assessing the current environment, understanding core component changes, and ensuring thorough testing and support after migration. Additionally, Whishworks offers proven migration processes and automation tools to facilitate the migration effort.
10 things to consider when planning your Mule 4 migration
- 1. 2019 © WHISHWORKS. All rights reserved. 10 things to consider when planning your Mule 4.x migration Prathima Sanka and Sreekanth Cherukuri | WHISHWORKS October 10, 2019
- 2. 2019 © WHISHWORKS. All rights reserved. • Introduction to WHISHWORKS and Mule 4 • When to consider migrating to Mule 4 • Mule 3.x to Mule 4.x main differences • Things to consider • Before you migrate • During migration • After you migrate • An end-to-end approach AGENDA OF THE SESSION
- 3. 2019 © WHISHWORKS. 3 WHISHWORKS & MULE 4 Experience We have worked extensively on Mule 4, from providing feedback on the beta version and migrating our connectors, to completing our first Mule 4 implementations. Certified capabilities Our consultants hold more than 500 MuleSoft certifications, including Mule 4 certifications Proven migration process We provide a proven migration process based on years of successful implementations and numerous platform migrations and data integrations. Automation tools Our Mule 4 Migration Accelerator can automate upto 90% of the migration dependent on your current Mule version and environment
- 4. 2019 © WHISHWORKS. 4 MULE 4 - THE LATEST AND MOST ADVANCED VERSION OF MULE YET simplicity performance extensibility Mule 4 promises reduced management complexity and accelerates application development with up to 50% fewer steps and concepts to learn.
- 5. 2019 © WHISHWORKS. All rights reserved. When to consider migrating to Mule 4 from a previous version • 4 reasons to migrate • MuleSoft product support Mule 3.x to Mule 4.x migration
- 6. 2019 © WHISHWORKS. WHEN SHOULD YOU CONSIDER MIGRATING TO MULE 4 The Mule version you’re using reaches end of support or end of life You want to make significant updates to the existing applications You want to take advantage of key Mule 4 capabilities You decide to upgrade all your apps to Mule 4 so that they are on one version 1 2 3 4
- 7. 2019 © WHISHWORKS. MULESOFT PRODUCT SUPPORT 7 Standard Support Extended Support End of Life Support (only for on premise) January 15, 2015 July 9, 2015 November 16, 2018 March 20, 2021 January 15, 2017 November 16, 2017 November 16, 2021 March 20, 2024 N/A November 16, 2019 After Nov 16, 2021 After March 20, 2024 Mule 3.6 Mule 3.7 Mule 3.8 Mule 3.9
- 8. 2019 © WHISHWORKS. All rights reserved. What changes • Key features Comparison 3.x vs 4.x ‒ Runtime ‒ Message structure ‒ Exception/Error Handling ‒ Connectors ‒ Weaving payload ‒ Data handling ‒ Streaming ‒ Enriching eventsMule 3.x to Mule 4.x migration
- 9. 2019 © WHISHWORKS. 10 Mule Runtime – Feature Comparison 3.x vs 4.x Feature / Characteristic Mule 3.x Mule 4.x Runtime Not so smart, explicit runtime tuning available depending on the scenario Smart – self tuning, high performance, leverages the complete advantages of Non blocking I/O Message structure Complex message structure with inbound, outbound properties and payload Simplified message model with payload and attributes Exception / Error handling Only way to deal with errors is by handling java exceptions Improved error handling with on-error- continue and on-error-propagate. Simplified with built in errors and predefined errors, specific to connector operations. New Try scope to handle errors specific to processor. Connectors Tightly coupled to runtime, both transport and operation oriented Independent of runtime with the introduction of isolated class loading, completely operation oriented
- 10. 2019 © WHISHWORKS. Feature / Characteristic Mule 3.x Mule 4.x Weaving payload Can be updated by using mule expression language, Dataweave, scripting components (using Javascript, Python, and Ruby) and direct binding with java class implementing callable message. Payload can only be overwritten rather than partial update. Data handling Both languages -mule expression language (MEL) and Dataweave 1.0 are used Dataweave 2.0 replaces both of them Streaming Explicit manual configuration required to enable or disable streaming, non repeatable streams Streaming concept is completely abstracted and automatically handled by runtime with the introduction of repeatable streams Enriching events Need to use message enricher component Can be achieved by configuring target variable at the connector and component level 11 Mule Runtime – Feature Comparison 3.x vs 4.x
- 11. 2019 © WHISHWORKS. All rights reserved. Things to consider – before migration • Environment • Mule version • Non Maven projects • Connectors Mule 3.x to Mule 4.x migration
- 12. 2019 © WHISHWORKS. 1. Environment 13 Before Migration – extensive assessment to estimate impact & effort Deployment Mechanism Instructions CloudHub CloudHub is Mule 4 ready. Hybrid Deployment You must install the standalone version of Mule 4 your servers. Anypoint Platform Private Cloud Edition (PCE) PCE supports Mule runtime, version 4. Anypoint Platform for Pivotal Cloud Foundry (PCF) PCF does not support Mule runtime, version 4. 1
- 13. 2019 © WHISHWORKS. 2. Current version(s) and skillsets 14 Before Migration – extensive assessment to estimate impact & effort P2P 1.x 2.x 3.x 3.9 4.x 2
- 14. 2019 © WHISHWORKS. 3. Non Maven projects need to be ‘mavenized’ 15 Before Migration – extensive assessment to estimate impact & effort 3
- 15. 2019 © WHISHWORKS. 4. Connectors used in the applications ▪ Out of the box vs custom connectors ▪ DB queries ▪ HTTP headers ▪ Secure properties 16 Before Migration – extensive assessment to estimate impact & effort 4
- 16. 2019 © WHISHWORKS. All rights reserved. Things to consider – during migration • Core components • API proxies • Munit • Redesign Mule 3.x to Mule 4.x migration
- 17. 2019 © WHISHWORKS. 5. Core components used in the applications –need to rewrite ▪ Number of core components ▪ Use of Java utilities 18 During Migration – Whole implementation needs almost a complete rewrite 5
- 18. 2019 © WHISHWORKS. 7. MUnit ▪ Complete rewrite ▪ Assertions expressions have to replaced with MunitTools::expressions 8. Redesign to utilize Mule 4 capabilities ▪ Batch processing ▪ Filters ▪ Message Enricher ▪ Transformations 19 During Migration – Whole implementation needs almost a complete rewrite 6 7
- 19. 2019 © WHISHWORKS. All rights reserved. Things to consider – after migration • Regression / Performance Testing • Phased / big bang release • Stable support handover / hyper care Mule 3.x to Mule 4.x migration
- 20. 2019 © WHISHWORKS. 9. Regression / Performance Testing ▪ Extensive testing: regression testing and performance testing ▪ Create new baselines 21 After Migration – Testing & Release Management 8
- 21. 2019 © WHISHWORKS. 9. Phased or big bang release ▪ CICD pipelines have to be updated ▪ Mule 4.x release management plan 22 After Migration – Testing & Release Management 9
- 22. 2019 © WHISHWORKS. 9. Plan support handover / hyper care ▪ As the applications are almost rewritten, a proper support handover should be planned ▪ 1-4 weeks hyper care ▪ Decommission 23 After Migration – Testing & Release Management 10
- 23. 2019 © WHISHWORKS. All rights reserved. An integrated approach • Discovery • Migration • Testing and release • Go live Mule 3.x to Mule 4.x
- 24. 2019 © WHISHWORKS. WHISHWORKS MIGRATION – AN INTEGRATED APPROACH Preliminary Assessment (Checklist) Source Code Analysis (Assessment Tool) Consolidation (Checklist & Code Analysis) Migration Strategy & Estimation Automated Migration (Migration Tool) Manual Migration Regression Testing Support • Scripts Preparation • Running Tests • Testing Support Performance Testing Support • Scripts Preparation • Running Tests • Testing Support Functional Testing • Scripts Preparation • Running Tests • Testing Support Go Live SupportAdditional Development • MUnits Development • New Development Environment Setup • Mule4 Platform Setup (on Prem / Cloudhub) Discovery Migration Testing & Release Go Live 1 2 3 4
- 25. 2019 © WHISHWORKS. info@whishworks.com 020 34757980 THANK YOU ANY QUESTIONS? UNITED KINGDOM Vista Building, 2 William Street, Windsor, Berkshire, SL4 1BA Phone: +44 20 34757980 Email: info@whishworks.com INDIA Cyber Gateway C-Block, 2nd Floor, Wing-2 Madhapur, Hyderabad Telangana, 500081 Phone: +91 40 4265 6565 Email: info@whishworks.com UNITED STATES 205 East 42nd Street NY, NY 10017 Phone: +1 646 568 9786 Email: info@whishworks.com