After you have successfully enabled soapUI deep diagnostics (see Section 1.3.3.8, “soapUI”), you are now ready to run. RTI provides deep diagnostics when you run your soapUI tests as usual, from prepared scripts or interactively.
In this example we have a soapUI script running in the soapUI GUI on a remote server, v-ngi3, exercising a CMS application, Alfresco, in Tomcat on the same remote server: Both soapUI and Tomcat have been enabled for RTI data collection.
We start the RTI console and verify that we are connected to the host or hosts where the test is running. In this case we can see that RTI is collecting data in both the soapui and tomcat_tomcat collectors:
After exercising our application we can transfer the RTI data from the remote host to the RTI console to analyze our application performance. To do this we select the Transfer Deep-Dive Performance Data link on the welcome page:
This displays the Get Data From Collectors dialog where we will specify which data to get:
In this case we have selected to transfer data from both the soapui collector on v-ngi3 which started the transactions, and the tomcat_tomcat collector on v-ngi3 where they were processed. We keep the default name for the name of the local data set to hold the data, choose to get the last 10 minutes of data, and choose to see all traced methods. Once the data is downloaded to the RTI console it is correlated and an overview of the data is displayed:
The columns and sort orders shown are the default when starting on a new machine. The chart on the lower right shows that all the transactions collected initiated with soapUI (in blue) and were fairly consistent over time. The soapUI events are sorted by Create Time, so the first thing one can do to highlight long-running transactions is to sort by descending Elapsed Time:
Now we see these soapUI events indicate that they can be expanded to show multiple events that comprise these transactions. We can see that all the request times are pretty quick -- let's see what's going on.  Just double-click on a line to "Focus On" the transaction, which replaces this view with the fully expanded decomposition of the transaction. In this case there are not many underneath because all the transactions are failing!


loading table of contents...