Monday, March 15, 2010

Monitoring SOAP requests

The easiest way is to use TCP-Monitor (either the Eclipse plugin or the standalone application );

this entails pointing your test suite to a different port, and with WLI test client (Web) this doesn't work because they hardcode the portnumber in the HTTP Response (smart!).

Perhaps using this trick of pointing the JVM to use the TCP mon as a proxy (-Dhttp.proxyHost=localhost -Dhttp.proxyPort=8080) you can make it work...

I have tried this PortPeeker port traffic monitoring tool:
but it cannot examine an already opened port.... pretty useless for a sniffer tool...

Let's try then Wireshark
or tcpdump / windump
(both Wireshark and WinDumo use WinpCap libraries to capture traffic)

No comments: