IBM CICS Transaction Server vs. Red Hat JBoss Enterprise Application Platform

IBM CICS Transaction Server is multi-decades proven transaction server which is very scalable, very secured, easy to use, has good transactional capabilities, works well all other mainframe resources such as Db2, languages on IBM mainframe, has access control capabilities in terms of who can access the transaction for read mode vs update mode, etc.

Incentivized

JBoss EAP is subscription based/open source platform. It's very reliable and great for deploying high transaction Java based enterprise applications. It integrates well with third party components like mod_cluster and supports popular Java EE web-based frameworks such as Spring, Angular JS, jQuery Mobile, and Google Web Toolkit.

Incentivized

• De facto standard in the legacy enterprise
• Multiplatform connection
• Native connection with DB2

Incentivized

• 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.

Incentivized

• Would like to see the transaction response matrix on the average transaction response among all requests.
• Would like to see GUI tool to be able to see currently running transactions
• Would like to be able to get the details of where the cics transaction was triggered from

Incentivized

• 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.

Incentivized

We are planning to migrate away from Jboss to Tomcat as Jboss has shown not interest in supporting OSGi which is heavily used at our shop

Incentivized

JBoss overall is easy to use. The installation and deployment of applications are quick. Documentations and support are also readily available.

Incentivized

Usually, Red Hat JBoss Enterprise Application Platform is good at performance and well suited for high traffic Java EE-based applications, but we have faced hard times performance tuning it for our specific needs. The product would be nicer if they would add a performance diagnostic and recommendations feature to it.

Incentivized

Fast response.

Incentivized

There is no comparison, in practice, the possibility of using the latest programming languages but, above all, the databases can be different and more modern than DL1.

Incentivized

We selected JBoss because of compatibility with EJB's. We currently are trying to reduce our footprint and will highly consider using Tomcat.

Incentivized

• It has allowed us to use our decades old code and still continue to support the business
• Allows us to have faster time to market and modernize our systems
• We can still continue to use our legacy resources for modern systems

Incentivized

• Improved delivery timelines due to easy out of the box setup.
• It is a cheap subscription-based/open-source Java EE-based application server. This reduces the overall cost of delivery.

Incentivized