IBM WebSphere Application Server Reviews

It's scalable and very reliable.

The incredible support that we get from IBM is of primary importance, that I see, because anytime we have a problem, help is just a phone call away.

I'd like to see the ability to build clusters made a little bit easier. It is kind of a manual process right now and this would just help save time and reduce resources.

The process is only partially automated and still requires significant manual effort to complete the configuration of an operational WebSphere cluster.

We have yet to max out the IBM MQ cluster. We have not been able to find the limits of the scalability yet.

We have used the technical support several times, successfully. It was great.

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

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.

It's an awesome solution. Compared to everything else that's out there in the market right now, IBM MQ is hands down the best solution available and that's based on 40 years of IT experience.

Invest in training. It's a complex product, but once you learn how it works, it's fantastic.

Reliability and the use of cutting-edge technology are important factors while selecting a vendor. Everything that's already in IBM MQ is state-of-the-art technology.

This solution is part of an enterprise web presence. It integrates well with the Tivoli Federated Identity Management system, which works as a single sign-on mechanism for other e-services that we have shared with other clients. They utilize some of our authentication engines and they provided access for their users back into their system, however, the presentation and the web presence for it comes on the WebSphere portal solution.

We've had so many challenges with the solution in the last two years that it's a bit difficult to find highlights.

It does integrate well with the Tivoli Federated Identity Management system.

I'm not certain if the WebSphere solution was deployed by IBM. There are a lot of complexities in how the solution was actually built and deployed, which means troubleshooting on management for us is pretty difficult. 

One of the biggest issues that we've had is there are certain features that we required that were hardcoded into the solution itself. When you manage them for making any architectural or solution changes, it becomes very difficult and near impossible to do. With respect to that, we tried to change the SSL certificate that would be in use, and because of how we tried to change the SSL certificate, we tried to change the DNS mover that it was pointing to.

There were hardcoded elements in the solution that didn't make it very easy for us. At the end of the day, we just kind-of renewed whatever services that we had already ongoing with it, which was a duplicate payment with what we had from other sources. We couldn't take advantage of the shared resources that we had before. We now have to maintain it as an isolated instance.

Based on the field and based on the build that was provided, we've noticed a lot of constraints in terms of the performance now.

Due to GDPR and other issues, not everybody is able to utilize cloud services. That's something that people need to be aware of. The company needs to be clear on the business use case and how they need to maintain compliance with its policies and regulations. Some of the feature sets that we found a little lacking in this particular solution. By now they've probably changed the ability to embed and utilize the rich media content and web presence. 

Our site is basically little image JPEGs, and that's it. We have low embedded video. We have low dynamic speech response for mobile viewing, we have low integration or extension for mobile apps. We have low integration as well as for dynamic content of bits from other sites. For some of our clients who wish to display information on our website, we actually have to lift the content, reform our tips, and recreate it into the content management engine.

We first did a deployment back in 2008. It was an enterprise deployment where we wanted to get modules for forms and themes and gateways, especially an SMS Gateway. We needed to have different services. The IBM WebSphere solution was the only one at the time that was able to provide a full suite solution. 

We upgraded in 2014 and since then, we've kind of continued to utilize the service. In 2017 it became a bit cost-prohibitive for us to maintain all the different levels of support on it. We've just kind of been getting by with some third party support services and reactive support services.

Since we've been monitoring it directly ourselves, we've found that there has been an increase in the number of failures. The failures result in deadlock processes that generate very little to no troubleshooting logs. A lot of time we find ourselves just really staffing services to get these solutions to market in our online space. Reviewing logs to get the root cause and drilling down into something more definitive so that we could enable resolutions that are more permanent, that has been absent, basically.

When we exited the contracts, IBM did an audit of the solution and there were licensing entitlements that we had no information about. The products themselves could only run on specific servers of specific configurations, which we worked at up until the audit was done. 

The scalability in terms of company full storage looks fine. What we've realized is that the DB2 disappears, as there is an amendment and build. Therefore the IBM DB2 database has been less than optimal as we've grown over the last two to three years. And we've started to see this as a little more of a challenge, in terms of the configuration for the build as well. It doesn't support the groups. The license entitlement rarely gives us a bare minimum for the capacity to process what we have now. So the scalability of the solution is very limited.

