In Depth
Features of InfoReach FIX Engine

Automatic Reconnect

A FIX Client Engine can attempt to reestablish lost FIX connections automatically.

Automatic Resends

An engine can reply to the Resend Requests that it receives from counterparts.

Complete FIX Server

The FIX Engine library includes a multi-threaded FIX server.

Configurable Database Schema

Users can define the layout of any database table that stores FIX messages. They can add dedicated FIX Message field columns to their database as needed.

Configurable Database Schema

Cross-DBMS Connectivity

FIX Engine is compatible with many databases, such as Oracle, MS SQL, Sybase, PostgreSQL or others for which a JDBC driver is available.

Custom Log Levels

You can specify which FIX message type to persist into the database.

Database Optimization

Engine can store its sent and received FIX messages into separate database tables. The FIX Engine is able to maintain multiple dedicated database connections for each database table that it utilizes to store messages. Furthermore, the FIX Engine is capable of writing its FIX messages into different databases and/or tables for different FIX connection concurrently. 

Through the FIX Engine configuration one can specify the utilization of tables and DB connections the Engine will use to persist FIX messages.

Distributed Object Middleware

InfoReach FIX Engine can use various object middleware for its inter-process communications (RMI, CORBA, and others).

Dynamic Configuration

Adding or removing of FIX connection does not require the restart of the engine.

Event Logging

A flexible and configurable event logging facility is a part of the product. You may choose to provide an alternative event logging implementation in order to integrate the engine with an existing corporate alert and event-monitoring infrastructure.

Fault Tolerance

A FIX Engine can be deployed to form clusters consisting of primary and secondary engines. A client application utilizing an engine cluster will not experience any service disruption should the primary FIX Engine fail.

File-based persistence

To achieve higher message throughput INFOREACH FIX Engine can utilize file-based storage of FIX messages.

Guaranteed Message Delivery

A client application will always be notified of all messages in the order that the engine received them.

High Availability

You can deploy a FIX Engine in standby mode so that it takes on the state of another FIX engine in case of a system failure.

IP Filtering

FIX server IP filter. IP filter allows you to specify valid IP addresses of counterpart FIX engines from which you accept connections.

Java Implementation

InfoReach FIX Engine is implemented 100% in Java and can be deployed on a variety of operating systems.

Loopback Connection Mode

The engine’s loopback connection behaves just like a regular FIX connection. The only exception is that it does not have a FIX session layer. Client applications can use a loopback connection as a messaging queue.


Separate threads for database persistence and each client-server connection assure optimal engine operation.

Multihome System Support

For computers equipped with two or more network interface cards, FIX Engine can be “bound” to a specified network adapter. 

Multiple Connectivity

A single FIX Server can accept connections from multiple FIX clients. A single FIX client can connect to multiple FIX servers.

Operation Modes

You can use FIX Engine in client, server and loopback mode. 

Optimized Performance

InfoReach FIX Engine is optimized to handle extreme message throughput and volumes.

Supported Protocol Versions

A single FIX Engine supports the FIX Protocol Versions 4.0, 4.1, 4.2, 4.3, 4.4 and FIXML. The engine can handle multiple connections with differing protocol versions simultaneously.

Publish/Subscribe Model

Engine messages and state events are delivered to client applications via publish/subscribe middleware. Various JMS providers can be used (e.g. InfoReach Event Service, TIBCO, SmartSockets, JMQ, MQ Series, etc).

Persisted Queues

This feature allows the engine to continue accepting messages from the client application while a FIX client connection is not active. Once the FIX client connection is established, the engine can automatically send all pending messages. This persistent queue prevents the loss of the FIX messages while receiving them from an application and sending them to a counterpart.

Pending Queues Threshold

You can configure the maximum sizes of the message queues.

Rule-based Gateway

InfoReach FIX Engine can be easily configured as a rule-based pass-through FIX message gateway.


InfoReach FIX Engine components can be distributed across multiple processes on same machine as well as across multiple machines.

Connect/Disconnect/Reset Schedule

You can configure FIX to automatically connect, disconnect or reset its own FIX connections.

Connect/Disconnect/Reset Schedule

Configurable Socket Parameters

You can configure various socket parameters. SO linger and timeout, send and receive buffer sizes, connection backlog, keep alive, TCP No Delay, SSL keystore and cipher suits.

Configurable Socket Parameters

State Recovery

FIX Engine can fully recover its state from FIX messages stored in a database.