JMeter Installation

Pre-Requisite

Apache JMeter (Requires Java 8+)

Download JMeter: Visit the Apache JMeter website (https://jmeter.apache.org/) and navigate to
the download section.

Choose the Binary Package: Select the binary package for download. Usually, it's a .zip or .tgz
file.

Download the Zip File: Click on the download link for the ZIP file corresponding to the latest
version of JMeter.

Extract the Zip File: Once the download is complete, extract the contents of the ZIP file to a
directory on your Windows machine.

Run JMeter: Navigate to the directory where you extracted the contents of the ZIP file and
locate the bin folder. Inside this folder, you'll find the jmeter.bat file.
Execute jmeter.bat: Double-click on jmeter.bat to start JMeter. Alternatively, you can open a
command prompt, navigate to the bin directory, and execute jmeter.bat from there.

JMeter GUI: Once JMeter starts up, you'll see the JMeter GUI, where you can create and execute
performance tests.

That's it! You've successfully installed JMeter on your Windows machine. You can now start
creating and running performance tests to analyze the performance of your applications.
To install the BlazeMeter plugin for JMeter recording, follow these steps:

Download BlazeMeter Plugin:

 Visit the BlazeMeter website (https://www.blazemeter.com/) and navigate to the

"BlazeMeter | Continuous Testing Platform" section.
 Sign up for a BlazeMeter account if you don't have one already.
 After logging in, navigate to the "BlazeMeter | Continuous Testing Platform" section
again and find the "Get Started for Free" button. Click on it.
 Follow the prompts to access the BlazeMeter plugin for JMeter. You may need to provide
some basic information.

Install BlazeMeter Plugin:

 Once you have access to the BlazeMeter plugin, download the plugin file (usually a JAR
file).
 Copy Plugin to JMeter's lib/ext directory:
 Locate the directory where you installed JMeter.
 Inside the JMeter directory, find the lib/ext folder.
 Copy the BlazeMeter plugin JAR file into the lib/ext folder.

Restart JMeter:

 If JMeter is running, close it.

 After copying the plugin JAR file, restart JMeter to ensure that the plugin is loaded.
Verify Installation:

 Once JMeter restarts, you can verify that the BlazeMeter plugin is installed by opening
JMeter.
 In JMeter, navigate to the "Options" menu and select "Plugins Manager."
 The BlazeMeter plugin should appear in the list of installed plugins.

Configure BlazeMeter Recorder:

 In JMeter, navigate to the "Options" menu and select "BlazeMeter Recorder."

 Follow the prompts to configure the BlazeMeter Recorder settings, such as specifying the
port for recording and configuring any proxy settings if necessary.

Start Recording:

 Once configured, start the BlazeMeter Recorder within JMeter.

 Start recording your interactions with mainframes by adding Non-Test Eement -> bzm-
RTE Recorder in the Test Plan.
And after adding bzm-RTE Recorder and it looks as like below

You can provide any Name and comments what ever you want o leave it as it is.
Provide mainframes server ,port ,Protocol and terminal type as per your requirement to connect
your mainframes and record your actions.

Before you start the recording add a thread group to Test Plan
After adding Thread Group and the server name other details just click to start recording

Once you start and we can see a window will popup with the mainframes screen the server
which you want to connect and from there the keyboard actions will be recorded.

Each action recorded as a sampler for user identification you can change each sampler name as
you wish (Ex: The first sampler name it shows as per system bzm-RTE-SEND_INPU-1 and I
changed it to Logon Credentials)
Stop Recording:

 After recording the necessary interactions, stop the BlazeMeter Recorder within JMeter.
  That's it! You've successfully installed and configured the BlazeMeter plugin for recording
in JMeter. You can now use the recorded interactions to create performance tests in
JMeter. All your activities saved in Thread group this can be saved as a test plan and run
number of times.

Pro/JCL started task performance Testing:

I have created a Test Plan which is having Seven thread groups to perform multiple actions on
the DSSISCT7 started task on RSB3

Prerequisite to execute below test plan would be.

Ensure no other users working or using the DSSISTC7 while performing the test.

Ensure DSSISTC7 up and running.

Ensure Pro/JCL product running without any issues.

Ensure already allocate necessary datasets SPJMLOAD and SPJMEXEC, if those are not allocating
through your login proc.

Ensure necessary remote machines defined.

Note: Since Remote Machines definitions we are not automated you have to manually create
below machines on Mainframes before start of the testing

Ensure Correct paths and ports for API testing updated in the API test thread group.

Ensure Updated the correct User Name and Passwords in the CSV spreadsheet or User
Parameters(In all thread groups), which one you prefer it’s your choice.
Load Testing :

Open Jmeter

Click on File -> Open -> Test scrip (PRO_JCL_Load_Testing_Perfect-Demo.jmx)

Once we open the script the Test plan ready to run.

Check your User IDs and Passwords edited correctly

Note : Refer Prerequisite before start of the testing.

Once all verifications done then it is ready to go and start the testing.

Some important Information to Lear and understand to run the test scripts:

There two options we can pass the user IDs & password

1. User Paremeter
2. CSV Data Set Config
In JMeter, the User Parameters Pre-Processor is used to define user-specific parameters
that can be referenced throughout the test plan. This component allows you to
dynamically change the values of variables based on user input or external data sources.
Here's how it works:

1. Adding User Parameters: You can add the User Parameters Pre-Processor by
right-clicking on a Thread Group or any other element in the test plan, selecting
"Add" > "Config Element" > "User Parameters". Once added, you can define the
parameters within this element.
 2. Defining Parameters: Within the User Parameters Pre-Processor, you can define
key-value pairs representing the parameters you want to use. These parameters
can have static values, or you can use JMeter functions or variables to make them
dynamic.
3. Referencing Parameters: After defining the parameters, you can reference them
throughout your test plan using the ${} syntax. For example, if you define a
parameter called username, you can reference it as ${username} in HTTP requests,
JDBC requests, or any other elements where you need to use it.
4. Dynamic Parameterization: The User Parameters Pre-Processor is particularly
useful when you want to simulate multiple users with different credentials, input
data, or configurations. By defining parameters at the user level, you can easily
parameterize your test plan and simulate various user scenarios.
5. CSV Data Set Config: In cases where you need to use a large set of dynamic data
(e.g., usernames, passwords, input data), you can combine the User Parameters
Pre-Processor with the CSV Data Set Config element. The CSV Data Set Config
allows you to read data from external CSV files and feed it into the User
Parameters, enabling dynamic parameterization based on external data sources.

Overall, the User Parameters Pre-Processor provides flexibility and reusability in JMeter
test plans by allowing you to define and use user-specific parameters dynamically. It's
particularly handy for scenarios where you need to simulate diverse user behaviors or
configurations.

Adding a CSV Data Set Config in JMeter is a straightforward process. The CSV Data Set
Config element allows you to read data from external CSV files and use it in your test
plan. Here's how you can add it:

1. Open JMeter: Start JMeter and open the test plan where you want to add the
CSV Data Set Config.
2. Add CSV Data Set Config:
 Right-click on the Thread Group or any other element where you want to
add the CSV Data Set Config.
 Go to "Add" > "Config Element" > "CSV Data Set Config".
3. Configure CSV Data Set Config:
 Once added, you'll see the CSV Data Set Config element added under the
selected element in the tree view.
 In the CSV Data Set Config element, you'll find various fields to configure:
 Filename: Specify the path to the CSV file containing your data.
You can use a relative or absolute path.
 File encoding (optional): Specify the encoding of your CSV file if
it's not in the default encoding.
 Variable Names: Provide a list of variable names separated by
commas. These names will be used to refer to the corresponding
columns in the CSV file.
 Delimiter (optional): If your CSV file uses a delimiter other than a
comma (,), you can specify it here.
 Other options: There are additional options such as whether to
stop the thread when the end of the file is reached or to recycle
through the file.
4. Use Variables in Test Elements:
 Once you've configured the CSV Data Set Config, you can use the
variables defined in the "Variable Names" field in other test elements such
as HTTP requests, JDBC requests, etc.
 Use the variables by enclosing them in ${} notation. For example, if you
have a variable named username, you can refer to it as ${username} in your
test elements.
5. Prepare CSV File:
 Make sure your CSV file is properly formatted with the required data.
 Each row in the CSV file represents a set of values that will be assigned to
the variables defined in the CSV Data Set Config.
6. Run Your Test:
 After configuring the CSV Data Set Config and using the variables in your
test elements, run your test plan to see how JMeter iterates through the
CSV file and uses the data.

By following these steps, you can easily add and configure a CSV Data Set Config in
JMeter to use external data in your performance tests.

In JMeter, the Loop Controller is a logic controller that allows you to repeatedly execute its child
elements a specified number of times or indefinitely. It's commonly used to create loops within your
test plan to simulate scenarios where you want certain operations to be repeated.

Here's how you can use the Loop Controller in JMeter:

1. Adding a Loop Controller:

 Right-click on the Thread Group or any other element where you want to add the
Loop Controller.
  Go to "Add" > "Logic Controller" > "Loop Controller".
2. Configuring the Loop Controller:
 Once added, you'll see the Loop Controller added under the selected element in the
tree view.
 In the Loop Controller, you can specify the number of times you want its child
elements to be executed. If you want the loop to run indefinitely, you can leave this
field blank or set it to -1.
3. Adding Elements to the Loop Controller:
 You can add any test elements (samplers, controllers, etc.) as children of the Loop
Controller. These elements will be executed repeatedly according to the loop
configuration.
4. Using Variables and Functions:
 You can use variables and functions within the Loop Controller to create dynamic
behavior. For example, you can use counter variables to track the iteration number
within the loop.
5. Combining with Other Controllers:
 The Loop Controller can be combined with other controllers such as If Controller,
While Controller, or Transaction Controller to create more complex test scenarios.
6. Executing the Test:
 After configuring the Loop Controller and adding child elements, you can run your
test plan to see how JMeter executes the loop according to the specified
configuration.
7. Analyzing Results:
 Once the test is executed, you can analyze the results to see how the loop behavior
affects the performance of your application.

Overall, the Loop Controller is a powerful tool in JMeter for creating repetitive test scenarios. It
allows you to simulate realistic user behavior by executing certain operations multiple times within
your test plan.

Why we use View Results Tree:

The "View Results Tree" listener in JMeter is a tool that provides a visual representation of the
execution results of the test plan.When you run your test plan, the View Results Tree listener
displays the details of each request and response, allowing you to inspect the data sent and
received during the test.

It's important to note that while the View Results Tree listener is a powerful debugging tool, it
can consume a lot of memory when used in large-scale tests because it stores all request and
response data. Therefore, it is recommended to disable or remove this listener during actual
load testing to conserve resources and get more accurate performance metrics.
Why we use Aggregate Graph:

The "Aggregate Graph" listener in JMeter is a tool that provides a graphical representation of the
aggregate performance metrics of the requests made during a test. It is used to analyze the
overall performance of the application under test by summarizing the results into a bar graph,
which makes it easier to visualize and interpret the data.
Key features of the Aggregate Graph listener include:
1. Graphical Representation: It displays a bar graph where each bar represents a sample
(usually an HTTP request), and the height of the bar indicates a particular metric,
such as average response time.
2. Performance Metrics: The Aggregate Graph shows various performance metrics,
including:

o Average: The average response time of all samples.

o Median: The middle response time (50th percentile).

o 90% Line: The response time below which 90% of the samples fall.

o Min: The minimum response time recorded.

o Max: The maximum response time recorded.

o Error %: The percentage of requests that resulted in errors.

o Throughput: The number of requests per second the server handled.

o Standard Deviation: A measure of the variability of the response times.

3. Customization: You can customize the graph by selecting which metrics to display,
changing the colors of the bars, and adjusting other visual settings.
4. Data Export: The listener allows you to save the graph data to a file or export the
graph as an image for reporting or further analysis.
5. Data Table: Below the graph, there is a table that lists the same metrics for each
sample in a numerical format, providing a detailed view of the performance data.
6. Filtering: You can filter which samples to display in the graph based on their names,
which is useful when you want to focus on specific transactions or requests.
The Aggregate Graph listener is valuable for performance testing because it aggregates data
from all threads (users) over the entire run of the test, giving you a high-level overview of the
application's performance. It helps in identifying trends, such as increased response times under
higher loads, which might not be apparent from individual sample results.

However, like the View Results Tree listener, the Aggregate Graph listener can consume
significant resources when processing large amounts of data. Therefore, it's recommended to
use it judiciously during load testing, especially when running tests with a high number of users
or requests.

In JMeter, the Summary Report Listener is a component used for analyzing and aggregating
results from load tests. It provides a concise overview of key performance metrics gathered
during test execution. Here's how it's typically used:
Performance Metrics: The Summary Report Listener displays essential performance metrics
such as average response time, median response time, minimum and maximum response times,
throughput (requests per second), error rate, and the number of samples processed.
Aggregated Data: It aggregates data across all threads (virtual users) and provides statistical
summaries, giving testers a quick understanding of how the application is performing under the
given load.
Real-Time Monitoring: During test execution, the Summary Report Listener updates in real-
time, allowing testers to monitor the performance of the system as the load test progresses. This
helps in identifying any immediate performance issues or anomalies.
Data Export: Test results from the Summary Report Listener can be exported in various formats
such as CSV, XML, or text for further analysis or reporting purposes.
Trend Analysis: By comparing results from different test runs or iterations, testers can perform
trend analysis to track the performance of the application over time and identify any
performance improvements or degradation.
Overall, the Summary Report Listener serves as a vital tool for load testing and performance
analysis in JMeter, providing actionable insights into the performance of web applications, APIs,
or other services under different load conditions.
Top of Form