The document discusses the Mulesoft VM transport and its advantages for breaking complex integrations into smaller, decoupled parts for better control and high performance. It provides a sample use case of exposing a CXF web service using two separate flows connected by a VM queue, and explains how message properties can be preserved across the VM by storing them before sending to the outbound endpoint.

1. Mulesoft
VM Transport Reference
https://docs.mulesoft.com/mule-user-guide/v/3.8/vm-transport-reference
Kumar Gaurav
k10gaurav@gmail.com

2. Agenda
• About
• Reason
• Advantages
• Sample Use Case
• Conclusion

3. About
Mule supports VM transport, which by default uses in-
memory queues but can optionally be configured to use
persistent queues.
The VM transport has often been used to implement
complex integrations, where the flow is big and
complex and need to be broken into smaller parts for
better control.

4. Reason
One main reason to use this architecture, is that we can
fragment the logic into smaller pieces and can connect
it and decouple each event, and is done mainly for high
performance and high control.

5. Advantages
• Advantage with breaking the flow with a queue :-
• Help to control on each event queue
• It also reduce the complexity in the Mule flow, where there is a large Mule
flow with different functionality.
• The service can be well-conditioned to load
• Preventing resources from being over committed when demand exceeds
service capacity.
• The message flow will be faster compared to other queue services like
ActiveMq.

6. Sample Use Case
So now, we will see how easy it is to configure and expose a CXF web service
with VM component in Mule. And for this we need to have 2 separate flow to
expose the web service.

7. Continue…
You can see that we have used a set property after CXF component to store
the method name which is actually SOAP action here as the message
properties generally get lost if passed through a VM queue.

8. Continue…
The Mule configuration file will have below snippet where you can see in flow2,
the SOAP action stored is provided as entry point for web service
implementing java class

9. Continue…
Now, we let’s start testing in SOAPUI and see that the web service response to
check actual working of it.

10. Conclusion
So, if we are exposing a web service using VM endpoints the first thing we
should keep in mind is to store the outbound properties of the message before
sending the message to the VM outbound endpoint .
The main reason of doing is to protect the properties and get it in our next flow,
since a message may loose it’s outbound properties while passing through a
VM.

11. Thank you!