The HP Diagnostics integration
with LoadRunner allows you to monitor and analyze the performance of Java 2
Enterprise Edition (J2EE), .NET-connected, SAP, Oracle, and other complex
environments.
Specifying the
Diagnostics Server Details: The first time you use LoadRunner to
capture J2EE or .NET diagnostics data, you need to identify the machine on
which the Diagnostics Server in Commander mode is running, and the port that it
is using for communication with LoadRunner. You must update this information if
you want to integrate with a different Diagnostics Server in Commander mode, or
if you change the port it is using. To update the LoadRunner configuration
settings for HP Diagnostics:
1. Select Start > Programs
> HP LoadRunner > LoadRunner to open the LoadRunner launcher window.
2. From the LoadRunner launcher
window menu, select Configuration > Diagnostics for J2EE/.NET Setup to open
the Diagnostics for J2EE/.NET Setup dialog box. Enter the details for the
Diagnostics Server in Commander mode.
3. Click Test to verify that you
entered the correct information for the Diagnostics Server in Commander Mode
and that there is connectivity between the Diagnostics Server in Commander Mode
and LoadRunner. Click OK to complete the configuration process.
Configure
LoadRunner Scenarios to use HP Diagnostics
1. Before configuring your
scenario for Diagnostics, ensure that the application server that you are
monitoring has been started.
2. In the Controller, open the
relevant load test scenario (File > Open) or create a new scenario (File
> New).
3. Select Diagnostics >
Configuration to open the Diagnostics Distribution dialog box.
4. Set the percentage of Vusers
to participate in the HP Diagnostics (J2EE/.NET Diagnostics) monitoring. The
maximum percentage of Vusers for which HP Diagnostics (J2EE/.NET Diagnostics)
data can be collected is 100%, unless you have enabled other types of
diagnostics. In this case, the percentage of Vuser participation in HP
Diagnostics (J2EE/.NET Diagnostics) cannot exceed the maximum of any of the
other types of diagnostics that you enabled.
5. In the Online & Offline
Diagnostics section of the Diagnostics Distribution dialog box, next to
J2EE/.NET Diagnostics, click Configure. The J2EE/.NET Diagnostics Configuration
dialog box opens.
6. Select Enable J2EE/.NET
Diagnostics
7. In the Select probes list,
select the probes to be included in your load test scenario.
8. If the Diagnostics Server (or
a Diagnostics Server in Mediator mode in a distributed environment) is located
behind a firewall, select there is a firewall between the mediator and the
Controller, and enter the name of the MI listener server in the MI listener
server box. If there is a firewall between the LoadRunner Controller and the
Diagnostics Server involved in a load test, you must configure the Controller
and the Diagnostics Server to use the MI Listener to enable the transfer of the
offline analysis file.
9. To capture a percentage of
server requests which occur outside the context of any Vuser transaction select
Monitor server requests.
10. To investigate any issues
that you have with the connections between the Diagnostics components, click
the Troubleshoot Diagnostics for J2EE/.NET connectivity link. This will open
the HP Diagnostics System Health Monitor in a new browser window.
During a LoadRunner load test
scenario, you can view HP Diagnostic’s data for the whole scenario or you can
drill down to HP Diagnostic’s data from a particular transaction. After you
have run your scenario, you can use HP LoadRunner Analysis to analyze offline
Diagnostics data generated during the scenario.
