If we compare the solution with JBoss, WebLogic, and Tomcat, we can see that they are different and the installation is more difficult than Tomcat. Tomcat is relatively straightforward, but with IBM WebSphere Application Server, we need to follow the steps provided by the product team at IBM. Therefore, the installation is more difficult. We have to configure each level and install the server within 30 minutes. The deployment manager and installation manager are included in the solution. We must install the installation manager, followed by the IBM JDK, and then the product itself.

The initial setup is a bit complex, although management can be accomplished with ease once the initial environment has been set up. 

The initial setup is relatively easy to set up WebSphere Application Server. In our environment, it's mostly on-premises. We typically use silent installation via command line and a response file.

The deployment takes a few hours. The installation and setup itself don't take long. For active deployments, we automate the process using Jenkins pipelines and Ansible playbooks.

The installation is very complex.

The initial setup for IBM WebSphere Application Server is in the middle, meaning that it's not complicated, but you'll need some knowledge.

Normally, one person is enough from my side to deploy the solution, then another person from the customer side.

How long the full deployment of the IBM WebSphere Application Server takes would depend on various factors because it lies in the communication between the customer and the destination, so the solution is usually easy to deploy, but it could take days. Deployment is not difficult, but a common problem would be personnel availability or the person available to do the configuration.

It is complex. It is not something that you can do on your own without recourse to IBM. You need access and all the support and help from IBM for this. We need consultants who are proficient and IBM partners to do the setup. When you get the license from IBM, they have the recommended partners in a country to set it up. 

The tool's deployment is complex. The deployment takes three to four hours to complete. 

The initial setup was complex. We needed an expert WAS administrator. We took iterative steps to achieve higher efficiencies.

I set up everything. you just need the hardware, and I do everything else. 

The initial setup is relatively easy. The complete deployment time depends on the application. Some might take as little as eight hours, while others require more time.

The initials setup is not straightforward. It's quite complicated. An organization needs some pretty good experience. They need a high skill level.

For us, deployment took half a year.

The initial setup was very complex due to the complexity of the already existing business logics.

The initial setup is quite easy. You don't necessarily need to be a technical person. The configuration can be a little more demanding, but the initial installation is not difficult.

It wasn't easy, but nothing in IT is. The setup was pretty straightforward and any problems that I had, I was able to find the answers on the IBM Website.

The first deployment took about 18 months. That was in 2008. The upgrade took roughly six months, however, there were certain features and there was specific stuff we wanted that was never implemented. For example, the authentication system. While it uses our randomly generated 16 digit username, we wanted to do an alias for that system and we couldn't. I don't know what was the reason, however, it just couldn't be done. We've had issues as well with the file sizes being very bloated of using Blogger instead of any other optimized file storage mechanism. When the IBM deployment was contracted it used to run very smoothly. What we recognize now is that we're not set up properly and we're finding a lot of intricate complexities that we don't believe were necessary.

Depending on which platform you are on, the initial setup isn't too complex.

Currently, it is all straightforward, but it should be where the next generation of container-based, docker-based is and it's not there yet. Everyone wants that type of compatibility.

Deployment takes about two to three hours.

The installation is not straightforward and it can take three days.

The initial setup was straightforward.

I deployed it from scratch. It was not complex. It's easy to implement compared to other application servers. 

The implementation took eight hours. 

We require three engineers who do maintenance. We have an unlimited amount of users.

The initial setup is simple and takes under five minutes.

The initial setup is straightforward and, thanks to Java and its platform independency, it requires almost the same steps in all operating systems.

You just have to install IBM Installation Manager, define your repositories, and click Install or Update.

Initial setup is very simple. Just use the IBM Installation Manager and add the packages. The install wizard takes care of the rest. The only thing that can be difficult is to find the right packages on the IBM website, because of all the changes that IBM does on its website(s).

The initial setup of this solution is easy.