During a performance test, the ALM diagnostics modules trace, time, and troubleshoot individual transactions across the Web, application, and database servers. You can drill down from a slow end-user transaction all the way to the bottlenecked method or SQL statement. The ALM Performance Center diagnostics modules enable organizations to:

• Rapidly isolate application components that have a significant impact on end-user experience.

• Provide developers with precise data on how to make performance improvements.

ERP/CRM Diagnostics architecture, as shown in the diagram below, is comprised of the following components:

• Mediator. The ERP/CRM Mediator ("Mediator") gathers and correlates offline transaction data from the Web, database, and application servers. For information on installing the Mediator, see the HP LoadRunner Installation Guide.

• Controller. Before test execution, the Controller transfers all server information to the Mediator and distributes the percentage of users that will participate in the monitoring. After test execution, the Controller collects the aggregated transaction data files from the Mediators and collates the results. Results are transferred to the Siebel diagnostics, SAP diagnostics, or Oracle DB results directory.

• Load Generators. When you execute a load test, the Controller distributes each Vuser to a load generator, and the load generator executes the Vuser script.

• Analysis. Displays detailed diagnostics graphs and reports. For more information about the diagnostics graphs, see the HPE LoadRunner Analysis User Guide.

When you set up the ERP/CRM Diagnostics modules, you define a server to monitor by entering the user name of the server where trace/log files are stored. This section explains how the Mediator connects to the server when it is a remote Windows or UNIX server.

• When monitoring a remote Windows server, the Mediator attempts to connect to the server using the configuration details which you enter in the <diagnostics type> Server Configuration Dialog Box during the diagnostics configuration process. This configuration should give administrator permissions to the remote machine.

• When monitoring a remote Linux, the Mediator supports the remote shell connection type. For more information on remote shell connections, see the section that describes verifying the Linux load generator installation in the HP LoadRunner Installation Guide.

Siebel Diagnostics are split into the following modules:

• Siebel Diagnostics Module. Enables you to break down Siebel transactions into layers, areas, sub-areas, servers, and scripts. You can also view the transaction chain of calls and call stack statistics to track the percentage of time spent on each part of the transaction. Siebel-Web Vusers support Siebel Diagnostics.

• Siebel DB Diagnostics Module. Helps you rapidly identify and resolve database performance problems. You can view the SQLs for each transaction, identify the problematic SQL queries of each script, and identify at which point problems occurred. Siebel-Web Vusers support Siebel DB Diagnostics.

For information on how to pre-configure the Siebel/Siebel DB Diagnostics modules, see How to Pre-Configure Siebel/Siebel DB Diagnostics.

Oracle 11i Diagnostics helps pinpoint performance problems on Oracle NCA systems. The diagnostics information drills down from the transaction to the SQL statements, and to the SQL stages of each statement. Oracle NCA Vusers support Oracle 11i Diagnostics.

For information on how to pre-configure the Oracle 11i Diagnostics module, see How to Pre-Configure Oracle 11i Diagnostics.

SAP Diagnostics enables you to pinpoint the root cause of a certain problem (for example, DBA, Network, WAS, Application, OS/HW) quickly and easily, and engage with the relevant expert only, without having to present the problem to a whole team of people.

For information on how to configure the SAP Diagnostics module, see How to Pre-Configure SAP Diagnostics.

Server-side Data Collection. SAP Diagnostics is based on SAP Distributed Statistical Records (DSR). For each dialog step performed on application server, a statistical record is generated, which includes information such as response time components, database statistics, RFC times, and so on. The Diagnostics Mediator is responsible for collecting diagnostics data from the server during a performance test.

Vuser Coloring. SAP Diagnostics allows replaying the SAPGUI protocol. You set the percentage of colored Vusers in the Configuration dialog (up to 100% allowed). Coloring of SAPGUI users creates no overhead on the Application server.