The solution's initial setup process is easy as I have experience working with six versions of it. We have deployed it on the cloud and have some of its components on-premises.

It’s not a task for a fresh and new learner. You still have to have some kind of experience working on Linux machines, as it is good for working with command lines. Because I believe deployment using command lines and scripts will be faster and more efficient than using GUI for the IBM IB.

If the command goes time out while deploying, you have to work closely with the engine and maybe have to cancel the process or make some changes on the file, or system points to complete your deployment.

The initial setup is complex. It took too long to deploy.

The solution has been on the market for over a decade, so the initial setup is pretty straightforward. They've had time to perfect the process. There's also a lot of people who understand how to install it, as it's a mature product with lots of history. Many people have worked with it.

Its initial setup was not that tough or challenging. We could easily do the setup without any challenges.

The initial setup is straightforward. We did not face any challenges.

The initial setup is straightforward. We already have a CI/CD pipeline in place. We just have to create the images, and then automation takes over and deploys it quickly.

On a scale from one to ten, I would give the initial setup a nine.

Setting up the solution is not straightforward. It's difficult and complex. We needed assistance in order to manage the process properly. It's not something you can just pick up, and then, run on your own. You need help from a partner, which involves additional costs.

The initial setup is straightforward and takes about one minute to deploy

The initial setup of IBM Integration Bus version 7 was complex, but the 10 and 11 versions were not difficult. We are using IBM App Connect Enterprise, the successor version of the IBM Integration Bus. IBM Integration Bus no longer exists, but the installation was quite easy. This is a single-step installation. The installation can take approximately 15 to 20 minutes.

The initial setup is easy, but the database is quite heavy for the local DC. It was also a little bit complex to connect to some databases.

IBM Integration Bus's initial setup is straightforward. They made it really simple to install everything. The process only took a few minutes.

I would rate my experience with the initial setup a nine out of ten, with ten being easy. 

It's very easy to set up. It typically takes less than an hour.

The initial setup was complex; deployment took around a month, while implementation took around four months.

The initial setup was relatively straightforward and not overly challenging. Establishing the required environment to run the IBM Integration Bus was a simple process. All that was needed was some server space to install and bring up the runtime environment.

The initial setup is easy. If the customer requires any API on any server, it should take a maximum of five to six seconds to deploy.

Migrating to this solution is complicated and not simple to do if they already have API integration between systems.

The initial setup is not complex, but you should have a good understanding of programming. Installation depends on the project. For some projects with a limited interface, it takes two to three months, but for a bigger and complex one, installation can take up to six months.

In banks, it is deployed on both Cloud and On-premise.

The installation of the IBM Integration Bus was straightforward. The time frame that it takes for the deployment depends on the environment the customer has. 

The initial setup is straightforward. 

Primarily, our customers have the product deployed on-premises to follow protocols. Some customers deploy on private clouds as well. The product’s installation and configuration process is straightforward. It takes six months to two years, depending on the complexity of specific requirements.

Its installation is easy.

It is quite straightforward. For our project, we do have different needs. We build artifacts that are ready to be deployed. These artifacts need to be placed in a specific folder or directory. They are then picked up and deployed in the servers. It is quite automated these days.

Its deployment is quick. It is a matter of seconds.

I was not part of the initial setup for this solution. One of the things that I have been doing is migrating from version 9 to version 10, and I have been struggling with it for the past several months.

The problems are due, in part, because there are a lot of things that we didn't know. There were mistakes in the migration because some of the things were not upward compatible. It had to do with a bug in the new version. We'd had to fix things, and we are still working on it. If the vendor would have proactively warned people about the bug then it would have been a great move.

I take care of the upgrades myself, but the maintenance is handled by three of us.

The initial setup is reasonable. However, the product requires administrators and developers to spend some time studying or to have previous experience.  Deployment is very fast. 

I would rate the initial setup (with MQ) on AIX and Linux as a six out of 10, as it needs expertise.

The deployment takes about a week or so, it's lengthy.

The initial setup is difficult to configure and set up the first time. I rate the setup a four out of ten.

The initial setup was straightforward, and IBM has a great knowledge base to help. I would rate the setup experience as four out of five.

Setting up IBM Integration Bus wasn't simple, but we've got a unique environment. We're probably about two or three months behind on our implementation because of unforeseen interoperability problems between Red Hat OpenShift and VMware. We've got a team of about 15 overseeing the deployment, including engineers, developers, and the support staff for the platform.

From an installation point of view and just initially setting up this product, it required a lot of configuration. The configuration is the harder part of the installation. Otherwise, the installation was done in a few days by our team. I do not remember exactly whether we had any major problems in doing that, but it could be there were problems and I just did not hear about them.  

