Used to establish a connection between a TT FIX Gateway and a third-party FIX acceptor
From TT FIX Gateways to a third-party FIX acceptor and then from a third-party FIX acceptor to TT FIX Gateways
Tag # | Field Name | Req’d | Data Type | Comments | |
---|---|---|---|---|---|
Component: Standard Header | Y | 35=A (MsgType) | |||
96 | RawData | C | String |
Logon password Condition: Will be sent when the TT FIX Gateway initiates a connection. The third-party FIX acceptor need not send this in the response. |
|
98 | EncryptMethod | Y | int |
Method of encryption As TT FIX Gateway does not support encrypted logons, you must set the value to 0 (None/Other). |
|
108 | HeartBtInt | Y | int |
Heartbeat interval (seconds) |
|
141 | ResetSeqNumFlag | N | Boolean |
Whether to reset the sequence numbers on both sides of the FIX session Valid values include Y and N (default). |
|
Component: Standard Trailer | Y |
The Logon (A) message is used by a TT FIX Gateway to begin a new or continue an existing session with a third-party FIX acceptor.
The following data flow illustrates a typical logon sequence between a TT FIX Gateway and a third-party FIX acceptor:
The TT FIX Price Gateway will only support non-persistent FIX sessions. In other words, it will always send a Logon (A) message with Tag 34 (MsgSeqNum)=1 and Tag 141 (ResetSeqNumFlag)=Y when initiating a connection. As a result, the FIX session will terminate when the connection does.
When the TT FIX Order Gateway is started for the first time, it will send a Logon (A) message with Tag 34 (MsgSeqNum)=1. When there are unscheduled restarts, the standard FIX message sequence number negotiation will take place. After scheduled message sequence number resets, the TT FIX Order Gateway will send a Logon (A) message with Tag 34 (MsgSeqNum)=1.