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.
It fits perfectly for SOA and EAI architecture with large numbers of services that required to be wired to each other, the binding virtualization is quite good to simply this part. For the simple scenario of orchestration and /or ESB architecture could be a better use traditional stack.
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
TIBCO service grid has been chosen as a natural selection of the TIBCO product evolution. The high flexibility and the binding virtualization fits very well with client needs for its EAI applications due to the huge number of services and applications, the management of application dependencies during deployment, the advantage of perfect integration with EMS for logging
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.
The integration of old BW with BWSE and its interface quite similar to design time has reduced the cost of training for developers
The TIBCO support for this product is no the best and clients complains too much about this. This required to find a workaround or force the client to move to new/or different product. Huge impact on ROI
