Can I use newer Rational Agent Controller with older Rational Application Developer releases?
It is sometimes useful to use newer Rational Agent Controller, containing latest bug fixes, with older Rational Application Developer.
The release of Rational Agent Controller containing the same code level as a particular release of Rational Application Developer is listed here:
However, in order to get the latest bug fixes, it is sometimes useful to use a newer version of Rational Agent Controller than the version of Agent Controller that is in a particular version of RAD. For remote profiling, users can just download a newer Rational Agent Controller release and start it on the remote machine. For local profiling, users need to disable the Integrated Agent Controller first before using a standalone Rational Agent Controller.
To disable the Integrated Agent Controller, go to Window > preferences > Agent Controller > Integrated Agent Controller and select the Disable radio button. After the Integrated Agent Controller is disabled (the ACServer process should be terminated), download the Rational Agent Controller release and start the standalone Rational Agent Controller on the local machine.
Refer to the getting_started.html file under the [ Rational Agent Controller install directory]\AgentController directory for instruction on how to start, stop and use the agent controller.
Note that Rational Agent Controller v8.3.4 is the latest release you can use when profiling with Java 1.4. For profiling with Java 1.5 and up, you can use up to the latest available release of Rational Agent Controller (which currently is Rational Agent Controller v8.3.6).
Rational Application Developer v8.x and newer releases
You should be able to use newer Rational Agent Controller releases with Rational Application Developer v8 and newer releases without any extra setup required.
Rational Application Developer v7.x and older releases
When using Rational Application Developer v7.x releases to profile on newer Rational Agent Controller releases, you will need to ensure that the profiling environment variables are properly set up before launching Rational Application Developer.
1. Open a new command window and set these environment variables:
2. Set the following environment variables:
set TPTP_AC_HOME=[ Rational Agent Controller install directory]\AgentController
3. Launch Rational Application Developer thru command line:
[Rational Application Developer install directory]\eclipse.exe" -product com.ibm.rational.rad.product.v75.ide
Rational Application Developer v6.x
When using Rational Application Developer v6.x with the latest Rational Agent Controller release (up to Rational Agent Controller v8.3.4), in addition to setting up the environment variable as described in the "Rational Application Developer v7.x and older releases" section (required for profiling on server), if you encounter the following problem, you will need to update the JRE used in Rational Agent Controller as well.
When profiling an application, you may encounter the following error if the Rational Agent Controller's JRE is not compatible with Rational Application Developer's JRE:
"JVMJ9VM011W Unable to load j9jpi24: The specified module could not be found.
Could not resolve to JVMPI interface
JVMJ9VM011W Unable to load j9jpi24: The specified module could not be found.
JVMJ9VM015W Initialization error for library piAgent(-3): JVM_OnLoad failed
Could not create the Java virtual machine."
In this case, run SetConfig.bat under [ Rational Agent Controller install directory]\AgentController\bin directory to set Rational Agent Controller to use the JDK shipped in Rational Application Developer. For example, when prompted to specify the fully qualified path of "javaw.exe", enter [Rational Application Developer v6 install directory]/\jdk\jre\bin\java.exe. Then just hit Enter to accept the defaults for the other prompts in SetConfig.
When you run SetConfig.bat, if you get "...cannot find java in the PATH..." error or "ERROR: The Java Runtime in use does not contain a suitable JAXP feature". This means that the PATH variable is not set properly. In that case, reset "PATH" from command line by running:
set PATH=[Rational Application Developer v6 install directory]\jdk\jre\bin;%PATH%
Finally, launch Rational Application Developer thru command line:
[Rational Application Developer install directory]\eclipse.exe"