Software for brokers, markets, and investors
Solutions

FIX Connectivity and Order Routing

The FIX Protocol (www.fixprotocol.org) has evolved as the de facto standard in broker-exchange connectivity. The vast majority of exchanges and most universal brokers now offer order routing through the FIX protocol.

Mannes Technology offers a FIX engine which greatly simplifies connecting to exchanges or brokers. This FIX Engine is a class library which implements all important aspects of the FIX protocol in all of its versions, from 4.0 to 4.4. Our FIX Engine offers the following benefits:

The FIX Engine can be combined with a simple order management system that can store orders and operations in a database. In conjunction with this OMS, we offer adapters to MEFF (the FIX 4.4-based MEFFGate system), which already implement the entire logic used by MEFF.

Naturally, the FIX engine also forms the base for the FinanceGear Routing Integration.

Using the FIX Engine

The FIX Engine is implemented in a class library which contains a collection of classes that greatly simplify implementing any particular version of FIX. You can use the library directly with different versions of FIX (4.0 until 4.4), or adapt to a new dialect or implementation of FIX.

 

If you want to connect to a standard-compliant FIX engine, the steps to connect your applications are simple:

If you use a modern IDE, you will never have to read documentation: with autocomplete, your code will practically write itself.

 

Adaptability to FIX Dialects

But even if you are dealing with a non-standard dialect of FIX, adaptation is easy.

One of the key advantages of the MTFIX Engine is its adaptability to FIX dialects. Dialects of FIX and non-standard implementations are a fact of life, and our FIX engine gives you the flexibility you need. The process of adapting to a dialect of FIX - even non-standard ones - is as follows: an XML file is created that specifies which messages are supported; and which fields insides these messages are supported, required, or optional (see the sample definition of FIX 4.0 and a minimal subset of 4.4). A utility program then converts this XML file to class definitions which wrap each message and its fields inside objects. Once this code is generated, all that's left is to write the application. (picture here: XML to code + class diagram) Even if your peer's FIX uses a non-standard implementation of the protocol, adaptation is easy: our FIX engine lets you create custom protocol implementations based on standard versions of FIX (source code is provided).This is done by subclassing the "Session" class and overriding a few methods.

Existing Adapters

We have build adapters for the following systems:

Please contact us if you would like to know more about integrating a FIX-based system.