[wsas-java-dev] svn commit r558 - wsas/java/trunk/xdocs/tools

svn at wso2.com svn at wso2.com
Mon Jan 22 20:31:10 PST 2007 

Author: marietta
Date: Mon Jan 22 20:31:05 2007
New Revision: 558

Modified:
   wsas/java/trunk/xdocs/tools/tcpmonguide.html
Log:
Reviewed.

Modified: wsas/java/trunk/xdocs/tools/tcpmonguide.html
==============================================================================
--- wsas/java/trunk/xdocs/tools/tcpmonguide.html	(original)
+++ wsas/java/trunk/xdocs/tools/tcpmonguide.html	Mon Jan 22 20:31:05 2007
@@ -1,12 +1,13 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
 <!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" />
-  <link href="cmd/css/wsas-dist-doc.css" rel="stylesheet" type="text/css"
-  media="all" />
   <title>WSO2 Web Services Application Server Standalone Edition for Java
   @wso2wsas_version@ - TCPMon Guide</title>
+  <link href="cmd/css/wsas-dist-doc.css" rel="stylesheet" type="text/css"
+  media="all" />
 </head>
 
 <body>
@@ -14,8 +15,8 @@
 v at wso2wsas_version@ - TCPMon Guide</h1>
 
 <p>The aim of this simple tutorial is to explain how the TCPMon works. It
-will explain how messages are exchanged and some other important features
-such as Slow Connection Simulation and HTTP Proxy Support.</p>
+explains how messages are exchanged and other important features such as Slow
+Connection Simulation and HTTP Proxy Support.</p>
 
 <h2>Content</h2>
 <ul>
@@ -36,44 +37,43 @@
   </li>
   <li><a href="#conclusion">Conclusion</a></li>
 </ul>
-<a name="intro" id="intro"></a>
+<a id="intro"></a>
 
 <h2>Introduction</h2>
 
 <p>TCPMon is a utility that allows the user to monitor the messages passed
 along in a TCP based conversation. It is based on a swing UI and works on
-almost all platforms that Java supports.</p>
+almost all the platforms that Java supports.</p>
 The script file, tcpmon.{sh|bat} to run this tool is located in the "bin"
-folder of the WSO2 WSAS standalone edition. <a name="dependencies"
-id="dependencies"></a>
+folder of the WSO2 WSAS standalone edition. <a id="dependencies"></a>
 
 <h2>Structure and Dependencies</h2>
 
 <p>TCPMon has absolutely no dependencies on third party libraries. TCPMon
 needs a JRE that is 1.4 or higher.</p>
-<a name="patterns" id="patterns"></a>
+<a id="patterns"></a>
 
 <h2>Usage Patterns</h2>
-<a name="intermediate" id="intermediate"></a>
+<a id="intermediate"></a>
 
 <h3>As an Explicit Intermediate</h3>
 
 <p>The most common usage pattern for the TCPMon is as an
 <strong>intermediary</strong>. It is called <strong>explicit</strong> since
-the client has to send the messages to the intermediary rather than the
+the client has to send the messages to the intermediary rather than to the
 original endpoint in order to monitor the messages. The following figure
 explains this concept.</p>
 
 <p><img alt="Figure 1: concept" src="../images/concept.jpg" /></p>
 
-<p>In order to start the TCPMon in this configuration one has to provide the
-target host name &amp; port as well as the listening port in the admin
-screen. See the image below.</p>
+<p>In order to start the TCPMon in this configuration, you have to provide
+the target host name and port as well as the listening port on the Admin tab.
+See the image below.</p>
 
 <p><img alt="Figure 2: first screen" src="../images/screen1.jpg" /></p>
 
-<p>Pressing the 'add' button opens up a new tab that allows the messages to
-be seen as in the following screen.</p>
+<p>Click 'Add' to open a new tab that displays the messages to be seen, as
+displayed in the following screen.</p>
 
 <p><img alt="Figure 3: message screen" src="../images/screen2.jpg" /></p>
 
@@ -81,32 +81,33 @@
 TCPMon instead of the original endpoint. Let us understand this with an
 example:</p>
 
-<p>Say all messages passed between www.apache.org needs to be monitored.</p>
+<p>For example, we need to monitor all the messages that are sent to and from
+www.apache.org.</p>
 
-<p><strong>Step 1</strong> - Add a listener with host as www.apache.org and
-port as 80. Set the listener to port 8080 which may be any unused port in the
-local machine</p>
+<p><strong>Step 1</strong> - Add a listener with the host as www.apache.org
+and port as 80. Set the listener to port 8080, which may be any unused port
+in the local machine.</p>
 
 <p><img alt="Figure 4: the settings" src="../images/screen2-closeup2.jpg"
 /></p>
 
-<p><strong>Step 2</strong> - Point the browser to localhost:8080 instead of
-www.apache.org.</p>
+<p><strong>Step 2</strong> - Point the browser to the localhost:8080 instead
+of www.apache.org.</p>
 
 <p><img alt="Figure 5: browser address bar"
 src="../images/screen2-browser.jpg" /></p>
 
-<p>Once the messages start flowing they can be seen in the relevant tab as
-seen below.</p>
+<p>Once the exchange of messages start, they can be seen on the relevant tab
+as seen below.</p>
 
 <p><img alt="Figure 6: Filles screen" src="../images/screen3.jpg" /></p>
 
-<p>The bottom controls allow the messages to be XML formatted (useful in
-debugging Web services), save and resend the messages, and also to switch the
-layout of the message windows.</p>
+<p>The options at the bottom of the screen can be used to have the messages
+in XML format (useful in debugging Web services), save and resend the
+messages, and also to switch the layout of the message windows.</p>
 
 <p><img alt="Figure 7: button set" src="../images/screen2-closeup1.jpg" /></p>
-<a name="sender" id="sender"></a>
+<a id="sender"></a>
 
 <h3>As a Request Sender for Web Services</h3>
 
@@ -115,19 +116,19 @@
 server.</p>
 
 <p><img alt="Figure 8: request sender" src="../images/screen4.jpg" /></p>
-<a name="proxy" id="proxy"></a>
+<a id="proxy"></a>
 
 <h3>As a Proxy</h3>
 
 <p>TCPMon can act as a proxy. To start the TCPMon in proxy mode, just select
-the proxy option from the radio buttons. When acting as a proxy, TCPMon only
-needs the listener port to be configured.</p>
+the Proxy option. When acting as a proxy, TCPMon only needs the listener port
+to be configured.</p>
 
 <p><img alt="Figure 9: proxy" src="../images/screen5.jpg" /></p>
-<a name="advanced" id="advanced"></a>
+<a id="advanced"></a>
 
 <h2>Advanced Settings</h2>
-<a name="slow" id="slow"></a>
+<a id="slow"></a>
 
 <h3>Slow Connection Simulation</h3>
 
@@ -136,13 +137,13 @@
 Web services.</p>
 
 <p><img alt="Figure 10: slow-connection" src="../images/screen6.jpg" /></p>
-<a name="http_proxy" id="http_proxy"></a>
+<a id="http_proxy"></a>
 
 <h3>HTTP Proxy support</h3>
 
-<p>If HTTP proxy support is required then that can also be set on the admin
+<p>If HTTP proxy support is required, then that can also be set on the admin
 screen.</p>
-<a name="conclusion" id="conclusion"></a>
+<a id="conclusion"></a>
 
 <h2>Conclusion</h2>

More information about the Wsas-java-dev mailing list