[Jmeter Wiki] Update of "JMeterAutomatedRemoteTesting" by JMeterAdmin

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jmeter Wiki" for change notification.

The "JMeterAutomatedRemoteTesting" page has been changed by JMeterAdmin:
http://wiki.apache.org/jmeter/JMeterAutomatedRemoteTesting?action=diff&rev1=5&rev2=6

Comment:
Fix up Jakarta references

   * have touched on remote testing (from GUI is fine)
  
  = Set up =
-  * In your existing test plan, make sure that any variations in testing make use of functions or variables. For example, if running a HTTP sampler, use HTTP Request Defaults to specify a host as `${__P(targetHost,localhost)}`. Other useful places for parameterisation might include number of threads, ramp-up period or scheduler duration in a thread group, using a format of `${__P(threadgroup.threads,500)}`  (The `__P` function is shorthand for `__property`. See the [http://jakarta.apache.org/jmeter/usermanual/functions.html#__P user manual] for more info on using this function).
+  * In your existing test plan, make sure that any variations in testing make use of functions or variables. For example, if running a HTTP sampler, use HTTP Request Defaults to specify a host as `${__P(targetHost,localhost)}`. Other useful places for parameterisation might include number of threads, ramp-up period or scheduler duration in a thread group, using a format of `${__P(threadgroup.threads,500)}`  (The `__P` function is shorthand for `__property`. See the [http://jmeter.apache.org/usermanual/functions.html#__P user manual] for more info on using this function).
   * Save your test plan and properties file to a directory.
   * Create a properties file containing all your variables. E.g. mytest.properties could contain threadgroup.threads=100, targetHost=my-target-host.com
   * The test plan does not need Listeners, as this will be configured via parameters. This will improve performance on the testing.