This tutorial explains how to profile java code running with IBM WebSphere 2.0.

In this document:

     <OptItDir> is the directory where OptimizeIt has been installed. (ex: c:\OptimizeIt\OptimizeIt311D)
     <WebSphereDir> is the directory where WebSphere has been installed (ex: d:\WebSphere)

1) Configuring WebSphere

2) Starting the OptimizeIt servlet

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 WebSphere is running with OptimizeIt profiler, you can start OptimizeIt and attach to the virtual machine.

4) 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 the servlet engine.
 

Copyright (c) 1997, 1998, 1999, 2000 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.