	File	Modified

No files shared here yet.

Overview

The underpinning SBE schema definition also allows MarketFactory to offer a vanilla FIX protocol interface. This delivers identical session and application messages as those via SBE, but in standard key=value form.

Existing client FIX engine and technology can be used with minimal effort, by integrating against our Application-level Whisperer Data Dictionary and the standard Session-level FIXT.1.1 Data Dictionary.

Use of both interfaces is supported, e.g

A Client may use the direct SBE interface for Market Data, whilst integrating via FIX for Orders.
A client may use the FIX interface for speed-to-market considerations, and build out a direct SBE interface at a later date.

Usage Guide

The FIX interface is in reality a thin abstraction layer that rests on top of Whisperer's standard SBE representation. This has the following implications for integration:

Session Layer - The Interface uses FIXT.1.1 as the session layer definition. Refer to https://www.fixtrading.org/standards/fix-session-layer/ for further details. Note that no modifications to the standard FIXT.1.1 session are required.
API version - it is the responsibility of the Client to ensure that all FIX messages conform to the schema version of the deployed Bridge. This is provided by Whisperer in every message sent to the Client in the CstmApplVerID field. (e.g. 1129=mfsbe4.18459.0.0). Any Client message that that cannot be parsed correctly will be treated as corrupted and result in a session-disconnect.
Tag Order - ordering matters and must exactly match the ordering of fields in the data dictionary.
Omitted Tags - Fields with default values do not need to be populated - they will automatically be treated as NULL. Empty 'No' and 'Has' groups can be entirely omitted. E.g NoHops, HasLegNDFFields.
Timestamp Precision - The following Session-level timestamps are published at nanosecond precision in all messages to the Client: SendingTime, OrigSendingTime, HopArrivalTime & HopNetworkTime. The Client may use any timestamp precision they wish for SendingTime & OrigSendingTime in its outbound messages - to a maximum of nanosecond precision.
Session Synchronisation - As with the SBE interface, the FIX interface utilises the NextExpectedMsgSeqNum field in the exchanged Logon messages to ensure session synchronisation. ResendRequest messages are not supported.
Sequence Numbers - As with the SBE, inbound and outbound sequence numbers are reset on a weekly basis.

Message Specification

Standard Header

The table below defines the Standard Header to be used for all Client messages:

Tag	Description	Required	Values	Example
8	BeginString	Yes	Must be "FIXT.1.1".	FIXT.1.1
9	BodyLength	Yes	Message length, in bytes, forward to the CheckSum field.	109
34	MsgSeqNum	Yes	1..n	1
49	SenderCompID	Yes	MF-created and assigned MFAPI username	MyUsername
56	TargetCompID	Yes	<VenueName>.<SessionType> VenueName is MF-defined and provided SessionType: Indicates desired session type for user, bilaterally agreed with MF. One of {Pricing \| Orders \| RFS \| DropCopy}	qa-360t.RFS
52	SendingTime	Yes	YYYYMMDD-HH:MM:SS.sssssssss The fractions of seconds may be empty when no fractions of seconds are conveyed (in such a case the period is not conveyed). It may include 3 digits to convey milliseconds, 6 digits to convey microseconds, 9 digits to convey nanoseconds.	20200812-08:31:06.527

Standard Trailer

The table below defines the Standard Header to be used for all Client messages:

Tag	Description	Required	Values	Example
10	Checksum	Yes	Three byte, simple checksum that serves, with the trailing <SOH>, as the end-of-message delimiter. Always defined as three characters.	042

Session Messages

Session-level messages used by Whisperer are a subset of the standard FIXT1.1. session definition, as defined below.

Logon

The Client Logon message differs from the SBE equivalent in that the Header TargetCompID is used to convey the desired venue name and session type.

Full details of the required fields is provided in the table below:

Tag	Description	Required	Values	Example
	Standard Header	Yes
98	EncryptMethod	Yes	Must be '0' (Unencrypted)	0
108	HeartBtInt	Yes	Integer between 0-300 inclusive. Heartbeat-generation interval in seconds.	30
141	ResetSeqNumFlag	No	If populated, must be 'N' (Do not reset sequence numbers)	N
789	NextExpectedMsgSeqNum	Yes	Provided by MFAPI Client to support MF message gap checks. If equal to the next-to-be-assigned MF sequence then Whisperer will respond with a LogonResponse message and then proceed with the session as normal. If lower, then Whisperer will respond with a LogonResponse message and immediately (re)send persisted messages or GapFills, in order. On completion, it will proceed with the session as normal. If higher, then Whisperer will respond with a Logout message to abort the session.	1234
553	Username	Yes	MF-created and assigned MFAPI username. This is the same value as the Client SenderCompID.	MyUsername
554	Password	Yes	MF-created password for user	MyPassword
58	Text	No	Free-form text string the client may wish to use for support purposes.	Start of Session
	Standard Trailer	Yes

Logout

Tag	Description	Required	Values	Example
	Standard Header	Yes
58	Text	No	Text string detailing the logout reason.	System Shutdown
	Standard Trailer	Yes

SequenceResetGapFill

Tag	Description	Required	Values	Example
	Standard Header	Yes
36	NewSeqNo	Yes	The sequence number of the next message to be transmitted.	1234
	Standard Trailer	Yes

TestRequest

Tag	Description	Required	Values	Example
	Standard Header	Yes
112	TestReqID	No	Free-form text string to be returned in resulting Heartbeat. e.g. UTC/Epoch Timestamp.	TR_678
	Standard Trailer	Yes

Heartbeat

The Client Heartbeat message differs from the SBE equivalent in that the Header TargetCompID is used to convey the desired venue name and session type. Note that the Username is not echoed back as in SBE.