Red Hat JBoss Enterprise Application Platform vs. TIBCO® BPM Enterprise

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

The scenario where TIBCO ActiveMatrix is well suited is in the scenario where there are more long-term business processes and in a complex corporate organization where there are many users with different privileges to perform actions on the same processes. It's less appropriate where there are no complex business process especially if the resubmit of the task in error is not required.

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

• TIBCO offers multiple ways to implement the sophisticated forms of event-driven BPM. It also balances the combination of business rules and AMX BPM for a different variety of IT Applications
• It depends on the Enterprise service bus which is message oriented middleware
• The integration of Spotfire with AMXBPM and BusinessEvents is a unique advantage

Incentivized

• Difficult to replicate configuration outside of a container environment
• Still requires quite a bit of knowledge of the CLI
• Integration with deployment tools requires CLI knowledge

Incentivized

• A little bit too conservative. Not really anything leading edge. [Tibco] has plenty of customers, and that means they will probably be around forever, but [product enhancements] seem to be more [abundant in competitor product offerings].
• It would be great to have some pre-defined themes. Pie chart labels - it would be great to get more options for sizing and placement.
• I find it hard to trust the online portal too much. I doubt the security that is offered by this software.

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

Such a BPM sw is amazing and usefull. You have a gret visibility in design and development phase.

Incentivized

JBoss EAP is lightweight and doesn't really consumes much physical resources. It's high performing and suites well for high transaction Java enterprise applications. The out of box performance settings are not really great and you will have to configure the settings to suite your environment to leverage it's full benefits.

Incentivized

Fast response.

Incentivized

Because our support team is always available also for development suggestions.

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

For BPM we looked at some IBM products suites, BPM Online, Oracle products and Pega Systems. The decision to go with AMX BPM was based on the evaluation by the software architect team and the cost of acquiring the TIBCO suites.

Incentivized

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

Incentivized

• In order to create a BPM management, you need to make a very solid data management model, which becomes very important in its reuse
• The business process is very often unconnected with the implementation logic and therefore plays in favor of the re-usability of the software
• Large customization at log level for which managing these tools can be handled minimizing effort

Incentivized