Profiling portlets on remote servers

Profiling tools allow you to gather runtime statistics and analyze the performance of your portlets.

To use Rational® Developer profiling tools to analyze the performance of a portlet running on a remote server, you must first install the Agent Controller on the system where the WebSphere® Portal server is running. You must also enable profiling on the remote WebSphere Portal server.

To use profiling tools on a portlet running on a remote server,

  1. Define a remote portal server attach server.
  2. On the remote system, start the WebSphere Portal server.


    For Windows

    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
    ./startServer.sh WebSphere_Portal
    where WebSphere_installation_root is the directory where you installed WebSphere Application Server.
  3. On the remote system, start the Agent Controller.

    For Windows
    1. Open Control Panel > Administrative Tools > Services
    2. Highlight the IBM Rational Agent Controller service. Right-click and select Start.


    For
Linux

    Type the following from a command window:

    cd Agent_Controller_installation_root/bin
    ./RAStart.sh
    where Agent_Controller_installation_root is the directory where you installed Agent Controller.
  4. From the Project Explorer view, expand Dynamic Web Projects. Select a portlet project, right-click and select Run > Run on Server. The portlet is published to the remote portal server and the Web browser opens to the PortletPreview page.
  5. Define profiling options.
  6. Select Run > Profile.
  7. Select the Attach - Java Process configuration that you defined for the remote server.
  8. On the Agents tab, highlight the unknown agent in the left pane. Click > to move the agent to the Selected Agents list in the right pane.
  9. You can use the Profiling tab to override your default profiling settings.
  10. Click Profile.
  11. If the Profiling Tips dialog box opens, click OK.
  12. If the Confirm Enablement dialog box appears, click OK.
  13. In the Profiling Monitor view of the Profiling and Logging perspective , right-click unknown at host name > <attached> Profiling (date time) and select Start Monitoring.
  14. Switch back to the Web perspective and use your portlet application.
  15. Switch back to the Profiling and Logging perspective.
  16. Right-click unknown at host name > <attached> Profiling (date time) and select Pause Monitoring.
  17. Double-click the Execution Time Analysis entry in the Profiling Monitor view. The statistics that you collected appear on the right. If the statistics do not display correctly, right-click in the right pane and select Refresh Views.
  18. Right-click unknown at host name > <attached> Profiling (date time) and select Detach from Agent.

    Warning: Do not use the Terminate option. This stops the server that is being monitored.

Related concepts
Getting started with run-time problem determination
Related tasks
Profiling portlets on local servers
Installing Agent Controller
Enabling profiling on remote WebSphere Portal servers
Defining profiling options
Profiling an application
Related reference
WebSphere Studio Application Developer Version 5 Programming Guide Redbook

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