Controller

You use the LoadRunner Controller to manage and maintain your scenarios. Using the Controller, you control all the Vusers in a scenario from a single workstation.

Creating the Scenario

A scenario describes the events that occur during a testing session. A scenario includes a list of machines on which Vusers run a list of scripts that the Vusers run, and a specified number of Vusers or Vuser groups that run during the scenario. You create scenarios using the LoadRunner Controller.

Creating a Manual Scenario

You create a scenario by defining Vuser groups to which you assign a quantity of individual Vusers, Vuser scripts, and load generators to run the scripts.
You can also create a scenario using the Percentage Mode, in which you define the total number of Vusers to be used in the scenario, and the load generator machines and percentage of the total number of Vusers to be assigned to each Vuser script.

Creating a Goal-Oriented Scenario

For Web tests, you can create a goal-oriented scenario, in which you define the goals you want your test to achieve. LoadRunner automatically builds a scenario for you, based on these goals.

Creating Sample Scenario

1. Launch LoadRunner
2. Under Load Testing tab, select Run Load Tests

3. To manage your load test by specifying the number of virtual users to run, select Scenario type as Manual Scenario

4. Add scripts to scenario and click Ok.

5. Look at the Scenario Groups, here you can add more scripts, edit Vusers quantity, add load generators, edit Runtimes Settings.

6. Then work on Scenario Schedule, specify Schedule name, according to test plan Choose Schedule type , and Run Mode

7. Then work on Global Schedule, keep properties for Initialize as it is.
8. Set Start Vusers properties depending on the ramp up required.
9. Specify Duration of test run.
10. Set Stop Vusers properties depending on the ramp down required.

11. You can see the graphical representation of the created scenario.

12. When you are done with Scenario Design part click on Run which is located at bottom of the page.
13. To add Windows Resources go to Available Graphs, Under System Resource Graphs, choose Windows Resources

14. To add Measurements, right click on Windows Resources, and choose Add Measurements.
15. In the Windows Resources pop-up, click on Add button, in the new pop-up specify Machine Information, like name and platform.

16. Select the Resource Measurements and click on add button, and add the resource.
17. Click on Start Scenario.
18. Now controller will start running your designed scenario.
19. When test is running you can monitor the Windows Resources and Test Status with respect to Transactions passed, failed and Errors occurred while running.

20. You can see the detail status of transaction passed and failed by click on mirror right next to Passed Transactions and Failed Transactions

21. You can see the errors thrown by web app by clicking on mirror right next to Errors

22. While test is running, if you want to Add Vusers, you can do that by clicking on Add Vusers Tab.
23. Select group name, quantity to add, load generators name and script name.
24. You can see the Test results by clicking on Analysis icon.

Performance Center

Using minimal hardware resources, HP Performance Center lowers the cost of distributed load testing by providing a standard solution that can be managed via the web.

This integrated performance validation solution emulates hundreds or thousands of concurrent users to apply simulated production workloads to virtually any client platform or environment. Using Performance Center, testing teams can stress an application from end to end—applying consistent, measurable and repeatable loads—and then use the data to identify scalability issues that could impact users. HP Performance Center:

• Lowers the cost of distributed load testing

• Reduces the risk of deploying systems that do not meet your performance requirements

Creating Load Test

1. Launch Performance Center link.
2. Under Load Test tab click on Manage and then to create new load test click on New Load Test
3. To manage load test, there are four tabs General, Workload, Monitors, Diagnotics.
4. In General tab, we specify load test name and description like type of test (baseline, benchmark), number of Vusers
5. In Workload tab, there are four types of scenario, most of the time we choose Basic Schedule, by load test and Vuser distribution option as by number.
6. Like LoadRunner Controller, there are many tabs to manage scenario.
7. In the Scripts tab, you can Add Scripts, Vusers, Load Generators.
8. In Global Schedule tab, you mention the properties like Initialize, Start Vusers (Ramp Up), Duration of the test run and Stop Vusers (Ramp Down).
9. To apply same runtime setting to all groups, Click on Duplicate Runtime Settings and select source group and target group to apply runtime settings.
10. For managing load generators, click on LG Distribution, choose Manual Distribution, under that choose Assign Actual LG to groups.
11. Select load generators.
12. To add and edit monitors, click on Monitors tab
13. To add monitors click on Add Profile, create New Profile.
14. Specify Profile name and description like App Server, Web Services, Database Server
15. Choose monitor like Windows Resources, under System Resources graph.
16. Choose Server which you want to monitor, provide server name, username, password for that server.
17. Select the Measurements like Page Faults/Sec, Processor Time.
18. In Diagnostic tab, enable the diagnostic.
19. Specify value for Perform diagnostic breakdown on X %.
20. Enable Web Page diagnostic of all relevant Vusers.

HP SiteScope

HP SiteScope is agentless monitoring software focused on monitoring the availability and performance of distributed IT infrastructures, including servers, operating systems, network and Internet services, applications and application components.

HP SiteScope tests a web page or a series of web pages using synthetic monitoring. However, it is not limited to web applications and can be used to monitor database servers (Oracle Database, Microsoft SQL Server, etc), UNIX servers, Microsoft Windows servers and many other types of hardware and software. It can export the collected data in real time to HP LoadRunner or it can be used in standalone mode. HP SiteScope collects data using agentless data collection. Using the collected data, HP SiteScope can send automated alerts and create monitoring reports showing status over time in graphical and tabular formats.

Monitors

HP SiteScope supports more than 85 types of IT infrastructure in physical and virtual environments and can monitor servers, databases, applications, networks, web transactions, streaming technology and integration technology, as well as generic elements including files, scripts and directories. HP SiteScope monitoring supports mid-tier processes, URLs, utilization of servers and response time of the mid-tier processes. Users can set thresholds for specific characteristics and be alerted for critical or warning conditions.

Solution Templates

HP SiteScope comes with 25 solution templates for monitoring IT infrastructure elements, including Oracle, Microsoft Exchange, SAP, WebLogic, and UNIX and Linux operating systems. Solution templates are for rapidly deploying specific monitoring based on best practice methodologies.

Components

The object-oriented SiteScope components fall into six broad categories: Webpage, Scheduler, Monitor, Alert, Script Alert and Reports.

• The Webpage feature displays the browser-based user interface.
• The Scheduler specifies when each monitor (such as each device or server status tracking process) runs.
• The Monitor gathers statistics for each monitored device or server.
• The Alert module sends e-mail, pager messages and SNMP alerts when SiteScope detects a problem.
• The Script Alert program can run a script, restart a background service or run an external program when a problem occurs.
• The Reports code generates Web pages that contain network statistics in a graphical or tabular format.