IBM CICS (Customer Information Control System) is mixed-language application server that runs on IBM z/OS. CICS® Transaction Server, often called CICS, is used for hosting transactional enterprise applications in a hybrid architecture.
N/A
Red Hat JBoss EAP
Score 7.3 out of 10
N/A
N/A
N/A
Pricing
IBM CICS Transaction Server
Red Hat JBoss Enterprise Application Platform
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
IBM CICS Transaction Server
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 CICS Transaction Server
Red Hat JBoss Enterprise Application Platform
Considered Both Products
IBM CICS Transaction Server
Verified User
Anonymous
Chose IBM CICS Transaction Server
IBM CICS Transaction Server product works well in conjunction with IBM DB2 and they go together very well. Both are equally scalable and reliable products to use. They both can handle very large numbers of transactions and have been around for decades and stood for times and …
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.
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 …
We decided to use Red Hat JBoss EAP as it lowers our overall cost, supports all the features that we are looking for including clustering, distributed caching and web services. JBoss EAP is modular and has cloud-ready architecture.
JBoss does practically everything Apache Tomcat and Weblogic does in terms of our requirements, but JBoss is more suited for larger enterprise J2EE apps compared to Tomcat. Boot time is not as quick as Tomcat, but still relatively fast for our deployments. The system can also …
Jboss supports JEE standards and provides features like high availability, clustering, hot deployments, configurable features. you can quickly add or remove needed features and cut jboss footprint and reduce boot time.
The strengths of CICS are certainly the scalability. The multilevel architecture of the CICS regions, security, and performance, manages to manage large volumes of transactions with efficient performances.
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.
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.
IBM CICS Transaction Server product works well in conjunction with IBM Db2 and they go together very well. Both are equally scalable and reliable products to use. They both can handle very large numbers of transactions and have been around for decades and stood for times and have great experience by those who have used it.
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.