mirror of https://github.com/apache/jmeter.git
Text cleanup.
git-svn-id: https://svn.apache.org/repos/asf/jakarta/jmeter/trunk@322757 13f79535-47bb-0310-9956-ffa450edef68
Former-commit-id: 6a4c953acb
This commit is contained in:
khammond
parent
c35ffd693e
commit
1c30754ac8
|
|
@ -74,55 +74,55 @@ by registering the SSL Provider.</p>
|
|||
|
||||
|
||||
<section name="2.3 Installation" anchor="install">
|
||||
<p>Blah, blah, blah.</p>
|
||||
</section>
|
||||
|
||||
<section name="2.3.1 Downloading the Latest Release" anchor="download_release">
|
||||
<p>We recommend that most users run the <a href="http://jakarta.apache.org/builds/jakarta-jmeter/release/">latest release</a>.</p>
|
||||
<p>To install from a release build, simply unzip the zip/tar file into the directory
|
||||
where you want JMeter to be installed. Provided you have a JDK correctly installed,
|
||||
and JAVA_HOME environment variable set, there is nothing more to do.</p>
|
||||
<p>To install a release build, simply unzip the zip/tar file into the directory
|
||||
where you want JMeter to be installed. Provided that you have a JDK correctly installed
|
||||
and the JAVA_HOME environment variable set, there is nothing more for you to do.</p>
|
||||
</section>
|
||||
|
||||
<section name="2.3.2 Downloading Nightly Builds" anchor="download_nightly">
|
||||
<p>If you do not mind working with beta-quality software, then you can download and run the <a href="http://jakarta.apache.org/builds/jakarta-jmeter/nightly">latest nightly build</a>.</p>
|
||||
<p>To install from a nightly build, you must build JMeter. To do so, unzip the zip/tar file into the directory where you want JMeter
|
||||
to be installed. Then, open a shell or command prompt and change directory to JMeter's top
|
||||
level directory. Next, type "build install" to install JMeter. Provided your system has
|
||||
a JDK correctly installed and the JAVA_HOME environment variable set, JMeter should
|
||||
install correctly.</p>
|
||||
<p>To install a nightly build, unzip the zip/tar file into the directory where you want JMeter
|
||||
to be installed. Then, open a shell or command prompt and change to JMeter's top-level directory.
|
||||
Next, type "build install". Provided that you have a JDK correctly installed
|
||||
and the JAVA_HOME environment variable set, JMeter should be installed successfully.</p>
|
||||
</section>
|
||||
|
||||
<section name="2.4 Running JMeter" anchor="running">
|
||||
<p>To run JMeter, run the jmeter.bat (for Windows) or jmeter (for Unix) file.</p>
|
||||
|
||||
<p>If JMeter does not start correctly, it may be because your system does not support
|
||||
the commands contained in jmeter.bat/jmeter. In this case,
|
||||
you will need to rewrite the jmeter.bat/jmeter file to explicitly include all
|
||||
jar files found in JMeter's lib/ directory in JMeter's classpath.</p>
|
||||
the commands contained in jmeter.bat/jmeter. If this is the case,
|
||||
you will need to rewrite the jmeter.bat/jmeter file to explicitly include all
|
||||
JAR files that are located in JMeter's "lib" directory in the JMeter classpath.</p>
|
||||
</section>
|
||||
|
||||
<section name="2.4.1 JMeter's Classpath" anchor="classpath">
|
||||
<p>The jmeter.bat/jmeter file automatically adds all jar files found in JMeter's lib/
|
||||
directory. Because of this, if you need to add your own or third party jar files to
|
||||
JMeter's classpath, it is only required that you copy them into JMeter's lib/
|
||||
directory. </p>
|
||||
<p>The jmeter.bat/jmeter file automatically adds all JAR files that are located in JMeter's "lib"
|
||||
directory to JMeter's classpath. If you want to add other JAR files to JMeter's classpath, then
|
||||
you must copy them to JMeter's "lib" directory.</p>
|
||||
</section>
|
||||
|
||||
<section name="2.4.2 Using a Proxy Server" anchor="proxy_server">
|
||||
<p>If you are testing a system behind a firewall, you may need to tell JMeter to
|
||||
use a proxy server. To do so, use the jmeter.bat/jmeter file from a command line to start
|
||||
JMeter, and include two options:<br/>
|
||||
-h [proxy server hostname or ip address]<br/>
|
||||
-p [proxy server port]<br/>
|
||||
<b>eg.</b>: jmeter -h my.proxy.server -p 8000
|
||||
</p>
|
||||
<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>
|
||||
<p>-h [proxy server hostname or ip address]<br/>
|
||||
-p [proxy server port]</p>
|
||||
<p><b>Example</b>: jmeter -h my.proxy.server -p 8000</p>
|
||||
</section>
|
||||
|
||||
<section name="2.4.3 Non-GUI Mode" anchor="non_gui">
|
||||
<p>To run JMeter without the GUI, invoke the nongui.bat/nongui.sh files from the
|
||||
command line, with the -o option (-o [name of *.jmx file that describes entire test script]).<br/>
|
||||
<b>eg:</b> nongui -o my_test.jmx -h [proxy server] -p [proxy port]</p>
|
||||
<p>For non-interactive testing, you may choose to run JMeter without the GUI. Run the
|
||||
nongui.bat/nongui.sh script has one required parameter:</p>
|
||||
<p>-o [name of JMX file that contains the Test Plan].</p>
|
||||
<p>The script also lets you specify the optional firewall/proxy server information:</p>
|
||||
<p>-h [proxy server hostname or ip address]<br/>
|
||||
-p [proxy server port]</p>
|
||||
<p><b>Example</b>: nongui -o my_test.jmx -h my.proxy.server -p 8000</p>
|
||||
</section>
|
||||
|
||||
</body>
|
||||
|
|
|
|||
Loading…
Reference in New Issue