Understanding of application development concepts in ESB due to the easy application of concepts within the tools. Understanding of application development concepts in ESB due to the easy application of concepts within the tools. The almost zero administration of the tool that contributes to almost 99% of service availability and easy integration with third-party applications. Versatility for design and development of customized frameworks in an agile way due to the diversity of prefabricated components that are included in the Enterprise Service Bus. The development of support packages either by IBM or by the community is of great help when implementing or obtaining specific features such as traces, quick statistics on the behavior of the integrations and evaluation of resources based on work load.

Highly scalable High availability in hardware and software mode Easy maintenance Simple and easy-to-use development tools

Limited web console Managed security in operating system and not in application layer Desktop tools for administration very poorly optimized Poor emphasis on JCA standards

Very good performance and customization of the different server processes. A cloud deployment would be great to reduce the cost burden.

Great control center for managing the different server configuration such as setting port numbers, users and authentication, Servlet auto reloading, etc. Excellent performance even on Virtual machines. Easy loading process of application/library WAR and JAR files. A great complete implementation of the J2EE platform. Used it mainly for testing secure SSL channels with JSPs and Servlets. Very customizable and performance efficient.

The cost is a major concern. With cloud integration by IBM this would be more manageable. Not much more features than that provided by Apache Tomcat or the J2EE Glassfish reference implementation. Definitely better performance with specific tuning of the JVM, but still the cost is a major factor.

I would recommend to anyone to really think do they really need IBM WebSphere or if their business problem could be solved using some other (more stable and cheaper) options.

I have been using IBM WebSphere Application Server and Portal for a long time, and it does come with tons of options and integration features, which is great for big enterprise systems.

I've had many issues with it - official docs are really bad, the community is small and it is hard even to describe some problems you experience, and it takes more time to learn than other options available. And since not many people are familiar with it, it is sometimes not easy to find a good engineer to support it.

Generally using IBM WebSphere application server for building, deploying and running an java applications.Also it's maintenance is easy, also we are currently moving our applications to cloud so WebSphere helped us without much problems. I would say for java applications and security wise it's a great tool in the market.Our organisation is big so we were looking for such kind of tool only. It solves a problem of integration of front end and backend. Recommended tool

IBM WebSphere Application Server allows to integrate with other WebSphere tools easily and quickly. It is the oldest application running server to deploy or host java applications mostly, Also the documentation provided by IBM is pretty easy to understand and implement, customer support is also good. The best thing about it is it supports both on prem as well as cloud.

Cost is bit hight for IBM WebSphere application server so it is suitable for banking or big companies. Also if it provides videos along with documents then it will be helpful to beginners. Sometimes it tooks time to start the server.

You will always be able to accomplish what you need to with WebSphere, but be prepared to learn! Also, take all tutorials with a grain of salt. Things have changed drastically between versions and also depending on who's doing the video. Some people take shortcuts that may impact (or may not) what you're trying to accomplish.

WebSphere has support for nearly any type of web server you need. While we've mainly used WebSphere Application Servers to run Maximo and related 3rd party applications, we've also tested using Tomcat, Liberty, and other server options/configurations with great success. Control is handled nicely from a web-based dashboard.

There is a steep learning curve to configuring WebSphere even for a simple use. If you're already familiar with basic web servers (such as Apache Tomcat), you'll be able to get a basic server set up and running fairly quickly, but as soon as you need any additional functionality, it can often take a long time to figure out how to accomplish it in the web-based UI. While guides abound for just about any functionality, there is always multiple ways to do it that seem to conflict with each other at times. The web-based UI is really just executing some .bat files on the backend, and if you learn those, you can accomplish certain tasks much quicker. Unfortunately, it seems like a lot of trial & error is the only way to learn.