This tutorial explains how to profile a Java code running with WebSphere 3.5.
In this document, <WebSphere> is the directory where WebSphere 3.5 has been installed (ex: c:\WebSphere\AppServer) and <OptItDir> is the directory where OptimizeIt has been installed. (ex: c:\OptimizeItDemo\OptimizeIt40D)

1) Configuring WebSphere 3.5 for OptimizeIt

2) Starting the OptimizeIt servlet

The OptimizeIt servlet allows you to start OptimizeIt profiler in the virtual machine of the Application Server of WebSphere. Once the profiler runs in the virtual machine of the Application Server, you can attach to the Application Server from OptimizeIt. Once this operation is done, you should see a message in your web browser indicating that OptimizeIt's audit system is running.

3) Attaching from OptimizeIt

Now that the Application Server is running with OptimizeIt profiler, you can start OptimizeIt and attach to the virtual machine. Note: OptimizeIt does not have a "detach" function. If you press the stop button in OptimizeIt, the Application Server exits and automatically restarts. After doing this, you need to invoke the OptimizeIt servlet to restart the profiler.

4) Filtering resources used by WebSphere

OptimizeIt provides filters for filtering resources used by WebSphere. In order to use filters, you must create an OptimizeIt setting for the profiling session,  turn on the WebSphere filter, and then attach by using the Attach now button or pressing the play button. Note: OptimizeIt settings can be saved for subsequent usage. This is done by using the save menu.

5) Starting OptimizeIt profiler from your Java code

While the OptimizeIt servlet is convenient to start profiling quickly, you may want to automatically start OptimizeIt profiler with one of your servlet. That way, you don't have to invoke the OptimizeIt servlet to start the audit system before testing your servlets.

Starting OptimizeIt profiler can be easily done by using OptimizeIt's API. OptimizeIt's API is documented in OptimizeIt user manual, chapter 9. The following code demonstrates how to start the profiler from your servlet:

import intuitive.audit.Audit;
...
static boolean isProfilerStarted = false;
 if(!isProfilerStarted) {
        /* Start OptimizeIt's profiler */
        Audit.start(1470, Audit.PROFILERS_ALWAYS_ENABLED);
   isProfilerStarted = true;
  }
...


Note: you will need to add <OptItDir>\lib\optit.jar to your CLASSPATH to compile this code

Once OptimizeIt's profiler is running, you can start OptimizeIt and attach to WebSphere.
 

Copyright (c) 1997, 1998, 1999, 2000, 2001 Intuitive Systems Inc. All rights reserved. Specifications subject to change without notice.
OptimizeIt is a trademark of Intuitive Systems, Inc.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. All other brand names and products are trademarks or registered trademarks of their respective holders.