MQ is the middleware, which takees the files from an upstream system to a downstream system or the downstream system to an upstream system.
IBM MQ and IBM MQ Advanced (software)
IBM SoftwareExternal reviews
190 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Has great system integration features
What is our primary use case?
What is most valuable?
The system integration is good.
What needs improvement?
The pricing needs improvement.
For how long have I used the solution?
I have been using IBM MQ for six years.
What do I think about the scalability of the solution?
The scalability is a nine out of ten.
How was the initial setup?
The initial setup is complex.
What other advice do I have?
Overall, I would rate it an eight out of ten.
Quick notes about IBM MQ
What do you like best about the product?
IBM MQ is a robust and reliable messaging platform that ensures seamless communication between diverse applications and systems. With its high performance, scalability, and security features, IBM MQ simplifies the integration process, facilitating efficient data exchange across various environments. Its intuitive interface and comprehensive management tools make it easy to configure, monitor, and troubleshoot messaging workflows. Whether for large enterprises or small businesses, IBM MQ is a trusted solution for streamlining communication channels and enhancing overall operational efficiency.
What do you dislike about the product?
None, all the features are good enough to work with.
What problems is the product solving and how is that benefiting you?
It helps out clients business to maintain BAU condition.
IBM MQ Review
What do you like best about the product?
Creating messages channel on the go as and when required.
What do you dislike about the product?
Message prioritisation and customer isolation is not achieved in some cases.
What problems is the product solving and how is that benefiting you?
Creating multiple message channels when required.
I have 20+ years experience on z/OS and Unix.
What do you like best about the product?
Store and forward and guarantee delivery. It has been reliable and easy to maintain. Customer Support is superior to most other competing products. IBM offers MQ Client free software for use in business applications.
What do you dislike about the product?
Needs more application coding and tracing options & examples: springboot, python, etc. Need to trace at the API level by MQ object for focused debugging. At the network level, I would like IBM software to incorporate TCP trace route which seems to be one of the most commonly used methods for network debugging.
What problems is the product solving and how is that benefiting you?
IBM MQ is being used as a transport across platforms with a unified API interface by platform.
The backup threshold feature ensures message delivery without loss
What is our primary use case?
During my tenure, there was a transition to using IBM MQ due to its compatibility with IBM mainframe systems, which was beneficial for projects involving message queuing systems, particularly for clients like Volkswagen. I've handled various tasks related to IBM MQ, including testing connections, configuring and installing the system, setting up high availability and disaster recovery solutions, and providing administration support. Additionally, I've conducted training courses on IBM MQ.
What is most valuable?
One of the most crucial aspects for us is ensuring no data loss, and IBM MQ excels in this area, especially in banking environments where reliability is paramount. The feature I find most effective for ensuring message delivery without loss is the backup threshold. This feature allows for automatic retries of transactional messages within a specified threshold. For instance, if the backup threshold is set to five, IBM MQ will automatically retry sending the message up to five times. If unsuccessful, the message is then sent to the backout queue, indicating that it has been attempted multiple times. This flexibility allows us to handle message delivery failures by either discarding, logging, or retrying the message using mediation patterns.
The security features of IBM MQ have met our data protection requirements well. We utilize encryption with SSL keys to ensure data encryption. Additionally, many companies prefer using MQ connections with SSL challenges for added security. The integration with operating systems like Linux and authentication with Active Directory or Open Endpoint of Microsoft has made security configuration straightforward.
What needs improvement?
IBM MQ could streamline its complexity to be more like Kafka without the channel complexities of clusters, making it more straightforward. Migrating to IBM MQ from another messaging solution has not impacted our operational efficiency as we always build our messaging solutions from scratch.
For how long have I used the solution?
I have been using IBM MQ from 17 years.
What do I think about the stability of the solution?
Regarding stability, IBM MQ itself is stable, but issues can arise from the surrounding infrastructure or configurations. Technical support from IBM can be hit or miss, with varying levels of expertise and dedication among support personnel.
What do I think about the scalability of the solution?
In terms of scalability, IBM MQ has supported our growing transaction volumes effectively. We use telemetry and performance tools like Mehdi, Nessus, Zavix, etc., to monitor and manage scalability. While some tools like Cisco AppDynamics offer proprietary solutions, we often create or customize performance monitoring tools within MQ for scalability monitoring.
How was the initial setup?
The initial setup of IBM MQ can be quite complex, often leading to mistakes during configuration. The documentation, while extensive, can be challenging to navigate. The deployment is typically on-premises, and the actual deployment time can vary based on the complexity of the configuration.
What other advice do I have?
I would recommend IBM MQ to others depending on their budget and specific requirements. While it offers robust features, its cost-effectiveness varies based on the client's needs and financial resources. I would rate IBM MQ at 8.5 on a scale of 1 to 10. While it offers robust features and reliability, improvements in documentation, ease of configuration, and support consistency could further enhance its value.
A product that offers good scalability to support business growth
What needs improvement?
The product does not allow users to access data from API or external networks since it can only be used in a closed network, making it an area where improvements are required.
For how long have I used the solution?
I have been using IBM MQ for fourteen years. My company is a customer of the product. I don't remember the version of the solution.
What do I think about the stability of the solution?
Stability-wise, I rate the solution a ten out of ten.
What do I think about the scalability of the solution?
Scalability-wise, I rate the solution a nine out of ten.
Around 15 to 20 people in my company use the solution.
The product is used whenever there is a need to use it in the development phase. Once the tool is deployed on a particular site, we don't need to use the product until and unless any issues or errors are reported.
How are customer service and support?
I rate the technical support a nine out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Before IBM MQ, my company used to use normal point-to-point APIs. My company started to use IBM MQ because we wanted to introduce standardization in our processes.
How was the initial setup?
The solution is deployed on an on-premises model.
What's my experience with pricing, setup cost, and licensing?
I rate the product price a four on a scale of one to ten, where one is low price and ten is high price.
What other advice do I have?
IBM MQ streamlined our company's application-to-application communication since it is a rigid and robust solution that allows you to transfer data from one system to another system using the tool's adapters. In general, the product is very robust.
A scenario where IBM MQ reliability was critical for our company's operations includes an incident involving three to four of our clients who use the product, among which a few are airports situated in regions like Delhi and Bangalore in India. All the big airports use IBM MQ as an integration platform, so it is considered a tier-one application. In the aforementioned areas, there is a need for a tool that offers scalability and robustness.
The feature of IBM MQ, which I found to be most instrumental for our messaging needs, stems from the fact that my company never lost messages when we were using the product. The product has a queue manager, and the message doesn't go anywhere until and unless you read it. The best part of the product is that it ensures that there is no data loss.
IBM MQ's security features have enhanced the data transmission process in our company since it functions in a very secure manner. Nobody can get unauthorized access to the product.
The product offers very good scalability to support business growth.
IBM MQ's integration capabilities with other systems are beneficial since we have developed many interfaces for many airports. Many systems use IBM MQ to send data from one system to another, so it has helped in a great way when it comes to the integration part.
I rate the overall tool an eight to nine out of ten.
MQ Enterprise experience
What do you like best about the product?
Reliable Point to Point connection
Supported Message size is more than sufficient
Monitoring tools
Supported Message size is more than sufficient
Monitoring tools
What do you dislike about the product?
Message Headers could be improved to contain state information
What problems is the product solving and how is that benefiting you?
Connecting to different systems hosted in different underlying architectures
Connection between applications implemented in different programming languages
Connection between applications implemented in different programming languages
IBM helped with some channel wait issues as well as reporting solutions.
What do you like best about the product?
Easy to update/upgrade and maintain and support response.
What do you dislike about the product?
Sometimes it is hard to get someone on the phone just to ask a simple question/answer.
What problems is the product solving and how is that benefiting you?
Buisiness continuity.
IBMMQ - Messaging system
What do you like best about the product?
The options to address some security issues are very useful on some business scenario!
The integration with other IBM tools, on which you can deploy messaging processing components!
The integration with other IBM tools, on which you can deploy messaging processing components!
What do you dislike about the product?
The installation process is no simple, so you need to understand the requirements to achieve the performance and results!
The configuration (interval and number of attempts) of retries, which is useful, on messaging processing errors scenario!
The configuration (interval and number of attempts) of retries, which is useful, on messaging processing errors scenario!
What problems is the product solving and how is that benefiting you?
It worked as decoupling mechanism of processing layers. Possibiliting differents business processing designs to achieve the reliability and the performance required by business
The best middleware in the market
What do you like best about the product?
Easy to use, multiplatform (includes zOS), resilience, security, scalability
What do you dislike about the product?
Some features in MQ for zOS could be implemented in distributed platform (eg. shared queues)
What problems is the product solving and how is that benefiting you?
Integration between plaforms, Scalability, data confidence, security, quick learning for developers.
showing 21 - 30