This article describes how to test ASP.NET Web services with
the WAS tool. The WAS tool generates an artificial load on a Web server. The
purpose of the WAS tool is to:
- measure responsiveness
- test scalability
- tune performance
The WAS tool simulates requests from multiple users with Web
browsers. While ASP.NET Web services are not intended to be used by Web
browsers, ASP.NET Web services do generate browser-friendly pages. Therefore,
ASP.NET Web services can be tested by using the WAS tool. To simulate Web
service requests by using the WAS tool, follow these steps:
Simulate Web Services Requests
To simulate the Web services HTTP GET
request by using Microsoft Internet Explorer, follow these steps:
- Start Internet Explorer. In the
Address field, type the URL to your Web services (.asmx) file.
For example, a Web service that is named WebServiceTest with a .asmx file that is named MyWebService must be identified with the URL
Type this URL and then click Go.
- The ASP.NET Web service generates a browser-friendly page
that describes the methods that are available in the Web service. Click the
method that you want to issue a request to.
- The Web service generates another browser-friendly page
with a detailed description of the method that you select. Scroll down to view
sample requests and responses in all available Web service
- At the top of the page, type the parameters that are
requested. Skip this step if no parameters are requested
- Click Invoke to issue an HTTP GET request to the Web service.
Internet Explorer opens a
new window and then issues the request. The Web service responds by returning
an XML file that is displayed by Internet Explorer. Note the URL that appears
in the address bar of the browser. The path that is shown after the hostname in
the URL identifies the Web service and includes all parameters that are passed
to the Web service.
Configure the Web Application Stress (WAS) Tool for Web Services
Because ASP.NET Web services can communicate with a browser, this
enables the WAS tool to issue Web service requests to ASP.NET.
create a WAS script to simulate Web service methods, follow these steps:
- In the WAS tool, create a new WAS database.
- To create a new script, on the Scripts
menu, point to Create and then click Manual.
A new, blank script is created.
- In the right pane, type the hostname of the ASP.NET server
in the Server field.
This name is the hostname of
the ASP.NET server that hosts the Web service.
- In the script grid, create a new grid item. To do this,
select GET from the Verb drop-down list box
on the first blank line.
- In the Path text box, type the absolute
path of the Web service. This path must not include the http:// prefix or the hostname.
For example, to issue a request
to a Web service that is named WebServiceTest, with a .asmx file that is named MyWebService, a method that is named HelloWorld, and the single parameter cycles with a value of
3, type the path:
- Repeat step 4 and step 5 to add additional Web service
You may have to adjust the settings.
- On the Scripts menu, click
- After the script completes, on the View
menu, click Reports to view the results.
For more information about deploying applications, visit the following Microsoft Web sites:
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
HOW TO: Tune and Scale Performance of Applications That Are Built on the .NET Framework
Article ID: 815160 - Last Review: July 31, 2012 - Revision: 2.0
- Microsoft ASP.NET 1.0
- Microsoft ASP.NET 1.1
|kbwebservices kbconfig kbweb kbhowtomaster KB815160|