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

Fri Dec 1 06:24:44 PST 2006

Author: chatra
Date: Fri Dec  1 06:24:44 2006
New Revision: 63

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

Modified: wsas/java/trunk/xdocs/tools/tcpmonguide.html
==============================================================================

--- wsas/java/trunk/xdocs/tools/tcpmonguide.html	(original)
+++ wsas/java/trunk/xdocs/tools/tcpmonguide.html	Fri Dec  1 06:24:44 2006
@@ -1,16 +1,15 @@
-<?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" />
-  <title>WSO2 Web Services Application Server Standalone Edition for Java
+  <title>WSO2 Web Services Application Server Standalone Edition for Java
   @wso2wsas_version@ - TCPMon Guide</title>
 </head>
 
 <body>
-<h1>WSO2 Web Services Application Server Standalone Edition for Java
-  @wso2wsas_version@ - TCPMon Guide</h1>
+<h1>WSO2 Web Services Application Server Standalone Edition for Java,
+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
@@ -42,13 +41,14 @@
 <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>
-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>
+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>
+
 <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>
+<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>
 
 <h2>Usage Patterns</h2>
@@ -58,15 +58,15 @@
 
 <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 original endpoint
-in order to monitor the messages. The following figure explains this
-concept.</p>
+the client has to send the messages to the intermediary rather than 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 & port as well as the listening port in the admin screen. See the image
-below.</p>
+target host name &amp; port as well as the listening port in the admin
+screen. See the image below.</p>
 
 <p><img alt="Figure 2: first screen" src="../images/screen1.jpg" /></p>
 
@@ -85,12 +85,14 @@
 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><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><img alt="Figure 5: browser address bar" src="../images/screen2-browser.jpg" /></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>


