[wsas-java-dev] svn commit r71 -
wsas/java/trunk/modules/samples/CommodityQuote/xdocs
svn at wso2.com
svn at wso2.com
Fri Dec 1 08:07:33 PST 2006
Author: chatra
Date: Fri Dec 1 08:07:32 2006
New Revision: 71
Modified:
wsas/java/trunk/modules/samples/CommodityQuote/xdocs/commodity_quote_sample.html
Log:
minor change in title
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 Fri Dec 1 08:07:32 2006
@@ -1,186 +1,200 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html>
-<head>
- <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
- <title>Commodity Quote Sample Guide for WSO2 Web Services Application Server @wso2wsas_version@</title>
- <link href="css/wsas-dist-doc.css" rel="stylesheet" type="text/css"
- media="all" />
-</head>
-
-<body>
-<h1>Commodity Quote Sample Guide for WSO2 Web Services Application Server(WSO2 WSAS) @wso2wsas_version@</h1>
-
-<p> </p>
-<p><img alt="Figure:1" src="images/cse.jpg" /><br />
-</p>
-
-<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 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>
-
-<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
-available chemical elements (symbols). Using one of these symbols, the client
-gets stock quotes from the CommodityQuote service.</p>
-
-<h3>In summary the services are as follows:</h3>
-
-<p><img alt="Figure:2" src="images/scenario.jpg" /><br />
-</p>
-
-<h4>Services offered by CommodityQuote to Client</h4>
-<ul>
- <li>List stock symbols</li>
- <li>Get stock quote (name, symbol, price, high, low) and portfolio</li>
-</ul>
-
-<p><strong>Note</strong>: attributes of Stock Quote -name, symbol, selling
-price, high price, low price</p>
-
-<h2>HOW TO BUILD AND RUN THE SAMPLE</h2>
-
-<p>Commodity quote sample is in WSO2WSAS_HOME/samples/CommodityQuote. This
-sample emulates a simple "stock trader", where you can get the stock symbols
-and the stock quote for a particular stock symbol. In this case the stocks
-are elements in the periodic table, and their symbols are their chemical
-element symbols.</p>
-
-<p>To build the samples you need the <a href="http://ant.apache.org/">Apache
-Ant</a> build tool.</p>
-
-<h3>Now follow the simple instructions:</h3>
-<ol>
- <li>Run WSO2 WSAS. See <a
- href="../../../docs/installationguide.html">Installation Guide</a> for
- installation details.</li>
- <li>Switch to the CommodityQuote directory, e.g.</li>
- <pre> cd WSO2WSAS_HOME\samples\CommodityQuote</pre>
- <li>From there simply type</li>
- <pre> ant</pre>
-
- <h4>You should see messages like this:</h4>
- <pre>Buildfile: build.xml
-clean:
-init:
-
-[mkdir] Created dir: C:\wso2wsas- at wso2wsas_version@\samples\CommodityQuote\temp
-[mkdir] Created dir:
-C:\wso2wsas- at wso2wsas_version@\samples\CommodityQuote\temp\classes
-
-[some lines deleted here]
-
-build-all:
-[echo] Copying the created aar files in to the repository
-[copy] Copying 1 file to C:\wso2wsas- at wso2wsas_version@\repository\services
-
-BUILD SUCCESSFUL
-Total time: 11 seconds</pre>
-
- <p>The build automatically copies the .aar file containing the service into
- the repository.</p>
- <li>If you select the Services page in the Management Console, you should see the CommodityQuote service deployed. If you don't see it,
- the page will be refreshed once the deployment engine of Axis2 picks up
- the newly added .aar</li>
-
- <p>(See <a
- href="../../../docs/administratorguide.html">Administrator’s
- Guide</a> on how to sign into the Management Console and to navigate through
- it.)</p>
- <li>If you are still in the CommodityQuote directory, you will find the
- run-client.bat and run-client.sh files. To see the CommodityQuote in
- action you can use the following syntax on the command prompt.</li>
-
- <p><strong>On MS Windows:</strong></p>
-
- <p>run-client.bat [ -qos (rm|secure|securerm)] [ -e
- CommodityQuoteServiceURL]</p>
-
- <p><strong>On Unix/Linux:</strong></p>
-
- <p>run-client.sh [ -qos (rm|secure|securerm)] [ -e
- CommodityQuoteServiceURL]</p>
-
- <p><strong>Terms used:</strong></p>
-</ol>
-<ul>
- <li>-e : is the Endpoint Reference (EPR) of the CommodityQuote service.
- This can be obtained from the Management Console: The relevant
- service EPR can be found at Services > CommondityQuote (under services
- column) > End Points. For this sample the default URL is
- “http://127.0.0.1:9762/soap/CommodityQuote” in the case of
- the standalone distribution, and
- “http://127.0.0.1:9762/wso2wsas/soap/CommodityQuote” in the
- case of the embeddable version. In addition to this the ssl connection
- (https://127.0.0.1:9443/soap/CommodityQuote or https://127.0.0.1:9443/wso2wsas/soap/CommodityQuote)will be needed for security scenarios, which will be discussed later in this
-document. The default EPRs for http and https will be available in WSO2WSAS_HOME/samples/CommodityQuote/conf/default_epr.properties file.
-
- <p>In addition to that mail transport can also be used. In mail transport
- there should be two mail addresses to identify the client and server.
- Those are the EPRs needed to communicate. A mail server should be used in
- this case and two accounts should be created (A mail server like JAMES
- can be used for this purpose). One should correspond to WSO2 WSAS
- and the other one should correspond to the client. In addition to that
- Client's axis2.xml and server's axis2.xml should be configured to do SMTP
- and pop according to the mail server used. Here the EPR should be given
- as "mail:<mail id corresponds to the
- server>@localhost/soap/CommodityQuote". More details will be discussed later in this
- document. </p>
- </li>
- <li>-qos : This will represent rm, secure or securerm options, which will eventually engage
- respective modules to the CommodityQuote service. These modules can be easily engaged from
- WSO2 WSAS console. More details will be discussed below.
- <ul>
- <li>rm - Sandesha2: Sandesha2 configuration will be available from RM domain policies. We would only demonstrate the sample with the default policy available from Sandesha2</li>
- <li>secure - Rampart/Rahas: WSO2 WSAS distribution compliant with ten security scenarios.
-
- <ol>
- <li>Username Token authentication</li>
- <li>Requests as well as responses are signed</li>
- <li>Sign and encrypt using Basic256 algorithm suite</li>
- <li>Encrypt and sign using Basic256 algorithm suite</li>
- <li>Sign and encrypt using Basic256 algorithm suite and derived keys</li>
- <li>Sign and encrypt using TripleDesRsa15 algorithm suite</li>
- <li>Sign and encrypt using TripleDesRsa15 algorithm suite and derived keys</li>
- <li>Sign and encrypt using TripleDesRsa15 algorithm suite, derived keys and encrypt primary signature</li>
- <li>SecureConversation - Sign and encrypt - Service as STS - Bootstrap policy - UsernameToken with Timestamp over HTTPS</li>
- <li>SecureConversation - Sign and encrypt with signature encrypted - Service as STS - Bootstrap policy - Derived Key encr/sig based on an phemeral key</li>
-
- </ol>
- <p><strong>Note:</strong>
- Some of the scenarios listed above need provision for unlimited security jurisdiction. This will basically be couple of Jar files, which will be available at <a href="http://java.sun.com/javase/downloads/index.jsp">Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files.</a>
-Download jce_policy-x_y_z.zip and extract the jar files local_policy.jar and US_export_policy.jar to $JAVA_HOME/lib/security.
- </p>
- </li>
- <li>securerm - Both Sandesha2 and Rampart. securerm option will demonstrate all the
- security scenarios with reliable messaging.
- </li>
- </ul>
- </li>
-</ul>
-
-
-
-<h3>Let’s illustrate the above options with following samples:</h3>
-
-<h4><em>Sample 1: Without any module engaged.</em></h4>
-
-<p>From CommodityQuote directory type:</p>
-<pre> $ sh run-client.sh</pre>
-
-<p><strong>You should see:</strong></p>
-<pre>
-STARTING COMMODITY QUOTE SAMPLE CLIENT
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
+ "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
+<html>
+<head>
+ <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
+ <title>Commodity Quote Sample Guide for WSO2 Web Services Application
+ Server @wso2wsas_version@</title>
+ <link href="css/wsas-dist-doc.css" rel="stylesheet" type="text/css"
+ media="all" />
+</head>
+
+<body>
+<h1>Commodity Quote Sample Guide for WSO2 Web Services Application Server
+(WSO2 WSAS) for Java, v at wso2wsas_version@</h1>
+
+<p> </p>
+
+<p><img alt="Figure:1" src="images/cse.jpg" /><br />
+</p>
+
+<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
+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>
+
+<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
+available chemical elements (symbols). Using one of these symbols, the client
+gets stock quotes from the CommodityQuote service.</p>
+
+<h3>In summary the services are as follows:</h3>
+
+<p><img alt="Figure:2" src="images/scenario.jpg" /><br />
+</p>
+
+<h4>Services offered by CommodityQuote to Client</h4>
+<ul>
+ <li>List stock symbols</li>
+ <li>Get stock quote (name, symbol, price, high, low) and portfolio</li>
+</ul>
+
+<p><strong>Note</strong>: attributes of Stock Quote -name, symbol, selling
+price, high price, low price</p>
+
+<h2>HOW TO BUILD AND RUN THE SAMPLE</h2>
+
+<p>Commodity quote sample is in WSO2WSAS_HOME/samples/CommodityQuote. This
+sample emulates a simple "stock trader", where you can get the stock symbols
+and the stock quote for a particular stock symbol. In this case the stocks
+are elements in the periodic table, and their symbols are their chemical
+element symbols.</p>
+
+<p>To build the samples you need the <a href="http://ant.apache.org/">Apache
+Ant</a> build tool.</p>
+
+<h3>Now follow the simple instructions:</h3>
+<ol>
+ <li>Run WSO2 WSAS. See <a
+ href="../../../docs/installationguide.html">Installation Guide</a> for
+ installation details.</li>
+ <li>Switch to the CommodityQuote directory, e.g.</li>
+ <pre> cd WSO2WSAS_HOME\samples\CommodityQuote</pre>
+ <li>From there simply type</li>
+ <pre> ant</pre>
+
+ <h4>You should see messages like this:</h4>
+ <pre>Buildfile: build.xml
+clean:
+init:
+
+[mkdir] Created dir: C:\wso2wsas- at wso2wsas_version@\samples\CommodityQuote\temp
+[mkdir] Created dir:
+C:\wso2wsas- at wso2wsas_version@\samples\CommodityQuote\temp\classes
+
+[some lines deleted here]
+
+build-all:
+[echo] Copying the created aar files in to the repository
+[copy] Copying 1 file to C:\wso2wsas- at wso2wsas_version@\repository\services
+
+BUILD SUCCESSFUL
+Total time: 11 seconds</pre>
+
+ <p>The build automatically copies the .aar file containing the service into
+ the repository.</p>
+ <li>If you select the Services page in the Management Console, you should
+ see the CommodityQuote service deployed. If you don't see it, the page
+ will be refreshed once the deployment engine of Axis2 picks up the newly
+ added .aar</li>
+
+ <p>(See <a
+ href="../../../docs/administratorguide.html">Administrator’s
+ Guide</a> on how to sign into the Management Console and to navigate
+ through it.)</p>
+ <li>If you are still in the CommodityQuote directory, you will find the
+ run-client.bat and run-client.sh files. To see the CommodityQuote in
+ action you can use the following syntax on the command prompt.</li>
+
+ <p><strong>On MS Windows:</strong></p>
+
+ <p>run-client.bat [ -qos (rm|secure|securerm)] [ -e
+ CommodityQuoteServiceURL]</p>
+
+ <p><strong>On Unix/Linux:</strong></p>
+
+ <p>run-client.sh [ -qos (rm|secure|securerm)] [ -e
+ CommodityQuoteServiceURL]</p>
+
+ <p><strong>Terms used:</strong></p>
+</ol>
+<ul>
+ <li>-e : is the Endpoint Reference (EPR) of the CommodityQuote service.
+ This can be obtained from the Management Console: The relevant service
+ EPR can be found at Services > CommondityQuote (under services column)
+ > End Points. For this sample the default URL is
+ “http://127.0.0.1:9762/soap/CommodityQuote” in the case of
+ the standalone distribution, and
+ “http://127.0.0.1:9762/wso2wsas/soap/CommodityQuote” in the
+ case of the embeddable version. In addition to this the ssl connection
+ (https://127.0.0.1:9443/soap/CommodityQuote or
+ https://127.0.0.1:9443/wso2wsas/soap/CommodityQuote)will be needed for
+ security scenarios, which will be discussed later in this document. The
+ default EPRs for http and https will be available in
+ WSO2WSAS_HOME/samples/CommodityQuote/conf/default_epr.properties file.
+ <p>In addition to that mail transport can also be used. In mail transport
+ there should be two mail addresses to identify the client and server.
+ Those are the EPRs needed to communicate. A mail server should be used in
+ this case and two accounts should be created (A mail server like JAMES
+ can be used for this purpose). One should correspond to WSO2 WSAS and the
+ other one should correspond to the client. In addition to that Client's
+ axis2.xml and server's axis2.xml should be configured to do SMTP and pop
+ according to the mail server used. Here the EPR should be given as
+ "mail:<mail id corresponds to the
+ server>@localhost/soap/CommodityQuote". More details will be discussed
+ later in this document.</p>
+ </li>
+ <li>-qos : This will represent rm, secure or securerm options, which will
+ eventually engage respective modules to the CommodityQuote service. These
+ modules can be easily engaged from WSO2 WSAS console. More details will
+ be discussed below.
+ <ul>
+ <li>rm - Sandesha2: Sandesha2 configuration will be available from RM
+ domain policies. We would only demonstrate the sample with the
+ default policy available from Sandesha2</li>
+ <li>secure - Rampart/Rahas: WSO2 WSAS distribution compliant with ten
+ security scenarios.
+ <ol>
+ <li>Username Token authentication</li>
+ <li>Requests as well as responses are signed</li>
+ <li>Sign and encrypt using Basic256 algorithm suite</li>
+ <li>Encrypt and sign using Basic256 algorithm suite</li>
+ <li>Sign and encrypt using Basic256 algorithm suite and derived
+ keys</li>
+ <li>Sign and encrypt using TripleDesRsa15 algorithm suite</li>
+ <li>Sign and encrypt using TripleDesRsa15 algorithm suite and
+ derived keys</li>
+ <li>Sign and encrypt using TripleDesRsa15 algorithm suite, derived
+ keys and encrypt primary signature</li>
+ <li>SecureConversation - Sign and encrypt - Service as STS -
+ Bootstrap policy - UsernameToken with Timestamp over HTTPS</li>
+ <li>SecureConversation - Sign and encrypt with signature encrypted
+ - Service as STS - Bootstrap policy - Derived Key encr/sig based
+ on an phemeral key</li>
+ </ol>
+ <p><strong>Note:</strong> Some of the scenarios listed above need
+ provision for unlimited security jurisdiction. This will basically be
+ couple of Jar files, which will be available at <a
+ href="http://java.sun.com/javase/downloads/index.jsp">Java
+ Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy
+ Files.</a> Download jce_policy-x_y_z.zip and extract the jar files
+ local_policy.jar and US_export_policy.jar to
+ $JAVA_HOME/lib/security.</p>
+ </li>
+ <li>securerm - Both Sandesha2 and Rampart. securerm option will
+ demonstrate all the security scenarios with reliable messaging.</li>
+ </ul>
+ </li>
+</ul>
+
+<h3>Let’s illustrate the above options with following samples:</h3>
+
+<h4><em>Sample 1: Without any module engaged.</em></h4>
+
+<p>From CommodityQuote directory type:</p>
+<pre> $ sh run-client.sh</pre>
+
+<p><strong>You should see:</strong></p>
+<pre>STARTING COMMODITY QUOTE SAMPLE CLIENT
=============================
Sample will be invoked using following parameters ..
@@ -192,31 +206,32 @@
(1) getQuote
(2) getSymbols
(3) Exit
-:
-</pre>
-
-<h4><em>Sample 2: With -qos secure : Rampart/Rahas </em></h4>
-
-<p>From CommodityQuote directory type:</p>
+:</pre>
+
+<h4><em>Sample 2: With -qos secure : Rampart/Rahas</em></h4>
+
+<p>From CommodityQuote directory type:</p>
<pre> $ sh run-client.sh -qos secure</pre>
-<p>
-<pre>
-STARTING COMMODITY QUOTE SAMPLE CLIENT
+<p></p>
+<pre>STARTING COMMODITY QUOTE SAMPLE CLIENT
=============================
Enter security scenario [1 .. 10]...
{select a value between 1 to 10}
-
</pre>
-</p>
-
<ol>
- <li>Username Token authentication
- <ul>
- <li><strong>Server Side:</strong> Logging to management console. Go to 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) <font color="red">//TODO pics</font> </li>
- <li><strong>Client Side:</strong>
- <pre>
+ <li>Username Token authentication
+ <ul>
+ <li><strong>Server Side:</strong> Logging to management console. Go to
+ 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) //TODO pics</li>
+ <li><strong>Client Side:</strong>
+ <pre>
STARTING COMMODITY QUOTE SAMPLE CLIENT
=============================
@@ -273,18 +288,24 @@
</pre>
-
- </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 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". The go to Services > CommodityQuote > Security Configuration. Select Trusted Certificate Stores as service.jks and select private keystore as service.jks <font color="red">//TODO pics</font></li>
- <li><strong>Client side:</strong>
- <pre>
-STARTING COMMODITY QUOTE SAMPLE CLIENT
+ </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
+ 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". The go to Services >
+ CommodityQuote > Security Configuration. Select Trusted
+ Certificate Stores as service.jks and select private keystore as
+ service.jks //TODO pics</li>
+ <li><strong>Client side:</strong>
+ <pre>STARTING COMMODITY QUOTE SAMPLE CLIENT
=============================
Enter security scenario [1 .. 10]...
@@ -323,55 +344,42 @@
</pre>
- </li>
- </ul>
+ </li>
+ </ul>
+ </li>
+ <li>Sign and encrypt using Basic256 algorithm suite<br />
+ <strong>Configuration as in 2. Yet select this and configure</strong></li>
+ <li>Encrypt and sign using Basic256 algorithm suite<br />
+ <strong>Configuration as in 2. Yet select this and configure</strong></li>
+ <li>Sign and encrypt using Basic256 algorithm suite and derived keys<br />
+ <strong>Configuration as in 2. Yet select this and configure</strong></li>
+ <li>Sign and encrypt using TripleDesRsa15 algorithm suite<br />
+ <strong>Configuration as in 2. Yet select this and configure</strong></li>
+ <li>Sign and encrypt using TripleDesRsa15 algorithm suite and derived
+ keys<br />
+ <strong>Configuration as in 2. Yet select this and configure</strong></li>
+ <li>Sign and encrypt using TripleDesRsa15 algorithm suite, derived keys and
+ encrypt primary signature<br />
+ <strong>Configuration as in 2. Yet select this and configure</strong></li>
+ <li>SecureConversation - Sign and encrypt - Service as STS - Bootstrap
+ policy - UsernameToken with Timestamp over HTTPS<br />
+ <strong>Select "client" as the user.</strong></li>
+ <li>SecureConversation - Sign and encrypt with signature encrypted -
+ Service as STS - Bootstrap policy - Derived Key encr/sig based on an
+ phemeral key<br />
+ <strong>Select "client" as the user.</strong></li>
+</ol>
+
+<h4><em>sample 3: -qos rm : Where Sandesha2 module has been
+engaged.</em></h4>
+
+<p>From CommodityQuote directory type:</p>
+<pre> $ sh run-client.sh -qos rm -e http://127.0.0.1:9762/soap/CommodityQuote
+ or
+ $ sh run-client.sh -qos rm</pre>
- </li>
- <li>Sign and encrypt using Basic256 algorithm suite<br></br>
-
- <strong>Configuration as in 2. Yet select this and configure</strong>
- </li>
- <li>Encrypt and sign using Basic256 algorithm suite<br></br>
-
- <strong>Configuration as in 2. Yet select this and configure</strong>
- </li>
- <li>Sign and encrypt using Basic256 algorithm suite and derived keys<br></br>
-
- <strong>Configuration as in 2. Yet select this and configure</strong>
- </li>
- <li>Sign and encrypt using TripleDesRsa15 algorithm suite<br></br>
-
- <strong>Configuration as in 2. Yet select this and configure</strong>
- </li>
- <li>Sign and encrypt using TripleDesRsa15 algorithm suite and derived keys<br></br>
-
- <strong>Configuration as in 2. Yet select this and configure</strong>
- </li>
- <li>Sign and encrypt using TripleDesRsa15 algorithm suite, derived keys and encrypt primary signature<br></br>
-
- <strong>Configuration as in 2. Yet select this and configure</strong>
- </li>
- <li>SecureConversation - Sign and encrypt - Service as STS - Bootstrap policy - UsernameToken with Timestamp over HTTPS<br></br>
-
- <strong>Select "client" as the user.</strong>
- </li>
- <li>SecureConversation - Sign and encrypt with signature encrypted - Service as STS - Bootstrap policy - Derived Key encr/sig based on an phemeral key<br></br>
-
- <strong>Select "client" as the user.</strong>
- </li>
-
- </ol>
-</ol>
-
-<h4><em>sample 3: -qos rm : Where Sandesha2 module has been engaged.</em></h4>
-
-<p>From CommodityQuote directory type:</p>
-<pre> $ sh run-client.sh -qos rm -e http://127.0.0.1:9762/soap/CommodityQuote
- or
- $ sh run-client.sh -qos rm</pre>
-
-<p> </p>
-<pre>
+<p> </p>
+<pre>
STARTING COMMODITY QUOTE SAMPLE CLIENT
=============================
@@ -387,77 +395,81 @@
(3) Exit
:
+</pre>
-</pre>
-
-<h4><em>sample 4: -qos securerm : When Rampart/Rahas and Sandesha been engaged. <font color="red">//TODO pics</font></em></h4>
-<p>From CommodityQuote directory type:</p>
-<pre> $ sh run-client.sh -qos securerm</pre>
+<h4><em>sample 4: -qos securerm : When Rampart/Rahas and Sandesha been
+engaged. //TODO pics</em></h4>
-<h4><em>sample 5: Invoking Commodity quote sample using mail transport with/without RM/Sec</em></h4>
+<p>From CommodityQuote directory type:</p>
+<pre> $ sh run-client.sh -qos securerm</pre>
+<h4><em>sample 5: Invoking Commodity quote sample using mail transport
+with/without RM/Sec</em></h4>
<ol>
-<li> Unzip the wso2wsas-standalone-edition-java-SNAPSHOT.zip. I assumed the unzipped location as WSO2WSAS_HOME.</li>
+ <li>Unzip the wso2wsas-standalone-edition-java-SNAPSHOT.zip. I assumed the
+ unzipped location as WSO2WSAS_HOME.</li>
+ <li>Go to WSO2WSAS_HOME/samples/CommodityQuote folder. Run "ant" this will
+ copy the generated CommodityQuote.aar to
+ WSO2WSAS_HOME/repository/services.</li>
+ <li>In mail transport there should be two mail addresses to identify the
+ client and server. Thus, these are the EPR's need to communicate. For
+ this example I've create two email addressed "red" and "blue", where
+ "red" corresponds to WSO2WSAS server and "blue" corresponds to the
+ client. I've used JAMES Mail server to create the two accounts.</li>
+ <li>Client's axis2.xml and server's axis2.xml has been configured to do
+ SMTP and POP from JAMES. {See, axis2.xml in WSO2WSAS_HOME/conf/ to server
+ config and WSO2WSAS_HOME/samples/CommodidtyQuote/conf for client
+ config}</li>
+ <li>Start the server WSO2WSAS_HOME/bin/run.sh</li>
+ <li>Go to client repository and do the following sh run-client.sh -e
+ mail:red at localhost/soap/CommodityQuote. </li.></li>
+ <li>To run the sample with RM enabled, first engaged Sandesha2-1.1 to
+ CommodityQuote service. Go to admin page using https://host:9443/,
+ Username and password will be "admin". Go to
+ Services/CommodityQuote/Manage Module Engagement and engage Sandesha2-1.1
+ mar. Go to client repo and use the following command, sh run-client.sh -e
+ mail:red at localhost/soap/CommodityQuote -qos rm</li>
+ <li>POP interval for the client and server has been given as 3000 ms. If
+ user wants to change this value, in the respective axis2.xml, find
+ following, <transportReceiver name="mail"
+ class="org.apache.axis2.transport.mail.SimpleMailListener"> ...
+ <parameter name="transport.listener.interval"
+ locked="false">3000</parameter> ... </transportReceiver>
+ and change the interval as you pleased.</li>
+</ol>
-<li>Go to WSO2WSAS_HOME/samples/CommodityQuote folder. Run "ant" this will copy the generated CommodityQuote.aar to WSO2WSAS_HOME/repository/services.</li>
-
-<li>In mail transport there should be two mail addresses to identify the client and server. Thus, these are the EPR's need to communicate. For this example I've create two email addressed "red" and "blue", where "red" corresponds to WSO2WSAS server and "blue" corresponds to the client. I've used JAMES Mail server to create the two accounts.</li>
-
-<li>Client's axis2.xml and server's axis2.xml has been configured to do SMTP and POP from JAMES. {See, axis2.xml in WSO2WSAS_HOME/conf/ to server config and WSO2WSAS_HOME/samples/CommodidtyQuote/conf for client config}</li>
-
-<li>Start the server WSO2WSAS_HOME/bin/run.sh </li>
-
-<li>Go to client repository and do the following
- sh run-client.sh -e mail:red at localhost/soap/CommodityQuote. </li.
-
-<li>To run the sample with RM enabled, first engaged Sandesha2-1.1 to CommodityQuote service.
- Go to admin page using https://host:9443/, Username and password will be "admin".
- Go to Services/CommodityQuote/Manage Module Engagement and engage Sandesha2-1.1 mar.
- Go to client repo and use the following command,
- sh run-client.sh -e mail:red at localhost/soap/CommodityQuote -qos rm </li>
-
-<li>POP interval for the client and server has been given as 3000 ms. If user wants to change this value, in the respective axis2.xml, find following,
- <transportReceiver name="mail" class="org.apache.axis2.transport.mail.SimpleMailListener">
- ...
- <parameter name="transport.listener.interval" locked="false">3000</parameter>
- ...
- </transportReceiver>
+<p></p>
-and change the interval as you pleased. </li>
-
-</ol>
-<p></p>
-
-<p>As you will be able to see, with the rm option, the time to receive the
-response for the very first request will be comparatively larger. This is due
-to the control messages that are sent initially, in order to establish the
-reliable messaging channel.</p>
-
-<p>Try playing around with the above options and see how it works for
-yourself!</p>
-
-<p></p>
-
-<h2>Running the Sample with persistent RM</h2>
-<ul>
- <li>Set the 'SandeshaStorageManager' property of the axis2.xml of the
- server side to 'persistent'.</li>
- <li>Start the WSO2 Web Services Application Server.</li>
- <li>Engage the Sandesha2 module to Commodity Quote service.</li>
- <li>Run the client with QOS 'rm' and issue a command (e.g. getSymbols).</li>
- <li>Before this command gets completed (before response is received)
- shutdown the server.</li>
- <li>Then start the server again.</li>
- <li>The client should now show the response.</li>
-</ul>
-
-<p></p>
-
-<h2>APPENDIX</h2>
-<ul>
- <li>WSDL for services offered by Commodity Quote service to Client
- –“<a
- href="../wsdl/CommodityQuote.wsdl">/samples/CommodityQuote/wsdl/Trader.wsdl</a>”</li>
-</ul>
-</body>
-</html>
+<p>As you will be able to see, with the rm option, the time to receive the
+response for the very first request will be comparatively larger. This is due
+to the control messages that are sent initially, in order to establish the
+reliable messaging channel.</p>
+
+<p>Try playing around with the above options and see how it works for
+yourself!</p>
+
+<p></p>
+
+<h2>Running the Sample with persistent RM</h2>
+<ul>
+ <li>Set the 'SandeshaStorageManager' property of the axis2.xml of the
+ server side to 'persistent'.</li>
+ <li>Start the WSO2 Web Services Application Server.</li>
+ <li>Engage the Sandesha2 module to Commodity Quote service.</li>
+ <li>Run the client with QOS 'rm' and issue a command (e.g. getSymbols).</li>
+ <li>Before this command gets completed (before response is received)
+ shutdown the server.</li>
+ <li>Then start the server again.</li>
+ <li>The client should now show the response.</li>
+</ul>
+
+<p></p>
+
+<h2>APPENDIX</h2>
+<ul>
+ <li>WSDL for services offered by Commodity Quote service to Client
+ –“<a
+ href="../wsdl/CommodityQuote.wsdl">/samples/CommodityQuote/wsdl/Trader.wsdl</a>”</li>
+</ul>
+</body>
+</html>
More information about the Wsas-java-dev
mailing list