You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by ms...@apache.org on 2002/06/26 02:59:49 UTC
cvs commit: jakarta-jmeter/xdocs/usermanual boss.xml build-db-test-plan.xml build-ftp-test-plan.xml build-web-test-plan.xml index.xml
mstover1 2002/06/25 17:59:49
Modified: . build.xml
docs/usermanual boss.html build-db-test-plan.html
build-ftp-test-plan.html build-web-test-plan.html
index.html
src_1/org/apache/jmeter/protocol/jdbc/sampler
JDBCSampler.java
xdocs/usermanual boss.xml build-db-test-plan.xml
build-ftp-test-plan.xml build-web-test-plan.xml
index.xml
Added: docs/images/screenshots/ftptest ftp-defaults.png
ftp-defaults2.png ftp-request.png ftp-request2.png
spline-results.png threadgroup.png threadgroup2.png
docs/images/screenshots/jdbctest JDBCRequest.png
JDBCRequest2.png JDBCRequest3.png graph-results.png
threadgroup.png threadgroup2.png
Log:
Documentation updates
Revision Changes Path
1.60 +2 -2 jakarta-jmeter/build.xml
Index: build.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/build.xml,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -r1.59 -r1.60
--- build.xml 18 Jun 2002 01:32:17 -0000 1.59
+++ build.xml 26 Jun 2002 00:59:48 -0000 1.60
@@ -231,7 +231,7 @@
projectFile="./stylesheets/project.xml"
excludes="**/stylesheets/**"
includes="**/*.xml"
- lastModifiedCheck="false"
+ lastModifiedCheck="true"
velocityPropertiesFile="${docs.src}/velocity.properties"/>
<copy todir="${docs.dest}">
<fileset dir="${docs.src}">
@@ -248,7 +248,7 @@
projectFile="./stylesheets/project.xml"
excludes="**/stylesheets/**"
includes="**/*.xml"
- lastModifiedCheck="false"
+ lastModifiedCheck="true"
velocityPropertiesFile="${docs.src}/velocity.properties"/>
</target>
1.1 jakarta-jmeter/docs/images/screenshots/ftptest/ftp-defaults.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/ftptest/ftp-defaults2.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/ftptest/ftp-request.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/ftptest/ftp-request2.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/ftptest/spline-results.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/ftptest/threadgroup.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/ftptest/threadgroup2.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/jdbctest/JDBCRequest.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/jdbctest/JDBCRequest2.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/jdbctest/JDBCRequest3.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/jdbctest/graph-results.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/jdbctest/threadgroup.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/jdbctest/threadgroup2.png
<<Binary file>>
1.13 +31 -6 jakarta-jmeter/docs/usermanual/boss.html
Index: boss.html
===================================================================
RCS file: /home/cvs/jakarta-jmeter/docs/usermanual/boss.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- boss.html 30 Apr 2002 02:41:32 -0000 1.12
+++ boss.html 26 Jun 2002 00:59:49 -0000 1.13
@@ -12,7 +12,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<meta name="author" value="Martin Ramshaw">
- <meta name="email" value="$au.getAttributeValue("email")">
+ <meta name="email" value="mramshaw@alumni.concordia.ca">
<title>JMeter - User's Manual: My boss wants me to...</title>
</head>
@@ -281,7 +281,8 @@
<p >
This can be used to establish whether or not you can reach your
- target site.
+ target site. Options can be specified so that 'ping' provides the
+ same type of route reporting as 'traceroute'.
</p>
</blockquote>
@@ -291,7 +292,7 @@
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif">
- <a name="$subsection.getAttributeValue("anchor")"><strong>12.4.2 nslookup</strong></a>
+ <a name="$subsection.getAttributeValue("anchor")"><strong>12.4.2 nslookup/dig</strong></a>
</font>
</td></tr>
<tr><td>
@@ -308,7 +309,7 @@
you
</u>
may wish to avoid the overhead of DNS lookups when
- performing benchmarking/load-testing. This can be used to determine
+ performing benchmarking/load-testing. These can be used to determine
the unique address (dotted quad) of your target site.
</p>
@@ -386,7 +387,31 @@
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif">
- <a name="$subsection.getAttributeValue("anchor")"><strong>12.5.2 Microsoft WAS</strong></a>
+ <a name="$subsection.getAttributeValue("anchor")"><strong>12.5.2 HttpUnit</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <p >
+
+ This is worth a look. It is a library (and therefore of more interest to
+ developers) that can be used to perform HTTP tests/benchmarks. It is
+ intended to be used instead of a web browser (therefore no GUI) in
+ conjunction with
+ <b >
+ JUnit
+ </b>
+ .
+
+ </p>
+ </blockquote>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#828DA6">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="$subsection.getAttributeValue("anchor")"><strong>12.5.3 Microsoft WAS</strong></a>
</font>
</td></tr>
<tr><td>
@@ -405,7 +430,7 @@
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif">
- <a name="$subsection.getAttributeValue("anchor")"><strong>12.5.3 JMeter</strong></a>
+ <a name="$subsection.getAttributeValue("anchor")"><strong>12.5.4 JMeter</strong></a>
</font>
</td></tr>
<tr><td>
1.11 +370 -3 jakarta-jmeter/docs/usermanual/build-db-test-plan.html
Index: build-db-test-plan.html
===================================================================
RCS file: /home/cvs/jakarta-jmeter/docs/usermanual/build-db-test-plan.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- build-db-test-plan.html 7 Mar 2002 23:03:12 -0000 1.10
+++ build-db-test-plan.html 26 Jun 2002 00:59:49 -0000 1.11
@@ -11,7 +11,9 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
-
+ <meta name="author" value="Martin Ramshaw">
+ <meta name="email" value="mramshaw@alumni.concordia.ca">
+
<title>JMeter - User's Manual: Building a Database Test Plan</title>
</head>
@@ -68,14 +70,379 @@
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
- <a name=""><strong>7. Building a Database Test Plan</strong></a>
+ <a name="building"><strong>7. Building a Database Test Plan</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <p >
+ In this section, you will learn how to create a basic
+
+ <a href="build-test-plan.html">
+ Test Plan
+ </a>
+ to test an database server.
+You will create ten users that send five SQL requests to the database server.
+Also, you will tell the users to run their tests three times. So, the total number
+of requests is (10 users) x (2 requests) x (repeat 3 times) = 60 JDBC requests.
+To construct the Test Plan, you will use the following elements:
+
+ <a href="test_plan.html#thread_group">
+ Thread Group
+ </a>
+ ,
+
+ <a href="../usermanual/component_reference.html#JDBC_Request">JDBC Request</a>
+ ,
+ <a href="../usermanual/component_reference.html#Graph_Results">Graph Results</a>
+ .
+ </p>
+ <p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
+ <tr><td> This example uses the PostgreSQL
+ <b >
+ org.postgresql.Driver
+ </b>
+ database driver.
+To use this driver, its' containing .jar file must be copied to the extension
+.../lib/ directory (see
+ <a href="get-started.html#classpath">
+ JMeter's Classpath
+ </a>
+
+for more details). Otherwise, expect a substantial amount of stack traces when
+running this test plan.
+ </td></tr>
+ </table></p>
+ </blockquote>
+ </p>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="adding_users"><strong>7.1 Adding Users</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <p >
+ The first step you want to do with every JMeter Test Plan is to add a
+
+ <a href="test_plan.html#thread_group">
+ Thread Group
+ </a>
+ element. The Thread Group
+tells JMeter the number of users you want to simulate, how often the users should
+send requests, and the how many requests they should send.
+ </p>
+ <p >
+ Go ahead and add the ThreadGroup element by first selecting the Test Plan,
+clicking your right mouse button to get the Add menu, and then select
+Add --> ThreadGroup.
+ </p>
+ <p >
+ You should now see the Thread Group element under Test Plan. If you do not
+see the element, then "expand" the Test Plan tree by clicking on the
+Test Plan element.
+ </p>
+ <p >
+ Next, you need to modify the default properties. Select the Thread Group element
+in the tree, if you have not already selected it. You should now see the Thread
+Group Control Panel in the right section of the JMeter window (see Figure 7.1
+below)
+ </p>
+ <p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/jdbctest/threadgroup.png"><br/>
+ <font size="-1">
+Figure 7.1. Thread Group with Default Values
+ </font></td></tr></table></p>
+ <p >
+ Start by providing a more descriptive name for our Thread Group. In the name
+field, enter JDBC Users.
+ </p>
+ <p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
+ <tr><td> You will need a valid database, database table, and user-level access to that
+table. In the example shown here, the database is 'mydb' and the tables' name is
+'Stocks'.
+ </td></tr>
+ </table></p>
+ <p >
+ Next, increase the number of users (called threads) to 10.
+ </p>
+ <p >
+ In the next field, the Ramp-Up Period, leave the the default value of 0
+seconds. This property tells JMeter how long to delay between starting each
+user. For example, if you enter a Ramp-Up Period of 5 seconds, JMeter will
+finish starting all of your users by the end of the 5 seconds. So, if we have
+5 users and a 5 second Ramp-Up Period, then the delay between starting users
+would be 1 second (5 users / 5 seconds = 1 user per second). If you set the
+value to 0, then JMeter will immediately start all of your users.
+ </p>
+ <p >
+ Finally, clear the checkbox labeled "Forever", and enter a value of 3 in
+the Loop Count field. This property tells JMeter how many times to repeat your
+test. If you enter a loop count value of 0, then JMeter will run your test only
+once. To have JMeter repeatedly run your Test Plan, select the Forever
+checkbox.
+ </p>
+ <p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
+ <tr><td> In most applications, you have to manually accept
+changes you make in a Control Panel. However, in JMeter, the Control Panel
+automatically accepts your changes as you make them. If you change the
+name of an element, the tree will be updated with the new text after you
+leave the Control Panel (for example, when selecting another tree element).
+ </td></tr>
+ </table></p>
+ <p >
+ See Figure 7.2 for the completed JDBC Users Thread Group.
+ </p>
+ <p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/jdbctest/threadgroup2.png"><br/>
+ <font size="-1">
+Figure 7.2. JDBC Users Thread Group
+ </font></td></tr></table></p>
+ </blockquote>
+ </p>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="adding_requests"><strong>7.2 Adding JDBC Requests</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <p >
+ Now that we have defined our users, it is time to define the tasks that they
+will be performing. In this section, you will specify the JDBC requests to
+perform.
+ </p>
+ <p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
+ <tr><td> Although there are
+ <a href="../usermanual/component_reference.html#JDBC_Database_Connection_Pool_Defaults">JDBC Database Connection Pool Defaults</a>
+ ,
+
+ <a href="../usermanual/component_reference.html#JDBC_Database_Login_Defaults">JDBC Database Login Defaults</a>
+ , and
+
+ <a href="../usermanual/component_reference.html#JDBC_SQL_Query_Defaults">JDBC SQL Query Defaults</a>
+ components, they will not be used
+in this example.
+ </td></tr>
+ </table></p>
+ <p >
+ Begin by selecting the JDBC Users element. Click your right mouse button
+to get the Add menu, and then select Add --> Sampler --> JDBC Request.
+Then, select this new element to view its Control Panel (see Figure 7.3).
+ </p>
+ <p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/jdbctest/JDBCRequest.png"><br/>
+ <font size="-1">
+Figure 7.3. JDBC Request
+ </font></td></tr></table></p>
+ <p >
+ In our Test Plan, we will make two JDBC requests. The first one is for
+Eastman Kodak stock, and the second is Pfizer stock (obviously you should
+change these to examples appropriate for your particular database). These
+are illustrated below.
+ </p>
+ <p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
+ <tr><td> JMeter sends requests in the order that you add them to the tree.
+ </td></tr>
+ </table></p>
+ <p >
+ Start by editing the following properties (see Figure 7.4):
+
+ <ol >
+
+
+ <li >
+ Change the Name to "Kodak".
+ </li>
+
+
+ <li >
+ Enter the JDBC URL field.
+ </li>
+
+
+ <li >
+ Enter the Driver Class field.
+ </li>
+
+
+ <li >
+ Change the Number of Connections in Pool field to "1".
+ </li>
+
+
+ <li >
+ Change the Max. Usage For Each Connection field to "1".
+ </li>
+
+
+ <li >
+ Enter the Username field.
+ </li>
+
+
+ <li >
+ Enter the Password field.
+ </li>
+
+
+ <li >
+ Enter the SQL Query String field.
+ </li>
+
+
+ </ol>
+
+
+ </p>
+ <p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/jdbctest/JDBCRequest2.png"><br/>
+ <font size="-1">
+Figure 7.4. JDBC Request for Eastman Kodak stock
+ </font></td></tr></table></p>
+ <p >
+ Next, add the second JDBC Request and edit the following properties (see
+Figure 7.5):
+
+ <ol >
+
+
+ <li >
+ Change the Name to "Pfizer".
+ </li>
+
+
+ <li >
+ Enter the JDBC URL field.
+ </li>
+
+
+ <li >
+ Enter the Driver Class field.
+ </li>
+
+
+ <li >
+ Change the Number of Connections in Pool field to "1".
+ </li>
+
+
+ <li >
+ Change the Max. Usage For Each Connection field to "1".
+ </li>
+
+
+ <li >
+ Enter the Username field.
+ </li>
+
+
+ <li >
+ Enter the Password field.
+ </li>
+
+
+ <li >
+ Enter the SQL Query String field.
+ </li>
+
+
+ </ol>
+
+
+ </p>
+ <p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/jdbctest/JDBCRequest3.png"><br/>
+ <font size="-1">
+Figure 7.6. JDBC Request for Pfizer stock
+ </font></td></tr></table></p>
+ </blockquote>
+ </p>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="adding_listener"><strong>7.3 Adding a Listener to View/Store the Test Results</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <p >
+ The final element you need to add to your Test Plan is a
+
+ <a href="component_reference.html#listeners">
+ Listener
+ </a>
+ . This element is
+responsible for storing all of the results of your JDBC requests in a file
+and presenting a visual model of the data.
+ </p>
+ <p >
+ Select the JDBC Users element and add a
+ <a href="../usermanual/component_reference.html#Graph_Results">Graph Results</a>
+
+listener (Add --> Listener --> Graph Results).
+ </p>
+ <p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/jdbctest/graph-results.png"><br/>
+ <font size="-1">
+Figure 7.6. Graph results Listener
+ </font></td></tr></table></p>
+ </blockquote>
+ </p>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="saving"><strong>7.4 Saving the Test Plan</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <p >
+ Although it is not required, we recommend that you save the Test Plan to a
+file before running it. To save the Test Plan, select Save Test Plan from the
+File menu (with the latest release, it is no longer necessary to select the
+Test Plan element first).
+ </p>
+ <p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
+ <tr><td> JMeter allows you to save the entire Test Plan tree or
+only a portion of it. To save only the elements located in a particular "branch"
+of the Test Plan tree, select the Test Plan element in the tree from which to start
+the "branch", and then click your right mouse button to access the Save As menu item.
+Alternatively, select the appropriate Test Plan element and then select Save As from
+the Edit menu.
+
+ </td></tr>
+ </table></p>
+ </blockquote>
+ </p>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="running"><strong>7.5 Running the Test Plan</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p >
- To be written.
+ From the Run menu, select Run.
</p>
+ <p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
+ <tr><td> JMeter lights up a green square in the upper-right-hand corner to indicate if a
+test is currently running. The square is turned gray when all tests stop. Even after
+you select "stop", the green light will stay on until all test threads have exited.
+ </td></tr>
+ </table></p>
</blockquote>
</p>
</td></tr>
1.12 +4 -3 jakarta-jmeter/docs/usermanual/build-ftp-test-plan.html
Index: build-ftp-test-plan.html
===================================================================
RCS file: /home/cvs/jakarta-jmeter/docs/usermanual/build-ftp-test-plan.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- build-ftp-test-plan.html 19 Jun 2002 19:56:20 -0000 1.11
+++ build-ftp-test-plan.html 26 Jun 2002 00:59:49 -0000 1.12
@@ -208,9 +208,10 @@
elements which use some of the default settings you specified here.
</p>
<p >
- Begin by selecting the O'Reilly Users element. Clicking your right mouse button
+ Begin by selecting the O'Reilly Users element. Click your right mouse button
to get the Add menu, and then select Add --> Config Element --> FTP Request
Defaults. Then, select this new element to view its Control Panel (see Figure 8.3).
+
</p>
<p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/ftptest/ftp-defaults.png"><br/>
<font size="-1">
@@ -353,7 +354,7 @@
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
- <a name="adding_listener"><strong>8.4 Adding a Listener to View Store the Test Results</strong></a>
+ <a name="adding_listener"><strong>8.4 Adding a Listener to View/Store the Test Results</strong></a>
</font>
</td></tr>
<tr><td>
@@ -369,7 +370,7 @@
a visual model of the data.
</p>
<p >
- Select the Jakarta Users element and add a
+ Select the O'Reilly Users element and add a
<a href="../usermanual/component_reference.html#Spline_Visualizer">Spline Visualizer</a>
listener (Add --> Listener --> Spline Visualizer).
1.20 +7 -10 jakarta-jmeter/docs/usermanual/build-web-test-plan.html
Index: build-web-test-plan.html
===================================================================
RCS file: /home/cvs/jakarta-jmeter/docs/usermanual/build-web-test-plan.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- build-web-test-plan.html 19 Jun 2002 19:56:20 -0000 1.19
+++ build-web-test-plan.html 26 Jun 2002 00:59:49 -0000 1.20
@@ -132,16 +132,12 @@
</p>
<p >
Go ahead and add the ThreadGroup element by first selecting the Test Plan,
-and then from the Edit menu, select Add --> ThreadGroup.
+clicking your right mouse button to get the Add menu, and then select
+Add --> ThreadGroup.
</p>
- <p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
- <tr><td> You can also access the Edit menu by selecting an element
-and then clicking your right mouse button.
- </td></tr>
- </table></p>
<p >
You should now see the Thread Group element under Test Plan. If you do not
-see the element, then "expand" the Test Plan tree by double-clicking on the
+see the element, then "expand" the Test Plan tree by clicking on the
Test Plan element.
</p>
<p >
@@ -212,9 +208,10 @@
elements which use some of the default settings you specified here.
</p>
<p >
- Begin by selecting the Jakarta Users element. From the Edit menu, choose
-Add --> Config Element --> HTTP Request Defaults. Then, select this new
-element to view its Control Panel (see Figure 5.3).
+ Begin by selecting the Jakarta Users element. Click your right mouse button
+to get the Add menu, and then select Add --> Config Element --> HTTP Request
+Defaults. Then, select this new element to view its Control Panel (see Figure 5.3).
+
</p>
<p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/webtest/http-defaults1.gif"><br/>
<font size="-1">
1.23 +43 -2 jakarta-jmeter/docs/usermanual/index.html
Index: index.html
===================================================================
RCS file: /home/cvs/jakarta-jmeter/docs/usermanual/index.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- index.html 19 Jun 2002 19:56:20 -0000 1.22
+++ index.html 26 Jun 2002 00:59:49 -0000 1.23
@@ -422,7 +422,7 @@
<li >
<a href="build-web-test-plan.html#adding_listener">
- 5.5 Adding a Listener to View and Store the Test Results
+ 5.5 Adding a Listener to View/Store the Test Results
</a>
</li>
@@ -477,6 +477,47 @@
</a>
</li>
+
+ <ul >
+
+
+ <li >
+ <a href="build-db-test-plan.html#adding_users">
+ 7.1 Adding Users
+ </a>
+ </li>
+
+
+ <li >
+ <a href="build-db-test-plan.html#adding_requests">
+ 7.2 Adding JDBC Requests
+ </a>
+ </li>
+
+
+ <li >
+ <a href="build-db-test-plan.html#adding_listener">
+ 7.3 Adding a Listener to View/Store the Test Results
+ </a>
+ </li>
+
+
+ <li >
+ <a href="build-db-test-plan.html#saving">
+ 7.4 Saving the Test Plan
+ </a>
+ </li>
+
+
+ <li >
+ <a href="build-db-test-plan.html#running">
+ 7.5 Running the Test Plan
+ </a>
+ </li>
+
+
+ </ul>
+
<li >
<a href="build-ftp-test-plan.html">
@@ -511,7 +552,7 @@
<li >
<a href="build-ftp-test-plan.html#adding_listener">
- 8.4 Adding a Listener to View the Test Results
+ 8.4 Adding a Listener to View/Store the Test Results
</a>
</li>
1.11 +3 -2 jakarta-jmeter/src_1/org/apache/jmeter/protocol/jdbc/sampler/JDBCSampler.java
Index: JDBCSampler.java
===================================================================
RCS file: /home/cvs/jakarta-jmeter/src_1/org/apache/jmeter/protocol/jdbc/sampler/JDBCSampler.java,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- JDBCSampler.java 14 Jun 2002 00:12:33 -0000 1.10
+++ JDBCSampler.java 26 Jun 2002 00:59:49 -0000 1.11
@@ -231,6 +231,7 @@
res.setTime(time);
res.setResponseData(data.toString().getBytes());
res.setSamplerData(this);
+ res.setSuccessful(true);
return res;
}
1.5 +15 -6 jakarta-jmeter/xdocs/usermanual/boss.xml
Index: boss.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/boss.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- boss.xml 30 Apr 2002 02:41:32 -0000 1.4
+++ boss.xml 26 Jun 2002 00:59:49 -0000 1.5
@@ -2,7 +2,7 @@
<document>
<properties>
- <author>Martin Ramshaw</author>
+ <author email="mramshaw@alumni.concordia.ca">Martin Ramshaw</author>
<title>User's Manual: My boss wants me to...</title>
</properties>
@@ -94,14 +94,15 @@
<subsection name="12.4.1 ping">
<p>
This can be used to establish whether or not you can reach your
- target site.
+ target site. Options can be specified so that 'ping' provides the
+ same type of route reporting as 'traceroute'.
</p>
</subsection>
- <subsection name="12.4.2 nslookup">
+ <subsection name="12.4.2 nslookup/dig">
<p>
While the <u>user</u> will normally use a human-readable internet
address, <u>you</u> may wish to avoid the overhead of DNS lookups when
- performing benchmarking/load-testing. This can be used to determine
+ performing benchmarking/load-testing. These can be used to determine
the unique address (dotted quad) of your target site.
</p>
</subsection>
@@ -132,14 +133,22 @@
performance reporting.
</p>
</subsection>
- <subsection name="12.5.2 Microsoft WAS">
+ <subsection name="12.5.2 HttpUnit">
+ <p>
+ This is worth a look. It is a library (and therefore of more interest to
+ developers) that can be used to perform HTTP tests/benchmarks. It is
+ intended to be used instead of a web browser (therefore no GUI) in
+ conjunction with <b>JUnit</b>.
+ </p>
+ </subsection>
+ <subsection name="12.5.3 Microsoft WAS">
<p>
This is definitely worth a look. It has an excellent user interface
but it may not do exactly what you want. If this is the case, be aware
that the functionality of this product is not likely to change.
</p>
</subsection>
- <subsection name="12.5.3 JMeter">
+ <subsection name="12.5.4 JMeter">
<p>
If you have non-standard requirements, then this solution offers an
open-source community to provide them (of course, if you are reading
1.3 +174 -2 jakarta-jmeter/xdocs/usermanual/build-db-test-plan.xml
Index: build-db-test-plan.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/build-db-test-plan.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- build-db-test-plan.xml 6 Mar 2002 03:52:03 -0000 1.2
+++ build-db-test-plan.xml 26 Jun 2002 00:59:49 -0000 1.3
@@ -2,13 +2,185 @@
<document>
<properties>
+ <author email="mramshaw@alumni.concordia.ca">Martin Ramshaw</author>
<title>User's Manual: Building a Database Test Plan</title>
</properties>
<body>
-<section name="7. Building a Database Test Plan">
-<p>To be written.</p>
+<section name="7. Building a Database Test Plan" anchor="building">
+<p>In this section, you will learn how to create a basic
+<a href="build-test-plan.html">Test Plan</a> to test an database server.
+You will create ten users that send five SQL requests to the database server.
+Also, you will tell the users to run their tests three times. So, the total number
+of requests is (10 users) x (2 requests) x (repeat 3 times) = 60 JDBC requests.
+To construct the Test Plan, you will use the following elements:
+<a href="test_plan.html#thread_group">Thread Group</a>,
+<complink name="JDBC Request"/>, <complink name="Graph Results"/>.</p>
+
+<note>This example uses the PostgreSQL <b>org.postgresql.Driver</b> database driver.
+To use this driver, its' containing .jar file must be copied to the extension
+.../lib/ directory (see <a href="get-started.html#classpath">JMeter's Classpath</a>
+for more details). Otherwise, expect a substantial amount of stack traces when
+running this test plan.</note>
+
+</section>
+
+<section name="7.1 Adding Users" anchor="adding_users">
+<p>The first step you want to do with every JMeter Test Plan is to add a
+<a href="test_plan.html#thread_group">Thread Group</a> element. The Thread Group
+tells JMeter the number of users you want to simulate, how often the users should
+send requests, and the how many requests they should send.</p>
+
+<p>Go ahead and add the ThreadGroup element by first selecting the Test Plan,
+clicking your right mouse button to get the Add menu, and then select
+Add --> ThreadGroup.</p>
+
+<p>You should now see the Thread Group element under Test Plan. If you do not
+see the element, then "expand" the Test Plan tree by clicking on the
+Test Plan element.</p>
+
+<p>Next, you need to modify the default properties. Select the Thread Group element
+in the tree, if you have not already selected it. You should now see the Thread
+Group Control Panel in the right section of the JMeter window (see Figure 7.1
+below)</p>
+
+<figure image="../images/screenshots/jdbctest/threadgroup.png">
+Figure 7.1. Thread Group with Default Values</figure>
+
+<p>Start by providing a more descriptive name for our Thread Group. In the name
+field, enter JDBC Users.</p>
+
+<note>You will need a valid database, database table, and user-level access to that
+table. In the example shown here, the database is 'mydb' and the tables' name is
+'Stocks'.</note>
+
+<p>Next, increase the number of users (called threads) to 10.</p>
+
+<p>In the next field, the Ramp-Up Period, leave the the default value of 0
+seconds. This property tells JMeter how long to delay between starting each
+user. For example, if you enter a Ramp-Up Period of 5 seconds, JMeter will
+finish starting all of your users by the end of the 5 seconds. So, if we have
+5 users and a 5 second Ramp-Up Period, then the delay between starting users
+would be 1 second (5 users / 5 seconds = 1 user per second). If you set the
+value to 0, then JMeter will immediately start all of your users.</p>
+
+<p>Finally, clear the checkbox labeled "Forever", and enter a value of 3 in
+the Loop Count field. This property tells JMeter how many times to repeat your
+test. If you enter a loop count value of 0, then JMeter will run your test only
+once. To have JMeter repeatedly run your Test Plan, select the Forever
+checkbox.</p>
+
+<note>In most applications, you have to manually accept
+changes you make in a Control Panel. However, in JMeter, the Control Panel
+automatically accepts your changes as you make them. If you change the
+name of an element, the tree will be updated with the new text after you
+leave the Control Panel (for example, when selecting another tree element).</note>
+
+<p>See Figure 7.2 for the completed JDBC Users Thread Group.</p>
+
+<figure image="../images/screenshots/jdbctest/threadgroup2.png">
+Figure 7.2. JDBC Users Thread Group</figure>
+
+</section>
+
+<section name="7.2 Adding JDBC Requests" anchor="adding_requests">
+<p>Now that we have defined our users, it is time to define the tasks that they
+will be performing. In this section, you will specify the JDBC requests to
+perform.</p>
+
+<note>Although there are <complink name="JDBC Database Connection Pool Defaults"/>,
+<complink name="JDBC Database Login Defaults"/>, and
+<complink name="JDBC SQL Query Defaults"/> components, they will not be used
+in this example.</note>
+
+<p>Begin by selecting the JDBC Users element. Click your right mouse button
+to get the Add menu, and then select Add --> Sampler --> JDBC Request.
+Then, select this new element to view its Control Panel (see Figure 7.3).</p>
+
+<figure image="../images/screenshots/jdbctest/JDBCRequest.png">
+Figure 7.3. JDBC Request</figure>
+
+<p>In our Test Plan, we will make two JDBC requests. The first one is for
+Eastman Kodak stock, and the second is Pfizer stock (obviously you should
+change these to examples appropriate for your particular database). These
+are illustrated below.</p>
+
+<note>JMeter sends requests in the order that you add them to the tree.</note>
+
+<p>Start by editing the following properties (see Figure 7.4):
+<ol>
+<li>Change the Name to "Kodak".</li>
+<li>Enter the JDBC URL field.</li>
+<li>Enter the Driver Class field.</li>
+<li>Change the Number of Connections in Pool field to "1".</li>
+<li>Change the Max. Usage For Each Connection field to "1".</li>
+<li>Enter the Username field.</li>
+<li>Enter the Password field.</li>
+<li>Enter the SQL Query String field.</li>
+</ol>
+</p>
+
+<figure image="../images/screenshots/jdbctest/JDBCRequest2.png">
+Figure 7.4. JDBC Request for Eastman Kodak stock</figure>
+
+<p>Next, add the second JDBC Request and edit the following properties (see
+Figure 7.5):
+<ol>
+<li>Change the Name to "Pfizer".</li>
+<li>Enter the JDBC URL field.</li>
+<li>Enter the Driver Class field.</li>
+<li>Change the Number of Connections in Pool field to "1".</li>
+<li>Change the Max. Usage For Each Connection field to "1".</li>
+<li>Enter the Username field.</li>
+<li>Enter the Password field.</li>
+<li>Enter the SQL Query String field.</li>
+</ol>
+</p>
+
+<figure image="../images/screenshots/jdbctest/JDBCRequest3.png">
+Figure 7.6. JDBC Request for Pfizer stock</figure>
+
+</section>
+
+<section name="7.3 Adding a Listener to View/Store the Test Results" anchor="adding_listener">
+<p>The final element you need to add to your Test Plan is a
+<a href="component_reference.html#listeners">Listener</a>. This element is
+responsible for storing all of the results of your JDBC requests in a file
+and presenting a visual model of the data.</p>
+
+<p>Select the JDBC Users element and add a <complink name="Graph Results"/>
+listener (Add --> Listener --> Graph Results).</p>
+
+<figure image="../images/screenshots/jdbctest/graph-results.png">
+Figure 7.6. Graph results Listener</figure>
+
+</section>
+
+<section name="7.4 Saving the Test Plan" anchor="saving">
+<p>Although it is not required, we recommend that you save the Test Plan to a
+file before running it. To save the Test Plan, select Save Test Plan from the
+File menu (with the latest release, it is no longer necessary to select the
+Test Plan element first).</p>
+
+<note>JMeter allows you to save the entire Test Plan tree or
+only a portion of it. To save only the elements located in a particular "branch"
+of the Test Plan tree, select the Test Plan element in the tree from which to start
+the "branch", and then click your right mouse button to access the Save As menu item.
+Alternatively, select the appropriate Test Plan element and then select Save As from
+the Edit menu.
+</note>
+
+</section>
+
+<section name="7.5 Running the Test Plan" anchor="running">
+
+<p>From the Run menu, select Run.</p>
+
+<note>JMeter lights up a green square in the upper-right-hand corner to indicate if a
+test is currently running. The square is turned gray when all tests stop. Even after
+you select "stop", the green light will stay on until all test threads have exited.</note>
+
</section>
</body>
1.4 +5 -4 jakarta-jmeter/xdocs/usermanual/build-ftp-test-plan.xml
Index: build-ftp-test-plan.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/build-ftp-test-plan.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- build-ftp-test-plan.xml 19 Jun 2002 19:56:21 -0000 1.3
+++ build-ftp-test-plan.xml 26 Jun 2002 00:59:49 -0000 1.4
@@ -86,9 +86,10 @@
for your FTP requests. And then, in section 8.3, you will add FTP Request
elements which use some of the default settings you specified here.</p>
-<p>Begin by selecting the O'Reilly Users element. Clicking your right mouse button
+<p>Begin by selecting the O'Reilly Users element. Click your right mouse button
to get the Add menu, and then select Add --> Config Element --> FTP Request
-Defaults. Then, select this new element to view its Control Panel (see Figure 8.3).</p>
+Defaults. Then, select this new element to view its Control Panel (see Figure 8.3).
+</p>
<figure image="../images/screenshots/ftptest/ftp-defaults.png">
Figure 8.3. FTP Request Defaults</figure>
@@ -156,13 +157,13 @@
</section>
-<section name="8.4 Adding a Listener to View Store the Test Results" anchor="adding_listener">
+<section name="8.4 Adding a Listener to View/Store the Test Results" anchor="adding_listener">
<p>The final element you need to add to your Test Plan is a
<a href="component_reference.html#listeners">Listener</a>. This element is
responsible for storing all of the results of your FTP requests in a file and presenting
a visual model of the data.</p>
-<p>Select the Jakarta Users element and add a <complink name="Spline Visualizer"/>
+<p>Select the O'Reilly Users element and add a <complink name="Spline Visualizer"/>
listener (Add --> Listener --> Spline Visualizer).</p>
<figure image="../images/screenshots/ftptest/spline-results.png">
1.13 +7 -8 jakarta-jmeter/xdocs/usermanual/build-web-test-plan.xml
Index: build-web-test-plan.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/build-web-test-plan.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- build-web-test-plan.xml 19 Jun 2002 19:56:21 -0000 1.12
+++ build-web-test-plan.xml 26 Jun 2002 00:59:49 -0000 1.13
@@ -36,13 +36,11 @@
requests, and the how many requests they should send.</p>
<p>Go ahead and add the ThreadGroup element by first selecting the Test Plan,
-and then from the Edit menu, select Add --> ThreadGroup.</p>
-
-<note>You can also access the Edit menu by selecting an element
-and then clicking your right mouse button.</note>
+clicking your right mouse button to get the Add menu, and then select
+Add --> ThreadGroup.</p>
<p>You should now see the Thread Group element under Test Plan. If you do not
-see the element, then "expand" the Test Plan tree by double-clicking on the
+see the element, then "expand" the Test Plan tree by clicking on the
Test Plan element.</p>
<p>Next, you need to modify the default properties. Select the Thread Group element
@@ -91,9 +89,10 @@
for your HTTP requests. And then, in section 5.3, you will add HTTP Request
elements which use some of the default settings you specified here.</p>
-<p>Begin by selecting the Jakarta Users element. From the Edit menu, choose
-Add --> Config Element --> HTTP Request Defaults. Then, select this new
-element to view its Control Panel (see Figure 5.3).</p>
+<p>Begin by selecting the Jakarta Users element. Click your right mouse button
+to get the Add menu, and then select Add --> Config Element --> HTTP Request
+Defaults. Then, select this new element to view its Control Panel (see Figure 5.3).
+</p>
<figure image="../images/screenshots/webtest/http-defaults1.gif">
Figure 5.3. HTTP Request Defaults</figure>
1.22 +9 -2 jakarta-jmeter/xdocs/usermanual/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/index.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- index.xml 19 Jun 2002 19:56:21 -0000 1.21
+++ index.xml 26 Jun 2002 00:59:49 -0000 1.22
@@ -68,7 +68,7 @@
<li><a href="build-web-test-plan.html#adding_defaults">5.2 Adding Default HTTP Request Properties</a></li>
<li><a href="build-web-test-plan.html#adding_cookie_support">5.3 Adding Cookie Support</a></li>
<li><a href="build-web-test-plan.html#adding_requests">5.4 Adding HTTP Requests</a></li>
- <li><a href="build-web-test-plan.html#adding_listener">5.5 Adding a Listener to View and Store the Test Results</a></li>
+ <li><a href="build-web-test-plan.html#adding_listener">5.5 Adding a Listener to View/Store the Test Results</a></li>
<li><a href="build-web-test-plan.html#saving">5.6 Saving the Test Plan</a></li>
<li><a href="build-web-test-plan.html#running">5.7 Running the Test Plan</a></li>
</ul>
@@ -78,12 +78,19 @@
<li><a href="build-adv-web-test-plan.html#header_manager">6.2 Using a Header Manager</a></li>
</ul>
<li><a href="build-db-test-plan.html">7. Building a Database Test Plan</a></li>
+ <ul>
+ <li><a href="build-db-test-plan.html#adding_users">7.1 Adding Users</a></li>
+ <li><a href="build-db-test-plan.html#adding_requests">7.2 Adding JDBC Requests</a></li>
+ <li><a href="build-db-test-plan.html#adding_listener">7.3 Adding a Listener to View/Store the Test Results</a></li>
+ <li><a href="build-db-test-plan.html#saving">7.4 Saving the Test Plan</a></li>
+ <li><a href="build-db-test-plan.html#running">7.5 Running the Test Plan</a></li>
+ </ul>
<li><a href="build-ftp-test-plan.html">8. Building an FTP Test Plan</a></li>
<ul>
<li><a href="build-ftp-test-plan.html#adding_users">8.1 Adding Users</a></li>
<li><a href="build-ftp-test-plan.html#adding_defaults">8.2 Adding Default FTP Request Properties</a></li>
<li><a href="build-ftp-test-plan.html#adding_requests">8.3 Adding FTP Requests</a></li>
- <li><a href="build-ftp-test-plan.html#adding_listener">8.4 Adding a Listener to View the Test Results</a></li>
+ <li><a href="build-ftp-test-plan.html#adding_listener">8.4 Adding a Listener to View/Store the Test Results</a></li>
<li><a href="build-ftp-test-plan.html#saving">8.5 Saving the Test Plan</a></li>
<li><a href="build-ftp-test-plan.html#running">8.6 Running the Test Plan</a></li>
</ul>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>