Author: charitha Date: Fri Jun 6 07:48:06 2008 New Revision: 18084 URL: http://wso2.org/svn/browse/wso2?view=rev&revision=18084
Log: Updated commodity_quote_guide.xml with instructions to engage mercury module and removed sandesha2 specific details Modified: branches/wsas/java/2.3/wsas/modules/documentation/src/site/xdoc/commodity_quote_guide.xml Modified: branches/wsas/java/2.3/wsas/modules/documentation/src/site/xdoc/commodity_quote_guide.xml URL: http://wso2.org/svn/browse/wso2/branches/wsas/java/2.3/wsas/modules/documentation/src/site/xdoc/commodity_quote_guide.xml?rev=18084&r1=18083&r2=18084&view=diff ============================================================================== --- branches/wsas/java/2.3/wsas/modules/documentation/src/site/xdoc/commodity_quote_guide.xml (original) +++ branches/wsas/java/2.3/wsas/modules/documentation/src/site/xdoc/commodity_quote_guide.xml Fri Jun 6 07:48:06 2008 @@ -160,9 +160,7 @@ be discussed below. <strong>To run the sample with these QoS, you must engage the respective modules for the CommodityQuote service on the WSO2 WSAS server.</strong> <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>rm - Mercury </li> <li>secure - Rampart/Rahas: WSO2 WSAS distribution compliant with fifteen security scenarios. @@ -192,7 +190,7 @@ version) and extract the jar files local_policy.jar and US_export_policy.jar to $JAVA_HOME/jre/lib/security.</p> </li> - <li>securerm - Both Sandesha2 and Rampart. securerm option will + <li>securerm - Both Mercury and Rampart. securerm option will demonstrate all the security scenarios with reliable messaging. </li> </ul> @@ -474,7 +472,7 @@ scenario.</strong></li> </ol> -<h4><em>sample 3: -qos rm : When Sandesha2 module has been engaged.</em></h4> +<h4><em>sample 3: -qos rm : When Mercury module has been engaged.</em></h4> <p>From CommodityQuote directory type:</p> <pre> $ ./run-client.sh -qos rm -e http://127.0.0.1:9762/services/CommodityQuote @@ -497,7 +495,7 @@ : </pre> -<h4><em>sample 4: -qos securerm : When Rampart/Rahas and Sandesha have been +<h4><em>sample 4: -qos securerm : When Rampart/Rahas and Mercury have been engaged.</em></h4> <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> @@ -530,7 +528,7 @@ <li>Go to client repository and do the following ./run-client.sh -e mail:[EMAIL PROTECTED]/services/CommodityQuote. </li> - <li>To run the sample with RM enabled, first engaged Sandesha2-<version> to + <li>To run the sample with RM enabled, first engage Mercury-<version> 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-<version> @@ -559,21 +557,6 @@ <p></p> -<h2>Running the Sample with persistent RM</h2> -<ul> - <li>Set the 'Sandesha2StorageManager' 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> _______________________________________________ Wsas-java-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
