WebSphere Hybrid Edition from IBM is a collection of WebSphere application runtimes and modernization tools that provides support for on-premise and major public cloud deployments, in virtual machines, containers and Kubernetes. The user can choose any WebSphere edition and deploy Liberty and application modernization tools to help move to a cloud-native architecture, modernize existing applications and support an existing WebSphere estate.
$88.50
per month
Microsoft Application Server (deprecated)
Score 7.3 out of 10
N/A
Application Server is an expanded server role in the Windows Server® 2008 operating system. It provided an integrated environment for deploying and running custom, server-based business applications. These applications respond to requests that arrive over the network from remote client computers or from other applications. Application Server is deprecated.
N/A
Oracle BPM Suite
Score 8.5 out of 10
N/A
The Oracle Business Process Management Suite is an integrated environment for developing, administering, and using business applications centered around business processes.
We did choose because of its dependability, speed, complex environment support, and ease of use. Microsoft Application Server is cheaper than IBM WebSphere Application Server and faster than WebSphere. Microsoft Application Server is a close competitor in terms of features, but …
Verified User
Administrator
Chose Microsoft Application Server (deprecated)
Microsoft Application Server was cheaper then what IBM WebSphere Application Server would have cost us. Also, our legacy applications run much faster on MS Application Server.
It has a similar feature to what Microsoft Application Server has but at a greater cost and also having to deal with another vendor when we could use a full Microsoft Stack for better training and support.
IBM WebSphere Hybrid edition is well-suited for the development and deployment of large enterprise-level applications such as Electronic Health Records that are used in our organization. IBM WebSphere is appropriate for organizations that require strong security and compliance as it provides a high level of security and compliance features. This works well with organizations that are subject to strict regulatory requirements, such as hospitals.
Microsoft Application Server has been incredible this past year during COVID. Previously I would have said that we could go without it, but after this past season, I’m glad we have utilized it. Without having this software set up prior to COVID, we would have been in a tough situation. I mention COVID a lot because we were able to continue our work almost seamlessly this entire year.
Oracle BPM is well suited to organizations and environments that have a good understanding of their business processes and organizational structures. Trying to introduce a tool such as Oracle BPM into the organization without a good grasp on how the business operates is a recipe for disaster as the implementation will uncover all of the dirty secrets of an organizations business processes and bring them to light. BPM is not to be utilized for smaller service orchestrations or technical service implementations, these should be handled by the Oracle SOA Suite using the BPEL process manager, leaving BPM to handle the organizational business processes, referring to and including lower level services and BPEL processes as needed.
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.
Oracle BPM is left behind by other tools more modern in terms of user experience, usability and ability to integrate with everything else.
To really harvest the potential of Oracle BPM you need to do it in JDeveloper and with ADF. This restricts its usage to very technical people.
The administration of the Oracle BPM tools has really put a burden on our team. It is running on Weblogic and we experience issues very often either with performance or with a bad configuration of the system.
As with all Oracle products, the price can be an issue for smaller shops.
Mostly we will be renewing unless the strategic direction changes drastically or there are other complelling external circumstances. We've been on a multi year project to modernize our legacy applications and that effort will continue for the foreseeable future.
WebSphere Application Server is used across our organization. Most projects use this for Java products and applications. Being robust and scalable makes it even more usable. We love using WebSphere Application Server due to its configuration management ability made simple and vast across all java related parameters. It is dependent on the features and upgrades and IBM releases some great upgrades to WebSphere Application Server.
I have found Microsoft Application Server to be incredibly easy to use. I have used dozens of similar programs and have always struggled to navigate through all the functions. So far I have been able to adapt and learn this software with ease. I rarely run into a problem that I wasn’t easily able to move forward on with a few tips.
IBM was quick to respond when we had an issue with our specific infrastructure. We raised a PMR, which they picked up quickly and updated us about every step of the way. We had an appropriate fix for quite a business critical issue within a fortnight, which was impressive!
Stability is one of the first things we consider when evaluating software. MS Application Server has been rock solid and has reduced the time that our IT staff dedicates to maintaining our legacy applications.
Cleo Integration Clould has many bells and whistles; however, when we added more maps and trading partners, it really slowed down. We found that the Cleo support was very slow to respond and there was a language barrier. IBM Websphere had better customer support and its processing was much faster than Cleo Integration Cloud
It has a similar feature to what Microsoft Application Server has but at a greater cost and also having to deal with another vendor when we could use a full Microsoft Stack for better training and support.
We evaluated Bonita and found that it might fit a smaller-sized company better; we found that Oracle BPM Suite scaled much more evenly. We almost went with one of the competitors, but in the end chose Oracle BPM Suite after we factored in the cost of VMware licensing. There are literally tons of analytics on the back end which are great for upper management, but not so much for average users, but this fits our business model quite well.
Continuous uptime of the business applications we manage
It's now much simpler for me to build and deploy cloud-native applications.
Because it can offload for me management and maintenance of the application server to IBM I can focus on the development, deployment and testing of the applications which is more important
Our ROI has been great since it has enabled our IT staff to have a central location to perform application updates which enables us to save time and money.
Deployment is very easy since the internal applications that required constant updating are now updated in one central location.
It's a lot easier to be within compliance protocols requirements.
You'll most certainly need a deep dive and extensive training before your users can even think of using the product and they are very expensive.
Lack of documentation makes it very difficult to manage the application if any error is encountered which will result in you ending up hiring a dedicated person to look into the application once it's deployed.
For a very large org., if properly implemented and used, it can help identify the cost-intensive and inefficient processes.
