We have it on-premises. We're not using it on a public cloud currently, but it can be deployed there.

The initial deployment takes hours. There's a lot of manual scripting involved. So, Ideally, some kind of automation for that process would be helpful.

Initial deployment is very simple. You don't need someone who is very technical to configure it, unless you are establishing a new environment or a server, or infrastructure as a service. If you're upgrading things, it's very easy.

We use one support engineer for maintenance. They monitor the server and infrastructure.

Setting up MQ is straightforward. Generally, installing MQ isn't a big deal. It's a simple product. The magic happens when you go configure the topology and do some performance tuning.

I work for a huge company, so the deployment is done by DevOps. We're on the application side. The installation was dodgy in versions 5 or 6, but now you just drop a container.  We try to automate as much as possible, so we wrote extended Jenkins jobs to flash install all the virtual machinesWe don't deploy MQ on the cloud, but I'm thinking of migrating it to Azure. I see no benefit in a private cloud. 

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.

The initial setup is easy with no huge steps. 

There really isn't any deployment. Creating queues does not take much time and we use them with channels and subscription topics to push and pull messages

I am MQ version 6, & 7 -certified solutions architect & system administrator. So I find the setup to be very easy. I have been using MQ since very early of my career, and I was also with IBM for quite some time. So for me, it's very straightforward. The installers come with a nice, quick-setup guide, and most of the time, after the training, users can go set up their own MQ.

The amount of time it would take to bring it to production depends on the scope of the services. If I just have to install MQ, it is not more than an hour. But if I have to install MQ for specific servers, I would probably have to take account of the log size, its location, and what the volume is per day or per week, availability aspects, so it would take a bit longer.

Most of the time, when we implement MQ, we implement it along with other products. It depends on the use case. If you just want to query the server to get the information, I would recommend that to be asynchronous because inquiries are huge in volume. If the use case is payments, it could be defined as synchronous mode, and within the flow we could still break it into two or three parts.

From the design point of view, it is still pretty straightforward, depending on what licensing model you want to go for. If you want to use one MQ server with multiple clients it's doable, but if you have more critical systems running, then you should go for multiple MQ servers so that you have a dedicated server for each particular application. Those are the guiding principles that we use internally for projects to follow.

For deployment, we have written our own scripts. We are mostly relying on AIX/ Linux server. Our scripts are pretty much standard to do things like create/ change queue, channels and it's properties, shut down, restart the MQ services. All these are already scripted, so for our support team it takes them a few minutes to run through them, one after the other, and wait for scripts to be executed.

The solution is deployed on an on-premises model.

Setting up MQ is easy. We had a "grow as you go" implementation strategy. We started with a single channel and progressed to multiple queues and channels depending on the systems and integrations with other systems. It was a gradual deployment and expansion as we grew the services interacting with the core system using MQ. Maintenance requires two or three admins. 

The installation can be fairly simple, but when changes or modifications are necessary within the system for the implementation it can be a bit difficult. We standardize a lot of the process whether it is using Jenkins or Pipelines, or another solution to make it as simple as possible. However, when we make changes and more errors and configuration problems come up, it can be quite difficult to narrow down those problems. Generally, we automate most of this part which has limited the impact but the process could be improved.

Since we automate a lot of the deployment elements I am not sure the breakdown of how long it takes for each part, but typically all together it takes approximately half a day.

The initial setup is easy. If the required access and permissions are provided, the deployment takes one day or less. But in most cases, we wait for some permissions or access to systems to finish the deployment on the customer site. One DevOps employee is enough for the deployment.

I rate the initial setup an eight out of ten.

In terms of the initial setup, we never faced any problems. It's quite easy. Even the cloning and queue managers are really good. 

From an implementation perspective, it was hard for the features that we were using. However, recently, it has become quite easy to implement.

The setup team is a bigger team due to the size of MQ in the company, which is quite huge. We have around 200 managers and the size of the team is around 20 members and they can all assist with deployment tasks.

The initial setup is pretty easy. It's not that complex. I'd rate the ease of implementation at a seven or eight out of ten.

The deployment time is pretty short. It's not a long process. 

In an integration scenario, like payment processing, where the payment has to go to the backend system, SAP, or talk to multiple applications, due to the fact that it's a lengthy, complex business process, we just decouple it. Some of the information we get immediately after receiving the request, and we pass on the information to the customer. Then, we put the payload into the IBM MQ, and then we started processing from IBM MQ. So there are integrations that sometimes need to be done or worked with. 

