Enabling profiling on remote WebSphere Portal servers

Profiling support must be enabled on the remote target WebSphere® Portal server before you can use the profiling tools within Rational® Developer. Profiling support is automatically enabled on local test environment servers.

To use profiling tools with WebSphere Portal v5.0, the WebSphere Application Server 5.0.2 Cumulative Fix for SDKs must be installed.

To enable profiling support on a remote WebSphere Portal server:

  1. On the WebSphere Portal system, start WebSphere Application Server.


    For Windows

    Start > All Programs > IBM WebSphere > Application Server v5.x > Start the Server


    For Linux

    From a command window, type these commands:
    cd WebSphere_installation_root/bin
    ./startServer.sh server1
    where WebSphere_installation_root is the directory where you installed WebSphere Application Server.
  2. Open the WebSphere Administrative console and log in.


    For Windows

    Start > All Programs > IBM WebSphere > Application Server v5.x > Administrative Console


    For Linux

    From a Web browser, open one of the following URLs to access the WebSphere Administrative console. Port 9090 is the default port if security is not enabled on the WebSphere server; port 9043 is the default port if security is enabled.
    http://your.server.name:9090/admin
    https://your.server.name:9043/admin
    where your.server.name is the fully-qualified host name of the WebSphere Application Server system.
  3. In the left pane, select Servers > Application Servers .
  4. In the right pane, select the WebSphere_Portal server.
  5. On the Configuration tab of the WebSphere_Portal page, select Process Definition from the list of Additional Properties.
  6. On the Configuration tab of the Process Definition page, select Java Virtual Machine from the list of Additional Properties.
  7. On the Configuration tab of the Java Virtual Machine page, under General Properties, add the following to the Generic JVM arguments field to enable profiling:
     -XrunpiAgent:server=enabled

    To enable the J2EE Request Profiler, also add the following option to the Generic JVM arguments field:

    -DPD_DT_ENABLED=true 
  8. Click OK.
  9. Click Save, then click Save on the Save to Master Configuration panel.
  10. Logout of the WebSphere Administrative console.
  11. Stop the WebSphere Application Server.


    For Windows

    Start > All Programs > IBM WebSphere > Application Server v5.x > Stop the Server


    For Linux

    From a command window, type these commands:
    cd WebSphere_installation_root/bin
    ./stopServer.sh server1
    where WebSphere_installation_root is the directory where you installed WebSphere Application Server.
  12. Restart the WebSphere Portal server.


    For Windows

    Start > All Programs > IBM WebSphere > WebSphere Portal v5.x > Stop the Server

    Start > All Programs > IBM WebSphere > WebSphere Portal v5.x > Start the Server


    For Linux

    From a command window, type these commands:
    cd WebSphere_installation_root/bin
    ./stopServer.sh WebSphere_Portal
    ./startServer.sh WebSphere_Portal
    where WebSphere_installation_root is the directory where you installed WebSphere Application Server.
Note: Agent Controller must be installed and running on the same system where you installed the WebSphere Portal server before you can use the Rational Developer profiling tools.
Related tasks
Installing Agent Controller
Profiling portlets on local servers
Profiling portlets on remote servers
Defining profiling options
Profiling an application
Profiling an application in stand-alone mode
Profiling J2EE applications

(C) Copyright IBM Corporation 2002, 2005. All Rights Reserved.