I have developed MQExerciser over the past five years to make my life easier while testing MQSeries and MQSeries Integrator applications. I started out looking for a simple way to get, put, and browse messages and quite frankly, the existing tools required too many 'clicks' and took too much time. To make matters worse, all my applications used more than one queue at the same time - GET from one queue, PUT to several others. I hated opening and closing the queues I needed to work with. I hated hitting the Refresh button over and over again just to see if there were any results. I wanted to open all the queues at the same time regardless of what queue manager they were on. So, I built MQExerciser.
As time went on, I added more functionality to simplify many of the repetitive tasks needed to test my applications. Capturing messages to file and later retrieving them from the file, moving messages between queues, and putting a message onto a queue repeatedly under timer control are just a few examples. As you may have guessed by now, I am basically lazy. I got tired of manually refreshing views to see new queue depths so I automated that with Dynamic Refresh. I got tired of reentering settings from session to session, so I built in Sticky Settings to save over 130 variables, settings, and options between sessions.
I've also streamlined functionality when working with WebSphere MQ Integrator. I have added capabilities to stop/start broker trace and display data with a command button. I can examine input data in a variety of ways, and there is a command assistant to import and export message sets.
MQExerciser makes the routine and repetative tasks for message management, manipulation, and testing almost painless. This leaves more time to focus on providing the best response to business requirements.
Built by Developers - for Developers