RTI supports monitoring JMeter scripts, allowing HTTP transactions to be
traced from JMeter into the backend application to understand and diagnose
any poor performing code or SQL queries that may be degrading the high-level
JMeter transactions.
Enabling RTI for JMeter is very similar to enabling RTI for JBoss or
Tomcat. Follow the same steps as described in Section 1.3.3.1, “Tomcat and JBoss”, choosing either the
command-line or RTI Console graphical wizard, but specify the root of your
JMeter installation as opposed to JBoss or Tomcat.
The next time you start JMeter, RTI will monitor and log all HTTP requests
initiated from JMeter.
You will know that JMeter is instrumented because RTI adds its output to
Java's standard error output on startup, for example:
C:\Users\perftest\RTI>jmeter Guessed Java is 32-bit RTI License expires in 25 days. (I) Installing sensorpoint module "C:\PROGRA~2\OCSYST~1\RTI\ENTERP~1/probes/JMeterArmBaseBean.usm"... (I) Installed sensorpoint module "JMeterArmBaseBean.usm(1267454625)". ...
You're now ready to run. Refer to Section 2.5.1, “Deep-Dive Tracing from JMeter” for a walk-through of running
JMeter with RTI and analyzing the results.
 |  |  |
| 1.3.3.4. Enabling RTI Using the Console Wizard |  | 1.3.3.6. LoadRunner |
