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 se...@apache.org on 2007/08/20 20:07:54 UTC
svn commit: r567775 - /jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/
Author: sebb
Date: Mon Aug 20 11:07:53 2007
New Revision: 567775
URL: http://svn.apache.org/viewvc?rev=567775&view=rev
Log:
Use ENTITY sectnum for all sections
Remove duplicated saving/running sections
Modified:
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/boss.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-adv-web-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-db-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ftp-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-point-to-point-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-topic-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldap-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldapext-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-monitor-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-web-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ws-test-plan.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/get-started.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/remote-test.xml
jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/test_plan.xml
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/boss.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/boss.xml?rev=567775&r1=567774&r2=567775&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/boss.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/boss.xml Mon Aug 20 11:07:53 2007
@@ -15,6 +15,10 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
+
+<!DOCTYPE document[
+<!ENTITY sect-num '17'>
+]>
<document prev="best-practices.html" next="component_reference.html" date="$Date$">
@@ -25,14 +29,14 @@
<body>
-<section name="17. Help! My boss wants me to load test our web app!" anchor="boss">
+<section name="§-num;. Help! My boss wants me to load test our web app!" anchor="boss">
<p>This is a fairly open-ended proposition. There are a number of questions to
be asked first, and additionally a number of resources that will be needed. You
will need some hardware to run the benchmarks/load-tests from. A number of
tools will prove useful. There are a number of products to consider. And finally,
why is Java a good choice to implement a load-testing/Benchmarking product.
</p>
-<subsection name="17.1 Questions to ask">
+<subsection name="§-num;.1 Questions to ask">
<p>What is our anticipated average number of users (normal load) ?
</p>
<p>What is our anticipated peak number of users ?
@@ -45,13 +49,13 @@
</p>
<p>What is the testing intended to achieve?</p>
</subsection>
-<subsection name="17.2 Resources">
+<subsection name="§-num;.2 Resources">
<p>The following resources will prove very helpful. Bear in mind that if you
cannot locate these resources, <b>you</b> will become these resources. As you
already have your work cut out for you, it is worth knowing who the following
people are, so that you can ask them for help if you need it.
</p>
- <subsection name="17.2.1 Network">
+ <subsection name="§-num;.2.1 Network">
<p>Who knows our network topology ? If you run into any firewall or
proxy issues, this will become very important. As well, a private
testing network (which will therefore have very low network latency)
@@ -61,7 +65,7 @@
hardware ?
</p>
</subsection>
- <subsection name="17.2.2 Application">
+ <subsection name="§-num;.2.2 Application">
<p>Who knows how our application functions ? The normal sequence is
<ul>
<li>test (low-volume - can we benchmark our application?)</li>
@@ -78,7 +82,7 @@
</p>
</subsection>
</subsection>
-<subsection name="17.3 What platform should I use to run the benchmarks/load-tests ?">
+<subsection name="§-num;.3 What platform should I use to run the benchmarks/load-tests ?">
<p>This should be a widely-used piece of hardware, with a standard
(i.e. vanilla) software installation. Remember, if you publish your results,
the first thing your clients will do is hire a graduate student to verify them.
@@ -109,20 +113,20 @@
The batch log file can then be loaded into JMeter on a workstation for analysis, or you can
use CSV output and import the data into a spreadsheet.</p>
</subsection>
-<subsection name="17.4 Tools">
+<subsection name="§-num;.4 Tools">
<p>The following tools will all prove useful. It is definitely worthwhile to
become familiar with them. This should include trying them out, and reading the
appropriate documentation (man-pages, info-files, application --help messages,
and any supplied documentation).
</p>
- <subsection name="17.4.1 ping">
+ <subsection name="§-num;.4.1 ping">
<p>
This can be used to establish whether or not you can reach your
target site. Options can be specified so that 'ping' provides the
same type of route reporting as 'traceroute'.
</p>
</subsection>
- <subsection name="17.4.2 nslookup/dig">
+ <subsection name="§-num;.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
@@ -130,7 +134,7 @@
the unique address (dotted quad) of your target site.
</p>
</subsection>
- <subsection name="17.4.3 traceroute">
+ <subsection name="§-num;.4.3 traceroute">
<p>
If you cannot "ping" your target site, this may be used to determine
the problem (possibly a firewall or a proxy). It can also be used
@@ -141,7 +145,7 @@
</p>
</subsection>
</subsection>
-<subsection name="17.5 What other products are there ?">
+<subsection name="§-num;.5 What other products are there ?">
<p>There are a number of commercial products, which generally have fairly
hefty pricetags. If you can justify it, these are probably the way to go.
If, however, these products do not do exactly what you want, or you are on a
@@ -149,7 +153,7 @@
start by trying the Apache <b>ab</b> tool, as it may very well do the job
if your requirements are not particularly complicated.
</p>
- <subsection name="17.5.1 Apache 'ab' tool">
+ <subsection name="§-num;.5.1 Apache 'ab' tool">
<p>
You should definitely start with this one. It handles HTTP 'get' requests
very well, and can be made to handle HTTP 'post' requests with a little
@@ -157,7 +161,7 @@
performance reporting.
</p>
</subsection>
- <subsection name="17.5.2 HttpUnit">
+ <subsection name="§-num;.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
@@ -165,14 +169,14 @@
conjunction with <b>JUnit</b>.
</p>
</subsection>
- <subsection name="17.5.3 Microsoft WAS">
+ <subsection name="§-num;.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="17.5.4 JMeter">
+ <subsection name="§-num;.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
@@ -181,7 +185,7 @@
</p>
</subsection>
</subsection>
-<subsection name="17.6 Why Java ?">
+<subsection name="§-num;.6 Why Java ?">
<p>Why not Perl or C ?
</p>
<p>Well, Perl might be a very good choice except that the Benchmark package
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-adv-web-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-adv-web-test-plan.xml?rev=567775&r1=567774&r2=567775&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-adv-web-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-adv-web-test-plan.xml Mon Aug 20 11:07:53 2007
@@ -15,7 +15,11 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
-
+
+<!DOCTYPE document[
+<!ENTITY sect-num '6'>
+]>
+
<document prev="build-web-test-plan.html" next="build-db-test-plan.html" date="$Date$">
<properties>
@@ -24,14 +28,14 @@
<body>
-<section name="6. Building an Advanced Web Test Plan" anchor="building">
+<section name="§-num;. Building an Advanced Web Test Plan" anchor="building">
<p>In this section, you will learn how to create advanced
<a href="build-test-plan.html">Test Plans</a> to test a Web site.</p>
<p>For an example of a basic Test Plan, see
<a href="build-web-test-plan.html">Building a Web Test Plan</a>.</p></section>
-<section name="6.1 Handling User Sessions With URL Rewriting" anchor="session_url_rewriting">
+<section name="§-num;.1 Handling User Sessions With URL Rewriting" anchor="session_url_rewriting">
<p>If your web application uses URL rewriting rather than cookies to save session information,
then you'll need to do a bit of extra work to test your site.</p>
<p>To respond correctly to URL rewriting, JMeter needs to parse the HTML
@@ -54,7 +58,7 @@
</example>
</section>
-<section name="6.2 Using a Header Manager" anchor="header_manager">
+<section name="§-num;.2 Using a Header Manager" anchor="header_manager">
<p>The <complink name="HTTP Header Manager"/> lets you customize what information
JMeter sends in the HTTP request header. This header includes properties like "User-Agent",
"Pragma", "Referer", etc.</p>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-db-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-db-test-plan.xml?rev=567775&r1=567774&r2=567775&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-db-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-db-test-plan.xml Mon Aug 20 11:07:53 2007
@@ -15,6 +15,11 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
+
+<!DOCTYPE document[
+<!ENTITY sect-num '7'>
+]>
+
<document prev="build-adv-web-test-plan.html" next="build-ftp-test-plan.html" date="$Date$">
<properties>
@@ -24,7 +29,7 @@
<body>
-<section name="7. Building a Database Test Plan" anchor="building">
+<section name="§-num;. 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 a database server.
You will create ten users that send five SQL requests to the database server.
@@ -41,7 +46,7 @@
</section>
-<section name="7.1 Adding Users" anchor="adding_users">
+<section name="§-num;.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
@@ -57,11 +62,11 @@
<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
+Group Control Panel in the right section of the JMeter window (see Figure §-num;.1
below)</p>
<figure image="jdbctest/threadgroup1.png">
-Figure 7.1. Thread Group with Default Values</figure>
+Figure §-num;.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>
@@ -91,21 +96,21 @@
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>
+<p>See Figure §-num;.2 for the completed JDBC Users Thread Group.</p>
<figure image="jdbctest/threadgroup2.png">
-Figure 7.2. JDBC Users Thread Group</figure>
+Figure §-num;.2. JDBC Users Thread Group</figure>
</section>
-<section name="7.2 Adding JDBC Requests" anchor="adding_requests">
+<section name="§-num;.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>
<p>Begin by selecting the JDBC Users element. Click your right mouse button
to get the Add menu, and then select Add --> Config Element --> JDBC Connection Configuration.
-Then, select this new element to view its Control Panel (see Figure 7.3).</p>
+Then, select this new element to view its Control Panel (see Figure §-num;.3).</p>
<p>Set up the following fields (these assume we will be using a local MySQL database called test):</p>
<ul>
@@ -123,14 +128,14 @@
More than one JDBC Request can refer to the same pool.
</p>
<figure image="jdbctest/jdbc-config.png">
-Figure 7.3. JDBC Configuration</figure>
+Figure §-num;.3. JDBC Configuration</figure>
<p>Selecting the JDBC Users element again. 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.4).</p>
+Then, select this new element to view its Control Panel (see Figure §-num;.4).</p>
<figure image="jdbctest/JDBCRequest.png">
-Figure 7.4. JDBC Request</figure>
+Figure §-num;.4. 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
@@ -139,7 +144,7 @@
<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.5):
+<p>Start by editing the following properties (see Figure §-num;.5):
<ul>
<li>Change the Name to "Kodak".</li>
<li>Enter the Pool Name: MySQL (same as in the configuration element)</li>
@@ -148,10 +153,10 @@
</p>
<figure image="jdbctest/JDBCRequest2.png">
-Figure 7.5. JDBC Request for Eastman Kodak stock</figure>
+Figure §-num;.5. JDBC Request for Eastman Kodak stock</figure>
<p>Next, add the second JDBC Request and edit the following properties (see
-Figure 7.6):
+Figure §-num;.6):
<ul>
<li>Change the Name to "Pfizer".</li>
<li>Enter the SQL Query String field.</li>
@@ -159,11 +164,11 @@
</p>
<figure image="jdbctest/JDBCRequest3.png">
-Figure 7.6. JDBC Request for Pfizer stock</figure>
+Figure §-num;.6. JDBC Request for Pfizer stock</figure>
</section>
-<section name="7.3 Adding a Listener to View/Store the Test Results" anchor="adding_listener">
+<section name="§-num;.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
@@ -173,37 +178,11 @@
listener (Add --> Listener --> Graph Results).</p>
<figure image="jdbctest/graph-results.png">
-Figure 7.7. 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>
+Figure §-num;.7. Graph results Listener</figure>
</section>
-<section name="7.7 JDBC settings" anchor="running">
+<section name="§-num;.4 JDBC settings" anchor="jdbc_settings">
<p>Different databases and JDBC drivers require different JDBC settings.
The Database URL and JDBC Driver class are defined by the provider of the JDBC implementation.</p>
<p>Some possible settings are shown below. Please check the exact details in the JDBC driver documentation.</p>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ftp-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ftp-test-plan.xml?rev=567775&r1=567774&r2=567775&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ftp-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ftp-test-plan.xml Mon Aug 20 11:07:53 2007
@@ -15,6 +15,12 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
+
+<!DOCTYPE document
+[
+<!ENTITY sect-num '8'>
+]>
+
<document prev="build-db-test-plan.html" next="build-ldap-test-plan.html" date="$Date$">
<properties>
@@ -24,7 +30,7 @@
<body>
-<section name="8. Building an FTP Test Plan" anchor="building">
+<section name="§-num;. Building an FTP 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 FTP site. You will
create four users that send requests for two files on the O'Reilly FTP site.
@@ -42,7 +48,7 @@
</section>
-<section name="8.1 Adding Users" anchor="adding_users">
+<section name="§-num;.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
@@ -58,11 +64,11 @@
<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 8.1
+Group Control Panel in the right section of the JMeter window (see Figure §-num;.1
below)</p>
<figure image="webtest/threadgroup.png">
-Figure 8.1. Thread Group with Default Values</figure>
+Figure §-num;.1. Thread Group with Default Values</figure>
<p>Start by providing a more descriptive name for our Thread Group. In the name
field, enter O'Reilly Users.</p>
@@ -88,26 +94,26 @@
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 8.2 for the completed O'Reilly Users Thread Group.</p>
+<p>See Figure §-num;.2 for the completed O'Reilly Users Thread Group.</p>
<figure image="ftptest/threadgroup2.png">
-Figure 8.2. O'Reilly Users Thread Group</figure>
+Figure §-num;.2. O'Reilly Users Thread Group</figure>
</section>
-<section name="8.2 Adding Default FTP Request Properties" anchor="adding_defaults">
+<section name="§-num;.2 Adding Default FTP Request Properties" anchor="adding_defaults">
<p>Now that we have defined our users, it is time define the tasks that they
will be performing. In this section, you will specify the default settings
-for your FTP requests. And then, in section 8.3, you will add FTP Request
+for your FTP requests. And then, in section §-num;.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. 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).
+Defaults. Then, select this new element to view its Control Panel (see Figure §-num;.3).
</p>
<figure image="ftptest/ftp-defaults.png">
-Figure 8.3. FTP Request Defaults</figure>
+Figure §-num;.3. FTP Request Defaults</figure>
<p>
Like most JMeter elements, the <complink name="FTP Request Defaults"/> Control
@@ -124,14 +130,14 @@
to send an FTP request. It simply defines the default values that the
FTP Request elements use.</note>
-<p>See Figure 8.4 for the completed FTP Request Defaults element</p>
+<p>See Figure §-num;.4 for the completed FTP Request Defaults element</p>
<figure image="ftptest/ftp-defaults2.png">
-Figure 8.4. FTP Defaults for our Test Plan</figure>
+Figure §-num;.4. FTP Defaults for our Test Plan</figure>
</section>
-<section name="8.3 Adding FTP Requests" anchor="adding_requests">
+<section name="§-num;.3 Adding FTP Requests" anchor="adding_requests">
<p>In our Test Plan, we need to make two FTP requests. The first one is for the
O'Reilly mSQL Java README file (ftp://ftp.oro.com/pub/msql/java/README), and the
@@ -142,7 +148,7 @@
<p>Start by adding the first <complink name="FTP Request"/>
to the O'Reilly Users element (Add --> Sampler --> FTP Request).
Then, select the FTP Request element in the tree and edit the following properties
-(see Figure 8.5):
+(see Figure §-num;.5):
<ol>
<li>Change the Name to "README".</li>
<li>Change the File to Retrieve From Server field to "pub/msql/java/README".</li>
@@ -155,10 +161,10 @@
this value in the FTP Request Defaults element.</note>
<figure image="ftptest/ftp-request.png">
-Figure 8.5. FTP Request for O'Reilly mSQL Java README file</figure>
+Figure §-num;.5. FTP Request for O'Reilly mSQL Java README file</figure>
<p>Next, add the second FTP Request and edit the following properties (see
-Figure 8.6:
+Figure §-num;.6:
<ol>
<li>Change the Name to "tutorial".</li>
<li>Change the File to Retrieve From Server field to "pub/msql/java/tutorial.txt".</li>
@@ -168,11 +174,11 @@
</p>
<figure image="ftptest/ftp-request2.png">
-Figure 8.6. FTP Request for O'Reilly mSQL Java tutorial file</figure>
+Figure §-num;.6. FTP Request for O'Reilly mSQL Java tutorial file</figure>
</section>
-<section name="8.4 Adding a Listener to View/Store the Test Results" anchor="adding_listener">
+<section name="§-num;.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
@@ -182,33 +188,7 @@
listener (Add --> Listener --> Spline Visualizer).</p>
<figure image="ftptest/spline-results.png">
-Figure 8.7. Spline Visualizer Listener</figure>
-
-</section>
-
-<section name="8.5 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="8.6 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>
+Figure §-num;.7. Spline Visualizer Listener</figure>
</section>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-point-to-point-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-point-to-point-test-plan.xml?rev=567775&r1=567774&r2=567775&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-point-to-point-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-point-to-point-test-plan.xml Mon Aug 20 11:07:53 2007
@@ -15,6 +15,9 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
+
+<!DOCTYPE document[<!ENTITY sect-num '11'>]>
+
<document prev="build-ws-test-plan.html" next="build-jms-topic-test-plan.html" date="$Date$">
<properties>
@@ -24,7 +27,7 @@
<body>
- <section name="11. Building a JMS Point-to-Point Test Plan" anchor="building">
+ <section name="§-num;. Building a JMS Point-to-Point Test Plan" anchor="building">
<note>
Make sure the required jar files are in JMeter's lib directory. If they are not, shutdown JMeter,
@@ -52,7 +55,7 @@
</section>
- <section name="11.1 Adding a Thread Group" anchor="adding_threadgroup">
+ <section name="§-num;.1 Adding a Thread Group" anchor="adding_threadgroup">
<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
@@ -69,11 +72,11 @@
<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 11.1
+Group Control Panel in the right section of the JMeter window (see Figure §-num;.1
below)</p>
<figure image="webtest/threadgroup.png">
-Figure 11.1. Thread Group with Default Values</figure>
+Figure §-num;.1. Thread Group with Default Values</figure>
<p>Start by providing a more descriptive name for our Thread Group. In the name
field, enter Point-to-Point.</p>
@@ -103,7 +106,7 @@
</section>
- <section name="11.2 Adding JMS Point-to-Point Sampler" anchor="adding_point_to_point_sampler">
+ <section name="§-num;.2 Adding JMS Point-to-Point Sampler" anchor="adding_point_to_point_sampler">
<p>Start by adding the sampler <complink name="JMS Point-to-Point"/>
to the Point-to-Point element (Add --> Sampler --> JMS Point-to-Point).
@@ -186,7 +189,7 @@
</section>
- <section name="11.3 Adding a Listener to View Store the Test Results" anchor="adding_listener">
+ <section name="§-num;.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 JMS requests in a file and presenting
@@ -201,14 +204,8 @@
</p>
<figure image="graph_results.png">
-Figure 11.2. Graph Results Listener</figure>
-
- </section>
+Figure §-num;.2. Graph Results Listener</figure>
- <section name="11.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.</p>
</section>
</body>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-topic-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-topic-test-plan.xml?rev=567775&r1=567774&r2=567775&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-topic-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-jms-topic-test-plan.xml Mon Aug 20 11:07:53 2007
@@ -189,12 +189,5 @@
</section>
-<section name="§-num;.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.</p>
-
-</section>
-
</body>
</document>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldap-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldap-test-plan.xml?rev=567775&r1=567774&r2=567775&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldap-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldap-test-plan.xml Mon Aug 20 11:07:53 2007
@@ -15,16 +15,21 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
+
+<!DOCTYPE document
+[
+<!ENTITY sect-num '9a'>
+]>
+
<document prev="build-ftp-test-plan.html" next="build-ldapext-test-plan.html" date="$Date$">
<properties>
- <author email="chezhiyan@siptech.co.in">Elanjchezhiyan.T</author>
<title>User's Manual: Building an LDAP Test Plan</title>
</properties>
<body>
-<section name="9. Building an LDAP Test Plan" anchor="building">
+<section name="§-num;. Building an LDAP Test Plan" anchor="building">
<p>In this section, you will learn how to create a basic Test Plan to test an LDAP server.
You will create four users that send requests for four tests on the LDAP server.Also, you will tell
the users to run their tests twice. So, the total number of requests is (4 users) x (4 requests) x
@@ -36,7 +41,7 @@
.</p>
<p>This example assumes that the LDAP Server is installed in your Local machine.</p>
</section>
- <section name="9.1 Adding Users" anchor="adding_users">
+ <section name="§-num;.1 Adding Users" anchor="adding_users">
<p>The first step you want to do with every JMeter Test Plan is to add a Thread Group 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>
@@ -45,11 +50,11 @@
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.
<figure image="ldaptest/threadgroup.png">
-Figure 9.1. Thread Group with Default Values</figure>
+Figure §-num;.1. Thread Group with Default Values</figure>
</p>
</section>
- <section name="9.2 Adding Login Config Element" anchor="add_login">
+ <section name="§-num;.2 Adding Login Config Element" anchor="add_login">
<p>Begin by selecting the Siptech Users element. Click your right mouse
button to get the Add menu, and then select Add --> Config Element --> Login Config Element.
Then, select this new element to view its Control Panel.</p>
@@ -57,7 +62,7 @@
field that you can modify. In this example, leave this field with the default value.</p>
<figure image="ldaptest/login-config-element.png">
- Figure 9.2 Login Config Element for our Test Plan</figure>
+ Figure §-num;.2 Login Config Element for our Test Plan</figure>
<note><p>Enter Username field to "your Server Username",<br/>
The password field to "your Server Passowrd"</p>
@@ -65,7 +70,7 @@
<p>These values are default for the LDAP Requests.</p></note>
</section>
- <section name="9.3 Adding LDAP Request Defaults" anchor="add_defaults">
+ <section name="§-num;.3 Adding LDAP Request Defaults" anchor="add_defaults">
<p>Begin by selecting the Siptech Users element. Click your right mouse button
to get the Add menu, and then select Add --> Config Element -->LDAP Request Defaults. Then,
select this new element to view its Control Panel.</p>
@@ -74,7 +79,7 @@
<figure image="ldaptest/requestdefaults.png">
- Figure 9.3 LDAP Defaults for our Test Plan</figure>
+ Figure §-num;.3 LDAP Defaults for our Test Plan</figure>
<note>Enter DN field to "your Server Root Dn".<br/>
Enter LDAP Server's Servername field to "localhost".<br/>
@@ -83,7 +88,7 @@
</section>
- <section name="9.4 Adding LDAP Requests" anchor="add_requests">
+ <section name="§-num;.4 Adding LDAP Requests" anchor="add_requests">
<p>In our Test Plan, we need to make four LDAP requests.</p>
<ol>
<li>Inbuilt Add Test</li>
@@ -100,7 +105,7 @@
<li>Select the Add test Radio button</li>
</ol>
<figure image="ldaptest/add.png">
- Figure 9.4.1 LDAP Request for Inbuilt Add test</figure>
+ Figure §-num;.4.1 LDAP Request for Inbuilt Add test</figure>
<p>You do not have to set the Server Name field, port field, Username, Password
@@ -114,7 +119,7 @@
</ol>
Next, add the Third LDAP Request and edit the following properties
<figure image="ldaptest/modify.png">
- Figure 9.4.2 LDAP Request for Inbuilt Modify test</figure>
+ Figure §-num;.4.2 LDAP Request for Inbuilt Modify test</figure>
<ol>
<li>Change the Name to "Inbuilt-Delete Test".</li>
@@ -123,31 +128,25 @@
Next, add the fourth LDAP Request and edit the following properties
<figure image="ldaptest/delete.png">
- Figure 9.4.3 LDAP Request for Inbuilt Delete test</figure>
+ Figure §-num;.4.3 LDAP Request for Inbuilt Delete test</figure>
<ol>
<li>Change the Name to "Inbuilt-Search Test".</li>
<li>Select the Search test Radio button</li>
</ol>
<figure image="ldaptest/search.png">
- Figure 9.4.4 LDAP Request for Inbuilt Search test</figure>
+ Figure §-num;.4.4 LDAP Request for Inbuilt Search test</figure>
</section>
- <section name="9.5 Adding a Listener to View/Store the Test Results" anchor="add_listener">
+ <section name="§-num;.5 Adding a Listener to View/Store the Test Results" anchor="add_listener">
<p>The final element you need to add to your Test Plan is a Listener.
This element is responsible for storing all of the results of your LDAP
requests in a file and presenting a visual model of the data.Select the Siptech
Users element and add a View Results in Table (Add --> Listener -->View Results in Table)</p>
<figure image="ldaptest/viewtable.png">
- Figure 9.5 View result in Table Listener</figure>
+ Figure §-num;.5 View result in Table Listener</figure>
</section>
-<section name="9.6 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.</p>
-</section>
-
</body>
</document>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldapext-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldapext-test-plan.xml?rev=567775&r1=567774&r2=567775&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldapext-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ldapext-test-plan.xml Mon Aug 20 11:07:53 2007
@@ -15,16 +15,20 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
+
+<!DOCTYPE document[
+<!ENTITY sect-num '9b'>
+]>
+
<document prev="build-ldap-test-plan.html" next="build-ws-test-plan.html" date="$Date$">
<properties>
- <author email="dolf.smits@siemens.com">Dolf Smits</author>
<title>User's Manual: Building an Extended LDAP Test Plan</title>
</properties>
<body>
-<section name="9b. Building an Extended LDAP Test Plan" anchor="ldapexttest">
+<section name="§-num;. Building an Extended LDAP Test Plan" anchor="ldapexttest">
<p>
In this section, you will learn how to create a basic Test Plan to test an LDAP
server.</p>
@@ -62,7 +66,7 @@
</p>
- <subsection name="9b.1 Adding Users" anchor="ext_adding_users">
+ <subsection name="§-num;.1 Adding Users" anchor="ext_adding_users">
<p>
The first step you want to do with every JMeter Test Plan is to add a Thread Group element.
The Thread Group tells JMeter the number of users you want to simulate, how often the users should send
@@ -76,11 +80,11 @@
</p>
<p>
<figure image="ldaptest/extthreadgroup.png">
-Figure 9b.1. Thread Group with Default Values</figure>
+Figure §-num;.1. Thread Group with Default Values</figure>
</p>
</subsection>
- <subsection name="9b.2 Adding LDAP Extended Request Defaults" anchor="add_ldapext_defaults">
+ <subsection name="§-num;.2 Adding LDAP Extended Request Defaults" anchor="add_ldapext_defaults">
<p>
Begin by selecting the Thread Group element. Click your right mouse button
to get the Add menu, and then select Add --> Config Element -->LDAP Extended Request Defaults. Then,
@@ -91,7 +95,7 @@
field that you can modify. In this example, leave this field with the default value.
</p>
<p><figure image="ldaptest/extrequestdefaults.png"><br/>
- Figure 9b.2 LDAP Defaults for our Test Plan</figure>
+ Figure §-num;.2 LDAP Defaults for our Test Plan</figure>
</p>
<p>
For each of the different operations, some default values can be filled in.
@@ -101,7 +105,7 @@
</p>
We will not enter any default values here, as we will build a very small testplan, so we will explain all the different fields when we add the LDAP Extended samplers.
</subsection>
-<subsection name="9b.3 Adding LDAP Requests" anchor="add_extrequests">
+<subsection name="§-num;.3 Adding LDAP Requests" anchor="add_extrequests">
<p>
In our Test Plan, we want to use all 8 LDAP requests.
</p>
@@ -144,7 +148,7 @@
and edit the following properties.</p>
-<subsection name="9b.3.1 Adding a Thread bind Request" anchor="add_threadbind">
+<subsection name="§-num;.3.1 Adding a Thread bind Request" anchor="add_threadbind">
<p>
<ol>
<li>
@@ -173,11 +177,11 @@
</p>
<p>
<figure image="ldaptest/extthreadbind.png">
-Figure 9b.3.1. Thread Bind example</figure>
+Figure §-num;.3.1. Thread Bind example</figure>
</p>
</subsection>
-<subsection name="9b.3.2 Adding a search Request" anchor="add_searchreq">
+<subsection name="§-num;.3.2 Adding a search Request" anchor="add_searchreq">
<p>
<ol>
<li>
@@ -225,10 +229,10 @@
</p>
<p>
<figure image="ldaptest/extsearch.png">
-Figure 9b.3.2. search request example</figure>
+Figure §-num;.3.2. search request example</figure>
</p></subsection>
-<subsection name="9b.3.3 Adding a Compare Request" anchor="add_comparereq">
+<subsection name="§-num;.3.3 Adding a Compare Request" anchor="add_comparereq">
<p>
<ol>
<li>
@@ -244,11 +248,11 @@
</p>
<p>
<figure image="ldaptest/extcompare.png">
-Figure 9b.3.3. Compare example</figure>
+Figure §-num;.3.3. Compare example</figure>
</p>
</subsection>
-<subsection name="9b.3.4 Adding a Single bind/unbind" anchor="add_sbind">
+<subsection name="§-num;.3.4 Adding a Single bind/unbind" anchor="add_sbind">
<p>
<ol>
<li>
@@ -268,11 +272,11 @@
</ol>
</p><p>
<figure image="ldaptest/extsbind.png">
-Figure 9b.3.4. Single bind/unbind example</figure>
+Figure §-num;.3.4. Single bind/unbind example</figure>
</p>
</subsection>
-<subsection name="9b.3.5 Adding an Add Request" anchor="add_addreq">
+<subsection name="§-num;.3.5 Adding an Add Request" anchor="add_addreq">
<p>
<ol>
<li>
@@ -291,11 +295,11 @@
</p>
<p>
<figure image="ldaptest/extadd.png">
-Figure 9b.3.5. Add request example</figure>
+Figure §-num;.3.5. Add request example</figure>
</p>
</subsection>
-<subsection name="9b.3.6 Adding a Modify Request" anchor="add_modreq">
+<subsection name="§-num;.3.6 Adding a Modify Request" anchor="add_modreq">
<p>
<ol>
<li>
@@ -331,11 +335,11 @@
</p>
<p>
<figure image="ldaptest/extmod.png">
-Figure 9b.3.6. Modify example</figure>
+Figure §-num;.3.6. Modify example</figure>
</p>
</subsection>
-<subsection name="9b.3.7 Adding a Delete Request" anchor="add_delreq">
+<subsection name="§-num;.3.7 Adding a Delete Request" anchor="add_delreq">
<p>
<ol>
<li>
@@ -350,11 +354,11 @@
</p>
<p>
<figure image="ldaptest/extdel.png">
-Figure 9b.3.7. Delete example</figure>
+Figure §-num;.3.7. Delete example</figure>
</p>
</subsection>
-<subsection name="9b.3.8 Adding a Rename Request (moddn)" anchor="add_moddn">
+<subsection name="§-num;.3.8 Adding a Rename Request (moddn)" anchor="add_moddn">
<p>
<ol>
<li>
@@ -375,10 +379,10 @@
</p>
<p>
<figure image="ldaptest/extmoddn.png">
-Figure 9b.3.8. Rename example</figure>
+Figure §-num;.3.8. Rename example</figure>
</p>
</subsection>
-<subsection name="9b.3.9 Adding an unbind Request" anchor="add_unbind">
+<subsection name="§-num;.3.9 Adding an unbind Request" anchor="add_unbind">
<p>
<ol>
<li>
@@ -389,12 +393,12 @@
</p>
<p>
<figure image="ldaptest/extthreadunbind.png">
-Figure 9b.3.9. Unbind example</figure>
+Figure §-num;.3.9. Unbind example</figure>
</p>
</subsection>
</subsection>
-<subsection name="9b.4 Adding a Listener to View/Store the Test Results" anchor="add_ldapext_listener">
+<subsection name="§-num;.4 Adding a Listener to View/Store the Test Results" anchor="add_ldapext_listener">
<p>
The final element you need to add to your Test Plan is a Listener.
This element is responsible for storing all of the results of your LDAP
@@ -403,7 +407,7 @@
</p>
<p>
<figure image="ldaptest/extviewtree.png">
-Figure 9b.4. View result Tree Listener</figure>
+Figure §-num;.4. View result Tree Listener</figure>
</p>
<p>
In this listener you have three tabs to view, the sampler result, the request and the response data.
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-monitor-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-monitor-test-plan.xml?rev=567775&r1=567774&r2=567775&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-monitor-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-monitor-test-plan.xml Mon Aug 20 11:07:53 2007
@@ -151,12 +151,5 @@
</section>
-<section name="§-num;.7 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.</p>
-
-</section>
-
</body>
</document>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-test-plan.xml?rev=567775&r1=567774&r2=567775&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-test-plan.xml Mon Aug 20 11:07:53 2007
@@ -15,6 +15,11 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
+
+<!DOCTYPE document[
+<!ENTITY sect-num '3'>
+]>
+
<document prev="get-started.html" next="test_plan.html" date="$Date$">
<properties>
@@ -23,13 +28,13 @@
<body>
-<section name="3. Building a Test Plan">
+<section name="§-num;. 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>
-<subsection name="3.1 Adding and Removing Elements" anchor="add_remove">
+<subsection name="§-num;.1 Adding and Removing Elements" anchor="add_remove">
<p>Adding <a href="test_plan.html">elements to a test plan</a> 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>
@@ -38,7 +43,7 @@
and choose the "remove" option.</p>
</subsection>
-<subsection name="3.2 Loading and Saving Elements" anchor="load_save">
+<subsection name="§-num;.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>
@@ -50,7 +55,7 @@
<note>The workbench is not automatically saved with the test plan, but it can be saved separately as above.</note>
</subsection>
-<subsection name="3.3 Configuring Tree Elements" anchor="config_element">
+<subsection name="§-num;.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>
@@ -58,7 +63,22 @@
<note>The Test Tree itself can be manipulated by dragging and dropping components around the test tree.</note>
</subsection>
-<subsection name="3.4 Running a Test Plan" anchor="run">
+<subsection name="§-num;.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>
+</subsection>
+
+<subsection name="§-num;.5 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.
When JMeter is running, it shows a small green box at the right hand end of the section just under the menu bar.
@@ -74,7 +94,7 @@
</p>
</subsection>
-<subsection name="3.5 Scoping Rules" anchor="scoping_rules">
+<subsection name="§-num;.6 Scoping Rules" anchor="scoping_rules">
<p>
The JMeter test tree contains elements that are both hierarchical and ordered. Some elements in the test trees are strictly hierarchical (Listeners, Config Elements, Post-Procesors, Pre-Processors, Assertions, Timers), and some are primarily ordered (controllers, samplers). When you create your test plan, you will create an ordered list of sample request (via Samplers) that represent a set of steps to be executed. These requests are often organized within controllers that are also ordered. Given the following test tree:</p>
<figure image="scoping1.png">Example test tree</figure>
@@ -99,7 +119,7 @@
only one Manager is used, but there is currently no way to specify <b>which</b> is used.
</b>
</subsection>
-<subsection name="3.6 Error reporting" anchor="error_reporting">
+<subsection name="§-num;.7 Error reporting" anchor="error_reporting">
<p>
JMeter reports warnings and errors to the jmeter.log file, as well as some information on the test run itself.
Just occaisionally there may be some errors that JMeter is unable to trap and log; these will appear on the command console.
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-web-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-web-test-plan.xml?rev=567775&r1=567774&r2=567775&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-web-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-web-test-plan.xml Mon Aug 20 11:07:53 2007
@@ -15,6 +15,11 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
+
+<!DOCTYPE document[
+<!ENTITY sect-num '5'>
+]>
+
<document prev="test_plan.html" next="build-adv-web-test-plan.html" date="$Date$">
<properties>
@@ -23,7 +28,7 @@
<body>
-<section name="5. Building a Web Test Plan" anchor="building">
+<section name="§-num;. Building a Web 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 a Web site. You will
create five users that send requests to two pages on the Jakarta Web site.
@@ -45,7 +50,7 @@
WorkBench (a temporary place to store your elements while constructing a Test
Plan).</p>-->
-<section name="5.1 Adding Users" anchor="adding_users">
+<section name="§-num;.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
@@ -61,11 +66,11 @@
<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 5.1
+Group Control Panel in the right section of the JMeter window (see Figure §-num;.1
below)</p>
<figure image="webtest/threadgroup.png">
-Figure 5.1. Thread Group with Default Values</figure>
+Figure §-num;.1. Thread Group with Default Values</figure>
<p>Start by providing a more descriptive name for our Thread Group. In the name
field, enter Jakarta Users.</p>
@@ -92,26 +97,26 @@
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 5.2 for the completed Jakarta Users Thread Group.</p>
+<p>See Figure §-num;.2 for the completed Jakarta Users Thread Group.</p>
<figure image="webtest/threadgroup2.png">
-Figure 5.2. Jakarta Users Thread Group</figure>
+Figure §-num;.2. Jakarta Users Thread Group</figure>
</section>
-<section name="5.2 Adding Default HTTP Request Properties" anchor="adding_defaults">
+<section name="§-num;.2 Adding Default HTTP Request Properties" anchor="adding_defaults">
<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 default settings
-for your HTTP requests. And then, in section 5.3, you will add HTTP Request
+for your HTTP requests. And then, in section §-num;.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 (Thread Group) 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).
+Defaults. Then, select this new element to view its Control Panel (see Figure §-num;.3).
</p>
<figure image="webtest/http-defaults1.png">
-Figure 5.3. HTTP Request Defaults</figure>
+Figure §-num;.3. HTTP Request Defaults</figure>
<p>
Like most JMeter elements, the <complink name="HTTP Request Defaults"/> Control
@@ -128,14 +133,14 @@
to send an HTTP request. It simply defines the default values that the
HTTP Request elements use.</note>
-<p>See Figure 5.4 for the completed HTTP Request Defaults element</p>
+<p>See Figure §-num;.4 for the completed HTTP Request Defaults element</p>
<figure image="webtest/http-defaults2.png">
-Figure 5.4. HTTP Defaults for our Test Plan</figure>
+Figure §-num;.4. HTTP Defaults for our Test Plan</figure>
</section>
-<section name="5.3 Adding Cookie Support" anchor="adding_cookie_support">
+<section name="§-num;.3 Adding Cookie Support" anchor="adding_cookie_support">
<p>Nearly all web testing should use cookie support, unless your application
specifically doesn't use cookies. To add cookie support, simply add an
<complink name="HTTP Cookie Manager"/> to each <a href="test_plan.html#thread_group">Thread
@@ -149,7 +154,7 @@
</section>
-<section name="5.4 Adding HTTP Requests" anchor="adding_requests">
+<section name="§-num;.4 Adding HTTP Requests" anchor="adding_requests">
<p>In our Test Plan, we need to make two HTTP requests. The first one is for the
Jakarta home page (http://jakarta.apache.org/), and the second one is for the
@@ -160,7 +165,7 @@
<p>Start by adding the first <complink name="HTTP Request"/>
to the Jakarta Users element (Add --> Sampler --> HTTP Request).
Then, select the HTTP Request element in the tree and edit the following properties
-(see Figure 5.5):
+(see Figure §-num;.5):
<ol>
<li>Change the Name field to "Home Page".</li>
<li>Set the Path field to "/". Remember that you do not have to set the Server
@@ -170,10 +175,10 @@
</p>
<figure image="webtest/http-request1.png">
-Figure 5.5. HTTP Request for Jakarta Home Page</figure>
+Figure §-num;.5. HTTP Request for Jakarta Home Page</figure>
<p>Next, add the second HTTP Request and edit the following properties (see
-Figure 5.6:
+Figure §-num;.6:
<ol>
<li>Change the Name field to "Project Guidelines".</li>
<li>Set the Path field to "/site/guidelines.html".</li>
@@ -181,11 +186,11 @@
</p>
<figure image="webtest/http-request2.png">
-Figure 5.6. HTTP Request for Jakarta Project Guidelines Page</figure>
+Figure §-num;.6. HTTP Request for Jakarta Project Guidelines Page</figure>
</section>
-<section name="5.5 Adding a Listener to View Store the Test Results" anchor="adding_listener">
+<section name="§-num;.5 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 HTTP requests in a file and presenting
@@ -197,43 +202,7 @@
Browse button and browse to a directory and then enter a filename.</p>
<figure image="graph_results.png">
-Figure 5.7. Graph Results Listener</figure>
-
-</section>
-
-<section name="5.6 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.</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="5.7 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>
-
-<p>The numbers to the left of the green square show the currently active and total number of threads.</p>
-
-<p>Once JMeter has finished running your Test Plan, the green box will turn to grey.
-If you wish to stop the test plan earlier, select Shutdown or Stop from the
-Run menu.</p>
-<p>If you selected a file to save the results to in your listener, then you will have a file that can be
-opened in any visualizer. Each visualizer will display the results in its own fashion.</p>
-
-<note>It is possible to have the same file open in more than one visualizer. This is not a problem. JMeter
-will ensure during the test run that no sample is recorded to the same file more than once (this only applies to XML format samples).</note>
+Figure §-num;.7. Graph Results Listener</figure>
</section>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ws-test-plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ws-test-plan.xml?rev=567775&r1=567774&r2=567775&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ws-test-plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/build-ws-test-plan.xml Mon Aug 20 11:07:53 2007
@@ -15,10 +15,11 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
-<!DOCTYPE document
-[
+
+<!DOCTYPE document[
<!ENTITY sect-num '10'>
]>
+
<document prev="build-ldapext-test-plan.html" next="build-jms-point-to-point-test-plan.html" date="$Date$">
<properties>
@@ -185,14 +186,6 @@
Figure §-num;.7. Graph Results Listener</figure>
</section>
-
-<section name="§-num;.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.</p>
-
-</section>
-
</body>
</document>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/get-started.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/get-started.xml?rev=567775&r1=567774&r2=567775&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/get-started.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/get-started.xml Mon Aug 20 11:07:53 2007
@@ -15,6 +15,11 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
+
+<!DOCTYPE document[
+<!ENTITY sect-num '2'>
+]>
+
<document prev="intro.html" next="build-test-plan.html" date="$Date$">
<properties>
@@ -22,7 +27,7 @@
</properties>
<body>
-<section name="2. Getting Started" anchor="get_started">
+<section name="§-num;. Getting Started" anchor="get_started">
<p>The easiest way to begin using JMeter is to first
<a href="http://jakarta.apache.org/site/downloads/index.html">download the latest production release</a> and install it.
The release contains all of the files you need to build and run most types of tests,
@@ -66,10 +71,10 @@
over your Test Plans.</p>
</section>
-<section name="2.1 Requirements" anchor="requirements">
+<section name="§-num;.1 Requirements" anchor="requirements">
<p>JMeter requires your computing environment meets some minimum requirements.</p>
-<subsection name="2.1.1 Java Version" anchor="java_versions">
+<subsection name="§-num;.1.1 Java Version" anchor="java_versions">
<note>JMeter requires a fully compliant JVM 1.4 or higher.
<br/>
Version 2.2 and later no longer support Java 1.3.
@@ -78,7 +83,7 @@
JMeter because of JRE implementation issues.</p>
</subsection>
-<subsection name="2.1.2 Operating Systems" anchor="os">
+<subsection name="§-num;.1.2 Operating Systems" anchor="os">
<p>JMeter is a 100% Java application and should run correctly on any system
that has a compliant Java implementation.<br/>
JMeter has been tested and works under:
@@ -92,28 +97,28 @@
</subsection>
</section>
-<section name="2.2 Optional" anchor="optional">
+<section name="§-num;.2 Optional" anchor="optional">
<p>If you plan on doing JMeter development or want to use Sun's Java Standard Extension packages, then you will need one or more optional packages listed below.</p>
-<subsection name="2.2.1 Java Compiler" anchor="opt_compiler">
+<subsection name="§-num;.2.1 Java Compiler" anchor="opt_compiler">
<p>If you want to build the JMeter source or develop JMeter plugins, then you will need a fully compliant JDK 1.4 or higher.</p>
</subsection>
-<subsection name="2.2.2 SAX XML Parser" anchor="opt_sax">
+<subsection name="§-num;.2.2 SAX XML Parser" anchor="opt_sax">
<p>JMeter comes with Apache's <a href="http://xml.apache.org/">Xerces XML parser</a>. You have the option of telling JMeter
to use a different XML parser. To do so, include the classes for the third-party parser in JMeter's <a href="#classpath">classpath</a>,
and update the <a href="#configuring_jmeter">jmeter.properties</a> file with the full classname of the parser
implementation.</p>
</subsection>
-<subsection name="2.2.3 Email Support" anchor="opt_email">
+<subsection name="§-num;.2.3 Email Support" anchor="opt_email">
<p>JMeter has limited Email capabilities. It can send email based on test results, and has a POP/IMAP sampler.
It does not currently support SMTP sampling.
To enable Email support, add Sun's JavaMail packages and the activation packages to JMeter's <a href="#classpath">classpath</a>.</p>
</subsection>
-<subsection name="2.2.4 SSL Encryption" anchor="opt_ssl">
+<subsection name="§-num;.2.4 SSL Encryption" anchor="opt_ssl">
<p>To test a web server using SSL encryption (HTTPS), JMeter requires that an
implementation of SSL be provided, as is the case with Sun Java 1.4 and above.
If your version of Java does not include SSL support, then it is possible to add an external implementation.
@@ -127,22 +132,22 @@
<note>The JMeter proxy server (see below) does not support recording SSL (https).</note>
</subsection>
-<subsection name="2.2.5 JDBC Driver" anchor="opt_jdbc">
+<subsection name="§-num;.2.5 JDBC Driver" anchor="opt_jdbc">
<p>You will need to add your database vendor's JDBC driver to the <a href="#classpath">classpath</a> if you want to do JDBC testing.
Make sure the file is a jar file, not a zip.
</p>
</subsection>
-<subsection name="2.2.6 Apache SOAP" anchor="opt_soap">
+<subsection name="§-num;.2.6 Apache SOAP" anchor="opt_soap">
<p>Apache SOAP requires mail.jar and activation.jar. You need to download and copy these two jar files to your <b>jmeter/lib</b> directory. Once the files are in there, JMeter will automatically pick them up.</p>
</subsection>
-<subsection name="2.2.7 BeanShell" anchor="opt_beanshell">
+<subsection name="§-num;.2.7 BeanShell" anchor="opt_beanshell">
<p>To run the BeanShell function or any of the BeanShell test elements (sampler, timer etc),
you need to download the beanshell jar from <a href="http://www.beanshell.org/">http://www.beanshell.org/</a> and copy the jar file to the <b>jmeter/lib directory</b>, where JMeter will automatically pick it up.</p>
</subsection>
-<subsection name="2.2.7 Libraries for ActiveMQ 3.0" anchor="libraries_activemq">
+<subsection name="§-num;.2.7 Libraries for ActiveMQ 3.0" anchor="libraries_activemq">
<note>This list is probably out of date</note>
<p>The following libraries have to be supplied in the lib directory of JMeter:
<ol>
@@ -167,7 +172,7 @@
</note>
</section>
-<section name="2.3 Installation" anchor="install">
+<section name="§-num;.3 Installation" anchor="install">
<note>
Note: avoid installing JMeter in a path with spaces in the name.
@@ -180,12 +185,12 @@
</section>
-<section name="2.4 Running JMeter" anchor="running">
+<section name="§-num;.4 Running JMeter" anchor="running">
<br/>
<p>To run JMeter, run the jmeter.bat (for Windows) or jmeter (for Unix) file.
</p>
-<subsection name="2.4.1 JMeter's Classpath" anchor="classpath">
+<subsection name="§-num;.4.1 JMeter's Classpath" anchor="classpath">
<p>JMeter automatically finds classes from jars in the following directories:</p>
<ul>
<li>JMETER_HOME/lib - used for utility jars</li>
@@ -212,7 +217,7 @@
[This occurs with all Java programs, not just JMeter.]</p>
</subsection>
-<subsection name="2.4.2 Using a Proxy Server" anchor="proxy_server">
+<subsection name="§-num;.4.2 Using a Proxy Server" anchor="proxy_server">
<p>If you are testing from behind a firewall/proxy server, you may need to provide JMeter with
the firewall/proxy server hostname and port number. To do so, run the jmeter.bat/jmeter file
from a command line with the following parameters:</p>
@@ -230,7 +235,7 @@
This is not to be confused with the proxy settings described above, which are used when JMeter makes HTTP or HTTPS requests itself.</note>
</subsection>
-<subsection name="2.4.3 Non-GUI Mode (Command Line mode)" anchor="non_gui">
+<subsection name="§-num;.4.3 Non-GUI Mode (Command Line mode)" anchor="non_gui">
<p>For non-interactive testing, you may choose to run JMeter without the GUI. To do so, use
the following command options</p>
<p>-n This specifies JMeter is to run in non-gui mode</p>
@@ -243,7 +248,7 @@
<p><b>Example</b>: jmeter -n -t my_test.jmx -l log.jtl -H my.proxy.server -P 8000</p>
</subsection>
-<subsection name="2.4.4 Server Mode" anchor="server">
+<subsection name="§-num;.4.4 Server Mode" anchor="server">
<p>For <a href="remote-test.html">distributed testing</a>, run JMeter in server mode on the remote node(s), and then control the server(s) from the GUI.
You can also use non-GUI mode to run remote tests.
<note>The jmeter-server/jmeter-server.bat script should start rmiregistry for you with the appropriate classpath. If it fails to
@@ -256,7 +261,7 @@
<p><b>Example</b>: jmeter-server -H my.proxy.server -P 8000</p>
</subsection>
-<subsection name="2.4.5 Overriding Properties Via The Command Line" anchor="override">
+<subsection name="§-num;.4.5 Overriding Properties Via The Command Line" anchor="override">
<p>Java system properties, JMeter properties, and logging properties can be overriden directly on the command line (instead of modifying jmeter.properties).
To do so, use the following options:</p>
<p>-D[prop_name]=[value] - defines a java system property value.</p>
@@ -276,7 +281,7 @@
Attempts to use the -J flag to update log_level or log_file properties will have no effect.</b>
</p>
</subsection>
-<subsection name="2.4.6 Logging and error messages" anchor="logging">
+<subsection name="§-num;.4.6 Logging and error messages" anchor="logging">
<p>If JMeter detects an error, a message will be written to the log file.
The log file name is defined in the jmeter.properties file (or using the -j option, see below).
It defaults to <b>jmeter.log</b>, and will be found in the directory from which JMeter was launched.
@@ -310,7 +315,7 @@
<p>The log file can be helpful in determining the cause of an error,
as JMeter does not interrupt a test to display an error dialogue.</p>
</subsection>
-<subsection name="2.4.7 Full list of command-line options" anchor="options">
+<subsection name="§-num;.4.7 Full list of command-line options" anchor="options">
<p>Invoking JMeter as "jmeter -?" will print a list of all the command-line options.
These are shown below.</p>
<pre>
@@ -360,7 +365,7 @@
</section>
-<section name="2.5 Configuring JMeter" anchor="configuring_jmeter">
+<section name="§-num;.5 Configuring JMeter" anchor="configuring_jmeter">
<p>If you wish to modify the properties with which JMeter runs you need to
either modify the jmeter.properties in the /bin directory or create
your own copy of the jmeter.properties and specify it in the command line.
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/remote-test.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/remote-test.xml?rev=567775&r1=567774&r2=567775&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/remote-test.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/remote-test.xml Mon Aug 20 11:07:53 2007
@@ -15,6 +15,11 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
+
+<!DOCTYPE document[
+<!ENTITY sect-num '15'>
+]>
+
<document prev="listeners.html" next="best-practices.html" date="$Date$">
<properties>
@@ -23,7 +28,7 @@
<body>
-<section name="15. Remote Testing">
+<section name="§-num;. Remote Testing">
<p>In the event that your JMeter client machine is unable, performance-wise, to simulate
enough users to stress your server, an option exists to control multiple, remote JMeter
@@ -85,7 +90,7 @@
</note>
</p>
-<subsection name="15.1 Doing it Manually" anchor="detail_instructions">
+<subsection name="§-num;.1 Doing it Manually" anchor="detail_instructions">
<p>In some cases, the jmeter-server script may not work for you (if you are using an OS platform not anticipated by the JMeter developers). Here is how to start the JMeter servers (step 1 above) with a more manual process:</p>
<p><b>Step 1a: Start the RMI Registry</b></p>
<p>JMeter uses Remote Method Invocation (RMI) as the remote communication mechanism. Therefore, you need
@@ -106,7 +111,7 @@
<p>Steps 2 and 3 remain the same.</p>
</subsection>
-<subsection name="15.2 Tips" anchor="tips">
+<subsection name="§-num;.2 Tips" anchor="tips">
<p>If you're running Suse Linux, these tips may help. The default installation may enable the firewall. In that case, remote testing will not work properly. The following tips were contributed by Sergey Ten.</p>
<p>If you see connections refused, turn on debugging by passing the following options.</p>
rmiregistry -J-Dsun.rmi.log.debug=true
@@ -128,7 +133,7 @@
</ul>
<p>Also create a policy file and add [computer_name][computer_domain] line to /etc/hosts.</p>
</subsection>
-<subsection name="15.3 Using a different port" anchor="portchange">
+<subsection name="§-num;.3 Using a different port" anchor="portchange">
<p>By default, JMeter uses the standard RMI port 1099. It is possible to change this. For this to work successfully, all the following need to agree:</p>
<ul>
<li>On the server, start rmiregistry using the new port number</li>
Modified: jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/test_plan.xml
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/test_plan.xml?rev=567775&r1=567774&r2=567775&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/test_plan.xml (original)
+++ jakarta/jmeter/branches/rel-2-2/xdocs/usermanual/test_plan.xml Mon Aug 20 11:07:53 2007
@@ -15,6 +15,11 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
+
+<!DOCTYPE document[
+<!ENTITY sect-num '4'>
+]>
+
<document prev="build-test-plan.html" next="build-web-test-plan.html" date="$Date$">
<properties>
@@ -23,7 +28,7 @@
<body>
-<section name="4. Elements of a Test Plan">
+<section name="§-num;. Elements of a Test Plan">
<p>The Test Plan object has a checkbox called "Functional Testing". If selected, it
will cause JMeter to record the data returned from the server for each sample. If you have
@@ -35,7 +40,7 @@
<p>If you are not recording the data to file, this option makes no difference.</p>
<p>You can also use the Configuration button on a listener to decide what fields to save.</p>
-<subsection name="4.1 ThreadGroup" anchor="thread_group">
+<subsection name="§-num;.1 ThreadGroup" anchor="thread_group">
<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
@@ -75,7 +80,7 @@
Note that delay overrides start-time, and duration over-rides end-time.</p>
</subsection>
-<subsection name="4.2 Controllers" anchor="controllers">
+<subsection name="§-num;.2 Controllers" anchor="controllers">
<p> JMeter has two types of Controllers: Samplers and Logical Controllers.</p>
@@ -93,7 +98,7 @@
</subsection>
-<subsection name="4.2.1 Samplers" anchor="samplers">
+<subsection name="§-num;.2.1 Samplers" anchor="samplers">
<p>Samplers tell JMeter to send requests to a server.
JMeter samplers include:
@@ -128,7 +133,7 @@
<p><a href="component_reference.html#samplers">JMeter's built-in samplers</a></p>
</subsection>
-<subsection name="4.2.2 Logic Controllers" anchor="logic_controller">
+<subsection name="§-num;.2.2 Logic Controllers" anchor="logic_controller">
<p>Logic Controllers let you customize the logic that JMeter uses to
decide when to send requests. Logic Controllers may have as child elements any
of the following: Samplers (requests), Configuration Elements, and other Logic
@@ -211,7 +216,7 @@
Logic Controllers</a>.</p>
</subsection>
-<subsection name="4.3 Listeners" anchor="listeners">
+<subsection name="§-num;.3 Listeners" anchor="listeners">
<p>Listeners provide access to the information JMeter gathers about the test cases while
JMeter runs. The <complink name="Graph
Results"/> listener plots the response times on a graph.
@@ -233,7 +238,7 @@
that come with JMeter.</p>
</subsection>
-<subsection name="4.4 Timers" anchor="timers">
+<subsection name="§-num;.4 Timers" anchor="timers">
<p>By default, a JMeter thread sends requests without pausing between each request.
We recommend that you specify a delay by adding one of the available timers to
@@ -248,7 +253,7 @@
the timers and pauses for that amount of time before executing the samplers to which they apply.</p>
</subsection>
-<subsection name="4.5 Assertions" anchor="assertions">
+<subsection name="§-num;.5 Assertions" anchor="assertions">
<p>Assertions allow you to assert facts about responses received from the
server being tested. Using an assertion, you can essentially "test" that your
@@ -270,7 +275,7 @@
</p>
</subsection>
-<subsection name="4.6 Configuration Elements" anchor="config_elements">
+<subsection name="§-num;.6 Configuration Elements" anchor="config_elements">
<p>A configuration element works closely with a Sampler. Although it does not send requests
(except for <complink name="HTTP Proxy Server"/>), it can add to or modify requests.</p>
@@ -287,15 +292,15 @@
Test Plan Showing Accessability of Configuration Elements</figure>
</subsection>
-<subsection name="4.7 Pre-Processor Elements" anchor="preprocessors">
+<subsection name="§-num;.7 Pre-Processor Elements" anchor="preprocessors">
<p>A Pre-Processor executes some action prior to a Sampler Request being made. If a Pre-Processor is attached to a Sampler element, then it will execute just prior to that sampler element running. A Pre-Processor is most often used to modify the settings of a Sample Request just before it runs, or to update variables that aren't extracted from response text. See the <scope>scoping rules</scope> for more details on when Pre-Processors are executed.</p>
</subsection>
-<subsection name="4.8 Post-Processor Elements" anchor="postprocessors">
+<subsection name="§-num;.8 Post-Processor Elements" anchor="postprocessors">
<p>A Post-Processor executes some action after a Sampler Request has been made. If a Post-Processor is attached to a Sampler element, then it will execute just after that sampler element runs. A Post-Processor is most often used to process the response data, often to extract values from it. See the <scope>scoping rules</scope> for more details on when Pre-Processors are executed.</p>
</subsection>
-<subsection name="4.9 Execution order" anchor="executionorder">
+<subsection name="§-num;.9 Execution order" anchor="executionorder">
<ol>
<li>Pre-Processors</li>
<li>Timers</li>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org