|Table of Contents|
FIXEdge is a server application that provides FIX connectivity for standalone client applications. Client applications (hereinafter Clients) communicate with FIXEdge via FIX or via one of the supported transport protocols (e.g. Simple Sockets, TIBCO, CORBA).
FIXEdge can also be customized to use other connectivity bridges like CMS, ISE, INET etc.
Clients can use FIX protocol versions 4.0 - 4.4 inclusive and 5.0 over FIXT1.1.
Supporting standard FIX protocol
FIXEdge uses FIX Antenna C++ on a FIX layer and thus inherits all FIX Antenna's functionality.
- 100% FIX standard compliance:
- FIX 4.0, 4.1, 4.2, 4.3, 4.4, 5.0, 5.0 SP1, 5.0 SP2
- FAST 1.1
- Supports all FIX message types (pre-trade, trade, post-trade, market data, etc.)
- Supports user-defined tags
- Message validation
- Customizable FIX protocol. User can create his own FIX dialect e.g. define extra field for a message, change "required" attribute, etc. in a friendly XML format
- Multiple session management
- Supports up to 200 concurrent sessions on a single instance on recommended hardware. Number of concurrent sessions can be increased if more CPUs are added
- Each session can be configured separately. FIX Dialect can be configured for session
- Guaranteed delivery
- Relies on the store and forward technique
- Flat files are used for persistence to achieve maximum performance
- Standard FIX routing based on DeliverTo and OnBehalfOf fields
Transport protocols supported by FIXEdge
Additional non-FIX transports are available via pluggable transport adaptors:
|Object message middleware|
|IBM MQ||Session is a set of queues: for incoming messages, for outgoing messages and for errors. Raw FIX message is packed into MQ message as blob. In case of conversion to FIXML, a corresponding XML is packed into MQ message as blob. See IBM MQ Series Adaptor for details. |
Session is a TIBRV session, raw FIX message is packed into TIB message as blob.
|JMS||Topic and queue modes are supported, raw FIX messages is packed into JMS message. See JMS Transport Adapter for details.|
FIX engine, FIX session and FIX message are COM objects.
FIX engine, FIX session and FIX message are CORBA objects.
|Raw message middleware|
|Domain Socket||Raw FIX messages are sent via domain sockets.|
|UDP||Raw FIX messages are sent via UDP.|
|Named Pipes||Raw FIX messages are sent via named pipes.|
|HTTPS||Raw FIX messages are sent via HTTP.|
|Simple Sockets||Raw FIX message are sent via TCP sockets; several XML messages form light-weight session level protocol for identification and heart-beating.|
|SMTP||Raw FIX messages are sent via SMTP (to email); FIX email message can be automatically converted to a standard email message.|
FIXEdge could be deployed on the following platforms:
|Windows (Windows Server 2003, Windows 7, Windows Server 2008 R2, Windows 8, Windows Server 2012)|
|Linux RHEL/CentOS 6|
The sequence and peculiarity of installation are described in part FIXEdge Installation Guide.
The easiest way of using FIXEdge is running just one instance on a single machine. Instance listens to incoming connection on a specified TCP port and can initiate connections as configured. The whole functionality is available, including all Transport Adaptors and FIXICC monitoring tools. FIXICC GUI can be ran either on the same workstation (the first picture) or on a separate workstation (the second picture). In both cases FIXICC GUI can be connected to FIXEdge either directly or through FIXICC Agent. But to access all the functionality of monitoring and configuration the connection through FIXICC Agent is required.
It is possible to install more than one instance of FIXEdge on a single machine. All instances work independently (i.e. have separate list of sessions, independent configuration and log files), however they can be managed using common FIXICC control application. Of course, several instances of FIXEdge can be started on different machines.