How has it helped my organization?
The product encourages the idea of asynchronous processing, which means that the sender and receiver are not required to be active and running at the same time. The message will be saved to the receiver queue until the system starts successfully and pulls it for processing. This is typically used in all internet banking functions that receive their data from different bank systems.
What is most valuable?
- Support for JMS 2.0, because we develop solutions compatible with Java EE7.
- Seamless integration with IBM WebSphere Application Server, which is the most stable application server I ever worked with.
- Installed and configured at Windows, AIX and IBM i mostly the same way and set of commands.
What needs improvement?
They need to add the ability to send full messages (header + payload) from the MQ Explorer program, not just the payload.
What do I think about the stability of the solution?
We have not encountered any stability issues.
What do I think about the scalability of the solution?
We have not encountered any scalability issues.
How are customer service and technical support?
I would rate the technical support as good, 8/10.
Which solution did I use previously and why did I switch?
I previously used ActiveMQ, but I switched to IBM MQ due to the robustness of the solution.
How was the initial setup?
If you are familiar with IBM products, you will find initial setup straightforward.
What's my experience with pricing, setup cost, and licensing?
IBM MQ has a flexible license model based on the Processor Value Unit (PVU) and I recommend it.
Which other solutions did I evaluate?
We evaluated Active MQ also.
What other advice do I have?
I would advise the potential user to read about security considerations and compliance with security standards.
Which version of this solution are you currently using?