Author: indika
Date: Wed Jun 24 23:03:41 2009
New Revision: 39851
URL: http://wso2.org/svn/browse/wso2?view=rev&revision=39851

Log:
samples_setup_guide.xml  update 

Modified:
   trunk/esb/java/docs/xdoc/samples_setup_guide.xml

Modified: trunk/esb/java/docs/xdoc/samples_setup_guide.xml
URL: 
http://wso2.org/svn/browse/wso2/trunk/esb/java/docs/xdoc/samples_setup_guide.xml?rev=39851&r1=39850&r2=39851&view=diff
==============================================================================
--- trunk/esb/java/docs/xdoc/samples_setup_guide.xml    (original)
+++ trunk/esb/java/docs/xdoc/samples_setup_guide.xml    Wed Jun 24 23:03:41 2009
@@ -46,9 +46,9 @@
 <ul>
   <li><a href="#Pre-requis">Prerequisites</a> </li>
   <li><a href="#Understand">Understanding the Samples</a> </li>
-  <li><a href="#Using">Using the Sample Clients</a>
+  <li><a href="#Using">Using the Sample Clients</a> 
     <ul>
-      <li><a href="#L51">1. Stock Quote Client</a>
+      <li><a href="#L51">1. Stock Quote Client</a> 
         <ul>
           <li><a href="#Smart">Smart Client Mode:</a> </li>
           <li><a href="#Gateway">Gateway / Dumb Client Mode:</a> </li>
@@ -60,7 +60,7 @@
       <li><a href="#L133">3. MTOM / SwA Client</a> </li>
     </ul>
   </li>
-  <li><a href="#Starting">Starting the Sample Services</a>
+  <li><a href="#Starting">Starting the Sample Services</a> 
     <ul>
       <li><a href="#L161">1. SimpleStockQuoteService</a> </li>
       <li><a href="#L165">2. SecureStockQuoteService</a> </li>
@@ -70,14 +70,14 @@
   <li><a href="#config">Starting Sample ESB Configurations</a> </li>
   <li><a href="#Setting">Setting up the JMS Listener</a> </li>
   <li><a href="#mailsender">Setting up Mail Transport Sender</a> </li>
-  <li><a href="#script">Configuring the ESB for Script Mediator Support</a>
+  <li><a href="#script">Configuring the ESB for Script Mediator Support</a> 
     <ul>
       <li><a href="#JavaScript">JavaScript Support</a> </li>
       <li><a href="#Ruby">Ruby Support</a> </li>
     </ul>
   </li>
   <li><a href="#derby">Setting up Derby database server</a> </li>
-<li><a href="#datasource">Setting up Synapse DataSources</a> </li>
+  <li><a href="#datasource">Setting up Synapse DataSources</a> </li>
 </ul>
 </div>
 
@@ -177,7 +177,7 @@
   &lt;/m:request&gt;
 &lt;/m:getFullQuote&gt;</pre>
   </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">&lt;m:placeOrder 
xmlns:m="http://services.samples/xsd"&gt;
   &lt;m:order&gt;
     &lt;m:price&gt;3.141593E0&lt;/m:price&gt;
@@ -285,7 +285,7 @@
 
 <pre 
xml:space="preserve">u...@host:/tmp/wso2esb-2.0/samples/axis2Server/src/SimpleStockQuoteService$
 ant
 Buildfile: build.xml
-...
+ ...
 build-service:
    ....
       [jar] Building jar: 
/tmp/wso2esb-2.0/samples/axis2Server/repository/services/SimpleStockQuoteService.aar
@@ -341,7 +341,7 @@
 follows: </p>
 
 <pre xml:space="preserve">wso2esb-samples.bat -sn &lt;n&gt;
-./wso2esb-samples.sh -sn &lt;n&gt;</pre>
+ ./wso2esb-samples.sh -sn &lt;n&gt;</pre>
 
 <h2 id="Setting">Setting up the JMS Listener </h2>
 
@@ -601,41 +601,49 @@
 
 <div>
 <p>Definition of the reusable database connection pool or datasources can be
