mstover1 02/02/28 16:09:07
Modified: xdocs velocity.properties
xdocs/stylesheets site.vsl
xdocs/usermanual component_reference.xml http-config.xml
index.xml
Log:
updating component reference
consolidating more pages
adding new features to the site.vsl template
Revision Changes Path
1.2 +1 -1 jakarta-jmeter/xdocs/velocity.properties
Index: velocity.properties
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/velocity.properties,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- velocity.properties 7 Mar 2001 06:38:36 -0000 1.1
+++ velocity.properties 1 Mar 2002 00:09:06 -0000 1.2
@@ -1 +1 @@
-resource.loader.1.resource.path = ../jakarta-site2/xdocs/stylesheets
+resource.loader.1.resource.path = ../jakarta-site2/xdocs/stylesheets
\ No newline at end of file
1.6 +33 -37 jakarta-jmeter/xdocs/stylesheets/site.vsl
Index: site.vsl
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/stylesheets/site.vsl,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- site.vsl 28 Feb 2002 22:51:42 -0000 1.5
+++ site.vsl 1 Mar 2002 00:09:06 -0000 1.6
@@ -140,7 +140,7 @@
#foreach ($items in $properties.getChildren("property"))
<tr>
<td>$items.getAttributeValue("name")</td>
- <td>$xmlout.outputString($items,true)</td>
+ <td>#runloop($items)</td>
<td>
#if($items.getAttributeValue("required") != "")
$items.getAttributeValue("required")
@@ -157,42 +157,54 @@
#macro (seeAlso $seeAlso)
<p><b>See Also:</b>
<br/>
- #foreach ($items in $seeAlso.getChildren("link"))
- <a
href="$items.getAttributeValue("href")">$xmlout.outputString($items,true)</a>,
+ #foreach ($items in $seeAlso.getChildren())
+ #if($items.getName() == "link")
+ <a
href="$items.getAttributeValue("href")">$xmlout.outputString($items,true)</a>,
+ #elseif($items.getName() == "complink")
+ #complink($items),
+ #end
#end
</p>
#end
#macro (figure $figure)
<table border="0" cellspacing="0" cellpadding="0"><tr><td><img
src="$figure.getAttributeValue("image")"><br/>
- <font
size="-1">$xmlout.outputString($figure,true)</font></td></tr></table><br/>
+ <font size="-1">#runloop($figure)</font></td></tr></table><br/>
#end
#macro (example $example)
<a name="$example.getAttributeValue("anchor")"/>
<p><b>$example.getAttributeValue("title")</b></p>
- #foreach ($items in $example.getChildren())
- #if ($items.getName().equals("figure"))
- #figure ($items)
- #else
- #unknown($items)
- #end
- #end
+ #runloop($example)
#end
#macro (note $note)
- <table border="1" bgcolor="$notebackground" cellspacing="0" cellpadding="2">
+ <p><table border="1" bgcolor="$notebackground" width="50%" cellspacing="0"
cellpadding="2">
<tr><td>#runloop($note)</td></tr>
- </table>
+ </table></p>
#end
#macro (unknown $node)
#if($node.getName() == "note")
#note($node)
#elseif($node.getName() == "complink")
- <a
href="$relativePath/usermanual/component_reference.html#$node.getAttributeValue("name").replace($space,$udsc)">$node.getAttributeValue("name")</a>
+ #complink($node)
#elseif($node.getName() == "figure")
#figure($node)
+ #elseif ($node.getName() == "links")
+ #seeAlso ($node)
+ #elseif ($node.getName() == "properties")
+ #properties ($node)
+ #elseif ($node.getName() == "example")
+ #example ($node)
+ #elseif ($node.getName().equals("source"))
+ #source ($node)
+ #elseif ($node.getName().equals("table"))
+ #table ($node)
+ #elseif ($node.getName().equals("component"))
+ #component($node)
+ #elseif ($node.getName().equals("subsection"))
+ #subsection ($node)
#else
#outputTag($node)
#runloop($node)
@@ -200,6 +212,10 @@
#end
#end
+#macro (complink $complink)
+ <a
href="$relativePath/usermanual/component_reference.html#$complink.getAttributeValue("name").replace($space,$udsc)">$complink.getAttributeValue("name")</a>
+#end
+
#macro (outputTag $tag)
<$tag.getName()#getAtts($tag)>
#end
@@ -212,8 +228,8 @@
</$tag.getName()>
#end
-#macro (runloop $item)
- #foreach ($node in $item.getMixedContent())
+#macro (runloop $itemToLoop)
+ #foreach ($node in $itemToLoop.getMixedContent())
#if($node.getClass().getName().indexOf("Element") > -1)
#unknown($node)
#else
@@ -234,17 +250,11 @@
<tr><td>
#foreach ( $items in $component.getChildren() )
#if ($items.getName().equals("description"))
- $xmlout.outputString($items,true)
+ #runloop($items)
<p><b>Control Panel</b></p>
#if ($screenshot != "")
<div align="center"><img
src="$screenshot"></div>
#end
- #elseif ($items.getName().equals("links"))
- #seeAlso ($items)
- #elseif ($items.getName().equals("properties"))
- #properties ($items)
- #elseif ($items.getName().equals("example"))
- #example ($items)
#else
#unknown($items)
#end
@@ -267,12 +277,6 @@
#foreach ( $items in $subsection.getChildren() )
#if ($items.getName().equals("img"))
#image ($items)
- #elseif ($items.getName().equals("source"))
- #source ($items)
- #elseif ($items.getName().equals("table"))
- #table ($items)
- #elseif ($items.getName().equals("component"))
- #component($items)
#else
#unknown($items)
#end
@@ -295,14 +299,6 @@
#foreach ( $items in $section.getChildren() )
#if ($items.getName().equals("img"))
#image ($items)
- #elseif ($items.getName().equals("source"))
- #source ($items)
- #elseif ($items.getName().equals("table"))
- #table ($items)
- #elseif ($items.getName().equals("subsection"))
- #subsection ($items)
- #elseif ($items.getName().equals("component"))
- #component($items)
#else
#unknown($items)
#end
1.6 +86 -26 jakarta-jmeter/xdocs/usermanual/component_reference.xml
Index: component_reference.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/component_reference.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- component_reference.xml 28 Feb 2002 22:51:42 -0000 1.5
+++ component_reference.xml 1 Mar 2002 00:09:06 -0000 1.6
@@ -16,7 +16,7 @@
<component index="13.1.1" name="FTP Request"
screenshot="../images/screenshots/gen-controller/ftp-request.gif">
<description>This controller lets you send an FTP "retrieve file" request to an FTP
server.
If you are going to send multiple requests to the same FTP server, consider
-using a <a href="ftp-config.html#request_defaults">FTP Request Defaults</a>
Configuration
+using a <complink name="FTP Request Defaults"/> Configuration
Element so you do not have to enter the same information for each FTP Request
Generative
Controller. </description>
<properties>
@@ -28,8 +28,8 @@
<property name="Password" required="Usually">FTP account password.</property>
</properties>
<links>
- <link href="assertion.html">Assertion</link>
- <link href="#ftp_request_defaults">FTP Request Defaults</link>
+ <link href="test_plan.html#assertions">Assertions</link>
+ <complink name="FTP Request Defaults"/>
<link href="build-ftp-test-plan.html">Building an FTP Test Plan</link>
</links>
@@ -442,7 +442,7 @@
</component>
-<component index="13.4.3" name="HTTP Proxy Server"
screenshot="../images/screenshots/proxy_control.gif">
+<component index="13.4.3" name="HTTP Proxy Server"
screenshot="../images/screenshots/http-config/http-proxy-server.gif">
<description><p>The Proxy Server allows JMeter to watch and record your actions
while you browse your web application
with your normal browser (such as Internet Explorer). JMeter will create test
sample objects and store them
@@ -456,15 +456,17 @@
<property name="Name" required="No">Descriptive name for this controller that
is shown in the tree.</property>
<property name="Port" required="Yes">The port that the Proxy Server listens
to. 8080 is the default, but you can change it
if that port is already in use on your machine.</property>
- <property name="Include" required="No">Regular expressions that are matched
against the full URL that is sampled. Allows filtering of requests that are recorded.
All requests pass through, but only
+ <property name="Patterns to Include" required="No">Regular expressions that
are matched against the full URL that is sampled. Allows filtering of requests that
are recorded. All requests pass through, but only
those that meet the requirements of the Include/Exclude fields are
<i>recorded</i>. If both Include and Exclude are
left empty, then everything is recorded (which can result in dozens of samples
recorded for each page, as images, stylesheets,
etc are recorded). <b>If there is at least one entry in the Include field,
then only requests that match one or more Include patterns are
recorded</b>.</property>
- <property name="Exclude" required="No">Regular expressions that are matched
against the URL that is sampled. Allows filtering of requests that are recorded. All
requests pass through, but only
- those that meet the requirements of the Include/Exclude fields are
<i>recorded</i>. If both Include and Exclude are
- left empty, then everything is recorded (which can result in dozens of samples
recorded for each page, as images, stylesheets,
- etc are recorded). <b>Any requests that match one or more Exclude pattern are
<i>not</i> recorded</b>.</property>
+ <property name="Patterns to Exclude" required="No">Regular expressions that
are matched against the URL that is sampled.
+ <b>Any requests that match one or more Exclude pattern are <i>not</i>
recorded</b>.</property>
+ <property name="Clear Buttons" required="N/A">Remove all regular expressions
from the list.</property>
+ <property name="Start Button" required="N/A">Start the proxy server. JMeter
writes the following message to the console once the proxy server
+has started up and is ready to take requests: "Proxy up and running!".</property>
+ <property name="Stop Button" required="N/A">Stop the proxy server.</property>
</properties>
<p>To add an entry to the Include or Exclude field, type the entry into the text
field, and hit "Enter" when done.
@@ -479,15 +481,16 @@
not.</p>
<p>When you are ready to begin, hit "start".</p>
+<note>You will need to edit the proxy settings of your browser to point at the
+appropriate server and port, where the server is the machine JMeter is running on,
and
+the port # is from the Proxy Control Panel shown above.</note>
<b>Where Do Samples Get Recorded?</b>
-<p>The samples will be recorded as Web Test controllers under any Simple Controller
elements in your tree (note, if you have more than one
-Simple Controller, they will all have duplicate Web Test controllers created for
them). If your Simple Controller has a
-Url Sample element with domain or path settings, then your Web Test controllers
will be created with blank domain and/or path settings (provided
-they match, of course). This allows you to simply create test plans with a single
top level config element to control which server name is
-being tested.</p>
-
-<p>If there are no Simple Controllers in your test plan, then no samples will be
recorded.</p>
+<p>JMeter places the recorded samples in the Thread Group, or if you have a Simple
Logic Controller, JMeter places
+them there. Also, if you have a HTTP Request Defaults element, then the recorded
samples will have empty fields for
+the default values you specified.</p>
+<note>If you have more than one Simple Logic Controller, JMeter records the samples
to each
+of your Simple Logic Controllers. We plan to correct this in a future
release.</note>
<p>When you are done recording your test samples, stop the proxy server (hit the
"stop" button). Remember to reset
your browser's proxy settings. Now, you may want to sort and re-order the test
script, add timers, listeners, a
@@ -495,24 +498,52 @@
</component>
-<component index="13.4.4" name="HTTP Request Defaults" screenshot="">
+<component index="13.4.4" name="HTTP Request Defaults"
+ screenshot="../images/screenshots/http-config/http-request-defaults.gif">
+<description><p>This element lets you set default values that your HTTP Request
controllers use. For example, if you are
+creating a Test Plan with 25 HTTP Request controllers and all of the requests are
being sent to the same server,
+you could add a single HTTP Request Defaults element with the "Server Name or IP"
field filled in. Then, when
+you add the 25 HTTP Request controllers, leave the "Server Name or IP" field empty.
The controllers will inherit
+this field value from the HTTP Request Defaults element.</p>
+</description>
+<properties>
+ <property name="Name" required="No">Descriptive name for this controller that
is shown in the tree.</property>
+ <property name="Server" required="Yes">Domain name or IP address of the web
server.</property>
+ <property name="Port" required="No (defaults to 80)">Port the web server is
listening to.</property>
+ <property name="Protocol" required="Yes">HTTP or HTTPS.</property>
+ <property name="Method" required="Yes">HTTP GET or HTTP POST.</property>
+ <property name="Path" required="Yes">The path to resource (for example,
/servlets/myServlet). If the
+resource requires query string parameters, add them below in the
+"Send Parameters With the Request" section.</property>
+ <property name="Send Parameters With the Request" required="No">The query
string will
+ be generated from the list of parameters you provide. Each parameter has a
<i>name</i> and
+ <i>value</i>. The query string will be generated in the correct fashion,
depending on
+ the choice of "Method" you made (ie if you chose GET, the query string will be
+ appended to the URL, if POST, then it will be sent separately). Also, if you
are
+ sending a file using a multipart form, the query string will be created using
the
+ multipart form specifications.</property>
+</properties>
</component>
-<component index="13.4.5" name="FTP Request Defaults"
screenshot="../images/screenshots/ftp-config/ftp-request-defaults.gif">
-
+<component index="13.4.5" name="FTP Request Defaults"
+ screenshot="../images/screenshots/ftp-config/ftp-request-defaults.gif">
+<description></description>
</component>
-<component index="13.4.6" name="JDBC Database Connection Pool Defaults"
screenshot="">
-
+<component index="13.4.6" name="JDBC Database Connection Pool Defaults"
+ screenshot="../images/screenshots/jdbc-config/jdbc-db-conn-pool.gif">
+<description></description>
</component>
-<component index="13.4.7" name="JDBC Database Login Defaults" screenshot="">
-
+<component index="13.4.7" name="JDBC Database Login Defaults"
+ screenshot="../images/screenshots/jdbc-config/jdbc-db-login.gif">
+<description></description>
</component>
-<component index="13.4.8" name="JDBC SQL Query Defaults" screenshot="">
-
+<component index="13.4.8" name="JDBC SQL Query Defaults"
+ screenshot="../images/screenshots/jdbc-config/jdbc-sql-query.gif">
+<description></description>
</component>
<component index="13.4.9" name="HTML Link Parser" anchor="html_link_parser">
@@ -556,11 +587,40 @@
will choose at random, and replace the value in your URL test sample. Each time
through
the test, a new random value will be chosen.</p>
-<figure image="../images/screenshots/modification.gif">Figure 6 - Online Poll
Example</figure>
+<figure image="../images/screenshots/modification.gif">Figure 8 - Online Poll
Example</figure>
<note>One important thing to remember is that you must create a test sample
immediately
prior that will return an HTML page with the links and forms that are relevant to
your dynamic test sample.</note>
+</example>
+
+</component>
+
+<component index="13.4.10" name="HTTP Header Manager"
screenshot="../images/screenshots/http-config/http-header-manager.gif">
+<description><p>The Header Manager lets you add or override HTTP request
headers.</p>
+</description>
+
+<properties>
+ <property name="Name" required="No">Descriptive name for this element that is
shown in the tree. </property>
+ <property name="Name (Header)" required="No (You should have at least one,
however)">Name of the request header.
+ Two common request headers you may want to experiment with
+are "User-Agent" and "Referer".</property>
+ <property name="Value" required="No (You should have at least one,
however)">Request header value.</property>
+ <property name="Add Button" required="N/A">Add an entry to the header
table.</property>
+ <property name="Delete Button" required="N/A">Delete the currently selected table
entry.</property>
+ <property name="Load Button" required="N/A">Load a previously saved header table
and add the entries to the existing
+header table entries.</property>
+ <property name="Save As Button" required="N/A">Save the current header table to a
file.</property>
+</properties>
+
+<example title="Header Manager example" anchor="header_manager_example">
+
+<p><a href="../demos/HeaderManagerTestPlan.jmx">Download</a> this example. In this
example, we created a Test Plan
+that tells JMeter to override the default "User-Agent" request header and use a
particular Internet Explorer agent string
+instead. (see figures 9 and 10).</p>
+
+<figure
image="../images/screenshots/http-config/header-manager-example1a.gif">Figure 9 - Test
Plan</figure>
+<figure
image="../images/screenshots/http-config/header-manager-example1b.gif">Figure 10 -
Header Manager Control Panel</figure>
</example>
</component>
1.5 +0 -245 jakarta-jmeter/xdocs/usermanual/http-config.xml
Index: http-config.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/http-config.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- http-config.xml 24 Feb 2002 17:52:18 -0000 1.4
+++ http-config.xml 1 Mar 2002 00:09:06 -0000 1.5
@@ -6,253 +6,8 @@
</properties>
<body>
-
-<section name="4.7 HTTP Configuration Elements" anchor="elements">
-<p>A configuration element works closely with a Generative Controller. Although it
does not send requests
-(except for Proxy Server), it can add to or modify requests and handle
responses.</p>
-<p>A configuration element is accessible from only inside the tree branch where you
place the element.
-For example, if you place an HTTP Cookie Manager inside a Simple Logic Controller,
the Cookie Manager will
-only be accessible to HTTP Request Controllers you place inside the Simple Logic
Controller (see figure 1).
-The Cookie Manager is accessible to the HTTP requests "Web Page 1" and "Web Page
2", but not "Web Page 3". </p>
-<p>Also, a configuration element inside a tree branch has higher precedence than
the same element in a "parent"
-branch. For example, we defined two HTTP Request Defaults elements, "Web Defaults
1" and "Web Defaults 2".
-Since we placed "Web Defaults 1" inside a Loop Controller, only "Web Page 2" can
access it. The other HTTP
-requests will use "Web Defaults 2", since we placed it in the Thread Group (the
"parent" of all other branches).</p>
-
-<p><img src="../images/screenshots/http-config/http-config-example.gif" width="240"
height="240"></img>
-<br>Figure 1 - Test Plan Showing Accessability of Configuration Elements</br></p>
-
-
-</section>
-
-<section name="4.7.1 HTTP Authorization Manager" anchor="auth_manager">
-<p>The Authorization Manager lets you specify one or more user logins for web pages
that are
-restricted using Basic HTTP Authentication. You see this type of authentication
when you use
-your browser to access a restricted page, and your browser displays a login dialog
box. JMeter
-transmits the login information when it encounters this type of page.</p>
-
-<p>
-<table border="1" cellspacing="0" cellpadding="5">
- <tr><td><b>NOTE:</b> In the current release, all JMeter threads in a Thread Group
use the same username/password
-for a given Base URL even if you create multiple users with the same Base URL in
the authorization table.
-We plan to correct this in a future release. As a workwaround, you can create
multiple Thread Groups for your
-Test Plan, with each Thread Group having its own Authorization Manager.</td></tr>
-</table>
-</p>
-
-<p><b>Control Panel</b></p>
-<p><img src="../images/screenshots/http-config/http-auth-manager.gif" width="575"
height="340"></img>
-<br>Figure 2 - Authorization Manager Control Panel</br></p>
-<p>Properties:
-<ul>
- <li>Name - Descriptive name for this element that is shown in the tree. </li>
- <li>Base URL - A partial or complete URL that matches one or more HTTP Request
URLs. As an example,
-say you specify a Base URL of "http://jakarta.apache.org/restricted/"; with a
username of "jmeter" and
-a password of "jmeter". If you send an HTTP request to the URL
-"http://jakarta.apache.org/restricted/ant/myPage.html";, the Authorization Manager
sends the login
-information for the user named, "jmeter".</li>
- <li>Username - The username to authorize.</li>
- <li>Password - The password to authorize.</li>
- <li>Add Button - Add an entry to the authorization table.</li>
- <li>Delete Button - Delete the currently selected table entry.</li>
- <li>Load Button - Load a previously saved authorization table and add the entries
to the existing
-authorization table entries.</li>
- <li>Save As Button - Save the current authorization table to a file.</li>
-</ul>
-</p>
-
-<p>
-<table border="1" cellspacing="0" cellpadding="5">
- <tr><td><b>NOTE:</b> When you save the Test Plan, JMeter automatically saves all
of the authorization
-table entries.</td></tr>
-</table>
-</p>
-
-<p><b>Example</b></p>
-
-<p><a href="../demos/AuthManagerTestPlan.jmx">Download</a> this example. In this
example, we created a Test Plan on a local server that sends three HTTP requests, two
requiring a login and the
-other is open to everyone. See figure 3 to see the makeup of our Test Plan. On
our server, we have a restricted
-directory named, "secret", which contains two files, "index.html" and
"index2.html". We created a login id named, "kevin",
-which has a password of "spot". So, in our Authorization Manager, we created an
entry for the restricted directory and
-a username and password (see figure 4). The two HTTP requests named "SecretPage1"
and "SecretPage2" make requests
-to "/secret/index1.html" and "/secret/index2.html". The other HTTP request, named
"NoSecretPage" makes a request to
-"/index.html".</p>
-
-<p>When we run the Test Plan, JMeter looks in the Authorization table for the URL
it is requesting. If the Base URL matches
-the URL, then JMeter passes this information along with the request.</p>
-
-<p>
-<table border="1" cellspacing="0" cellpadding="5">
- <tr><td><b>NOTE:</b> You can download the Test Plan, but since it is built as a
test for our local server, you will not
-be able to run it. However, you can use it as a reference in constructing your own
Test Plan.</td></tr>
-</table>
-</p>
-
-<p><img src="../images/screenshots/http-config/auth-manager-example1a.gif"
width="292" height="205"></img>
-<br>Figure 3 - Test Plan</br></p>
-
-<p><img src="../images/screenshots/http-config/auth-manager-example1b.gif"
width="572" height="341"></img>
-<br>Figure 4 - Authorization Manager Control Panel</br></p>
-
-</section>
-
-<section name="4.7.2 HTTP Cookie Manager" anchor="cookie_manager">
-<p>The Cookie Manager element has two functions.</p>
-<p>First, it stores and sends cookies just like a web browser. If you
-have an HTTP Request and the response contains a cookie, the Cookie Manager
automatically stores that cookie and will use
-if, for all future request that particular request. Each JMeter thread has its own
"cookie storage area". So, if you
-are testing a web site that uses a cookie for storing session information, each
JMeter thread will have its own session.</p>
-<p>Second, you can manually add a cookie to the Cookie Manager. However, if you do
this, the cookie will be
-exposed to all JMeter threads.</p>
-<p><b>Control Panel</b></p>
-<p><img src="../images/screenshots/http-config/http-cookie-manager.gif" width="573"
height="340"></img>
-<br>Figure 5 - Cookie Manager Control Panel</br></p>
-<p>Properties:
-<ul>
- <li>Name - Descriptive name for this element that is shown in the tree. </li>
- <li>Base URL - A partial or complete URL that matches one or more HTTP Request
URLs. As an example,
-say you specify a Base URL of "http://jakarta.apache.org/restricted/"; with a
username of "jmeter" and
-a password of "jmeter". If you send an HTTP request to the URL
-"http://jakarta.apache.org/restricted/ant/myPage.html";, the Authorization Manager
sends the login
-information for the user named, "jmeter".</li>
- <li>Username - The username to authorize.</li>
- <li>Password - The password to authorize.</li>
- <li>Add Button - Add an entry to the authorization table.</li>
- <li>Delete Button - Delete the currently selected table entry.</li>
- <li>Load Button - Load a previously saved authorization table and add the entries
to the existing
-authorization table entries.</li>
- <li>Save As Button - Save the current authorization table to a file.</li>
-</ul>
-</p>
-
-</section>
-
-<section name="4.7.3 HTTP Header Manager" anchor="header_manager">
-<p>The Header Manager lets you add or override HTTP request headers.</p>
-<p><b>Control Panel</b></p>
-<p><img src="../images/screenshots/http-config/http-header-manager.gif" width="574"
height="341"></img>
-<br>Figure 6 - Header Manager Control Panel</br></p>
-<p>Properties:
-<ul>
- <li>Name - Descriptive name for this element that is shown in the tree. </li>
- <li>Name (Header) - Name of the request header. Two common request headers you
may want to experiment with
-are "User-Agent" and "Referer".</li>
- <li>Value - Request header value.</li>
- <li>Add Button - Add an entry to the header table.</li>
- <li>Delete Button - Delete the currently selected table entry.</li>
- <li>Load Button - Load a previously saved header table and add the entries to the
existing
-header table entries.</li>
- <li>Save As Button - Save the current header table to a file.</li>
-</ul>
-</p>
-
-<p><b>Example</b></p>
-
-<p><a href="../demos/HeaderManagerTestPlan.jmx">Download</a> this example. In this
example, we created a Test Plan
-that tells JMeter to override the default "User-Agent" request header and use a
particular Internet Explorer agent string
-instead. (see figures 7 and 8).</p>
-
-<p><img src="../images/screenshots/http-config/header-manager-example1a.gif"
width="205" height="150"></img>
-<br>Figure 7 - Test Plan</br></p>
-
-<p><img src="../images/screenshots/http-config/header-manager-example1b.gif"
width="573" height="334"></img>
-<br>Figure 8 - Header Manager Control Panel</br></p>
-
-
-</section>
-
-<section name="4.7.4 HTTP Proxy Server" anchor="proxy_server">
-<p>The Proxy Server acts as a gateway between your web browser and the Internet (or
your ISP's proxy server, if applicable).
-Instead of manually creating HTTP Request controllers, you can use a web browser.
In order to do this, you need to configure
-your browser to use the JMeter proxy server. This proxy server listens to your
browser's HTTP requests and creates the necessary HTTP Request
-controllers. You can place the Proxy Server element in the Thread Group. It is ok
to leave this element when you run the
-Test Plan because it will not affect JMeter.</p>
-<p>JMeter places the HTTP Request controllers in the Thread Group, or if you have a
Simple Logic Controller, JMeter places
-them there. Also, if you have a HTTP Request Defaults element, then the HTTP
Request controllers will have empty fields for
-the default values you specified.</p>
-<p>
-<table border="1" cellspacing="0" cellpadding="5">
- <tr><td><b>NOTE:</b> If you have more than one Simple Logic Controller, JMeter
adds HTTP Request Controllers to each
-of your Simple Logic Controllers. We plan to correct this in a future
release.</td></tr>
-</table>
-</p>
-<p>The Include and Exclude fields allow you to filter requests. If, for example,
you leave both fields blank, then JMeter
-will record every action of your browser. This can often result in 20+ test samples
being recorded for each web page
-(it will record all image requests, CSS files, Javascript files, etc). This is
probably not desirable. The Include/Exclude fields
-give you some say over what gets recorded. </p>
-<p>If the Include field is left empty, then all requests will "pass" the include
test. If the Exclude field is left empty, then all
-request will "pass" the exclude test. Once the Include field has at least one
entry, then only those requests that match at
-least one entry will "pass" ("pass" means "be recorded"). </p>
-<p>If the Exclude field is left empty, then all requests (that have passed the
Include field check) will pass. If there are
-entries in the Exclude field, then any request that matches at least one entry will
not be recorded.</p>
-<p><b>Control Panel</b></p>
-<p><img src="../images/screenshots/http-config/http-proxy-server.gif" width="398"
height="288"></img>
-<br>Figure 9 - Proxy Server Control Panel</br></p>
-<p>Properties:
-<ul>
- <li>Name - Descriptive name for this element that is shown in the tree. </li>
- <li>Port - Port the proxy server listens for your browser's requests. The
default port is 8080.</li>
- <li>Patterns to Include - Regular expression patterns describing which links you
want JMeter to create
-HTTP Request controllers. For example, the pattern, <b>.*\.jsp</b>, means all
links that have an extension of ".jsp". After
-typing the regular expression, press the ENTER/RETURN key to add the regular
expression to the list.</li>
- <li>Patterns to Exclude - Regular expression patterns describing which links you
do not want JMeter to create
-HTTP Request controllers. After typing the regular expression, press the
ENTER/RETURN key to add the regular expression
-to the list.</li>
- <li>Clear Buttons - Remove all regular expressions from the list.</li>
- <li>Start Button - Start the proxy server. JMeter writes the following message
to the console once the proxy server
-has started up and is ready to take requests: "Proxy up and running!".</li>
- <li>Stop Button - Stop the proxy server.</li>
-</ul>
-</p>
-<p><b>Example</b></p>
-
-<p><a href="../demos/ProxyServerTestPlan.jmx">Download</a> this example. In this
example, we created a basic Test Plan
-that tells JMeter to create a proxy server (see figure 10).</p>
-
-<p><img src="../images/screenshots/http-config/proxy-server-example1a.gif"
width="188" height="112"></img>
-<br>Figure 10 - Test Plan</br></p>
-
-
-</section>
-
<section name="4.7.5 HTTP Request Defaults" anchor="request_defaults">
-<p>This element lets you set default values that your HTTP Request controllers use.
For example, if you are
-creating a Test Plan with 25 HTTP Request controllers and all of the requests are
being sent to the same server,
-you could add a single HTTP Request Defaults element with the "Server Name or IP"
field filled in. Then, when
-you add the 25 HTTP Request controllers, leave the "Server Name or IP" field empty.
The controllers will inherit
-this field value from the HTTP Request Defaults element.</p>
-<p><b>Control Panel</b></p>
-<p><img src="../images/screenshots/http-config/http-request-defaults.gif"
width="569" height="448"></img>
-<br>Figure 11 - Request Defaults Control Panel</br></p>
-<p><b>Property Descriptions:</b>
-<ul>
- <li><b>Name</b> - Descriptive name for this controller that is shown in the tree.
</li>
- <li><i>Web Server</i></li>
- <ul>
- <li><b>Server Name or IP</b> - Domain name or IP address of the web
server.</li>
- <li><b>Port</b> - (optional) Port the web server is listening. If you leave
this field
-empty, JMeter assumes the default port.</li>
- </ul>
- <li><i>HTTP Request</i></li>
- <ul>
- <li><b>Protocol</b> - HTTP or HTTPS.</li>
- <li><b>Method</b> - HTTP GET or HTTP POST.</li>
- <li><b>Path</b> - The path to resource (for example, /servlets/myServlet). If
the
-resource requires query string parameters, add them below in the
-"Send Parameters With the Request" section.</li>
- <li><i>Send Parameters With the Request</i></li>
- <ul>
- <li><b>Name</b> - Parameter name</li>
- <li><b>Value</b> - Parameter value. You do not have to enter the value in
-URL-Encoded format. JMeter will URL-Encode it for you when it sends
-the HTTP request.</li>
- <li><b>Add</b> Button - Add a parameter.</li>
- <li><b>Delete</b> Button - Delete the currently selected parameter.</li>
- </ul>
- </ul>
-</ul>
-</p>
</section>
</body>
1.14 +1 -0 jakarta-jmeter/xdocs/usermanual/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-jmeter/xdocs/usermanual/index.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- index.xml 28 Feb 2002 22:51:42 -0000 1.13
+++ index.xml 1 Mar 2002 00:09:06 -0000 1.14
@@ -125,6 +125,7 @@
<li>13.4.7 <complink name="JDBC Database Login Defaults"/></li>
<li>13.4.8 <complink name="JDBC SQL Query Defaults"/></li>
<li>13.4.9 <complink name="HTML Link Parser"/></li>
+ <li>13.4.10 <complink name="HTTP Header Manager"/></li>
</ul>
<li><a href="component_reference.html#assertions">13.5
Assertions</a></li>
<ul>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
