IBM MQ Room for Improvement
An area for improvement for this software is that sometimes, messages are not consumed in the queues. We have seen queues where not all messages are emptied. That issue has been solved by our IBM team located in Spain, but we haven't received detailed technical information as to why those queues are not totally consumed. A probable reason could be some service and availability issue because of server updates in IBM MQ itself, or server updates related to the operating system, which in our case, we are using Red Hat Linux.
I have seen a lot of problems with the file transfers, e.g. using FTP or SFTP or LFTP. Normally with all these kinds of transfers, they are not on a transaction boundary, meaning a transfer can fail during the execution. We are not certain why it hasn't reached the destination as these protocols are not transactional which you normally have in MQ messages. What I would like to see in the next release is a solution for the MQ file transfer. I saw some literature about it, but I am not sure if the feature is available, or if it will be easy to configure and maintain in the bank.View full review »
Head Of Operations at a financial services firm with 10,001+ employees
Everything in the solution could be simplified a little. We have trouble with the configuration and cost which is mostly an internal issue, but nevertheless, the errors do come up when there are configuration changes across a specific version. We have slightly different versions, which may have slightly different configurations which cause issues.
It is intensive to maintain and train people to use the application. There has to be a certain amount of education going into the developers, as well as the infrastructure staff. This could be improved.View full review »
Software Engineer at a financial services firm with 10,001+ employees
Sometimes, there are network issues, which means more applications are connected to those messages, so I would like to fix that. For example, suppose there's a new network, and I want to add virtual memory to address a network issue within the cluster. So there is a network issue that needs to be resolved from the cluster. So I need to add the permissions for that particular team or particular time. There are many complications with IBM MQ servers.
It would be an advantage if they can include streaming in IBM MQ, similar to Kafka. Kafka is used mainly for streaming purposes. This feature is clearly lacking in IBM MQ. If they add this feature to IBM MQ, it will have an edge over other products.View full review »
Enterprise Architect at a energy/utilities company with 501-1,000 employees
There are things within the actual product itself that can be improved, such as limitations on message length, size, etc. There is no standardized message length outside of IBM. Each of the implementations of the MQ series or support of that functionality varies between various suppliers, and because of that, it is very difficult to move from one to the other. We have IBM MQ, but we couldn't use it because the platform that was speaking to MQ didn't support the message length that was standard within IBM MQ. So, we had to use a different product to do exactly the same thing. So, perhaps, there could be more flexibility in the standards around the message queue. If we had been able to increase the message queue size within the IBM MQ implementation, we wouldn't have had to go over to another competing product because the system that was using MQ messaging required the ability to hold messages that were far larger than the IBM MQ standard. So, there could be a bit more flexibility in the structuring. It has as such nothing to do with the IBM implementation of MQ. It is just that the standard that is being put out onto the market doesn't actually stipulate those types of things. As a result, rather than following the recommendations and the standard that was within the IBM MQ implementation, some suppliers say that we need the ability to have longer message lengths than they've implemented, but that's the way it is. Other than that, I'm very pleased with it as it is. It is good at doing what it does. I love the actual implementation, and I've used it a lot.
Lead Talent Acquisition Specialist at a tech services company with 1,001-5,000 employees
The user interface should be easier to use.
The user interface should be enhanced to include more monitoring features and other metrics. The metrics should include not only those from the IBM MQ point of view but also CPU and memory utilization. These kinds of features would be really helpful when we have a large infrastructure. Right now, this limits us from using the product.
In general, the user interface should be more catchy, to entice users.
IBM should promote the use of the MQ appliance because the speed and performance are superior when compared to traditional ways of using the product.
If IBM were to release as least some limited features for MQ as open-source, then it would be great because people will migrate to this solution instead of choosing open-source products like Apache Kafka or RabbitMQ.View full review »
The way the solution provides us with the product and the way we use it gives us what we need. We don't actually have any issues with it.
There could be a better front-end GUI interface for us, where we can see things more easily. However, apart from that, it works well.
The pricing is definitely could be cheaper. Also, the support model, even though it's very good, could be cheaper as well.View full review »
Lead Software Engineer at a retailer with 10,001+ employees
I would like to see message duplication included. We don't have a mechanism for duplicating a message.
There is a different model where you can have multiple subscribers and not publish the stored data to multiple subscribers.
Duplication is the most important for sending the same data for different applications.View full review »
We have had an issue with the migration. Most of our applications are running on Java and WebSphere. We have a project to get rid of an old .NET application since we are experiencing a loss in connection during the migration to 9.1. The problem appears to be more on the .NET side than the MQ side though.
The technical user interface is outdated in terms of the language used. I think this is inherited from the mainframe. This is more of an engineering issue. It is running on a Windows platform, and I don't like having Windows being the backbone of our company.
I don’t like legacy view of MQ.View full review »
I would like to see their cloud feasibility with other vendors. I know that they are very much tied to their own cloud right now, but I don't know how they are supporting AWS and Azure.
With IBM products, there's less marketing. If they do more demos and more seminars on their products, it will be very useful. On a given day. I get seminar invites for many vendors and products, but for IBM, I may get an invite once or twice a year.
Documentation is easily available to people who know about IBM products. However, if you're not familiar with the products and because there are no popups about seminars and product news, you will not be able to easily find the documentation. So, I think that there's a gap in IBM's marketing, which needs to be improved.View full review »
IBM support team is really only concerned with the IBM cloud. They're not supporting any other cloud platforms or suggestions. It would be nice if we could get support for Azure.
MQ supports more than 4MB of data transmitting. That is not supported by ASB. Because of this feature, we are using MQ. Otherwise, clients will be motivated to use Azure Service Bus. IBM MQ should think about how the cost can be minimized and how to provide better service for users. MQ could provide more incentives or services that are better than Service Bus, so that our users will be motivated to use IBM MQ.View full review »
Service Delivery Consultant at a computer software company with 10,001+ employees
The licensing fees should be more cost-effective so that we can better pitch the product to our clients. With the pricing as it is, they tend to move away from IBM products. They look for other solutions, such as open-source products.View full review »
Sr. Solution Architect at a computer software company with 10,001+ employees
The integration capabilities could be even easier.View full review »
Enterprise Architect & Solutions Architect at AIA Australia
They probably need to virtualize the MQ flow and allow us to design the MQ flow using the UI. It would also help to migrate to the cloud easily and implement AWS Lambda functions with minimum coding. If you have to code, then just with NodeJS or Java.
Many things should be done out of the box, like MQPUT directly to databases or MQGET to link to the main database. MQ should be able to connect to any language and just do it whether you're using mobile apps or web apps. It should be possible.
The other probably more key thing is that to get IBM on-premise is hard because there are no freely available videos and courses. Technical support in Australia could be better.
Senior Technology Lead at a financial services firm with 5,001-10,000 employees
The clustering capabilities have provided some difficulties when it comes to resiliency. This has been a challenge for managing the environment.View full review »
IT Architect at a financial services firm with 10,001+ employees
We are looking at the latest version, and we hope that resilience, high availability, and monitoring will be improved.
It can have some more improvements in the heterogeneous messaging feature. The current solution is on-premises, so good integration with public cloud messaging solutions would be useful.View full review »
Senior Technical Lead at a financial services firm with 10,001+ employees
The main issue we are having with the solution is due to the connection dropouts which have been going on for a long time now. Sometimes randomly the connection gets disconnected and we try to send a message, we get a failure. We then need to manually take an action on the message, which is happening quite a lot in production. We have been working together with the MQ team trying to increase the connection and some channel upgrades. We are taking steps in the right direction but the issue is not completely fixed.
Additionally, there is not any statistical messaging information being captured. We are not able to pull up any reports to determine when a message was sent. For example, how many messages during the day or during five minutes.View full review »
IBM MQ is not very user-friendly. MQ needs to redesign or add some sort of user-friendly interface in order to offer better performance.
This is a very old solution. Nowadays, some other products are designed to be much more user-friendly as compared to IBM MQ.
The product needs better administration.View full review »
Database Administration Team Leader at a transportation company with 10,001+ employees
There isn't that much happening with the installation consoles and monitoring consoles. This could be improved.
We need to have a better administration console and better monitoring features. Right now, they are not good and could be a lot better.
The pricing could be better.View full review »
Technical Specialist at a maritime company with 10,001+ employees
I'd very much like to see more integration in the monitoring tools.
It could always be more stable and secure.View full review »
Yapı Kredi şirketinde Application Infrastructure Manager at a financial services firm with 10,001+ employees
It would be nice if we could use the cluster facilities because we are doing active/passive configuration use. Maybe we could implement them in cluster scenario and use the active/active nodes.