There were a lot of things to configure, but that was taken care of by a different department. Our operations department would be the group that handled this. So I do not have actual first-hand information because I did not participate in the process.  

The initial setup is straightforward, especially with Java and EasyCODE.

We make use of tools like bash scripting when we deploy files. When we deploy a single file, it takes about five minutes.

The initial setup is straightforward.

The installation is not easy. You need experts who know how to install this IIB. The common technician will not have the knowledge to do it. You will need assistance installing the solution even though on IBM's website you can download the complete user manual explaining how to install the IIB servers. 

The initial setup is complex. It is not user friendly. When you have a file in the MQ Server, it moves to the next directory, which is the output. It is very complex to call a web service. It should just give the setup of the endpoint and do some basic stuff so that it can be consumed by the web service. It might be complex because of my less experience in using IBM Integration Bus.

The initial setup was easy. For Windows, you will run the installation file and you have an environment that is ready to develop an integrated solution.

If you want additional resources such an MQ, or databases, you will have to read the manual to understand how to connect them.

The building and deployment are quick and easy. It only takes a few minutes to deploy, depending on the size of your application, but it's fast.

There are two methods of deployment. You can use the manual deployment method using the drag and drop. On the other hand, you can use command-line interface for building and deployment applications. The application represented as one or some number of .bar file. It's something similar to .ear but other structure inside.

You only really need one person to deploy this solution, but we shared build and responsibility using GitLab tool-chain and Nexus Repository. The first factor is for development and building and the other one is for deployment. We use the same process for different environments. All necessary parametrization inside the application are stored as a file and substituted depend on the deployment environment during the building process.

The initial setup was complex. 

Including preparation time, addressing the environment and building the POC, deployment took around one month. We are talking about active, on-premises deployment. 

The initial setup is straightforward and took a maximum of two hours. Our technical team had eight people dealing with the end-to-end deployment. 

I believe the initial setup was easy, but this is a question best taken up with the technical team. 

I was not part of the original deployment.

The implementation of the solution at the beginning phase can be complicated. The time it takes for the implementation depends on the environment a lot of other factors.

The development toolkit that is provided is very good. It helps to configure all the message flows and data transformation. They also provide Extended SQL language (ESQL) for different types of data transformation.

The initial setup was straightforward.

The installation was straightforward.

We have experienced no trouble installing this product.

It takes a few days to deploy.

The installation is very simple. I've been working with the Oracle platform as well, and the Oracle platform installation is quite difficult compared to IBM Integration Bus.

The initial setup is straightforward, it's a simple solution. 

It was a challenging task because we were moving to a new technology, especially from Microsoft to IBM. With the help of IBM technical sales staff, online help, and some trial and error, we now have a good implementation of IIB.

It is very straightforward. It is very user-friendly integration.

For myself, the initial setup was very easy due to the fact that I have worked with IBM for many years and I'm quite comfortable with the brand.

That said, the IBM environment is fairly complicated. It is much easier than other options, even so, and technical support is quite helpful if users run into issues. 

In older versions, the setup was very complex. In recent releases, it's been very straightforward.

This solution is cloud-based. We are using it in a container image, so the one time CI/CD setup is there, in the pipeline setup, and after that the process is very seamless. We just check in our code, and then the pipeline creates an image of it and deploys it onto our private cloud platform. So it's very seamless and there's no hassle involved. 

Initially, we needed about three people for deployment: one for administrative activities, one with DevOps knowledge, and one developer. 

The initial setup of IBM Integration Bus was not complex. 

The product is usually very easy to deploy.

The product was only integrated with IBM servers. 

The initial setup is simple enough. Right now, in its entirety, the download is very simple. It's actually a one-click solution.

Deployment takes very little time. It depends mostly on the load and what we are pushing out. However, it usually takes a matter of seconds.

We have 14 people in general on our team using the solution, and they are all able to perform maintenance.

The implementation is straightforward. It's not complex. What takes a long time, however, is implementing the workflows or projects. That's where the efforts is. In terms of implementation, the implementation is straightforward. However, building the integration of workflows can be a bit tricky. 

You have to pick the right project as the first project, due to the fact that you're introducing a new product inside an organization. The first project is important in terms of setting the stage for understanding the underlying functionality. It shouldn't be too complex. At the same time, it should be impactful enough that you get management support going forward. It should be a project that is big enough whereby you can see the impact of the Integration Bus. 

The initial setup is straightforward.

Our installation is quite fast, but the process or the competition of user testing is what takes a longer time. Normally the user has to do a Tableau test, so it's not just the deployment. After the installation, they have to spend time to test.

The deployment is complex and you need to have an experienced administrator.

It has a moderate or medium-level complexity. The duration depends on the use case in terms of the number of services and workflows, but typically, doing installation and configuration is a matter of a few weeks.