IBM MQ Review

The message queue and the integration with many development platforms/languages are the most valuable features.

What is most valuable?

The message queue and the integration with any development platform/language, i.e., NET and Java, are the most valuable features.

How has it helped my organization?

We are the Companies and Intellectual Property Commission where our mandate is to register and regulate companies and intellectual property (patents, designs, trademarks, and copyrights).

In South Africa, a company that wants to do business with the government or a privately owned company is required to also register for taxes through the South African Revenue Services (SARS).

We have integrated our registration process with SARS to seamlessly register both the company and the taxes upon registration of a company with CIPC using the near real time concept.

We created an interface between two state-owned companies. We replaced the FTP/SFTP process that was cumbersome and often difficult to synchronize the two databases between CIPC & SARS.

Now that we utilize IBM WebSphere MQ, we are never down. Even if the MQ server crashes, messages are queued and can be recovered.

This extends the use of this product to allow seamless integration with all of our stakeholders for data exchange purposes.

What needs improvement?

I don’t know of any room for improvement.

For how long have I used the solution?

I have been using WebSphere since 2013.

What do I think about the stability of the solution?

We have not had any issues with stability.

What do I think about the scalability of the solution?

We have not had any issues with scalability.

How are customer service and technical support?

We've never encountered any critical issues that required technical expertise except when the server crashed. We had to get an IBM WebSphere MQ accredited service provider to reconfigure the application. We never experienced any other pressing issues after that.

Which solution did I use previously and why did I switch?

We used FTP/SFTP before. We switched to IBM WebSphere MQ because we needed a robust, scalable message processing mechanism with the ability to integrate with different technologies.

How was the initial setup?

The setup was straightforward. Network connectivity is easy as long as you understand your solution design requirements.

I had to take over the project with limited knowledge about the product. I can safely say today that I support the solution with minimum assistance from the software vendor. I was not trained, nor did I have skills transferred to me to enable me to support the product

What's my experience with pricing, setup cost, and licensing?

Since this was not the initial direction CIPC was embarking on, we had the minimal license requirement. The cost was less than the value we would be getting out of this product. There's an annual license with support and it is reasonable cost wise.

Which other solutions did I evaluate?

We did not evaluate other options. This was recommended to us by SARS. This currently is their standard of integrating with SARS.

What other advice do I have?

IBM WebSphere MQ is robust, scalable, and reliable. You just have to clearly articulate your requirements and understand your needs so that you can realize the benefits of using the product. Our lesson learned is to always plan wide and implement narrow. This is the "phase approach."

**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More IBM MQ reviews from users
...who work at a Financial Services Firm
...who compared it with Apache Kafka
Learn what your peers think about IBM MQ. Get advice and tips from experienced pros sharing their opinions. Updated: January 2021.
455,301 professionals have used our research since 2012.
Add a Comment
1 Comment

author avatarMeir Joffe

Thanks for the review Sello. I was curious what is your opinion of the monitoring capabilities, and if your organization felt the need to use additional tools for that? Thanks, Meir