Warning: A non-numeric value encountered in /home/customer/www/archive.ricston.com/public_html/wp-content/themes/Divi/functions.php on line 5766

We at Ricston have had our fix connector available for a few years now and we recently decided to create a version built with Devkit.

The FIX protocol has evolved over time. It’s now more than a decade since its invention by Fidelity and Solomon Brothers. FIX connectivity is the most popular connectivity solution and caters for equities trading, futures, options or fixed income or even foreign exchange (FX) trading and normal online stock trading.

FIX has dominated the market and become a standard solution for any market or broker which is trying to develop connectivity with the market. The protocol allows development of financial orders and processes with other brokers within a shorter period of time because of standardization. Several FIX protocol versions exist: FIX4.0, FIX4.1, FIX4.2 and FIX4.4 and newer. Looking at the industry wide statistics it appears that most firms support FIX 4.2 but the majority of versions are typically supported.

In Feb of 2013 the connector was ported over to be compatible with Mule 3. We are now happy to announce that we’ve developed a Devkit version (you can drag and drop in Mule studio + XML auto-completion) that supports Mule 3.x (tested with Mule 3.4.0). The implementation of this transport is based on version 1.5.3 of QuickFix/J.

So presently we support Fix inbound and outbound endpoints and an example real world scenario can be seen below:


The above flows have a FIX inbound and FIX outbound endpoint with Java components providing the in house custom FIX logic.

With our new connector you can use them for an inbound and outbound Fix endpoint respectively, as follows: