Date: 2005-03-07T06:30:41
   Editor: MichaelStover
   Wiki: Apache JMeter Wiki
   Page: UserManual/GettingStarted
   URL: http://wiki.apache.org/jakarta-jmeter/UserManual/GettingStarted

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -11,7 +11,7 @@
 == Requirements ==
 
 JMeter requires your computing environment meets some minimum requirements.
-
+[[Anchor(javaversion)]]
 === Java Version ===
 
 JMeter version 1.8 requires a fully compliant JDK1.4 or higher.
@@ -19,7 +19,7 @@
 JMeter 1.8.1 and 1.9 requires a fully compliant JDK1.3 or higher. This may 
seem odd, but we are making a strong effort currently to be compatible with the 
1.3 JDK's, though it is expected JMeter performs best with 1.4 or better. 
Because JMeter uses only standard Java APIs (java.*), please do not file bug 
reports if your JRE fails to run JMeter because of JRE implementation issues.
 
 {{{JDK1.4.1Beta appears to be buggy, and there are some GUI elements that 
won't work correctly in this JVM.}}}
-
+[[Anchor(operatingsystems)]]
 === Operating Systems ===
 
 JMeter has been tested and works under Unix (Solaris, Linux, etc) and Windows 
(98, NT, 2000, XP). Also works on OpenVMS. JMeter is a 100% Java application 
and should run correctly on any system that has a compliant Java implementation.
@@ -27,19 +27,19 @@
 == Optional ==
 
 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.
-
+[[Anchor(javacompiler)]]
 === Java Compiler ===
 
 If you want to build the JMeter source or develop JMeter plugins, then you 
will need a fully compliant JDK1.3 (1.4 for JMeter 1.8) or higher compiler.
-
+[[Anchor(saxparser)]]
 === SAX XML Parser ===
 
 JMeter comes with [http://xml.apache.org Apache's Xerces XML parser]. 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 [#classpath classpath], and 
update the [#configuring jmeter.properties] file with the full classname of the 
parser implementation.
-
+[[Anchor(email)]]
 === Email Support ===
 
 JMeter has limited Email capabilities (it can send email based on test 
results). To enable Email support, add Sun's JavaMail packages and the 
activation packages to JMeter's [#classpath classpath].
-
+[[Anchor(ssl)]]
 === SSL Encryption ===
 
 To test a web server using SSL encryption (HTTPS), JMeter requires that an 
implementation of SSL be provided (such as Sun's 
[http://java.sun.com/products/jsse/index.jsp Java Secure Sockets Extension -- 
JSSE] ). Include the necessary encryption packages in JMeter's [#classpath 
classpath] . Also, update [#configuring jmeter.properties] by registering the 
SSL Provider.
@@ -47,11 +47,11 @@
 There is also the SSL Manager , for greater control of certs.
 
 {{{If you are running JDK1.4, then you do not have to download JSSE because 
Sun integrated it into JDK1.4 as a standard library.}}}
-
+[[Anchor(jdbc)]]
 === JDBC Driver ===
 
 You will need to add your database vendor's JDBC driver to the  classpath  if 
you want to do JDBC testing.
-
+[[Anchor(soap)]]
 === Apache SOAP ===
 
 Apache SOAP requires mail.jar and activation.jar. You need to download and 
copy these two jar files to your jmeter/lib directory. Once the files are in 
there, JMeter will automatically pick them up.
@@ -60,13 +60,13 @@
 ==  Installation ==
 
 Installing JMeter is a snap. Specifics depend on which release file you 
downloaded.
-
+[[Anchor(release)]]
 === Downloading the Latest Release ===
 
 We recommend that most users run the 
[http://jakarta.apache.org/site/downloads/downloads_jmeter.cgi latest release].
 
 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.
-
+[[Anchor(nightly)]]
 === Downloading Nightly Builds ===
 
 If you do not mind working with beta-quality software, then you can download 
and run the latest nightly build.
@@ -84,7 +84,7 @@
 You can also install utility Jar files in $JAVA_HOME/jre/lib/ext
 
 Note that setting the CLASSPATH environment variable will have no effect. This 
is because JMeter is started with "java -jar", and the java command silently 
ignores the CLASSPATH variable, and the -classpath/-cp options when -jar is 
used. [This occurs with all Java programs, not just JMeter.]
-
+[[Anchor(proxy)]]
 === Using a Proxy Server ===
 
 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:
@@ -100,7 +100,7 @@
     {{{jmeter -H my.proxy.server -P 8000 -u username -a password}}}
 
 Alternatively, you can use --proxyHost, --proxyPort, --username, and --password
-
+[[Anchor(nongui)]]
 ===  Non-GUI Mode ===
 
 For non-interactive testing, you may choose to run JMeter without the GUI. To 
do so, use the following command options
@@ -120,7 +120,7 @@
     -P [proxy server port]
 
     {{{jmeter -n -t my_test.jmx -l log.jtl -H my.proxy.server -P 8000}}}
-
+[[Anchor(servermode)]]
 === Server Mode ===
 
 For distributed testing , run JMeter in server mode, and then control each 
server from the GUI.
@@ -136,7 +136,7 @@
     -P [proxy server port]
 
     {{{jmeter-server -H my.proxy.server -P 8000}}}
-
+[[Anchor(propertyoverride)]]
 === Overriding Properties Via The Command Line ===
 
 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:
@@ -156,7 +156,7 @@
    {{{jmeter -LDEBUG}}}
 
 The command line properties are processed early in startup, but after the 
logging system has been set up. Attempts to use the -J flag to update log_level 
or log_file properties will have no effect.
-
+[[Anchor(logging)]]
 === Logging and error messages ===
 
 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. It is normally defined as 
jmeter.log , and will be found in the JMeter startup directory, i.e. bin.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to