Using DevPartner Remote Agent with IBM WebSphere 3.5 on Solaris



How can I use DevPartner Remote Agent 2.1 to profile Java applications on IBM WebSphere 3.5


The following steps are required to properly configure WebSphere 3.5 on Solaris in order to profile your Java applications with Compuware's DevPartner Remote Agent version 2.1.

   1. Download and install the supported JVMPI JDK

   2. Add IBM extensions to the new JDK

   3. Modify WebSphere startup files to point to the new JDK

   4. Launch WebSphere through dpagentshell and profile as


Download and install the JVMPI JDK

The JVM installed with WebSphere 3.5 does not support the Java Virtual Machine Profiling Interface (JVMPI) required by the DPRA to gather data. To properly run within the WebSphere environment, you need to substitute a JVMPI supported JVM in the WebSphere environment. To accomplish this first Download and Install Sun Microsystems' JDK 1.2.2 Reference Implementation from:

Add IBM extensions to the new JDK

Install IBM's RMI-IIOP extensions to support CORBA within your newly installed JDK. This involves copying .jar files and shared libraries from Web Sphere's JDK extension directory to your JDK 1.2.2 Reference Implementation. The following files need to be copied:

    <WebSphere install>/java/jre/lib/

    <WebSphere install>/java/jre/lib/ext/cosnaming.jar

    <WebSphere install>/java/jre/lib/ext/jndi.jar

    <WebSphere install>/java/jre/lib/ext/providerutil.jar

    <WebSphere install>/java/jre/lib/ext/rmiregistry.jar

    <WebSphere install>/java/jre/lib/ext/iioprt.jar

    <WebSphere install>/java/jre/lib/ext/rmiorb.jar

    <WebSphere install>/java/jre/lib/sparc/

    <WebSphere install>/java/jre/lib/sparc/

    <WebSphere install>/java/lib/idlj.jar

    <WebSphere install>/java/lib/tools.jar

    <WebSphere install>/java/lib/orb.idl

    <WebSphere install>/java/lib/ir.idl

Or use the following shell script to automate the process.

#! /bin/ksh

## Copy IBM specific RMI-IIOP to Solaris JDK 1.2.2 directory

# Usage  source (IBM WebSphere) destination (new JDK)

cp $1/java/jre/lib/ $2/jre/lib/

cp $1/java/jre/lib/ext/cosnaming.jar $2/jre/lib/ext

cp $1/java/jre/lib/ext/jndi.jar $2/jre/lib/ext

cp $1/java/jre/lib/ext/providerutil.jar $2/jre/lib/ext

cp $1/java/jre/lib/ext/rmiregistry.jar $2/jre/lib/ext

cp $1/java/jre/lib/ext/iioprt.jar $2/jre/lib/ext

cp $1/java/jre/lib/ext/rmiorb.jar $2/jre/lib/ext

cp $1/java/jre/lib/sparc/ $2/jre/lib/sparc

cp $1/java/jre/lib/sparc/ $2/jre/lib/sparc

cp $1/java/README.rmi-iiop $2

cp $1/java/lib/idlj.jar  $2/lib

cp $1/java/lib/tools.jar  $2/lib

cp $1/java/lib/orb.idl   $2/lib

cp $1/java/lib/ir.idl $2/lib

exit 0

Modify WebSphere startup files to point to the new JDK

This step involves modifying environment variables to ensure that

the WebSphere servers use the new JDK 1.2.2 Reference Implementation. This involves manually editing the following IBM startup scripts located in the:

<install directory>/WebSphere/bin directory

A.  - Modify the following

                               environment variables:


- Reference the new JDK path


- set to $JAVA_HOME/jre/bin/java

B. admin.config  Modify the following variables

                         to reference the new JDK path

C. - Modify the following

                             environment variable:


- Reference the new JDK path

Launch WebSphere through dpagentshell and profile as required

To instrument the WebSphere applications run dpagentshell and launch the WebSphere server ( and administrative client interface ( Java applications will be instrumented from within the DPAgent shell.


1. Make backup copies before editing any files.

2. If you apply a FixPack to your WebSphere environment, be

    sure to perform the steps outlined in this tech note before

    running DPRA.

Old KB# 11660
Comment List
Related Discussions