JProfiler as an eclipse 2.x / WSAD 5.x plugin

When JProfiler is integrated into the eclipse 2.x IDE or into WSAD 5.x (which is based on eclipse 2.1), JProfiler can be invoked from within the IDE without any further need for session configuration.
Requirements: The eclipse 2.x plugin works with eclipse 2.0, eclipse 2.1 and WSAD 5.x. In the following text, the IDE will always be called "eclipse". For eclipse 3, a different plugin with more capabilities is available.

Profiling a J2EE application from WSAD:
With the IDE integration for WSAD, only run configurations of type "Java application" can be profiled. To profile a J2EE application from within WSAD, please choose Session->Integration wizards->New server integration from JProfiler's main menu and select the server integration type IBM Websphere started from WSAD. The integration wizard will lead you step by step through the required modifications to profile your server.

The installation of the eclipse plugin is started by selecting "eclipse 2.x" or "IBM WSAD 5.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 eclipse while performing the plugin installation. If you are performing the installation from JProfiler's setup wizard, please complete the entire setup first before starting eclipse.
A file selector will then prompt you to locate the installation directory of eclipse. For WSAD, this is the directory that contains the "eclipse" subdirectory.
After acknowledging the completion message, you can start eclipse and check whether the installation was successful. If the menu item Run->Invoke JProfiler does not exist in the Java perspective, please enable the JProfiler plugin for this perspective under Window->Customize perspective by opening the Other section and checking "JProfiler".

To profile your application from eclipse, choose Run->Invoke JProfiler from eclipse's main menu or click on the corresponding toolbar button.

Main toolbar with "JProfiler" button

"Run" menu with "JProfiler" action

A dialog with the available launch configurations will be displayed. Choose the desired configuration and press [Ok]. If JProfiler has already been opened from eclipse, you can check the Open in new window option to open a new window of JProfiler for the profiling session. Otherwise the last used main window will accommodate the profiling session.

If no instance of JProfiler is currently running, JProfiler is started, otherwise the running instance of JProfiler will be used for starting the application and for presenting profiling data. The information contained in the launch configuration is transmitted to JProfiler. With this information, JProfiler immediately starts a new profiling session. When you close the window, JProfiler asks you if you want to save the session for standalone execution. If you answer with yes, you can enter a name for the session. You will then be able to start it from the start center or from the open session dialog if you open JProfiler as a standalone application.

All profiling settings and view settings changes are persistent across session restarts.

When JProfiler is used with the eclipse integration, the "Show source" action for a class or a method in one of JProfiler's view will show the source element in eclipse and not in JProfiler's integrated source code viewer.

Note: To configure a native library path, please define the VM parameter -Djava.library.path in eclipse, it will be translated to the native library path by JProfiler.

The used JProfiler installation can be changed by repeating the integration from JProfiler or by adjusting the JProfiler executable in eclipse under Window->Preferences->JProfiler. When you upgrade to a newer version of JProfiler, make sure to repeat the integration, since the plugin has to be updated, too.