Objective: Demonstrate the capability of switching between FIX versions, for example, FIX4.0 to FIX4.1.
- You will need the two sample FIX applications that come with Quickfix/J (Banzai and Executor). Configure the two applications to establish sessions with Synapse.
- Add the following lines to the
FIX40-synapse.xml can be found at
$ESB_HOME/repository/samples/resources/fix. This is a custom FIX data dictionary file that has added tag 150,151 to the execution messages (35=8) of FIX4.0. Make sure the
DataDictionary property of the
banzai.cfg points to this data dictionary file.
- Add the following lines to the Executor configuration file (
- Start Banzai and Executor using the custom configuration files.
- Enable FIX transport in the Synapse
- Configure Synapse for FIX samples. We will be using two custom configuration files for Synapse in this sample. These two custom configuration files can be found at
ESB_HOME/repository/samples/resources/fixdirectory. The two files are called
synapse-sender-m.cfg. You can point your Synapse configuration to these two files (this is already done in the supplied
synapse_sample_261.xmlfile) or you may create copies of them and point the Synapse configuration to the copies. In either case, make sure that the properties like
FileLogPathin the two files point to valid locations in your local file system.
Open up the
$ESB_HOME/repository/samples/synapse_sample_261.xmlfile and make sure that
transport.fix.AcceptorConfigURLproperty points to the
fix-synapse-m40.cfgfile described above and
transport.fix.InitiatorConfigURLpoints to the
synapse-sender-m.cfgfile described above. Once done you can start the Synapse configuration numbered 261: i.e.
wso2esb-samples.sh -sn 261
Synapse creates a new FIX session with Banzai at this point.
- Send an order request from Banzai to Synapse. For example, Buy DELL 1000 @ MKT.
Synapse will forward the order request from FIX4.0 to the Executor that accepts FIX4.1 messages. Executor will send an ACK and an execution back to Banzai.
Configuring Sample FIX Applications
If you use a binary distribution of Quickfix/J, the two samples and their configuration files are all packed to a single JAR file called
quickfixj-examples.jar. You will have to extract the JAR file, modify the configuration files and pack them to a JAR file again under the same name.
You can pass the new configuration file as a command line parameter too, in that case you do not need to modify the
quickfixj-examples.jar. You can copy the config files from
$ESB_HOME/repository/samples/resources/fix folder to
$QFJ_HOME/etc folder. Execute the sample apps from
./banzai.sh/bat ../etc/banzai.cfg executor.sh/bat ../etc/executor.cfg.
Locate and edit the FIX configuration file of Executor to be as follows. This file is usually named
Locate and edit the FIX configuration file of Banzai to be as follows. This file is usually named
FileStorePath property in the above two files should point to two directories in your local file system. The launcher scripts for the sample application can be found in the bin directory of Quickfix/J distribution.
Setting up FIX Transport
To run the FIX samples used in this guide, you need a local Quickfix/J (http://www.quickfixj.org) installation. Download Quickfix/J from: .
To enable the FIX transport for samples, first you must deploy the Quickfix/J libraries into the
repository/components/lib directory of the ESB. Generally, the following libraries should be deployed into the ESB.
Then uncomment the FIX transport sender and FIX transport receiver configurations in the
repository/conf/axis2.xml. Simply locate and uncomment the
FIXTransportListener sample configurations. Alternatively, if the FIX transport management bundle is in use, you can enable the FIX transport listener and the sender from the WSO2 ESB management console. Login to the console and navigate to " " on management menu. Scroll down to locate the sections related to the . Simply click on the "Enable" links to enable the FIX listener and the sender.