You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jmeter.apache.org by mi...@apache.org on 2015/03/28 01:21:36 UTC
svn commit: r1669716 [1/2] - in /jmeter/branches/docs-2.13: ./ docs/
docs/usermanual/ xdocs/stylesheets/
Author: milamber
Date: Sat Mar 28 00:21:35 2015
New Revision: 1669716
URL: http://svn.apache.org/r1669716
Log:
Backport (cherry-pick via svn merge -c) the commits r1668162 and r1668364. Update the website docs
Modified:
jmeter/branches/docs-2.13/ (props changed)
jmeter/branches/docs-2.13/docs/download_jmeter.html
jmeter/branches/docs-2.13/docs/mail2.html
jmeter/branches/docs-2.13/docs/svnindex.html
jmeter/branches/docs-2.13/docs/usermanual/best-practices.html
jmeter/branches/docs-2.13/docs/usermanual/boss.html
jmeter/branches/docs-2.13/docs/usermanual/build-ldapext-test-plan.html
jmeter/branches/docs-2.13/docs/usermanual/build-test-plan.html
jmeter/branches/docs-2.13/docs/usermanual/functions.html
jmeter/branches/docs-2.13/docs/usermanual/get-started.html
jmeter/branches/docs-2.13/docs/usermanual/hints_and_tips.html
jmeter/branches/docs-2.13/docs/usermanual/index.html
jmeter/branches/docs-2.13/docs/usermanual/intro.html
jmeter/branches/docs-2.13/docs/usermanual/ldapanswer_xml.html
jmeter/branches/docs-2.13/docs/usermanual/ldapops_tutor.html
jmeter/branches/docs-2.13/docs/usermanual/listeners.html
jmeter/branches/docs-2.13/docs/usermanual/realtime-results.html
jmeter/branches/docs-2.13/docs/usermanual/regular_expressions.html
jmeter/branches/docs-2.13/docs/usermanual/remote-test.html
jmeter/branches/docs-2.13/docs/usermanual/test_plan.html
jmeter/branches/docs-2.13/xdocs/stylesheets/website-style.xsl
Propchange: jmeter/branches/docs-2.13/
------------------------------------------------------------------------------
svn:mergeinfo = /jmeter/trunk:1668162
Modified: jmeter/branches/docs-2.13/docs/download_jmeter.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/download_jmeter.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/download_jmeter.html (original)
+++ jmeter/branches/docs-2.13/docs/download_jmeter.html Sat Mar 28 00:21:35 2015
@@ -79,7 +79,7 @@
<a href="https://www.apache.org/dist/jmeter/KEYS">KEYS</a>
</p>
</div><div class="section"><h1>Apache JMeter 2.13 (Requires Java 6 or later)</h1>
- <div class="subsection"><h2>Binaries<a class="sectionlink" href="#binaries" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="binaries">Binaries<a class="sectionlink" href="#binaries" title="Link to here">¶</a></h2>
<table>
<tr>
<td><a href="[preferred]/jmeter/binaries/apache-jmeter-2.13.tgz">apache-jmeter-2.13.tgz</a></td>
@@ -93,7 +93,7 @@
</tr>
</table>
</div>
- <div class="subsection"><h2>Source<a class="sectionlink" href="#source" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="source">Source<a class="sectionlink" href="#source" title="Link to here">¶</a></h2>
<table>
<tr>
<td><a href="[preferred]/jmeter/source/apache-jmeter-2.13_src.tgz">apache-jmeter-2.13_src.tgz</a></td>
Modified: jmeter/branches/docs-2.13/docs/mail2.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/mail2.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/mail2.html (original)
+++ jmeter/branches/docs-2.13/docs/mail2.html Sat Mar 28 00:21:35 2015
@@ -46,7 +46,7 @@ For details of how to subscribe/unsubscr
</div><div class="section"><h1>JMeter lists and archives at the ASF</h1>
The following mailing lists are available:
-<div class="subsection"><h2>Apache JMeter User<a class="sectionlink" href="#JMeterUser" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="JMeterUser">Apache JMeter User<a class="sectionlink" href="#JMeterUser" title="Link to here">¶</a></h2>
<p>
This is the list where users of Apache JMeter meet and discuss issues.
</p>
@@ -63,12 +63,12 @@ For earlier postings, please see the Jak
<li>All old mails at <a href="http://mail-archives.apache.org/mod_mbox/jmeter-user/">jmeter-user Archive</a></li>
</ul>
</div>
-<div class="subsection"><h2>Jakarta JMeter User<a class="sectionlink" href="#JakartaJMeterUser" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="JakartaJMeterUser">Jakarta JMeter User<a class="sectionlink" href="#JakartaJMeterUser" title="Link to here">¶</a></h2>
This is the old JMeter user list from when JMeter was a sub-project of Apache Jakarta.
<ul>
<li>All old mails at <a href="http://mail-archives.apache.org/mod_mbox/jakarta-jmeter-user/">jakarta-jmeter-user Archive</a></li></ul>
</div>
-<div class="subsection"><h2>Apache JMeter Developer<a class="sectionlink" href="#JMeterDev" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="JMeterDev">Apache JMeter Developer<a class="sectionlink" href="#JMeterDev" title="Link to here">¶</a></h2>
<p>
This is the list where participating developers meet and discuss issues, code changes/additions etc.
</p>
@@ -86,7 +86,7 @@ For earlier postings, please see below.
<li>All old mails at <a href="http://mail-archives.apache.org/mod_mbox/jmeter-dev/">jmeter-dev Archive</a></li>
</ul>
</div>
-<div class="subsection"><h2>Apache JMeter Commits<a class="sectionlink" href="#JMeterCommits" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="JMeterCommits">Apache JMeter Commits<a class="sectionlink" href="#JMeterCommits" title="Link to here">¶</a></h2>
<p>
SVN commit messages are sent here.
</p>
@@ -97,7 +97,7 @@ Prior to Nov 2011, they were sent to the
<li>All old mails at <a href="http://mail-archives.apache.org/mod_mbox/jmeter-commits/">jmeter-commits Archive</a></li>
</ul>
</div>
-<div class="subsection"><h2>Apache JMeter Issues<a class="sectionlink" href="#JMeterIssues" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="JMeterIssues">Apache JMeter Issues<a class="sectionlink" href="#JMeterIssues" title="Link to here">¶</a></h2>
<p>
Bugzilla messages are sent here.
</p>
@@ -110,19 +110,19 @@ Prior to Nov 2011, they were sent to the
<li>All old mails at <a href="http://mail-archives.apache.org/mod_mbox/jmeter-issues/">jmeter-issues Archive</a></li>
</ul>
</div>
-<div class="subsection"><h2>Jakarta Developer<a class="sectionlink" href="#JakartaDev" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="JakartaDev">Jakarta Developer<a class="sectionlink" href="#JakartaDev" title="Link to here">¶</a></h2>
<p>Combined Jakarta developer list, April 2010 to November 2011</p>
<ul>
<li>All old mails at <a href="http://mail-archives.apache.org/mod_mbox/jakarta-dev/">jakarta-dev Archive</a></li>
</ul>
</div>
-<div class="subsection"><h2>Jakarta JMeter Developer<a class="sectionlink" href="#JakartaJMeterDev" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="JakartaJMeterDev">Jakarta JMeter Developer<a class="sectionlink" href="#JakartaJMeterDev" title="Link to here">¶</a></h2>
Historical list, up to April 2010.
<ul>
<li>All old mails at <a href="http://mail-archives.apache.org/mod_mbox/jakarta-jmeter-dev/">jakarta-jmeter-dev Archive</a></li>
</ul>
</div>
-<div class="subsection"><h2>Jakarta Notifications<a class="sectionlink" href="#JakartaNotif" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="JakartaNotif">Jakarta Notifications<a class="sectionlink" href="#JakartaNotif" title="Link to here">¶</a></h2>
Combined Jakarta notifications to November 2011.
Includes Bugzilla, SVN and Wiki commit mails for JMeter.
<ul>
Modified: jmeter/branches/docs-2.13/docs/svnindex.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/svnindex.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/svnindex.html (original)
+++ jmeter/branches/docs-2.13/docs/svnindex.html Sat Mar 28 00:21:35 2015
@@ -42,7 +42,7 @@ page</a>. </p>
<p>Modules available for access are listed below.</p>
-<div class="subsection"><h2>Subversion<a class="sectionlink" href="#subversion" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="subversion">Subversion<a class="sectionlink" href="#subversion" title="Link to here">¶</a></h2>
<p><a href="http://subversion.apache.org">Subversion</a> is an open-source version control system. The root url of the
ASF Subversion repository is <a href="http://svn.apache.org/repos/asf/">http://svn.apache.org/repos/asf/</a> for non-committers and <a href="https://svn.apache.org/repos/asf/">https://svn.apache.org/repos/asf/</a> for committers. </p>
Modified: jmeter/branches/docs-2.13/docs/usermanual/best-practices.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/usermanual/best-practices.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/usermanual/best-practices.html (original)
+++ jmeter/branches/docs-2.13/docs/usermanual/best-practices.html Sat Mar 28 00:21:35 2015
@@ -234,7 +234,7 @@ For example:
java -jar ../lib/bshclient.jar localhost 9000 throughput.bsh 70 5 100 60
</pre>
</div><div class="section"><h1 id="bsh_scripting">17.9 BeanShell scripting<a class="sectionlink" href="#bsh_scripting" title="Link to here">¶</a></h1>
-<div class="subsection"><h2>17.9.1 Overview<a class="sectionlink" href="#bsh_overview" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="bsh_overview">17.9.1 Overview<a class="sectionlink" href="#bsh_overview" title="Link to here">¶</a></h2>
<p>
Each BeanShell test element has its own copy of the interpreter (for each thread).
If the test element is repeatedly called, e.g. within a loop, then the interpreter is retained
@@ -256,7 +256,7 @@ bsh% exit(); // or use EOF key (e.g. ^Z
</pre>
</p>
</div>
-<div class="subsection"><h2>17.9.2 Sharing Variables<a class="sectionlink" href="#bsh_variables" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="bsh_variables">17.9.2 Sharing Variables<a class="sectionlink" href="#bsh_variables" title="Link to here">¶</a></h2>
<p>
Variables can be defined in startup (initialisation) scripts.
These will be retained across invocations of the test element, unless the reset option is used.\
Modified: jmeter/branches/docs-2.13/docs/usermanual/boss.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/usermanual/boss.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/usermanual/boss.html (original)
+++ jmeter/branches/docs-2.13/docs/usermanual/boss.html Sat Mar 28 00:21:35 2015
@@ -35,7 +35,7 @@ will need some hardware to run the bench
tools will prove useful. There are a number of products to consider. And finally,
why is Java a good choice to implement a load-testing/Benchmarking product.
</p>
-<div class="subsection"><h2>18.1 Questions to ask<a class="sectionlink" href="#questions" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="questions">18.1 Questions to ask<a class="sectionlink" href="#questions" title="Link to here">¶</a></h2>
<p>What is our anticipated average number of users (normal load) ?
</p>
<p>What is our anticipated peak number of users ?
@@ -48,13 +48,13 @@ bearing in mind that this may very well
</p>
<p>What is the testing intended to achieve?</p>
</div>
-<div class="subsection"><h2>18.2 Resources<a class="sectionlink" href="#resources" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="resources">18.2 Resources<a class="sectionlink" href="#resources" title="Link to here">¶</a></h2>
<p>The following resources will prove very helpful. Bear in mind that if you
cannot locate these resources, <b>you</b> will become these resources. As you
already have your work cut out for you, it is worth knowing who the following
people are, so that you can ask them for help if you need it.
</p>
- <div class="subsection"><h2>18.2.1 Network<a class="sectionlink" href="#network" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="network">18.2.1 Network<a class="sectionlink" href="#network" title="Link to here">¶</a></h2>
<p>Who knows our network topology ? If you run into any firewall or
proxy issues, this will become very important. As well, a private
testing network (which will therefore have very low network latency)
@@ -64,7 +64,7 @@ people are, so that you can ask them for
hardware ?
</p>
</div>
- <div class="subsection"><h2>18.2.2 Application<a class="sectionlink" href="#application" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="application">18.2.2 Application<a class="sectionlink" href="#application" title="Link to here">¶</a></h2>
<p>Who knows how our application functions ? The normal sequence is
<ul>
<li>test (low-volume - can we benchmark our application?)</li>
@@ -80,7 +80,7 @@ people are, so that you can ask them for
during this process, so be prepared to defend your work.</p>
</div>
</div>
-<div class="subsection"><h2>18.3 What platform should I use to run the benchmarks/load-tests ?<a class="sectionlink" href="#platform" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="platform">18.3 What platform should I use to run the benchmarks/load-tests ?<a class="sectionlink" href="#platform" title="Link to here">¶</a></h2>
<p>This should be a widely-used piece of hardware, with a standard
(i.e. vanilla) software installation. Remember, if you publish your results,
the first thing your clients will do is hire a graduate student to verify them.
@@ -118,20 +118,20 @@ The batch log file can then be loaded in
use CSV output and import the data into a spreadsheet.</p>
<div class="clear"></div><div class="note">Remember GUI mode is for Script creation and debugging, not for load testing</div><div class="clear"></div>
</div>
-<div class="subsection"><h2>18.4 Tools<a class="sectionlink" href="#tools" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="tools">18.4 Tools<a class="sectionlink" href="#tools" title="Link to here">¶</a></h2>
<p>The following tools will all prove useful. It is definitely worthwhile to
become familiar with them. This should include trying them out, and reading the
appropriate documentation (man-pages, info-files, application --help messages,
and any supplied documentation).
</p>
- <div class="subsection"><h2>18.4.1 ping<a class="sectionlink" href="#ping" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="ping">18.4.1 ping<a class="sectionlink" href="#ping" title="Link to here">¶</a></h2>
<p>
This can be used to establish whether or not you can reach your
target site. Options can be specified so that 'ping' provides the
same type of route reporting as 'traceroute'.
</p>
</div>
- <div class="subsection"><h2>18.4.2 nslookup/dig<a class="sectionlink" href="#dig" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="dig">18.4.2 nslookup/dig<a class="sectionlink" href="#dig" title="Link to here">¶</a></h2>
<p>
While the <u>user</u> will normally use a human-readable internet
address, <u>you</u> may wish to avoid the overhead of DNS lookups when
@@ -139,7 +139,7 @@ and any supplied documentation).
the unique address (dotted quad) of your target site.
</p>
</div>
- <div class="subsection"><h2>18.4.3 traceroute<a class="sectionlink" href="#traceroute" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="traceroute">18.4.3 traceroute<a class="sectionlink" href="#traceroute" title="Link to here">¶</a></h2>
<p>
If you cannot "ping" your target site, this may be used to determine
the problem (possibly a firewall or a proxy). It can also be used
@@ -150,10 +150,10 @@ and any supplied documentation).
</p>
</div>
</div>
-<div class="subsection"><h2>18.5 How can I enhance JMeter ?<a class="sectionlink" href="#plugins" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="plugins">18.5 How can I enhance JMeter ?<a class="sectionlink" href="#plugins" title="Link to here">¶</a></h2>
<p>There a lot of open-source and commercial plugins that can enhance JMeter, let's mention here the main open-source ones:
</p>
- <div class="subsection"><h2>18.5.1 JMeter-Plugins<a class="sectionlink" href="#jmeter-plugins" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="jmeter-plugins">18.5.1 JMeter-Plugins<a class="sectionlink" href="#jmeter-plugins" title="Link to here">¶</a></h2>
<p>This <a href="http://jmeter-plugins.org/" target="_blank">non official project</a> is THE companion to core JMeter.<br>
It provides many useful extensions, among which:
<ul>
@@ -166,20 +166,20 @@ and any supplied documentation).
</ul>
</p>
</div>
- <div class="subsection"><h2>18.5.2 JMeter Plugin for Maven<a class="sectionlink" href="#jmeter-maven-plugin" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="jmeter-maven-plugin">18.5.2 JMeter Plugin for Maven<a class="sectionlink" href="#jmeter-maven-plugin" title="Link to here">¶</a></h2>
<p>This <a href="http://jmeter.lazerycode.com/" target="_blank">non official plugin</a> allows you to run your automated JMeter tests through Maven.</p>
</div>
- <div class="subsection"><h2>18.5.3 JMeter Performance Plugin<a class="sectionlink" href="#jmeter-performance-plugin" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="jmeter-performance-plugin">18.5.3 JMeter Performance Plugin<a class="sectionlink" href="#jmeter-performance-plugin" title="Link to here">¶</a></h2>
<p>This <a href="https://wiki.jenkins-ci.org/display/JENKINS/Performance+Plugin" target="_blank">non official plugin</a> allows you to capture reports from JMeter and JUnit.<br>
Jenkins will generate graphic charts with the trend report of performance and robustness.
It includes the feature of setting the final build status as good, unstable or failed, based on the reported error percentage.
</p>
</div>
- <div class="subsection"><h2>18.5.4 JMeter plugin for AWS<a class="sectionlink" href="#jmeter-ec2" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="jmeter-ec2">18.5.4 JMeter plugin for AWS<a class="sectionlink" href="#jmeter-ec2" title="Link to here">¶</a></h2>
<p>This <a href="https://github.com/oliverlloyd/jmeter-ec2" target="_blank">non official plugin</a> automates running Apache JMeter on Amazon EC2</p>
</div>
</div>
-<div class="subsection"><h2>18.6 Why Java ?<a class="sectionlink" href="#java" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="java">18.6 Why Java ?<a class="sectionlink" href="#java" title="Link to here">¶</a></h2>
<p>Why not Perl or C ?
</p>
<p>Well, Perl might be a very good choice except that the Benchmark package
Modified: jmeter/branches/docs-2.13/docs/usermanual/build-ldapext-test-plan.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/usermanual/build-ldapext-test-plan.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/usermanual/build-ldapext-test-plan.html (original)
+++ jmeter/branches/docs-2.13/docs/usermanual/build-ldapext-test-plan.html Sat Mar 28 00:21:35 2015
@@ -66,7 +66,7 @@ cn=c:\\\\log.txt to add an entry with a
</p>
- <div class="subsection"><h2>9b.1 Adding Users<a class="sectionlink" href="#ext_adding_users" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="ext_adding_users">9b.1 Adding Users<a class="sectionlink" href="#ext_adding_users" title="Link to here">¶</a></h2>
<p>
The first step you want to do with every JMeter Test Plan is to add a Thread Group element.
The Thread Group tells JMeter the number of users you want to simulate, how often the users should send
@@ -85,7 +85,7 @@ Figure 9b.1. Thread Group with Default V
</p>
</div>
- <div class="subsection"><h2>9b.2 Adding LDAP Extended Request Defaults<a class="sectionlink" href="#add_ldapext_defaults" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="add_ldapext_defaults">9b.2 Adding LDAP Extended Request Defaults<a class="sectionlink" href="#add_ldapext_defaults" title="Link to here">¶</a></h2>
<p>
Begin by selecting the LDAP Ext Users element. Click your right mouse button
to get the <b>Add</b> menu, and then select <b>Add </b>><b>Config Element</b>><b>LDAP Extended Request Defaults</b>. Then,
@@ -107,7 +107,7 @@ field that you can modify. In this examp
</p>
We will not enter any default values here, as we will build a very small testplan, so we will explain all the different fields when we add the LDAP Extended samplers.
</div>
-<div class="subsection"><h2>9b.3 Adding LDAP Requests<a class="sectionlink" href="#add_extrequests" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="add_extrequests">9b.3 Adding LDAP Requests<a class="sectionlink" href="#add_extrequests" title="Link to here">¶</a></h2>
<p>
In our Test Plan, we want to use all 9 LDAP requests.
</p>
@@ -150,7 +150,7 @@ Sampler</b>><b>LDAP Ext Request</b>).
and edit the following properties.</p>
-<div class="subsection"><h2>9b.3.1 Adding a Thread bind Request<a class="sectionlink" href="#add_threadbind" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="add_threadbind">9b.3.1 Adding a Thread bind Request<a class="sectionlink" href="#add_threadbind" title="Link to here">¶</a></h2>
<p>
<ol>
<li>
@@ -191,7 +191,7 @@ Figure 9b.3.1. Thread Bind example</figc
</p>
</div>
-<div class="subsection"><h2>9b.3.2 Adding a search Request<a class="sectionlink" href="#add_searchreq" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="add_searchreq">9b.3.2 Adding a search Request<a class="sectionlink" href="#add_searchreq" title="Link to here">¶</a></h2>
<p>
<ol>
<li>
@@ -249,7 +249,7 @@ Figure 9b.3.2. search request example"><
Figure 9b.3.2. search request example</figcaption></figure>
</p></div>
-<div class="subsection"><h2>9b.3.3 Adding a Compare Request<a class="sectionlink" href="#add_comparereq" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="add_comparereq">9b.3.3 Adding a Compare Request<a class="sectionlink" href="#add_comparereq" title="Link to here">¶</a></h2>
<p>
<ol>
<li>
@@ -273,7 +273,7 @@ Figure 9b.3.3. Compare example</figcapti
</p>
</div>
-<div class="subsection"><h2>9b.3.4 Adding a Single bind/unbind<a class="sectionlink" href="#add_sbind" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="add_sbind">9b.3.4 Adding a Single bind/unbind<a class="sectionlink" href="#add_sbind" title="Link to here">¶</a></h2>
<p>
<ol>
<li>
@@ -299,7 +299,7 @@ Figure 9b.3.4. Single bind/unbind exampl
</p>
</div>
-<div class="subsection"><h2>9b.3.5 Adding an Add Request<a class="sectionlink" href="#add_addreq" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="add_addreq">9b.3.5 Adding an Add Request<a class="sectionlink" href="#add_addreq" title="Link to here">¶</a></h2>
<p>
<ol>
<li>
@@ -326,7 +326,7 @@ Figure 9b.3.5. Add request example</figc
</p>
</div>
-<div class="subsection"><h2>9b.3.6 Adding a Modify Request<a class="sectionlink" href="#add_modreq" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="add_modreq">9b.3.6 Adding a Modify Request<a class="sectionlink" href="#add_modreq" title="Link to here">¶</a></h2>
<p>
<ol>
<li>
@@ -371,7 +371,7 @@ Figure 9b.3.6. Modify example</figcaptio
</p>
</div>
-<div class="subsection"><h2>9b.3.7 Adding a Rename Request (moddn)<a class="sectionlink" href="#add_moddn" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="add_moddn">9b.3.7 Adding a Rename Request (moddn)<a class="sectionlink" href="#add_moddn" title="Link to here">¶</a></h2>
<p>
<ol>
<li>
@@ -401,7 +401,7 @@ Figure 9b.3.8. Rename example</figcaptio
</p>
</div>
-<div class="subsection"><h2>9b.3.8 Adding a Delete Request<a class="sectionlink" href="#add_delreq" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="add_delreq">9b.3.8 Adding a Delete Request<a class="sectionlink" href="#add_delreq" title="Link to here">¶</a></h2>
<p>
<ol>
<li>
@@ -424,7 +424,7 @@ Figure 9b.3.7. Delete example</figcaptio
</p>
</div>
-<div class="subsection"><h2>9b.3.9 Adding an unbind Request<a class="sectionlink" href="#add_unbind" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="add_unbind">9b.3.9 Adding an unbind Request<a class="sectionlink" href="#add_unbind" title="Link to here">¶</a></h2>
<p>
<ol>
<li>
@@ -444,7 +444,7 @@ Figure 9b.3.9. Unbind example</figcaptio
</div>
</div>
-<div class="subsection"><h2>9b.4 Adding a Listener to View/Store the Test Results<a class="sectionlink" href="#add_ldapext_listener" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="add_ldapext_listener">9b.4 Adding a Listener to View/Store the Test Results<a class="sectionlink" href="#add_ldapext_listener" title="Link to here">¶</a></h2>
<p>
The final element you need to add to your Test Plan is a Listener.
This element is responsible for storing all of the results of your LDAP
Modified: jmeter/branches/docs-2.13/docs/usermanual/build-test-plan.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/usermanual/build-test-plan.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/usermanual/build-test-plan.html (original)
+++ jmeter/branches/docs-2.13/docs/usermanual/build-test-plan.html Sat Mar 28 00:21:35 2015
@@ -34,7 +34,7 @@ test plan will consist of one or more Th
controllers, listeners, timers, assertions, and configuration elements.
</p>
-<div class="subsection"><h2>3.1 Adding and Removing Elements<a class="sectionlink" href="#add_remove" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="add_remove">3.1 Adding and Removing Elements<a class="sectionlink" href="#add_remove" title="Link to here">¶</a></h2>
<p>Adding <a href="test_plan.html">elements to a test plan</a> can be done by right-clicking on an element in the
tree, and choosing a new element from the "add" list. Alternatively, elements can
be loaded from file and added by choosing the "merge" or "open" option.</p>
@@ -43,7 +43,7 @@ be loaded from file and added by choosin
and choose the "remove" option.</p>
</div>
-<div class="subsection"><h2>3.2 Loading and Saving Elements<a class="sectionlink" href="#load_save" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="load_save">3.2 Loading and Saving Elements<a class="sectionlink" href="#load_save" title="Link to here">¶</a></h2>
<p>To load an element from file, right click on the existing tree elements to which
you want to add the loaded element, and select the "merge" option. Choose the file where
your elements are saved. JMeter will merge the elements into the tree.</p>
@@ -55,7 +55,7 @@ you can save test tree fragments and ind
<div class="clear"></div><div class="note">The workbench is not automatically saved with the test plan, but it can be saved separately as above.</div><div class="clear"></div>
</div>
-<div class="subsection"><h2>3.3 Configuring Tree Elements<a class="sectionlink" href="#config_element" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="config_element">3.3 Configuring Tree Elements<a class="sectionlink" href="#config_element" title="Link to here">¶</a></h2>
<p>Any element in the test tree will present controls in JMeter's right-hand frame. These
controls allow you to configure the behavior of that particular test element. What can be
configured for an element depends on what type of element it is.</p>
@@ -63,7 +63,7 @@ configured for an element depends on wha
<div class="clear"></div><div class="note">The Test Tree itself can be manipulated by dragging and dropping components around the test tree.</div><div class="clear"></div>
</div>
-<div class="subsection"><h2>3.4 Saving the Test Plan<a class="sectionlink" href="#saving" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="saving">3.4 Saving the Test Plan<a class="sectionlink" href="#saving" title="Link to here">¶</a></h2>
<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" or "Save Test Plan As ..." from the
File menu (with the latest release, it is no longer necessary to select the
@@ -78,7 +78,7 @@ the Edit menu.
</div><div class="clear"></div>
</div>
-<div class="subsection"><h2>3.5 Running a Test Plan<a class="sectionlink" href="#run" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="run">3.5 Running a Test Plan<a class="sectionlink" href="#run" title="Link to here">¶</a></h2>
<p>To run your test plan, choose "Start" (Control + r) from the "Run" menu item.
When JMeter is running, it shows a small green box at the right hand end of the section just under the menu bar.
You can also check the "Run" menu.
@@ -90,7 +90,7 @@ These only apply to a locally run test;
</p>
</div>
-<div class="subsection"><h2>3.6 Stopping a Test<a class="sectionlink" href="#stop" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="stop">3.6 Stopping a Test<a class="sectionlink" href="#stop" title="Link to here">¶</a></h2>
<p>
There are two types of stop command available from the menu:
<ul>
@@ -132,7 +132,7 @@ The commands will only be accepted if th
</p>
</div>
-<div class="subsection"><h2>3.7 Error reporting<a class="sectionlink" href="#error_reporting" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="error_reporting">3.7 Error reporting<a class="sectionlink" href="#error_reporting" title="Link to here">¶</a></h2>
<p>
JMeter reports warnings and errors to the jmeter.log file, as well as some information on the test run itself.
JMeter shows at the right hand end of its window, the number of warnings/errors found in jmeter.log file next to the warning icon.
Modified: jmeter/branches/docs-2.13/docs/usermanual/functions.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/usermanual/functions.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/usermanual/functions.html (original)
+++ jmeter/branches/docs-2.13/docs/usermanual/functions.html Sat Mar 28 00:21:35 2015
@@ -128,7 +128,7 @@ Alternatively, just use / instead for th
<tr><td>String</td><td> <a href="#__TestPlanName">TestPlanName</a></td><td>Return name of current test plan</td><td>2.6</td></tr>
</table>
<p></p>
-<div class="subsection"><h2>20.1 What can functions do<a class="sectionlink" href="#what_can_do" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="what_can_do">20.1 What can functions do<a class="sectionlink" href="#what_can_do" title="Link to here">¶</a></h2>
<p>There are two kinds of functions: user-defined static values (or variables), and built-in functions.<br>
User-defined static values allow the user to define variables to be replaced with their static value when
a test tree is compiled and submitted to be run. This replacement happens once at the beginning of the test
@@ -151,7 +151,7 @@ request throughout the course of the tes
Each occurrence of a function call in a test plan is handled by a separate function instance.</div><div class="clear"></div>
</div>
-<div class="subsection"><h2>20.2 Where can functions and variables be used?<a class="sectionlink" href="#where" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="where">20.2 Where can functions and variables be used?<a class="sectionlink" href="#where" title="Link to here">¶</a></h2>
<p>
Functions and variables can be written into any field of any test component (apart from the TestPlan - see below).
Some fields do not allow random strings
@@ -194,7 +194,7 @@ SELECT item from table where name=${VAR}
</div><div class="clear"></div>
</div>
-<div class="subsection"><h2>20.3 How to reference variables and functions<a class="sectionlink" href="#how" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="how">20.3 How to reference variables and functions<a class="sectionlink" href="#how" title="Link to here">¶</a></h2>
<p>Referencing a variable in a test element is done by bracketing the variable name with '${' and '}'.</p>
<p>Functions are referenced in the same manner, but by convention, the names of
functions begin with "__" to avoid conflict with user value names<sup>*</sup>. Some functions take arguments to
@@ -246,7 +246,7 @@ that can be used to display the values o
variable will override the built-in function.</div><div class="clear"></div>
</div>
-<div class="subsection"><h2>20.4 The Function Helper Dialog<a class="sectionlink" href="#function_helper" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="function_helper">20.4 The Function Helper Dialog<a class="sectionlink" href="#function_helper" title="Link to here">¶</a></h2>
<p>The Function Helper dialog is available from JMeter's Tools menu.</p>
<figure><a href="../images/screenshots/function_helper_dialog.png"><img src="../images/screenshots/function_helper_dialog.png" width="831" height="305" alt="Function Helper Dialog"></a><figcaption>Function Helper Dialog</figcaption></figure>
<p>Using the Function Helper, you can select a function from the pull down, and assign
@@ -257,7 +257,7 @@ functions take different arguments.</p>
for you to copy-paste into your test plan wherever you like.</p>
</div>
-<div class="subsection"><h2>20.5 Functions<a class="sectionlink" href="#functions" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="functions">20.5 Functions<a class="sectionlink" href="#functions" title="Link to here">¶</a></h2>
<div class="component"><h2 id="__regexFunction">__regexFunction<a class="sectionlink" href="#__regexFunction" title="Link to here">¶</a></h2>
<div class="description"><p>The Regex Function is used to parse the previous response (or the value of a variable) using any regular
@@ -1345,7 +1345,7 @@ A reference name - refName - for reusing
</div>
-<div class="subsection"><h2>20.6 Pre-defined Variables<a class="sectionlink" href="#predefinedvars" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="predefinedvars">20.6 Pre-defined Variables<a class="sectionlink" href="#predefinedvars" title="Link to here">¶</a></h2>
<p>
Most variables are set by calling functions or by test elements such as User Defined Variables;
in which case the user has full control over the variable name that is used.
@@ -1359,7 +1359,7 @@ Note: this is updated after PostProcesso
<li>START variables (see next section)</li>
</ul>
</div>
-<div class="subsection"><h2>20.6 Pre-defined Properties<a class="sectionlink" href="#predefinedprops" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="predefinedprops">20.6 Pre-defined Properties<a class="sectionlink" href="#predefinedprops" title="Link to here">¶</a></h2>
<p>
The set of JMeter properties is initialised from the system properties defined when JMeter starts;
additional JMeter properties are defined in jmeter.properties, user.properties or on the command line.
Modified: jmeter/branches/docs-2.13/docs/usermanual/get-started.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/usermanual/get-started.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/usermanual/get-started.html (original)
+++ jmeter/branches/docs-2.13/docs/usermanual/get-started.html Sat Mar 28 00:21:35 2015
@@ -67,14 +67,14 @@ over your Test Plans.</p>
</div><div class="section"><h1 id="requirements">2.1 Requirements<a class="sectionlink" href="#requirements" title="Link to here">¶</a></h1>
<p>JMeter requires that your computing environment meets some minimum requirements.</p>
-<div class="subsection"><h2>2.1.1 Java Version<a class="sectionlink" href="#java_versions" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="java_versions">2.1.1 Java Version<a class="sectionlink" href="#java_versions" title="Link to here">¶</a></h2>
<div class="clear"></div><div class="note">JMeter requires a fully compliant JVM 6 or higher.
</div><div class="clear"></div>
<p>Because JMeter uses only standard Java APIs, please do not file bug reports if your JRE fails to run
JMeter because of JRE implementation issues.</p>
</div>
-<div class="subsection"><h2>2.1.2 Operating Systems<a class="sectionlink" href="#os" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="os">2.1.2 Operating Systems<a class="sectionlink" href="#os" title="Link to here">¶</a></h2>
<p>JMeter is a 100% Java application and should run correctly on any system
that has a compliant Java implementation.</p>
<p>Operating systems tested with JMeter can be viewed on
@@ -86,25 +86,25 @@ on JMeter wiki.</p>
<p>If you plan on doing JMeter development, then you will need one or more optional packages listed below.</p>
-<div class="subsection"><h2>2.2.1 Java Compiler<a class="sectionlink" href="#opt_compiler" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="opt_compiler">2.2.1 Java Compiler<a class="sectionlink" href="#opt_compiler" title="Link to here">¶</a></h2>
<p>If you want to build the JMeter source or develop JMeter plugins, then you will need a fully compliant JDK 6 or higher.</p>
</div>
-<div class="subsection"><h2>2.2.2 SAX XML Parser<a class="sectionlink" href="#opt_sax" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="opt_sax">2.2.2 SAX XML Parser<a class="sectionlink" href="#opt_sax" title="Link to here">¶</a></h2>
<p>JMeter comes with Apache's <a href="http://xml.apache.org/">Xerces XML parser</a>. 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 <a href="#classpath">classpath</a>,
and update the <a href="#configuring_jmeter">jmeter.properties</a> file with the full classname of the parser
implementation.</p>
</div>
-<div class="subsection"><h2>2.2.3 Email Support<a class="sectionlink" href="#opt_email" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="opt_email">2.2.3 Email Support<a class="sectionlink" href="#opt_email" title="Link to here">¶</a></h2>
<p>JMeter has extensive Email capabilities.
It can send email based on test results, and has a POP3(S)/IMAP(S) sampler.
It also has an SMTP(S) sampler.
</p>
</div>
-<div class="subsection"><h2>2.2.4 SSL Encryption<a class="sectionlink" href="#opt_ssl" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="opt_ssl">2.2.4 SSL Encryption<a class="sectionlink" href="#opt_ssl" title="Link to here">¶</a></h2>
<p>To test a web server using SSL encryption (HTTPS), JMeter requires that an
implementation of SSL be provided, as is the case with Sun Java 1.4 and above.
If your version of Java does not include SSL support, then it is possible to add an external implementation.
@@ -125,13 +125,13 @@ The SMTP sampler can optionally use a lo
</p>
</div>
-<div class="subsection"><h2>2.2.5 JDBC Driver<a class="sectionlink" href="#opt_jdbc" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="opt_jdbc">2.2.5 JDBC Driver<a class="sectionlink" href="#opt_jdbc" title="Link to here">¶</a></h2>
<p>You will need to add your database vendor's JDBC driver to the <a href="#classpath">classpath</a> if you want to do JDBC testing.
Make sure the file is a jar file, not a zip.
</p>
</div>
-<div class="subsection"><h2>2.2.6 JMS client<a class="sectionlink" href="#opt_jms" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="opt_jms">2.2.6 JMS client<a class="sectionlink" href="#opt_jms" title="Link to here">¶</a></h2>
<p>
JMeter now includes the JMS API from Apache Geronimo, so you just need to add the appropriate JMS Client implementation
jar(s) from the JMS provider. Please refer to their documentation for details.
@@ -139,7 +139,7 @@ There may also be some information on th
</p>
</div>
-<div class="subsection"><h2>2.2.7 Libraries for ActiveMQ JMS<a class="sectionlink" href="#libraries_activemq" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="libraries_activemq">2.2.7 Libraries for ActiveMQ JMS<a class="sectionlink" href="#libraries_activemq" title="Link to here">¶</a></h2>
<p>
You will need to add the jar activemq-all-X.X.X.jar to your classpath, e.g. by storing it in the lib/ directory.
</p>
@@ -233,7 +233,7 @@ JVM_ARGS="-Xms1024m -Xmx1024m" jmeter -t
</pre>
will override the HEAP settings in the script.
</p>
-<div class="subsection"><h2>2.4.1 JMeter's Classpath<a class="sectionlink" href="#classpath" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="classpath">2.4.1 JMeter's Classpath<a class="sectionlink" href="#classpath" title="Link to here">¶</a></h2>
<p>JMeter automatically finds classes from jars in the following directories:</p>
<ul>
<li>JMETER_HOME/lib - used for utility jars</li>
@@ -265,7 +265,7 @@ and the java command silently ignores th
[This occurs with all Java programs, not just JMeter.]</p>
</div>
-<div class="subsection"><h2>2.4.2 Create Test Plan from Template<a class="sectionlink" href="#template" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="template">2.4.2 Create Test Plan from Template<a class="sectionlink" href="#template" title="Link to here">¶</a></h2>
<p>You have the ability to create a new Test Plan from existing template.</p>
<p>To do so you use the menu <b>File</b> > <b>Templates...</b> or Templates icon:
<figure><a href="../images/screenshots/template_menu.png"><img src="../images/screenshots/template_menu.png" width="" height="" alt="Templates icon item"></a><figcaption>Templates icon item</figcaption></figure>
@@ -276,7 +276,7 @@ and the java command silently ignores th
<p>A documentation for each template explains what to do once test plan is created from template.</p>
</div>
-<div class="subsection"><h2>2.4.3 Using JMeter behing a proxy<a class="sectionlink" href="#proxy_server" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="proxy_server">2.4.3 Using JMeter behing a proxy<a class="sectionlink" href="#proxy_server" title="Link to here">¶</a></h2>
<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] file
from a command line with the following parameters:</p>
@@ -317,7 +317,7 @@ This is only used for recording HTTP or
This is not to be confused with the proxy settings described above, which are used when JMeter makes HTTP or HTTPS requests itself.</div><div class="clear"></div>
</div>
-<div class="subsection"><h2>2.4.4 Non-GUI Mode (Command Line mode)<a class="sectionlink" href="#non_gui" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="non_gui">2.4.4 Non-GUI Mode (Command Line mode)<a class="sectionlink" href="#non_gui" title="Link to here">¶</a></h2>
<p>For non-interactive testing, you may choose to run JMeter without the GUI. To do so, use
the following command options:</p>
<p>
@@ -341,7 +341,7 @@ Normally this is not necessary.
</p>
</div>
-<div class="subsection"><h2>2.4.5 Server Mode<a class="sectionlink" href="#server" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="server">2.4.5 Server Mode<a class="sectionlink" href="#server" title="Link to here">¶</a></h2>
<p>For <a href="remote-test.html">distributed testing</a>, run JMeter in server mode on the remote node(s), and then control the server(s) from the GUI.
You can also use non-GUI mode to run remote tests.
To start the server(s), run jmeter-server[.bat] on each server host.</p>
@@ -367,7 +367,7 @@ Normally this is not necessary.
</p>
</div>
-<div class="subsection"><h2>2.4.6 Overriding Properties Via The Command Line<a class="sectionlink" href="#override" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="override">2.4.6 Overriding Properties Via The Command Line<a class="sectionlink" href="#override" title="Link to here">¶</a></h2>
<p>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:</p>
<p>
@@ -391,7 +391,7 @@ jmeter -LDEBUG</pre>
Attempts to use the -J flag to update log_level or log_file properties will have no effect.</b>
</p>
</div>
-<div class="subsection"><h2>2.4.7 Logging and error messages<a class="sectionlink" href="#logging" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="logging">2.4.7 Logging and error messages<a class="sectionlink" href="#logging" title="Link to here">¶</a></h2>
<div class="clear"></div><div class="note">
JMeter does not generally use pop-up dialog boxes for errors, as these would interfere with
running tests. Nor does it report any error for a mis-spelt variable or function; instead the
@@ -436,7 +436,7 @@ jmeter -LDEBUG</pre>
<p>The log file can be helpful in determining the cause of an error,
as JMeter does not interrupt a test to display an error dialogue.</p>
</div>
-<div class="subsection"><h2>2.4.8 Full list of command-line options<a class="sectionlink" href="#options" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="options">2.4.8 Full list of command-line options<a class="sectionlink" href="#options" title="Link to here">¶</a></h2>
<p>Invoking JMeter as "jmeter -?" will print a list of all the command-line options.
These are shown below.</p>
<pre>
@@ -498,7 +498,7 @@ that was run in interactive mode.
</p>
</div>
-<div class="subsection"><h2>2.4.9 non-GUI shutdown<a class="sectionlink" href="#shutdown" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="shutdown">2.4.9 non-GUI shutdown<a class="sectionlink" href="#shutdown" title="Link to here">¶</a></h2>
<p>
Prior to version 2.5.1, JMeter invoked System.exit() when a non-GUI test completed.
This caused problems for applications that invoke JMeter directly, so JMeter no longer invokes System.exit()
Modified: jmeter/branches/docs-2.13/docs/usermanual/hints_and_tips.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/usermanual/hints_and_tips.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/usermanual/hints_and_tips.html (original)
+++ jmeter/branches/docs-2.13/docs/usermanual/hints_and_tips.html Sat Mar 28 00:21:35 2015
@@ -34,7 +34,7 @@ This section is a collection of various
If you don't find what you are looking for here, please check the <a href="http://wiki.apache.org/jmeter">JMeter Wiki</a>.
Also, try search the JMeter User list; someone may well have already provided a solution.
</p>
-<div class="subsection"><h2>22.1 Passing variables between threads<a class="sectionlink" href="#variable_and_threads" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="variable_and_threads">22.1 Passing variables between threads<a class="sectionlink" href="#variable_and_threads" title="Link to here">¶</a></h2>
<p>
JMeter variables have thread scope. This is deliberate, so that threads can act indepently.
However sometimes there is a need to pass variables between different threads, in the same or different Thread Groups.
@@ -56,7 +56,7 @@ read it using CSV Dataset.
</p>
</div>
-<div class="subsection"><h2>22.2 Enabling Debug logging<a class="sectionlink" href="#debug_logging" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="debug_logging">22.2 Enabling Debug logging<a class="sectionlink" href="#debug_logging" title="Link to here">¶</a></h2>
<p>
Most test elements include debug logging. If running a test plan from the GUI,
select the test element and use the Help Menu to enable or disable logging.
@@ -84,7 +84,7 @@ To avoid using too much memory, this com
</p>
</div>
-<div class="subsection"><h2>22.3 Searching<a class="sectionlink" href="#searching" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="searching">22.3 Searching<a class="sectionlink" href="#searching" title="Link to here">¶</a></h2>
<p>
It is sometimes hard to find in a Test Plan tree and elements using a variable or containing a certain URL or parameter.
A new feature is now available since 2.6, you can access it in Menu Search.
@@ -102,7 +102,7 @@ It provides search with following option
</div>
-<div class="subsection"><h2>22.4 Toolbar icons size<a class="sectionlink" href="#toolbar" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="toolbar">22.4 Toolbar icons size<a class="sectionlink" href="#toolbar" title="Link to here">¶</a></h2>
<div class="description">
<p>
You can change the size of icons in the toolbar using the property <pre>jmeter.toolbar.icons.size</pre> with these values: 22x22 (default size), 32x32 or 48x48.
Modified: jmeter/branches/docs-2.13/docs/usermanual/index.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/usermanual/index.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/usermanual/index.html (original)
+++ jmeter/branches/docs-2.13/docs/usermanual/index.html Sat Mar 28 00:21:35 2015
@@ -33,7 +33,7 @@
Click on the "+" to go to the relevant section of the detailed section list,
where you can select individual subsections.</p>
-<div class="subsection"><h2>Section Summary<a class="sectionlink" href="#summary" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="summary">Section Summary<a class="sectionlink" href="#summary" title="Link to here">¶</a></h2>
<ul>
<li><a href="../changes.html">Changes</a></li>
<li><a href="#intro">+</a>...<a href="intro.html">1. Introduction</a></li>
@@ -62,7 +62,7 @@
<li><a href="#glossary">+</a>...<a href="glossary.html">23. Glossary</a></li>
</ul>
</div>
-<div class="subsection"><h2>Detailed Section List<a class="sectionlink" href="#details" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="details">Detailed Section List<a class="sectionlink" href="#details" title="Link to here">¶</a></h2>
<ul>
<li><a name="intro"></a><a href="intro.html">1. Introduction</a></li>
<ul>
Modified: jmeter/branches/docs-2.13/docs/usermanual/intro.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/usermanual/intro.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/usermanual/intro.html (original)
+++ jmeter/branches/docs-2.13/docs/usermanual/intro.html Sat Mar 28 00:21:35 2015
@@ -45,7 +45,7 @@ results you expect. For maximum flexibi
regular expressions.</p>
<p>But please note that JMeter is not a browser, it works at protocol level.</p>
-<div class="subsection"><h2>1.1 History<a class="sectionlink" href="#history" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="history">1.1 History<a class="sectionlink" href="#history" title="Link to here">¶</a></h2>
<p>Stefano Mazzocchi of the Apache Software Foundation was the original developer of JMeter.
He wrote it primarily to test the performance of Apache JServ (a project that has
since been replaced by the Apache Tomcat project). We redesigned JMeter to enhance the GUI
@@ -55,7 +55,7 @@ and to add functional-testing capabiliti
<p>JMeter became a Top Level Apache project in November 2011, which means it has a Project Management Commitee and a dedicated website.</p>
</div>
-<div class="subsection"><h2>1.2 The Future<a class="sectionlink" href="#future" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="future">1.2 The Future<a class="sectionlink" href="#future" title="Link to here">¶</a></h2>
<p>We hope to see JMeter's capabilities rapidly expand as developers take advantage of its
pluggable architecture. <br>
The primary goal of further developments will be:
Modified: jmeter/branches/docs-2.13/docs/usermanual/ldapanswer_xml.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/usermanual/ldapanswer_xml.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/usermanual/ldapanswer_xml.html (original)
+++ jmeter/branches/docs-2.13/docs/usermanual/ldapanswer_xml.html Sat Mar 28 00:21:35 2015
@@ -36,12 +36,12 @@
construct an answer in xml encoding, so the results may be parsed with regextracter or alike functions.
</p>
-<div class="subsection"><h2>1 Global overview<a class="sectionlink" href="#overview" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="overview">1 Global overview<a class="sectionlink" href="#overview" title="Link to here">¶</a></h2>
<p>
The global structure is as follows:<br>
</p>
-<div class="subsection"><h2>1.1 The operation section<a class="sectionlink" href="#operation" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="operation">1.1 The operation section<a class="sectionlink" href="#operation" title="Link to here">¶</a></h2>
<p>
The operation section defines the operation as it is sent to the LDAP Server. The
following tags (with a short explanation) are used
@@ -49,7 +49,7 @@ following tags (with a short explanation
</p>
</div>
-<div class="subsection"><h2>1.2 Response message section<a class="sectionlink" href="#response_message" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="response_message">1.2 Response message section<a class="sectionlink" href="#response_message" title="Link to here">¶</a></h2>
<p>
As the response code, the official LDAP error definitions are used, so this section
contains the error message as returned from the server.
@@ -57,7 +57,7 @@ A succesfull request always returns "Suc
The following tag is used:
</p>
</div>
-<div class="subsection"><h2>1.3 Response code section<a class="sectionlink" href="#response_code" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="response_code">1.3 Response code section<a class="sectionlink" href="#response_code" title="Link to here">¶</a></h2>
<p>
As the response code, the official LDAP error definitions are used, so this section
contains the error number as returned from the server.
@@ -66,7 +66,7 @@ The following tag is used:
</p>
</div>
-<div class="subsection"><h2>1.4 Search Result section<a class="sectionlink" href="#search" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="search">1.4 Search Result section<a class="sectionlink" href="#search" title="Link to here">¶</a></h2>
<p>
The following tag is used:
</p>
Modified: jmeter/branches/docs-2.13/docs/usermanual/ldapops_tutor.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/usermanual/ldapops_tutor.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/usermanual/ldapops_tutor.html (original)
+++ jmeter/branches/docs-2.13/docs/usermanual/ldapops_tutor.html Sat Mar 28 00:21:35 2015
@@ -43,19 +43,19 @@
The type of an object is determined by the "structural objectClass" eg person, organizationalUnit or country.<br>
The attributes contain the data of an object, eg mailadress, name, streetadress etc. Each attribute can have 0, 1 or more values.
</p>
-<div class="subsection"><h2>1 Bind operation<a class="sectionlink" href="#bind" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="bind">1 Bind operation<a class="sectionlink" href="#bind" title="Link to here">¶</a></h2>
<p>
Any contact with an LDAP server MUST start with a bind request. LDAP is a state dependent protocol. Without opening a session to
a LDAP server, no additional request can be made.
Due to some peculiarities in the JAVA libraries, 2 different bind operations are implemented.
</p>
-<div class="subsection"><h2>1.1 Thread Bind<a class="sectionlink" href="#thread_bind" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="thread_bind">1.1 Thread Bind<a class="sectionlink" href="#thread_bind" title="Link to here">¶</a></h2>
<p>
This bind is meant to open a session to a LDAP server. Any testplan should use this operation as the starting point from a session.
For each Thread (each virtual user) a seperate connection with the LDAP server is build, and so a seperate Thread bind is performed.
</p>
</div>
-<div class="subsection"><h2>1.2 Single bind/unbind<a class="sectionlink" href="#single" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="single">1.2 Single bind/unbind<a class="sectionlink" href="#single" title="Link to here">¶</a></h2>
<p>
This bind is used for user authentication verification.
A proper developed LDAP client, who needs an authenticated user, perform a bind with a given distinguished name and password.
@@ -64,33 +64,33 @@
</p>
</div>
</div>
-<div class="subsection"><h2>2 Unbind<a class="sectionlink" href="#unbind" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="unbind">2 Unbind<a class="sectionlink" href="#unbind" title="Link to here">¶</a></h2>
<p>
To close a connection to a LDAP server, an unbind operation is needed.
As the Single bind/unbind operation already (implicitly) performs an unbind, only a Thread unbind operation is needed.
This Thread unbind just closes the connection and cleans up any resources it has used.
</p>
</div>
-<div class="subsection"><h2>3 Compare<a class="sectionlink" href="#compare" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="compare">3 Compare<a class="sectionlink" href="#compare" title="Link to here">¶</a></h2>
<p>
The compare operation needs the full distinguished name from a LDAP object, as well as a attribute and a value for the attribute.
It will simply check: "Has this object really this attribute with this value?".
Typical use is checking the membership of a certain user with a given group.
</p>
</div>
-<div class="subsection"><h2>4 Search<a class="sectionlink" href="#search" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="search">4 Search<a class="sectionlink" href="#search" title="Link to here">¶</a></h2>
<p>
The search test simply searches for all objects which comply with a given search filter, eg.
all persons with a "employeeType=inactive" or "all persons with a userID equals user1"
</p>
</div>
-<div class="subsection"><h2>5 Add<a class="sectionlink" href="#add" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="add">5 Add<a class="sectionlink" href="#add" title="Link to here">¶</a></h2>
<p>
This simply add an object to the LDAP directory.
Off course the combination of attributes and distinguishedName must be valid!
</p>
</div>
-<div class="subsection"><h2>6 Modify<a class="sectionlink" href="#modify" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="modify">6 Modify<a class="sectionlink" href="#modify" title="Link to here">¶</a></h2>
<p>
This operation modifies one or more attributes from a given object.
It needs the distinghised name from the object, as well as the attributes and the new values for this attribute.<br>
@@ -99,13 +99,13 @@
delete, to delete a value form an attribute, or to delete all the values of an attribute<br>
</p>
</div>
-<div class="subsection"><h2>7 Delete<a class="sectionlink" href="#delete" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="delete">7 Delete<a class="sectionlink" href="#delete" title="Link to here">¶</a></h2>
<p>
This operation deletes an object from the LDAP server.
It needs the distinghised name from the object.
</p>
</div>
-<div class="subsection"><h2>8 modDN<a class="sectionlink" href="#moddn" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="moddn">8 modDN<a class="sectionlink" href="#moddn" title="Link to here">¶</a></h2>
<p>
This operation modifies the distinguished name from an object (it "moves" the object).<br>
It comes in two flavours, just renaming an entry, then you specify a new RDN (relative distinguished name, this is the lowest part of the DN)<br>
Modified: jmeter/branches/docs-2.13/docs/usermanual/listeners.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/usermanual/listeners.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/usermanual/listeners.html (original)
+++ jmeter/branches/docs-2.13/docs/usermanual/listeners.html Sat Mar 28 00:21:35 2015
@@ -205,7 +205,7 @@ JMeter (2.9+) will try the following for
Matching is now also strict (non-lenient).
JMeter 2.8 and earlier used lenient mode which could result in timestamps with incorrect dates
(times were usually correct).</p>
-<div class="subsection"><h2>14.1.1 Sample Variables<a class="sectionlink" href="#sample_variables" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="sample_variables">14.1.1 Sample Variables<a class="sectionlink" href="#sample_variables" title="Link to here">¶</a></h2>
<p>
JMeter supports the <b>sample_variables</b>
property to define a list of additional JMeter variables which are to be saved with
@@ -214,7 +214,7 @@ and as additional attributes in XML file
</p>
</div>
-<div class="subsection"><h2>14.1.2 Sample Result Save Configuration<a class="sectionlink" href="#sample_configuration" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="sample_configuration">14.1.2 Sample Result Save Configuration<a class="sectionlink" href="#sample_configuration" title="Link to here">¶</a></h2>
<p>
Listeners can be configured to save different items to the result log files (JTL) by using the Config popup as shown below.
The defaults are defined as described in the <a href="#defaults">Listener Default Configuration</a> section above.
Modified: jmeter/branches/docs-2.13/docs/usermanual/realtime-results.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/usermanual/realtime-results.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/usermanual/realtime-results.html (original)
+++ jmeter/branches/docs-2.13/docs/usermanual/realtime-results.html Sat Mar 28 00:21:35 2015
@@ -46,8 +46,8 @@ In this document we will present the con
<li>Graphite</li>
</ul>
</p>
-<div class="subsection"><h2>16.1 Metrics exposed<a class="sectionlink" href="#metrics" title="Link to here">¶</a></h2>
- <div class="subsection"><h2>16.1.1 Thread/Virtual Users metrics<a class="sectionlink" href="#metrics-threads" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="metrics">16.1 Metrics exposed<a class="sectionlink" href="#metrics" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="metrics-threads">16.1.1 Thread/Virtual Users metrics<a class="sectionlink" href="#metrics-threads" title="Link to here">¶</a></h2>
<p>
Threads metrics are the following:
</p>
@@ -78,7 +78,7 @@ In this document we will present the con
</tr>
</table>
</div>
- <div class="subsection"><h2>16.1.2 Response times metrics<a class="sectionlink" href="#metrics-response-times" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="metrics-response-times">16.1.2 Response times metrics<a class="sectionlink" href="#metrics-response-times" title="Link to here">¶</a></h2>
<p>Response times metrics are the following:</p>
<table>
<tr>
@@ -145,21 +145,21 @@ In this document we will present the con
</p>
</div>
</div>
-<div class="subsection"><h2>16.2 JMeter configuration<a class="sectionlink" href="#jmeter-configuration" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="jmeter-configuration">16.2 JMeter configuration<a class="sectionlink" href="#jmeter-configuration" title="Link to here">¶</a></h2>
<p>
To make JMeter send metrics to backend add a <a href="./component_reference.html#Backend_Listener">BackendListener</a> using the GraphiteBackendListenerClient.
</p>
<figure><a href="../images/screenshots/backend_listener.png"><img src="../images/screenshots/backend_listener.png" width="902" height="341" alt="Graphite configuration"></a><figcaption>Graphite configuration</figcaption></figure>
</div>
-<div class="subsection"><h2>16.2 InfluxDB<a class="sectionlink" href="#influxdb" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="influxdb">16.2 InfluxDB<a class="sectionlink" href="#influxdb" title="Link to here">¶</a></h2>
<p>InfluxDB is an open-source, distributed,time-series database that allows to
easily store metrics.
Installation and configuration is very easy, read this for more details <a href="http://influxdb.com/docs/v0.8/introduction/installation.html" target="_blank">InfluxDB documentation</a>.<br>
InfluxDB data can be easily viewed in a browser through either <a href="https://github.com/hakobera/influga" target="_blank">Influga</a> or <a href="http://grafana.org/" target="_blank">Grafana</a>.
We will use Grafana in this case.
</p>
- <div class="subsection"><h2>16.2.1 InfluxDB graphite listener configuration<a class="sectionlink" href="#influxdb_configuration" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="influxdb_configuration">16.2.1 InfluxDB graphite listener configuration<a class="sectionlink" href="#influxdb_configuration" title="Link to here">¶</a></h2>
<p>To enable Graphite listener in InfluxDB, edit files /opt/influxdb/shared/config.toml or /usr/local/etc/influxdb.conf, find "input_plugins.graphite" and set this:
</p>
<span class="code">
@@ -172,7 +172,7 @@ We will use Grafana in this case.
# udp_enabled = true # enable udp interface on the same port as the tcp interface<br>
</span>
</div>
- <div class="subsection"><h2>16.2.2 InfluxDB database configuration<a class="sectionlink" href="#influxdb_db_configuration" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="influxdb_db_configuration">16.2.2 InfluxDB database configuration<a class="sectionlink" href="#influxdb_db_configuration" title="Link to here">¶</a></h2>
<p>Connect to InfluxDB admin console and create 2 databases:
<ul>
<li>grafana : Used by Grafana to store the dashboards we will create</li>
@@ -180,7 +180,7 @@ We will use Grafana in this case.
</ul>
</p>
</div>
- <div class="subsection"><h2>16.2.3 Grafana configuration<a class="sectionlink" href="#grafana_configuration" title="Link to here">¶</a></h2>
+ <div class="subsection"><h2 id="grafana_configuration">16.2.3 Grafana configuration<a class="sectionlink" href="#grafana_configuration" title="Link to here">¶</a></h2>
<p>
Installing grafana is just a matter of putting the unzipped bundle behind an Apache HTTP server.<br>
Read <a href="http://grafana.org/docs/" targer="_blank">documentation</a> for more details.
@@ -212,7 +212,7 @@ We will use Grafana in this case.
</div>
</div>
-<div class="subsection"><h2>16.3 Graphite<a class="sectionlink" href="#graphite" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="graphite">16.3 Graphite<a class="sectionlink" href="#graphite" title="Link to here">¶</a></h2>
<p>TODO.</p>
</div>
Modified: jmeter/branches/docs-2.13/docs/usermanual/regular_expressions.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/usermanual/regular_expressions.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/usermanual/regular_expressions.html (original)
+++ jmeter/branches/docs-2.13/docs/usermanual/regular_expressions.html Sat Mar 28 00:21:35 2015
@@ -29,7 +29,7 @@
}
})(document, 'script', 'twitter-wjs');
</script></div></div><div class="banner"><iframe src="http://www.apache.org/ads/bannerbar.html" style="border-width:0;" frameborder="0" scrolling="no"></iframe><div class="clear"></div></div></div><div class="nav"><ul class="menu"><li onClick="return true"><div class="menu-title">About</div><ul><li><a href="../index.html">Overview</a></li><li><a href="http://twitter.com/ApacheJMeter">JMeter on Twitter<img src="../images/twitter.png" alt="Icon for JMeter on Twitter"></a></li><li><a href="../issues.html">Issue Tracking</a></li><li><a href="http://projects.apache.org/feeds/rss/jmeter.xml">Subscribe to What's New</a></li><li><a href="http://www.apache.org/licenses/">License</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Download</div><ul><li><a href="../download_jmeter.cgi">Download Releases</a></li><li><a href="../nightly.html">Developer (Nightly) Builds</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class
="menu-title">Documentation</div><ul><li><a href="../changes.html">Changes per version</a></li><li><a href="../usermanual/get-started.html">Get Started</a></li><li><a href="../usermanual/index.html">User Manual</a></li><li><a href="../usermanual/best-practices.html">Best Practices</a></li><li><a href="../usermanual/component_reference.html">Component Reference</a></li><li><a href="../usermanual/functions.html">Functions Reference</a></li><li><a href="../api/index.html">Javadocs</a></li><li><a href="../building.html">Building JMeter and Add-Ons</a></li><li><a href="http://wiki.apache.org/jmeter">JMeter Wiki</a></li><li><a href="http://wiki.apache.org/jmeter/JMeterFAQ">FAQ (Wiki)</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Tutorials (PDF format)</div><ul><li><a href="../usermanual/jmeter_distributed_testing_step_by_step.pdf">Distributed Testing</a></li><li><a href="../usermanual/jmeter_proxy_step_by_step.pdf">Recording Tests</a></li><li><a
href="../usermanual/junitsampler_tutorial.pdf">JUnit Sampler</a></li><li><a href="../usermanual/jmeter_accesslog_sampler_step_by_step.pdf">Access Log Sampler</a></li><li><a href="../extending/jmeter_tutorial.pdf">Extending JMeter</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Community</div><ul><li><a href="http://wiki.apache.org/jmeter/JMeterCommitters">Contributors</a></li><li><a href="../mail.html">Mailing Lists</a></li><li><a href="../svnindex.html">SVN Repositories</a></li></ul></li></ul><ul class="menu"><li onClick="return true"><div class="menu-title">Foundation</div><ul><li><a href="http://www.apache.org/">ASF</a></li><li><a href="http://www.apache.org/foundation/getinvolved.html">Get Involved in the ASF</a></li><li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li><li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li></ul></li></ul></div><div class="main" id="content"><ul class="pa
gelinks"><li><a href="functions.html">< Prev</a></li><li><a href="../index.html">Index</a></li><li><a href="hints_and_tips.html">Next ></a></li></ul><div class="section"><h1 id="regex">21. Regular Expressions<a class="sectionlink" href="#regex" title="Link to here">¶</a></h1>
-<div class="subsection"><h2>21.1 Overview<a class="sectionlink" href="#overview" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="overview">21.1 Overview<a class="sectionlink" href="#overview" title="Link to here">¶</a></h2>
<p>
JMeter includes the pattern matching software <a href="http://attic.apache.org/projects/jakarta-oro.html">Apache Jakarta ORO</a>
<br>
@@ -74,7 +74,7 @@ The solution is to use <i>extended regul
See also <a href="#placement">Placement of modifiers</a> below.
</p>
</div>
-<div class="subsection"><h2>21.2 Examples<a class="sectionlink" href="#examples" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="examples">21.2 Examples<a class="sectionlink" href="#examples" title="Link to here">¶</a></h2>
<h3>Extract single string</h3>
<p>
Suppose you want to match the following portion of a web-page:
@@ -144,7 +144,7 @@ The following variables would be set:
These variables can be referred to later on in the JMeter test plan, as ${MYREF}, ${MYREF_g1} etc
</p>
</div>
-<div class="subsection"><h2>21.3 Line mode<a class="sectionlink" href="#line_mode" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="line_mode">21.3 Line mode<a class="sectionlink" href="#line_mode" title="Link to here">¶</a></h2>
<p>The pattern matching behaves in various slightly different ways,
depending on the setting of the multi-line and single-line modifiers.
Note that the single-line and multi-line operators have nothing to do with each other;
@@ -170,7 +170,7 @@ and the '$' metacharacter matches at the
</div>
-<div class="subsection"><h2>21.4 Meta characters<a class="sectionlink" href="#meta_chars" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="meta_chars">21.4 Meta characters<a class="sectionlink" href="#meta_chars" title="Link to here">¶</a></h2>
<p>
Regular expressions use certain characters as meta characters - these characters have a special meaning to the RE engine.
Such characters must be escaped by preceeding them with \ (backslash) in order to treat them as ordinary characters.
@@ -212,7 +212,7 @@ The following Perl5 extended regular exp
</div>
-<div class="subsection"><h2>21.5 Placement of modifiers<a class="sectionlink" href="#placement" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="placement">21.5 Placement of modifiers<a class="sectionlink" href="#placement" title="Link to here">¶</a></h2>
<p>
Modifiers can be placed anywhere in the regex, and apply from that point onwards.
[A bug in ORO means that they cannot be used at the very end of the regex.
Modified: jmeter/branches/docs-2.13/docs/usermanual/remote-test.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/usermanual/remote-test.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/usermanual/remote-test.html (original)
+++ jmeter/branches/docs-2.13/docs/usermanual/remote-test.html Sat Mar 28 00:21:35 2015
@@ -129,7 +129,7 @@ The second example will define remote_ho
The command-line client will exit when all the remote servers have stopped.
</p>
-<div class="subsection"><h2>15.1 Doing it Manually<a class="sectionlink" href="#detail_instructions" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="detail_instructions">15.1 Doing it Manually<a class="sectionlink" href="#detail_instructions" title="Link to here">¶</a></h2>
<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>
@@ -155,7 +155,7 @@ Use the "-s" option with the jmeter star
<p>Steps 2 and 3 remain the same.</p>
</div>
-<div class="subsection"><h2>15.2 Tips<a class="sectionlink" href="#tips" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="tips">15.2 Tips<a class="sectionlink" href="#tips" title="Link to here">¶</a></h2>
<p>
JMeter/RMI requires a connection from the client to the server. This will use the port you chose, default 1099.<br>
JMeter/RMI also requires a reverse connection in order to return sample results from the server to the client.<br>
@@ -198,7 +198,7 @@ in remote testing, since JMeter 2.6:</p>
loopback interface is now allowed to be used if it has been specified directly using the Java System Property "java.rmi.server.hostname" parameter.</li>
</ul>
</div>
-<div class="subsection"><h2>15.3 Using a different port<a class="sectionlink" href="#portchange" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="portchange">15.3 Using a different port<a class="sectionlink" href="#portchange" title="Link to here">¶</a></h2>
<p>By default, JMeter uses the standard RMI port 1099. It is possible to change this. For this to work successfully, all the following need to agree:</p>
<ul>
<li>On the server, start rmiregistry using the new port number</li>
@@ -226,7 +226,7 @@ The chosen port will be logged in the se
</p>
</div>
-<div class="subsection"><h2>15.4 Using a different sample sender<a class="sectionlink" href="#sendermode" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="sendermode">15.4 Using a different sample sender<a class="sectionlink" href="#sendermode" title="Link to here">¶</a></h2>
<p>
Listeners in the test plan send their results back to the client JMeter which writes the results to the specified files
By default, samples are sent back synchronously as they are generated.
@@ -291,7 +291,7 @@ This is not really a problem as there is
</div>
-<div class="subsection"><h2>15.5 Dealing with nodes that failed starting<a class="sectionlink" href="#retries" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="retries">15.5 Dealing with nodes that failed starting<a class="sectionlink" href="#retries" title="Link to here">¶</a></h2>
<p>
For large-scale tests there is a chance that some part of remote servers will be unavailable or down.
For example, when you use automation script to allocate many cloud machines and use them as generators,
Modified: jmeter/branches/docs-2.13/docs/usermanual/test_plan.html
URL: http://svn.apache.org/viewvc/jmeter/branches/docs-2.13/docs/usermanual/test_plan.html?rev=1669716&r1=1669715&r2=1669716&view=diff
==============================================================================
--- jmeter/branches/docs-2.13/docs/usermanual/test_plan.html (original)
+++ jmeter/branches/docs-2.13/docs/usermanual/test_plan.html Sat Mar 28 00:21:35 2015
@@ -40,7 +40,7 @@ is off by default). </p>
<p>If you are not recording the data to file, this option makes no difference.</p>
<p>You can also use the Configuration button on a listener to decide what fields to save.</p>
-<div class="subsection"><h2>4.1 Thread Group<a class="sectionlink" href="#thread_group" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="thread_group">4.1 Thread Group<a class="sectionlink" href="#thread_group" title="Link to here">¶</a></h2>
<p>Thread group elements are the beginning points of any test plan.
All controllers and samplers must be under a thread group.
Other elements, e.g. Listeners, may be placed directly under the test plan,
@@ -83,7 +83,7 @@ Start with Ramp-up = number of threads a
Note that delay overrides start-time, and duration over-rides end-time.</p>
</div>
-<div class="subsection"><h2>4.2 Controllers<a class="sectionlink" href="#controllers" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="controllers">4.2 Controllers<a class="sectionlink" href="#controllers" title="Link to here">¶</a></h2>
<p>
JMeter has two types of Controllers: Samplers and Logical Controllers.
@@ -104,7 +104,7 @@ For more information, see <a href="#logi
</div>
-<div class="subsection"><h2>4.2.1 Samplers<a class="sectionlink" href="#samplers" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="samplers">4.2.1 Samplers<a class="sectionlink" href="#samplers" title="Link to here">¶</a></h2>
<p>
Samplers tell JMeter to send requests to a server and wait for a response.
@@ -144,7 +144,7 @@ expressions.</p>
<p><a href="component_reference.html#samplers">JMeter's built-in samplers</a></p>
</div>
-<div class="subsection"><h2>4.2.2 Logic Controllers<a class="sectionlink" href="#logic_controller" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="logic_controller">4.2.2 Logic Controllers<a class="sectionlink" href="#logic_controller" title="Link to here">¶</a></h2>
<p>Logic Controllers let you customize the logic that JMeter uses to
decide when to send requests.
Logic Controllers can change the order of requests coming from their
@@ -224,7 +224,7 @@ will share the same cookies.</p>
Logic Controllers</a>.</p>
</div>
-<div class="subsection"><h2>4.2.3 Test Fragments<a class="sectionlink" href="#test_fragments" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="test_fragments">4.2.3 Test Fragments<a class="sectionlink" href="#test_fragments" title="Link to here">¶</a></h2>
<p>The Test Fragment element is a special type of <a href="#controllers">controller</a> that
exists on the Test Plan tree at the same level as the Thread Group element. It is distinguished
from a Thread Group in that it is not executed unless it is
@@ -233,7 +233,7 @@ referenced by either a <a href="../userm
<p>This element is purely for code re-use within Test Plans and was introduced in Version 2.5</p>
</div>
-<div class="subsection"><h2>4.3 Listeners<a class="sectionlink" href="#listeners" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="listeners">4.3 Listeners<a class="sectionlink" href="#listeners" title="Link to here">¶</a></h2>
<p>Listeners provide access to the information JMeter gathers about the test cases while
JMeter runs. The <a href="../usermanual/component_reference.html#Graph_Results">Graph Results</a> listener plots the response times on a graph.
The "View Results Tree" Listener shows details of sampler requests and responses, and can display basic HTML and XML representations of the response.
@@ -256,7 +256,7 @@ They will collect data only from element
that come with JMeter.</p>
</div>
-<div class="subsection"><h2>4.4 Timers<a class="sectionlink" href="#timers" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="timers">4.4 Timers<a class="sectionlink" href="#timers" title="Link to here">¶</a></h2>
<p>By default, a JMeter thread sends requests without pausing between each request.
We recommend that you specify a delay by adding one of the available timers to
@@ -276,7 +276,7 @@ To provide a pause at a single place in
</p>
</div>
-<div class="subsection"><h2>4.5 Assertions<a class="sectionlink" href="#assertions" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="assertions">4.5 Assertions<a class="sectionlink" href="#assertions" title="Link to here">¶</a></h2>
<p>Assertions allow you to assert facts about responses received from the
server being tested. Using an assertion, you can essentially "test" that your
@@ -303,7 +303,7 @@ and will count towards the error %age fo
</p>
</div>
-<div class="subsection"><h2>4.6 Configuration Elements<a class="sectionlink" href="#config_elements" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="config_elements">4.6 Configuration Elements<a class="sectionlink" href="#config_elements" title="Link to here">¶</a></h2>
<p>A configuration element works closely with a Sampler. Although it does not send requests
(except for <a href="../usermanual/component_reference.html#HTTP(S)_Test_Script_Recorder">HTTP(S) Test Script Recorder</a>), it can add to or modify requests.</p>
@@ -327,21 +327,21 @@ For simplicity, it is suggested that the
</div><div class="clear"></div>
</div>
-<div class="subsection"><h2>4.7 Pre-Processor Elements<a class="sectionlink" href="#preprocessors" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="preprocessors">4.7 Pre-Processor Elements<a class="sectionlink" href="#preprocessors" title="Link to here">¶</a></h2>
<p>A Pre-Processor executes some action prior to a Sampler Request being made.
If a Pre-Processor is attached to a Sampler element, then it will execute just prior to that sampler element running.
A Pre-Processor is most often used to modify the settings of a Sample Request just before it runs, or to update variables that aren't extracted from response text.
See the <a href="test_plan.html#scoping_rules"><b>scoping rules</b></a> for more details on when Pre-Processors are executed.</p>
</div>
-<div class="subsection"><h2>4.8 Post-Processor Elements<a class="sectionlink" href="#postprocessors" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="postprocessors">4.8 Post-Processor Elements<a class="sectionlink" href="#postprocessors" title="Link to here">¶</a></h2>
<p>A Post-Processor executes some action after a Sampler Request has been made.
If a Post-Processor is attached to a Sampler element, then it will execute just after that sampler element runs.
A Post-Processor is most often used to process the response data, often to extract values from it.
See the <a href="test_plan.html#scoping_rules"><b>scoping rules</b></a> for more details on when Post-Processors are executed.</p>
</div>
-<div class="subsection"><h2>4.9 Execution order<a class="sectionlink" href="#executionorder" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="executionorder">4.9 Execution order<a class="sectionlink" href="#executionorder" title="Link to here">¶</a></h2>
<ol start="0">
<li>Configuration elements</li>
<li>Pre-Processors</li>
@@ -394,7 +394,7 @@ Assertion 1
</p>
</div>
-<div class="subsection"><h2>4.10 Scoping Rules<a class="sectionlink" href="#scoping_rules" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="scoping_rules">4.10 Scoping Rules<a class="sectionlink" href="#scoping_rules" title="Link to here">¶</a></h2>
<p>
The JMeter test tree contains elements that are both hierarchical and ordered. Some elements in the test trees are strictly hierarchical (Listeners, Config Elements, Post-Procesors, Pre-Processors, Assertions, Timers), and some are primarily ordered (controllers, samplers). When you create your test plan, you will create an ordered list of sample request (via Samplers) that represent a set of steps to be executed. These requests are often organized within controllers that are also ordered. Given the following test tree:</p>
<figure><a href="../images/screenshots/scoping1.png"><img src="../images/screenshots/scoping1.png" width="" height="" alt="Example test tree"></a><figcaption>Example test tree</figcaption></figure>
@@ -421,7 +421,7 @@ only one Manager is used, but there is c
</div>
-<div class="subsection"><h2>4.11 Properties and Variables<a class="sectionlink" href="#properties" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="properties">4.11 Properties and Variables<a class="sectionlink" href="#properties" title="Link to here">¶</a></h2>
<p>
JMeter <b>properties</b> are defined in jmeter.properties (see <a href="get-started.html#configuring_jmeter">Gettting Started - Configuring JMeter</a> for more details).
@@ -457,7 +457,7 @@ These are global to the test plan, so ca
<div class="clear"></div><div class="note">Both variables and properties are case-sensitive.</div><div class="clear"></div>
</div>
-<div class="subsection"><h2>4.12 Using Variables to parameterise tests<a class="sectionlink" href="#using_variables" title="Link to here">¶</a></h2>
+<div class="subsection"><h2 id="using_variables">4.12 Using Variables to parameterise tests<a class="sectionlink" href="#using_variables" title="Link to here">¶</a></h2>
<p>
Variables don't have to vary - they can be defined once, and if left alone, will not change value.
So you can use them as short-hand for expressions that appear frequently in a test plan.