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"...eve
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 re
