[This message was posted by Clive Browning of Rapid Addition Ltd <[email protected]> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/e945f5ad - PLEASE DO NOT REPLY BY MAIL.]
Hi Mahesh This is interesting, FIX engines are used in a variety of scenarios including gateways to exchanges and in routing hubs (to mention 2). Depending on the destination for the FIX messages there are several integration "methods". The easiest is obviously a destination that can handle FIX messages (and sessions) natively. But there are other standard and proprietary interfaces. Tieing down config options for FIX end points would include sender / target comp id details, ip-addresses, ports, max message size supported, default FIX session version, supported FIX message versions, heart beat interval etc. Clive > Hi Arpita, Russ, Toby, Clive, > > Sorry for the very late reply. I was looking into this topic and I > believe there are two parts of a FIX engine config - > > 1 Counterparty details - this could be standardizable but Counterparty > config for Session initiators would be different from config for > Session acceptors > > 2 Config required for FIX engine to communicate with Trading application > behind it - I think this part would be tough to standardize because > there are so many different integration methods between FIX engine and > trading application > > Regards, > K. Mahesh [You can unsubscribe from this discussion group by sending a message to mailto:[email protected]] -- You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/fix-protocol?hl=en.
