Author: hiranya
Date: Fri Sep 24 06:11:58 2010
New Revision: 1000722
URL: http://svn.apache.org/viewvc?rev=1000722&view=rev
Log:
Documentation updates
Modified:
synapse/trunk/java/src/site/xdoc/Synapse_Samples.xml
Modified: synapse/trunk/java/src/site/xdoc/Synapse_Samples.xml
URL:
http://svn.apache.org/viewvc/synapse/trunk/java/src/site/xdoc/Synapse_Samples.xml?rev=1000722&r1=1000721&r2=1000722&view=diff
==============================================================================
--- synapse/trunk/java/src/site/xdoc/Synapse_Samples.xml (original)
+++ synapse/trunk/java/src/site/xdoc/Synapse_Samples.xml Fri Sep 24 06:11:58
2010
@@ -1143,10 +1143,10 @@ Content-ID:
</definitions></pre>
<p>
<strong>Objective: Demonstrate the failover sending</strong> </p>
+<p>
<strong>Prerequisites:</strong>
<br/>Start Synapse with sample configuration 53 (i.e. synapse -sample 53)
-<br/>Deploy the LoadbalanceFailoverService and start three instances of sample
Axis2 server as mentioned in sample 52.
-<p></p>
+<br/>Deploy the LoadbalanceFailoverService and start three instances of sample
Axis2 server as mentioned in sample 52.</p>
<p>Above configuration sends messages with the failover behavior. Initially
the server at port 9001 is treated as primary and other two are treated as
backups. Messages are always directed only to the primary server. If the
primary server has failed, next listed server is selected as the primary. Thus,
messages are sent successfully as long as there is at least one active server.
To test this, run the loadbalancefailover client to send infinite requests as
follows: </p>
<pre xml:space="preserve">ant loadbalancefailover</pre>
<p>You can see that all requests are processed by MyServer1. Now shutdown
MyServer1 and inspect the console output of the client. You will observe that
all subsequent requests are processed by MyServer2. </p>
@@ -1215,10 +1215,10 @@ Content-ID:
<p>
<strong>Objective: Demonstrate the loadbalancing with session affinity using
client initiated sessions</strong> </p>
<p>
-<strong>Prerequisites:</strong> </p>
-<p>Start Synapse with sample configuration 54 (i.e. synapse -sample 54). </p>
-<p>Deploy the LoadbalanceFailoverService and start three instances of the
sample Axis2 server as in sample 52. </p>
-<p></p>
+<strong>Prerequisites:</strong>
+<br/>Start Synapse with sample configuration 54 (i.e. synapse -sample 54).
+<br/>Deploy the LoadbalanceFailoverService and start three instances of the
sample Axis2 server as in sample 52. </p>
+
<p>Above configuration is same as the load balancing configuration in sample
52, except that the session type is specified as
"simpleClientSession". This is a client initiated session, which
means that the client generates the session identifier and sends it with each
request. In this sample session type, client adds a SOAP header named ClientID
containing the identifier of the client. Synapse binds this ID with a server on
the first request and sends all successive requests containing that ID to the
same server. Now switch to samples/axis2Client directory and run the client
using the following command to check this in action. </p>
<pre xml:space="preserve">ant loadbalancefailover -Dmode=session</pre>
<p>In the session mode, client continuously sends requests with three
different client (session) IDs. One ID is selected among these three IDs for
each request randomly. Then client prints the session ID with the responded
server for each request. Client output for the first 10 requests are shown
below. </p>
@@ -1300,10 +1300,9 @@ Content-ID:
<p>
<strong>Objective: Demonstrate the session affinity based load balancing with
failover capability</strong> </p>
<p>
-<strong>Prerequisites:</strong> </p>
-<p>Start Synapse with sample configuration 55 (i.e. synapse -sample 55). </p>
-<p>Deploy the LoadbalanceFailoverService and start four sample Axis2 servers
on HTTP ports 9001, 9002, 9003 and 9004 respectively (make sure to specify
non-conflicting HTTPS ports). </p>
-<p></p>
+<strong>Prerequisites:</strong>
+<br/>Start Synapse with sample configuration 55 (i.e. synapse -sample 55).
+<br/>Deploy the LoadbalanceFailoverService and start four sample Axis2 servers
on HTTP ports 9001, 9002, 9003 and 9004 respectively (make sure to specify
non-conflicting HTTPS ports). </p>
<p>This configuration also uses "simpleClientSession" to bind
sessions as in the previous sample. But failover endpoints are specified as the
child endpoints of the load balance endpoint. Therefore sessions are bound to
the failover endpoints. Session information has to be replicated among the
servers listed under each failover endpoint using some clustering mechanism.
Therefore, if one endpoint bound to a session failed, successive requets for
that session will be directed to the next endpoint in that failover group. Run
the client using the following command to observe this behaviour. </p>
<pre xml:space="preserve">ant loadbalancefailover -Dmode=session</pre>
<p>You can see a client output as shown below. </p>
@@ -1358,9 +1357,10 @@ Content-ID:
<p>
<strong>Objective: Demonstrate the use of WSDL endpoints</strong> </p>
<p>
-<strong>Prerequisites:</strong> </p>
-<p>Start the Synapse configuration numbered 56 (i.e. synapse -sample 56). </p>
-<p>Deploy the SimpleStockQuoteService and start the sample Axis2 server. </p>
+<strong>Prerequisites:</strong>
+<br/>Start the Synapse configuration numbered 56 (i.e. synapse -sample 56).
+<br/>Deploy the SimpleStockQuoteService and start the sample Axis2 server. </p>
+
<p>This sample uses a WSDL endpoint inside the send mediator. WSDL endpoints
can extract endpoint's address from the given WSDL. As WSDL documents can have
many services and many ports inside each service, the service and port of the
required endpoint has to be specified. As with address endpoints, QoS
parameters for the endpoint can be specified in-line in the configuration. An
excerpt taken from the sample_proxy_1.wsdl containing the specified service and
port is listed below. </p>
<pre xml:space="preserve"><