Using JProfiler with IBM RAD 6.x

## Using JProfiler with IBM RAD 6.x |

| Since IBM RAD 6.x is based on eclipse 3.0, the RAD plugin works just like the plugin for eclipse 3. However there are a few important points to notice about the integration process as well as the usage of the plugin.

| The installation of the IBM RAD plugin is started by selecting IBM RAD 6.x on the IDE integration tab of JProfiler's setup wizard miscellaneous options tab of JProfiler's general settings (use Session->IDE integrations in JProfiler's main menu as a shortcut). and clicking on [Integrate] Reminder: Please close IBM RAD while performing the plugin installation. If you are performing the installation from JProfiler's setup wizard, please complete the entire setup first before starting IBM RAD. A file selector will then prompt you to locate the installation directory of IBM RAD. The installation directory must contain an `eclipse` directory. eclipse provides shared infrastructure for profiling plugins that allows only one active profiler at a time. If another profiler has registered itself in eclipse, JProfiler will show a collision message dialog at startup. While eclipse does not ship with any profilers, IBM RAD 6.x has an integrated profiler. The way in which eclipse selects the profiler that's bound to the "Profile" buttons is undefined. As it happens, the JProfiler plugin is selected before the integrated profiler. To get rid of the collision message that is shown at startup, please perform the following steps: Locate `eclipse/plugins/org.eclipse.hyades.trace.ui_n.n.n/plugin.xml` where n.n.n is a version number like 3.0.1 Replace all instances of "profile" with "tptp" in the above file. Please note that the quotes are part of the search and replace expressions. If you remove JProfiler, you can revert this change by replacing "tptp" with "profile". Delete the directory `eclipse/configuration/org.eclipse.osgi`. The plugin cache will be rebuilt on the next startup of RAD. This is necessary since otherwise RAD does not notice the above change.

| Only launch configuration types that exist in eclipse 3.0 can be profiled by the JProfiler plugin. Specifically, the Websphere and Apache Tomcat launch configuration types cannot be profiled with the JProfiler plugin. For these servers, please use the corresponding server integration wizard. The Websphere integration wizard asks you to locate the `server.xml` file that contains the configuration for your Websphere server, Finding this file can be a little difficult. If you start your search at `{RAD install directory}/runtimes/base_v6/profiles/default/config/cells/` you can locate the config file in `$CELL/nodes/$NODE/servers/$SERVER` where $CELL, $NODE and $SERVER depend on your system and the target server. In addition, the integration wizard asks to locate a startup script named `startServer.bat`. That script can be found in `{RAD install directory}/runtimes/base_v6/bin/`.