Author: asankha
Date: Mon Nov 5 20:15:08 2007
New Revision: 592262
URL: http://svn.apache.org/viewvc?rev=592262&view=rev
Log:
sample setup guide doc changes
Modified:
webservices/synapse/branches/1.1/src/site/resources/Synapse_Samples_Setup.html
Modified:
webservices/synapse/branches/1.1/src/site/resources/Synapse_Samples_Setup.html
URL:
http://svn.apache.org/viewvc/webservices/synapse/branches/1.1/src/site/resources/Synapse_Samples_Setup.html?rev=592262&r1=592261&r2=592262&view=diff
==============================================================================
---
webservices/synapse/branches/1.1/src/site/resources/Synapse_Samples_Setup.html
(original)
+++
webservices/synapse/branches/1.1/src/site/resources/Synapse_Samples_Setup.html
Mon Nov 5 20:15:08 2007
@@ -105,29 +105,29 @@
<p></p>
-<p>Synapse ships with a set of working examples that demonstrates some of the
+<p>Synapse ships with a set of working examples that demonstrate some of the
basic features and capabilities of Synapse. A set of sample clients and
-services are provided in addition to the sample configurations, and scripts
-are provided to execute the sample scenarios as explained below. </p>
+services are provided in addition to the sample configurations. Scripts are
+provided to execute the sample scenarios as explained below. </p>
-<h4>Pre-requisites</h4>
+<h4>Prerequisites</h4>
-<p>You will need a Java development kit version 1.5.x or later and Apache Ant
-1.6.5 or later at a minimum to try out the samples. Ant can be downloaded
-from http://ant.apache.org. The JMS examples could be executed against an
-ActiveMQ installation by default (or another JMS provider with
-configuration).</p>
+<p>To try out the samples you will need Java development kit version 1.5.x or
+later and Apache Ant version 1.6.5 or later. Ant can be downloaded from
+http://ant.apache.org. The JMS examples can be executed against an ActiveMQ
+installation by default (or another JMS provider with relevant configuration
+changes.)</p>
<p></p>
-<p>Note*: The samples and the documentation assumes that you are running
-Synapse in DEBUG mode. You could switch from the default INFO log messages to
+<p>Note*: The samples and the documentation assume that you are running
+Synapse in DEBUG mode. You can switch from the default INFO log messages to
DEBUG log messages by changing the line
"log4j.category.org.apache.synapse=INFO" as
"log4j.category.org.apache.synapse=DEBUG" in the lib/log4j.properties
file.</p>
-<h2>Understanding the samples</h2>
+<h2>Understanding the Samples</h2>
<table border="1" style="width: 100%">
<caption></caption>
@@ -150,35 +150,35 @@
<tr>
<td></td>
<td></td>
- <td>SecureStockQuoteService etc..</td>
+ <td>SecureStockQuoteService etc.</td>
</tr>
</tbody>
</table>
<p>The above diagram depicts the interactions between the clients, Synapse
-and services at a high level. The Clients are able to send SOAP/REST or POX
-messages over transports such as http/s or JMS with WS-Addressing,
-WS-Security or WS-Reliable messaging. They could send binary optimized
-content using MTOM or SwA or binary or plain text JMS messages. After
-mediation through Synapse, the requests are passed over to the sample
-services. The sample clients and services are explained below.</p>
+and the services at a higher level. The Clients are able to send SOAP/REST or
+POX messages over transports such as http/s or JMS with WS-Addressing,
+WS-Security or WS-Reliable messaging. They can send binary optimized content
+using MTOM or SwA or binary or plain text JMS messages. After mediation
+through Synapse, the requests are passed over to the sample services. The
+sample clients and services are explained below.</p>
<p></p>
-<h2>Using the sample clients</h2>
+<h2>Using the Sample Clients</h2>
<p></p>
-<p>The sample clients could be executed from the samples/axis2Client
-directory through the provided ant script. Simply executing 'ant' displays
-the available clients and some of the sample options used to configure them.
-The sample clients available are listed below:</p>
+<p>The sample clients can be executed from the samples/axis2Client directory
+through the provided ant script. Simply executing 'ant' displays the
+available clients and some of the sample options used to configure them. The
+sample clients available are listed below:</p>
-<h3>1. Stock quote client</h3>
+<h3>1. Stock Quote Client</h3>
<p></p>
-<p>This is a simple SOAP client that could send stock quote requests, and
+<p>This is a simple SOAP client that can send stock quote requests, and
receive and display the last sale price for a stock symbol. </p>
<pre>ant stockquote [-Dsymbol=IBM|MSFT|SUN|..]
[-Dmode=quote | customquote | fullquote | placeorder | marketactivity]
@@ -190,7 +190,7 @@
payloads listed below as SOAP messages:</p>
<ul>
<li>quote - send a quote request for a single stock as follows. The
- response contains the last sales price for the stock which would be
+ response contains the last sales price for the stock which will be
displayed
<pre><m:getQuote xmlns:m="http://services.samples/xsd">
<m:request>
@@ -198,11 +198,11 @@
</m:request>
</m:getQuote></pre>
</li>
- <li>customquote - send a quote request in a custom format. Synapse 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
- be transformed again to a custom response format and returned to the
- client, which will then display the last sales price.
+ <li>customquote - send a quote request in a custom format. Synapse will
+ transform this custom request to the standard stock quote request format
+ and send it to the service. Upon receipt of the response, it will be
+ transformed again to a custom response format and returned to the client,
+ which will then display the last sales price.
<pre><m0:checkPriceRequest
xmlns:m0="http://www.apache-synapse.org/test">
<m0:Code>symbol</m0:Code>
</m0:checkPriceRequest></pre>
@@ -239,17 +239,17 @@
<p>Note : See samples/axis2Client/src/samples/common/StockQuoteHandler.java
for sample responses expected by the clients.</p>
-<h4>Smart client mode:</h4>
+<h4>Smart Client Mode:</h4>
<p>The 'addurl' property sets the WS-Addressing EPR, and the 'trpurl' sets a
transport URL for a message. Thus by specifying both of these properties, the
-client could operate in the 'smart client' mode, where the addressing EPR
-could specify the ultimate receiver, while the transport URL set to Synapse
-would ensure that any necessary mediation takes place before the message is
+client can operate in the 'smart client' mode, where the addressing EPR can
+specify the ultimate receiver, while the transport URL set to Synapse will
+ensure that any necessary mediation takes place before the message is
delivered to the ultimate reciver. </p>
<pre>e.g: ant stockquote -Daddurl=<addressingEPR>
-Dtrpurl=<synapse></pre>
-<h4>Gateway / Dumb client mode:</h4>
+<h4>Gateway / Dumb Client Mode:</h4>
<p>By specifying only a transport URL, the client operates in the 'dumb
client' mode, where it sends the message to Synapse and depends on the
@@ -257,12 +257,12 @@
destination.</p>
<pre>e.g: ant stockquote -Dtrpurl=<synapse></pre>
-<h4>Proxy client mode:</h4>
+<h4>Proxy Client Mode:</h4>
<p>In this mode, the client uses the 'prxurl' as a http proxy to send the
-request. Thus by setting the 'prxurl' to Synapse, the client could ensure
-that the message would reach Synapse for mediation. The client could
-optionally set a WS-Addressing EPR if required.</p>
+request. Thus by setting the 'prxurl' to Synapse, the client can ensure that
+the message will reach Synapse for mediation. The client can optionally set a
+WS-Addressing EPR if required.</p>
<pre>e.g: ant stockquote -Dprxurl=<synapse>
[-Daddurl=<addressingEPR>]</pre>
<p></p>
@@ -270,27 +270,27 @@
<p>Specifying a policy</p>
<p>By specifying a WS-Policy using the 'policy' property, QoS aspects such as
-WS-Security could be enforced on the request. The policy could specify
-details such as timestamps, signatures and encryption. See Apache Axis2 and
-Apache Rampart documentation for more information.</p>
+WS-Security can be enforced on the request. The policy can specify details
+such as timestamps, signatures and encryption. See Apache Axis2 and Apache
+Rampart documentation for more information.</p>
<p></p>
-<h3>2. Generic JMS client</h3>
+<h3>2. Generic JMS Client</h3>
<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.
-The 'jms_type' property could specify 'text', 'binary' or 'pox' to specify
-the type of message payload. </p>
+The 'jms_type' property can specify 'text', 'binary' or 'pox' to specify the
+type of message payload. </p>
<p></p>
-<p>The plain text payload for a 'text' message could 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 would
+<p>The plain text payload for a 'text' message can be specified through the
+'payload' property. For binary messages, the 'payload' property will contain
+the path to the binary file. For POX messages, the 'payload' property will
hold a stock symbol name to be used within the POX request for stock order
placement request.</p>
@@ -305,22 +305,22 @@
<p></p>
-<h3>3. MTOM / SwA client</h3>
+<h3>3. MTOM / SwA Client</h3>
<p></p>
<p>The MTOM / SwA client is able to 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' could specify 'mtom' or 'swa'
+save it as a temporary file. The 'opt_mode' can specify 'mtom' or 'swa'
respectively for the above mentioned optimizations. Optionally the path to a
-custom file could be specified through the 'opt_file' property, and the
-destination address could be changed through the 'opt_url' property if
+custom file can be specified through the 'opt_file' property, and the
+destination address canou be changed through the 'opt_url' property if
required.</p>
<pre>e.g. ant optimizeclient -Dopt_mode=[mtom | swa]</pre>
<p></p>
-<h2>Starting the sample services</h2>
+<h2>Starting the Sample Services</h2>
<p></p>
@@ -330,8 +330,7 @@
and handling of binary content using MTOM and SwA.</p>
<p>The sample services can be found in the samples/axis2Server/src directory
-and could be built and deployed using ant from within each service
-directory</p>
+and can be built and deployed using ant from within each service directory</p>
<pre>[EMAIL
PROTECTED]:/tmp/synapse-1.1/samples/axis2Server/src/SimpleStockQuoteService$ ant
Buildfile: build.xml
...
@@ -349,7 +348,7 @@
server with the http transport listener on port 9000 and https on 9002
respectively. To enable JMS transport, you will need to setup and start a JMS
provider. An ActiveMQ 4.0.1 or later JMS server on the local machine is
-supported by default, and could be easily enabled by uncommenting the JMS
+supported by default, and can be easily enabled by uncommenting the JMS
transport from the repository/conf/axis2.xml</p>
<p></p>
@@ -378,7 +377,7 @@
uploadFileUsingSwA(in-out) and oneWayUploadUsingMTOM(in-only) and
demonstrates the use of MTOM and SwA. The uploadFileUsingMTOM and
uploadFileUsingSwA operations accept a binary image from the SOAP request as
-MTOM and SwA, and returns this image back again as the response; while the
+MTOM and SwA, and returns this image back again as the response, while the
oneWayUploadUsingMTOM saves the request message to disk.</p>
<p></p>
@@ -442,7 +441,7 @@
<p></p>
-<h2 id="mailsender">Setting up Mail transport sender</h2>
+<h2 id="mailsender">Setting up Mail Transport Sender</h2>
<p>To enable the mail transport, you need to uncomment the mail transport
sender configuration in the repository/conf/axis2.xml. Change the
@@ -459,16 +458,16 @@
<p></p>
-<h2 id="script">Configuring Synapse for Script Mediator support</h2>
+<h2 id="script">Configuring Synapse for Script Mediator Support</h2>
<p></p>
<p>The Synapse Script Mediator is a Synapse extension, and thus all
-pre-requisites are not bundled by default with the Synapse distribution.
+prerequisites are not bundled by default with the Synapse distribution.
Before you use some script mediators you may need to manually add the
required jar files to the Synapse lib directory, and optionally perform other
installation tasks as may be required by the individual scripting language.
-This is detailed in the following sections.</p>
+This is explained in the following sections.</p>
<h4>JavaScript support</h4>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
