We deployed this solution. We have two to three people who do this.

Usually, we have the support team of a project. The support team takes care of such installations.

Its maintenance is easy. It doesn't take a lot of effort to maintain the product. The Infra team usually does some patching of the environment, but we haven't seen any outage of our application that impacts the business in real-time.

It took us a couple of minutes to deploy the product. We deployed the solution with our in-house team. A team of two to three administrators usually monitors the product in the production environment.

A was working as part of the vendor team, as part of the implementation consulting organization.

We didn't do it alone. We worked with IBM, and then, IBM nominated a local partner in Nigeria that worked with us to set this up.

The deployment of the solution is very easy. We just add the integration server and drag and drop the services to the integration server. We deployed the solution in-house. We do not face any trouble in the maintenance of the product.

We did the implementation of the IBM Integration Bus in-house. We have two people for the maintenance and support of the solution.

Two people were involved. One is the administrator, who has the necessary permissions and installs the product. 

The other is the integration developer, who defines the integration flows, steps, and profiles. 

One person could be from IBM support, while the other would be from the Windows or Linux administration team.

The product requires ongoing maintenance. However, the people required for the maintenance depend on the project. In my organization, we have five to ten based on our projects.

A common practice is the implementation of CI, CD, and DevOps tools. These tools automate the deployment process seamlessly. Whenever code changes are made and pushed, the configured DevOps tools take over, ensuring an automated deployment without the need for manual intervention. This streamlined approach enhances efficiency and minimizes manual efforts during the deployment phase. Maintenance for IBM Integration Bus is well-established. As part of routine maintenance, regular fixes are provided for the product, contributing to the overall stability. Daily monitoring of IBM Integration Bus objects is a crucial aspect of maintenance. We maintain a dedicated team that monitors these objects 24/7, both on-site and offshore. This continuous vigilance ensures that any potential issues are promptly identified and addressed, minimizing any impact on business operations.

I was the developer consultant.

I have been working on the migration myself, but I am using a support engineer to help us. He is working very hard, spending many weeks and months with me, guiding me when I experience a problem.

I did not implement all of the applications, but I took on the responsibility to migrate all of the previous ones. This is a challenge because I was not involved in developing them. I treated it more like a recompilation problem, but some of the functions are not working. The old libraries are no longer used, so I am learning all of the new things that have to be done.

Given that I thought the upgrade process would be automatic, I did not really have an upgrade or migration strategy. I thought that all of the projects would compile. When they did not, I looked back at the manual that the previous consultants had written.

What I found is that the project structure was a little bit tricky, and it took some time for me to understand it. Things were not done in a normal way, and it did not work when I set it up as such. This meant that I had to backtrack and follow the instructions in the manual.

The first time we purchased the tool, we worked with a consulting company that assisted in the implementation. Now that we have experience, we handle it ourselves.

We implemented it in-house.

We had a consulting team from IBM on-site to perform the implementation. For the first three years, we had IBM consultants with us to guide us in the development and also in the operating of the solution.

We did the implementation through our in-house team and it took approximately one day to complete.

We used a third-party vendor, who help us install the solution and it was not easy. If you have most things in place at the site the whole installation process can take approximately three days. 

To do the complete deployment you will need at least one architecture that understands this IIB solution. It all depends on what kind of IP division architecture you have. Based on the project's scope, you then can define your team. There is no certain number of how many team members is required. It depends on your project, how large it is, and based on that you can decide how much manpower is required.

The implementation was done with our team. Additionally, we used the standard development process for teamwork.

There are nearly five people required for deployment and maintenance. 

The solution does not require much maintenance.

We have a team of 10 or 11 people for deployment and maintenance.

We are working in the bank, and we implement everything internally ourselves. We are maintaining it, and we don't have to do too much. We have a separate team for maintenance. We have administrators as well on the operations side. They are looking after it.

It is important to consider:

• API control
• Firewall security

 I am working in a consultancy company. We install this for most of our clients. We develop services for them using it.

We implemented through an in-house team. I work as an architect, but we have a DevOps team that takes care of maintaining the pipelines and as-needed administration activities. 

I handled the implementation myself.