1.3.3.7. Custom Java

Enterprise testing is often driven by a custom Java script, especially when testing individual components or non-HTTP protocols like SOAP. In this case you may still want to trace the transactions as they are initiated, and perhaps log custom test-driver-specific data. This is very easy to do. From an RTI-enabled command line you can just change "java" to "rti java --". (the "--" separates rti options from java options). This will automatically create a collector based on the main class name. From the RTI Console, you can create a collector of type "java" as described in Section 1.3.3.4.2, “Enabling RTI Performance Collectors” and specify the collector name when you run, for example:

rti java -c TestMain -- -cp /work/tests/tests.jar com.ocsystems.rti.TestMain

The collector created starts by logging methods from the main class as well as methods associated with common protocols. Other RTI-instrumented applications that receive requests from your RTI-instrumented Java test driver will show its main class as the initiator.

As always, you will know your application is instrumented from the RTI-specific messages written to stderr on startup. Once you have success with this, you can add custom instrumentation to your Java driver using the Edit Configuration operation on the collector, as described in Section 4.2, “Configuring a Collector”.