Synchronise recent doc updates

git-svn-id: https://svn.apache.org/repos/asf/jakarta/jmeter/branches/rel-2-2@567777 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Sebastian Bazley 2007-08-20 18:12:01 +00:00
parent e48290c4d7
commit 31b59e9d2f
12 changed files with 123 additions and 349 deletions

View File

@ -444,58 +444,7 @@ Figure 7.7. Graph results Listener
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="saving"><strong>7.4 Saving the Test Plan</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p >
Although it is not required, we recommend that you save the Test Plan to a
file before running it. To save the Test Plan, select Save Test Plan from the
File menu (with the latest release, it is no longer necessary to select the
Test Plan element first).
</p>
<p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
<tr><td> JMeter allows you to save the entire Test Plan tree or
only a portion of it. To save only the elements located in a particular "branch"
of the Test Plan tree, select the Test Plan element in the tree from which to start
the "branch", and then click your right mouse button to access the Save As menu item.
Alternatively, select the appropriate Test Plan element and then select Save As from
the Edit menu.
</td></tr>
</table></p>
</blockquote>
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="running"><strong>7.5 Running the Test Plan</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p >
From the Run menu, select Run.
</p>
<p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
<tr><td> JMeter lights up a green square in the upper-right-hand corner to indicate if a
test is currently running. The square is turned gray when all tests stop. Even after
you select "stop", the green light will stay on until all test threads have exited.
</td></tr>
</table></p>
</blockquote>
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="running"><strong>7.7 JDBC settings</strong></a>
<a name="jdbc_settings"><strong>7.4 JDBC settings</strong></a>
</font>
</td></tr>
<tr><td>

View File

@ -444,57 +444,6 @@ Figure 8.7. Spline Visualizer Listener
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="saving"><strong>8.5 Saving the Test Plan</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p >
Although it is not required, we recommend that you save the Test Plan to a
file before running it. To save the Test Plan, select Save Test Plan from the
File menu (with the latest release, it is no longer necessary to select the
Test Plan element first).
</p>
<p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
<tr><td> JMeter allows you to save the entire Test Plan tree or
only a portion of it. To save only the elements located in a particular "branch"
of the Test Plan tree, select the Test Plan element in the tree from which to start
the "branch", and then click your right mouse button to access the Save As menu item.
Alternatively, select the appropriate Test Plan element and then select Save As from
the Edit menu.
</td></tr>
</table></p>
</blockquote>
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="running"><strong>8.6 Running the Test Plan</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p >
From the Run menu, select Run.
</p>
<p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
<tr><td> JMeter lights up a green square in the upper-right-hand corner to indicate if a
test is currently running. The square is turned gray when all tests stop. Even after
you select "stop", the green light will stay on until all test threads have exited.
</td></tr>
</table></p>
</blockquote>
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table>
<tr>

View File

@ -545,24 +545,6 @@ Figure 11.2. Graph Results Listener
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="saving"><strong>11.4 Saving the Test Plan</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p >
Although it is not required, we recommend that you save the Test Plan to a
file before running it. To save the Test Plan, select Save Test Plan from the
File menu.
</p>
</blockquote>
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table>
<tr>

View File

@ -473,24 +473,6 @@ Figure 12.4. Graph Results Listener
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="saving"><strong>12.4 Saving the Test Plan</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p >
Although it is not required, we recommend that you save the Test Plan to a
file before running it. To save the Test Plan, select Save Test Plan from the
File menu.
</p>
</blockquote>
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table>
<tr>

View File

