Ignore:
Timestamp:
2006-11-16T13:32:14+13:00 (17 years ago)
Author:
daven
Message:

notes on SOAP debugging using TCPMonitor

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/gsdl3/docs/manual/manual.tex

    r13281 r13284  
    23432343The listen port is the port that you want the monitor to be listening on. It should 'act as' a Listener, with target hostname 127.0.0.1 (localhost), and target port the port that Tomcat is running on (8080). You need to modify the address used to talk to the SOAP service. For example, if you want to monitor traffic between the gateway site and the localsite SOAP server, you will need to edit gateway's siteConfig.xml file and change the port number (in the site element) to whatever you have chosen as the listen port.
    23442344
     2345For example, in the Admin panel of TCPMonitor the Target Hostname might be 127.0.0.1, and the Target Port # 8080. Set the Listen Port # to be a different port, such as 8070 and click Add. This produces a new tab panel where you can see the messages arriving at port 8070 before being forwarded to port 8080. You then need to set your test request from your SOAP application to arrive at port 8070 and you will see copies of the messages in the new tab panel.
     2346
     2347
    23452348\newpage
    23462349\section{Tidying up the formatting for imported Greenstone 2 collections}\label{app:gs2tidy}
Note: See TracChangeset for help on using the changeset viewer.