ERP/CRM Diagnostics Module Architecture - LoadRunner

The ERP/CRM Diagnostics architecture is composed of the following components:

ERP/CRM Mediator: The ERP/CRM Mediator (“mediator”) gathers and correlates offline transaction data from the Web, database, and application servers. The mediator must be installed on a machine that resides in the same LAN as the monitored ERP/CRM server, and preferably on a dedicated server. We do not recommend installing the mediator on a Siebel or Oracle server that is involved in the load test.

Note: By default, the mediator agent is installed to run as a process. We recommend configuring the mediator agent to run as a service.

If you run the agent as a process, you may encounter the following Microsoft Windows networking limitation: “Failed to establish connection. System error 1219“. You can either:

1. Run the agent as a service.
2. Disconnect all previous connections to the server and try again.

Note: For Siebel DB diagnostics, it may take a long time to copy the files from the application server to the mediator, and then from the mediator to the results directory. During the first copying stage, the Summary Data Processing window is displayed. To minimize copying time in the second stage (if you are not working over a firewall), we recommend using localhost as the mediator machine. This reduces the time it takes to copy the Siebel DB diagnostics files to the results directory, since the diagnostics files are already on the Controller machine.

Controller: Before scenario execution, the Controller transfers all server information to the mediators and distributes the percentage of users that will participate in the monitoring. After scenario execution, the Controller collects the aggregated transaction data files from the mediators and collates the results. Siebel results are transferred to the \sbl_bd directory, and Oracle DB diagnostics are transferred to the \ora_bd directory. You can view the status of diagnostics file collation in the Collate Results dialog box.

Load Generator:When you execute a scenario, the Controller distributes each Vuser to a load generator, and the load generator executes the Vuser script.

Analysis: Displays detailed diagnostics graphs and reports.