-done using datasources.properties file. It is possible to configure any number 
of
-datasources. Currently this only supports two types of datasources and those 
are
-based on Apache DBCP datasources. Those types are BasicDataSource and
-PerUserPoolDataSource (based on Apache DBCP). Following configuration includes
-both two definition. This configuration is related with sample 363.</p>
-
+done using <strong>datasources.properties</strong> file. It is possible to
+configure any number of datasources. Currently this only supports two types of
+datasources and those are based on Apache DBCP datasources. Those types are
+BasicDataSource and PerUserPoolDataSource (based on Apache DBCP). Following
+configuration includes both two definition. This configuration is related with
+sample 363.</p>
 
 <p>Configuration is somewhat similar to the log4j appender configuration.</p>
 
-
-<p>It requires two databases, follow the above specified (Setting up
-Derby Database server) steps to create the two databases
+<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
-'esb'. Fill in the data for those two databases as per described in the above 
section</p>
+<strong>'jdbc:derby://localhost:1527/reportdb'</strong> using the user name and
+password as '<strong>esb</strong>'. Fill in the data for those two databases as
+per described in the above section</p>
 
 <div>
 <p><strong>datasources.properties configuration <br />
 </strong></p>
-<pre>#datasources
+<pre>###############################################################################
+# DataSources Configuration
+###############################################################################
 synapse.datasources=lookupds,reportds
 synapse.datasources.icFactory=com.sun.jndi.rmi.registry.RegistryContextFactory
-synapse.datasources.providerUrl=rmi://localhost:2199
 synapse.datasources.providerPort=2199
+# If following property is present , then assumes that there is an external 
JNDI provider and will not start a RMI registry
+#synapse.datasources.providerUrl=rmi://localhost:2199
 
+synapse.datasources.lookupds.registry=Memory
 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
+# Optionally you can specifiy a specific password provider implementation 
which overrides any globally configured provider
+synapse.datasources.lookupds.secretProvider=org.apache.synapse.commons.security.secret.handler.SharedSecretCallbackHandler
 synapse.datasources.lookupds.username=esb
+# Depending on the password provider used, you may have to use an encrypted 
password here!
 synapse.datasources.lookupds.password=esb
 synapse.datasources.lookupds.dsName=lookupdb
 synapse.datasources.lookupds.maxActive=100
 synapse.datasources.lookupds.maxIdle=20
 synapse.datasources.lookupds.maxWait=10000
 
+synapse.datasources.reportds.registry=JNDI
 synapse.datasources.reportds.type=PerUserPoolDataSource
 
synapse.datasources.reportds.cpdsadapter.factory=org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS
 
synapse.datasources.reportds.cpdsadapter.className=org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS
@@ -643,13 +651,32 @@
 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
+# Optionally you can specifiy a specific password provider implementation 
which overrides any globally configured provider
+synapse.datasources.reportds.secretProvider=org.apache.synapse.commons.security.secret.handler.SharedSecretCallbackHandler
 synapse.datasources.reportds.username=esb
+# Depending on the password provider used, you may have to use an encrypted 
password here!
 synapse.datasources.reportds.password=esb
 synapse.datasources.reportds.maxActive=100
 synapse.datasources.reportds.maxIdle=20
 synapse.datasources.reportds.maxWait=10000</pre>
+
+<p></p>
+
+<p>To secure data sources password, it is need to use the mechanism for
+<strong>securing secret Information</strong>. Please refer <strong>securing
+secret Information guide</strong>. If that mechanism is used, then passwords
+that have been specified are considered as aliases and those are used for
+picking actual passwords. To get password securely, it is needed to set the
+password provider for each data source. The password provider should be an
+implementation of
+<strong>org.apache.synapse.commons.security.secret.SecretCallbackHandler</strong>.
+There are few options and for more information please refer <strong>securing
+secret Information guide.</strong> </p>
+
+<p>For run this sample, you just need to uncomment
+<strong>secret-conf.properties, cipher-text.properties and
+datasources.properties</strong>. Those files are in conf directory. </p>
 </div>
 </div>
-
 </body>
 </html>

_______________________________________________
Esb-java-dev mailing list
[email protected]
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev

Reply via email to