While the initial setup is quite linear, it is not for everyone. I see people that often go into a panic. Usually, if they have a lack of experience in other fields, or in other integrated technologies, it makes them nervous. 

I am the team leader for the management of the product at the client. So, I represent my company to the client. We have a team of about six people that can handle deployment and maintenance.

It was quite easy to deploy. We deployed it around ten times, and it was a smooth process. 

The process depends on the complexity of the deployment. For simpler deployments, it can be done within seconds without any downtime. However, for some patches or changes in the product, it may require restarting the whole server, which can take some time. But overall, the deployment of an API takes just a second with no downtime.

The initial setup was straightforward. It was easy.

The initial setup is not difficult if you have prior experience.

I've worked with Versions 9 and 10, converted to Version 10, and now working with 11 and 12. It's a bit confusing between versions 10 and 11. Still, we made language transformations, such as using the compute node and MQ nodes, into web services that work easily in REST web services, MQ Web Services, and shared libraries. Shared libraries are significant because they have half our needed functions. I like Version 10 because it was really easy to work. 

Moreover, the deployment process depends on the requirements. If we consume only one service and the requirement is normal, then it takes only one day to deploy. We can get all the group requirements and deploy the service in Unity. If we want to plan for production, we can give them a timeline of one day.

The product's initial setup phase is straightforward. I rate the product's initial setup phase a seven on a scale of one to ten, where one is a difficult process, and ten is an easy process, if compared to the setup phases of other OEMs like IBM and TIBCO.

The solution is deployed on an on-premises model.

The solution can be deployed in a few months.

The initial setup is neither easy nor difficult, and the installer should have appropriate knowledge about the process. It took almost three days because I was new to the job and was researching the process.

I have worked with the infrastructure of the system in the cloud. We built a cluster with two or more computers and made it scalable and safe, making the machines visualized on the cloud using AWS.

The documentation is efficient. The deployment takes minutes in the production phase.

I rate the initial setup an eight out of ten, where one is difficult, and ten is easy.

The initial setup was straightforward. However, it took a few hours to deploy the solution.

The setup was straightforward and simple.

We found it difficult to handle integration. Other than that, it was easy. It only takes a few minutes to set up. It's very quick.

We did not have to worry about maintenance while we used it. 

I was not present at the company when it was implemented. I can't speak to how easy or difficult the process was. 

Maintenace can be an issue sometimes as the support hasn't been great. With a lack of external support, we can run into issues. 

On this solution, the installation is easy, however, customization, mostly due to the fact that there will be a good amount of customization and mediations, requires expertise. If the people who are implementing the solution have the right set of expertise they will be able to do it. If a novice user is attempting an implementation, they will need some training first.

The solution's initial setup process is straightforward.

The initial setup was straightforward. WSO2 Enterprise Integrator is not a complex piece of software. It's simple to handle and easy to manage.

We can deploy it in a day's time. We have done major deployments, so it doesn't take much time for us. 

The latest version remains very complex, although it's going to wizard. The information is very easy for handling the integration. The initial version we used had some complications but it's handled now. The deployment didn't take more than an hour. We only needed two people to implement the solution - an admin and a developer. For maintenance, we only need the admin.

The deployment took a few hours.