This documentation is for WSO2 ESB version 4.9.0. You can view this page (if available) in the latest documentation or go to the latest version's home page.

Skip to end of metadata
Go to start of metadata

This section explains how TCPMon can be used to monitor the ESB. Following topics are covered.

Introduction to TCPMon

Users can view and monitor the messages passed along a TCP-based conversation using the TCPMon utility. Therefore, this is a convenient tool, particularly useful for debugging when you develop Web services. TCPMon is an Apache project distributed under Apache 2.0 License.TCPMon is not dependent on any third party libraries. Its user interface is based on a swing UI and works on almost all platforms that support Java.

TCPMon is most commonly used to monitor the communication between the client (front end) and the back end server. 

The following diagram depicts a typical communication between the front end client and the back end server. 80 is the listening port of the back end server which receives the messages from the client.



TCPMon can be used as an intermediary between the client and the server in order as shown below in order to monitor the messages. 8081 is the listening port in TCPMon which receives the messages from the client instead of the back end server.

Starting TCPMon

TCPMon is available in the <ESB_HOME>/bin directory of any WSO2 Carbon based product distribution. Alternatively, you can download TCPMon from Apache and run the tool.

Running TCPMon (from Carbon product pack)

Ensure that the following prerequisites are fulfilled in order to run TCPMon.

  • Install JDK 1.4 or later version.
  • Set the JAVA_HOME variable. This setting is required only if you are using the TCPMon available in the WSO2 Carbon based product pack.

    For information on how to set the JAVA_HOME variable, go to Installing the Product, select the instructions relevant to your operating system and refer the 'Setting JAVA_HOME' section.

To run the TCPMon available with your WSO2 Carbon product pack:

  1. Go to <PRODUCT_HOME>/bin directory of your product pack.
  2. Execute the following command to run the tool.

    For Windows

    For Linux

Running TCPMon (downloaded from Apache)

To download TCPMon from Apache and run the tool: 

  1. Download TCPMon from the following location: http://archive.apache.org/dist/ws/tcpmon/1.0/tcpmon-1.0-bin.zip.
  2. Extract tcpmon-1.0-bin.zip archive.
  3. Go to the build of the extracted directory to find the execution script.
  4. Execute the following command to run the tool.

    For Windows

    For Linux

Monitoring ESB with TCPMon

The following diagram illustrates the typical message flow when a proxy service is involved in a communication between a client and a server.

In this scenario the proxy service is listening from port 8280 and the backend server is listening from port 9000.

There are two connections in this scenario:

  • Client to proxy service connection.
  • Proxy to backend server connection.
     
Monitoring client to proxy service connection

In this scenario, the message flow between the client and the proxy service is monitored as illustrated in the following diagram.

To monitor the client to proxy service connection:

  1. Start TCPMon and enter the listener properties. Enter 8281 as the listener port, 8280 as the target port, and then click Add.
  2. Run sample 150 as follows. See Setting Up the ESB Samples for detailed instructions on how to run a sample.
    1. Execute one of the following commands to start the ESB with the configuration for sample 150.
      • On Windows: wso2esb-samples.bat -sn 150
      • On Linux/Solaris: ./wso2esb-samples.sh -sn 150
    2. Execute one of the following commands to start the the Axis2 server.
      • On Windows: axis2server.bat
      • On Linux/Solaris: ./ axis2server.sh
    3. Run ant from the <ESB_HOME>/samples/axis2Server/src/SimpleStockQuoteService directory.
    4. Run the following ant command from the <ESB_HOME>/samples/axis2Client directory.

      By specifying the URL as shown above, you will be sending the request to port 8281 (which is set as the listening port) instead of sending it directly to port 8280.

  3. The request and the response would be displayed in TCPMon as follows.
     
Monitoring proxy service to backend connection

In this scenario, the message flow between the proxy service and backend is monitored as illustrated in the following diagram.

To monitor proxy service to backend connection:

  1. Start the ESB management console.
  2. Click List under Services in the left navigator to view the deployed services. Then click on the Source View link of the StockQuoteProxy service.
  3. Configure the proxy service to send the request to port 9001 instead of sending it directly to port 9000. This can be done as follows.

  4. Start TCPMon and enter 9001 as the listener port and 9000 as the target port. Click Add
  5. Run sample 150 as follows.
    1. Execute one of the following commands to start the ESB with the configuration for sample 150.
      • On Windows: wso2esb-samples.bat -sn 150
      • On Linux/Solaris: ./wso2esb-samples.sh -sn 150
    2. Execute one of the following commands to start the the Axis2 server.
      • On Windows: axis2server.bat
      • On Linux/Solaris: ./ axis2server.sh
    3. Run ant from the <ESB_HOME>/samples/axis2Server/src/SimpleStockQuoteService directory.
    4. Run the following ant command from the <ESB_HOME>/samples/axis2Client directory.

  6. You will be able to see the request and the response as shown below.

Limitations

  • TCPMon cannot be used to view messages transferred via the https protocol. However, you can view messages transferred via the https protocol in WSO2 ESB using the wire logs functionality.
  • No labels