Subsystems are identified to the performance test engine with extensions. Typically, a new protocol indicates in its plugin.xml file the class name of the subsystem that it is providing. This example modifies an existing performance test plug-in and specifies the class name of the sample plug-in in the plugin.xml file.
Inform the test engine that the subsystem exists
To identify the subsystem to the performance testing engine, complete the following steps.
- Open a command prompt, and change directory to the RPT plug-ins directory.
- Save a copy of the existing HTTP execution JAR.
For example:
C:\IBM\common\plugins>copy com.ibm.rational.test.lt.execution.http_7.0.0.v200609010404.jar com.ibm.rational.test.lt.execution.http_7.0.0.v200609010404.jar.orig
- Make a new copy of the HTTP execution JAR for modification. For example:
C:\IBM\common\plugins>copy com.ibm.rational.test.lt.execution.http_7.0.0.v200609010404.jar foo.jar
- Extract the plugin.xml file.
For example:
C:\IBM\common\plugins>jar xvf foo.jar plugin.xml
You must have a Java SDK in PATH statement so that you have access to the JAR utility.
- Add these lines to the plugin.xml file just above the </plugin> line at the bottom:
<extension point="com.ibm.rational.test.lt.execution.Subsystem"> <Subsystem feature="com.ibm.rational.test.lt.feature.lt" class="test.SampleSubsystem"/> </extension>- Start Rational Performance Tester with the -clean option so that the plug-ins are reloaded, for example:
C:\IBM\RPT>eclipse –clean