IBM Cloud Pak® for Applications (CP4Apps) is an end-to-end hybrid cloud application platform, providing flexibility for deployments, building new cloud-native applications, refactoring and re-platforming existing applications. Designed to leverage a collection of application runtimes, modernization tools and a Kubernetes container platform to adapt to their landscape needs.
N/A
Red Hat JBoss EAP
Score 7.4 out of 10
N/A
N/A
N/A
Pricing
IBM Cloud Pak for Applications
Red Hat JBoss Enterprise Application Platform
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
IBM Cloud Pak for Applications
Red Hat JBoss EAP
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
IBM Cloud Pak for Applications
Red Hat JBoss Enterprise Application Platform
Features
IBM Cloud Pak for Applications
Red Hat JBoss Enterprise Application Platform
Application Servers
Comparison of Application Servers features of Product A and Product B
IBM Cloud Pak for Applications is clearly suitable for modernizing the WebSphere runtime from the heavy, complex and expensive WAS-ND, and to a lesser extent WAS-base, to the super simple, fast and lightweight WebSphere Liberty runtime. I guarantee, once you start using Liberty you'll never look back. Enough cannot be said about how awesome Transformation Advisor is. The output analysis it produces, along with the migration plan and associated artifacts, considerably simplifies both the decision-making process surrounding modernization and subsequent implementation. Without TA we would've made bad decisions by blindly picking unsuitable apps for moving from WAS to Liberty. Using the results from TA we've excluded multiple WAS apps from our immediate plans to migrate to Liberty, saving time and effort that probably would have resulted in a failed migration. We recently used Transformation Advisor to help us successfully migrate an app from Tomcat to WebSphere Liberty. We needed to make some changes to the Tomcat app, but TA helped highlight these required changes. Without TA I'm not sure we would have succeeded.
Red Hat JBoss Enterprise Application Platform (JBoss EAP) is well suited for deploying high transaction Java EE based applications. It supports many popular Java EE web-based frameworks such as Spring, Angular JS, jQuery Mobile, and Google Web Toolkit.
MOD_CLUSTER integration. JBoss EAP integrates pretty well with mod_cluster. This is an intelligent load balancer especially useful in highly clustered environments.
Supports enterprise-grade features such as high availability clustering, distributed caching, messaging etc.
Supports deployment in on-premise, virtual and hybrid cloud environments.
While the licensing is considerably simplified than it used to be, I still find it somewhat confusing. For example, WebSphere Liberty Core has an 8:1 VPC ratio. This is clear when dealing with VMs but it is still not clear to me as to whether we get an 8:1 ratio when running on OpenShift or whether we need to purchase additional OpenShift licenses to support running WebSphere Liberty Core in OpenShift.
Not so much related to IBM Cloud Pak for Applications, but while Transformation Advisor is an indispensable tool to help modernize to the WebSphere Liberty runtime, I wish we could run it against WebSphere Liberty itself. The reason being, we are now using TA as a single repository for our configurations. TA also highlights many potential issues when migrating to Liberty; these issues may also be applicable for apps already running in Liberty, we just don't know it yet.
Jboss CLI is a great tool but we had trouble using it to get values that are displayed on Jboss GUI. It also has limitations parsing the applications.xml files and we had to use a mix of jboss-cli and linux bash commands to automate certain application administrative tasks.
JBoss doesn't really provides performance tuning recommendations. It would have been nice if it could learn from the current demand vs current settings for things like connection pool, server configurations, garbage collection etc.
Our customer mission-critical core banking applications like Temenos T24 run on best of the breed IBM WebSphere Application Server which is java based-application server. IBM has kept up the promise of providing support, fixpack, and any update. As far as I know, at least by 2030, IBM is committed to continue with WHE which gives customers confidence in their current investments.
WebSphere Application Server is propriety and increases project cost. It is slightly complicated to learn when compared to Jboss EAP. These were the two main reasons why we chose Red Hat JBoss EAP over WebSphere Application Server. Also, JBoss EAP is light weight and requires less server resource
Jboss EAP is easy to deploy and configure. This lead to lower cost and faster delivery.
Even though we have large number of machines running JBoss, we have only two Jboss Administrators. It doesn't requires too much administration and maintenance on daily basis and reduces number of administrators required for large implementations.
