• Adi Jaradat

Building JMeter Monitor for IBM Maximo Part 1

Updated: Feb 25

  1. Part 1

  2. Part 2

  3. Part 3

  4. Part 4

Combining IBM Maximo and JMeter as a monitor is an interesting idea. JMeter is an open source tool designed to load test and measure the performance of web applications. JMeter is so versatile that it can also be used as a Heartbeat monitor for Maximo or any web application.

In this post I will discuss a simple recipe to configure JMeter to passively monitor Maximo. The use of open source tools doesn’t contradict with using vendor specific tools, in fact, JMeter can complement those tools.

I selected JMeter because it’s open source, easy to use, agile, and can work with any application.

JMeter Monitor for IBM Maximo - JMeter

JMeter Monitor for IBM Maximo – Apache JMeter

This will be a multi-part post and I will cover the following topics:

Part One:

  1. Test Plan

  2. Thread Group

  3. HTTP Request

Part Two:

  1. Constant Timer

  2. Response Assertion

  3. Mailer Visualizer

Part Three:

  1. BeanShell Assertion

  2. View Results Tree

  3. User Defined Variables

  4. Saving JMeter Test Plan

  5. Running Faceless JMeter (No GUI)

  6. Configure JMeter as a Windows Service

Part Four:

  1. What to expect?

  2. What’s Next

JMeter Test Plan

Think of Test Plan as the binder that holds the rest of the components together. With this in mind, Test Plan cannot be complicated! Create a new Test Plan and give it a meaningful name, preferably the application name and the environment, for example:

  1. Maximo Production

  2. Maximo DMZ

  3. Maximo UAT

  4. Maximo Development

Just keep in mind that you may have multiple test plans for multiple environments for Maximo and most probably other applications as well.

JMeter Monitor for IBM Maximo - Test Plan

JMeter Monitor for IBM Maximo – Test Plan

JMeter Thread Group

This is an important component of JMeter because you define a lot of critical information at this stage. The Thread Group gives you control over scheduling Parameters of whatever tasks imbedded within this Group and orchestrate post-sampling actions. In case you want to stress test an instance, this is where you control how to stress out your application and know it down.

Let’s start with a meaningful name for out Thread Group, you can organize the groups the way you want, but you also can dedicate each Thread Group to go after a single instance. Let’s say you have two Maximo servers with two Maximo instances deployed in each server. Then you do have a total of 4 Maximo instances and hence you can create four Thread Groups and name them accordingly. Sample names are:

  1. Maximo Production Server 1 9080

  2. Maximo Production Server 1 9081

  3. Maximo Production Server 2 9080

  4. Maximo Production Server 2 9081

Since we need this Test Plan to behave as a monitor, let’s assign the value of “Continue” in the “Action to be taken after a Sampler error”. This way if JMeter sampler encounters irregular response from a specific Maximo instance (Thread Group), then the Thread Group shall do nothing and just continue monitoring (we will handle this in a few steps down the road).

Now, let’s set “Number of Threads (Users)” to 1 and “Ramp-up Period (In-seconds)” to 1. No need to stress our instance! Select “Forever” in the “Loop Count” option to keep this Thread Group running for … forever. That’s all for Thread Group! Let’s keep in mind that the Thread Group responsibility is to keep on going on and on.

That’s all for Thread Group! Let’s keep in mind that the Thread Group responsibility is to keep on going on and on.

JMeter Monitor for IBM Maximo - Thread Group

JMeter Monitor for IBM Maximo – Thread Group





62 views0 comments

Recent Posts

See All