Question

Difference between tibco and oracle fusion middleware

Answer 1

1. The foundation of TIBCO's SOA technologies is ActiveMatrix set of technologies, anchored by Active Matrix BusinessWorks. TIBCO’s messaging system also plays in many SOA related deals, and consists of Rendezvous, a proprietary messaging system, and TIBCO EMS, which includes JMS support. TIBCO’s ActiveMatrix platform is very new and unproven in the integration space. There are likely fewer than 100 customers for products running on ActiveMatrix. Note that there are about 2,000 customers of Oracle BPEL PM.
2. TIBCO has two separate products that can be classified in the ESB space: ActiveMatrix Service Bus and ActiveMatrix BusinessWorks. There is no real upgrade path (i.e. one is not a subset of the other). This is problematic for users starting out with the lower cost ActiveMatrix Service Bus and upgrading. Both require the installation of the ActiveMatrix Service Grid, a proprietary set of containers that essentially provides similar services to Java containers. Please note this caution from Gartner: “ActiveMatrix is new (as compared with Java EE application servers), and does not have the track record of competing infrastructure products.”
3. Both ACTIVEMATRIX Service Bus and ACTIVEMATRIX BusinessWorks require the installation of the proprietary Rendezvous messaging system.
4. Service Grid is non-J2EE-based, so must set up duplicate distributed failover/clustering or interact with third party products.
5. ACTIVEMATRIX Service Bus provides basic mediation and routing, and transformation: there is no orchestration tool.
6. ACTIVEMATRIX Service Bus also lacks large-scale references and implementations at the present time.
7. ACTIVEMATRIX Service Bus does not have dynamic configuration capabilities: users must redesign and redeploy.
8. ACTIVEMATRIX BusinessWorks still has its own interface, and is not yet fully unified with BusinessStudio, TIBCO’s planned unifying development interface.
9. Models built with BusinessStudio cannot be implemented on BusinessWorks.
10. ACTIVEMATRIX BusinessWorks has problematic BPEL. TIBCO advertises BPEL support in BusinessWorks 5.7, however it is achieved in an unusual way. While TIBCO can run BPEL code, it creates “BPEL pallets,” which are compiled after constructing a process. However, the previous proprietary BUSINESSWORKS workflow is still supported as an option. This means TIBCO maintains dual infrastructures. Also, translation could have an effect on performance.
11. No references for BPEL use, as most users are using proprietary BUSINESSWORKS orchestration.
12. ACTIVEMATRIX BusinessWorks provides an older, heavyweight, “pre-SOA” EAI, integration broker style architecture. This is essentially unchanged with version 5.8, which runs on ACTIVEMATRIX. While services are supported, it lacks the kind of explicitly pre-built features such as service monitoring, throttling, and other items that pre suppose a services environment. This functionality and approach is present in Oracle Service Bus.
13. Oracle's Service Bus includes significant ease of use and configuration features for an ESB, including Web-based configuration, built in service monitoring, and “throttling,” not present in the heavyweight TIBCO ACTIVEMATRIX BusinessWorks or the still immature ActiveMatrix Service Bus product.
14. Oracle has a suite-based approach for SOA/integration, with numerous points of integration between the components of the suite and a single runtime. Oracle's suite-based product includes common installation, management and development tools, bringing down management costs. TIBCO, by comparison, does not have a suite-based approach, but instead promotes an EAI style Integrator Broker (BusinessWorks), and associated products that are sold separately. Even the various elements of ActiveMatrix are sold separately, and often have redundant tooling.
15. Oracle’s products are based on Java standards and run on a standards-based Java application server. TIBCO’s runtime and development technologies are non-Java and in fact, TIBCO promotes its ActiveMatrix proprietary container as the underlying platform.
16. Oracle’s SOA products have a foundation in WebLogic application infrastructure. This provides high end clustering, and availability, as well as advanced features such as Application Grid. TIBCO is not based on application server based clustering or availability.
17. TIBCO is missing key elements needed for integration/SOA, including a full-fledged IDE for service creation (instead it offers Eclipse plug-ins), an application server runtime, and an IDM product. In other areas, such as Rules and BAM, it has a weak solution with little presence among customers.
18. Oracle has a full range of security and authentication options, including services security (OWSM), and user based security and IDM. TIBCO has poor message based security and no real IDM.