|Table of Contents|
FIX Edge FIXEdge is a server application that provides FIX connectivity for standalone client applications. Client applications (hereinafter Clients) communicate with FIX Edge FIXEdge via FIX or via one of the supported transport protocols (e.g. Simple Sockets, TIBCO, CORBA).
FIX Edge FIXEdge can also be customized to use other connectivity bridges like CMS, ISE, INET etc.
|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. See TIB RV Adaptor for details.
|JMS||Topic and queue modes are supported, raw FIX messages is packed into JMS message. See JMS Adaptor for details.|
FIX engine, FIX session and FIX message are COM objects. See COM/DCOM Adaptor for details.
FIX engine, FIX session and FIX message are CORBA objects. See CORBA Adaptor for details.
|Raw message middleware|
|Domain Socket||Raw FIX messages are sent via domain sockets.|
|UDP||Raw FIX messages are sent via UDP. See UDP Adaptor for details.|
|Named Pipes||Raw FIX messages are sent via named pipes.|
|HTTPS||Raw FIX messages are sent via HTTP. See HTTPs Adaptor for details.|
|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:
The sequence and peculiarity of installation are described in part FIXEdge Installation Guide.
It is possible to install more than one instance of FIX Edge 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.