This document describes how to integrate JProbe with IBM's WebSphere Application Server Advanced Single Server Edition on UNIX.
It is assumed that:
1. There is a writable directory named /tmp.
2. WebSphere is installed to /opt/WebSphere/AppServer.
3. JProbe is installed to /opt/JProbe_Suite.
4. You have downloaded and installed the most recent JProbe Technical Support Pack.
Please adjust path names and install patches as appropriate.
Integration errors will prevent access to the Administrative Console, so make changes to a copy of the server configuration file. The application server can be started with an alternate configuration file using startServer.sh -configFile <config file name>.
JProbe Instructions
Start JProbe Profiler, Memory Debugger, Coverage, or Threadalyzer.
Select Session > New Settings... from the JProbe menu. The JProbe LaunchPad appears.
Under Data Collection Settings, create a filter on at least one package, class, or method.
Under Runtime Settings, set the Snapshot Directory to /tmp.
Do not modify Program Settings, they will be provided by WebSphere.
Save the settings as /tmp/was.jpl.
Close the JProbe LaunchPad by clicking OK.
Select Program > Attach to Remote Session from the JProbe menu.
Set the snapshot directory to /tmp and click OK.
WebSphere Instructions
Open the WebSphere Administrative Console.
Select the application server you want to profile (ie. Default Server).
Click Process Definition.
Change the Executable Name to:
/opt/JProbe_Suite/bin/jplauncher -jp_java=/opt/WebSphere/AppServer/java/bin/java -jp_input=/tmp/was.jpl
Click Save
Click OK
Stop the application server with stopServer.sh.
Restart the application server with startServer.sh -configFile <config file name>.
For more information on using JProbe to profile your application, please consult the JProbe Documentation found in the JPROBE_HOME\doc directory.
If Something Goes Wrong
The most common cause of failure is a mistyped path name, so double check the arguments to -jp_input and-jp_java. If all of the path names are correct, check the WebSphere log files for more informative error messages.
