Big elephant, need a horse
August 15, 2014

Big elephant, need a horse

Manoj Prasad | TrustRadius Reviewer
Score 3 out of 10
Vetted Review
Verified User

Software Version

Websphere Application Server

Modules Used

  • Websphere Application Server

Overall Satisfaction with IBM WebSphere

IBM Websphere Application Server 7.x is being used for deploying web applications using Liferay 6.1.2 a enterprise portal application
  • Robust application server
  • Good logging of various levels
  • Ability to create multiple nodes and clusters
  • Good documentation
  • Very nice WAS console interface
  • Ease of use in terms of deployment, give simple interface to do simple stuff like Tomcat, JBoss or GlassFish.
  • Takes long time to start the server.
  • The Liferay wars need to be decorated and then deployed. Perhaps we could simplify that.
  • Some of the concepts are good for complexity that WAS can handle but could be simplified and better documented, like concepts of well and profile, context, etc.
  • A Liferay war file created using Liferay Developer studio runs fine in Tomcat, however that may not run in WAS 7.x because it needs to be decorated. I had one war for a Liferay portlet with a simple cron job, and had hard time running to WAS server. It was running on the latest free download done on my friends m/c. Other times I have seen that there are issues running a war file that runs on Tomcat but runs on WAS after lot of customization for WAS.
  • The corporations like this however, the product may need better vibrant community of users where issues can be discussed.
  • Because of lack of ease of use, the time taken to deploy and run applications is high. That may be good job security but not fun as developer when you are trying to prove a solution. A sleeker simpler and lightweight solution would be appreciated.
  • Takes long time to learn deploy and adapt to the complexity and vast difference with other servers.
  • Negative impact on ROI in terms of more expertise needed may be compensated with more robust application that WAS offers.
  • tomcat,jboss,jetty,glassfish
I did not choose IBM WAS, it was a coporate decision. We are glad that we have been using this for a number of years and are quite happy as a corporation. However, it does take more time to learn WAS because of its complexity in terms of installation, various features and special deployment and packaging needs.
Ok to continue with increased usage and used to its various features.
It may be good for big corporates. It looks like a big heavy elephant with lots of features. However it's slower and more complex that its competitors like Tomcat, JBoss, etc.