Setting up environment variables to profile a server

Profiling a server allows you to analyze performance, threading, and memory usage when running a Web application. You must setup environment variables on the target host machine before starting the server in profile-mode. The machine to setup the environment variables depends if your application server is located on the same or another machine as your workbench.

Select one of the following scenarios that applies to your environment:

For a server running on the same machine as the workbench, complete the following steps:

  1. Locate the following plugin folders under the installation directory of the IBM® Rational® Software Delivery Platform: 

     

    <Agent Controller Home>=<install_dir>\SDPShared\plugins\org.eclipse.tptp.platform.ac.win_<XXXX>\agent_controller
<Java Profiler Home>=<install_dir>\SDPShared\plugins\org.eclipse.tptp.platform.jvmti.runtime<n.n.n>.v<yyyymmddtttt>\agent_files\win_<XXXX>

    Optional: If you are using the Probe Insertion monitor option, locate and include the following plugin folder: 

    <Probekit Home>=<install_dir>\SDPShared\plugins\org.eclipse.hyades.probekit<n.n.n>.v<yyyymmddtttt>\os\win32\x86

     

    <Agent Controller Home>=<install_dir>/SDPShared/plugins/org.eclipse.tptp.platform.ac.linux_<XXXX>/agent_controller
<Java Profiler Home>=<install_dir>/SDPShared/plugins/org.eclipse.tptp.platform.jvmti.runtime<n.n.n>.v<yyyymmddtttt>/agent_files/linux_<XXXX>

    Optional: If you are using the Probe Insertion monitor option, locate and include the following plugin folder: 

    <Probekit Home>=<install_dir>/SDPShared/plugins/org.eclipse.hyades.probekit<n.n.n>.v<yyyymmddtttt>/os/linux/x86
    where <install_dir> is the installation directory of the IBM Rational Software Delivery Platform and <XXXX> depends on the architect of the operating system. Substitute <XXXX> with your appropriate processor by selecting ia32 for a 32-bit processor, em64 for a 64-bit processor, or ipf for an Itanium® Processor Family processor, for example org.eclipse.tptp.platform.ac.win_ia32_<n.n.n>.v<yyyymmddtttt>, where <n.n.n> is a version number, and <yyyymmddtttt> is a date and time stamp of the plugin.

  2. Setup the following environment variables before you start the workbench and the application server.

    1. Open a command prompt and type the following commands by replacing <Agent Controller Home>, <Java Profiler Home> and the optional <Probekit Home> with the value identified above: 

       

      set TPTP_AC_HOME=<Agent Controller Home>
set JAVA_PROFILER_HOME=<Java Profiler Home>
set PROBEKIT_HOME=<Probekit Home>
set PATH=%JAVA_PROFILER_HOME%;%TPTP_AC_HOME%\bin;%TPTP_AC_HOME%\lib;%PROBEKIT_HOME%;%PATH%

       

      export TPTP_AC_HOME=<Agent Controller Home>
export JAVA_PROFILER_HOME=<Java Profiler Home>
export PROBEKIT_HOME=<Probekit Home>
export LD_LIBRARY_PATH=$JAVA_PROFILER_HOME:$TPTP_AC_HOME/bin:$TPTP_AC_HOME/lib:$PROBEKIT_HOME:$LD_LIBRARY_PATH

  3. Start the IBM Rational Software Delivery Platform workbench from a command prompt such that the environment variables are picked up by the workbench process. For example, run the following command: 

     

    /opt/IBM/SDP>./eclipse -product com.ibm.rational.rad.product.v75.ide

     

    C:\Program Files\IBM\SDP>eclipse -product com.ibm.rational.rad.product.v75.ide

For application servers running on a different machine from the workbench, complete the following steps:

Note: If you are profiling a remote application server, install Agent Controller on the same machine where the application server is located. Verify the below environment variables settings are picked up by the startup process of the application server.

  1. On the machine where the remote application server is located, setup the following environment variables before you start the workbench and the application server:

    1. Set the following environment variables on the target system by replacing <AC installation directory> with the installation directory of the Agent Controller. In addition, if you are using the Probe Insertion monitor option, specify the PROBEKIT_HOME environment variable: 

       

      set TPTP_AC_HOME=<AC installation directory>
set JAVA_PROFILER_HOME=%TPTP_AC_HOME%\plugins\org.eclipse.tptp.javaprofiler
set PROBEKIT_HOME=%TPTP_AC_HOME%\plugins\org.eclipse.hyades.probekit
set PATH=%JAVA_PROFILER_HOME%;%TPTP_AC_HOME%\bin;%TPTP_AC_HOME%\lib;%PROBEKIT_HOME%\lib;%PATH%

       

      export TPTP_AC_HOME=<AC installation directory>
export JAVA_PROFILER_HOME=$TPTP_AC_HOME$/plugins/org.eclipse.tptp.javaprofiler
export PROBEKIT_HOME=$TPTP_AC_HOME$/plugins/org.eclipse.hyades.probekit
export LD_LIBRARY_PATH=$JAVA_PROFILER_HOME:$TPTP_AC_HOME/bin:$TPTP_AC_HOME/lib:$PROBEKIT_HOME/lib:$LD_LIBRARY_PATH

 

Related concepts

J2EE Request Profiler

 

Related tasks

Starting a server in profiling mode

Profiling the application using the WAS

Displaying the data collected by the J2EE Request Profiler as sequence diagrams