LoadRunner ERP/CRM Diagnostics Types - LoadRunner

LoadRunner provides the following ERP/CRM Diagnostics solutions:

  • Siebel Diagnostics
    The diagram below shows transaction breakdown on a Siebel CRM system. LoadRunner’s Siebel diagnostics are split into the following modules:

LoadRunner ERP/CRM Diagnostics Types

Siebel Diagnostics Module enables you to breakdown 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 percent of time spent for each part of the transaction. Siebel-Web Vusers support Siebel Diagnostics.

Siebel DB Diagnostics Module helps you to 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 what point problems occurred. Siebel-Web Vusers support Siebel DB Diagnostics.

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

Working With LoadRunner ERP/CRM Diagnostics

To use LoadRunner’s ERP/CRM diagnostics, follow these steps:

  1. Prepare for generating diagnostics data.
    Make sure that the ERP/CRM Mediator is installed. The mediator collects and processes the diagnostics data. The ERP/CRM Mediator is installed on the Controller machine as part of the LoadRunner Full Setup.
  2. Configure the erver machine to enable the diagnostics feature.
    For more information, see “Configuring Siebel Diagnostics on the Application and Web Servers”, “Enabling Server Logging on the Siebel Server” , “Enabling Server Logging on the Oracle Server”, and “Selecting the Oracle NCA Application Version” .
  3. Prepare the Controller machine to generate diagnostics data and communicate with the mediator machines.
    For more information, see “Configuring Siebel Diagnostics” , “Configuring Siebel DB Diagnostics”, “Configuring Oracle DB Diagnostics”, and “Enabling Diagnostics” .
  4. Collect and prepare the diagnostics data.
    During the load test, the mediator collects the data and processes the diagnostics information.
  5. Create the results.
    After the load test, the Controller collects the aggregated data from the mediator machines and collates the results. For more information on result collation, see “Collating Results”
  6. Present the data.
    Use the analysis graphs to view the diagnostics data and drill down to the problematic areas.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

LoadRunner Topics