The initial setup is not complex. It is a very simple installation. I've been provided with instructions that make the whole solution extremely easy to download and install.

The entire process is very fast. It only takes about 30 minutes to deploy.

We have different departments that can handle deployments. We have about 100 people on our team that can handle this type of assignment.

I've been doing it for over 20 years, so it's straightforward to me. Beginners might struggle with the initial settings, like user rights and the basic stuff, but setting up MQ is fine.

Actually, setup was straightforward. I'm not a hardware person and it was a first-time setup. It was what they said it was. It wasn't a 30-minute setup, but it was pretty easy.

The initial setup of IBM MQ can be straightforward if you have the documentation, it is step-by-step and straightforward.

The solution's initial setup is easy.

The setup for this software was very complex, particularly with the integration between the two systems I was talking about earlier: on the core backend and on the user frontend that is the Wall Street system. It has a lot of different types of flows, and all those flows are defined into the server that is called TTI that is working under the MQ series. That contains a lot of complexities because the vendor of the front-end system has included in the MQ side the server functionality for the application, instead of doing it directly in either the backend or the frontend. This means the MQ part is also helping with the logic for processing messages, and the logic is maintained in a layer: the MQ layer in the server that's called TTI. This is the first time we have faced such complexity, but regarding the MQ as is, meaning the vanilla version, it is quite straightforward. That server works the proper way.

I was involved in the initial setup, but not in this company; at a different company. I found that it was easy to install.

I was not really involved in the initial setup. I was probably around for it, but I had an applications background. I went from the systems side to the applications side, and back to the systems side. It was kind of the interim period. I'm not really responsible for the MQ right now. I'm more of a user of MQ and a supporting group. As a mainframe user, we basically have that relationship with them.

If it is a standalone implementation, it is straightforward. If the implementation is the higher availability mode, XM mode, it becomes a complicated process because it comes with a shared disk resource where one instance goes down, and another instance comes up. This means it can not always be an Active mode, you require an Active-Passive mode all the time. This can increase the setup cost and complexity.

It was straightforward. It took less than a minute.

The initial setup is straightforward, it's easy.

If someone knows its basic structure, it is easy, but the open-source is much easier than IBM MQ because you just have to install it and start working on it. With IBM MQ you have some installation procedures.

The open-source version needs route access which could be security compliance and could be complex.

There are a lot of things that MQ can do, so the configuration setup needs some involvement.

In some places, setup is very easy and in others, it is a little bit complex. When we are trying to deliver all of our transactions from web to system CID, it's a little bit complex because the workload is not the same in both platforms. To make this work is sometimes difficult.

Setup was straightforward. I had experience from my previous work, so I was able to bring that experience and implement it here. I was fully versed with it, so it was easier for me.

I was not involved in the initial setup. I was a DB2 engineer, a systems programmer, for many years. Then I moved into management, into the middleware area, which had CICS, MQ, and other products. Then I actually moved up into a director and now, I'm director of mainframe services. I wasn't involved in the actual initial setup.

Some of the things have been around for 20 years or so, but I've been involved in probably five or six upgrades, other deployments and other feature turn-ons that MQs contributed to. I was heavily involved with that, but not as far as bringing it up and installing it from the beginning, no.

It was already there when I came to the company some 13 years ago; already in place. But I've managed it for probably 8-9 years.

From a coding perspective, it's a straightforward process. There are no complications. We cannot directly access the IBM server because there is a separate team assigned to do some security and get some code of conduct from the MQ team. They are handling the MQ server. So we ask them to create these entry servers to discuss that. And also, we are defining everything. We are responsible for handling invalid queries. So they recreate a wrong question or wrong to them. So, whatever is an appropriate question. 

In terms of maintenance, there are three reasons you'll get a maintenance window. On the maintenance window, we are just restarting the epicenter. Nothing else. If it requires any patching or updates, we perform those. But you don't have to restart the application.  The epicenter typically runs continuously.

The installation was straightforward until we started to have resiliency problems, it then became more complex to have to set up clustered MQ servers. We were using Linux Red Hat cluster services, which became an extra burden. When it eventually came time to do other activities, such as updating the operating system or a specific driver, for example, a firmware driver for the bare-metal servers themselves, having the MQ's clusters being sensitive caused a challenge for service and support.

The initial setup was average. Not so complex and not so straightforward. 

The deployment itself, not including testing, took a couple of hours. 

The initial setup was easy because IBM did the installation and integration of MQ with our appliance.

The deployment took a month.

The setup was straightforward and we wrapped it in a very complex way.

The initial setup was straightforward. It was easy to install and configure.

We setup IBM MQ about four or five years back. I think the setup now would be much easier than the one we did then.

We have a standardized way in describing our servers, services and rights because we have our own infrastructure. We just generate the MQSC scripts, then push it to the right server.

Initial setup was pretty straightforward. The more complicated part of it was the actual IBM CLM tools implemented within IBM MQ. IBM MQ itself was pretty simple.

I've heard that there have been challenges with upgrades, but we haven't gone through an upgrade cycle yet, at least in quite some time. We'll see how well that is but we haven't had that challenge yet.

I was not involved in the initial setup.

I was not involved in the initial setup.

Initial setup was straightforward and flexible.

The setup was very complex in the beginning: how we had to put it in, how we had to tune it, and how we had to fix it. There were so many parameters. It wasn't just a simple drop-in, deploy, and go. In addition, because certain applications work in a certain manner, it required a lot of tuning.

My team, on average, has 10 years of experience on MQ so at this stage we've come to the point where we can tune it fairly quickly. So while the initial setup wasn't simple and quick, it has become very quick.

The initial setup took us several weeks, if not a few months. We had to get IBM to help with things in the beginning. We had system issues then, but it has been stable since then.

I was involved in the setup. It's straightforward, but I had done this before.

Because I had worked with it before, initial setup wasn't that bad. If I look at myself at the beginning, when we wanted to set it up, I actually went and took a course before setting it up. Especially on the iSeries side and all the communications, you have to get familiar with all the terms and terminology that are being used on the application. Once you know that, then setting it up is not a big deal.

The initial setup is very simple. The installation doesn't take more than 15 or 20 minutes.

We've set it up in several ways. I had it for a year. Each original implementation was with Accenture and we've had several crews come in to manage the services. There are different SIs that come in like Tech Mahindra and HCL. Over 15 years we've had a lot of independents come in and support. 

We're just building on top of the existing platform now. But we've made a strategic decision to move away from this on-premise infrastructure, the data centers if possible.

We've got 4,000 employees, it's quite a sizeable business that we take on vendors to come in. We're not an IT shop. Different managed services from different vendors.

We don't consider users for the platform. It's more about what transactions. So I think it ranges from two and a half million to 10 million messages a day.

The initial setup is very straightforward. I have done it both on Linux and on Windows. With Windows, it is just a case of hitting the "next" button. I would say that within ten minutes, you should be finished with the installation.

Prior to the installation, you have to make sure that you have Java installed.

The setup was straightforward for simple usage. Load balancing is more complex.

I was involved in the initial setup. It was fairly straightforward. Once you start creating the queue managers, there's some configuration involved, which our developers take care of. I just take care of the basic installation of the product, which is very simple.

I was involved in the initial setup. It was straightforward.

I was involved in the setup process. We got the basic functionality working, which is not difficult. It's getting the full value out of this solution that was harder.

I was involved in the initial set up at my organization from an infrastructure standpoint. We provide the infrastructure tier. On the open-system side, we helped with it and helped the implementation out on the mainframe.

The actual installation is straightforward. The configuration and the implementation of enabling MQ to talk and communicate between the systems can be complicated.

I was involved in all the possibilities. In the past, I have carried out the implementation process from scratch. With my current employer, I have started supporting and building more for the already existing environment.

Initial setup was complex because of what we were trying to do, as far as the distribution of a number of clones. With the IBM team, there was more internal drama and relationships – more personal problems – than there were technology problems.

The onboarding processes and setup are very easy. 

The basic setup is simple. The deployment is fully automated.

I was not involved in the initial setup.

I was involved in the initial setup. It is straightforward. Since I'm familiar with this tool and been working with it for 12 years, it was straightforward.

Initial setup was quite straightforward.

The people on my team were involved in the initial setup, absolutely. There was a little bit of complexity involved with the mainframe section, around some general ways that the thing is implemented in the system, and things that have to happen early on during the IPL and some other processes that we have. That's the part I'm most familiar with. The other platforms it's run on, I'm not sure.

In general, once we got through some of those issues, it was pretty straightforward.

IBM MQ has a complex setup. The time it takes for deployment take approximately two to three months.

The initial setup was straightforward and took around half an hour.

IBM MQ is not at all difficult to set up.

There is no deployment, per se. A broker will handle the deployment.

The installation can be easy, but it depends on the environment.

The initial setup is 50/50, between straightforward and complex. The difficult part is because for the integration of other systems with IBM MQ, they need to use software from the IBM client. But the installation itself is not difficult.

The initial setup of IBM MQ is complex.

The installation is not difficult for IBM MQ and takes approximately one day.

Setup has to be done by the team from IBM. Client just needs to enjoy the excellent support.

The initial setup was straightforward.

I was not involved in the initial setup.

It's straightforward to set up IBM MQ because we can use it in lightweight modules, like containers, for example. It's not always easy for applications to connect to IBM MQ, but I think it's fine in general.

I can't speak to how the initial setup went. Those kinds of tasks are handled by the technology team. Therefore, I can't say if it was an easy or complex process.

I'm not sure, ultimately, how long the deployment process was.

The initial setup was straightforward. It's all about planning because we have multiple application teams involved. Deployment takes somewhere between half an hour to an hour, but for the coordination to check and perform from the application side, takes almost a full day because we have critical, multiple applications. It needs to be coordinated and we need to be sure they are able to connect perfectly with our environment or with the MQ.

The initial setup is straightforward. It takes a few minutes.

In the latest installation that we are talking about right now, I was not involved. But, for other installations in the past, I was involved in the set up and it was pretty straightforward. I'd consider MQ one of the simplest products to use.

I was involved with the initial setup. It wasn't quite straightforward because the original versions used CICS and that was a little tricky sometimes. But, then they went and made the agent as part of the package of using the CICS.

Setup was more complex than what I thought it might be. We have an active-active cluster, meaning that the systems will fail over to each other if they need to. It was more complicated to set up. We had difficulties setting that up initially, even with consultant help.

Initial setup was straightforward.

I'm a director and me and my team were involved in the initial set up of MQ. It was very straight forward. We had people that were familiar with it. Some of the people that I worked with, or that worked for me, really had a good background, so it went very quickly, and it was very straight forward.

The initial setup was a bit complex. The installation itself can take anywhere from half an hour to four hours, and the configuration could also take a couple of hours, depending on the complexity of the design.

The initial setup is usually left to other people to do. I've never actually done the installation and setup of it myself. It has been other people with a bit more deep technical knowledge who have done the implementation and actual installations. It was a very long time ago when I received the first set of CDs where we were going to be doing the installation of it, but I don't have that deep technical knowledge of the implementation as such.

While I was part of the process for implementing RabbitMQ, which was very simple and straightforward, in the case of IBM, I didn't install it myself. Unfortunately, I cannot explain how easy or difficult it was as I was not part of the experience. My understanding is it's not too difficult.

In terms of maintenance, we have two people from the support team handling that aspect. They can restart the server or look into the queues. They aren't working in shifts, however, if there are issues, one of them is normally available to troubleshooting.

In comparison, for RabbitMQ, we had only one developer that installed it and created the publishers, workers etc. I believe the support will be the same as for IBM. In both cases, there aren't too many people needed for maintenance.

The initial setup for the messaging part is straightforward. For other features, it's of medium complexity.

Setup was complex. It requires a lot of components to be configured.

I was involved in the setup of the distributive systems. It was straightforward.

Setup was pretty straightforward. MQ has been around for a long time. It's a reliable product. It doesn't change that much, so I think everybody, at least in my organization, is fairly comfortable with installing and implementing MQ.

It is pretty easy to set up. The installation takes less than five minutes for each server. People can learn IBM MQ in one week.

Even a version upgrade can be done easily. Including doing backups and installation, it can be completed in 10 to 15 minutes. Even RabbitMQ and Kafka require more steps for setup than IBM MQ. Installation of the IBM product is very simple. 

I was not involved in the initial setup.

I was in the initial setup; I was involved in the design of the environment for MQ and the rollout of that platform.

It was midway between straightforward and being complex. Our environment is quite complex. We have to integrate the different systems; we have MQ on z/OS, we have MQ distributed. It's right across the platform. The setup of MQ was not complex, but the integration with our environment had some complexity. Overall, with the MQ platform, I don’t think we could have done it any easier.

MQ is has a straightforward implementation. There is not much configuration required. It is more complicated for a cluster implementation and the active-passive implementation. You'll need more technical knowledge 

A regular deployment will take around five to 10 minutes. If it's for a cluster implementation, it will take at least 15 to 30 minutes.

We have an internal team that does the implementation. We asked IBM to do the deployment. 

The setup and configurations are very easy, not complex. I would give the product plus points for this. This is compared to readily available, open source products that make you scratch your head when you go to set them up because they don't have documentation.

It takes a couple days to deploy the product to production.

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

The setup is between straightforward and complex. It's not as straightforward as Apache ActiveMQ.

I was not involved in the initial setup.

If you are familiar with IBM products, you will find initial setup straightforward.

The setup is straightforward. There is not much to create, it's a one-time setup, including configuring the high-availability. That is the main thing. The parameters create the queues. It takes about 10 to 15 seconds for each queue.

In addition, we had IIB, the IBM Integration Bus deployment, including message flows and DB scripts, etc. So the deployment was not only MQ. In deploying IIB flows, we had some queue creation, server connections, and channel creation. Overall, it was about 80 percent IIB deployment and 20 percent MQ deployment.

We had two people involved: one guy from the support team and one guy from admin. For maintenance, in the sense of the application support, we have four team members but we are handling multiple applications, not only MQ.

I was not involved with the initial setup.

The setup was complicated because when I started and there were around 400 queue managers. We have four companies that we communicate with, so we changed a lot of the architecture, i.e., we went from the local queue managers to centralize and to reduce issues, in order to have a more manageable system.

I was not involved in the initial setup with this current version.

Sometimes I am involved in the setup. But, now my people have become experts setting it up. There are issues that happen once in a while. For example, last year it happened when we changed the server. For whatever reasons, the configurations were in fact reset. So we brought IBM in. Those were complex configurations. For whatever reason, a couple of parameters could not be reset. Or, they didn't remember which parameters to reset.

The initial install was a long time ago.

This initial setup is not complex at all. Deploying it was very easy.

The initial setup is straightforward. On the AS/400, setup takes about an hour.

The initial setup is difficult. Creating your own cluster is difficult and working with cluster repositories is difficult. Issue management with IBM MQ is difficult.

I'm working on the development side. There is a setup team that is dedicated to working on implementations. I don't have enough hands-on in the configuration of MQ to comment on the setup.

The setup is moderate; it's not that complex. Recently, we are working for one of the Microsoft technologies transformation, i.e., from the legacy Microsoft technologies to the latest Microsoft technologies and that integrates with some of the z Systems.They are using MQ as the integration layer and even there, it was a very seamless integration for us. It's not too complicated nor very simple either. It is at the moderate level, which for integration is anticipated.

I would say it was both straightforward and complex, but not that complex. I mean the installation normally would take some time and with all of them open, it's just a button click and you're done.

I was not involved in the initial setup.

I was not involved with the initial setup. We usually get in touch with them in order to solve the issues.

While the initial setup is not overly difficult, the user interface is not very user-friendly. 

I do not get involved with the setup of the solutions. But, my team member was very happy with it, and said it was quite easy to install. 

The initial setup is very easy. Deployment took a few hours and required a three-person team to implement. 

N/A

The initial setup is straightforward, but you need to take the platform into consideration. If you are talking about Linux, AIX, and Windows, then the setup is really straightforward. However, z/OS or iSeries from IBM are not so straightforward so you need to be familiar with those platforms.

It takes half a day to fully configure MQ on Windows and Linux, and a bit longer on AIX. For z/OS and iSeries, it takes about five days to fully configure their environments.

The initial setup is not complex. It's very simple. I didn't find any difficulty with it.

I was not involved in the initial setup.

The initial setup is straightforward. It's not very complex.

The installation is easy but the configuration could be complicated because you have to specify a lot of stuff, like queues. It could be a little bit complicated to configure if you have some specific scenarios. For a simple scenario it's easy, but when you have somewhat more complicated scenarios — for example, when you have a hybrid or you need to support some specific security requirements which you use to implement custom components — then it's not easy.

The time it takes to deploy depends on what type of clusters you need. For deployment for testing purposes, where you do not need any cluster, it can really be done in one day, maximum. It's not that difficult. But if you need to deploy a cluster, like a Veritas Cluster, and to prepare the workload balance, it can take days, with system testing etc. You have to combine a lot of other components.