More Related Content
What's hot
What's hot (19)
Similar to Indore MuleSoft Meetup #4 : Demystifying Error Handling & Snowflake Integration
Similar to Indore MuleSoft Meetup #4 : Demystifying Error Handling & Snowflake Integration (20)
Recently uploaded
Recently uploaded (19)
Indore MuleSoft Meetup #4 : Demystifying Error Handling & Snowflake Integration
- 1. July 10, 2021 Indore MuleSoft Meetup Group Demystifying Error Handling & Snowflake Integration
- 2. 2 ● Introductions ● Error Handling ● Snowflake Integration ● Q&A ● Quiz Agenda
- 3. 3 ●About the Organizers Introductions Chetan Joshi Lead Engineer Apisero Certified MuleSoft Integration Architect Anand Joshi System Analyst Hexaware Certified MuleSoft Integration and Platform Architect Shivam Khandelwal MTS Salesforce Certified MuleSoft Platform Architect
- 4. 4 ●About the Speakers : Introductions Shekh Muenuddeen Solution Architect Apisero Certified MuleSoft Integration and Platform Architect MuleSoft Mentor, Leader and Forum Moderator 8+ years of Experience in Integrations Shivam Khandelwal - Member of Technical Staff - Salesforce - Certified MuleSoft Platform Architect - MuleSoft Leader - 7+ years of Experience in MuleSoft and Java -
- 5. 5 ● Both the Speakers and Hosts are organizing this meetup at individual capacity. We are not representing our Organisations here. ● This presentation is strictly for learning purpose only. ● We do not hold any responsibility that same solution will work for your business usecase also. ● This Presentation is not meant for any promotional activities. Safe Harbor Statement
- 7. 7 Errors that occur in Mule belong to one of following two major categories: ● System Errors ○ Mule throws system error when an exception occurs at the system level and no mule event is involved. ○ A system error handlers manages exceptions that occur ■ During application startup ■ When a connection to an external system fails ○ When a system error occurs, Mule sends an error notification to registered listeners, logs the error, and if the error is caused by a connection failure, executes a reconnection strategy. ● Messaging Errors ○ Mule throws a messaging error (a Mule error) whenever a problem occurs within a flow of a Mule app, where Mule events and the messages they contain are processed ○ You can handle these messaging error with ■ Default Error Handling ■ On Error Components ● This is built in error component inside flow. ● You can have any number of components to process error. Mule Error Types
- 8. 8 Error handlers can be added at ● Application level (Global Error Handler) ● Flow level ● Processor level (Try scope) Creating Error Handlers
- 9. 9 ● Error handlers can contain one or more error handling scopes ○ On Error Propagate ■ All processors in this error handling scope are executed ■ At end of the scope ● The rest of flow that threw the error is not executed ● Error is re thrown up to next level and handled there ■ The HTTP listener returns an error response ○ On Error Continue ■ All processors in this error handling scope are executed ■ At end of the scope ● The rest of flow that threw the error is not executed ● The event is passed to next level as if the flow execution has completed successfully ■ The HTTP listener returns an successful response Adding Error Handling Scopes
- 10. 10 ● This is laziest way of handling error ● If you don’t handle any error Mule will handle in its own way ● What is Mule way to handle error? ○ When a flow is processing a Mule message that raises an error, the normal execution of the flow stops ○ Transfer to default error handler ○ Propagates the error Following example is for default error handling Default Error Handling
- 11. 11 ● Description: A description regarding the problem #[error.description] ● Type: A type, used to characterize the problem and allow routing within an error handler #[error.errorType] ● Cause: The underlying Java Throwable that resulted in the failure #[error.cause] ● Message: An optional Mule Message regarding the problem #[error.errorMessage] ● Child Errors: An optional collection of inner errors, used by elements like Scatter-Gather to provide aggregated route errors. #[error.childErrors] 5 Components of Error Object
- 13. 13 • Sub-Flow doesn’t have Error Handling scope . • So it’s just Flow and a Private flow where you can place On-Error-Propagate and On-Error-Continue inside “Error Handling” block. • Either it is Propagate or Continue, Mule Executes all the components within that block. Remember : The error will route to error-handling only if it identifies that the errorType of that error is handled or match expression if provided errorType is combination of Namespace and Identifier : Eg : HTTP:UNAUTHORIZED namespace = HTTP Identifier = UNAUTHORIZED Error Handling
- 14. 14 Raise Error
- 15. 15 Error Handling - Mule 3 vs Mule 4 Mule 3 Mule 4 • Missing error handling at processor level • Using “try” scope processor level error handling can be achieved • Error handling is not possible at sub flow level • Error handling at subflow level can be done using “try” scope • Catch exception strategy can be used to avoid propagating exception to parent flow • On error continue process errors and doesn’t propagates error • Rollback strategy handles errors that occur in a flow that involve a transaction • Transaction are possible using try scope • Choice exception strategy catches and evaluates a type or content of exception. • Error handler with on-error components can have multiple exception strategy • Custom errors can be raised with groovy script or Java code • Custom error can be raised using Raise error. • Custom error mapping is not possible • Custom error mapping of existing exception is possible and it allows granular error handling
- 16. Demo - Error Handling
- 18. Content ▪ What is Snowflake ▪ How is Snowflake different as compared to other Data Warehouses ▪ How to integrate Snowflake with Mule 4 ▪ Demo ▪ QA
- 20. Data Platform as a Cloud Service Snowflake is a true SaaS offering. More specifically: ▪ There is no hardware (virtual or physical) to select, install, configure, or manage. ▪ There is virtually no software to install, configure, or manage. ▪ Ongoing maintenance, management, upgrades, and tuning are handled by Snowflake.
- 22. Connecting to Snowflake • A web-based user interface from which all aspects of managing and using Snowflake can be accessed. • Command line clients (e.g. SnowSQL) which can also access all aspects of managing and using Snowflake. • ODBC and JDBC drivers that can be used by other applications (e.g. Tableau) to connect to Snowflake. • Native connectors (e.g. Python, Spark) that can be used to develop applications for connecting to Snowflake. • Third-party connectors that can be used to connect applications such as Mule 4 Connector
- 23. Snowflake Mule 4 Connector 23
- 24. Demo - Snowflake Integration
- 25. Trivia Quiz
- 26. 26 ● Share: ○ Share using the hashtag #MuleSoftMeetups ○ https://meetups.mulesoft.com/indore/ ● Feedback: ○ Fill out the survey feedback and suggest topics for upcoming events ○ Contact MuleSoft at meetups@mulesoft.com for ways to improve the program What’s next?
- 27. Thank you