Author: ruwan Date: Thu Jun 5 04:10:39 2008 New Revision: 18001 URL: http://wso2.org/svn/browse/wso2?view=rev&revision=18001
Log: Fixing the Samples Setup guide Modified: branches/esb/java/1.7/esb/java/src/site/xdoc/ESB_Samples_Setup.xml Modified: branches/esb/java/1.7/esb/java/src/site/xdoc/ESB_Samples_Setup.xml URL: http://wso2.org/svn/browse/wso2/branches/esb/java/1.7/esb/java/src/site/xdoc/ESB_Samples_Setup.xml?rev=18001&r1=18000&r2=18001&view=diff ============================================================================== --- branches/esb/java/1.7/esb/java/src/site/xdoc/ESB_Samples_Setup.xml (original) +++ branches/esb/java/1.7/esb/java/src/site/xdoc/ESB_Samples_Setup.xml Thu Jun 5 04:10:39 2008 @@ -131,7 +131,7 @@ <p></p> -<p>The above diagram depicts the interactions between the clients, the ESB +<p>The above table depicts the interactions between the clients, the ESB and services at a high level. The Clients are able to send SOAP/REST or POX messages over transports such as HTTP/HTTPS or JMS with WS-Addressing, WS-Security, or WS-Reliable messaging. They could send binary optimized @@ -165,9 +165,7 @@ <p>The client is able to operate in the following modes, and send the payloads listed below as SOAP messages: </p> -<p></p> <ul> - <li></li> <li>quote - sends a quote request for a single stock as follows. The response contains the last sales price for the stock which would be displayed. @@ -177,7 +175,6 @@ </m:request> </m:getQuote></pre> </li> - <li></li> <li>customquote - sends a quote request in a custom format. The ESB would transform this custom request into the standard stock quote request format and send it to the service. Upon receipt of the response, it would @@ -187,7 +184,6 @@ <m0:Code>symbol</m0:Code> </m0:checkPriceRequest></pre> </li> - <li></li> <li>fullquote - gets quote reports for the stock over a number of days (i.e., last 100 days of the year). <pre xml:space="preserve"><m:getFullQuote xmlns:m="http://services.samples/xsd"> @@ -196,8 +192,7 @@ </m:request> </m:getFullQuote></pre> </li> - <li></li> - <li>placeorder - places an order for stocks using a one way request + <li>placeorder - places an order for stocks using a one way request <pre xml:space="preserve"><m:placeOrder xmlns:m="http://services.samples/xsd"> <m:order> <m:price>3.141593E0</m:price> @@ -206,7 +201,6 @@ </m:order> </m:placeOrder></pre> </li> - <li></li> <li>marketactivity - gets a market activity report for the day (i.e., quotes for multiple symbols) <pre xml:space="preserve"><m:getMarketActivity xmlns:m="http://services.samples/xsd"> @@ -217,7 +211,6 @@ </m:request> </m:getMarketActivity></pre> </li> - <li></li> </ul> <p></p> @@ -282,20 +275,12 @@ such as timestamps, signatures, and encryption. See Apache Axis2 and Apache Rampart documentation for more information. </p> -<p></p> - -<p></p> - -<p></p> - <h3 id="L115">2. Generic JMS Client </h3> <p></p> <p></p> -<p></p> - <p>The JMS client is able to send plain text, plain binary content, or POX content by directly publishing a JMS message to the specified destination. The JMS destination name should be specified with the 'jms_dest' property. @@ -304,10 +289,6 @@ <p></p> -<p></p> - -<p></p> - <p>The plain text payload for a 'text' message can be specified through the 'payload' property. For binary messages, the 'payload' property would contain the path to the binary file. For POX messages, the 'payload' property will @@ -331,18 +312,10 @@ <p></p> -<p></p> - -<p></p> - <h3 id="L133">3. MTOM / SwA Client </h3> <p></p> -<p></p> - -<p></p> - <p>The MTOM / SwA client can send a binary image file as a MTOM or SwA optimized message, and receive the same file again through the response and save it as a temporary file. The 'opt_mode' can specify 'mtom' or 'swa' @@ -356,16 +329,10 @@ <p></p> -<p></p> - <h2 id="Starting">Starting the Sample Services </h2> <p></p> -<p></p> - -<p></p> - <p>The sample services ship with a pre-configured Axis2 server, and demonstrates in-only and in-out SOAP/REST or POX messaging over HTTP/HTTPS and JMS transports using WS-Addressing, WS-Security, and WS-Reliable @@ -389,10 +356,6 @@ <p></p> -<p></p> - -<p></p> - <p>To start the Axis2 server, go to the samples/axis2Server directory and execute the axis2server.sh or axis2server.bat script. This starts the Axis2 server with the HTTP transport listener on port 9000 and HTTPS on 9002 @@ -444,10 +407,6 @@ <p></p> -<p></p> - -<p></p> - <h2 id="config">Starting Sample ESB Configurations </h2> <p></p> @@ -468,18 +427,10 @@ <p></p> -<p></p> - -<p></p> - <h2 id="Setting">Setting up the JMS Listener </h2> <p></p> -<p></p> - -<p></p> - <p>The samples used in this guide assumes the existence of a local ActiveMQ (4.1.0 or higher) installation, which is properly installed and started. </p> @@ -539,18 +490,168 @@ <p></p> -<p></p> +<h2 id="fixtransport"> + Configuring Synapse for the FIX Transport + </h2> + <p> + First of all you need to put the following jar files into the lib folder of the + synapse distribution + </p> + <ul> + <li>quickfixj-core-1.3.1.jar</li> + <li>quickfixj-msg-fix40-1.3.1.jar</li> + <li>quickfixj-msg-fix41-1.3.1.jar</li> + <li>quickfixj-msg-fix42-1.3.1.jar</li> + <li>quickfixj-msg-fix43-1.3.1.jar</li> + <li>quickfixj-msg-fix44-1.3.1.jar</li> + <li>slf4j-api-1.3.0.jar</li> + <li>slf4j-jdk14-1.3.0.jar</li> + </ul> + <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 + 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> + </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 + specified below. + </p> + <p> + The FileStorePath property in the following two files should point + to two directories in your local file system. Once the samples + are executed, Synapse will create FIX message stores in these two + directories. + </p> + <p> + Put the following entries in a file called fix-synapse.cfg -<p></p> + <pre> + [default] + FileStorePath=examples/target/data/synapse-acceptor + ConnectionType=acceptor + StartTime=00:00:00 + EndTime=00:00:00 + HeartBtInt=30 + ValidOrderTypes=1,2,F + SenderCompID=SYNAPSE + TargetCompID=BANZAI + UseDataDictionary=Y + DefaultMarketPrice=12.30 + + [session] + BeginString=FIX.4.0 + SocketAcceptPort=9876 + </pre> + </p> + <p> + Put the following entries in a file called synapse-sender.cfg + <pre> + [default] + FileStorePath=examples/target/data/synapse-initiator + SocketConnectHost=localhost + StartTime=00:00:00 + EndTime=00:00:00 + HeartBtInt=30 + ReconnectInterval=5 + </pre> + </p> + <p/> + <h3 id="fixsamplesconfig"> + Configuring Sample FIX Applications + </h3> + <p> + Locate and edit the FIX configuration file of Executor to be as follows. + This file is usually named executor.cfg + <pre> + [default] + FileStorePath=examples/target/data/executor + ConnectionType=acceptor + StartTime=00:00:00 + EndTime=00:00:00 + HeartBtInt=30 + ValidOrderTypes=1,2,F + SenderCompID=EXEC + TargetCompID=SYNAPSE + UseDataDictionary=Y + DefaultMarketPrice=12.30 + + [session] + BeginString=FIX.4.0 + SocketAcceptPort=19876 + </pre> + </p> + <p> + Locate and edit the FIX configuration file of Banzai to be as follows. + This file is usually named banzai.cfg + <pre> + [default] + FileStorePath=examples/target/data/banzai + ConnectionType=initiator + SenderCompID=BANZAI + TargetCompID=SYNAPSE + SocketConnectHost=localhost + StartTime=00:00:00 + EndTime=00:00:00 + HeartBtInt=30 + ReconnectInterval=5 + + [session] + BeginString=FIX.4.0 + SocketConnectPort=9876 + </pre> + </p> + <p> + The FileStorePath property in the above two files should point + to two directories in your local file system. + </p> + <p> + If you are using 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. + </p> + <p> + For more information regarding the FIX sample applications please + refer the <a href="http://www.quickfixj.org/quickfixj/usermanual/usage/examples.html";>Example Applications</a> section in the Quickfix/J + documentation. For more information on configuring Quickfix/J applications + refer the <a href="http://www.quickfixj.org/quickfixj/usermanual/usage/configuration.html";>Configuring Quickfix/J</a> section of the Quickfix/J + documentation. + </p> + <p/> <h2 id="script">Configuring the ESB for Script Mediator Support </h2> <p></p> -<p></p> - -<p></p> - <p>The Script Mediator is a Synapse extension, and thus all pre-requisites for all BSF supported scripting languages may not be bundled by default with the ESB distribution. Before you use some script mediators, you may need to @@ -570,52 +671,44 @@ <p></p> -<h4 id="Ruby">Ruby Support </h4> - -<p></p> - -<p>For Ruby support, you need to download the 'jruby-complete.jar' from the -Maven repository for JRuby, and copy it into the 'lib' folder of ESB . <a -href="http://repo1.maven.org/maven2/org/jruby/jruby-complete/";>Download</a> -the JRuby JAR. </p> - -<p></p> - -<p></p> - -<p></p> - -<h2 id="derby">Setting up Derby database server </h2> - -<p></p> - -<p>You can download Apache Derby distribution from <a -href="http://db.apache.org/derby/";>http://db.apache.org/derby/</a> </p> - -<p></p> -<ol> - <li></li> - <li>Set up and start the Derby network server </li> - <li></li> - <li>Create and open a connection to the database using the Derby client - driver - <p>CONNECT - 'jdbc:derby://localhost:1527/esbdb;user=esb;password=esb;create=true'; +<h4> + Ruby Support + </h4> + <p> + For Ruby support you need to download the 'jruby-complete.jar' from the + Maven repository for JRuby, and copy it into the 'lib' folder of Synapse . + The JRuby JAR can be downloaded from <a + href="http://repo1.maven.org/maven2/org/jruby/jruby-complete/1.0.1/jruby-complete-1.0.1.jar";> + here</a>. </p> - </li> - <li></li> - <li>Create a table using the following statement - <p>create table company(name varchar(10), id varchar(10), price double); + <p/> + <h2 id="derby"> + Setting up Derby database server + </h2> + <p> + You can download Apache Derby distribution from <a + href="http://db.apache.org/derby/";>http://db.apache.org/derby/</a> </p> - </li> - <li></li> - <li>Inserts some data using following statements - <p>insert into company values ('IBM','c1',0.0); </p> - <p>insert into company values ('SUN','c2',0.0); </p> - <p>insert into company values ('MSFT','c3',0.0); </p> - </li> - <li></li> -</ol> + <ol> + <li> + Set up and start the Derby network server + </li> + <li> + Create and open a connection to the database using the Derby client + driver<br/> + <pre> CONNECT 'jdbc:derby://localhost:1527/synapsedb;user=synapse;password=synapse;create=true';</pre> + </li> + <li> + Create a table using the following statement + <pre> CREATE table company(name varchar(10), id varchar(10), price double);</pre> + </li> + <li> + Inserts some data using following statements + <pre> INSERT into company values ('IBM','c1',0.0); + INSERT into company values ('SUN','c2',0.0); + INSERT into company values ('MSFT','c3',0.0);</pre> + </li> + </ol> <p></p> @@ -632,10 +725,9 @@ <p></p> -<h2 id="datasource">Setting up Synapse DataSources</h2> - -<p></p> +<h2>Setting up Synapse DataSources</h2> +<div> <p>Definition of the reusable database connection pool or datasources can be done using synapse.properties file. It is possible to configure any number of datasources. Currently only supports two type of datasources and those are @@ -643,23 +735,21 @@ PerUserPoolDataSource (based on apache dhcp).Following configuration includes both two definition. This configuration is related with sample 363.</p> -<p></p> <p>Configuration is somewhat similar to the log4j appender configuration.</p> -<p></p> - -<p>It requires two databases, follow the above specified (Setting up Derby -Database server) steps to create the two databases -'jdbc:derby://localhost:1527/lookupdb', -'jdbc:derby://localhost:1527/reportdb' using the user name and password as -'esb'. Fill in the data for those two databases as per described in the above -section</p> -<p></p> - -<h3>synapse.properties configuration </h3> -<pre>synapse.datasources=lookupds,reportds +<p>It requires two databases, follow the above specified (Setting up +Derby Database server) steps to create the two databases +<strong>'jdbc:derby://localhost:1527/lookupdb'</strong>, +<strong>'jdbc:derby://localhost:1527/reportdb'</strong> using the user name and password as +'synapse'. Fill in the data for those two databases as per described in the above section</p> + +<div> +<p><strong>synapse.properties configuration <br /> +</strong></p> +<pre>#datasources +synapse.datasources=lookupds,reportds synapse.datasources.icFactory=com.sun.jndi.rmi.registry.RegistryContextFactory synapse.datasources.providerUrl=rmi://localhost:2199 synapse.datasources.providerPort=2199 @@ -667,8 +757,8 @@ synapse.datasources.lookupds.type=BasicDataSource synapse.datasources.lookupds.driverClassName=org.apache.derby.jdbc.ClientDriver synapse.datasources.lookupds.url=jdbc:derby://localhost:1527/lookupdb;create=false -synapse.datasources.lookupds.username=esb -synapse.datasources.lookupds.password=esb +synapse.datasources.lookupds.username=synapse +synapse.datasources.lookupds.password=synapse synapse.datasources.lookupds.dsName=lookupdb synapse.datasources.lookupds.maxActive=100 synapse.datasources.lookupds.maxIdle=20 @@ -681,20 +771,13 @@ synapse.datasources.reportds.dsName=reportdb synapse.datasources.reportds.driverClassName=org.apache.derby.jdbc.ClientDriver synapse.datasources.reportds.url=jdbc:derby://localhost:1527/reportdb;create=false -synapse.datasources.reportds.username=esb -synapse.datasources.reportds.password=esb +synapse.datasources.reportds.username=synapse +synapse.datasources.reportds.password=synapse synapse.datasources.reportds.maxActive=100 synapse.datasources.reportds.maxIdle=20 synapse.datasources.reportds.maxWait=10000</pre> - -<p></p> - -<p></p> - -<p></p> - -<p></p> - -<p></p> +</div> +</div> + </body> </html> _______________________________________________ Esb-java-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
