With IBM MQ, the main use case is for applications in online banking. We use it within the banking industry. IBM MQ is a choice to create a relation between the Mainframe and distributed servers, allowing applications running on Linux or Windows to interface with Mainframe applications and enable more development of easier and open applications in a distributed environment. This means we can develop more applications that are easier to use.
Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
185 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Solution de messagerie forte
Qu'aimez-vous le plus à propos de the product?
Garantit la livraison des messages une seule fois
Gère un trafic intense avec un délai minimal
Prend en charge l'authentification des canaux avec ssl/tls, la messagerie sécurisée est prise en charge
Facile à créer et à maintenir l'environnement
Cloud Native HA est une très bonne solution !
Gère un trafic intense avec un délai minimal
Prend en charge l'authentification des canaux avec ssl/tls, la messagerie sécurisée est prise en charge
Facile à créer et à maintenir l'environnement
Cloud Native HA est une très bonne solution !
Que n’aimez-vous pas à propos de the product?
L'interface utilisateur semble un peu dépassée, elle pourrait bénéficier d'une mise à jour.
La configuration TLS du canal n'est pas toujours facile, d'autres clients ont souvent des difficultés à la mettre en place.
La sécurité de la file d'attente MQ ne semble pas intuitive au début, cela pourrait être plus facile à démarrer.
La configuration TLS du canal n'est pas toujours facile, d'autres clients ont souvent des difficultés à la mettre en place.
La sécurité de la file d'attente MQ ne semble pas intuitive au début, cela pourrait être plus facile à démarrer.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
Coordinateur de transactions pour les intégrations middleware
Plateforme de messagerie
Stockage persistant des messages
Plateforme de messagerie
Stockage persistant des messages
Super produit
Qu'aimez-vous le plus à propos de the product?
Configuration facile. Fiabilité, robustesse. Facile à gérer.
Que n’aimez-vous pas à propos de the product?
Rien.
Aucun.
Je n'ai trouvé aucun inconvénient jusqu'à présent dans les utilisations que nous avons d'IBM MQ.
Aucun.
Je n'ai trouvé aucun inconvénient jusqu'à présent dans les utilisations que nous avons d'IBM MQ.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
Nous utilisons IBM MQ pour communiquer avec d'autres institutions à SPB. Nous utilisons le MQ pour échanger des messages entre le système hérité (mainframe) et la plateforme basse.
Experience with reliability and resilience while knowledge accessibility needs improvement
What is our primary use case?
What is most valuable?
I work with CICs, Workload Manager, and DB2 mainly. I have experience with IBM MQ. We mainly use clusters at the Windows level or Linux level, and in the Mainframe, we have multiple paths and different lines of connectivity transmission to assess the impact of IBM MQ's high-availability configurations on our system's resilience.
We use advanced security features such as SSH for encryption and authentication mechanisms. The security features help protect our messaging data by encrypting the transmission and ensuring authentication for connection.
What needs improvement?
The customer service or technical support from IBM is not as good as we expected; it could be better. They don't meet our standards due to the timing to get a person with knowledge.
For how long have I used the solution?
We use some IBM solutions hosted on AWS as a cloud provider.
What was my experience with deployment of the solution?
The initial setup of IBM MQ is reasonable, just as we were expecting, and we were on time for that project.
What do I think about the stability of the solution?
The maintenance for IBM MQ is good to be once a year; that's the best.
What do I think about the scalability of the solution?
We mainly use clusters at the Windows level or Linux level, and in the Mainframe, we have multiple paths and different lines of connectivity transmission to assess the impact of IBM MQ's high-availability configurations on our system's resilience.
How are customer service and support?
The customer service or technical support from IBM is not as good as we expected; it could be better. I rate them a 7 on a scale of 1 to 10. They don't meet our standards due to the timing to get a person with knowledge.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I don't really know the main differences between IBM MQ and other messaging queue solutions because it has been my natural choice, coming from Mainframe z/OS.
How was the initial setup?
The initial setup of IBM MQ is reasonable, just as we were expecting, and we were on time for that project.
What about the implementation team?
In the setup, there are mainly two persons involved, but others from different areas are also involved, making it more than just those two.
Which other solutions did I evaluate?
I currently work with IBM, but we are also using other vendors such as BMC and Logon for specific backup solutions from Mainframe.
What other advice do I have?
My main experience is with IBM Mainframe. I do not have experience with their IBM QRadar. AWS is not our main cloud provider for IBM solutions. I am not very experienced with cloud, but we do use object storage, which is cloud or on-prem for example.
I don't remember specific examples at this moment, but if you contact me in two days, I will probably be able to refresh my memory as I'm currently focused on the capacity and performance issues of the system. I don't have thoughts on IBM MQ's pricing since I work in the support area and I'm not related to the purchasing process.
My company mainly provides services to the banking area but also sells many products, including IBM and open system solutions, such as storage. My company's name is Telcos, spelled T-A-L-C-O-S.
I am very interested in providing a review for the IBM Workload Automation based on my recent experience with it. I am still working with Workload Automation and probably have a project related to this support, but I have switched to focusing more on performance issues at the moment. I used to be more focused on Workload Automation, but now I have shifted my project to banking application performance and capacity.
I still work with IBM solutions in the other area, maintaining contact with AWS that relates to Workload Automation. I deal with banking services in general performance, mainly related to recovery, backup solutions, and CPU utilization. I have experience with IBM ProtecTIER, specifically the ProtecTIER, and not Tivoli. I do not remember experiencing Spectrum. I do not have experience with Spectrum Protect.
I have experience with backup and recovery, particularly on the Mainframe side, but not with HSM. HSM is more related to the Mainframe, and while I don't have recent experience, my focus has shifted to performance areas in z/OS, especially solutions relating to backups and disaster recovery.
We move data from Mainframe to the cloud. BMC is one of the companies I refer to, along with Logon. Logon is spelled L-O-G-O-N. Logon is based in Israel.
Overall, I would rate IBM MQ an 8 out of 10.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Provides reliable middleware support with room for cloud compatibility improvements
What is our primary use case?
My use case for IBM MQ is that it's a middleware solution for our enterprise.
What is most valuable?
The features of IBM MQ that have proven most effective for ensuring message delivery reliability are the stability of the system, the resilience and the product, which is definitely of top quality in this segment. This is a product which is very common, and many competent products are there, but it's time-tested, very stable, highly resilient, and has all the features to troubleshoot even if something goes wrong. It's the best from all perspectives.
What needs improvement?
The areas of IBM MQ that have room for improvement are its compatibility with the public clouds, specifically its compatibility with Azure or AWS, as there is definitely a lot of scope for improvement there.
For how long have I used the solution?
In our organization, we have been using IBM MQ for around 10 years, but we moved it to cloud two and a half years ago. The product has been in use for the last 10 years on-premises, and recently, for two and a half years, we have been using it on cloud.
What was my experience with deployment of the solution?
We used a direct service from IBM for the deployment of IBM MQ in our environment. It is not a third party, but it is a service taken from IBM itself. There is an IBM subsidiary IT team in the Middle East who has helped us.
How are customer service and support?
I would rate the technical support from IBM as seven out of 10.
The reason for this rating is due to the turnaround time, which is an important factor. IBM follows a practice of raising a ticket and has specified turnaround times to get back to us. Though usually, if it is high priority or top priority, they turn around faster, even for medium or low priority issues, their turnaround time is not as good to complete our project. We cannot hold on to the project for a long time just to wait for IBM to fix the issues. Our project will have its own timelines, so we expect turnaround times for medium and low priority incidents or tickets to be better than what IBM is currently offering.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
I did not use a different solution before IBM MQ. For the last 10 years, we have been using this solution, so I don't remember what was there 10 years back.
How was the initial setup?
The initial setup of IBM MQ was complex on cloud. If it had been on-premises, it would have been very simple. On cloud, it is complex, and we had to take help from IBM itself for that.
What about the implementation team?
We used a direct service from IBM for the deployment of IBM MQ in our environment. It is not a third party, but it is a service taken from IBM itself. There is an IBM subsidiary IT team in the Middle East who has helped us.
What was our ROI?
I have seen an ROI from IBM MQ in terms of its role as a tool for integration platforms; however, it does not directly relate to any cost or revenue. It does not have functional features, as it's a product which integrates the external systems with internal systems or among the systems themselves, making it an essential technology component required to integrate multiple systems.
What's my experience with pricing, setup cost, and licensing?
The price of IBM MQ is definitely on the higher side. There are many market-competitive products, but this is a top product in the market and messaging middleware software, so the cost is high.
What other advice do I have?
The approximate number of end users in our organization using IBM MQ is roughly 30.
I would recommend IBM MQ to other people.
I do not wish to disclose my organization's name or email because this does not represent the organization's viewpoint officially.
I rate IBM MQ overall as a seven on a scale from 1 to 10, when 1 is the worst solution, and 10 is the best solution.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Reliable payment processing is achieved with minimal disruption
What is our primary use case?
We use it for payment processing and to send these payments abroad in another country.
We use it for the production environment, and we consider it stable enough, which is why we continue to use this product.
What is most valuable?
The biggest advantage is that it's a reliable enough product which we use, and it's a highly documented product. We can learn it slowly, so we have experienced users and experienced staff to use this product.
We suppose it's secure because we use secure tools within the frame of this product, such as TLS 1.3 and so on. Its scalability is enough for our purposes, and that's all we can say about it.
What needs improvement?
Currently, we have some disadvantages; it's a bit difficult to use IBM ID to access support from the IBM site. To get nice support from IBM, we need to use IBM ID, and it's a bit complicated to integrate it with IBM support.
Support can be better because sometimes we need explanations for some behaviors of the product, and it's not easy to reach the proper person in IBM support.
They could add some new features into IBM MQ to make it better. A graphical user interface in addition to MQ Explorer could be useful, but we are satisfied with MQ Explorer as well.
For how long have I used the solution?
We have been using it in general for about 10 years.
What was my experience with deployment of the solution?
We have some experience with installations, and it's difficult. We need to state that it requires some experience and knowledge. We have required experience, having used this product about 10 years.
What do I think about the scalability of the solution?
Its scalability is enough for our purposes, and that's all we can say about it.
How are customer service and support?
Support can be better because sometimes we need explanations for some behaviors of the product, and it's not easy to reach the proper person in IBM support.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I cannot compare with other products, and I cannot give exact answers regarding whether it's expensive or cheap, as I don't know the costs of other products in this group. For us, we pay for it, and we rely on this product, and it's okay.
How was the initial setup?
It's possible to get some training, but the cost of this learning is expensive. It costs some money, but we have required experience and knowledge because we have been using it for about 10 years.
What's my experience with pricing, setup cost, and licensing?
It's possible to get some training, but the cost of this learning is expensive. It costs some money, but we have required experience and knowledge because we have been using it for about 10 years.
Which other solutions did I evaluate?
I cannot compare with other products, and I cannot give exact answers regarding whether it's expensive or cheap, as I don't know the costs of other products in this group. For us, we pay for it, and we rely on this product, and it's okay.
What other advice do I have?
I'm just a user, representing Raiffeisen Bank, and it's clear.
We use WebSphere MQ, which includes some tools such as ActiveMQ, IBM MQ, and VMware.
Today, we don't use AI for our purposes, but if we find any useful AI features for this product, we might use them later because we can't evaluate their reliability for our needs right now.
On a scale of 1-10, I rate IBM MQ a nine.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
IBM
Reliable data transfers have been made easier with enhanced security
What is our primary use case?
Primarily used for IBM MQ data transfers.
As a user of IBM MQ, I use it for data transfers, configuring the queues and similar tasks. I do not work with it beyond those functions.
It is primarily used for data transfers within the applications. That encompasses the most critical features and functionality for me.
What is most valuable?
The biggest advantage of IBM MQ is its reliability.
IBM MQ is reliable and includes important security aspects.
What needs improvement?
IBM MQ is still in a premature state. It is in a research phase, so it is very early to make specific suggestions about improvements.
What do I think about the stability of the solution?
The stability of IBM MQ rates at eight or nine out of ten.
What do I think about the scalability of the solution?
The scalability of IBM MQ rates at eight out of ten.
Scalability and sustainability could be examples for IBM MQ.
Any product of this nature should be scalable and sustainable. It depends on how the product evolves, how it has been implemented in the organization, and how we manage it.
What other advice do I have?
I found the information about IBM MQ on the website to be good.
I am just a user of IBM MQ conducting research and reviewing it.
Being a user of IBM MQ, I do not have detailed knowledge about the specifics. The support team handles those aspects.
We are informed about issues with IBM MQ periodically. However, we do not necessarily receive complete information about why certain things were not working, as it is outside of my purview.
From a sustainability perspective, there might be room for consideration regarding IBM MQ. Otherwise, it performs well.
My final rating for IBM MQ is nine out of ten points, where ten is the best.
Reliable and secure performance consistently enhances message transfer
What is our primary use case?
The use case for IBM MQ is for message transfer between banks and SWIFT, and message transfers within applications in banks. These are the most used cases.
What is most valuable?
IBM MQ is more reliable and secure than other software. There is a saying that for the last 30 years IBM MQ has never been hacked. It is more secure and reliable. Whenever the configuration is done, I do not have to touch it again. It works fine, it is stable, and its communication is to the point and accurate. All performance-related aspects are better.
Performance-wise, it is scalable, and other features such as DR, DC, replication, and active passive mode are complex to configure, but it remains scalable.
The pricing model for IBM MQ could be more flexible for clients.
What needs improvement?
Regarding improvements in IBM MQ, I cannot specify any issues because whatever requirements exist, I find them available since it is a very old product with all necessary features. I am not encountering any missing features in IBM MQ.
Feature-wise, everything required is available in IBM MQ. The pricing is consistently high, which is known in the market. In that scenario, pricing could be more competitive compared to other vendors.
The pricing model for IBM MQ could be more flexible for clients.
For how long have I used the solution?
I have been working with IBM MQ for 3 years.
What do I think about the stability of the solution?
I would rate the stability for IBM MQ as nine out of ten.
What do I think about the scalability of the solution?
While not easy, IBM MQ is scalable. Performance-wise, it is scalable, and other features such as DR, DC, replication, and active passive mode are complex to configure, but it remains scalable.
How are customer service and support?
I would give technical support from IBM an eight out of ten.
The response time for IBM MQ support could be better because when we are using IBM MQ and something goes wrong, support is required as the resource availability of the IBM product is very limited.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Some of my customers are now using IBM MQ. Previously they were using Kafka, but after using IBM MQ, they decided to move to IBM MQ and remove Kafka because IBM MQ is more reliable and more performance friendly than Kafka.
How was the initial setup?
The initial setup for IBM MQ is very simple.
Which other solutions did I evaluate?
For security, scalability, and performance, I suggest IBM MQ. However, customers have budget constraints and other considerations including application portfolio and requirements. There are alternatives such as Apache MQ and RabbitMQ. The choice depends on the budget, requirements, and priorities regarding security, performance, or budget. We can suggest the best solution, but if the customer cannot afford it, they might opt for the free option, RabbitMQ, or Apache MQ. It ultimately depends on the price and application needs.
What other advice do I have?
It depends on the application regarding what company size can use IBM MQ. If a small or medium company uses a complex application where security is measured, with multiple applications, they can use it. For enterprise level, it is mandatory if they require it because IBM MQ is a requirement product, not a day-to-day product. If you want the best solution then choose IBM MQ. I cannot suggest that small companies need it and enterprise companies do not need it. I rate this solution nine out of ten.
Which deployment model are you using for this solution?
On-premises
Ensured transaction security and reliability over fifteen years
What is our primary use case?
We deal with financial and non-financial transactions, and most of the financial transactions that interact with backend vendor systems are done via IBM MQ. It is manager-to-manager communication, and the transaction load is huge. That is one aspect where we need IBM MQ to communicate with backends.
What is most valuable?
With the setup that we have, financial transaction messages are not lost. We are primarily looking for a 100% quality of service in terms of non-repeating the message and message delivery. These are financial transactions, so we do not want to lose the message at any cost. That was the main reason why we have IBM MQ. Additionally, when dealing with posting financial messages to backend vendor systems, most of the revenue gets generated.
What needs improvement?
I extensively worked on IBM MQ some time back, but not at this point in time. We are dealing with IBM MQ client applications mostly, so I don't see any enhancements needed for the IBM MQ layer.
For how long have I used the solution?
I never used ActiveMQ or Amazon MQ. I have been using IBM MQ for the past fifteen years. It was my first message-oriented middleware, and I have been using the same middleware. I did not get an opportunity to explore other message-oriented middleware available in the market.
What was my experience with deployment of the solution?
No mentions of deployment issues in the transcript.
What do I think about the stability of the solution?
MQ is just a message staging engine and not a processing engine. Usually, processing engines would be either DataPower, API Gateway, API Connect, or ESB. The transaction is always guaranteed with IBM MQ, which is the main reason I have been working with it for fifteen years while dealing with financial transactions or messages. The message availability is always guaranteed.
What do I think about the scalability of the solution?
The implementation utilizes multi-instance managers. As it is a container version, we can vertically scale it. In our environment, we do not have horizontal scaling for IBM MQ, but as demand increases, we would just vertically scale it.
How are customer service and support?
Right now, I am not working on IBM MQ extensively, and we do not delve into any of its PMRs, so the support should be good. With containerized flavors of these products, we are having a tough time dealing with PMRs because the versions are new to IBM. However, for non-containerized flavors running on blade, VMware, or appliances, they are pretty good. I would give them a rating of eight for their overall service.
How would you rate customer service and support?
Positive
How was the initial setup?
The setup is very straightforward, and it's not complex, even with container flavors. It's very easy with the advent of OCP operators shipped with CP4I. You can create a manager in less than a minute's time. It's not challenging at all.
What about the implementation team?
We have a huge team that maintains the infrastructure of the entire stack and manages applications deployed on top of IBM MQ and other solutions. But just for infrastructure, even for a production-ready data center, it shouldn't require more than a couple of resources.
What was our ROI?
The kind of workload we have deals with posting financial messages to backend vendor systems, and most of the revenue gets generated. There are definite cost savings and return on investment.
What's my experience with pricing, setup cost, and licensing?
IBM MQ is pretty reasonable when compared to IBM ESB. We do not take advanced security licensing for our transactions.
What other advice do I have?
I would rate the solution ten out of ten because I have been working on it for the past fifteen years. The message availability and transaction guarantee with IBM MQ is the main reason. I would rate it a ten overall.
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Solution d'intégration haute performance
Qu'aimez-vous le plus à propos de the product?
C'est une solution d'intégration haute performance avec plusieurs outils qui renforcent encore plus la gestion et la capacité de traitement des messages et l'évolutivité.
Que n’aimez-vous pas à propos de the product?
Je crois que de nombreuses commandes et outils disponibles dans le CLI pourraient être disponibles via l'outil MQ Explore, permettant une plus grande facilité de gestion, compte tenu de l'évolution des solutions SI qui limitent l'accès direct aux serveurs.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
Le MQ nous aide dans le traitement de plusieurs messages et intégrations de solution de bus à travers l'utilisation de canaux et de files d'attente de transmission à distance sans la nécessité d'une architecture intermédiaire.
Improved message transport process supports thousands of high-volume transactions efficiently
What is our primary use case?
We use IBM MQ with a TELEX module for the airline industry as a transport layer. We compose messages specific to the airline industry and use IBM MQ for the actual message transport. We also use it for message transport related to scheduling flights, changing flight details, and capturing flight data like takeoff, airborne, landed, and on blocks.
What is most valuable?
IBM MQ processes many thousands of messages in a second, which is efficient for handling high transaction volumes. It is simple to use once you learn it, and the knowledge stays with you. It has contributed to better message transport compared to the Oracle-based solution we used before, which was slower. We have not experienced any downtime or crashes with IBM MQ.
What needs improvement?
It would be nice to have AI features and an updated graphical user interface. Currently, I am using it on Red Hat seven with a command line interface. Having a graphical user interface would improve usability.
For how long have I used the solution?
I have been working with IBM MQ for about ten years or more.
What was my experience with deployment of the solution?
I did not take part in the deployment process. It was handled by another party and involved two engineers.
What do I think about the stability of the solution?
IBM MQ is really stable. We have never had any downtime or crashes since it's been running.
What do I think about the scalability of the solution?
IBM MQ handles many thousands of messages in a second, indicating good scalability. It was more efficient compared to our previous Oracle-based solution, which was slower.
How are customer service and support?
I have not had any direct contact with IBM's technical support. It's mainly our administrators who deal with them. From what I heard, they are quite good, and I would rate technical support as an eight.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We were using an Oracle-based solution before, but it was a bit slow. Our customers are moving toward IBM MQ, so we made the switch.
How was the initial setup?
I did not take part in the initial setup. It was carried out by another party and involved two engineers, taking a couple of days.
What about the implementation team?
The deployment involved two engineers from another party.
What's my experience with pricing, setup cost, and licensing?
I am not exactly sure about the licensing cost compared to similar products, but I assume it is affordable since we continue to use it, and it is also used by our customers. I am not aware of any extra expenses or financial arrangements.
Which other solutions did I evaluate?
I did not evaluate any other options aside from IBM MQ. Our choice is tied to what our customer uses, which is IBM MQ.
What other advice do I have?
I highly recommend this product to other businesses. It's a good product to work on and simple to use once you learn it. The knowledge stays with you. I would rate IBM MQ overall as eight out of ten.
Which deployment model are you using for this solution?
On-premises
showing 1 - 10