FIX Transport

FIX (Financial Information eXchang) transport implementation is a module developed under the Apache Synapse project. This transport is mainly used with WSO2 ESB in conjunction with proxy services. The following class acts as the transport receiver:

org.apache.synapse.transport.fix.FIXTransportListener

The org.apache.synapse.transport.fix.FIXTransportSender acts as the transport sender implementation. These classes can be found in the <ESB_HOME/repository/components/plugins/synapse-fix-transport.jar file. The transport implementation is based on Quickfix/J open source FIX engine and hence the following additional dependencies are required to enable the FIX transport.

mina-core.jar
quickfixj-core.jar
quickfixj-msg-fix40.jar
quickfixj-msg-fix41.jar
quickfixj-msg-fix42.jar
quickfixj-msg-fix43.jar
quickfixj-msg-fix44.jar
slf4j-api.jar
slf4j-log4j12.jar

From WSO2 ESB 4.0.2 onwards, this transport supports JMX.

Download Quickfix/J from here and in the distribution archive you will find all the dependencies listed above. Also please refer to Quickfix/J documentation on configuring FIX acceptors and initiators.

FIX transport does not support any global parameters. All the FIX configuration parameters should be specified at service level.

QuickFix 4J configuration parameters can be found here

Service Level FIX Parameters

Tip

In transport parameter tables, literals displayed in italic mode under the "Possible Values" column should be considered as fixed literal constant values. Those values can be directly put in transport configurations.

Parameter Name	Description	Requried	Possible Values	Default Value
transport.fix. AcceptorConfigURL	URL to the Quickfix/J acceptor configuration file (see notes below).	Required for receiving messages over FIX	A valid URL
transport.fix. InitiatorConfigURL	URL to the Quickfix/J initiator configuration file (see notes below).	Required for sending messages over FIX	A valid URL
transport.fix. AcceptorLogFactory	Log factory implementation to be used for the FIX acceptor (Determines how logging is done at the acceptor level).	No	console, file, jdbc	Logging disabled
transport.fix. InitiatorLogFactory	Log factory implementation to be used for the FIX acceptor (Determines how logging is done at the acceptor level).	No	console, file, jdbc	Logging disabled
transport.fix. AcceptorMessage Store	Message store mechanism to be used with the acceptor (Determines how the FIX message store is maintained).	No	memory, file, sleepycat, jdbc	memory
transport.fix. InitiatorMessage Store	Message store mechanism to be used with the initiator (Determines how the FIX message store is maintained).	No	memory, file, sleepycat, jdbc	memory
transport.fix. ResponseDeliverTo CompID	If the response FIX messages should be delivered to a location different from the location the request was originated use this property to set the DeliverToCompID field of the FIX messages.	No
transport.fix. ResponseDeliverTo SubID	If the response FIX messages should be delivered to a location different from the location the request was originated use this property to set the DeliverToSubID field of the FIX messages.	No
transport.fix. ResponseDeliverTo LocationID	If the response FIX messages should be delivered to a location different from the location the request was originated use this property to set the DeliverToLocationID field of the FIX messages.	No
transport.fix. SendAllToInSequence	By default, all received FIX messages (including responses) will be directed to the in sequence of the proxy service. Use this property to override that behavior.	No	true, false	true
transport.fix. BeginStringValidation	Whether the transport should validate BeginString values when forwrding FIX messages across sessions.	No	true, false	true
transport.fix. DropExtraResponses	In situation where the FIX recipient sends multiple responses per request use this parameter to drop excessive responses and use only the first one.	No	true, false	false

For more information, see the following topics: