Deployment was done in-house. We've had some challenges, but that can be fixed while we are connected with our IBM MQ support team.

The length of deployment depends on if there is a huge queue manager and on the type of integrations that need to be done. If it's a simple integration or there are less than 100 or 200 applications, deployment will take four to five hours.

The implementation was completed in-house with integration developers doing the important work. 

We have a fully dedicated team in-house to support MQ. There are teams that can help. TCS is one of them and IBM itself is one of them. And there are a few local vendors in the market that are quite proficient in it.

We have a support/ maintenance team of four pax and we are running 200 to 300 services on MQ. The solution doesn't exactly provide a user interface to the business user. The solution is more of a technology layer to support applications and we have 15 to 20 applications that are connected via ESB & MQ.

We do the implementation of the solution.

This solution is a message exchanges system for queuing messages. The messages come in and if they are rejected or if they fail to be received, they sometimes fall into something that is called a dead letter queue, queues that are dead, or queues that are ineffective. Those have to be maintained and monitored at all times. There is quite a lot of attention needed. It is extremely critical and the robustness is extreme when it is on the edge. When it is in the enterprise is not that bad, but if it is on the edge, outward-facing to the client, we do a lot of work to maintain and ensure that it is working at all times.

The initial setup is done by our deployment team. In fact, I currently work in pipeline development for MQ, so it's easy to implement.

We have an admin team that does the configuration and setup of the solution. They can do it in one or two business days. 

We used consultants for the implementation and those were consultants from the vendor who were already experienced in the TTI server.

Implementation was done in-house and it took a couple of hours.

We didn't use any integrator. We have a team of about five people who work with this solution. We have developers, a team lead, and a project manager.

The vendor did the MQ installation. We had a good experience with the IBM consultants.

The deployment was done in-house.

The time it takes to deliver a new integration varies. From our point of view, we are really fast, but we do not develop applications on our own. We are a type of project management and system provider company. This means that most applications are written by different companies. E.g., we have IBM as a software supplier.

Two people from our company maintain the solution along with a consulting company that we have. All this is done part-time.

The IBM consultants we worked with were very good.

I have installed it myself. I'm also doing maintenance, patching, upgrades, and migrations. We have a team of 11 administrators who are working on IBM MQ. They use it on a daily basis.

The upgrade process is simple. I refer to IBM Information Center. As a part of the preparation, I go through all the steps that they have given. I correlate the information with the infrastructure that we have. According to the current infrastructure, we document the requirements, and after that, we do the upgrade. We couldn't do in-place migration or upgrade, so we had to do parallelization. We took a new server, installed the new version, created a new queue manager, and migrated all the services.

I deployed this solution for the company.

The number of people required for maintenance depends on the environment. We used to have one person manage each application that was connected to the MQ server, which meant that we had four people maintaining it.

We received the software from the vendor, but we deployed it on our own. We also do the maintenance ourselves. 

We used an in-house team and a system integrator.

We handle the implementation and maintenance in-house. The number of people required for maintenance depends on the team. Our team members support multiple accounts.

We had assistance from an integrator.

We have approximately seven engineers and administrators that do the implementation and maintance.

I wasn't a part of the process. I can't say if we enlisted outside help or not. 

Implementation was very straightforward.

We are a software development firm working with medium to large businesses.

We did the setup.

We deployed it ourselves.

Limited staff is required to maintain this solution because of its stability.

Through Vendor Team. Excellent.