@ -28,9 +28,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<meta name="author" value="Elanjchezhiyan.T">
<meta name="email" value="chezhiyan@siptech.co.in">
<title>JMeter - User's Manual: Building an LDAP Test Plan</title>
</head>
@ -132,7 +130,7 @@
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="building"><strong>9. Building an LDAP Test Plan</strong></a>
<a name="building"><strong>9a. Building an LDAP Test Plan</strong></a>
</font>
</td></tr>
<tr><td>
@ -169,7 +167,7 @@ repeat 2 times) = 32 LDAP requests. To construct the Test Plan, you will use the
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="adding_users"><strong>9.1 Adding Users</strong></a>
<a name="adding_users"><strong>9a.1 Adding Users</strong></a>
</font>
</td></tr>
<tr><td>
@ -187,7 +185,7 @@ clicking on the Test Plan element.
<p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/ldaptest/threadgroup.png"><br>
<font size="-1">
Figure 9.1. Thread Group with Default Values
Figure 9a.1. Thread Group with Default Values
</font></td></tr></table></p>
@ -201,7 +199,7 @@ Figure 9.1. Thread Group with Default Values
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="add_login"><strong>9.2 Adding Login Config Element</strong></a>
<a name="add_login"><strong>9a.2 Adding Login Config Element</strong></a>
</font>
</td></tr>
<tr><td>
@ -217,7 +215,7 @@ field that you can modify. In this example, leave this field with the default va
</p>
<p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/ldaptest/login-config-element.png"><br>
<font size="-1">
Figure 9.2 Login Config Element for our Test Plan
Figure 9a.2 Login Config Element for our Test Plan
</font></td></tr></table></p>
<p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
<tr><td> <p >
@ -243,7 +241,7 @@ field that you can modify. In this example, leave this field with the default va
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="add_defaults"><strong>9.3 Adding LDAP Request Defaults</strong></a>
<a name="add_defaults"><strong>9a.3 Adding LDAP Request Defaults</strong></a>
</font>
</td></tr>
<tr><td>
@ -259,7 +257,7 @@ field that you can modify. In this example, leave this field with the default va
</p>
<p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/ldaptest/requestdefaults.png"><br>
<font size="-1">
Figure 9.3 LDAP Defaults for our Test Plan
Figure 9a.3 LDAP Defaults for our Test Plan
</font></td></tr></table></p>
<p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
<tr><td> Enter DN field to "your Server Root Dn".
@ -285,7 +283,7 @@ field that you can modify. In this example, leave this field with the default va
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="add_requests"><strong>9.4 Adding LDAP Requests</strong></a>
<a name="add_requests"><strong>9a.4 Adding LDAP Requests</strong></a>
</font>
</td></tr>
<tr><td>
@ -339,7 +337,7 @@ and edit the following properties
</ol>
<p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/ldaptest/add.png"><br>
<font size="-1">
Figure 9.4.1 LDAP Request for Inbuilt Add test
Figure 9a.4.1 LDAP Request for Inbuilt Add test
</font></td></tr></table></p>
<p >
You do not have to set the Server Name field, port field, Username, Password
@ -366,7 +364,7 @@ properties
</ol>
<p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/ldaptest/modify.png"><br>
<font size="-1">
Figure 9.4.2 LDAP Request for Inbuilt Modify test
Figure 9a.4.2 LDAP Request for Inbuilt Modify test
</font></td></tr></table></p>
<ol >
@ -384,7 +382,7 @@ properties
</ol>
<p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/ldaptest/delete.png"><br>
<font size="-1">
Figure 9.4.3 LDAP Request for Inbuilt Delete test
Figure 9a.4.3 LDAP Request for Inbuilt Delete test
</font></td></tr></table></p>
<ol >
@ -402,7 +400,7 @@ properties
</ol>
<p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/ldaptest/search.png"><br>
<font size="-1">
Figure 9.4.4 LDAP Request for Inbuilt Search test
Figure 9a.4.4 LDAP Request for Inbuilt Search test
</font></td></tr></table></p>
</blockquote>
</p>
@ -412,7 +410,7 @@ properties
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="add_listener"><strong>9.5 Adding a Listener to View/Store the Test Results</strong></a>
<a name="add_listener"><strong>9a.5 Adding a Listener to View/Store the Test Results</strong></a>
</font>
</td></tr>
<tr><td>
@ -425,30 +423,12 @@ Users element and add a View Results in Table (Add --> Listener -->View Results
</p>
<p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/screenshots/ldaptest/viewtable.png"><br>
<font size="-1">
Figure 9.5 View result in Table Listener
Figure 9a.5 View result in Table Listener
</font></td></tr></table></p>
</blockquote>
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="saving"><strong>9.6 Saving the Test Plan</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p >
Although it is not required, we recommend that you save the Test Plan to a
file before running it. To save the Test Plan, select Save Test Plan from the
File menu.
</p>
</blockquote>
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table>
<tr>

View File

@ -28,9 +28,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<meta name="author" value="Dolf Smits">
<meta name="email" value="dolf.smits@siemens.com">
<title>JMeter - User's Manual: Building an Extended LDAP Test Plan</title>
</head>

View File

@ -403,24 +403,6 @@ performance or a bug of some sort.
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="saving"><strong>13.7 Saving the Test Plan</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p >
Although it is not required, we recommend that you save the Test Plan to a
file before running it. To save the Test Plan, select Save Test Plan from the
File menu.
</p>
</blockquote>
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table>
<tr>

View File

@ -216,7 +216,35 @@ configured for an element depends on what type of element it is.
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="run"><strong>3.4 Running a Test Plan</strong></a>
<a name="saving"><strong>3.4 Saving the Test Plan</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p >
Although it is not required, we recommend that you save the Test Plan to a
file before running it. To save the Test Plan, select Save Test Plan from the
File menu (with the latest release, it is no longer necessary to select the
Test Plan element first).
</p>
<p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
<tr><td> JMeter allows you to save the entire Test Plan tree or
only a portion of it. To save only the elements located in a particular "branch"
of the Test Plan tree, select the Test Plan element in the tree from which to start
the "branch", and then click your right mouse button to access the Save As menu item.
Alternatively, select the appropriate Test Plan element and then select Save As from
the Edit menu.
</td></tr>
</table></p>
</blockquote>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="run"><strong>3.5 Running a Test Plan</strong></a>
</font>
</td></tr>
<tr><td>
@ -257,7 +285,7 @@ There are two types of stop command:
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="scoping_rules"><strong>3.5 Scoping Rules</strong></a>
<a name="scoping_rules"><strong>3.6 Scoping Rules</strong></a>
</font>
</td></tr>
<tr><td>
@ -324,7 +352,7 @@ only one Manager is used, but there is currently no way to specify
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="error_reporting"><strong>3.6 Error reporting</strong></a>
<a name="error_reporting"><strong>3.7 Error reporting</strong></a>
</font>
</td></tr>
<tr><td>

View File

@ -464,73 +464,6 @@ Figure 5.7. Graph Results Listener
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="saving"><strong>5.6 Saving the Test Plan</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p >
Although it is not required, we recommend that you save the Test Plan to a
file before running it. To save the Test Plan, select Save Test Plan from the
File menu.
</p>
<p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
<tr><td> JMeter allows you to save the entire Test Plan tree or
only a portion of it. To save only the elements located in a particular "branch"
of the Test Plan tree, select the Test Plan element in the tree from which to start
the "branch", and then click your right mouse button to access the Save As menu item.
Alternatively, select the appropriate Test Plan element and then select Save As from
the Edit menu.
</td></tr>
</table></p>
</blockquote>
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="running"><strong>5.7 Running the Test Plan</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p >
From the Run menu, select Run.
</p>
<p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
<tr><td> JMeter lights up a green square in the upper-right-hand corner to indicate if a test is
currently running. The square is turned gray when all tests stop. Even after you select "stop",
the green light will stay on until all test threads have exited.
</td></tr>
</table></p>
<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>
<p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0" cellpadding="2">
<tr><td> 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).
</td></tr>
</table></p>
</blockquote>
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table>
<tr>

