Overview
The Genesis FIX module provides all the tools you need to integrate with your counterparties using the industry-standard FIX (Financial Information eXchange) protocol.
Our FIX Gateway comes pre-packaged with a range of configuration options, allowing it to adapt to your connectivity requirements. As well as support for multiple sessions, initiating and receiving connections, our Gateway has a range of configurations for message and session state storage, allowing it to seamlessly recover in any failover scenario.
In addition, the module comes with a suite of pre-packaged operational tools for managing session status, connectivity and security. With built in audit capability, you can have your entire message log at your fingertips.
We also offer translation modules that plug directly into our core data streaming components. You can generate your own API for any customisations in the FIX dialect, and translate seamlessly between your application data schema to the required FIX version.
Key Features
The Genesis FIX component provides a gateway process to communicate with external parties via the FIX protocol.
Outbound FIX
- For outbound FIX messages, you have to create Streamers that listen to specific tables and views in the application’s database.
- The outbound Streamer streams data updates to the outbound Streamer Client.
- The outbound Streamer Client transforms the data into a FIX message, and passes it to the FIX gateway. From there, the message is sent to the external system you are integrating with.
Inbound FIX
- Inbound FIX messages arrive through the FIX gateway and are written to a table in the data server called FIX_IN.
- You need to create a Streamer to monitor this table and stream the data to the relevant inbound Streamer Client (or Clients). The Streamer Client transforms the data to conform to the Genesis data set and passes it to the application’s Event Handler.
