Re: Help needed for TCPMonitor

[Jeff]

Hi Dipty,   TCPmonitor sits in between a web service client and the web service to which the client is intended to connect.   Typically, TCPmonitor is configured (i) to listen on a previously unused port and (ii) to forward client requests to the web service and web service responses back to the client. It doesn't matter on which machine(s) each of the three components is installed, provided that settings correctly reflect the configuration.   One simple scenario would leave the web service untouched, would have TCPmonitor calling into the web service as though it were the client while listening for connections from the real client and would have the client reconfigured to call into TCPmonitor.   Suppose that a web service is installed at 10.0.0.1:8080. Ordinarily, the client would be configured to call into 10.0.0.1:8080. To setup TCPmonitor on machine 10.0.0.2, choose an unused port to listen on, suppose its 9999, then configure TCPmonitor to connect to 10.0.0.1:8080 and configure the client to connect to 10.0.0.2:9999.     Jeff         ----- Original Message ----- From: Dipty Maybhate To: axis-user@ws.apache.org Sent: Tuesday, June 28, 2005 11:45 AM Subject: Help needed for TCPMonitor Hi Everyone,   I am trying to view the SOAP request and response using TCPmonitor. I invoke it using the command line option and give the host address and port mentioned in the WSDL <soap:address location> field which is enclosed in the <port> tag. When I inovoke this utility it just shows waiting for connection and nothing happens. Could anyone please help me? Are there some other settings or am I giving the wrong parameters? Is there some other way in which I can view the request and the response?   Thanks a lot! Dipty   Dipty Maybhate Austin, TX 78759