Enabling RTI for soapUI is very similar to enabling RTI for JBoss, Tomcat or Fuse. Follow the same steps as described in Section 1.3.3.1, “JBoss and Tomcat”, choosing either the command-line or RTI Console graphical wizard, but specify the root of your soapUI installation as opposed to JBoss, Tomcat or Fuse. The scripts soapui.sh, testrunnner.sh, loadtestrunner.sh and mockservicerunner.sh (where .sh is replaced by .bat on Windows) are all updated when the soapUI is created and enabled through the RTI console or enabled on the command line using the rti edit command (in which case you may choose to edit/enable each script individually, or leave it as-is).
The next time you run one of the enabled scripts, RTI will monitor and log all HTTP requests initiated from soapUI.
You will know that soapUI is instrumented because RTI adds its output to Java's standard error output on startup, for example:
# sh /opt/soapui-4.5.1/bin/soapui.sh
================================
=
= SOAPUI_HOME = /opt/soapui-4.5.1
=
================================
RTI Enterprise Version 3.4 (2012-12-12:03:17:23)
Updated /home/test/.ocs-rti-info
RTI_HOME=/opt/ocsystems/rti/ee64
RTI_DATA=/var/opt/ocsystems/rti/ee64
JAVA_HOME=/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64

RTI License expires in 29 days.
(I) RtiAgentInitializer: /opt/ocsystems/rti/ee64
(I) RtiAgentInitializer: logDir = /var/opt/ocsystems/rti/ee64/...
(I) RtiAgentInitializer: cfgFile = /tmp/spj-7055/startup/soapu...
(I) RtiAgentInitializer: collector.id = soapui-4.5.1
(I) RtiAgentInitializer: cfgDir = /var/opt/ocsystems/rti/ee64/...
(I) Installing sensorpoint module "/opt/ocsystems/rti/ee64/pro...
(I) Installed sensorpoint module "SoapuiArmBaseBean.usm(1126216897)".
(I) Enabling sensorpoint module 1126216897...
...
You're now ready to run.


loading table of contents...