Securely connects distributed apps and services across public cloud, on-premises, and edge environments. Utilizing Infrastructure as Code, App Connect provisions resources and maintain uniform policies across multiple sites.
N/A
IBM WebSphere Hybrid Edition
Score 7.5 out of 10
N/A
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.
My advice is if your firm build multi-cloud, high availability SaaS products or you just run polyglot workloads across kubernetes and VMs, then F5 Distributed Cloud App Connect is your guy. Coming from an expert, just start with a few core services or else you will be overwhelmed.
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.
Ease of use - standing up a new site took very little time, less then an hour.
Connecting the dots - the ease at standing up a load balancer and advertising it on CEs was simple and straight forward. Once you get familiar with the field layout it's very comparable to BIG-IP
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.
At this point it has become too focal to our operations. An entire department could collapse if we dropped it now or in the near future. My experiences as mentioned in the previous questions tell of its gravity
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.
From what we have been able to test load/responsiveness is quick and when we've tested out reporting and troubleshooting modules they have pulled the correct information in quick timeframes. We haven't been able to test out any software integration with Splunk of other software on our system since we are still in early POC stages but from what we've been told we should be able to implement that in our environment
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!
-F5 Distributed Cloud App Connect provides more granular security policies with features like DOS, WAF etc and others lack -F5 Distributed Cloud App Connect provides high performance global network and other rely on public internet and impact is latency and it gives F5 Distributed Cloud App Connect a better user experience
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
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
