mstover1 2003/06/11 12:01:32
Modified: docs/images/screenshots modification.png
docs/images/screenshots/gen-controller http-request.png
docs/images/screenshots/webtest threadgroup.png
threadgroup2.png
docs/usermanual component_reference.html remote-test.html
src/core/org/apache/jmeter/swing HtmlPane.java
xdocs/usermanual component_reference.xml remote-test.xml
Added: docs/images/screenshots testplan.png threadgroup.png
url_rewriter.png workbench.png
docs/images/screenshots/assertion example1a.png
docs/images/screenshots/http-config
http-request-defaults.png
Removed: docs/images/screenshots test_plan.gif url_rewriter.gif
docs/images/screenshots/assertion example1a.gif
docs/images/screenshots/http-config
http-request-defaults.gif
Log:
Doc updates
Revision Changes Path
1.4 +50 -36 jakarta-jmeter/docs/images/screenshots/modification.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/testplan.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/threadgroup.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/url_rewriter.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/workbench.png
<<Binary file>>
1.1 jakarta-jmeter/docs/images/screenshots/assertion/example1a.png
<<Binary file>>
1.5 +31 -21
jakarta-jmeter/docs/images/screenshots/gen-controller/http-request.png
<<Binary file>>
1.1
jakarta-jmeter/docs/images/screenshots/http-config/http-request-defaults.png
<<Binary file>>
1.2 +14 -58 jakarta-jmeter/docs/images/screenshots/webtest/threadgroup.png
<<Binary file>>
1.2 +23 -69 jakarta-jmeter/docs/images/screenshots/webtest/threadgroup2.png
<<Binary file>>
1.44 +124 -9 jakarta-jmeter/docs/usermanual/component_reference.html
Index: component_reference.html
===================================================================
RCS file: /home/cvs/jakarta-jmeter/docs/usermanual/component_reference.html,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- component_reference.html 11 Jun 2003 15:38:31 -0000 1.43
+++ component_reference.html 11 Jun 2003 19:01:30 -0000 1.44
@@ -162,6 +162,9 @@
</ul>
<li><a href="#Miscellaneous_Features">13.9 Miscellaneous
Features</a></li>
<ul>
+ <li><a href="#Test_Plan">Test Plan</a></li>
+ <li><a href="#Thread_Group">Thread
Group</a></li>
+ <li><a href="#WorkBench">WorkBench</a></li>
<li><a href="#SSL_Manager">SSL Manager</a></li>
</ul>
<li><a href="#functions">13.10 Functions</a></li>
@@ -391,7 +394,8 @@
<i >
value
</i>
- . The query
string will be generated in the correct fashion, depending on
+ , the options
to encode the parameter, and an option to include or exclude an equals sign (some
applications
+ don't expect an equals when the value is the empty string). The query
string will be generated in the correct fashion, depending on
the choice of "Method" you made (ie if you chose GET, the query string will
be
appended to the URL, if POST, then it will be sent separately). Also, if
you are
sending a file using a multipart form, the query string will be created
using the
@@ -969,7 +973,7 @@
</a>
this example
(see Figure 1). In this example,
we configured the Thread Group to have two threads and a loop count of five, for a
total of ten
-requests. See the table below for the sequence JMeter sends the HTTP Requests.
+requests per thread. See the table below for the sequence JMeter sends the HTTP
Requests.
</p>
@@ -1485,7 +1489,7 @@
<p >
The Module Controller
provides a mechanism for substituting test plan fragments into the current test plan
at run-time. To use this
module effectively, one might have a number of Controllers under the
-
<a href="../usermanual/component_reference.html#Workbench">Workbench</a>
+
<a href="../usermanual/component_reference.html#WorkBench">WorkBench</a>
, each with a
different series of
samplers under them. The module controller can then be used to easily switch
between these multiple test cases simply by choosing
the appropriate controller in it's drop down box. This provides convenience for
running many alternate test plans quickly and easily.
@@ -1496,8 +1500,7 @@
<p><b>Control Panel</b></p>
<div align="center"><img
src="../images/screenshots/module_controller.png"></div>
<p><table border="1" bgcolor="#bbbb00" width="50%" cellspacing="0"
cellpadding="2">
- <tr><td> The Module
Controller should not be used with remote testing since the Workbench test elements
are not part of remote testing, and
-the test run will fail.
+ <tr><td> The Module
Controller should not be used with remote testing or non-gui testing in conjunction
with Workbench components since the Workbench test elements are not part of test plan
.jmx files. Any such test will fail.
</td></tr>
</table></p>
<p>
@@ -2469,7 +2472,7 @@
<p><b>Control Panel</b></p>
- <div align="center"><img
src="../images/screenshots/http-config/http-request-defaults.gif"></div>
+ <div align="center"><img
src="../images/screenshots/http-config/http-request-defaults.png"></div>
<p>
<b>Parameters</b>
<table border="1" cellspacing="0" cellpadding="2">
@@ -2930,7 +2933,7 @@
<p><b>Assertion Examples</b></p>
-
<p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img
src="../images/screenshots/assertion/example1a.gif"><br>
+
<p><table border="0" cellspacing="0" cellpadding="0"><tr><td><img
src="../images/screenshots/assertion/example1a.png"><br>
<font size="-1"> Figure 7 -
Test Plan
</font></td></tr></table></p>
@@ -3396,7 +3399,7 @@
<p><b>Control Panel</b></p>
- <div align="center"><img
src="../images/screenshots/url_rewriter.gif"></div>
+ <div align="center"><img
src="../images/screenshots/url_rewriter.png"></div>
<p>
<b>Parameters</b>
<table border="1" cellspacing="0" cellpadding="2">
@@ -3428,6 +3431,14 @@
No
</td>
</tr>
+ <tr>
+ <td>Do not use equals in path extension</td>
+ <td> Some web apps
rewrite URLs without using an "=" sign between the parameter name and value (such as
Intershop Enfinity).
+ </td>
+ <td>
+
No
+ </td>
+ </tr>
</table>
</p>
</td></tr>
@@ -3873,7 +3884,111 @@
<table border="0" cellspacing="0" cellpadding="2">
<tr><td>
<font face="arial,helvetica,sanserif">
- <a name="SSL_Manager"><h3>13.9.1 SSL Manager</h3></a>
+ <a name="Test_Plan"><h3>13.9.1 Test Plan</h3></a>
+ </font>
+ </td></tr>
+ <tr><td>
+
<p
>
+ At the Test Plan
level, static variables can be defined that allow users to abstract values that are
repeated throughout their tests, such as server names. Here, one can instruct JMeter
to save the maximum sample information to file by selecting "functional testing".
Also, an option exists here to instruct JMeter to run the
+
<a href="../usermanual/component_reference.html#Thread_Group">Thread Group</a>
+ serially
rather than in parallel.
+ </p>
+
<p><b>Control Panel</b></p>
+ <div align="center"><img
src="../images/screenshots/testplan.png"></div>
+
</td></tr>
+ <tr><td><br></td></tr>
+ </table>
+ <hr>
+
<table
border="0" cellspacing="0" cellpadding="2">
+ <tr><td>
+ <font face="arial,helvetica,sanserif">
+ <a name="Thread_Group"><h3>13.9.2 Thread Group</h3></a>
+ </font>
+ </td></tr>
+ <tr><td>
+
<p
>
+ A Thread Group defines
a pool of users that will execute a particular test case against your server. In the
Thread Group GUI, you can control the number of users simulated (num of threads), the
ramp up time (how long it takes to start all the threads), the number of times to
perform the test, and optionally, a start and stop time for the test.
+ </p>
+
<p><b>Control Panel</b></p>
+ <div align="center"><img
src="../images/screenshots/threadgroup.png"></div>
+
<p>
+ <b>Parameters</b>
+ <table border="1" cellspacing="0" cellpadding="2">
+ <tr><th>Attribute</th><th>Description</th><th>Required</th></tr>
+ <tr>
+ <td>Name</td>
+ <td> Descriptive
name for this element that is shown in the tree.
+ </td>
+ <td>
+
No
+ </td>
+ </tr>
+ <tr>
+ <td>Number of Threads</td>
+ <td> Number of
users to simulate.
+ </td>
+ <td>
+
Yes
+ </td>
+ </tr>
+ <tr>
+ <td>Ramp-up Period</td>
+ <td> How long
JMeter should take to get all the threads started. If there are 10 threads and a
ramp-up time of 100 seconds, then each thread will begin 10 seconds after the previous
thread started, for a total time of 100 seconds to get the test fully up to speed.
+ </td>
+ <td>
+
Yes
+ </td>
+ </tr>
+ <tr>
+ <td>Loop Count</td>
+ <td> Number of
times to perform the test case. Alternatively, "forever" can be selected causing the
test to run until manually stopped.
+ </td>
+ <td>
+
No
+ </td>
+ </tr>
+ <tr>
+ <td>Start Time</td>
+ <td> If the
scheduler checkbox is selected, one can choose an absolute start time. When you start
your test, JMeter will wait until the specified start time to begin testing.
+ </td>
+ <td>
+
No
+ </td>
+ </tr>
+ <tr>
+ <td>End Time</td>
+ <td> If the
scheduler checkbox is selected, one can choose an absolute end time. When you start
your test, JMeter will wait until the specified start time to begin testing, and it
will stop at the specified end time.
+ </td>
+ <td>
+
No
+ </td>
+ </tr>
+ </table>
+ </p>
+ </td></tr>
+ <tr><td><br></td></tr>
+ </table>
+ <hr>
+
<table
border="0" cellspacing="0" cellpadding="2">
+ <tr><td>
+ <font face="arial,helvetica,sanserif">
+ <a name="WorkBench"><h3>13.9.3 WorkBench</h3></a>
+ </font>
+ </td></tr>
+ <tr><td>
+
<p
>
+ The WorkBench simply
provides a place to temporarily store test elements while not in use, for copy/paste
purposes, or any other purpose you desire. When you save your test plan, WorkBench
items are not saved with it. Your WorkBench can be saved independently, if you like
(right-click on WorkBench and choose Save).
+ </p>
+
<p><b>Control Panel</b></p>
+ <div align="center"><img
src="../images/screenshots/workbench.png"></div>
+
</td></tr>
+ <tr><td><br></td></tr>
+ </table>
+ <hr>
+
<table
border="0" cellspacing="0" cellpadding="2">
+ <tr><td>
+ <font face="arial,helvetica,sanserif">
+ <a name="SSL_Manager"><h3>13.9.4 SSL Manager</h3></a>
</font>
</td></tr>
<tr><td>
1.28 +68 -34 jakarta-jmeter/docs/usermanual/remote-test.html
Index: remote-test.html
===================================================================
RCS file: /home/cvs/jakarta-jmeter/docs/usermanual/remote-test.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- remote-test.html 11 Jun 2003 15:38:32 -0000 1.27
+++ remote-test.html 11 Jun 2003 19:01:31 -0000 1.28
@@ -134,14 +134,74 @@
overhead on the application server and thus your testing results will be
somewhat tainted. The recommended approach is to have one or more machines on
the same Ethernet segment as your application server that you configure to run
-the JMeterEngine. This will minimize the impact of the network on the test
+the JMeter Engine. This will minimize the impact of the network on the test
results without impacting the performance of the application serer
itself.
</p>
<p >
<b >
- Step 1: Start the RMI
Registry
+ Step 1: Start the
servers
+ </b>
+ </p>
+
<p >
+ To run JMeter in
remote node, start the JMeter server component on all machines you wish to run on by
running the
+
<b >
+
JMETER_HOME/bin/jmeter-server
+ </b>
+ (unix) or
+
<b >
+
JMETER_HOME/bin/jmeter-server.bat
+ </b>
+ (windows)
script.
+ </p>
+
<p >
+
<b >
+ Step 2: Add the server
IP to your client's Properties File
+ </b>
+ </p>
+
<p >
+ Edit the properties
file
+
<i >
+ on the controlling
JMeter machine
+ </i>
+ . In
/bin/jmeter.properties, find the property named, "remote_hosts", and
+add the value of your running JMeter server's IP address. Multiple such servers
can be added, comma-delimited.
+ </p>
+
<p >
+
<b >
+ Step 3: Start the
JMeter Client
+ </b>
+ </p>
+
<p >
+ Now you are ready to
start the controlling JMeter client. For MS-Windows, start the client with the script
"bin/jmeter.bat". For UNIX,
+use the script "bin/jmeter". You will notice that the Run menu contains two new
sub-menus: "Remote Start" and "Remote Stop"
+(see figure 1). These menus contain the client that you set in the properties file.
Use the remote start and stop instead of the
+normal JMeter start and stop menu items.
+ </p>
+
<p >
+
<img src="../images/screenshots/remote/run-menu00.gif" width="232"
height="156">
+ </img>
+
+
+
<br >
+ Figure 1 - Run Menu
+ </br>
+ </p>
+
<table
border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#828DA6">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="detail_instructions"><strong>10.1 Doing it
Manually</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+
<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 >
@@ -175,7 +235,7 @@
</p>
<p >
<b >
- Step 2: Start the
JMeter Server
+ Step 1b: Start the
JMeter Server
</b>
</p>
<p >
@@ -183,38 +243,12 @@
Use the "-s" option with the jmeter startup script ("jmeter -s").
</p>
<p >
-
<b >
- Step 3: Add the server
IP to your client's Properties File
- </b>
- </p>
-
<p >
- Edit the properties
file
-
<i >
- on the controlling
JMeter machine
- </i>
- . In
/bin/jmeter.properties, find the property named, "remote_hosts", and
-add the value of your running JMeter server's IP address. Multiple such servers
can be added, comma-delimited.
+ Steps 2 and 3 remain
the same.
</p>
-
<p >
-
<b >
- Step 4: Start the
JMeter Client
- </b>
- </p>
-
<p >
- Now you are ready to
start the controlling JMeter client. For MS-Windows, start the client with the script
"bin/jmeter.bat". For UNIX,
-use the script "bin/jmeter". You will notice that the Run menu contains two new
sub-menus: "Remote Start" and "Remote Stop"
-(see figure 1). These menus contain the client that you set in the properties file.
Use the remote start and stop instead of the
-normal JMeter start and stop menu items.
- </p>
-
<p >
-
<img src="../images/screenshots/remote/run-menu00.gif" width="232"
height="156">
- </img>
-
-
-
<br >
- Figure 1 - Run Menu
- </br>
- </p>
+ </blockquote>
+ </td></tr>
+ <tr><td><br></td></tr>
+ </table>
</blockquote>
</p>
</td></tr>
1.3 +1 -1 jakarta-jmeter/src/core/org/apache/jmeter/swing/HtmlPane.java
Index: HtmlPane.java
===================================================================
RCS file: /home/cvs/jakarta-jmeter/src/core/org/apache/jmeter/swing/HtmlPane.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- HtmlPane.java 11 Jun 2003 15:38:33 -0000 1.2
+++ HtmlPane.java 11 Jun 2003 19:01:31 -0000 1.3
@@ -13,7 +13,7 @@
*/
public class HtmlPane extends JTextPane
{
- Logger log = LoggingManager.getLoggerForClass();
+ private static Logger log = LoggingManager.getLoggerForClass();
public HtmlPane(){
this.addHyperlinkListener(
1.43 +31 -10 jakarta-jmeter/xdocs/usermanual/component_reference.xml
Index: component_reference.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/component_reference.xml,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- component_reference.xml 11 Jun 2003 15:49:30 -0000 1.42
+++ component_reference.xml 11 Jun 2003 19:01:32 -0000 1.43
@@ -74,7 +74,8 @@
"Send Parameters With the Request" section.</property>
<property name="Send Parameters With the Request" required="No">The query
string will
be generated from the list of parameters you provide. Each parameter has a
<i>name</i> and
- <i>value</i>. The query string will be generated in the correct fashion,
depending on
+ <i>value</i>, the options to encode the parameter, and an option to include
or exclude an equals sign (some applications
+ don't expect an equals when the value is the empty string). The query
string will be generated in the correct fashion, depending on
the choice of "Method" you made (ie if you chose GET, the query string will
be
appended to the URL, if POST, then it will be sent separately). Also, if
you are
sending a file using a multipart form, the query string will be created
using the
@@ -285,7 +286,7 @@
<p><a href="../demos/InterleaveTestPlan.jmx">Download</a> this example (see Figure
1). In this example,
we configured the Thread Group to have two threads and a loop count of five, for a
total of ten
-requests. See the table below for the sequence JMeter sends the HTTP Requests.</p>
+requests per thread. See the table below for the sequence JMeter sends the HTTP
Requests.</p>
<figure image="../images/screenshots/logic-controller/interleave.png">Figure 1 -
Interleave Controller Example 1</figure>
@@ -447,13 +448,12 @@
<component index="13.2.7" name="Module Controller"
screenshot="../images/screenshots/module_controller.png">
<description>
<p>The Module Controller provides a mechanism for substituting test plan fragments
into the current test plan at run-time. To use this
-module effectively, one might have a number of Controllers under the <complink
name="Workbench"/>, each with a different series of
+module effectively, one might have a number of Controllers under the <complink
name="WorkBench"/>, each with a different series of
samplers under them. The module controller can then be used to easily switch
between these multiple test cases simply by choosing
the appropriate controller in it's drop down box. This provides convenience for
running many alternate test plans quickly and easily.
</p>
</description>
-<note>The Module Controller should not be used with remote testing since the
Workbench test elements are not part of remote testing, and
-the test run will fail.</note>
+<note>The Module Controller should not be used with remote testing or non-gui
testing in conjunction with Workbench components since the Workbench test elements are
not part of test plan .jmx files. Any such test will fail.</note>
<properties>
<property name="Name" required="No">Descriptive name for this controller
that is shown in the tree.</property>
<property name="Module to Run" required="Yes">The module controller
provides a list of all controllers loaded into the gui. Select
@@ -810,7 +810,7 @@
</component>
<component index="13.4.4" name="HTTP Request Defaults"
- screenshot="../images/screenshots/http-config/http-request-defaults.gif">
+ screenshot="../images/screenshots/http-config/http-request-defaults.png">
<description><p>This element lets you set default values that your HTTP Request
controllers use. For example, if you are
creating a Test Plan with 25 HTTP Request controllers and all of the requests are
being sent to the same server,
you could add a single HTTP Request Defaults element with the "Server Name or IP"
field filled in. Then, when
@@ -952,7 +952,7 @@
</properties>
<example title="Assertion Examples" anchor="assertion_examples">
-<figure image="../images/screenshots/assertion/example1a.gif">Figure 7 - Test
Plan</figure>
+<figure image="../images/screenshots/assertion/example1a.png">Figure 7 - Test
Plan</figure>
<figure image="../images/screenshots/assertion/example1b.gif">Figure 8 - Assertion
Control Panel with Pattern</figure>
<figure image="../images/screenshots/assertion/example1c-pass.gif">Figure 9 -
Assertion Listener Results (Pass)</figure>
<figure image="../images/screenshots/assertion/example1c-fail.gif">Figure 10 -
Assertion Listener Results (Fail)</figure>
@@ -1110,7 +1110,7 @@
</component>
-<component index="13.7.2" name="HTTP URL Re-writing Modifier"
screenshot="../images/screenshots/url_rewriter.gif">
+<component index="13.7.2" name="HTTP URL Re-writing Modifier"
screenshot="../images/screenshots/url_rewriter.png">
<description><p>This modifier works similarly to the HTML Link Parser, except it
has a specific purpose for which
it is easier to use than the HTML Link Parser, and more efficient. For web
applications that
use URL Re-writing to store session ids instead of cookies, this element can be
attached at the
@@ -1129,6 +1129,7 @@
grab the value assigned to it, whether it's in an HREF or a form.</property>
<property name="Path Extension" required="No">Some web apps rewrite URLs by
appending
a semi-colon plus the session id parameter. Check this box if that is
so.</property>
+ <property name="Do not use equals in path extension" required="No">Some web
apps rewrite URLs without using an "=" sign between the parameter name and
value (such as Intershop Enfinity).</property>
</properties>
</component>
@@ -1247,7 +1248,27 @@
<section name="13.9 Miscellaneous Features" anchor="Miscellaneous_Features">
-<component index="13.9.1" name="SSL Manager" screenshot="">
+<component index="13.9.1" name="Test Plan"
screenshot="../images/screenshots/testplan.png">
+<description><p>At the Test Plan level, static variables can be defined that allow
users to abstract values that are repeated throughout their tests, such as server
names. Here, one can instruct JMeter to save the maximum sample information to file
by selecting "functional testing". Also, an option exists here to instruct JMeter to
run the <complink name="Thread Group"/> serially rather than in
parallel.</p></description>
+</component>
+
+<component index="13.9.2" name="Thread Group"
screenshot="../images/screenshots/threadgroup.png">
+<description><p>A Thread Group defines a pool of users that will execute a
particular test case against your server. In the Thread Group GUI, you can control
the number of users simulated (num of threads), the ramp up time (how long it takes to
start all the threads), the number of times to perform the test, and optionally, a
start and stop time for the test.</p></description>
+
+<properties>
+ <property name="Name" required="">Descriptive name for this element that is
shown in the tree.</property>
+ <property name="Number of Threads" required="Yes">Number of users to
simulate.</property>
+ <property name="Ramp-up Period" required="Yes">How long JMeter should take
to get all the threads started. If there are 10 threads and a ramp-up time of 100
seconds, then each thread will begin 10 seconds after the previous thread started, for
a total time of 100 seconds to get the test fully up to speed.</property>
+ <property name="Loop Count" required="No">Number of times to perform the
test case. Alternatively, "forever" can be selected causing the test to run until
manually stopped.</property>
+ <property name="Start Time" required="No">If the scheduler checkbox is
selected, one can choose an absolute start time. When you start your test, JMeter
will wait until the specified start time to begin testing.</property>
+ <property name="End Time" required="No">If the scheduler checkbox is
selected, one can choose an absolute end time. When you start your test, JMeter will
wait until the specified start time to begin testing, and it will stop at the
specified end time.</property></properties>
+</component>
+
+<component index="13.9.3" name="WorkBench"
screenshot="../images/screenshots/workbench.png">
+<description><p>The WorkBench simply provides a place to temporarily store test
elements while not in use, for copy/paste purposes, or any other purpose you desire.
When you save your test plan, WorkBench items are not saved with it. Your WorkBench
can be saved independently, if you like (right-click on WorkBench and choose
Save).</p></description>
+</component>
+
+<component index="13.9.4" name="SSL Manager" screenshot="">
<p>
The SSL Manager is a way to select a client certificate so that you can test
applications that use Public Key Infrastructure (PKI). In order to use it,
1.11 +24 -14 jakarta-jmeter/xdocs/usermanual/remote-test.xml
Index: remote-test.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/remote-test.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- remote-test.xml 11 Jun 2003 15:49:30 -0000 1.10
+++ remote-test.xml 11 Jun 2003 19:01:32 -0000 1.11
@@ -30,12 +30,29 @@
overhead on the application server and thus your testing results will be
somewhat tainted. The recommended approach is to have one or more machines on
the same Ethernet segment as your application server that you configure to run
-the JMeterEngine. This will minimize the impact of the network on the test
+the JMeter Engine. This will minimize the impact of the network on the test
results without impacting the performance of the application serer
itself.
</p>
-<p><b>Step 1: Start the RMI Registry</b></p>
+<p><b>Step 1: Start the servers </b></p>
+<p>To run JMeter in remote node, start the JMeter server component on all machines
you wish to run on by running the <b>JMETER_HOME/bin/jmeter-server</b> (unix) or
<b>JMETER_HOME/bin/jmeter-server.bat</b> (windows) script.</p>
+
+<p><b>Step 2: Add the server IP to your client's Properties File</b></p>
+<p>Edit the properties file <i>on the controlling JMeter machine</i>. In
/bin/jmeter.properties, find the property named, "remote_hosts", and
+add the value of your running JMeter server's IP address. Multiple such servers
can be added, comma-delimited.</p>
+
+<p><b>Step 3: Start the JMeter Client</b></p>
+<p>Now you are ready to start the controlling JMeter client. For MS-Windows, start
the client with the script "bin/jmeter.bat". For UNIX,
+use the script "bin/jmeter". You will notice that the Run menu contains two new
sub-menus: "Remote Start" and "Remote Stop"
+(see figure 1). These menus contain the client that you set in the properties file.
Use the remote start and stop instead of the
+normal JMeter start and stop menu items.</p>
+<p><img src="../images/screenshots/remote/run-menu00.gif" width="232"
height="156"></img>
+<br>Figure 1 - Run Menu</br></p>
+
+<subsection name="10.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
to run the RMI Registry application (which is named, "rmiregistry") that comes with
the JDK and is located in the "bin"
directory. Before running rmiregistry, make sure that the following jars are in
your system claspath:
@@ -48,21 +65,14 @@
rmiregistry application needs access to certain JMeter classes. Run rmiregistry
with no parameters. By default the
application listens to port 1099.</p>
-<p><b>Step 2: Start the JMeter Server</b></p>
+<p><b>Step 1b: Start the JMeter Server</b></p>
<p>Once the RMI Registry application is running, start the JMeter Server.
Use the "-s" option with the jmeter startup script ("jmeter -s").</p>
-<p><b>Step 3: Add the server IP to your client's Properties File</b></p>
-<p>Edit the properties file <i>on the controlling JMeter machine</i>. In
/bin/jmeter.properties, find the property named, "remote_hosts", and
-add the value of your running JMeter server's IP address. Multiple such servers
can be added, comma-delimited.</p>
+<p>Steps 2 and 3 remain the same.</p>
+</subsection>
+
-<p><b>Step 4: Start the JMeter Client</b></p>
-<p>Now you are ready to start the controlling JMeter client. For MS-Windows, start
the client with the script "bin/jmeter.bat". For UNIX,
-use the script "bin/jmeter". You will notice that the Run menu contains two new
sub-menus: "Remote Start" and "Remote Stop"
-(see figure 1). These menus contain the client that you set in the properties file.
Use the remote start and stop instead of the
-normal JMeter start and stop menu items.</p>
-<p><img src="../images/screenshots/remote/run-menu00.gif" width="232"
height="156"></img>
-<br>Figure 1 - Run Menu</br></p>
</section>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
