Sample 257: Proxy Services with the FIX Transport
<definitions xmlns="http://ws.apache.org/ns/synapse">
<proxy name="OrderProcesserProxy40" transports="fix">
<target>
<endpoint>
<address
uri="fix://localhost:19876?BeginString=FIX.4.0&SenderCompID=SYNAPSE&TargetCompID=EXEC"/>
</endpoint>
<inSequence>
<log level="full"/>
</inSequence>
<outSequence>
<log level="full"/>
<send/>
</outSequence>
</target>
<parameter name="transport.fix.AcceptorConfigURL">
file:repository/conf/sample/resources/fix/fix-synapse.cfg
</parameter>
<parameter name="transport.fix.AcceptorMessageStore">file</parameter>
<parameter name="transport.fix.InitiatorConfigURL">
file:repository/conf/sample/resources/fix/synapse-sender.cfg
</parameter>
<parameter name="transport.fix.InitiatorMessageStore">file</parameter>
</proxy>
</definitions>
Objective
This sample demonstrates the FIX (Financial Information eXchange) transport of
Synapse. FIX transport allows Synapse to connect to remote FIX acceptors and
initiators and exchange finance data.
Executing the Client
Send some FIX messages from Banzai to Synapse. Synapse will forward all requests
to Executor and get them processes. Responses from Executor will be routed back
to Banzai.
Synapse converts all received FIX messages into SOAP format. You can view these
SOAP messages from the Synapse log. When SOAP messages are sent to FIX endpoints,
Synapse converts them back into valid FIX messages. While FIX messages are flowing
through the service bus, you can perform various transformations and content based
routing on the FIX messages using the existing mediators like XSLT, XQuery, Filter
and Switch.
Back to Catalog