Author: hiranya
Date: Tue Aug 20 02:36:43 2013
New Revision: 1515688
URL: http://svn.apache.org/r1515688
Log:
Documentation update
Modified:
synapse/trunk/java/modules/documentation/src/site/xdoc/userguide/transports/fix.xml
Modified:
synapse/trunk/java/modules/documentation/src/site/xdoc/userguide/transports/fix.xml
URL:
http://svn.apache.org/viewvc/synapse/trunk/java/modules/documentation/src/site/xdoc/userguide/transports/fix.xml?rev=1515688&r1=1515687&r2=1515688&view=diff
==============================================================================
---
synapse/trunk/java/modules/documentation/src/site/xdoc/userguide/transports/fix.xml
(original)
+++
synapse/trunk/java/modules/documentation/src/site/xdoc/userguide/transports/fix.xml
Tue Aug 20 02:36:43 2013
@@ -36,6 +36,9 @@
<li><a href="#Sender">FIX Transport Sender</a></li>
</ul>
</li>
+ <li>
+ <a href="#Mediation">Mediation FIX Messages</a>
+ </li>
</ul>
</section>
<section name="Introduction" id="Introduction">
@@ -387,8 +390,8 @@
<li>SessionQualifier</li>
</ul>
<p>
- The DeliverTo* fields will be actually set on the
messages, as they are forwarded
- to the remote FIX endpoint.
+ The DeliverTo* fields will be actually set on the
messages, as the messages are
+ forwarded to the remote FIX endpoint.
</p>
<p>
There are several parameters that can be set at the proxy
service level to
@@ -479,5 +482,54 @@
</table>
</subsection>
</section>
+ <section name="Mediating FIX Messages" id="Mediation">
+ <p>
+ The FIX transport converts all received messages into SOAP
(XML). Therefore, you can
+ treat a FIX message as any other XML message at the mediation
level. You may use
+ XPath to extract individual fields from the FIX messages, and
use XSLT or XQuery to
+ transform them into other formats. An example FIX message and
its equivalent SOAP
+ infoset as constructed by the FIX transport are shown below.
+ </p>
+ <div
class="xmlConf">8=FIX.4.0[SOH]9=105[SOH]35=D[SOH]34=2[SOH]49=BANZAI[SOH]52=20080711-06:42:26[SOH]56=SYNAPSE[SOH]11=1215758546278[SOH]21=1[SOH]38=9000000040=154=155=DEL59=010=121</div>
+ <div class="xmlConf"><message>
+ <header>
+ <field id="8">FIX.4.0</field>
+ <field id="9">105</field>
+ <field id="34">2</field>
+ <field id="35">D</field>
+ <field id="49">BANZAI</field>
+ <field id="52">20080711-06:42:26</field>
+ <field id="56">SYNAPSE</field>
+ </header>
+ <body>
+ <field id="11">1215758546278</field>
+ <field id="21">1</field>
+ <field id="38">90000000</field>
+ <field id="40">1</field>
+ <field id="54">1</field>
+ <field id="55">DEL</field>
+ <field id="59">0</field>
+ </body>
+ <trailer>
+ <field id="10">121</field>
+ </trailer>
+</message></div>
+ <p>
+ Notice how the FIX header, body and trailer sections are
grouped under separate
+ parent XML elements. To extract the BeginString field (field
no. 8), you may use
+ the following XPath expression:
+ </p>
+ <div class="xmlConf">//header/field[@id='8']</div>
+ <p>
+ Similarly to extract the value of field 55 from the FIX
message body, you may use
+ the following XPath expression:
+ </p>
+ <div class="xmlConf">//body/field[@id='55']</div>
+ <p>
+ Representing FIX messages as XML enables you to use some of
the most powerful
+ mediation features of Synapse with FIX message flows. This
includes content-based
+ routing, message transformation and protocol switching.
+ </p>
+ </section>
</body>
</document>
\ No newline at end of file