Author: veithen
Date: Sat Mar 21 21:31:51 2009
New Revision: 757028
URL: http://svn.apache.org/viewvc?rev=757028&view=rev
Log:
Some improvements to the site:
* Added a direct link from the sidebar to the Samples Setup page.
* Added a separate page with documentation about the transports shipped with
Synapse.
* Moved some of the FIX documentation from the Samples Setup guide to the new
transport documentation.
* Moved some of the VFS documentation form the Configuration Language guide to
the new transport documentation.
* Added some new documentation for the HTTP transport, including the change in
r755711.
Added:
synapse/trunk/java/src/site/apt/
synapse/trunk/java/src/site/apt/transports.apt (with props)
Modified:
synapse/trunk/java/src/site/site.xml
synapse/trunk/java/src/site/xdoc/Synapse_Configuration_Language.xml
synapse/trunk/java/src/site/xdoc/Synapse_Samples_Setup.xml
Added: synapse/trunk/java/src/site/apt/transports.apt
URL:
http://svn.apache.org/viewvc/synapse/trunk/java/src/site/apt/transports.apt?rev=757028&view=auto
==============================================================================
--- synapse/trunk/java/src/site/apt/transports.apt (added)
+++ synapse/trunk/java/src/site/apt/transports.apt Sat Mar 21 21:31:51 2009
@@ -0,0 +1,359 @@
+{Introduction}
+
+ The Synapse project has developed a set of transport implementations that
provide protocol
+ support and/or features that go beyond what is provided out of the box by
Axis2:
+
+ * A non blocking HTTP transport that gives better performance in a highly
asynchronous
+ environment like Synapse.
+
+ * A VFS transport that can read messages from files and write outgoing
messages to a file system.
+ The file system can be local or remote, and several remote protocols are
supported, such as
+ FTP, SSH, WebDAV, etc.
+
+ * A transport supporting the {{{http://www.fixprotocol.org}Financial
Information eXchange}}
+ protocol. FIX is a public-domain messaging standard developed specifically
for the real-time electronic
+ exchange of securities transactions. It has a large user base and is
developed by the
+ collaborative effort of banks, broker-dealers, exchanges, industry
utilities and associations,
+ institutional investors, and IT providers around the world.
+
+ []
+
+ Note that while these transports are developed as part of the Synapse
project, they can be used
+ with any Axis2 based application.
+
+ The Synapse distribution also comes bundled with the following transports
from the WS-Commons
+ Transport project:
+
+ * A JMS transport supporting any JMS 1.0 or 1.1 provider.
+
+ * A mail transport able to send messages using SMTP and poll messages from a
POP3 or IMAP account.
+
+{Contents}
+
+%{toc}
+
+{Non-blocking HTTP transport}
+
+* {Example configurations}
+
++--------------------------------------------------------------------------------------------+
+<transportReceiver name="http"
class="org.apache.synapse.transport.nhttp.HttpCoreNIOListener">
+ <parameter name="port">8280</parameter>
+ <parameter name="non-blocking">true</parameter>
+</transportReceiver>
+
+<transportReceiver name="https"
class="org.apache.synapse.transport.nhttp.HttpCoreNIOSSLListener">
+ <parameter name="port" locked="false">8243</parameter>
+ <parameter name="non-blocking" locked="false">true</parameter>
+ <parameter name="keystore" locked="false">
+ <KeyStore>
+ <Location>lib/identity.jks</Location>
+ <Type>JKS</Type>
+ <Password>password</Password>
+ <KeyPassword>password</KeyPassword>
+ </KeyStore>
+ </parameter>
+ <parameter name="truststore" locked="false">
+ <TrustStore>
+ <Location>lib/trust.jks</Location>
+ <Type>JKS</Type>
+ <Password>password</Password>
+ </TrustStore>
+ </parameter>
+</transportReceiver>
+
+<transportSender name="http"
class="org.apache.synapse.transport.nhttp.HttpCoreNIOSender">
+ <parameter name="non-blocking" locked="false">true</parameter>
+</transportSender>
+
+<transportSender name="https"
class="org.apache.synapse.transport.nhttp.HttpCoreNIOSSLSender">
+ <parameter name="non-blocking" locked="false">true</parameter>
+ <parameter name="keystore" locked="false">
+ <KeyStore>
+ <Location>lib/identity.jks</Location>
+ <Type>JKS</Type>
+ <Password>password</Password>
+ <KeyPassword>password</KeyPassword>
+ </KeyStore>
+ </parameter>
+ <parameter name="truststore" locked="false">
+ <TrustStore>
+ <Location>lib/trust.jks</Location>
+ <Type>JKS</Type>
+ <Password>password</Password>
+ </TrustStore>
+ </parameter>
+</transportSender>
++--------------------------------------------------------------------------------------------+
+
+* {Transport listener parameters}
+
+ The following parameters are supported by both the HTTP and the HTTPS
listener:
+
+ [<<<port>>>] The TCP port to bind the listener to.
+
+ [<<<bind-address>>>] The IP address to bind the listener to.
+ This can be used on hosts that have more than one network interface or IP
address
+ to run multiple Synapse instances listening to the same port. If this
parameter is not specified,
+ the listener will accept connections on any IP address.
+
+ [<<<hostname>>>] The host name to use when computing endpoint references in
generated WSDL files.
+ The default value is the host name as provided by the operation system or
<<<localhost>>> if
+ the host name can't be determined. The value of this parameter is ignored if
<<<WSDLEPRPrefix>>>
+ is specified.
+
+ [<<<WSDLEPRPrefix>>>] The URL prefix to use when computing endpoint
references in generated WSDL
+ files. The value must be a valid URL with at least a protocol and host. If
this value is
+ unspecified, endpoint references will be computed based on the listener type
(HTTP or HTTPS)
+ and <<<hostname>>> and <<<port>>> parameters.
+
+ This parameter should be used if clients connect to Synapse through a
frontend server, e.g. a
+ (load balancing) Apache, and these clients rely on the address information
in the WSDL documents
+ exposed through <<<...?wsdl>>> URLs.
+
+ []
+
+ The following parameters are specific to the HTTPS listener:
+
+ [<<<keystore>>>] The keystore configuration. The value of this parameter
must be a
+ <<<\<KeyStore\>>>> element as shown in the example configurations above.
+
+ [<<<truststore>>>] The truststore configuration. The value of this parameter
must be a
+ <<<\<TrustStore\>>>> element as shown in the example configurations above.
+
+ [<<<SSLVerifyClient>>>] This parameter has the same meaning as the
corresponding
+ {{{http://httpd.apache.org/docs/2.2/mod/mod_ssl.html#sslverifyclient}mod_ssl
directive}} and
+ sets the desired certificate verification level for client authentication:
+
+ * <<<none>>> (default): no client certificate is required at all
+
+ * <<<optional>>>: the client may present a valid certificate, but is not
required to do so
+
+ * <<<require>>>: the client has to present a valid certificate, otherwise
the connection
+ request will be terminated during SSL handshake
+
+* {Transport sender parameters}
+
+ The following properties can be used to configure the HTTP sender to use a
proxy. They can
+ be specified either as transport parameters in declared in
<<<\<transportSender\>>>> or as
+ system properties.
+
+ [<<<http.proxyHost>>>] The host name or address of the proxy server.
+
+ [<<<http.proxyPort>>>] The TCP port of the proxy server.
+
+ [<<<http.nonProxyHosts>>>] The hosts to which the HTTP sender should connect
directly and
+ not through the proxy server. The value can be a list of hosts, each
seperated by a |, and
+ in addition a wildcard character (*) can be used for matching.
+
+ Example value: <<<*.foo.com|localhost>>>
+
+ []
+
+ Note that the HTTPS sender has no proxy support yet.
+
+ The following parameters are specific to the HTTP sender:
+
+ [<<<keystore>>>] The keystore configuration. The value of this parameter
must be a
+ <<<\<KeyStore\>>>> element as shown in the example configurations above.
+
+ [<<<truststore>>>] The truststore configuration. The value of this parameter
must be a
+ <<<\<TrustStore\>>>> element as shown in the example configurations above.
+
+ [<<<novalidatecert>>>] When set to <<<true>>>, this parameter disables
server certificate
+ validation (trust). The default value is <<<false>>>. This parameter will be
ignored if
+ <<<truststore>>> is set.
+
+ Setting his parameter to <<<true>>> is useful in development and test
environments, but
+ should not be used in production environments. If validation is disabled, a
warning
+ message will be logged at startup.
+
+ [<<<HostnameVerifier>>>] This optional parameter specifies the policy to
apply when
+ checking that the hostname of the server matches the names stored inside the
X.509 certificate
+ presented by the server. Possible values are <<<Strict>>>, <<<AllowAll>>> and
+ <<<DefaultAndLocalhost>>>. See the
+
{{{apidocs/org/apache/synapse/transport/nhttp/HostnameVerifier.html}HostnameVerifier
Javadoc}}
+ for more details.
+
+{VFS transport}
+
+* {Service parameters}
+
+ [<<<transport.vfs.FileURI>>> (Required)]
+ The primary File (or Directory) URI in the vfs* transport format,
+ for this service
+
+ [<<<transport.vfs.ContentType>>> (Required)]
+ The expected content type for files retrieved for this service. The
+ VFS transport uses this information to select the appropriate
+ message builder.
+
+ Examples:
+
+ * <<<text/xml>>> for plain XML or SOAP
+
+ * <<<text/plain; charset=ISO-8859-1>>> for text files
+
+ * <<<application/octet-stream>>> for binary data
+
+ []
+
+ [<<<transport.vfs.FileNamePattern>>> (Optional)]
+ A file name regex pattern to match files against a directory
+ specified by the FileURI
+
+ [<<<transport.PollInterval>>> (Optional)]
+ The poll interval (in seconds)
+
+ [<<<transport.vfs.ActionAfterProcess>>> (Optional)]
+ DELETE or MOVE
+
+ [<<<transport.vfs.MoveAfterProcess>>> (Optional)]
+ The directory to move files after processing (i.e. all files process
+ successfully)
+
+ [<<<transport.vfs.ActionAfterErrors>>> (Optional)]
+ DELETE or MOVE
+
+ [<<<transport.vfs.MoveAfterErrors>>> (Optional)]
+ The directory to move files after errors (i.e. some of the files
+ succeed but some fail)
+
+ [<<<transport.vfs.ActionAfterFailure>>> (Optional)]
+ DELETE or MOVE
+
+ [<<<transport.vfs.MoveAfterFailure>>> (Optional)]
+ The directory to move after failure (i.e. all files fail)
+
+ [<<<transport.vfs.ReplyFileURI>>> (Optional)]
+ Reply file URI
+
+ [<<<transport.vfs.ReplyFileName>>> (Optional)]
+ Reply file name (defaults to response.xml)
+
+ [<<<transport.vfs.MoveTimestampFormat>>> (Optional)]
+ Timestamp prefix format for processed file name. java.text.SimpleDateFormat
compatible string. e.g. yyMMddHHmmss'-'
+
+* {VFS Transport URI examples}
+
+ * <<<file:///directory/filename.ext>>>
+
+ * <<<file:////somehost/someshare/afile.txt>>>
+
+ * <<<jar:../lib/classes.jar!/META-INF/manifest.mf>>>
+
+ * <<<jar:zip:outer.zip!/nested.jar!/somedir>>>
+
+ *
<<<ftp://myusername:mypassw...@somehost/pub/downloads/somefile.tgz[?vfs.passive=true]>>>
+
+ []
+
+ See {{http://commons.apache.org/vfs/filesystems.html}} for more samples.
+
+{FIX transport}
+
+ A general overview about the FIX transport can be found in the following
articles:
+
+ * {{{http://wso2.org/library/3449}Apache Synapse FIX'ed}}
+
+ * {{{http://wso2.org/library/3837}Using the WSO2 ESB and FIX}} (also applies
to Synapse)
+
+* {Setting up the FIX Transport}
+
+ To use the FIX transport, you need a local
{{{http://www.quickfixj.org}Quickfix/J}} installation.
+ Download Quickfix/J from {{http://www.quickfixj.org/downloads}}.
+
+ To enable the FIX transport, you need to uncomment the FIX
+ transport sender and FIX transport receiver configurations in the
+ SYNAPSE_HOME/repository/conf/axis2.xml. Simply locate and uncomment the
+ FIXTransportSender and FIXTransportListener sample configurations. Also
+ add the following jars to the Synapse class path (SYNAPSE_HOME/lib
directory).
+
+ * quickfixj-core.jar
+
+ * quickfixj-msg-fix40.jar
+
+ * quickfixj-msg-fix41.jar
+
+ * quickfixj-msg-fix42.jar
+
+ * quickfixj-msg-fix43.jar
+
+ * quickfixj-msg-fix44.jar
+
+ * mina-core-1.1.0.jar
+
+ * slf4j-api-1.3.0.jar
+
+ * slf4j-jdk14-1.3.0.jar
+
+ []
+
+ All these jars are shipped with the Quickfix/J binary distribution.
+
+* {FIX Transport Parameters}
+
+ This is the list of all parameters accepted by the FIX transport. Refer
+ the sample 257 and 258 to see how some of them are used in practice.
+
+ [<<<transport.fix.AcceptorConfigURL>>>] If a service needs to listen to
incoming
+ FIX messages from a remote initiator then Synapse needs to create an
acceptor.
+ This parameter should contain the URL of the file which contains the FIX
+ configuration for the acceptor. (See sample 257)
+
+ [<<<transport.fix.InitiatorConfigURL>>>] If a service needs to send FIX
messages
+ to a remote acceptor Synapse should create an initiator. This parameter
should
+ contain the URL of the file which contains the FIX configuration for the
+ initiator. (See sample 257)
+
+ [<<<transport.fix.AcceptorMessageStore>>>] The type of message store to be
used
+ with the acceptor. Allowed values for this parameter are 'file', 'jdbc',
'memory'
+ and 'sleepycat'. If not specified memory based message store will be used by
+ default. Additional parameters required to configure each of the message
stores
+ should be specified in the acceptor configuration file.
+
+ [<<<transport.fix.InitiatorMessageStore>>>] Same as the above but applies
only
+ for the initiators. Additional parameters required to configure each of
+ the message stores should be specified in the initiator configuration file.
+
+ [<<<transport.fix.AcceptorLogFactory>>>] Specifies the transport level log
factory
+ to be used to log messages going through the acceptor. FIX messages are
logged
+ without putting them in SOAP envelopes at this level. Accepted values are
+ 'console', 'file' and 'jdbc'. If not specified no logging will be done at
the transport
+ level. Additional parameters required to configure each of the lof factories
should be
+ specified in the acceptor configuration file.
+
+ [<<<transport.fix.InitiatorLogFactory>>>] Specifies the transport level log
factory
+ to be used to log messages going through the initiator. Functionality is
similar
+ to the above. Additional parameters required to configure each of the lof
factories
+ should be specified in the initiator configuration file.
+
+ [<<<transport.fix.ResponseDeliverToCompID>>>] If a response FIX message sent
from
+ Synapse to a remote FIX engine should be forwarded from the remote engine to
+ another party this parameter can be used to set the DeliverToCompID field
+ of the messages at Synapse.
+
+ [<<<transport.fix.ResponseDeliverToSubID>>>] If a response FIX message sent
from
+ Synapse to a remote FIX engine should be forwarded from the remote engine to
+ another party this parameter can be used to set the DeliverToSubID field
+ of the messages at Synapse.
+
+ [<<<transport.fix.ResponseDeliverToLocationID>>>] If a response FIX message
sent from
+ Synapse to a remote FIX engine should be forwarded from the remote engine to
+ another party this parameter can be used to set the DeliverToLocationID field
+ of the messages at Synapse.
+
+ [<<<transport.fix.ServiceName>>>] Used when messages coming over a different
protocol
+ has to be forwarded over FIX. The value must be equal to the name of the
service
+ and the scope must be 'axis2-client' (See sample 258)
+
+ [<<<transport.fix.SendAllToInSequence>>>] When there are multiple responses
to a FIX
+ request and when we need only one of them to be sent to the original
requester
+ this parameter has to be set to 'false'. This mostly comes handy when the
original
+ requester is communicating over a different protocol (like HTTP). If this
parameter
+ is not set to 'false' at such scenarios messages might get into a loop. (See
+ sample 258)
+
+ [<<<transport.fix.BeginStringValidation>>>] When the FIX messages sent to
Synapse should not
+ be forwarded to a FIX session with a different BeginString value this
parameter can be
+ set to 'true'. Setting this parameter to 'true' will enforce this
restriction.
Propchange: synapse/trunk/java/src/site/apt/transports.apt
------------------------------------------------------------------------------
svn:eol-style = native
Modified: synapse/trunk/java/src/site/site.xml
URL:
http://svn.apache.org/viewvc/synapse/trunk/java/src/site/site.xml?rev=757028&r1=757027&r2=757028&view=diff
==============================================================================
--- synapse/trunk/java/src/site/site.xml (original)
+++ synapse/trunk/java/src/site/site.xml Sat Mar 21 21:31:51 2009
@@ -53,8 +53,10 @@
<item name="Documentation" href="docs_index.html">
<item name="Quick Start Guide" href="Synapse_QuickStart.html"/>
<item name="Samples" href="Synapse_Samples.html"/>
+ <item name="Samples Setup" href="Synapse_Samples_Setup.html"/>
<item name="Extending Synapse" href="Synapse_Extending.html"/>
<item name="Configuration Language"
href="Synapse_Configuration_Language.html"/>
+ <item name="Transports" href="transports.html"/>
<item name="Javadocs" href="apidocs/index.html"/>
</item>
<item name="Previous Versions" href="history.html">
Modified: synapse/trunk/java/src/site/xdoc/Synapse_Configuration_Language.xml
URL:
http://svn.apache.org/viewvc/synapse/trunk/java/src/site/xdoc/Synapse_Configuration_Language.xml?rev=757028&r1=757027&r2=757028&view=diff
==============================================================================
--- synapse/trunk/java/src/site/xdoc/Synapse_Configuration_Language.xml
(original)
+++ synapse/trunk/java/src/site/xdoc/Synapse_Configuration_Language.xml Sat Mar
21 21:31:51 2009
@@ -964,190 +964,8 @@
The wrapper element for the JMS message
</td>
</tr>
- <tr>
- <td>
- VFS
- </td>
- <td>
- Required
- </td>
- <td>
- transport.vfs.FileURI
- </td>
- <td>
- The primary File (or Directory) URI in the vfs* transport format,
- for this service
- </td>
- </tr>
- <tr>
- <td/>
- <td>
- Required
- </td>
- <td>
- transport.vfs.ContentType
- </td>
- <td>
- The expected content type for files retrieved for this service. The
- VFS transport uses this information to select the appropriate
- message builder.
- <br/>
- Examples:
- <ul>
- <li><tt>text/xml</tt> for plain XML or SOAP</li>
- <li><tt>text/plain; charset=ISO-8859-1</tt> for text files</li>
- <li><tt>application/octet-stream</tt> for binary data</li>
- </ul>
- </td>
- </tr>
- <tr>
- <td/>
- <td>
- Optional
- </td>
- <td>
- transport.vfs.FileNamePattern
- </td>
- <td>
- A file name regex pattern to match files against a directory
- specified by the FileURI
- </td>
- </tr>
- <tr>
- <td/>
- <td>
- Optional
- </td>
- <td>
- transport.PollInterval
- </td>
- <td>
- The poll interval (in seconds)
- </td>
- </tr>
- <tr>
- <td/>
- <td>
- Optional
- </td>
- <td>
- transport.vfs.ActionAfterProcess
- </td>
- <td>
- DELETE or MOVE
- </td>
- </tr>
- <tr>
- <td/>
- <td>
- Optional
- </td>
- <td>
- transport.vfs.MoveAfterProcess
- </td>
- <td>
- The directory to move files after processing (i.e. all files
process
- successfully)
- </td>
- </tr>
- <tr>
- <td/>
- <td>
- Optional
- </td>
- <td>
- transport.vfs.ActionAfterErrors
- </td>
- <td>
- DELETE or MOVE
- </td>
- </tr>
- <tr>
- <td/>
- <td>
- Optional
- </td>
- <td>
- transport.vfs.MoveAfterErrors
- </td>
- <td>
- The directory to move files after errors (i.e. some of the files
- succeed but some fail)
- </td>
- </tr>
- <tr>
- <td/>
- <td>
- Optional
- </td>
- <td>
- transport.vfs.ActionAfterFailure
- </td>
- <td>
- DELETE or MOVE
- </td>
- </tr>
- <tr>
- <td/>
- <td>
- Optional
- </td>
- <td>
- transport.vfs.MoveAfterFailure
- </td>
- <td>
- The directory to move after failure (i.e. all files fail)
- </td>
- </tr>
- <tr>
- <td/>
- <td>
- Optional
- </td>
- <td>
- transport.vfs.ReplyFileURI
- </td>
- <td>
- Reply file URI
- </td>
- </tr>
- <tr>
- <td/>
- <td>
- Optional
- </td>
- <td>
- transport.vfs.ReplyFileName
- </td>
- <td>
- Reply file name (defaults to response.xml)
- </td>
- </tr>
- <tr>
- <td/>
- <td>
- Optional
- </td>
- <td>
- transport.vfs.MoveTimestampFormat
- </td>
- <td>
- Timestamp prefix format for processed file name.
java.text.SimpleDateFormat compatible string. e.g. yyMMddHHmmss'-'
- </td>
- </tr>
</tbody>
</table>
- <p>
- VFS Transport URI examples (See <a
-
href="http://commons.apache.org/vfs/filesystems.html";>http://commons.apache.org/vfs/filesystems.html</a>
- for more samples)
- </p>
-<pre xml:space="preserve">file:///directory/filename.ext
-file:////somehost/someshare/afile.txt
-jar:../lib/classes.jar!/META-INF/manifest.mf
-jar:zip:outer.zip!/nested.jar!/somedir
-ftp://myusername:mypassw...@somehost/pub/downloads/somefile.tgz[?vfs.passive=true]</pre>
-
<h2>
<a name="task" id="task">Tasks</a>
</h2>
Modified: synapse/trunk/java/src/site/xdoc/Synapse_Samples_Setup.xml
URL:
http://svn.apache.org/viewvc/synapse/trunk/java/src/site/xdoc/Synapse_Samples_Setup.xml?rev=757028&r1=757027&r2=757028&view=diff
==============================================================================
--- synapse/trunk/java/src/site/xdoc/Synapse_Samples_Setup.xml (original)
+++ synapse/trunk/java/src/site/xdoc/Synapse_Samples_Setup.xml Sat Mar 21
21:31:51 2009
@@ -591,42 +591,14 @@
<h2 id="fixtransport">
Configuring Synapse for the FIX Transport
</h2>
- <h3 id="fixtransport">
- Setting up the FIX Transport
- </h3>
- <p>
- To run the FIX samples used in this guide you need a local
- <a href="http://www.quickfixj.org";>Quickfix/J</a> installation.
- Download Quickfix/J from <a
href="http://www.quickfixj.org/downloads";>here</a>.
- </p>
- <p>
- To enable the FIX transport for samples, you need to uncomment the FIX
- transport sender and FIX transport receiver configurations in the
- SYNAPSE_HOME/repository/conf/axis2.xml. Simply locate and uncomment the
- FIXTransportSender and FIXTransportListener sample configurations. Also
- add the following jars to the Synapse class path (SYNAPSE_HOME/lib
directory).
- </p>
- <ul>
- <li>quickfixj-core.jar</li>
- <li>quickfixj-msg-fix40.jar</li>
- <li>quickfixj-msg-fix41.jar</li>
- <li>quickfixj-msg-fix42.jar</li>
- <li>quickfixj-msg-fix43.jar</li>
- <li>quickfixj-msg-fix44.jar</li>
- <li>mina-core-1.1.0.jar</li>
- <li>slf4j-api-1.3.0.jar</li>
- <li>slf4j-jdk14-1.3.0.jar</li>
- </ul>
- <p>
- All these jars are shipped with the Quickfix/J binary distribution.
- </p>
- <p/>
<h3 id="fixsamples">
Configuring Synapse for FIX Samples
</h3>
<p>
- In order to configure Synapse to run the FIX samples given in this
- guide you will need to create some FIX configuration files as
+ In order to configure Synapse to run the FIX samples given in this guide
you will need to
+ to enable the FIX transport as described in the <a
href="transports.html#Setting_up_the_FIX_Transport">transport
+ documentation</a>.
+ In addition you will need to create some FIX configuration files as
specified below.
</p>
<p>
@@ -738,101 +710,6 @@
refer the <a
href="http://www.quickfixj.org/quickfixj/usermanual/usage/configuration.html";>Configuring
Quickfix/J</a> section of the Quickfix/J
documentation.
</p>
- <h3 id="fixparameters">
- FIX Transport Parameters
- </h3>
- <p>
- This is the list of all parameters accepted by the FIX transport. Refer
- the sample 257 and 258 to see how some of them are used in practice.
- </p>
- <ul>
- <li>
- transport.fix.AcceptorConfigURL - If a service needs to listen to
incoming
- FIX messages from a remote initiator then Synapse needs to create an
acceptor.
- This parameter should contain the URL of the file which contains the FIX
- configuration for the acceptor. (See sample 257)
- </li>
-
- <li>
- transport.fix.InitiatorConfigURL - If a service needs to send FIX
messages
- to a remote acceptor Synapse should create an initiator. This parameter
should
- contain the URL of the file which contains the FIX configuration for the
- initiator. (See sample 257)
- </li>
-
- <li>
- transport.fix.AcceptorMessageStore - The type of message store to be
used
- with the acceptor. Allowed values for this parameter are 'file',
'jdbc', 'memory'
- and 'sleepycat'. If not specified memory based message store will be
used by
- default. Additional parameters required to configure each of the
message stores
- should be specified in the acceptor configuration file.
- </li>
-
- <li>
- transport.fix.InitiatorMessageStore - Same as the above but applies only
- for the initiators. Additional parameters required to configure each of
- the message stores should be specified in the initiator configuration
file.
- </li>
-
- <li>
- transport.fix.AcceptorLogFactory - Specifies the transport level log
factory
- to be used to log messages going through the acceptor. FIX messages are
logged
- without putting them in SOAP envelopes at this level. Accepted values
are
- 'console', 'file' and 'jdbc'. If not specified no logging will be done
at the transport
- level. Additional parameters required to configure each of the lof
factories should be
- specified in the acceptor configuration file.
- </li>
-
- <li>
- transport.fix.InitiatorLogFactory - Specifies the transport level log
factory
- to be used to log messages going through the initiator. Functionality
is similar
- to the above. Additional parameters required to configure each of the
lof factories
- should be specified in the initiator configuration file.
- </li>
-
- <li>
- transport.fix.ResponseDeliverToCompID - If a response FIX message sent
from
- Synapse to a remote FIX engine should be forwarded from the remote
engine to
- another party this parameter can be used to set the DeliverToCompID
field
- of the messages at Synapse.
- </li>
-
- <li>
- transport.fix.ResponseDeliverToSubID -If a response FIX message sent
from
- Synapse to a remote FIX engine should be forwarded from the remote
engine to
- another party this parameter can be used to set the DeliverToSubID field
- of the messages at Synapse.
- </li>
-
- <li>
- transport.fix.ResponseDeliverToLocationID - If a response FIX message
sent from
- Synapse to a remote FIX engine should be forwarded from the remote
engine to
- another party this parameter can be used to set the DeliverToLocationID
field
- of the messages at Synapse.
- </li>
-
- <li>
- transport.fix.ServiceName - Used when messages coming over a different
protocol
- has to be forwarded over FIX. The value must be equal to the name of
the service
- and the scope must be 'axis2-client' (See sample 258)
- </li>
-
- <li>
- transport.fix.SendAllToInSequence - When there are multiple responses
to a FIX
- request and when we need only one of them to be sent to the original
requester
- this parameter has to be set to 'false'. This mostly comes handy when
the original
- requester is communicating over a different protocol (like HTTP). If
this parameter
- is not set to 'false' at such scenarios messages might get into a loop.
(See
- sample 258)
- </li>
-
- <li>
- transport.fix.BeginStringValidation - When the FIX messages sent to
Synapse should not
- be forwarded to a FIX session with a different BeginString value this
parameter can be
- set to 'true'. Setting this parameter to 'true' will enforce this
restriction.
- </li>
- </ul>
- <p/>
<h2 id="script">
Configuring Synapse for Script Mediator Support
</h2>
