Run JMeter Tests from Performance Center

This topic provides an overview of running Apache JMeter tests from Performance Center.

Note: This feature is released as a beta version.

JMeter tests overview

Apache JMeter is an open source load testing tool for analyzing and measuring the performance of a variety of services, with a focus on web applications. If you work with Apache JMeter tests, Performance Center provides the ability to also run the tests.

By including JMeter (.jmx) scripts in your tests, you can run one or more JMeter tests side-by-side with any other Performance Center tests, giving you a single entry point for executing your performance tests.

Measurements can be viewed online and offline (via Performance Center and Analysis), using the data points from the JMeter tests.

Back to top

Set up the JMeter test

This task describes how to upload JMeter scripts to Performance Center and configure runtime settings.

  1. Prerequisites:

    • Download and install JMeter and the latest 64-bit JRE or JDK on all load generator machines on which the script will be run. For JMeter download details, see the Apache documentation. For supported versions of JMeter, see the System Requirements.

    • When installing JMeter, it is recommended to install it on the same path for all the load generators, since you need to enter this path when configuring runtime settings in the Performance Test Designer (see step 3).

    • For existing projects (created in Performance Center versions earlier than 12.55), you need to add support for JMeter script types to the ALM server. For details, see Run JMeter Tests from Performance Center.

    • Create scripts in JMeter and save the scripts locally. The scripts must be saved in ZIP format and must include all the files in the test scripts folder (typically, .jmx and .csv files).

  2. Upload JMeter scripts to Performance Center

    1. On the My Performance Center navigation bar, select Test Management > Test Plan.

    2. Click the Upload Scripts button.

    3. Select a destination folder, scripts to upload, and upload options. For user interface details, see Upload Scripts Dialog Box.

      Once the JMeter script has been uploaded to Performance Center, you can select the script in the test plan tree (identified by the icon) and see script details in the Preview pane.

  3. Configure JMeter runtime settings

    1. After you have uploaded a JMeter script to Performance Center and added it to a test, select the test in the test plan tree and click Edit Test.

    2. In the Groups & Workload view, select a Vuser group and click Edit Runtime Settings . The JMeter Runtime Settings dialog box opens.

    3. Configure the runtime settings:

      UI Elements Description
      JMX Measurements Select to enable JMX measurements during performance test execution.
      JMeter path Enter the path to the JMeter script used in step 1, or leave empty to use the default %JMETER_HOME% environment variable.
      JMeter port

      Select the JMeter port to use:

      • Default. Uses the default port (JMeter starts from port 4000 and uses an alternate port if the default port is being used).

      • Range. Enter a range for the JMeter port, or use the default JMeter range (4445 - 4455).

      Remote testing

      Select this option to run JMeter in server/node mode.

      Running JMeter remotely can replicate a test across many low-end computers and thus simulate a larger load on the server.

      JMeter additional properties file

      Enter the local path for the remote load generator that is used as the JMeter Controller for remote JMeter Nodes.


      • This field is enabled only when the Remote testing option is selected.

      • Make sure the additional properties file actually exists in the local path on the remote load generator that is used as the JMeter Controller for remote JMeter Nodes when the test starts.

Note when running a JMeter script:

  • One Vuser will execute all of the JMeter threads defined for each jmx file.

  • We recommend setting test duration to Run Until Completion.

Back to top

See also: