you can monitor on client as well...
Configure your monitor so that local port is "X"[this is any free local port on ur local system] and destination port is "Y"[this is the port on which ur webservice is running...Ex:8080]..
Now making use of ur client,send requests to port "X" and NOT "Y"...everything should work fine..
Rgds
Prashanth
On 2/16/06, Pantvaidya, Vishwajit <[EMAIL PROTECTED]> wrote:
I am sending requests to a remote webservice - can I use SOAPMonitor to sniff and pick up those http requests? My understanding is that SOAPMonitor has to be deployed on the web service side to monitor the soap traffic to/from that service - since in this case I do not have access to the remote webservice host, I presume I will not be able to use the SOAPmonitor here.I tried tcpmon - it is able to intercept my resuest messages - I am not able to get the response back from the service. Not sure what is going wrong.
