mstover1 02/02/21 05:43:07
Modified: xdocs/usermanual build-test-plan.xml gen-controller.xml
glossary.xml index.xml thread-group.xml
Added: xdocs/usermanual component_reference.xml
Log:
Updating documentation
Revision Changes Path
1.2 +33 -3 jakarta-jmeter/xdocs/usermanual/build-test-plan.xml
Index: build-test-plan.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/build-test-plan.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- build-test-plan.xml 28 Oct 2001 13:22:50 -0000 1.1
+++ build-test-plan.xml 21 Feb 2002 13:43:07 -0000 1.2
@@ -8,15 +8,45 @@
<body>
<section name="3. Building a Test Plan">
+<p>A test plan describes a series of steps JMeter will execute when run. A complete
+test plan will consiste of one or more Thread Groups, logic conrollers, sample
generating
+controllers, listeners, timers, assertions, and configuration elements.
+</p>
</section>
-<section name="3.1 Adding and Removing Elements">
+<section name="3.1 Adding and Removing Elements" anchor="add_remove">
+<p>Adding elements to a test plan can be done by right-clicking on an element in the
+tree, and choosing a new element from the "add" list. Alternatively, elements can
+be loaded from file and added by choosing the "open" option. </p>
+
+<p>Every element will only allow you to add appropriate types of elements.</p>
+<p>To remove an element, make sure the element is selected, right-click on the
element,
+and choose the "remove" option.</p>
+</section>
+
+<section name="3.2 Loading and Saving Elements" anchor="load_save">
+<p>To load an element from file, right click on the existing tree element to which
+you want to add the loaded element, and select the "open" option. Choose the file
where
+your elements are saved. JMeter will load the elements into the tree.</p>
+
+<p>To save tree elements, right click on an element and choose the "save" option.
+JMeter will save the element selected, plus all child elements beneath it. In this
way,
+you can save test tree fragments, individual elements, or the entire test plan.</p>
</section>
-<section name="3.2 Loading and Saving Elements">
+<section name="3.3 Configuring Tree Elements" anchor="config_element">
+<p>Any element in the test tree will present controls in JMeter's right-hand frame.
These
+controls allow you to configure the behavior of that particular test element. What
can be
+configured for an element depends on what type of element it is.</p>
</section>
-<section name="3.3 Running a Test Plan">
+<section name="3.4 Running a Test Plan" anchor="run">
+<p>To run your test plan, choose "start" from the "run" menu item. To stop your
test
+plan, choose "stop" from the same menu. JMeter does not automatically give any
+indication of whether it is currently running. Some listeners make it obvious if
+JMeter is running, but the only way to be sure is to check the "run" menu. If
"start"
+is disabled, and "stop" is enabled, JMeter is running your test plan (or, at least,
it
+thinks it is).</p>
</section>
1.7 +8 -169 jakarta-jmeter/xdocs/usermanual/gen-controller.xml
Index: gen-controller.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/gen-controller.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- gen-controller.xml 19 Nov 2001 17:46:42 -0000 1.6
+++ gen-controller.xml 21 Feb 2002 13:43:07 -0000 1.7
@@ -11,11 +11,11 @@
<p>Generative Controllers tell JMeter to send requests to a server. JMeter
currently has three such controllers: FTP Request, HTTP Request, and JDBC
-request. Each controller has several properties you can set. You can further
+request. Each controller has several properties you can set. You can further
customize a controller by adding one or more Configuration Elements to it.
Also, note that JMeter sends requests in the order that you add them to the
tree.</p>
-<p>If you are going to send multiple requests of the same type (for example,
+<p>If you are going to send multiple requests of the same type (for example,
HTTP Request) to the same server, consider using a Defaults Configuration
Element. Each controller has its own Defaults element (see below). </p>
@@ -23,178 +23,17 @@
results of your requests to disk.</p>
<p>If your are interested in having JMeter perform basic validation on
-the response of your request, add an <a href="assertion.html">Assertion</a> to
-the Request controller. For example, in stress testing a web application, the
server
-may return a successful "HTTP Response" code, but the page may have errors on it or
-may be missing sections. You could add assertions to check for certain HTML tags,
-common error strings, and so on. JMeter lets you create these assertions using
"regular
-expressions".</p>
+the response of your request, add an <a href="assertion.html">Assertion</a> to
+the Request controller. For example, in stress testing a web application, the
server
+may return a successful "HTTP Response" code, but the page may have errors on it or
+may be missing sections. You could add assertions to check for certain HTML tags,
+common error strings, and so on. JMeter lets you create these assertions using
regular
+expressions.</p>
</section>
-<section name="4.2.1.1 FTP Request" anchor="ftp_request">
-<p>This controller lets you send an FTP "retrieve file" request to an FTP server.
-If you are going to send multiple requests to the same FTP server, consider
-using a <a href="ftp-config.html#request_defaults">FTP Request Defaults</a>
Configuration
-Element so you do not have to enter the same information for each FTP Request
Generative
-Controller. </p>
-<p><img src="../images/screenshots/gen-controller/ftp-request.gif" width="407"
height="238"></img></p>
-<p><b>Property Descriptions:</b>
-<ul>
- <li><b>Name</b> - Descriptive name for this controller that is shown in the tree.
</li>
- <li><b>Server Name or IP</b> - Domain name or IP address of the FTP server.
-JMeter assumes the FTP server is listening on the default port.</li>
- <li><b>File to Retrieve From Server</b> - Path and name of the file to
retrieve.</li>
- <li><i>Login Configuration</i></li>
- <ul>
- <li><b>Username</b> - FTP account username.</li>
- <li><b>Password</b> - FTP account password.</li>
- </ul>
-</ul>
-</p>
-
-<p><b>See Also:</b>
-<br></br><a href="assertion.html">Assertion</a>,
-<a href="ftp-config.html#request_defaults">FTP Request Defaults</a>,
-<a href="build-ftp-test-plan.html">Building an FTP Test Plan</a></p>
-</section>
-
-<section name="4.2.1.2 HTTP Request" anchor="http_request">
-<p>This controller lets you send an HTTP/HTTPS request to a web server. It
-also lets you control whether or not JMeter parses HTML files for images and
-Java applets and sends HTTP requests to retrieve them.</p>
-<p>If you are going to send multiple requests to the same web server, consider
-using an <a href="http-config.html#request_defaults">HTTP Request Defaults</a>
-Configuration Element so you do not have to enter the same information for each
-HTTP Request controller.</p>
-<p>Or, instead of manually adding HTTP Request controllers, you may want to use
-JMeter's <a href="http-config.html#proxy_server">HTTP Proxy Server</a> to create
-them. This can save you time if you have a lot of HTTP requests or requests with
many
-parameters.</p>
-<p>If the request requires a login authorization, you will also have to add an
-<a href="http-config.html#auth_manager">HTTP Authorization Manager</a>
-Configuration Element. And, if the request uses cookies, then you will also need an
-<a href="http-config.html#cookie_manager">HTTP Cookie Manager</a>. You can
-add either of these elements to the Thread Group or the HTTP Request. If you have
-more than one HTTP Request that needs authorizations or cookies, then add the
-elements to the Thread Group. That way, all HTTP Request controllers will share
the
-same Authorization Manager and Cookie Manager elements.</p>
-<p>If the request uses a technique called "URL Rewriting" to maintain sessions,
-then see section
-<a href="build-adv-web-test-plan.html#url_rewriting">6.x HTTP Requests and Session
ID's: URL Rewriting</a>
-for additional configuration steps.</p>
-<p><img src="../images/screenshots/gen-controller/http-request.gif" width="562"
height="635"></img></p>
-<p><b>Property Descriptions:</b>
-<ul>
- <li><b>Name</b> - Descriptive name for this controller that is shown in the tree.
</li>
- <li><i>Web Server</i></li>
- <ul>
- <li><b>Server</b> - Domain name or IP address of the web server.</li>
- <li><b>Port</b> - (optional) Port the web server is listening. If you leave
this field
-empty, JMeter assumes the default port.</li>
- </ul>
- <li><i>HTTP Request</i></li>
- <ul>
- <li><b>Protocol</b> - HTTP or HTTPS.</li>
- <li><b>Method</b> - HTTP GET or HTTP POST.</li>
- <li><b>Path</b> - The path to resource (for example, /servlets/myServlet). If
the
-resource requires query string parameters, add them below in the
-"Send Parameters With the Request" section.</li>
- <li><i>Send Parameters With the Request</i></li>
- <ul>
- <li><b>Name</b> - Parameter name</li>
- <li><b>Value</b> - Parameter value. You do not have to enter the value in
-URL-Encoded format. JMeter will URL-Encode it for you when it sends
-the HTTP request.</li>
- <li><b>Add</b> Button - Add a parameter.</li>
- <li><b>Delete</b> Button - Delete the currently selected parameter.</li>
- </ul>
- <li><i>Send a File With the Request</i></li>
- <ul>
- <li><b>Filename</b> - Name of the file to send.</li>
- <li><b>Browse</b> Button - Select this button to browse the file system for a
-filename.</li>
- <li><b>Parameter Name</b> - Name of the parameter.</li>
- <li><b>MIME Type</b> - MIME type (for example, text/plain).</li>
- </ul>
- </ul>
- <li><i>Optional Tasks</i></li>
- <ul>
- <li><b>Retrieve All Images and Java Applets</b> - Tell JMeter to parse the HTML
file
-and send HTTP/HTTPS requests for all images and Java applets referenced in the
file.</li>
- </ul>
-</ul>
-</p>
-
-<p><b>See Also:</b>
-<br></br>
-<a href="assertion.html">Assertion</a>,
-<a href="build-web-test-plan.html">Building a Web Test Plan</a>,
-<a href="build-adv-web-test-plan.html">Building an Advanced Web Test Plan</a>,
-<a href="http-config.html#auth_manager">HTTP Authorization Manager</a>,
-<a href="http-config.html#cookie_manager">HTTP Cookie Manager</a>,
-<a href="http-config.html#header_manager">HTTP Header Manager</a>,
-<a href="http-config.html#html_link_parser">HTTP HTML Link Parser</a>,
-<a href="http-config.html#proxy_server">HTTP Proxy Server</a>,
-<a href="http-config.html#request_defaults">HTTP Request Defaults</a>,
-<a href="build-adv-web-test-plan.html#url_rewriting">HTTP Requests and Session
ID's: URL Rewriting</a>
-</p>
-
-</section>
-
-<section name="4.2.1.3 JDBC Request" anchor="jdbc_request">
-<p>This controller lets you send an JDBC Request (an SQL query) to a database.</p>
-<p>If you are going to send multiple requests to the same database, consider
-using one or more of the Defaults Configuration Elements:
-<a href="jdbc-config.html#login">Login</a>,
-<a href="jdbc-config.html#conn_pool">Connection Pool</a>,
-<a href="jdbc-config.html#sql_query">SQL Query</a>.
-This way, you do not have to enter the same information for each JDBC Request
-controller.</p>
-<p><img src="../images/screenshots/gen-controller/jdbc-request.gif" width="466"
height="454"></img></p>
-
-<p><b>Property Descriptions:</b>
-<ul>
- <li><b>Name</b> - Descriptive name for this controller that is shown in the tree.
</li>
- <li><i>Database URL and JDBC Driver</i></li>
- <ul>
- <li><b>JDBC URL</b> - URL of the database (for example,
-"jdbc:weblogic:oracle"). Refer to your database's JDBC documentation for the
-URL you should use.</li>
- <li><b>Driver Class</b> - The database driver Java class (for example,
-"weblogic.jdbc.oci.Driver"). Refer to your database's JDBC documentation for
-the name of the JDBC driver class you should use.</li>
- </ul>
- <li><i>Login Configuration</i></li>
- <ul>
- <li><b>Username</b> - FTP account username.</li>
- <li><b>Password</b> - FTP account password.</li>
- </ul>
- <li><i>Database Connection Pool</i></li>
- <ul>
- <li><b>Number of Connections in Pool</b> - Number of database connection
-instances to create and keep active. The maximum value depends on your database.
-Also, JMeter imposes a maximum of 100 connections.</li>
- <li><b>Max Usage For Each Connection</b> - Maximum number of times JMeter
-uses a database connection instance before recycling it (destroying and creating
-a new instance).</li>
- </ul>
- <li><b>SQL Query String</b> - SQL query (for example, "select * from
t_customers").</li>
-</ul>
-</p>
-
-<p><b>See Also:</b>
-<br></br>
-<a href="assertion.html">Assertion</a>,
-<a href="build-db-test-plan.html">Building a Database Test Plan</a>,
-<a href="jdbc-config.html#login">JDBC Database Login Defaults</a>,
-<a href="jdbc-config.html#conn_pool">JDBC Database Connection Pool Defaults</a>,
-<a href="jdbc-config.html#sql_query">JDBC SQL Query Defaults</a>
-</p>
-
-</section>
</body>
</document>
1.2 +1 -1 jakarta-jmeter/xdocs/usermanual/glossary.xml
Index: glossary.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/glossary.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- glossary.xml 28 Oct 2001 13:22:50 -0000 1.1
+++ glossary.xml 21 Feb 2002 13:43:07 -0000 1.2
@@ -7,7 +7,7 @@
<body>
-<section name="12. Glossary">
+<section name="13. Glossary">
</section>
</body>
1.7 +109 -107 jakarta-jmeter/xdocs/usermanual/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/index.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- index.xml 20 Feb 2002 14:34:55 -0000 1.6
+++ index.xml 21 Feb 2002 13:43:07 -0000 1.7
@@ -11,118 +11,119 @@
<li><a href="intro.html">1. Introduction</a></li>
<li><a href="get-started.html">2. Getting Started</a></li>
<ul>
- <li><a href="get-started.html#requirements">2.1 Requirements</a></li>
- <ul>
- <li><a href="get-started.html#java_versions">2.1.1 Java Version</a></li>
- <li><a href="get-started.html#os">2.1.2 Operating Systems<!--: any (has been
tested on Windows 98, ...)--></a></li>
- </ul>
- <li><a href="get-started.html#optional">2.2 Optional</a></li>
- <ul>
- <li><a href="get-started.html#opt_compiler">2.2.1 Java Compiler</a></li>
- <li><a href="get-started.html#opt_sax">2.2.2 SAX XML Parser</a></li>
- <li><a href="get-started.html#opt_email">2.2.3 Email Support</a></li>
- <li><a href="get-started.html#opt_ssl">2.2.4 SSL Encryption</a></li>
- <li><a href="get-started.html#opt_jdbc">2.2.5 JDBC Driver</a></li>
- </ul>
- <li><a href="get-started.html#install">2.3 Installation</a></li>
- <ul>
- <li><a href="get-started.html#download_release">2.3.1 Downloading the Latest
Release</a></li>
- <li><a href="get-started.html#download_nightly">2.3.2 Downloading Nightly
Builds</a></li>
- </ul>
- <li><a href="get-started.html#running">2.4 Running JMeter</a></li>
- <ul>
- <li><a href="get-started.html#classpath">2.4.1 JMeter's Classpath</a></li>
- <li><a href="get-started.html#proxy_server">2.4.2 Using a Proxy
Server</a></li>
- <li><a href="get-started.html#non_gui">2.4.3 Non-GUI Mode</a></li>
- </ul>
+ <li><a href="get-started.html#requirements">2.1 Requirements</a></li>
+ <ul>
+ <li><a href="get-started.html#java_versions">2.1.1 Java
Version</a></li>
+ <li><a href="get-started.html#os">2.1.2 Operating Systems<!--: any
(has been tested on Windows 98, ...)--></a></li>
+ </ul>
+ <li><a href="get-started.html#optional">2.2 Optional</a></li>
+ <ul>
+ <li><a href="get-started.html#opt_compiler">2.2.1 Java
Compiler</a></li>
+ <li><a href="get-started.html#opt_sax">2.2.2 SAX XML Parser</a></li>
+ <li><a href="get-started.html#opt_email">2.2.3 Email Support</a></li>
+ <li><a href="get-started.html#opt_ssl">2.2.4 SSL Encryption</a></li>
+ <li><a href="get-started.html#opt_jdbc">2.2.5 JDBC Driver</a></li>
+ </ul>
+ <li><a href="get-started.html#install">2.3 Installation</a></li>
+ <ul>
+ <li><a href="get-started.html#download_release">2.3.1 Downloading the
Latest Release</a></li>
+ <li><a href="get-started.html#download_nightly">2.3.2 Downloading
Nightly Builds</a></li>
+ </ul>
+ <li><a href="get-started.html#running">2.4 Running JMeter</a></li>
+ <ul>
+ <li><a href="get-started.html#classpath">2.4.1 JMeter's
Classpath</a></li>
+ <li><a href="get-started.html#proxy_server">2.4.2 Using a Proxy
Server</a></li>
+ <li><a href="get-started.html#non_gui">2.4.3 Non-GUI Mode</a></li>
+ </ul>
</ul>
<li><a href="build-test-plan.html">3. Building a Test Plan</a></li>
<ul>
- <li><a href="build-test-plan.html#add_remove">3.1 Adding and Removing
Elements</a></li>
- <li><a href="build-test-plan.html#load_save">3.2 Loading and Saving
Elements</a></li>
- <li><a href="build-test-plan.html#run">3.3 Running a Test Plan</a></li>
+ <li><a href="build-test-plan.html#add_remove">3.1 Adding and Removing
Elements</a></li>
+ <li><a href="build-test-plan.html#load_save">3.2 Loading and Saving
Elements</a></li>
+ <li><a href="build-test-plan.html#config_element">3.3 Configuring Tree
Elements</a></li>
+ <li><a href="build-test-plan.html#run">3.3 Running a Test Plan</a></li>
</ul>
<li><a href="elements-test-plan.html">4. Elements of a Test Plan</a></li>
<ul>
- <li><a href="thread-group.html">4.1 Thread Group</a></li>
- <li><a href="controller.html">4.2 Controllers</a></li>
- <ul>
- <li><a href="gen-controller.html">4.2.1 Generative Controllers</a></li>
- <ul>
- <li><a href="gen-controller.html#ftp_request">4.2.1.1 FTP Request</a></li>
- <li><a href="gen-controller.html#http_request">4.2.1.2 HTTP Request</a></li>
- <li><a href="gen-controller.html#jdbc_request">4.2.1.3 JDBC Request</a></li>
- </ul>
- <li><a href="logic-controller.html">4.2.2 Logic Controllers</a></li>
- <ul>
- <li><a href="logic-controller.html#interleave">4.2.2.1 Interleave
Controller</a></li>
- <li><a href="logic-controller.html#loop">4.2.2.2 Loop Controller</a></li>
- <li><a href="logic-controller.html#mod_manager">4.2.2.3 Modification
Manager</a></li>
- <li><a href="logic-controller.html#once_only">4.2.2.4 Once Only
Controller</a></li>
- <li><a href="logic-controller.html#simple">4.2.2.5 Simple
Controller</a></li>
- </ul>
- </ul>
- <li><a href="listener.html">4.3 Listeners</a></li>
- <ul>
- <li><a href="listener.html#graph">4.3.1 Graphs</a></li>
- <ul>
- <li><a href="listener.html#view_graph_tree">4.3.1.1 View Graph Tree</a></li>
- <li><a href="listener.html#graph_full_results">4.3.1.2 Graph Full
Results</a></li>
- <li><a href="listener.html#graph_results">4.3.1.3 Graph Results</a></li>
- <li><a href="listener.html#spline">4.3.1.4 Spline Visualizer</a></li>
- </ul>
- <li><a href="listener.html#managers">4.3.2 Managers</a></li>
- <ul>
- <li><a href="listener.html#mod_manager">4.3.2.1 Modification
Manager</a></li>
- </ul>
- <li><a href="listener.html#misc">4.3.3 Miscellaneous</a></li>
- <ul>
- <li><a href="listener.html#assertion_results">4.3.3.1 Assertion
Results</a></li>
- <li><a href="listener.html#file_reporter">4.3.3.2 File Reporter</a></li>
- <li><a href="listener.html#view_results">4.3.3.3 View Results</a></li>
- <li><a href="listener.html#view_results_tree">4.3.3.4 View Result
Tree</a></li>
- </ul>
- </ul>
- <li><a href="timer.html">4.4 Timers</a></li>
- <ul>
- <li><a href="timer.html#constant">4.4.1 Constant Timer</a></li>
- <li><a href="timer.html#gaussian">4.4.2 Gaussian Random Timer</a></li>
- <li><a href="timer.html#uniform">4.4.3 Uniform Random Timer</a></li>
- </ul>
-
- <li><a href="assertion.html">4.5 Assertions</a></li>
-
- <li><a href="ftp-config.html">4.6 FTP Configuration Elements</a></li>
- <ul>
- <li><a href="ftp-config.html#request_defaults">4.6.1 FTP Request
Defaults</a></li>
- </ul>
-
- <li><a href="http-config.html">4.7 HTTP Configuration Elements</a></li>
- <ul>
- <li><a href="http-config.html#auth_manager">4.7.1 HTTP Authorization
Manager</a></li>
- <li><a href="http-config.html#cookie_manager">4.7.2 HTTP Cookie
Manager</a></li>
- <li><a href="http-config.html#header_manager">4.7.3 HTTP Header
Manager</a></li>
- <li><a href="http-config.html#proxy_server">4.7.4 HTTP Proxy Server</a></li>
- <li><a href="http-config.html#request_defaults">4.7.5 HTTP Request
Defaults</a></li>
- </ul>
-
- <li><a href="jdbc-config.html">4.8 JDBC Configuration Elements</a></li>
- <ul>
- <li><a href="jdbc-config.html#conn_pool">4.8.1 JDBC Database Connection Pool
Defaults</a></li>
- <li><a href="jdbc-config.html#login">4.8.2 JDBC Database Login
Defaults</a></li>
- <li><a href="jdbc-config.html#sql_query">4.8.3 JDBC SQL Query
Defaults</a></li>
- </ul>
+ <li><a href="thread-group.html">4.1 Thread Group</a></li>
+ <li><a href="controller.html">4.2 Controllers</a></li>
+ <ul>
+ <li><a href="gen-controller.html">4.2.1 Generative Controllers</a></li>
+ <ul>
+ <li><a href="gen-controller.html#ftp_request">4.2.1.1 FTP
Request</a></li>
+ <li><a href="gen-controller.html#http_request">4.2.1.2 HTTP
Request</a></li>
+ <li><a href="gen-controller.html#jdbc_request">4.2.1.3 JDBC
Request</a></li>
+ </ul>
+ <li><a href="logic-controller.html">4.2.2 Logic Controllers</a></li>
+ <ul>
+ <li><a href="logic-controller.html#interleave">4.2.2.1 Interleave
Controller</a></li>
+ <li><a href="logic-controller.html#loop">4.2.2.2 Loop
Controller</a></li>
+ <li><a href="logic-controller.html#mod_manager">4.2.2.3 Modification
Manager</a></li>
+ <li><a href="logic-controller.html#once_only">4.2.2.4 Once Only
Controller</a></li>
+ <li><a href="logic-controller.html#simple">4.2.2.5 Simple
Controller</a></li>
+ </ul>
+ </ul>
+ <li><a href="listener.html">4.3 Listeners</a></li>
+ <ul>
+ <li><a href="listener.html#graph">4.3.1 Graphs</a></li>
+ <ul>
+ <li><a href="listener.html#view_graph_tree">4.3.1.1 View Graph
Tree</a></li>
+ <li><a href="listener.html#graph_full_results">4.3.1.2 Graph Full
Results</a></li>
+ <li><a href="listener.html#graph_results">4.3.1.3 Graph
Results</a></li>
+ <li><a href="listener.html#spline">4.3.1.4 Spline Visualizer</a></li>
+ </ul>
+ <li><a href="listener.html#managers">4.3.2 Managers</a></li>
+ <ul>
+ <li><a href="listener.html#mod_manager">4.3.2.1 Modification
Manager</a></li>
+ </ul>
+ <li><a href="listener.html#misc">4.3.3 Miscellaneous</a></li>
+ <ul>
+ <li><a href="listener.html#assertion_results">4.3.3.1 Assertion
Results</a></li>
+ <li><a href="listener.html#file_reporter">4.3.3.2 File
Reporter</a></li>
+ <li><a href="listener.html#view_results">4.3.3.3 View
Results</a></li>
+ <li><a href="listener.html#view_results_tree">4.3.3.4 View Result
Tree</a></li>
+ </ul>
+ </ul>
+ <li><a href="timer.html">4.4 Timers</a></li>
+ <ul>
+ <li><a href="timer.html#constant">4.4.1 Constant Timer</a></li>
+ <li><a href="timer.html#gaussian">4.4.2 Gaussian Random Timer</a></li>
+ <li><a href="timer.html#uniform">4.4.3 Uniform Random Timer</a></li>
+ </ul>
+
+ <li><a href="assertion.html">4.5 Assertions</a></li>
+
+ <li><a href="ftp-config.html">4.6 FTP Configuration Elements</a></li>
+ <ul>
+ <li><a href="ftp-config.html#request_defaults">4.6.1 FTP Request
Defaults</a></li>
+ </ul>
+
+ <li><a href="http-config.html">4.7 HTTP Configuration Elements</a></li>
+ <ul>
+ <li><a href="http-config.html#auth_manager">4.7.1 HTTP Authorization
Manager</a></li>
+ <li><a href="http-config.html#cookie_manager">4.7.2 HTTP Cookie
Manager</a></li>
+ <li><a href="http-config.html#header_manager">4.7.3 HTTP Header
Manager</a></li>
+ <li><a href="http-config.html#proxy_server">4.7.4 HTTP Proxy
Server</a></li>
+ <li><a href="http-config.html#request_defaults">4.7.5 HTTP Request
Defaults</a></li>
+ </ul>
+
+ <li><a href="jdbc-config.html">4.8 JDBC Configuration Elements</a></li>
+ <ul>
+ <li><a href="jdbc-config.html#conn_pool">4.8.1 JDBC Database
Connection Pool Defaults</a></li>
+ <li><a href="jdbc-config.html#login">4.8.2 JDBC Database Login
Defaults</a></li>
+ <li><a href="jdbc-config.html#sql_query">4.8.3 JDBC SQL Query
Defaults</a></li>
+ </ul>
</ul>
<li><a href="build-web-test-plan.html">5. Building a Web Test Plan</a></li>
- <ul>
- <li><a href="build-web-test-plan.htm#adding_users">5.1 Adding Users</a></li>
- <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_requests">5.3 Adding HTTP
Requests</a></li>
- <li><a href="build-web-test-plan.html#adding_file_reporter">5.4 Adding a File
Reporter to Store the Test Results</a></li>
- <li><a href="build-web-test-plan.html#saving">5.5 Saving the Test
Plan</a></li>
- <li><a href="build-web-test-plan.html#running">5.6 Running the Test
Plan</a></li>
- </ul>
+ <ul>
+ <li><a href="build-web-test-plan.htm#adding_users">5.1 Adding
Users</a></li>
+ <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_requests">5.3 Adding HTTP
Requests</a></li>
+ <li><a href="build-web-test-plan.html#adding_file_reporter">5.4 Adding
a File Reporter to Store the Test Results</a></li>
+ <li><a href="build-web-test-plan.html#saving">5.5 Saving the Test
Plan</a></li>
+ <li><a href="build-web-test-plan.html#running">5.6 Running the Test
Plan</a></li>
+ </ul>
<li><a href="build-adv-web-test-plan.html">6. Building an Advanced Web Test
Plan</a></li>
<li><a href="build-db-test-plan.html">7. Building a Database Test Plan</a></li>
@@ -130,12 +131,13 @@
<li><a href="remote-test.html">9. Remote Testing</a></li>
<li><a href="best-practices.html">10. Best Practices</a></li>
<ul>
- <li><a href="best-practices.html#limit_threads">10.1 [ALL] Limit the Number of
Threads</a></li>
- <li><a href="best-practices.html#put_cookie_manager">10.2 [HTTP] Where to Put
the Cookie Manager</a></li>
- <li><a href="best-practices.html#put_auth_manager">10.3 [HTTP] Where to Put the
Authorization Manager</a></li>
+ <li><a href="best-practices.html#limit_threads">10.1 [ALL] Limit the Number
of Threads</a></li>
+ <li><a href="best-practices.html#put_cookie_manager">10.2 [HTTP] Where to Put
the Cookie Manager</a></li>
+ <li><a href="best-practices.html#put_auth_manager">10.3 [HTTP] Where to Put
the Authorization Manager</a></li>
</ul>
<li><a href="boss.html">11. Help! My boss wants me to load test our web
app!</a></li>
- <li><a href="glossary.html">12. Glossary</a></li>
+ <li><a href="component_reference.html">12. Component Reference</a></li>
+ <li><a href="glossary.html">13. Glossary</a></li>
</ul>
</section>
1.2 +23 -2 jakarta-jmeter/xdocs/usermanual/thread-group.xml
Index: thread-group.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/thread-group.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- thread-group.xml 14 Nov 2001 14:54:22 -0000 1.1
+++ thread-group.xml 21 Feb 2002 13:43:07 -0000 1.2
@@ -8,8 +8,29 @@
<body>
<section name="4.1 ThreadGroup">
-<p>Put description text here...</p>
+<p>Thread group elements are the beginning points of any test plan. All elements
+of a test plan must be under a thread group. As the name implies, the thread group
+element controls the number of threads JMeter will use to execute your test. The
+controls for a thread group allow you to:
+<ul><li> set the number of threads</li>
+<li>Set the ramp-up period</li>
+<li>Set the number of times to execute the test</li>
+</ul></p>
+
+<p>Each thread will execute the test plan in its entirety, and completely
independent
+of other test threads. Using multiple threads is used to simulate concurrent
connections
+to your server application.</p>
+
+<p>The ramp-up period tells JMeter how slowly to "ramp-up" to the full number of
+threads chosen. If 10 threads are used, and the ramp-up period is 100 seconds, then
+JMeter will take 100 seconds to get all 10 threads up and running. Each thread will
+start 10 (100/10) seconds after the previous thread was begun. If there are 30
threads
+and a ramp-up period of 120 seconds, then each successive thread will be delayed by
4 seconds.</p>
+
+<p>By default, a thread group is configured to loop indefinitely through its
elements.
+Alternatively, you can set the number of times the thread group will loop before
ending. If the number
+is set at one, then JMeter will execute the test only once before stopping.</p>
</section>
</body>
-</document>
+</document>
\ No newline at end of file
1.1 jakarta-jmeter/xdocs/usermanual/component_reference.xml
Index: component_reference.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>User's Manual: Generative Controllers</title>
</properties>
<body>
<section name="12. Component Reference">
</section>
<section name="4.2.1.1 FTP Request" anchor="ftp_request">
<p>This controller lets you send an FTP "retrieve file" request to an FTP server.
If you are going to send multiple requests to the same FTP server, consider
using a <a href="ftp-config.html#request_defaults">FTP Request Defaults</a>
Configuration
Element so you do not have to enter the same information for each FTP Request
Generative
Controller. </p>
<p><img src="../images/screenshots/gen-controller/ftp-request.gif" width="407"
height="238"></img></p>
<p><b>Property Descriptions:</b>
<ul>
<li><b>Name</b> - Descriptive name for this controller that is shown in the tree.
</li>
<li><b>Server Name or IP</b> - Domain name or IP address of the FTP server.
JMeter assumes the FTP server is listening on the default port.</li>
<li><b>File to Retrieve From Server</b> - Path and name of the file to
retrieve.</li>
<li><i>Login Configuration</i></li>
<ul>
<li><b>Username</b> - FTP account username.</li>
<li><b>Password</b> - FTP account password.</li>
</ul>
</ul>
</p>
<p><b>See Also:</b>
<br></br><a href="assertion.html">Assertion</a>,
<a href="ftp-config.html#request_defaults">FTP Request Defaults</a>,
<a href="build-ftp-test-plan.html">Building an FTP Test Plan</a></p>
</section>
<section name="4.2.1.2 HTTP Request" anchor="http_request">
<p>This controller lets you send an HTTP/HTTPS request to a web server. It
also lets you control whether or not JMeter parses HTML files for images and
Java applets and sends HTTP requests to retrieve them.</p>
<p>If you are going to send multiple requests to the same web server, consider
using an <a href="http-config.html#request_defaults">HTTP Request Defaults</a>
Configuration Element so you do not have to enter the same information for each
HTTP Request controller.</p>
<p>Or, instead of manually adding HTTP Request controllers, you may want to use
JMeter's <a href="http-config.html#proxy_server">HTTP Proxy Server</a> to create
them. This can save you time if you have a lot of HTTP requests or requests with
many
parameters.</p>
<p>If the request requires a login authorization, you will also have to add an
<a href="http-config.html#auth_manager">HTTP Authorization Manager</a>
Configuration Element. And, if the request uses cookies, then you will also need an
<a href="http-config.html#cookie_manager">HTTP Cookie Manager</a>. You can
add either of these elements to the Thread Group or the HTTP Request. If you have
more than one HTTP Request that needs authorizations or cookies, then add the
elements to the Thread Group. That way, all HTTP Request controllers will share the
same Authorization Manager and Cookie Manager elements.</p>
<p>If the request uses a technique called "URL Rewriting" to maintain sessions,
then see section
<a href="build-adv-web-test-plan.html#url_rewriting">6.x HTTP Requests and Session
ID's: URL Rewriting</a>
for additional configuration steps.</p>
<p><img src="../images/screenshots/gen-controller/http-request.gif" width="562"
height="635"></img></p>
<p><b>Property Descriptions:</b>
<ul>
<li><b>Name</b> - Descriptive name for this controller that is shown in the tree.
</li>
<li><i>Web Server</i></li>
<ul>
<li><b>Server</b> - Domain name or IP address of the web server.</li>
<li><b>Port</b> - (optional) Port the web server is listening. If you leave
this field
empty, JMeter assumes the default port.</li>
</ul>
<li><i>HTTP Request</i></li>
<ul>
<li><b>Protocol</b> - HTTP or HTTPS.</li>
<li><b>Method</b> - HTTP GET or HTTP POST.</li>
<li><b>Path</b> - The path to resource (for example, /servlets/myServlet). If
the
resource requires query string parameters, add them below in the
"Send Parameters With the Request" section.</li>
<li><i>Send Parameters With the Request</i></li>
<ul>
<li><b>Name</b> - Parameter name</li>
<li><b>Value</b> - Parameter value. You do not have to enter the value
in
URL-Encoded format. JMeter will URL-Encode it for you when it sends
the HTTP request.</li>
<li><b>Add</b> Button - Add a parameter.</li>
<li><b>Delete</b> Button - Delete the currently selected
parameter.</li>
</ul>
<li><i>Send a File With the Request</i></li>
<ul>
<li><b>Filename</b> - Name of the file to send.</li>
<li><b>Browse</b> Button - Select this button to browse the file
system for a
filename.</li>
<li><b>Parameter Name</b> - Name of the parameter.</li>
<li><b>MIME Type</b> - MIME type (for example, text/plain).</li>
</ul>
</ul>
<li><i>Optional Tasks</i></li>
<ul>
<li><b>Retrieve All Images and Java Applets</b> - Tell JMeter to parse the
HTML file
and send HTTP/HTTPS requests for all images and Java applets referenced in the
file.</li>
</ul>
</ul>
</p>
<p><b>See Also:</b>
<br></br>
<a href="assertion.html">Assertion</a>,
<a href="build-web-test-plan.html">Building a Web Test Plan</a>,
<a href="build-adv-web-test-plan.html">Building an Advanced Web Test Plan</a>,
<a href="http-config.html#auth_manager">HTTP Authorization Manager</a>,
<a href="http-config.html#cookie_manager">HTTP Cookie Manager</a>,
<a href="http-config.html#header_manager">HTTP Header Manager</a>,
<a href="http-config.html#html_link_parser">HTTP HTML Link Parser</a>,
<a href="http-config.html#proxy_server">HTTP Proxy Server</a>,
<a href="http-config.html#request_defaults">HTTP Request Defaults</a>,
<a href="build-adv-web-test-plan.html#url_rewriting">HTTP Requests and Session ID's:
URL Rewriting</a>
</p>
</section>
<section name="4.2.1.3 JDBC Request" anchor="jdbc_request">
<p>This controller lets you send an JDBC Request (an SQL query) to a database.</p>
<p>If you are going to send multiple requests to the same database, consider
using one or more of the Defaults Configuration Elements:
<a href="jdbc-config.html#login">Login</a>,
<a href="jdbc-config.html#conn_pool">Connection Pool</a>,
<a href="jdbc-config.html#sql_query">SQL Query</a>.
This way, you do not have to enter the same information for each JDBC Request
controller.</p>
<p><img src="../images/screenshots/gen-controller/jdbc-request.gif" width="466"
height="454"></img></p>
<p><b>Property Descriptions:</b>
<ul>
<li><b>Name</b> - Descriptive name for this controller that is shown in the tree.
</li>
<li><i>Database URL and JDBC Driver</i></li>
<ul>
<li><b>JDBC URL</b> - URL of the database (for example,
"jdbc:weblogic:oracle"). Refer to your database's JDBC documentation for the
URL you should use.</li>
<li><b>Driver Class</b> - The database driver Java class (for example,
"weblogic.jdbc.oci.Driver"). Refer to your database's JDBC documentation for
the name of the JDBC driver class you should use.</li>
</ul>
<li><i>Login Configuration</i></li>
<ul>
<li><b>Username</b> - FTP account username.</li>
<li><b>Password</b> - FTP account password.</li>
</ul>
<li><i>Database Connection Pool</i></li>
<ul>
<li><b>Number of Connections in Pool</b> - Number of database connection
instances to create and keep active. The maximum value depends on your database.
Also, JMeter imposes a maximum of 100 connections.</li>
<li><b>Max Usage For Each Connection</b> - Maximum number of times JMeter
uses a database connection instance before recycling it (destroying and creating
a new instance).</li>
</ul>
<li><b>SQL Query String</b> - SQL query (for example, "select * from
t_customers").</li>
</ul>
</p>
<p><b>See Also:</b>
<br></br>
<a href="assertion.html">Assertion</a>,
<a href="build-db-test-plan.html">Building a Database Test Plan</a>,
<a href="jdbc-config.html#login">JDBC Database Login Defaults</a>,
<a href="jdbc-config.html#conn_pool">JDBC Database Connection Pool Defaults</a>,
<a href="jdbc-config.html#sql_query">JDBC SQL Query Defaults</a>
</p>
</section>
</body>
</document>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
