15 January 2008 - 2.0.1 home user-guide eclipse intellij netbeans maven PDF files forums bugs sourceforge eviware.com






SOAP Monitor

soapUI 2.0 adds powerful SOAP Monitoring possibilities (ie tcpmon), allowing you to capture and analyze ongoing SOAP-traffic between an existing client and server. The captured traffic can be used to generate both TestCases and MockServices, and soapUI Pro adds (extremely cool) Coverage possibilities allowing you to monitor the actual utilization of the monitored WSDL contract(s).

Start the SOAP Monitor from the Project popup menu with the "Launch SOAP Monitor" action:

Specify which port the monitor should listen on and which mode it should run in:

  • Proxy : starts the monitor as an HTTP Proxy. When selecting this option, configure the monitors' host:port as the proxy for the client you want to monitor.
  • Tunnel : starts the monitor as a TCP-Tunnel, point your client directly at the host:port of the monitor (with the rest of the URL intact. The "Add endpoint" option will add the created tunnels endpoint to all interfaces in the project, for easy redirection of requests within soapUI.

The Incomging Request/Response WSS settings are used to select the Incoming WSS configurations to use for decrypting/validating monitored messages, which can be useful for viewing encrypted content and validating security

Main Window

The SOAP Monitor is displayed with the following window components (top to bottom):

  • The main toolbar with options for starting/stopping/re-configuring the SOAP Monitor
  • The available monitor tabs ("Traffig Log" and "Coverage" in soapUI Pro)
  • A traffic-log toolbar with actions to create requests, testcases, mockservices and clear the log
  • A filter bar for filtering out which requests to show in the traffic log
  • The traffic-log itself containing rows for captured messages
  • A "Message Content" inspector that displays the actual content of the message selected in the table. All standard request/response editor views and inspectors are available

Once started, the monitor will display captured messages as rows in the log table with their relevant data. Requests that belong to Interfaces/Operations available in the containing project will automatically be mapped to these and use underlying schema-information in the message inspectors in the Message Content views:

By default, the log will keep the 100 most recent messages, this can be adjusted in the SOAP Monitor options dialog available from the top toolbar.

Using Captured Messages

The 3 left-most buttons in the traffic-tables toolbar allow for creation of new items from captures messages:

  • Create Requests : creates requests under their corresponding operations for each selected request in the traffic log
  • Create TestCase : prompts to create a TestCase (or add to an existing one), by creating TestRequests corresponding to the currently selected requests in the traffic log
  • Create MockService : prompts to create a MockService (or add to an existing one), by creating MockOperations/MockResponses corresponding to the currently selected requests in the traffic log

The combination of the last 2 can be used to record and simulate an entire converation between a client and server for replaying, testing, etc..


Next: