Start of Content Area

Procedure documentation Measuring the Performance of Web Dynpro Applications  Locate the document in its SAP Library structure

Use

If you suspect that the Web Dynpro application is itself responsible for poor response times, you must identify the methods that are responsible for this behavior. The Web Dynpro framework enables you to include the event handler of a Web Dynpro application in your performance considerations. In this way you can determine the times necessary for analysis with the assistance of the Web Dynpro Console.

Prerequisites

You have administrator rights for the J2EE Engine or for SAP Enterprise Portal. If you do not have administrator rights, you can only access a small part of the monitoring information.

Procedure

       1.      To measure the performance of the Web Dynpro application, you must set the Java Application Responsetime Measurement (JARM) level to a value between 5 and 10 in the uppermost toolbar of the SAP NetWeaver Developer Studio under Preferences  Web Dynpro Generation.

       2.      To apply the new setting choose Apply.

       3.      To confirm the entry choose OK.

       4.      Rebuild the Web Dynpro project with the context menu Build Project.

       5.      Then deploy it and restart the Web Dynpro application.

Note

By setting a JARM level additional source text is added when you generate the Java classes. This source text uses the methods startComponent and endComponent of the JARM monitor to ensure that the time between calling and ending the method is measured. For example, the following bold source text is generated for the method wdDoInit:

/**

   * Hook method called to initialize view controller.

   */

  public void wdDoInit() {

    logger.pathT("entering: wdDoInit");

    TaskBinder.getCurrentTask().getJarmMonitor().startComponent("comsap.tut.wd.tutwd_table_init.tablecomp.TableCompView#wdDoInit");

    delegate.wdDoInit();

    TaskBinder.getCurrentTask().getJarmMonitor().endComponent("comsap.tut.wd.tutwd_table_init.tablecomp.TableCompView#wdDoInit");

    logger.pathT("exiting: wdDoInit");
  }

 

You can thus determine the time needed to execute the wdDoInit. You can set the measuring points in a Web Dynpro application to a higher granularity in the same way. To do so you must formulate the source text yourself.

       6.      To access the performance data, go to the Web Dynpro Console, which is either already open or can be started directly with the URL http://<Host Name:<Port Number>/webdynpro/dispatcher/sap.com/tc~wd~tools/WebDynproConsole.

       7.      Navigate to Applications under the tree item Performance.

       8.      Select the package name of the Web Dynpro application to be tested.

       9.      The performance data for the given time in [msec] is displayed automatically in the table.

Result

This data tells you how long the individual event handlers and methods took. Based on this data you can find the event handlers and methods that took the longest and slowed down the response times.

  

  

 

End of Content Area