View File

@ -403,24 +403,6 @@ Figure 10.7. Graph Results Listener
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="saving"><strong>10.4 Saving the Test Plan</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p >
Although it is not required, we recommend that you save the Test Plan to a
file before running it. To save the Test Plan, select Save Test Plan from the
File menu.
</p>
</blockquote>
</p>
</td></tr>
<tr><td><br></td></tr>
</table>
<table>
<tr>

View File

@ -242,7 +242,7 @@
</a>
...
<a href="build-ldap-test-plan.html">
9. Building an LDAP Test Plan
9a. Building an LDAP Test Plan
</a>
</li>
@ -808,20 +808,6 @@
</a>
</li>
<li >
<a href="build-web-test-plan.html#saving">
5.6 Saving the Test Plan
</a>
</li>
<li >
<a href="build-web-test-plan.html#running">
5.7 Running the Test Plan
</a>
</li>
</ul>
@ -887,20 +873,6 @@
</a>
</li>
<li >
<a href="build-db-test-plan.html#saving">
7.4 Saving the Test Plan
</a>
</li>
<li >
<a href="build-db-test-plan.html#running">
7.5 Running the Test Plan
</a>
</li>
</ul>
@ -944,20 +916,6 @@
</a>
</li>
<li >
<a href="build-ftp-test-plan.html#saving">
8.5 Saving the Test Plan
</a>
</li>
<li >
<a href="build-ftp-test-plan.html#running">
8.6 Running the Test Plan
</a>
</li>
</ul>
@ -966,7 +924,7 @@
<a name="build-ldap-test-plan">
</a>
<a href="build-ldap-test-plan.html">
9. Building an LDAP Test Plan
9a. Building an LDAP Test Plan
</a>
</li>
@ -976,53 +934,82 @@
<li >
<a href="build-ldap-test-plan.html#adding_users">
9.1 Adding Users
9a.1 Adding Users
</a>
</li>
<li >
<a href="build-ldap-test-plan.html#add_login">
9.2 Adding Login Config Element
9a.2 Adding Login Config Element
</a>
</li>
<li >
<a href="build-ldap-test-plan.html#add_defaults">
9.3 Adding LDAP Request Defaults
9a.3 Adding LDAP Request Defaults
</a>
</li>
<li >
<a href="build-ldap-test-plan.html#add_requests">
9.4 Adding LDAP Requests
9a.4 Adding LDAP Requests
</a>
</li>
<li >
<a href="build-ldap-test-plan.html#add_listener">
9.5 Adding a Listener to View/Store the Test Results
</a>
</li>
<li >
<a href="build-ldap-test-plan.html#saving">
9.6 Saving the Test Plan
</a>
</li>
<li >
<a href="build-ldap-test-plan.html#running">
9.7 Running the Test Plan
9a.5 Adding a Listener to View/Store the Test Results
</a>
</li>
</ul>
<li >
<a name="build-ldap-test-plan">
</a>
<a href="build-ldap-test-plan.html">
9b. Building an Extended LDAP Test Plan
</a>
</li>
<ul >
<li >
<a href="build-ldapext-test-plan.html#ext_adding_users">
9b.1 Adding Users
</a>
</li>
<li >
<a href="build-ldapext-test-plan.html#add_login">
9b.2 Adding LDAP Extended Request Defaults
</a>
</li>
<li >
<a href="build-ldapext-test-plan.html#add_extrequests">
9b.3 Adding LDAP Requests
</a>
</li>
<li >
<a href="build-ldapext-test-plan.html#add_ldapext_listener">
9b.4 Adding a Listener to View/Store the Test Results
</a>
</li>
</ul>
@ -1094,21 +1081,21 @@
<li >
<a href="best-practices.html#limit_threads">
16.1 [ALL] Limit the Number of Threads
16.1 Limit the Number of Threads
</a>
</li>
<li >
<a href="best-practices.html#put_cookie_manager">
16.2 [HTTP] Where to Put the Cookie Manager
16.2 Where to Put the Cookie Manager
</a>
</li>
<li >
<a href="best-practices.html#put_auth_manager">
16.3 [HTTP] Where to Put the Authorization Manager
16.3 Where to Put the Authorization Manager
</a>
</li>
@ -1119,6 +1106,27 @@
</a>
</li>
<li >
<a href="best-practices.html#user_variables">
16.5 User variables
</a>
</li>
<li >
<a href="best-practices.html#lean_mean">
16.6 Reducing resource requirements
</a>
</li>
<li >
<a href="best-practices.html#beanshell_server">
16.7 BeanShell server
</a>
</li>
</ul>

View File

@ -432,6 +432,7 @@ $ SERVER_PORT=1664 jmeter-server [other options]
In both cases, the script starts rmiregistry on the specified port,
and then starts JMeter in server mode, having defined the "server_port" property.
</p>
<p >