Using JARM for Monitoring Runtime Performance 

Use

You can use the Java Application Response Time Measurement (JARM) mechanism to measure the response time of Visual Composer functions, such as calls to data services or connections made through the portal connector framework. For more information, see Java Application Response Time Managementin the Java Technology Administration Manual.

JARM triggers have been programmed to map the total time spent in the VCBroker processing requests (inside the broker’s doContent method). These include calls to:

·        BAPIs

·        RFCs

·        Web services

·        Enterprise services

JARM cannot be used to measure processes for Adobe Flex and Web Dynpro calls.

Procedure

In Visual Administrator:

...

...

       1.      In the left pane, choose Server  ®  Services  ®  Performance Tracing.

       2.      In the main pane, click the JARM tab.

       3.      Run a Flex iView with a data service that uses the VCBroker.

       4.      In Visual Administrator, switch to the Component Overview in the left pane.

       5.      Click the first toolbar button, Actualize Data (with the blue circular arrows).

       6.      To filter out non-VCBroker components:

                            a.      Click the Filter button (the funnel). The Configure Filter dialog box is displayed.

                            b.      Click the Component tab.

                            c.      In the Component Name field, enter the filter EP:VC*.

                            d.      Click the Filter is off tab to turn it on.

Three Visual Composer components should be visible:

¡        EP:VCBroker:execService

Maps the time spent after the VCBroker has determined that it is answering a data service call, and until it returns the response xml. This is in order to ensure that the average time of this component is not distorted by the initial translation/user data calls.

¡        EP:VCBroker:createNewConnection

Maps the time between determining if a new connection is needed (no cached one available) and actually making the connection. If connection management is used, the average time reported for this component may not reflect the actual connection times, because not every data service requires a new connection from the same back-end system.

¡        EP:VCBroker:execute

Records the time spent in the portal Connector Framework, executing the data service.

       7.      To view the JARM information of the development server, use the header VC:devserver: as a filter.

·         Requests for translation and user data are not recorded in the three Visual Composer components. Be aware of this when comparing total/average request times with those of the components.

·         You can track an individual user, comparing his or her data to system averages, by filtering in the User tab of the Filter dialog box.