Mule Flows & Variable Persistence

Quick read to fully understand flow and variable persistence in Mule

Transcript

1. Flows & Variable Persistence A slide deck illustrating variable persistence in Mule
2. Read on for • Variable persistence between flows and processing strategies • Impacts of transport barriers, using VM Queues • 3Tests to illustrate
3. Test I: Setup • Two Flows, • Flow-A sets a flow variable and a session variable with the values 1 and 2 respectively • LogVariables prints the value of each to the console
4. Test I: Results Flow-A Flow-B So flow and session variables only exist in their defined/referenced flows, not globally across the whole project
5. Test II: Setup • Two Flows, • Flow-A sets a flow variable and a session variable with the values 1 and 2 respectively • LogVariables prints the value of each to the console, at each stage
6. Test II: Results • Flow and Session variables persist through Flow References
7. Test III: Setup • Two Flows • Request- Response VM queue instead of flow Ref • Logger logs all variables (including Flow B’s variables)
8. Test III: Results • The Flow variables cannot cross the VM queues (either direction) • Point 3 still logs myFlowVarA as 1, showing that the flowVar’s scope is the entire flow, irrespective of the existence of the VM queue • mySessionVarA is always set, showing that session variables persist across the VM queue
9. Hope this Helps • What other tests would be interesting? • Comment Below & Go Explore!