Adobe Performance Analysis 

Problem Description

This problem analysis scenario describes the approach in order to investigate performance problems of the Adobe document services.

The description of Distributed Statistical Records (DSR) that are automatically written for all components running inside the Web AS Java is out of scope for this document.

Scenario Type:	Performance analysis
NetWeaver Component:	SAP Web AS
Validity:	SAP NetWeaver 04 >= SP Stack 12 SAP NetWeaver 7.0 >= SP Stack 4

Decision Roadmap

Prerequisites

You need to have access to the following systems:

●      Web AS Java that hosts the Adobe document services (HTTP connection)

●      Web AS ABAP that hosts the Computing Center Management System (CCMS) (SAP GUI connection)

In order to change configuration settings you will need the appropriate user rights.

Main Tools

●      Visual Administrator

●      Transaction RZ20

Analysis

Check general availability

First of all you should check the general availability of the document services.

...

       1.      Connect to the CCMS and start transaction RZ20.

       2.      Navigate to the monitor set SAP J2EE Monitor Templates and load the monitor Adobe Document Services.

The Heartbeat node contains availability information for all registered servers. For more information, see Configuring GRMG Availability for the Adobe Document Services.

Check performance data

The Adobe document services are instrumented with JARM instructions in order to provide performance data. To view this performance information, do the following:

...

       1.      Start the Visual Administrator and choose Server <x>  →  Services  → Performance Tracing.

       2.      Choose the JARM tab within the right window pane, to get access to the JARM traces.

       3.      Click the button  Actualize all information and choose the tab Request Overview. The entries in the column Request Name are labeled in the format NW:J2E:SRV:HTTP.

The Adobe document services are accessed via a web service interface (i.e. HTTP protocol). Due to this fact the performance data on the top level is written by the HTTP layer.

       4.      Select such an entry for seeing detailed information in a separate section of the window. This table displays the components in different levels that were involved during the request processing with their appropriate net times. All components that are part of the document services begin with ADS:. By analyzing these values, you will be able to determine possible performance bottlenecks.

Additional Information

For more information see following documents:

●      Interactive Forms based on Adobe Software

●      Adobe Document Services Configuration Guide

●      Java Application Response Time Measurement