Adi Jaradat
Building JMeter Monitor for IBM Maximo Part 2
Updated: Feb 25
This is the second part of Building Monitor for IBM Maximo using Apache JMeter.
JMeter Monitor for IBM Maximo – Apache JMeter
HTTP Request
This is the point where we poke Maximo instance to check if it’s responsive. We shall start with a useful name here, let’s keep in mind that the Thread Group name helped us identify the Maximo instance in question.
Now we can take this concept one step further and use the HTTP Request name to reflect the Node name. You can obtain this name by logging into WebSphere and looking for this specific instance under “Application Servers”. This is not a mandatory step, but I found useful especially if you have in mind a more robust automation using BeanShells which I may cover in the future.
Filling up the “Basic” HTTP Request information:
Server Name or IP: the host
Port Number: the port
Timeouts: 20,000 you will need to tweak this number according to your environment
Response: 20,000 you will need to tweak this number according to your environment
HTTP Request Method: GET
Path: The Power of Maximo URL Parameters Builder
The “Path” is very important! You need to make a decision on the best way to poke your instance. Just keep in mind that it should not trigger a heavy operation otherwise you will be loading your instance unnecessarily given the frequency we will set shortly. Also you want to pick an action that will guarantee you a useful result. You need to think of the cases when the instance is all down, also if the application server is running but the database is down. You can attempt to login and this shall load resources from the application server and require database engagement. Of course you can pump this a notch with specific servlet implementation.
JMeter Monitor for IBM Maximo – HTTP Request
Constant Timer
Simple component here, good old fashioned timer, just specify a Thread Delay of 15,000 and tweak it as you go.
JMeter Monitor for Maximo Constant Timer
Mailer Visualizer
We initiated a “HTTP Request” based on a “Constant Timer” then we tested the response using “Response Assertion” and we managed to evaluate which response values are “pass” and “no-pass”. Now we need to take an action if the response yielded “no-pass”.
In this example we will send an email notification indicating that the instance did not respond on time. Additionally, we will also send an email when the instance is up again, so a pair of emails for a specific instance will indicate when the instance stopped responding and when it got back up again. Give the “Mailer” a name and fill the following fields:
From: from email address
Addresses: Recipients separated by a comma
Success Subject: I suggest using the instance direct link, for example: http://mymaximo:9080/maximo this will make it easier to link right into that specific instance for testing.
Success Limits: use 2, so if the instance started responding, wait for two trials before sending the email
Failure Subject: The same as Success Subject
Failure Limits: use 2
SMTP Server Host: You probably know it
Login and Password: you probably won’t need it if you placed JMeter on a server that it configured for SMPT relay
Now our “Mailer” will send us in email in the following cases:
Instance did not respond on time for two consecutive trials
Instance started to respond after failure for two consecutive trials
JMeter Monitor for Maximo Mailer Visualizer