This tutorial explains how to profile Java code with BEA WebLogic 4.5.1 and WebLogic 5.0
We advise you to use the wizard for WebLogic that OptimizeIt features, which performs automatically the steps described in this tutorial. This wizard can be started from OptimizeIt by selecting the Tool/Application server integration/WebLogic menu.
In this document, <OptItDir> is the directory where OptimizeIt has been installed. (ex: c:\OptimizeIt31D), and <WebLogicDir> is the directory where WebLogic has been installed (ex: c:\WebLogic).
 

1) Configuring the startWebLogicWithOptimizeIt script

2) Configuring the weblogic.policy file

In order to be able to profile using the java 2 (jdk 1.2 or 1.3), you will need to give OptimizeIt's classes the correct rights:

3) Starting WebLogic

To start WebLogic, invoke the startWebLogicWithOptimizeIt.bat script:

4) Attaching from OptimizeIt

Now that WebLogic 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, WebLogic server exits. After doing this, you need to restart WebLogic server.

5) Filtering resources used by WebLogic

OptimizeIt provides filters for filtering resources used by WebLogic. In order to use filters, you must create an OptimizeIt setting for the profiling session,  turn on the WebLogic 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.

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.