You have chosen to sponsor your bid up to a maximum amount of .
Goals of this project.
Create a POC that proves the Mule 3.4 ESB config and or Java custom code required for Mule to be a TCP server and an appropriate Java-based TCP client tester.
=========== Back ground =============
I want to configure Mule to be a TCP Server.
Example full realized flow: I want to receive WMQ messages from external sources, then output to TCP for client(s) to connect and consume.
I have proven so far:
- Mule as TCP Client to Poll
- Mule as a basic TCP echo
- Mule to Receive WMQ
But I can't seem to understand how to receive message in one side of a flow and then have then waiting to be received by a connected TCP client.
An example of a real-life use-case is I have a third party-vendor who wants to be a TCP client and connect to my environment i.e. I act as the TCP server (Within Mule). They can then receive messages for me once they connect, and they can also send me information if they wish one they are connected.
The answer may require custom code maybe my own TCP protocol? or Custom Mule Component
Please find me the solution with appropriate code to demonstrate.