StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>The accepted answer to <a href="https://stackoverflow.com/questions/486864/how-to-intercept-xml-response-and-request-during-web-service-invocation">this question</a> mentions that you can capture traffic to a web service using soapUI. You can use it to act as a proxy or HTTP tunnel in order to capture messages sent to your web service. I think using it in HTTP Tunnel mode makes sense, because then you won't have to do anything with your client other than to point the URL to soapUI instead of your actual service.</p> <p><a href="http://www.soapui.org/SOAP-Recording/recording-soap-trafic.html" rel="nofollow noreferrer">The soapUI website talks about the SOAP Monitor feature,</a> though I don't think it offers a good explanation for setting up the HTTP tunnel.</p> <p>Here are the steps involved (based on soapUI 3.0.1):</p> <ol> <li>Open Soap UI</li> <li>create a New soapUI Project... 2.1 Give your project a name 2.2 Enter the path to your service's WSDL (<a href="http://localhost/.../YourService.asmx?WSDL" rel="nofollow noreferrer">http://localhost/.../YourService.asmx?WSDL</a>)</li> <li>Right-click on the project you just created</li> <li>Select "Launch SOAP Monitor"</li> <li>Choose "HTTP Tunnel"</li> <li>Specify an unused port number for "Port". The default will probably work.</li> <li>Enter the URL to your web service in "Set endpoint for HTTP Tunnel"</li> <li>If you are using SSL, then you may need to fill in some of the other fields; otherwise, click OK</li> <li>The HTTP tunnel is running, so now just reconfigure a client to use the HTTP tunnel instead of the actual web service. So if your actual service is "<a href="http://localhost:1234/YourService.asmx" rel="nofollow noreferrer">http://localhost:1234/YourService.asmx</a>", then reconfigure your client to use "<a href="http://localhost" rel="nofollow noreferrer">http://localhost</a>:{Port}/YourService.asmx" where {Port} is the number you entered in step #6.</li> <li>Now just run your client normally. You'll see the traffic logged in the soapUI interface. Select a message and click on the "Message Content" button at the bottom of the window to view the actual SOAP message.</li> </ol>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload