Index: xdocs/usermanual/component_reference.xml =================================================================== RCS file: /home/cvspublic/jakarta-jmeter/xdocs/usermanual/component_reference.xml,v retrieving revision 1.27 diff -u -r1.27 component_reference.xml --- xdocs/usermanual/component_reference.xml 15 Oct 2002 20:28:42 -0000 1.27 +++ xdocs/usermanual/component_reference.xml 15 Dec 2002 12:59:24 -0000 @@ -81,7 +81,7 @@ multipart form specifications.

Additionally, you can specify whether each paramter should be URL encoded. If you are not sure what this - means, it is probably best to select it. If your values contain characters such as & or spaces, or + means, it is probably best to select it. If your values contain characters such as & or spaces, or question marks, then encoding is usually required.

Name of the file to send. If left blank, JMeter does not send a file, if filled in, JMeter automatically sends the request as @@ -181,7 +181,7 @@ Descriptive name for this sampler that is shown in the tree. The URL to direct the SOAP request to. - The Soap XML message, or XML-RPC + The Soap XML message, or XML-RPC instructions. @@ -375,7 +375,7 @@
-

The mailer visualizer can be set up to send email if a test run receives too many +

The mailer visualizer can be set up to send email if a test run receives too many failed responses from the server.

 @@ -409,7 +409,7 @@ includes any delays you added to your test and JMeter's own internal processing time. The advantage of doing the calculation like this is that this number represents something real - your server in fact handled that many requests per minute, and you can increase the number of threads -and/or decrease the delays to discover your server's maximum throughput. Whereas if you made calculations +and/or decrease the delays to discover your server's maximum throughput. Whereas if you made calculations that factored out delays and JMeter's processing, it would be unclear what you could conclude from that number.

 @@ -444,8 +444,8 @@ -This visualizer creates a row for every sample result. Each sample result's URL, -time in milliseconds, success/failure is displayed. Like the , +This visualizer creates a row for every sample result. Each sample result's URL, +time in milliseconds, success/failure is displayed. Like the , this visualizer uses a lot of memory. @@ -678,11 +678,11 @@

Allows the user to specify values for User Variables specific to individual threads.

User Variables can also be specified in the Test Plan but not specific to individual threads. This panel allows -you to specify a series of values for any User Variable. For each thread, the variable will be assigned one of the values from the series +you to specify a series of values for any User Variable. For each thread, the variable will be assigned one of the values from the series in sequence. If there are more threads than values, the values get re-used. For example, this can be used to assign a distinct user id to be used by each thread. User variables can be referenced in any field of any jMeter Component.

-

The variable is specified by clicking the Add Variable button in the bottom of the panel and filling in the Variable name in the 'Name:' column. +

The variable is specified by clicking the Add Variable button in the bottom of the panel and filling in the Variable name in the 'Name:' column. To add a new value to the series, click the 'Add User' button and fill in the desired value in the newly added column.

Values can be accessed in any test component in the same thread group, using the function syntax: ${variable}.

@@ -704,7 +704,7 @@ This controls how you refer to this value in other elements. Syntax is as in user-defined values: $(reference_name}. In other words, is this a global counter, or does each user get their - own counter? If unchecked, the counter is global (ie, user #1 will get value "1", and user #2 will get value "2" on + own counter? If unchecked, the counter is global (ie, user #1 will get value "1", and user #2 will get value "2" on the first iteration). If checked, each user has an independent counter. @@ -752,7 +752,7 @@ Descriptive name for this element that is shown in the tree. The maximum number of milliseconds each response is allowed before being marked as failed. - + @@ -861,16 +861,16 @@ it is easier to use than the HTML Link Parser, and more efficient. For web applications that use URL Re-writing to store session ids instead of cookies, this element can be attached at the ThreadGroup level, much like the . Simply give it the name -of the session id parameter, and it will find it on the page and add the argument to every +of the session id parameter, and it will find it on the page and add the argument to every request of that ThreadGroup.

-

Alternatively, this modifier can be attached to select requests and it will modify only them. -Clever users will even determine that this modifier can be used to grab values that elude the +

Alternatively, this modifier can be attached to select requests and it will modify only them. +Clever users will even determine that this modifier can be used to grab values that elude the .

Descriptive name given to this element in the test tree. - The name of the parameter to grab from + The name of the parameter to grab from previous response. This modifier will find the parameter anywhere it exists on the page, and grab the value assigned to it, whether it's in an HREF or a form. Some web apps rewrite URLs by appending @@ -886,7 +886,7 @@ parameter to the requests list of arguments.

The value of the argument in your HTTP Request must be a '*' in order for the HTML Parameter Mask Modifier to replace it. -

As an example, the username for a login script could be modified to send a series of values +

As an example, the username for a login script could be modified to send a series of values such as:
user_1
user_2
@@ -899,7 +899,7 @@ modify or add to the HTTP Request. A string value to prefix to every generated value. A number value to start the counter at. - A number value to end the counter, at which point it restarts + A number value to end the counter, at which point it restarts with the Lower Bound value. Value to increment the counter by each time through. A string value to add as suffix to every generated vaue. @@ -910,8 +910,8 @@

The User Parameter Modifier uses an XML file get values for HTTP arguments. Any HTTP Request that this modifier modifies will be checked for the existence of the specified arguments. If found, the values for those arguments will be replaced by the values found in the -xml file. The XML file can have multiple sets of the same values. This modifier will iterate -through these values in a round-robin style, thus each request will get a different set of values +xml file. The XML file can have multiple sets of the same values. This modifier will iterate +through these values in a round-robin style, thus each request will get a different set of values until the last set of values is reached, at which point it will begin again at the first set.

If the number of value sets is equal to the number of threads in your test, then it will work out that each thread will get the same set of values each time, which will be a different set from @@ -989,13 +989,21 @@ specific functions.

-

The Regex Function is used to parse the previous response using any regular +

The Regex Function is used to parse the previous response using any regular expression (provided by user). The function returns the template string with variable values filled in.

The __regexFunction stores values for future use. In the sixth parameter, you can specify a reference name. After this function executes, the same values can be retrieved at later times -using the syntax for user-defined values. For instance, ${refName_g1} would refer to the first -group parsed by this function. ${refName_g0} always refers to the entire match.

 +using the syntax for user-defined values. For instance, if you enter "refName" as the sixth +parameter you will be able to use: +
    +
  • ${refName} to refer to the computed result of the second parameter ("Template for the +replacement string") parsed by this function
    • +
  • ${refName_g0} to refer to the entire match parsed by this function.
    • +
  • ${refName_g1} to refer to the first group parsed by this function.
    • +
  • ${refName_g#} to refer to the nth group parsed by this function.
    • +
+

The first argument is the regular expression @@ -1010,7 +1018,7 @@ $[group_number]$. Ie: $1$, or $2$. Your template can be any string. The third argument tells JMeter which match to use. Your regular expression might find numerous matches. You have four choices: -
  • An integer - Tells JMeter to use that match. '1' for the first found match, '2' for the +
    • An integer - Tells JMeter to use that match. '1' for the first found match, '2' for the second, and so on
    • RAND - Tells JMeter to choose a match at random.
    • ALL - Tells JMeter to use all matches, and create a template string for each one and then @@ -1021,8 +1029,9 @@ If 'ALL' was selected for the above argument value, then this argument will be inserted between each appended copy of the template value. Default value returned if no match is found - A reference name for reusing the values parsed by this function.
      - Stored values are of the form ${refName_g#} where "#" is the group number from the regular expression.       + A reference name for reusing the values parsed by this function.
      + Stored values are ${refName} (the replacement template string) and ${refName_g#} where "#" is the + group number from the regular expression ("0" can be used to refer to the entire match).       @@ -1034,7 +1043,7 @@ counting how many times that request was run.

      - TRUE if you wish each simulated user's counter + TRUE if you wish each simulated user's counter to be kept independent and separate from the other users. FALSE for a global counter. A reference name for reusing the value created by this function.
      @@ -1044,7 +1053,7 @@ -

      The thread number function simply returns the number of the thread currently +

      The thread number function simply returns the number of the thread currently being executed. These numbers are independent of ThreadGroup, meaning thread #1 in one threadgroup is indistinguishable from thread #1 in another threadgroup, from the point of view of this function.