The scalability for the solution was supposed to be for about 800,000 users. We just coming up on 100,000 and we're already seeing performance issues.

We have roughly 100,000 users and the majority of them would be using the single sign-on service to access our client services. We have probably about 20 to 30 persons who deal with user administration and content of this onsite maintenance and management in terms of web posts, et cetera.

The rest of them are really just users - either web browser users or users of the single sign-on.

The documentation around the product is not very clear, even post-implementation. IBM just basically cut us off and whatever we had was what we had. They weren't going to offer us anything. If we found gaps in the configurations or the documents, and we asked for the other stored information, nothing was forthcoming. IBM was actually very dependent on a third-party provider. There were a few instances where IBM directly handled either an implementation or configuration aspects. A lot of it was actually passed on to a third-party provider, who was the person that we used to know. A very small fraction of the price was what we were paying to IBM, in fact.

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. 

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.

We used to pay about $100,000-$120,000 US or somewhere around there. That was a bit cost-prohibitive for us to continue.

You need to pay for both software licenses and software support, which was the IBM backline. There were two levels of support for software and software bots. We had hardware support, which was separate, and we had to proactively monitor service maintenance support as well.

The solution that we have now, one of the challenges we have is with the WebSphere portal. The WebSphere application and WebSphere content management software are no longer IBM products. IBM would have sold it off to ETL back in 2018 or 2019. Maintaining that as a full end to end IBM solution has become very difficult. They basically have a hands-off approach now. Anybody who's using this needs to be aware of what is available to them by way of manufacturer support and then other support. The licensing entitlements for the product need to be very carefully understood. There are limitations to the hardware configuration that goes together with the implementation.

The other thing is that we've recognized that there are few resources that have the experience and capability of monitoring this system. If you are going to deploy it, you should ensure that you either have strong and continued backline support with your vendors or third party managers or that your in-house team is well skilled in order to monitor and maintain everything and administer the system. If you can get to a point where the build, implementation, and commissioning could be done in house, that will give you a lot more visibility to all the different elements of the solution and how they integrate and interoperate so that it makes the management on troubleshooting a lot easier. 

I'm biased due to my previous experiences. My experiences are really more influenced by the build and not necessarily the product as a standalone product. 

I would rate the solution at a three out of ten.

We have some services which are doubled up using Java. To deploy this research we are using the WebSphere Application Server. A lot of channel applications are consuming these services in particular.

The solution is robust. The connection management and the scalability, which IBM provides to the Stack, are also valuable.

Nowadays the industry is moving towards a more open-source operating framework.

The cost factor is huge. It's very pricey compared to other open-source stacks. In the future, we'll deal with the IBM Stack so we might move to a compact server and other open-source alternatives which are comparatively less in terms of cost.

They should make the solution more lightweight and not bundle everything into a single product.

The solution would benefit from having a different licensing model.

I've been using the solution for 12 to 14 years.

The solution's scalability is good, but there is a cost factor, which is a disappointing element. If you want to go for another node then you have to go pull up that code license model, and that produces another licensing cost.

We've reached out to technical support. I find them good, but not excellent. They aren't very quick to respond.

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.

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.

We have our in-house team who are trained in the deployment of IBM WebSphere Application Servers, so we didn't need outside assistance. 

The solution is very expensive compared to an open-source stack.

The solution is deployed in the UX operating system.

Although the solution is good, open-source options keep getting better and better, so I'd recommend others to look into that. This solution is expensive. So is Oracle. I find open-source more innovative and they often have a good community around them that offers helpful support.

I'd rate the solution seven out of ten. I'd rate it higher, but there are basic features that have minimum capabilities that can be very dissatisfying. Apart from that, they provide good support, offer a good clustering model that's reliable, and it's properly tested with certified code.

We use IBM WebSphere Application Server in the financial industry for applications.

The solution has good performance.

The solution could improve the integration.

I have been using BM WebSphere Application Server for a few years.

The solution is stable.

I have found the solution to be scalable.

We have approximately 1,000 users using this solution in my organization.

The technical support from IBM is very good and responsive.

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

We use approximately four technicians for the implementation and maintenance of the solution.

The price of IBM WebSphere Application Server could be less expensive and there is an annual license required for this solution.

I recommend this solution to others.

I rate BM WebSphere Application Server an eight out of ten.

The most valuable features are its user-friendliness and reliability in terms of application hosting.

The licensing could be improved, and I would like it to give the longevity of the lifespan of the visions. In the next release, I would like to be able to download and extract the files so that I can just use my application server. 

I have been using this solution for fifteen years.

This is a scalable product.

Technical support is available instantly.

The initial setup was straightforward.

I would rate this solution as eight out of ten.

We use it as a gateway for our payment application. It receives requests and processes it. 

The most valuable feature is the configuration of the application server. It has a variety of configuration database certificates and connection pools. It has good stability of the application server in the long term compared to other solutions. 

It should be able to serve more concurrent requests like Oracle. Oracle has more powerful stability, availability, and real-time serving. 

WebSphere is not light enough to implement high available applications like gateways. But WebSphere has more configuration abilities and customizability.  

I have been using it for three months. 

Stability is frustrating. It goes down after a specific number of user connections. It does not have high availability. 

I have contacted their technical support. They offer good help to help resolve the issue. They were efficient and helpful. They have good documentation. 

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.

There aren't any additional costs besides for the standard licensing. 

I would rate it an eight out of ten. 

It has a sensitive implementation. If you do a wrong step, it will destroy the whole thing and you will need to start from scratch. 

WebSphere Application Server's best features include the data subscription and connection viewer. 

WebSphere Application Server doesn't have an automated deployment option, forcing us to use third-party tools like Jenkins UCD and Palo Automated Deployment. In the next release, IBM should invest in automated deployment instead of complex building integration with different tools.

I've been using WebSphere Application Server for almost twelve years.

WebSphere Application Server is very stable.

WebSphere Application Server is scalable.

The initial setup is simple and takes under five minutes.

WebSphere Application Server is expensive, so it may not be a good option for small companies.

I would give WebSphere Application Server a rating of nine out of ten.

We use IBM WAS Developer Edition in our development machines for free.

There is an Eclipse Plugin provided by IBM, so no need to buy IBM Rational Application Developer or Rational Software Architect tools.

Starting with version 8, WAS provides a special folder called monitor deployment. Once you put the .war or .ear file in there, it is deployed automatically without human intervention. This greatly helps us in our continuous integration server. Once the deployment binary is ready, we write a script to copy it to that folder and then, voila! The application is up and running and accessible from its context root.

• Stability: Once you deploy your application, it will be very stable with no issues at all.
• Ease of administration: It has an Integrated Solutions Console, what we call the administrative console, with very detailed configurations and Help pages for each configurable item.
• Up to date: Once a security vulnerability has been discovered, IBM patches it quickly, and later includes it in a bigger fix or update.
• Security: It is compatible with the latest Java 8 security features, supports FIPS 140-2 and NIST SP 800-53 with strong ciphers and cryptography keys, and supports TLS 1.2 completely. Also, configuring client and server certificates is relatively easy.

IBM needs to pay attention to market changes more quickly. We now have Java 9 and very soon Java EE8. We do not want to wait for two or three years after their release until they are supported by the new version, say WAS 10 in our case.

Installing or configuring a WAS server instance as a Windows Service causes a lot of problems, especially when the server needs credentials to stop.

No stability issues at all.

No scalability issues at all.

Very good.

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.

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.

If your application is just a web app that does not need to scale big, you can obtain a single core license of WAS Express edition, which has almost the same features with limited processing cores.

If you manage a very big application farm (i.e. need to run 10 or more WAS servers) it is better to get IBM WAS Hypervisor Edition.

I evaluated Red Hat JBoss EAP, but since we need to integrate with IBM MQ and the IBM Integration Bus, all in a mixed Windows/AIX environment, we found that IBM WAS was the winner.

IBM products, in general, need a lot of experience. They are very similar, have much in common, but to avoid getting into trouble and strange issues, it's important to read within the IBM Knowledge Center before starting. Also, do not skip any step in the installation/migration/configuration section, as it may stop you later, even without your knowing it.