We were using Apache Tomcat for server maintenance and deployments.

But we made a switch to IBM WebSphere. It offers greater flexibility and has superior features like LDAP integration and database connectivity compared to Apache Tomcat. That's why we switched.

I have worked with WebLogic, Apache Server, and SAP NetWeaver in the past. I've had a lot of experience.

No

This solution was already in place when I was hired, so I didn't have a choice.

A Microsoft solution that was used between 2006 and 2008. I believe it was based on a SharePoint platform. It really utilized the IIS together with standard HTML features, et cetera. It looked good, however, it didn't have the expandability for the other service modules that we wanted to use at the time to expand to true competitors bid. The IBM solution would have been the most comprehensive in terms of meeting the technical requirements. 

We were using WebLogic BL as our stack. Now we use an IBM Stack. It was about eight years ago when we switched, so we've been using IBM for a while now.

I used Oracle GlassFish and Apache Tomcat but found them good only for small applications. Also, they need a lot of XML configuration and are not really production-ready.

We used BEA WebLogic before using IBM WAS. The reason we switched was because of the licensing. BEA WebLogic has to be purchased separately, while IBM WAS base is part of the deal when you purchase IBM FileNet P8 Content Engine. Both products work fine by the way.