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.
At the suggestion of the contractor (retailer), who has always entrusted us with the Internet environment, we set up this tower server. The CAL upgrade cost associated with upgrading the file server can be greatly reduced because the StrageServer operating system was given as a line. The operability of remote maintenance was also greatly improved by employing the associated management software (iRMC).
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.
The support system that more than makes up for it is the determining factor for the choice.
When a RAID disk or power supply failed, the maintenance service alerted me with a monitoring alarm and replaced it quickly before service was interrupted.
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.
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
With respect to the backup system, I believe that relocation after the replacement was facilitated.
The best solution to the problem was that thanks to Fujitsu Interstage I created a separate cloud to store the data for each individual PC.
Being able to continue the tasks, without the interruption of service due to a hardware failure that was fixed very efficiently, demonstrates the quality of this company's operations.
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.