sebb 2005/06/18 10:40:58
Modified: xdocs/usermanual component_reference.xml
Log:
Fix column break location; make section renumbering easier in future
Revision Changes Path
1.118 +101 -97 jakarta-jmeter/xdocs/usermanual/component_reference.xml
Index: component_reference.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/component_reference.xml,v
retrieving revision 1.117
retrieving revision 1.118
diff -u -r1.117 -r1.118
--- component_reference.xml 18 Jun 2005 02:17:26 -0000 1.117
+++ component_reference.xml 18 Jun 2005 17:40:58 -0000 1.118
@@ -15,7 +15,11 @@
* limitations under the License.
*
-->
-<document index="yes" index-level-2="yes" colbreak="16.4"
+<!DOCTYPE document
+[
+<!ENTITY sect-num '18'>
+]>
+<document index="yes" index-level-2="yes" colbreak="§-num;.4"
prev="boss.html" next="functions.html" date="$Date$">
<properties>
@@ -34,11 +38,11 @@
-->
-<section name="18.1 Samplers" anchor="samplers">
+<section name="§-num;.1 Samplers" anchor="samplers">
<description>
<br></br>
</description>
-<component name="FTP Request" index="18.1.1"
screenshot="gen-controller/ftp-request.gif">
+<component name="FTP Request" index="§-num;.1.1"
screenshot="gen-controller/ftp-request.gif">
<description>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 <complink name="FTP Request Defaults"/> Configuration
@@ -60,7 +64,7 @@
</component>
-<component name="HTTP Request" index="18.1.2"
screenshot="gen-controller/http-request.png">
+<component name="HTTP Request" index="§-num;.1.2"
screenshot="gen-controller/http-request.png">
<description>
<p>This sampler lets you send an HTTP/HTTPS request to a web server.
It
@@ -143,7 +147,7 @@
</component>
-<component name="JDBC Request" index="18.1.3"
screenshot="gen-controller/jdbc-request.gif">
+<component name="JDBC Request" index="§-num;.1.3"
screenshot="gen-controller/jdbc-request.gif">
<description><p>This sampler lets you send an JDBC Request (an SQL query) to
a database.</p>
<p>Before using this you need to set up a
@@ -166,7 +170,7 @@
</component>
-<component name="Java Request" index="18.1.4" screenshot="java_request.gif">
+<component name="Java Request" index="§-num;.1.4"
screenshot="java_request.gif">
<description><p>This sampler lets you control a java class that implements
the
JavaSamplerClient interface. By writing your own implementation of this
interface,
@@ -189,7 +193,7 @@
</component>
-<component name="SOAP/XML-RPC Request" index="18.1.5"
screenshot="soap_sampler.png">
+<component name="SOAP/XML-RPC Request" index="§-num;.1.5"
screenshot="soap_sampler.png">
<description><p>This sampler lets you send a SOAP request to a webservice.
It can also be
used to send XML-RPC over HTTP. It creates an HTTP POST request, with the
specified XML as the
@@ -209,7 +213,7 @@
</component>
-<component name="LDAP Request" index="18.1.6" screenshot="ldap_request.png">
+<component name="LDAP Request" index="§-num;.1.6"
screenshot="ldap_request.png">
<description>This Sampler lets you send a different Ldap request(Add,
Modify, Delete and Search) to a LDAP server.
<p>If you are going to send multiple requests to the same LDAP server,
consider
using an <complink name="LDAP Request Defaults"/>
@@ -289,7 +293,7 @@
</links>
</component>
-<component name="LDAP Extended Request (ALPHA)" index="18.1.6b"
screenshot="ldapext_request.png">
+<component name="LDAP Extended Request (ALPHA)" index="§-num;.1.6b"
screenshot="ldapext_request.png">
<description>This Sampler can send all 8 different LDAP request to a LDAP
server. It is an extended version of the LDAP sampler,
therefore it is harder to configure, but can be made much closer
resembling a real LDAP session.
<p>If you are going to send multiple requests to the same LDAP server,
consider
@@ -418,7 +422,7 @@
</component>
-<component name="WebService(SOAP) Request" index="18.1.7"
screenshot="webservice_sampler.png">
+<component name="WebService(SOAP) Request" index="§-num;.1.7"
screenshot="webservice_sampler.png">
<center><h2>(Beta Code)</h2></center>
<description><p>This sampler has been tested with IIS Webservice running
.NET 1.0 and .NET 1.1.
It has been tested with SUN JWSDP, IBM webservices, Axis and gSoap toolkit
for C/C++.
@@ -465,7 +469,7 @@
</component>
-<component name="Access Log Sampler" index="18.1.8" screenshot="">
+<component name="Access Log Sampler" index="§-num;.1.8" screenshot="">
<center><h2>(Alpha Code)</h2></center>
<description><p>AccessLogSampler was designed to read access logs and
generate http requests.
For those not familiar with the access log, it is the log the webserver
maintains of every
@@ -518,7 +522,7 @@
</component>
-<component name="BeanShell Sampler" index="18.1.9" screenshot="">
+<component name="BeanShell Sampler" index="§-num;.1.9" screenshot="">
<description><p>This sampler allows you to write a sampler using the
BeanShell scripting language.
</p><p>
<b>Please note that the BeanShell jar file is not included with
JMeter; it needs to be separately downloaded.
@@ -585,7 +589,7 @@
</component>
-<component name="BSF Sampler" index="18.1.10" screenshot="">
+<component name="BSF Sampler" index="§-num;.1.10" screenshot="">
<note>This is Alpha code</note>
<description><p>This sampler allows you to write a sampler using a BSF
scripting language.<br></br>
@@ -604,7 +608,7 @@
TBC
</component>
-<component name="TCP Sampler" index="18.1.11" screenshot="">
+<component name="TCP Sampler" index="§-num;.1.11" screenshot="">
<note>ALPHA CODE</note>
<description>
<p>
@@ -657,7 +661,7 @@
</properties>
</component>
-<component name="JMS Publisher" index="18.1.12" screenshot="">
+<component name="JMS Publisher" index="§-num;.1.12" screenshot="">
<note>ALPHA CODE</note>
<description>
<p>
@@ -682,7 +686,7 @@
</properties>
</component>
-<component name="JMS Subscriber" index="18.1.13" screenshot="">
+<component name="JMS Subscriber" index="§-num;.1.13" screenshot="">
<note>ALPHA CODE</note>
<description>
<p>
@@ -707,7 +711,7 @@
</properties>
</component>
-<component name="JMS Point-to-Point" index="18.1.14"
screenshot="jms/JMS_Point-to-Point.png">
+<component name="JMS Point-to-Point" index="§-num;.1.14"
screenshot="jms/JMS_Point-to-Point.png">
<note>ALPHA CODE</note>
<description>
<p>
@@ -761,7 +765,7 @@
</properties>
</component>
-<component name="Test Action" index="18.1.15" screenshot="test_action.png">
+<component name="Test Action" index="§-num;.1.15"
screenshot="test_action.png">
<description>TBA
</description>
<properties>
@@ -771,12 +775,12 @@
</section>
-<section name="18.2 Logic Controllers" anchor="logic_controllers">
+<section name="§-num;.2 Logic Controllers" anchor="logic_controllers">
<description>
<br></br>
</description>
-<component index="18.2.1" name="Interleave Controller"
screenshot="logic-controller/interleave-controller.png">
+<component index="§-num;.2.1" name="Interleave Controller"
screenshot="logic-controller/interleave-controller.png">
<description><p>If you add Generative or Logic Controllers to an Interleave
Controller, JMeter will alternate among each of the
other controllers for each loop iteration. </p>
</description>
@@ -848,7 +852,7 @@
</example>
</component>
-<component index="18.2.2" name="Loop Controller" anchor="loop"
screenshot="logic-controller/loop-controller.gif">
+<component index="§-num;.2.2" name="Loop Controller" anchor="loop"
screenshot="logic-controller/loop-controller.gif">
<description><p>If you add Generative or Logic Controllers to a Loop
Controller, JMeter will
loop through them a certain number of times, in addition to the loop value
you
specified for the Thread Group. For example, if you add one HTTP Request to
a
@@ -887,7 +891,7 @@
</component>
-<component index="18.2.3" name="Once Only Controller"
anchor="once_only_controller"
+<component index="§-num;.2.3" name="Once Only Controller"
anchor="once_only_controller"
screenshot="logic-controller/once-only-controller.gif">
<description>
<p>The Once Only Logic Controller tells JMeter to process the controller(s)
inside it only once, and pass over any requests under it
@@ -915,7 +919,7 @@
</example>
</component>
-<component index="18.2.4" name="Simple Controller"
anchor="simple_controller" screenshot="logic-controller/simple-controller.gif">
+<component index="§-num;.2.4" name="Simple Controller"
anchor="simple_controller" screenshot="logic-controller/simple-controller.gif">
<description>
<p>The Simple Logic Controller lets you organize your Samplers and other
Logic Controllers. Unlike other Logic Controllers, this controller provides
no functionality beyond that of a
@@ -939,7 +943,7 @@
</example>
</component>
-<component index="18.2.5" name="Random Controller"
screenshot="logic-controller/random-controller.gif">
+<component index="§-num;.2.5" name="Random Controller"
screenshot="logic-controller/random-controller.gif">
<description>
<p>The Random Logic Controller acts similarly to the Interleave Controller,
except that
instead of going in order through its sub-controllers and samplers, it picks
one
@@ -954,7 +958,7 @@
</component>
-<component index="18.2.6" name="Recording Controller"
screenshot="logic-controller/recording-controller.gif">
+<component index="§-num;.2.6" name="Recording Controller"
screenshot="logic-controller/recording-controller.gif">
<description>
<p>The Recording Controller is a place holder indicating where the proxy
server should
record samples to. During test run, it has no effect, similar to the Simple
Controller. But during
@@ -968,7 +972,7 @@
</component>
-<component index="18.2.7" name="Module Controller"
screenshot="module_controller.png">
+<component index="§-num;.2.7" name="Module Controller"
screenshot="module_controller.png">
<description>
<p>The Module Controller provides a mechanism for substituting test plan
fragments into the current test plan at run-time. To use this
module effectively, one might have a number of Controllers under the
<complink name="WorkBench"/>, each with a different series of
@@ -985,7 +989,7 @@
</component>
-<component index="18.2.8" name="Throughput Controller"
screenshot="throughput_controller.png">
+<component index="§-num;.2.8" name="Throughput Controller"
screenshot="throughput_controller.png">
<description>
<p>The Throughput Controller allows the user to control how often it is
executed. There are two modes - percent execution and total executions.
Percent executions causes the controller to execute a certain percentage of the
iterations through the test plan. Total
executions causes the controller to stop executing after a certain number of
executions have occurred. Like the Once Only Controller, this
@@ -1001,7 +1005,7 @@
</properties>
</component>
-<component name="If Controller" index="18.2.9" screenshot="">
+<component name="If Controller" index="§-num;.2.9" screenshot="">
<description>
<p>The If Controller allows the user to control whether the
test elements below it (its children) are run or not.</p>
</description>
@@ -1011,7 +1015,7 @@
</properties>
</component>
-<component name="Random Order Controller" index="18.2.10" screenshot="">
+<component name="Random Order Controller" index="§-num;.2.10"
screenshot="">
<description>
<p>The Random Order Controller is much like a Simple Controller
in that it will execute each child
element at most once, but the order of execution of the nodes
will be random.</p>
@@ -1021,7 +1025,7 @@
</properties>
</component>
-<component name="ForEach Controller" index="18.2.11" anchor="loop"
screenshot="logic-controller/foreach-controller.png">
+<component name="ForEach Controller" index="§-num;.2.11" anchor="loop"
screenshot="logic-controller/foreach-controller.png">
<description><p>A ForEach controller loops through the values of a set of
related variables.
When you add samplers (or controllers) to a ForEach controller, every sample
sample (or controller)
is executed one or more times, where during every loop the variable has a
new value.
@@ -1093,7 +1097,7 @@
</example>
</component>
-<component name="Transaction Controller" index="18.2.12" screenshot="">
+<component name="Transaction Controller" index="§-num;.2.12"
screenshot="">
<description>
<p>The Transaction Controller times how long it takes for all
its children to run.
It then adds a "sample" entry to the test output with
the total elapsed time.
@@ -1105,7 +1109,7 @@
</properties>
</component>
-<component name="Runtime Controller" index="18.2.12" screenshot="">
+<component name="Runtime Controller" index="§-num;.2.12" screenshot="">
<description>
<p>The Runtime Controller controls how long its children are
allowed to run.
</p>
@@ -1148,7 +1152,7 @@
</properties>
</component>
-<component name="Switch Controller" index="18.2.14" screenshot="">
+<component name="Switch Controller" index="§-num;.2.14" screenshot="">
<description>
<note>ALPHA CODE</note>
<p>
@@ -1167,7 +1171,7 @@
</section>
-<section name="18.3 Listeners" anchor="listeners">
+<section name="§-num;.3 Listeners" anchor="listeners">
<description>
<br></br>
Most of the listeners perform several roles in addition to "listening"
@@ -1262,7 +1266,7 @@
<br></br>
</description>
-<component index="18.3.1" name="Mailer Visualizer"
screenshot="mailer_vis.png">
+<component index="§-num;.3.1" name="Mailer Visualizer"
screenshot="mailer_vis.png">
<description><p>The mailer visualizer can be set up to send email if a test
run receives too many
failed responses from the server.</p></description>
@@ -1285,11 +1289,11 @@
</properties>
</component>
-<component index="18.3.2" name="Graph Full Results" screenshot="">
+<component index="§-num;.3.2" name="Graph Full Results" screenshot="">
<description>No Description</description>
</component>
-<component index="18.3.3" name="Graph Results"
screenshot="graph_results.png">
+<component index="§-num;.3.3" name="Graph Results"
screenshot="graph_results.png">
<description><p>The Graph Results listener generates a simple graph that
plots all sample times. Along
the bottom of the graph, the current sample (black), the current average of
all samples(blue), the
current standard deviation (red), and the current throughput rate (green)
are displayed in milliseconds.</p>
@@ -1302,14 +1306,14 @@
number.</p></description>
</component>
-<component index="18.3.4" name="Spline Visualizer"
screenshot="spline_visualizer.png">
+<component index="§-num;.3.4" name="Spline Visualizer"
screenshot="spline_visualizer.png">
<description><p>The Spline Visualizer provides a view of all sample times
from the start
of the test till the end, regardless of how many samples have been taken.
The spline
has 10 points, each representing 10% of the samples, and connected using
spline
logic to show a single continuous line.</p></description>
</component>
-<component index="18.3.5" name="Assertion Results"
screenshot="assertion_results.png">
+<component index="§-num;.3.5" name="Assertion Results"
screenshot="assertion_results.png">
<description><p>The Assertion Results visualizer shows the URL of each
sample taken (no time information
is shown). It also reports failures of any <a
href="test_plan.html#assertions">Assertions</a> that
are part of the test plan.</p></description>
@@ -1319,7 +1323,7 @@
</links>
</component>
-<component index="18.3.6" name="View Results Tree"
screenshot="view_results_tree.png">
+<component index="§-num;.3.6" name="View Results Tree"
screenshot="view_results_tree.png">
<description>The View Results Tree shows a tree of all sample responses,
allowing you to view the
response for any sample. In addition to showing the response, you can see
the time it took to get
this response, and some response codes.
@@ -1347,27 +1351,27 @@
</p>
</component>
-<component index="18.3.7" name="Aggregate Report"
screenshot="aggregate_report.png">
+<component index="§-num;.3.7" name="Aggregate Report"
screenshot="aggregate_report.png">
<description>The aggregate report creates a table row for each differently
named request in your
test. For each request, it totals the response information and provides
request count, min, max,
average, error rate, approximate throughput (request/second) and Kilobytes
per second throughput.
Once the test is done, the throughput is the actual through for the duration
of the entire test.</description>
</component>
-<component index="18.3.8" name="View Results in Table"
screenshot="table_results.png">
+<component index="§-num;.3.8" name="View Results in Table"
screenshot="table_results.png">
<description>This visualizer creates a row for every sample result. Each
sample result's URL,
time in milliseconds, success/failure is displayed. Like the <complink
name="View Results Tree"/>,
this visualizer uses a lot of memory. The last column shows the number of
bytes for the
response from the server.</description>
</component>
-<component index="18.3.9" name="Simple Data Writer" screenshot="">
+<component index="§-num;.3.9" name="Simple Data Writer" screenshot="">
<description>This listener can record results to a file
but not to the UI. It is meant to provide an efficient means of
recording data by eliminating GUI overhead.</description>
</component>
-<component index="18.3.10" name="Monitor Results"
screenshot="monitor_screencap.png">
+<component index="§-num;.3.10" name="Monitor Results"
screenshot="monitor_screencap.png">
<description>
<p>Monitor Results is a new Visualizer for displaying server
status. It is designed for Tomcat 5, but any servlet container
@@ -1390,7 +1394,7 @@
</description>
</component>
-<component index="18.3.11" name="Distribution Graph (alpha)"
screenshot="distribution_graph.png">
+<component index="§-num;.3.11" name="Distribution Graph (alpha)"
screenshot="distribution_graph.png">
<description>
<p>The distribution graph will display a bar for every unique response time.
Since the
granularity of System.currentTimeMillis() is 10 milliseconds, the 90%
threshold should be
@@ -1411,7 +1415,7 @@
</section>
-<section name="18.4 Configuration Elements" anchor="config_elements">
+<section name="§-num;.4 Configuration Elements" anchor="config_elements">
<description>
<br></br>
Configuration elements can be used to set up defaults and variables for
later use by samplers.
@@ -1419,7 +1423,7 @@
i.e. before any samplers in the same scope.
<br></br>
</description>
-<component index="18.4.1" name="HTTP Authorization Manager"
screenshot="http-config/http-auth-manager.gif">
+<component index="§-num;.4.1" name="HTTP Authorization Manager"
screenshot="http-config/http-auth-manager.gif">
<note>If there is more than one Authorization Manager in the scope of a
Sampler,
there is currently no way to sepcify which one is to be used.</note>
@@ -1480,7 +1484,7 @@
</component>
-<component index="18.4.2" name="HTTP Cookie Manager"
screenshot="http-config/http-cookie-manager.gif">
+<component index="§-num;.4.2" name="HTTP Cookie Manager"
screenshot="http-config/http-cookie-manager.gif">
<note>If there is more than one Cookie Manager in the scope of a Sampler,
there is currently no way to sepcify which one is to be used.</note>
@@ -1509,7 +1513,7 @@
</component>
-<component index="18.4.3" name="HTTP Proxy Server"
screenshot="proxy_control.png">
+<component index="§-num;.4.3" name="HTTP Proxy Server"
screenshot="proxy_control.png">
<note>The Proxy Server can only record HTTP traffic.
There is currently no support for recording HTTPS (SSL) sessions.</note>
<description><p>The Proxy Server allows JMeter to watch and record your
actions while you browse your web application
@@ -1625,7 +1629,7 @@
</component>
-<component index="18.4.4" name="HTTP Request Defaults"
+<component index="§-num;.4.4" name="HTTP Request Defaults"
screenshot="http-config/http-request-defaults.png">
<description><p>This element lets you set default values that your HTTP
Request controllers use. For example, if you are
creating a Test Plan with 25 HTTP Request controllers and all of the
requests are being sent to the same server,
@@ -1653,12 +1657,12 @@
</properties>
</component>
-<component index="18.4.5" name="FTP Request Defaults"
+<component index="§-num;.4.5" name="FTP Request Defaults"
screenshot="ftp-config/ftp-request-defaults.gif">
<description></description>
</component>
-<component index="18.4.6" name="JDBC Connection Configuration"
+<component index="§-num;.4.6" name="JDBC Connection Configuration"
screenshot="jdbc-config/jdbc-conn-config.png">
<description>Creates a database connection pool (used by <complink
name="JDBC Request"/>Sampler)
with JDBC Connection settings.
@@ -1685,7 +1689,7 @@
</properties>
</component>
-<component index="18.4.7" name="JDBC SQL Query Defaults"
+<component index="§-num;.4.7" name="JDBC SQL Query Defaults"
screenshot="jdbc-config/jdbc-sql-query.png">
<description>Defines a default query for the <complink name="JDBC
Request"/>Sampler.
<br></br>
@@ -1693,13 +1697,13 @@
</description>
</component>
-<component index="18.4.8" name="Mail Reader Sampler">
+<component index="§-num;.4.8" name="Mail Reader Sampler">
<description>TBA</description>
</component>
-<component index="18.4.9" name="HTTP Header Manager"
screenshot="http-config/http-header-manager.gif">
+<component index="§-num;.4.9" name="HTTP Header Manager"
screenshot="http-config/http-header-manager.gif">
<note>If there is more than one Header Manager in the scope of a Sampler,
there is currently no way to sepcify which one is to be used.</note>
@@ -1731,7 +1735,7 @@
</component>
-<component index="18.4.10" name="Login Config Element"
screenshot="login-config.png">
+<component index="§-num;.4.10" name="Login Config Element"
screenshot="login-config.png">
<description><p>The Login Config Element lets you add or override username
and password settings in samplers that use username and password as part of
their setup.</p>
</description>
@@ -1743,7 +1747,7 @@
</component>
-<component index="18.4.11" name="Simple Config Element"
screenshot="simple_config_element.png">
+<component index="§-num;.4.11" name="Simple Config Element"
screenshot="simple_config_element.png">
<description><p>The Simple Config Element lets you add or override arbitrary
values in samplers. You can choose the name of the value
and the value itself. Although some adventurous users might find a use for
this element, it's here primarily for developers as a basic
GUI that they can use while developing new JMeter components.</p>
@@ -1758,26 +1762,26 @@
</component>
-<component index="18.4.12" name="LDAP Request Defaults"
screenshot="ldap_defaults.png">
+<component index="§-num;.4.12" name="LDAP Request Defaults"
screenshot="ldap_defaults.png">
<description><p>The LDAP Request Defaults component lets you set default
values for LDAP testing. See the <complink name="LDAP Request"/>.</p>
</description>
</component>
-<component index="18.4.12b" name="LDAP Extended Request Defaults (ALPHA)"
screenshot="ldapext_defaults.png">
+<component index="§-num;.4.12b" name="LDAP Extended Request Defaults
(ALPHA)" screenshot="ldapext_defaults.png">
<description><p>The LDAP Extended Request Defaults component lets you set
default values for extended LDAP testing. See the <complink name="LDAP
Extended Request (ALPHA)"/>.</p>
</description>
</component>
-<component index="18.4.13" name="Java Request Defaults"
screenshot="java_defaults.png">
+<component index="§-num;.4.13" name="Java Request Defaults"
screenshot="java_defaults.png">
<description><p>The Java Request Defaults component lets you set default
values for Java testing. See the <complink name="Java Request"/>.</p>
</description>
</component>
-<component index="18.4.14" name="User Defined Variables"
screenshot="user_defined_variables.png">
+<component index="§-num;.4.14" name="User Defined Variables"
screenshot="user_defined_variables.png">
<description><p>The User Defined Variables lets you define variables for use
in other test elements, just as in the <complink name="Test Plan"/>.
The variables in User Defined Variables components will take precedence over
those defined closer to the tree root -- including those defined in the Test
Plan.</p>
</description>
@@ -1789,7 +1793,7 @@
</properties>
</component>
-<component index="18.4.15" name="TCP Sampler Config" screenshot="">
+<component index="§-num;.4.15" name="TCP Sampler Config" screenshot="">
<note>ALPHA CODE</note>
<description>
The TCP Sampler Config provides default data for the TCP Sampler
@@ -1804,7 +1808,7 @@
</properties>
</component>
-<component index="18.4.16" name="CSV Data Set Config" screenshot="">
+<component index="§-num;.4.16" name="CSV Data Set Config" screenshot="">
<description>
CSV DataSet Config is used to read lines from a file, and split them
into variables.
<p>
@@ -1821,14 +1825,14 @@
</section>
-<section name="18.5 Assertions" anchor="assertions">
+<section name="§-num;.5 Assertions" anchor="assertions">
<description>
<br></br>
Assertions are used to perform additional checks on samplers, and are
processed after <b>each sampler</b>
in the same scope.
<br></br>
</description>
-<component index="18.5.1" name="Response Assertion" anchor="basic_assertion"
screenshot="assertion/assertion.gif">
+<component index="§-num;.5.1" name="Response Assertion"
anchor="basic_assertion" screenshot="assertion/assertion.gif">
<description><p>The response assertion control panel lets you add pattern
strings to be compared against various
fields of the response.
@@ -1888,7 +1892,7 @@
</component>
-<component index="18.5.2" name="Duration Assertion"
screenshot="duration_assertion.png">
+<component index="§-num;.5.2" name="Duration Assertion"
screenshot="duration_assertion.png">
<description><p>The Duration Assertion tests that each response was received
within a given amount
of time. Any response that takes longer than the given number of
milliseconds (specified by the
user) is marked as a failed response.</p></description>
@@ -1901,7 +1905,7 @@
</properties>
</component>
-<component index="18.5.3" name="Size Assertion"
screenshot="size_assertion.png">
+<component index="§-num;.5.3" name="Size Assertion"
screenshot="size_assertion.png">
<description><p>The Size Assertion tests that each response contains the
right number of bytes in it. You can specify that
the size be equal to, greater than, less than, or not equal to a given
number of bytes.</p></description>
@@ -1914,7 +1918,7 @@
</properties>
</component>
-<component index="18.5.4" name="XML Assertion"
screenshot="xml_assertion.png">
+<component index="§-num;.5.4" name="XML Assertion"
screenshot="xml_assertion.png">
<description><p>The XML Assertion tests that the response data consists of a
formally correct XML document. It does not
validate the XML based on a DTD or schema or do any further
validation.</p></description>
@@ -1924,7 +1928,7 @@
</properties>
</component>
-<component index="18.5.5" name="BeanShell Assertion"
screenshot="bsh_assertion.png">
+<component index="§-num;.5.5" name="BeanShell Assertion"
screenshot="bsh_assertion.png">
<description><p>The BeanShell Assertion allows the user to perform assertion
checking using a BeanShell script.
</p>
<p>
@@ -1987,7 +1991,7 @@
</ul></p>
</component>
-<component index="18.5.6" name="MD5Hex Assertion">
+<component index="§-num;.5.6" name="MD5Hex Assertion">
<description><p>The MD5Hex Assertion allows the user to check the MD5 hash
of the response data.</p></description>
<properties>
@@ -1997,7 +2001,7 @@
</properties>
</component>
-<component index="18.5.7" name="HTML Assertion"
screenshot="assertion/HTMLAssertion.png">
+<component index="§-num;.5.7" name="HTML Assertion"
screenshot="assertion/HTMLAssertion.png">
<description><p>The HTML Assertion allows the user to check the HTML syntax
of the response data using JTidy.</p></description>
<properties>
@@ -2011,7 +2015,7 @@
</properties>
</component>
-<component index="18.5.8" name="XPath Assertion"
screenshot="xpath_assertion.png">
+<component index="§-num;.5.8" name="XPath Assertion"
screenshot="xpath_assertion.png">
<description><p>The XPath Assertion tests a document for well formedness,
has the option
of validating against a DTD, or putting the document through JTidy and
testing for an
XPath. If that XPath exists, the Assertion is true. Using "/" will match
any well-formed
@@ -2030,7 +2034,7 @@
<property name="True if nothing matches" required="No">True if a XPath
expression is not matched</property>
</properties>
</component>
-<component index="18.5.9" name="XML Schema Assertion"
screenshot="assertion/XMLSchemaAssertion.png">
+<component index="§-num;.5.9" name="XML Schema Assertion"
screenshot="assertion/XMLSchemaAssertion.png">
<description><p>The XML Schema Assertion allows the user to validate a
response against an XML Schema.</p></description>
<properties>
@@ -2040,7 +2044,7 @@
</component>
</section>
-<section name="18.6 Timers" anchor="timers">
+<section name="§-num;.6 Timers" anchor="timers">
<description>
<br></br>
Note that timers are processed at the start of the scope in which they
are found;
@@ -2051,7 +2055,7 @@
child of a simple logic controller immediately after the sampler.
<br></br>
</description>
-<component index="18.6.1" name="Constant Timer" anchor="constant"
screenshot="timers/constant_timer.gif">
+<component index="§-num;.6.1" name="Constant Timer" anchor="constant"
screenshot="timers/constant_timer.gif">
<description>
<p>If you want to have each thread pause for the same amount of time between
requests, use this timer.</p></description>
@@ -2062,7 +2066,7 @@
</properties>
</component>
-<component index="18.6.2" name="Gaussian Random Timer"
screenshot="timers/gauss_random_timer.gif">
+<component index="§-num;.6.2" name="Gaussian Random Timer"
screenshot="timers/gauss_random_timer.gif">
<description><p>This timer pauses each thread request for a random amount of
time, with most
of the time intervals ocurring near a particular value. The total delay is
the
@@ -2079,7 +2083,7 @@
</component>
-<component index="18.6.3" name="Uniform Random Timer"
screenshot="timers/uniform_random_timer.gif">
+<component index="§-num;.6.3" name="Uniform Random Timer"
screenshot="timers/uniform_random_timer.gif">
<description><p>This timer pauses each thread request for a random amount of
time, with
each time interval having the same probability of occurring. The total delay
@@ -2095,7 +2099,7 @@
</component>
-<component index="18.6.4" name="Constant Throughput Timer"
screenshot="timers/constant_throughput_timer.png">
+<component index="§-num;.6.4" name="Constant Throughput Timer"
screenshot="timers/constant_throughput_timer.png">
<description><p>This timer introduces variable pauses, calculated to keep
the total throughput (in terms of samples per minute) as close as possible to a
give figure. Of course the throughput will be lower if the server is not
capable of handling it, or if other timers or time-consuming test elements
prevent it.</p>
@@ -2113,7 +2117,7 @@
</component>
-<component index="18.6.5" name="Synchronizing Timer"
screenshot="timers/sync_timer.png">
+<component index="§-num;.6.5" name="Synchronizing Timer"
screenshot="timers/sync_timer.png">
<description>
<p>
@@ -2132,13 +2136,13 @@
</section>
-<section name="18.7 Pre Processors" anchor="preprocessors">
+<section name="§-num;.7 Pre Processors" anchor="preprocessors">
<description>
<br></br>
Preprocessors are used to modify the Samplers in their scope.
<br></br>
</description>
-<component index="18.7.1" name="HTML Link Parser" anchor="html_link_parser">
+<component index="§-num;.7.1" name="HTML Link Parser"
anchor="html_link_parser">
<description>
<p>This modifier parses HTML response from the server and extracts
links and forms. A URL test sample that passes through this modifier will
be examined to
@@ -2188,7 +2192,7 @@
</component>
-<component index="18.7.2" name="HTTP URL Re-writing Modifier"
screenshot="url_rewriter.png">
+<component index="§-num;.7.2" name="HTTP URL Re-writing Modifier"
screenshot="url_rewriter.png">
<description><p>This modifier works similarly to the HTML Link Parser,
except it has a specific purpose for which
it is easier to use than the HTML Link Parser, and more efficient. For web
applications that
use URL Re-writing to store session ids instead of cookies, this element can
be attached at the
@@ -2212,7 +2216,7 @@
</properties>
</component>
-<component index="18.7.3" name="HTML Parameter Mask" useinstead="Counter"
screenshot="parameter_mask.png">
+<component index="§-num;.7.3" name="HTML Parameter Mask"
useinstead="Counter" screenshot="parameter_mask.png">
<description><p>The HTML Parameter Mask is used to generate unique values
for HTML arguments. By
specifying the name of the parameter, a value prefix and suffix, and counter
parameters, this
modifier will generate values of the form
"<code>name=prefixcountersuffix</code>". Any HTTP
@@ -2240,7 +2244,7 @@
</properties>
</component>
-<component index="18.7.4" name="HTTP User Parameter Modifier"
useinstead="User Parameters" screenshot="user_param_modifier.gif">
+<component index="§-num;.7.4" name="HTTP User Parameter Modifier"
useinstead="User Parameters" screenshot="user_param_modifier.gif">
<description><p>The User Parameter Modifier uses an XML file get values for
HTTP arguments. Any
HTTP Request that this modifier modifies will be checked for the existence
of the specified
arguments. If found, the values for those arguments will be replaced by the
values found in the
@@ -2259,7 +2263,7 @@
</properties>
</component>
-<component index="18.7.5" name="User Parameters"
screenshot="user_params.png">
+<component index="§-num;.7.5" name="User Parameters"
screenshot="user_params.png">
<description><p>Allows the user to specify values for User Variables
specific to individual threads.</p>
<p>User Variables can also be specified in the Test Plan but not specific to
individual threads. This panel allows
you to specify a series of values for any User Variable. For each thread,
the variable will be assigned one of the values from the series
@@ -2283,7 +2287,7 @@
</properties>
</component>
-<component index="18.7.6" name="Counter" screenshot="counter.png">
+<component index="§-num;.7.6" name="Counter" screenshot="counter.png">
<description><p>Allows the user to create a counter that can be referenced
anywhere
in the Thread Group. The counter config lets the user configure a starting
point, a maximum,
and the increment. The counter will loop from the start to the max, and
then start over
@@ -2305,7 +2309,7 @@
</section>
-<section name="18.8 Post-Processors" anchor="postprocessors">
+<section name="§-num;.8 Post-Processors" anchor="postprocessors">
<description>
<br></br>
As the name suggests, Post-Processors are applied after
samplers. Note that they are
@@ -2313,7 +2317,7 @@
is applied only to a particular sampler, add it as a child of
the sampler.
<br></br>
</description>
-<component index="18.8.1" name="Regular Expression Extractor"
screenshot="regex_extractor.png">
+<component index="§-num;.8.1" name="Regular Expression Extractor"
screenshot="regex_extractor.png">
<description><p>Allows the user to extract values from a server response
using a Perl-type regular expression. As a post-processor,
this element will execute after each Sample request in its <scope/>,
applying the regular expression, extracting the requested values,
generate the template string, and store the result into the given variable
name.</p></description>
@@ -2350,7 +2354,7 @@
</p>
</component>
-<component index="18.8.2" name="Result Status Action Handler"
screenshot="resultstatusactionhandler.png">
+<component index="§-num;.8.2" name="Result Status Action Handler"
screenshot="resultstatusactionhandler.png">
<description>This test element allows the user to stop the thread or the
whole test if the relevant sampler failed.
</description>
<properties>
@@ -2358,7 +2362,7 @@
</properties>
</component>
-<component index="18.8.3" name="Save Responses to a file"
screenshot="savetofile.png">
+<component index="§-num;.8.3" name="Save Responses to a file"
screenshot="savetofile.png">
<description>This test element can be placed anywhere in the test plan.
For each sample in its scope, it will create a file of the
response Data.
The primary use for this is in creating functional tests.
@@ -2371,7 +2375,7 @@
</properties>
</component>
-<component index="18.8.4" name="Generate Summary Results"
screenshot="summary.png">
+<component index="§-num;.8.4" name="Generate Summary Results"
screenshot="summary.png">
<description>This test element can be placed anywhere in the test plan.
Generates a summary of the test run so far to the log file and/or
standard output. Both running and differential totals are shown.
@@ -2388,15 +2392,15 @@
</section>
-<section name="18.9 Miscellaneous Features" anchor="Miscellaneous_Features">
+<section name="§-num;.9 Miscellaneous Features"
anchor="Miscellaneous_Features">
<description>
<br></br>
</description>
-<component index="18.9.1" name="Test Plan" screenshot="testplan.png">
+<component index="§-num;.9.1" name="Test Plan" screenshot="testplan.png">
<description><p>At the Test Plan level, static variables can be defined that
allow users to abstract values that are repeated throughout their tests, such
as server names. Here, one can instruct JMeter to save the maximum sample
information to file by selecting "functional testing". Also, an option exists
here to instruct JMeter to run the <complink name="Thread Group"/> serially
rather than in parallel.</p></description>
</component>
-<component index="18.9.2" name="Thread Group" screenshot="threadgroup.png">
+<component index="§-num;.9.2" name="Thread Group"
screenshot="threadgroup.png">
<description><p>A Thread Group defines a pool of users that will execute a
particular test case against your server. In the Thread Group GUI, you can
control the number of users simulated (num of threads), the ramp up time (how
long it takes to start all the threads), the number of times to perform the
test, and optionally, a start and stop time for the test.</p></description>
<properties>
@@ -2421,11 +2425,11 @@
</properties>
</component>
-<component index="18.9.3" name="WorkBench" screenshot="workbench.png">
+<component index="§-num;.9.3" name="WorkBench"
screenshot="workbench.png">
<description><p>The WorkBench simply provides a place to temporarily store
test elements while not in use, for copy/paste purposes, or any other purpose
you desire. When you save your test plan, WorkBench items are not saved with
it. Your WorkBench can be saved independently, if you like (right-click on
WorkBench and choose Save).</p></description>
</component>
-<component index="18.9.4" name="SSL Manager" screenshot="">
+<component index="§-num;.9.4" name="SSL Manager" screenshot="">
<p>
The SSL Manager is a way to select a client certificate so that you can
test
applications that use Public Key Infrastructure (PKI). In order to use it,
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
