: Instead of building individual "point-to-point" connections between every system (which is hard to manage), Cloverleaf serves as a central engine. Each system connects once to Cloverleaf, which then manages the distribution of data.
: This is the central dashboard used to monitor message traffic, stop/start threads, and troubleshoot errors.
In NetConfig, go to the "Inbound" tab of your source thread. Add a "Route Data" entry. Point it toward your destination thread and select the Xlate file you created. This tells Cloverleaf to take data from System A, run it through the map, and send it to System B. Testing and Troubleshooting
