[wsas-java-dev] svn commit r165 -
wsas/java/trunk/modules/samples/CommodityQuote/xdocs
svn at wso2.com
svn at wso2.com
Tue Dec 5 01:30:54 PST 2006
Author: chatra
Date: Tue Dec 5 01:30:53 2006
New Revision: 165
Modified:
wsas/java/trunk/modules/samples/CommodityQuote/xdocs/commodity_quote_sample.html
Log:
made improvements
Modified: wsas/java/trunk/modules/samples/CommodityQuote/xdocs/commodity_quote_sample.html
==============================================================================
--- wsas/java/trunk/modules/samples/CommodityQuote/xdocs/commodity_quote_sample.html (original)
+++ wsas/java/trunk/modules/samples/CommodityQuote/xdocs/commodity_quote_sample.html Tue Dec 5 01:30:53 2006
@@ -22,19 +22,19 @@
<h2>INTRODUCTION</h2>
<p>We will use this sample to demonstrate the capabilities of WSO2 Web
-Services Application Server , highlighting the ease of integration of quality
+Services Application Server, highlighting the ease of integration of quality
of service modules. In the context of this scenario, the use of security and
reliable messaging is emphasized on.</p>
<p>The Commodity Quote sample demonstrates the interactions between a simple
Web service client & and a CommodityQuote service. This service provides
-information of chemical agents in d-block.</p>
+information of chemical agents in d-block of the periodic table.</p>
<p>The following section describes the service in detail.</p>
<h2>SCENARIO</h2>
-<p>In this sample the client queries the CommodityQuote service for the
+<p>In this sample, the client queries the CommodityQuote service for the
available chemical elements (symbols). Using one of these symbols, the client
gets stock quotes from the CommodityQuote service.</p>
@@ -227,9 +227,9 @@
Security > Users > User Management. The add a user "client"
with password "testing". Then go to Services > CommodityQuote >
Security Configuration and select "Username Token authentication" and
- select "Continue". There select user "client" and apply it. (User can
- add many users and many roles as they please. For this demonstration,
- the author will use "client" users)</li>
+ select "Continue". In the next page select user "client" and apply
+ it. (User can add many users and many roles as they please. For this
+ demonstration, the author will use "client" users)</li>
<li><strong>Client Side:</strong>
<pre>
STARTING COMMODITY QUOTE SAMPLE CLIENT
@@ -291,19 +291,20 @@
</li>
</ul>
</li>
- <li>Requests as well as responses are signed For this scenario to work,
- commodity quote service need to import a certificate. Let this
- certificate be service.jks. In addition to this client need to import
- private key of the service.jks. Let say this is client.jks. For this
- demonstration purpose service.jks and client.jks will be shipped with the
+ <li>Requests as well as responses are signed for this scenario to work.
+ Commodity quote service needs to import a certificate. Let this
+ certificate be service.jks. In addition to this, client needs to import
+ the private key of the service.jks. Let's say this is client.jks. For
+ this demonstration, service.jks and client.jks will be shipped with the
sample and it's located at WSO2WSAS_HOME/samples/CommodityQuote/keys/
<ul>
<li><strong>Server side:</strong> Go to Key stores and upload the
service.jks. Keystore password will be "testing" and private key
store password will be "testing". Then go to Services >
- CommodityQuote > Security Configuration. Select Trusted
- Certificate Stores as service.jks and select private keystore as
- service.jks</li>
+ CommodityQuote > Security Configuration and select "Sign only",
+ after which select "Continue". Select Trusted Certificate Stores as
+ service.jks and select private keystore as service.jks in the next
+ page.</li>
<li><strong>Client side:</strong>
<pre>STARTING COMMODITY QUOTE SAMPLE CLIENT
=============================
@@ -401,7 +402,7 @@
<h4><em>sample 4: -qos securerm : When Rampart/Rahas and Sandesha have been
engaged.</em></h4>
-<b>Scenarios 1 & 9 with Secure-RM are not supported since since HTTPS is
+<b>Scenarios 1 & 9 with Secure-RM are not supported since HTTPS is
required on the client side receiver. This is a limitation of the client.</b>
<p>From CommodityQuote directory type:</p>
More information about the Wsas-java-dev
mailing list