camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r898382 - in /websites/production/camel/content: cache/main.pageCache quickfix.html
Date Tue, 18 Feb 2014 12:19:42 GMT
Author: buildbot
Date: Tue Feb 18 12:19:42 2014
New Revision: 898382

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/quickfix.html

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/camel/content/quickfix.html
==============================================================================
--- websites/production/camel/content/quickfix.html (original)
+++ websites/production/camel/content/quickfix.html Tue Feb 18 12:19:42 2014
@@ -102,16 +102,17 @@
 </dependency>
 ]]></script>
 </div></div><h3 id="Quickfix-URIformat">URI format</h3><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[quickfix:configFile[?sessionID=sessionID]
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[quickfix:configFile[?sessionID=sessionID&amp;lazyCreateEngine=true|false]
 ]]></script>
-</div></div><p>The <strong>configFile</strong> is the name
of the QuickFIX/J configuration to use for the FIX engine (located as a resource found in
your classpath). The optional sessionID identifies a specific FIX session. The format of the
sessionID is:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+</div></div><p>The <strong>configFile</strong> is the name
of the QuickFIX/J configuration to use for the FIX engine (located as a resource found in
your classpath). The optional <strong>sessionID</strong> identifies a specific
FIX session. The format of the sessionID is:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[(BeginString):(SenderCompID)[/(SenderSubID)[/(SenderLocationID)]]-&gt;(TargetCompID)[/(TargetSubID)[/(TargetLocationID)]]
 ]]></script>
-</div></div><p>Example URIs:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+</div></div><p>The optional <strong>lazyCreateEngine</strong>
(Camel 2.12.3+) parameter allows to create QuickFIX/J engine on demand. Value <strong>true</strong>
means the engine is started when first message is send or there's consumer configured in route
definition. When&#160;<strong>false</strong> value is used, the engine is
started at the endpoint creation. When this parameter is missing, the value of component's
property <strong>lazyCreateEngines</strong> is being used.</p><p>Example
URIs:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[quickfix:config.cfg
 
 quickfix:config.cfg?sessionID=FIX.4.2:MyTradingCompany-&gt;SomeExchange
-]]></script>
+
+quickfix:config.cfg?sessionID=FIX.4.2:MyTradingCompany-&gt;SomeExchange&amp;lazyCreateEngine=true]]></script>
 </div></div><h2 id="Quickfix-Endpoints">Endpoints</h2><p>FIX
sessions are endpoints for the <strong>quickfix</strong> component. An endpoint
URI may specify a single session or all sessions managed by a specific QuickFIX/J engine.
Typical applications will use only one FIX engine but advanced users may create multiple FIX
engines by referencing different configuration files in <strong>quickfix</strong>
component endpoint URIs.</p><p>When a consumer does not include a session ID in
the endpoint URI, it will receive exchanges for all sessions managed by the FIX engine associated
with the configuration file specified in the URI. If a producer does not specify a session
in the endpoint URI then it must include the session-related fields in the FIX message being
sent. If a session is specified in the URI then the component will automatically inject the
session-related fields into the FIX message.</p><h3 id="Quickfix-ExchangeFormat">Exchange
Format</h3><p>The exchange headers include info
 rmation to help with exchange filtering, routing and other processing. The following headers
are available:</p><div class="confluenceTableSmall">
 <table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"><p> Header Name </p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p> Description </p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> EventCategory </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> One of <code>AppMessageReceived</code>,
<code>AppMessageSent</code>, <code>AdminMessageReceived</code>, <code>AdminMessageSent</code>,
<code>SessionCreated</code>, <code>SessionLogon</code>, <code>SessionLogoff</code>.
See the <code>QuickfixjEventCategory</code> enum. </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> SessionID </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> The FIX message SessionID </p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p> MessageType </p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p> The FIX MsgType tag value </p></td></tr><tr><td
colspan="1" rowspan="1" class="conflue
 nceTd"><p> DataDictionary </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>
Specifies a data dictionary to used for parsing an incoming message. Can be an instance of
a data dictionary or a resource path for a QuickFIX/J data dictionary file </p></td></tr></tbody></table>
 </div><p>The DataDictionary header is useful if string messages are being received
and need to be parsed in a route. QuickFIX/J requires a data dictionary to parse certain types
of messages (with repeating groups, for example). By injecting a DataDictionary header in
the route after receiving a message string, the FIX engine can properly parse the data.</p><h3
id="Quickfix-QuickFIX/JConfigurationExtensions">QuickFIX/J Configuration Extensions</h3><p>When
using QuickFIX/J directly, one typically writes code to create instances of logging adapters,
message stores and communication connectors. The <strong>quickfix</strong> component
will automatically create instances of these classes based on information in the configuration
file. It also provides defaults for many of the common required settings and adds additional
capabilities (like the ability to activate JMX support).</p><p>The following sections
describe how the <strong>quickfix</strong> component processes the QuickFIX/J
configu
 ration. For comprehensive information about QuickFIX/J configuration, see the <a shape="rect"
class="external-link" href="http://www.quickfixj.org/quickfixj/usermanual/usage/configuration.html"
rel="nofollow">QFJ user manual</a>.</p><h4 id="Quickfix-CommunicationConnectors">Communication
Connectors</h4><p>When the component detects an initiator or acceptor session
setting in the QuickFIX/J configuration file it will automatically create the corresponding
initiator and/or acceptor connector. These settings can be in the default or in a specific
session section of the configuration file.</p><div class="confluenceTableSmall">



Mime
View raw message