Transaction Management - Local - Mule 4

***************************************************************************************
Links for other videos:
Dataweave: • DataWeave
Flow Control: • Flow Control
Mule scopes: • Mule Scopes
Mule Basics & Miscellaneous : • Mule Basics
Error Handling: • Error Handling
File Module: • File Module
Object Store: • Object Store
Database : • Database Module
VM Connector: • VM Connector
Batch Processing: • Batch Processing
Salesforce & Mulesoft Integration: • Salesforce - Mulesoft ...
HTTPS (1 way SSL & 2 way SSL): • HTTPS
Munits (created Manually): • Munits
Transaction Management: • Transaction Management
Alerts & Monitoring: • Alerts & Monitoring
Anypoint MQ: • Anypoint MQ

[@prathameshsuryavanshi4201]

Very helpful session, thank you!

[@soogureddys1341]

The way you explained the concept is even first time viewers also understand 90 percent 👍 Great explanation and Very Good concept, thank you sir 🙏🏻

[@IntegrationWorld]

Hi Reddy, Thanks for your words. I am glad that it's useful for you

[@ankithsharma725]

Thank you sooooooo Much im grateful to your explanation.

[@amanbesaw]

Thank you. You explain in great detail. Good job.

[@arunkumar-xu8nr]

Clearly explained 👏👏

[@ramreddy9574]

Good explanation with each step

[@harimetkari2202]

Very good

[@akarshkumarJavvaji]

Very good explanation and important stuff !! Thanks for sharing Vijay !!

[@IntegrationWorld]

Glad it's helpful 😀

[@amanbesaw]

If you’re using object store (store and retrieve) to watermark last entered record, you wouldn’t be able to roll that back with transaction local correct? I don’t see the option in the module. So even though the flow is rolled back if an error occurs, the object store will assume it’s been recorded even though it hasn’t? Thank you

[@IntegrationWorld]

@amanbesaw,
yes, object store entries can't be rolled back and object store operations doesn't support transactions.
the only connectors that support transactions by default are VM, JMS & DB.
The below url is for your reference.
docs.mulesoft.com/object-store-connector/1.2/#object-store-limitations

[@janeshen1506]

Very good explanation for transaction actions. It works for rollback when inserting into table and error on next update table. But not rollback when call multiple Stored procedures. Any idea on rollback when call multiple SPs?

[@mulesoftapi2643]

It is more advanced level explanation ,for beginners like me ,do not know how
to integrate database ,query write,need step by step explanation, it will helpful for beginners to better understanding concepts..

[@IntegrationWorld]

Hi, I will try to create one video on Database module.

[@IntegrationWorld]

Hey @Mulesoft Api, Check my Database playlist ua-cam.com/play/PLt74Wn6k8TfCYOn_bNILu04alitK59hc4.html

[@ThirupathiMasula]

hi sir, How to SET TRANSACTION Statement , i want to see the data in DB , after mule degguer go to next component.

[@mufaddalf4377]

In case of for each loop when we are doing inserts for each iteration. How do we manage Transactions in that case ? Do we keep try block inside or outside the for each loop and how we choose the Transactional Action. Kindly let me know

[@IntegrationWorld]

Hi,
You have to keep try scope inside for-each & also use on error continue inside try so even if a record's insert or update fails the error control goes to on-error continue, so it continues for processing of next record.
Regarding transactional action, it depends on the scenario. As explained in "Transaction Management - XA" & "Transaction Management" - Local, please choose accordingly.
Thanks,
Vijay Vaka