Bangalore meetup slides_dec_7th_2019
Download as PPTX, PDF2 likes632 views
The document outlines a Mulesoft meetup agenda held in Bangalore on December 7, 2019, focusing on the differences between Mule 3x and Mule 4x, alongside discussions and presentations on various aspects of the Mulesoft journey. Key points include coding habits, error handling, differences in project structures, and database handling in Mule 4. The speaker highlights that migration from Mule 3 to Mule 4 requires extensive reworking of code due to a lack of migration tools.
![All contents © MuleSoft Inc.
Databases
141414
• Multiple Database Blocks
• One Database Config Block
• DataWeave parameters in
SQL Code as prefered option
• Mule 3 • Mule 4
14
• One Database Block
• Multiple Database Config
Blocks
• #[…] working in SQL Code](https://image.slidesharecdn.com/bangaloremeetupslidesdec7th2019-191207175851/85/Bangalore-meetup-slides_dec_7th_2019-14-320.jpg)
Bangalore meetup slides_dec_7th_2019
- 1. 7th Dec 2019 : Mule 3x vs Mule 4x Bangalore Mulesoft Meetup Group
- 2. All contents © MuleSoft Inc. Agenda 2 • Introductions • Kimberly Clark Mulesoft journey • Interactive discussion about Mule 3x vs Mule 4x • Panel discussion with Mulesoft • Q&A • Networking time • Wrap-up & Lunch
- 3. All contents © MuleSoft Inc. Introductions 3 • About the organizers: • About the Speakers: A SHOW OF HANDS: Who is new to this MeetUp? About the Sponsor:
- 4. Kimberly Clark Mulesoft journey
- 5. Mule 3x vs Mule 4x What are we up to w.r.t Mule 4x..!!
- 6. All contents © MuleSoft Inc. Key Points 6 • Basic differences – Coding ’habits’ – Error handling • Reference elements differences – Salesforce – VM Queue – Databases – Scripts • DataWeave vs MEL • Munits • Project structure
- 7. All contents © MuleSoft Inc. Sample Services Concept - 1 7 HTTP • POST #1 Salesforce • Get data – simple SOQL • Get data – dynamic SOQL VM • Salesforce Data • Additional properties Database • Insert salesforce data with properties
- 8. All contents © MuleSoft Inc. Sample Services Concept - 2 8 HTTP • POST #2 Script • Prepare Query in Javascript Database • Run prepared query (select) JSON Response • Present data
- 9. All contents © MuleSoft Inc. Coding ’habits’ – properties, configurations etc. 9 • Mule 3 • Mule 4 9 • Anypoint Studio 6 – Both Community & Enterprise • Manually setting-up Maven • Property Placeholder • Message Properties, Mule Expression Language, DataWeave 1.0 • Anypoint Studio 7 – Only for Enterprise – Intellij + Mule plugin for Community • Ready-to-use Maven • Configuration properties • DataWeave 2.0
- 10. All contents © MuleSoft Inc. Salesforce 1010 • Mule 3 • Mule 4 • Single Salesforce Block • SOQL - Query Builder • Multiple Salesforce Blocks • No SOQL - Query Builder • Operations are individual connectors now in Mule4
- 11. All contents © MuleSoft Inc. Salesforce Continued..!! 1111 • Mule 3 • Mule 4
- 12. All contents © MuleSoft Inc. VM Queue 1212 • Mule 3 • Mule 4 12 • Dynamically-set queue names • Message property • Need to define queue names ’up-front’ in VM properties • No message properties (?) – or your speaker does not know how to do it
- 13. All contents © MuleSoft Inc. VM Queue – Continued..!! 131313 • Mule 3 • Mule 4
- 14. All contents © MuleSoft Inc. Databases 141414 • Multiple Database Blocks • One Database Config Block • DataWeave parameters in SQL Code as prefered option • Mule 3 • Mule 4 14 • One Database Block • Multiple Database Config Blocks • #[…] working in SQL Code
- 15. All contents © MuleSoft Inc. Database Continued..!! 151515 • Mule 3 • Mule 4
- 16. All contents © MuleSoft Inc. Databases – known issues in Mule 4 161616 • Database connections Out-of-memory on Mule Server caused by db-connector Database connections are not being closed after flow processing end: https://help.mulesoft.com/s/question/0D72T000003t3JO/database-connections-are-not-closing Database connectors are consuming a lot of memory, causing OutOfMemory exception Solution: Use try-catch block for each database call, and configure max/min pool size in Database Config. Solution: Upgrade mule-db-connector from 1.4.x to 1.5.x in pom.xml Note: Your speaker may not be aware if this is already fixed in latest release..!!
- 17. All contents © MuleSoft Inc. Scripts 171717 • Mule 3 • Mule 4 • Multiple blocks for scripting – One block also available – so a bit ’messy’ • message.setInvocationPropert y(..) as a method to set any number of variables you want in one script • One block for scripting • No functions to set multiple variables – or your speaker does not know how to do it – You can build your payload/variable, so variables values can be set-up as script- output elements, and re-write to Mule Variable.
- 18. All contents © MuleSoft Inc. Scripts Continued..!! 181818 • Mule 3 • Mule 4 18
- 19. All contents © MuleSoft Inc. Error Handling 191919 • Mule 3 • Mule 4 • * Exception Strategy – Catch – Choice – Custom – Reference – Rollback – Mapping • Try-Catch block • On Error Continue / On Error Propagate
- 20. All contents © MuleSoft Inc. Error Handling Continued..!! 2020 • Mule 3 • Mule 4 20
- 21. All contents © MuleSoft Inc. Summary 212121 Mule 3 and Mule 4 has differences we cannot underrestimate during migration project planning. So far – no migration tool. Each service we need to re-write code we have in Mule 3 to be compatible with Mule 4. Not that hard to re-learn – useful course: https://training.mulesoft.com/course/mulesoftu-mule443 In my opinion, Mule 4 is more mature in concept – but has some difficulties we need to overcome as is quite fresh platform.
- 22. All contents © MuleSoft Inc. Articles 222222 • High-level article about Mule 4 migrations: https://blog.bluesoft.com/mule-4-migration/ https://docs.mulesoft.com/mule-runtime/4.2/migration- process • MuleSoft Documenation https://docs.mulesoft.com/mule-runtime/4.2/migration-core https://docs.mulesoft.com/mule-runtime/4.2/migration-cheat- sheet
- 23. Vikram Kulkarni Panel Discussion with Mulesoft
- 24. All contents © MuleSoft Inc. Questions??
- 25. See you next time Please send topic suggestions to the organizers Next Meet up: Q1 2020
- 26. Networking time Engage yourself in interesting discussions with your neighbors!