Getting Started
The easiest way to begin using JMeter is to first [http://jakarta.apache.org/site/downloads/downloads_jmeter.cgi download the latest production release] and install it. The release contains all of the files you need to build and run Web, FTP, JDBC, and JNDI tests. If you want to perform JDBC testing, then you will, of course, need the appropriate JDBC driver from your vendor. JMeter does not come with any JDBC drivers.
Next, start JMeter and go through the [:../BuildTestPlan: Building a Test Plan] section of the User Guide to familiarize yourself with JMeter basics (for example, adding and removing elements).
Finally, go through the appropriate section on how to build a specific type of Test Plan. For example, if you are interested in testing a Web application, then see the section [:../BuildWebTest: Building a Web Test Plan]. The other specific Test Plan sections are for [:../BuildDbTest: JDBC] , [:../BuildFtpTest: FTP], [:../BuildWSTest: WebServices], and [:../BuildLdapTest: LDAP] .
Once you are comfortable with building and running JMeter Test Plans, you can look into the various configuration elements (timers, listeners, assertions, and others) which give you more control over your Test Plans.
Requirements
JMeter requires your computing environment meets some minimum requirements.
Java Version
JMeter version 1.8 requires a fully compliant JDK1.4 or higher.
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.
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.
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.
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.
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.
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].
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.
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.
JDBC Driver
You will need to add your database vendor's JDBC driver to the classpath if you want to do JDBC testing.
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.