Page 1

TIBCO Summary & BEA Co-exist Strategy Technical White Paper March 24, 2004

Abstract This document provides an overview of TIBCO products and does a high-level comparison with appropriate BEA products. It also attempts to provide a joint BEA-TIBCO co-exist strategy and BEA Platform advantages. This paper was originally intended for EDS and is for BEA internal use only.

Sudhrity Mondal TSG – Alliances BEA Systems Inc., 2315 North First Street, San Jose, CA 95131 smondal@bea.com

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 0


TIBCO Summary & BEA Co-exist Strategy Abstract ..................................................................................................................................................... 0 Acknowledgements ................................................................................................................................... 3 1

TIBCO COMPANY OVERVIEW ................................................................................................................... 4

2

TIBCO PRODUCT SUITE .......................................................................................................................... 6 2.1 TIBCO Enterprise for JMS.............................................................................................................. 7 2.2 TIBCO Rendezvous........................................................................................................................ 8 2.3 TIBCO SmartSockets ..................................................................................................................... 9 2.4 TIBCO SmartPGM & SMARTPGM FX ........................................................................................... 9 2.5 TIBCO Hawk................................................................................................................................. 10 2.6 TIBCO BusinessWorks EMInsight................................................................................................ 11 2.7 TIBCO Adapters ........................................................................................................................... 11 2.7.1 Horizontal Applications and Technologies ............................................................................ 12 2.7.2 Transport Technologies......................................................................................................... 13 2.7.3 Vertical Technologies ............................................................................................................ 13 2.8 TIBCO BusinessConnect.............................................................................................................. 15 2.9 TIBCO BusinessPartner ............................................................................................................... 17 2.10 TIBCO PartnerExpress ............................................................................................................. 18 2.11 TIBCO BusinessWorks ............................................................................................................. 18 2.12 TIBCO BusinessWorks Workflow ............................................................................................. 20 2.13 TIBCO SubStation ES............................................................................................................... 20 2.14 TIBCO BusinessWorks SmartMapper ...................................................................................... 20 2.15 TIBCO TurboXML ..................................................................................................................... 20 2.16 TIBCO XMLValidate.................................................................................................................. 20 2.17 TIBCO XMLTransform .............................................................................................................. 21 2.18 TIBCO XML Canon/Developer.................................................................................................. 21 2.19 TIBCO UAN Solutions............................................................................................................... 21 2.20 TIBCO PortalBuilder ................................................................................................................. 21 2.21 TIBCO PortalPACKS ................................................................................................................ 23 2.22 TIBCO BusinessFactor ............................................................................................................. 23

3

TIBCO PRODUCT SUITE – STRENGTH & WEAKNESSES ........................................................................... 24 3.1 TIBCO Strength and Weaknesess ............................................................................................... 24 3.2 TIBCO Summary .......................................................................................................................... 28

4

TIBCO & BEA PRODUCT COMPARISONS ............................................................................................... 29 4.1 TIBCO Rendezvous and BEA JMS .............................................................................................. 29 4.2 BusinessWorks/ Integration Manager and BEA WLI.................................................................... 29 4.3 TIBCO Adapters and BEA WLI / JCA........................................................................................... 30 4.4 TIBCO Hawk and BEA WLI / WLS ............................................................................................... 31 4.5 TIBCO Repository and WLI Repository........................................................................................ 32 4.6 TIBCO BusinessConnect and WLI B2B ....................................................................................... 32 4.7 TIBCO BusinessPartner and BEA BusinessConnect................................................................... 32 4.8 TIBCO PartnerExpress and WLI Zero-weight Client .................................................................... 33 4.9 TIBCO PortalBuilder and WebLogic Portal .................................................................................. 33 4.10 Summary................................................................................................................................... 34

5

WORKING WITH TIBCO – RECOMMENDED STRATEGY & ARCHITECTURE .................................................. 35 5.1 Service Oriented Architecture for Enterprise................................................................................ 35 5.2 Enterprise Technology Components provided by TIBCO & BEA................................................. 37 5.3 Recommended Product Strategy for EDS.................................................................................... 38 5.4 High-Level UseCases for TIBCO, BEA ImplementationS ............................................................ 39 5.4.1 Publish Stock Quotes ............................................................................................................ 39 5.4.2 Order Processing .................................................................................................................. 41 5.4.3 Joint BEA – TIBCO Use Case Scenarios.............................................................................. 43 5.5 BEA – TIBCO Integration ............................................................................................................. 46 5.5.1 JMS Bridge ............................................................................................................................ 46

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 1


TIBCO Summary & BEA Co-exist Strategy 5.5.2 Conexus Control for Tibco..................................................................................................... 46 5.5.3 WebServices ......................................................................................................................... 47 5.6 The BEA Platform Advantage....................................................................................................... 48

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 2


TIBCO Summary & BEA Co-exist Strategy Acknowledgements The information provided in this paper is based on public information provided at TIBCO website, documentation from Doculabs, my study of TIBCO products, BEA TRIP, and other publicly available information on TIBCO in the World Wide Web. Information provided here is for a high level understanding only. For up to date and detailed information on TIBCO products, please visit TIBCO at www.tibco.com. I would like to acknowledge and express gratitude for information, feedback and support that I received from discussions with Dean Hidalco, Fausto Ibarra, Jayesh Shah, Dave Ressler, Charlie Parker and Sushil Shukla. This paper is a concise collection of information obtained from various sources.

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 3


TIBCO Summary & BEA Co-exist Strategy 1

TIBCO Company Overview Item

Description

Corporate

Founded in 1985 as Teknekron Software Systems. Products included Teknekron Information Bus (TIB) to provide organized dissemination and integration of data using an information-oriented model, rather than the connection-oriented model prevalent at the time. This model depended upon each connecting system, working in conjunction with TIB software called Rendezvous, being entirely responsible for the sending and receiving of data across the network. The Teknekron Information Bus information-oriented model first introduced two key TIB features still in use today: self-describing data and subject-based addressing. Acquired by Reuters in 1994. In 1997, TIBCO was incorporated as an independent entity and established headquarters in Palo Alto, California.

Acquisitions

In October of 1999, TIBCO acquired the Inconcert workflow unit from Xerox, and re-branded it as TIB/InConcert, adding workflow functionality to the Integration Manager business process management toolkit. In April 2002, TIBCO acquired competitor Talarian to increase market share in the messaging-oriented middleware market, where it has traditionally suffered against IBM MQSeries. Later TIBCO acquired Praja adding BAM functionality to their product suite.

Products Groupings Today

Enterprise Backbone, provides the messaging framework for TIBCO. Business Integration is designed for Enterprise Application Integration and Business Process management. Business Optimization provides portal and business activity monitoring capabilities.

Market Share

TIBCO shares the integration market primarily with webMethods, with both companies commanding 34% market share. TIBCO is approximately even in the Application Integration space, and webMethods has the edge in the Business-to-business space.

Finances

TIBCO follows a fiscal year calendar that begins on December 1 of each year. Fiscal quarters (ending February 28, May 31, August 31, and November 31) mark periods of aggressive sales activity. TIBCO’s revenue for 2003 was $264 million and has assets worth $943 million.

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 4


TIBCO Summary & BEA Co-exist Strategy Industry Focus

Manufacturing

Telecom

Energy

Financial

Healthcare

Logistics

Compaq

AT&T

Chevron

ABN

Amgen

Delta Air Lines

Gateway

BT Cellnet

Equiva

AMRO

Northwest

Hitachi

Ericsson

Exxon Mobil

BankBoston

Catholic Healthcare West

Lucent Motorola NEC

Hutchison 3G Qwest Sprint

Mirant Pan Canadian Energy Services

Philips

Telstra

Reliant Energy

Pirelli

Vodafone

Shell Energy

Procter Gamble

Worldcom

Texaco Natural Gas

Seagate Siemens/Infineon Sony Toshiba

Williams Energy

Charles Schwab Chase Manhattan Credit Suisse First Boston Deutsche Bank

Bayer Foundation Health GlaxoSmithKline

SAS TNT Logistics FedEx Air Canada

Health Net UCB

Goldman Sachs HSBC Lehman Brothers Merrill Lynch Morgan Stanley NASDAQ Nomura Salomon Smith Barney

Tibco Partnership Programme

24-Mar-2004

The TIBCO Alliance Partner (TAP) program is a paid membership program TIBCO requires of all of its partners, regardless as to their category or level. The TAP program provides partners with access to TIBCO software, education, and joint marketing opportunities. TIBCO maintains alliances with over 130 firms, including systems integration partners, technology (development) partners, channel (resale or embedded) partners, as well as hardware partners. Key SI partners include Accenture, Braxton, and BearingPoint.

Confidential - BEA Systems, Inc.

Page 5


TIBCO Summary & BEA Co-exist Strategy 2

TIBCO Product Suite

The TIBCO product suite is categorized into the following categories and sub-categories as listed in Table 2.1.

TIBCO Product

Sub-Category

TIBCO Products

Category Enterprise Backbone

Messaging Solutions

Monitoring & Management Business Integration

Application Integration B2B Integration Process Management Mainframe Integration

Data & Metadata Management

Business Optimization

UAN Portal Business Activity Monitoring

TIBCO Enterprise for JMS TIBCO Rendezvous TIBCO SmartSockets TIBCO SmartPGM TIBCO SmartPGM FX TIBCO Hawk TIBCO BusinessWorks EMInsight TIBCO BusinessWorks TIBCO Adapters TIBCO BusinessConnect TIBCO BusinessPartner TIBCO PartnerExpress TIBCO BusinessWorks TIBCO BusinessWorks Workflow TIBCO Substation ES TIBCO Rendezvous for OS/390 and AS/400 TIBCO Adapters for CICS, Files for OS/390 and AS/400, and Adapter for DB2 TIBCO BusinessWorks SmartMapper TIBCO TurboXML TIBCO XMLValidate TIBCO XMLTransform TIBCO XMLCanon/Developer TIBCO UAN Solutions TIBCO PortalBuilder TIBCO PortalPacks TIBCO Portal Partners TIBCO BusinessFactor

Table 2.1 A high level view of these products is shown in Figure 2.1

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 6


TIBCO Summary & BEA Co-exist Strategy

Figure 2.1 – TIBCO Product Suite The TIBCO products are described briefly in the following sections. 2.1

TIBCO ENTERPRISE FOR JMS

TIBCO Enterprise™ for JMS software also known as TIBCO Enterprise Message Service is a highperformance and extremely robust implementation of JMS. Enterprise for JMS employs a store-andforward architecture, and supports both queue-based and publish/subscribe messaging, local messaging transactions (in which multiple messages may be sent or consumed as an atomic unit of work), message selectors. Features of TIBCO Enterprise Message Service include: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦

Full support for Sun's JMS 1.1 specification. Full support for native and 3rd-party JNDI (Java Naming and Directory Interface). C-based server for high throughput and transient peak messaging. Lightweight pure-Java client library for maximum compatibility. Additional C and C# clients are available for expanded integration capabilities. Support for XA transaction management in both the JMS and C clients. Superior scalability and fault-tolerance via server clustering and routing, as well as run-time message tracking and support for undelivered queues. Powerful administration capabilities including fine-grained user authorization, destination access controls, redelivery policies, and undelivered queues. Support for external LDAP user authentication and group information. Detailed run-time monitoring facilities, extensive server tracing capabilities, and advanced server log file management. Secure messaging with full support for SSL, including client-to-server and server-to-server connectivity and support for external SSL accelerators.

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 7


TIBCO Summary & BEA Co-exist Strategy ♦ ♦

2.2

Advanced messaging semantics via server-based destination bridging. Seamless bi-directional connectivity with TIBCO Rendezvous, including support for certified messaging, interoperability with leading application servers, and integration with TIBCO's entire range of business integration and management solutions.

TIBCO RENDEZVOUS

TIBCO Rendezvous™ messaging software is the industry leading proven mission-critical real-time publish/subscribe event-driven messaging infrastructure.

Figure 2.2 – TIBCO Rendezvous

Features of TIBCO Rendezvous include: ♦

♦ ♦ ♦ ♦ ♦ ♦

Building block for the entire TIBCO suite of products. All TIBCO products utilize Rendezvous first before going to any other messaging medium. This includes TIBCO Enterprise for JMS. The TIB/Rendezvous daemon (rvd) represents the messaging infrastructure for all of the TIBCO products. A distributed collection of Rendezvous daemons creates the TIBCO Information Bus, known as the TIB. Each rvd communicates with the others via messages broadcast to network peers. Subject-based addressing is the key to communications between applications in any TIB-based system. Rather than addressing a message to a specific listener’s IP address or other listenerspecific identifier, Rendezvous messages are associated with a specific subject line and sent to all listeners on the network. The listening components of a TIB-based system may choose to act upon a message based upon the contents of the subject line. Every Rendezvous message consists of self-describing data, referring to a bundle containing the message itself and descriptive information about the message. Messaging models: Broadcast (Pub/Sub, Request/Reply, Point-to-point) TIB/Rendezvous makes use of the TIBCO Reliable Data Protocol (TRDP) and Rendezvous Certified Messaging (RVCM) to make UDP broadcasts (64kb) more reliable. QOS - Reliable (TRDP), Certified (RVCM), Transactional delivery (RVTX) Comprises two primary components: ƒ TIB/Rendezvous API (C, C++, COM, Java) ƒ TIB/Rendezvous daemon TIBCO applications and adapters utilize the TIB API to communicate within the network. Load Balancing and Fault Tolerance is achieved via Rendezvous Distributed Queue

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 8


TIBCO Summary & BEA Co-exist Strategy

Figure 2.3 – TIBCO Rendezvous Administration Console

2.3

TIBCO SMARTSOCKETS

TIBCO SmartSockets™ provides reliable real-time messaging using industry-standard protocols with exceptional performance, scalability, bandwidth efficiency, and fault tolerance. Using TIBCO SmartSockets application programming interfaces (APIs) and class libraries, applications can distribute and exchange information quickly, reliably and securely across any platform and any network-LAN, WAN, Internet or satellite.

2.4

TIBCO SMARTPGM & SMARTPGM FX

TIBCO SmartPGM provides a highly robust, reliable, scalable, and standards-based solution for one-tomany and many-to-many content and data delivery over existing LAN, WAN, and satellite topologies. TIBCO SmartPGM addresses all reliable multicast needs today by providing congestion control and bandwidth management, three different types of error correction, and compliance with the multicast standard backed by industry giants Cisco and Nortel.

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 9


TIBCO Summary & BEA Co-exist Strategy TIBCO SmartPGM FX is a powerful content distribution product built on top of TIBCO SmartPGM. Optimized for LAN, WAN, and satellite environments, it provides efficient and reliable delivery of mediarich content to thousands of simultaneous receivers, regardless of data or network type. 2.5

TIBCO HAWK

TIBCO Hawk™ is a tool for monitoring and managing distributed applications and systems throughout the enterprise. With Hawk, system administrators can monitor application parameters, behavior, and loading activities for all nodes in a local or wide-area network and take action when pre-defined conditions occur. In many cases, runtime failures or slowdowns can be repaired automatically within seconds of their discovery, reducing unscheduled outages and slowdowns of critical business systems.

Figure 2.4 – TIBCO Hawk

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 10


TIBCO Summary & BEA Co-exist Strategy

Figure 2.5 – TIBCO Hawk Console

2.6

TIBCO BUSINESSWORKS EMINSIGHT

TIBCO® BusinessWorks EMInsight works with Enterprise Management platforms to give administrators and business managers complete insight into system, network, application and process data. By doing so, TIBCO BusinessWorks EMInsight gives them the ability to identify problems as they arise, analyze them in context of the impact they are likely to have across the organization, and address them before they impact customers.

2.7

TIBCO ADAPTERS

TIBCO Adapters™ enable packaged applications, databases and networking technologies to become active participants in the enterprise information flow. Adapters provide a configuration-based approach to integration, providing simple, automated mapping of incompatible technologies and data formats.

The list of adapters that TIBCO provides is provided in the following sections.

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 11


TIBCO Summary & BEA Co-exist Strategy 2.7.1

Horizontal Applications and Technologies

Collaboration

Miscellaneous

- eRoom - Webex

- @TheMoment - Consilient - Katmango - Lotus Notes - Mongoose - Tuxedo - Verity

Configurators - Calico - Selectica

Content Management - Interwoven - Documentum

Supply Chain Management

Customer Relationship Management

Security-Policy Management

- Chordiant - Clarify - Cygent - Epiphany - Netonomy - Remedy - Siebel - Vantive

Databases and Files - DB2 for AS/400 - DB2 for OS/390 - Files - Files (OS/390 and AS/400) - JDBC - Oracle - SQL Server - Sybase - Teradata

- i2 Demand Fulfillment

- Entrust GetAccess - Netegrity Siteminder - Oblix NetPoint - Securant

System Management and Software Distribution - BMC Patrol - CA Unicenter - HP Openview - Marimba - SNMP - Tivoli - XEVO

eCommerce - Ariba - CommerceOne - BroadVision One-to-One - ATG

Enterprise Resource Planning - JD Edwards OneWorld - JD Edwards WorldSoftware - Oracle Applications - PeopleSoft - SAP ITS - SAP R/3

LDAP/Directory Servers - iPlanet - IBM SecureWay - Novell eDirectory - Active Directory

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 12


TIBCO Summary & BEA Co-exist Strategy 2.7.2

Transport Technologies

- 3270 & 5250 Screen Scraping - CICS - COM - CORBA - EDI (ANSI X12 and EDIFACT) - EJB - FTP - HTTP - HTTP/S - HTML - IMS - JCA - JMS - JMX - JRMI - Lotus Domino - Microsoft Exchange - MQSeries - SMTP (email) - SOAP over HTTP - SWIFT - TCP - UDDI - XML - WSIL

2.7.3

Vertical Technologies

Energy

Financial Services

Customer Information System

- Atlas (Aleri, MPCT) - BANCS - Bloomberg - Centradia CPI - CS/Eximbills - Diagram/RTP - EBS - EuroeMTS - FIX - GL and GLNet - Global KreditNet - Globaus - GSTPA - Instinet - Kondor+ - Merucry OnLine - MTS by SIA - Murex - Olympic (ERI Banciare) - Reuters Portfolio Management System - Reuters Intertrade Direct - SENAF - Summit - SWIFT - TOF - Urbis - Wall Street Systems - Xetra

- SAP IS-U/CCS - Customer Choice Suite (Lodestar) - Excelergy

Exchange - Intercontinental Exchange (ICE) - TradeSpark

Graphic Information System - GE Smallworld

Market Data - GlobalView - LIMS

Real-time Data Historian - InfoPlus.21 (by AspenTech) - OSI PI - eDNA (by inStep)

Trading Systems - Endur (OpenLink) - ZAI*net (Caminus) - Nucleus (Caminus) - Tempest (Triple Point)

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 13


TIBCO Summary & BEA Co-exist Strategy

Telecommunications

Healthcare - Eclypsis - Cerner

Billing - ADC Singleview - Amdocs Ensemble - Amdocs Horizon - Convergys/Geneva - Digiquant - IBM ICMS - Intec - Kenan Arbor/BP - Portal Infranet - Sema Schlumberger (LHS) BSCS - Sema Schlumberger (LHS) Targys

High-tech Manufacturing Catalog Content Management - Saqqara - Chipdata

Manufacturing Execution Systems - Brooks Automation - Promis - Consilium

Supply Chain Management -

Gateway - Quintessent - Nokia WAP Server - Extended Systems (formerly Viafone)

Agile

Retail - Retek

Other - Axiom - Brience - Cisco Network Services - CMG SMSC - HP Openview TeMIP - Logica SMSC - MobileQ - Orchestream - Soprano - Tertio - Xacct

Order Management - Kenan OM - Metasolv

Network/Event Management - Syndesis - Micromuse (Netcool)

Mediation - Kabira Objectswitch - Narus

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 14


TIBCO Summary & BEA Co-exist Strategy TIBCO also provides an Adapter SDK to build custom adapters.

Figure 2.6 – TIBCO Adapter SDK 2.8

TIBCO BUSINESSCONNECT

TIBCO BusinessConnect and TIBCO BusinessPartner allow companies and marketplaces establish reliable and secure business-to-business connections over the Internet.

Figure 2.7 – TIBCO B2B Integration components

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 15


TIBCO Summary & BEA Co-exist Strategy

Figure 2.8 – TIBCO Business Connect

Figure 2.9 – TIBCO BusinessConnect Setup Console

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 16


TIBCO Summary & BEA Co-exist Strategy 2.9

TIBCO BUSINESSPARTNER

TIBCO BusinessPartner™ software is an application that enterprises can distribute to smaller trading partners that do not have their own B2B servers. By doing this, they increase the size of their trading community. TIBCO BusinessPartner can be preconfigured to work with the TIBCO BusinessConnect™ server of the enterprise, so the small business can quickly and easily install the software without needing to spend time and money configuring it or learning how it works.

Figure 2.10 – TIBCO BusinessPartner Setup Console

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 17


TIBCO Summary & BEA Co-exist Strategy 2.10 TIBCO PARTNEREXPRESS TIBCO PartnerExpress™ software enables B2B hubs to let their trading partners exchange XML or nonXML business documents or update catalog information through an easy-to-use Web interface. This lets partners more easily participate in the supply chain or marketplace initiatives of the host, which in turn lets businesses and marketplaces rapidly, increase the size of their trading networks.

Figure 2.11 – TIBCO Partner Express

2.11 TIBCO BUSINESSWORKS TIBCO BusinessWorks provide lifecycle management capability for integration projects. It includes GUI for creating and defining integration scenarios, an engine that automates routine sequences of tasks, and a Web-based interface for monitoring applications, system resources and processes. BusinessWorks provides the integration technology in a rapidly deployable solution that manages the entire lifecycle of integration projects. TIBCO BusinessWorks also includes a graphical user interface (GUI) for creating and defining integration scenarios, an engine that automates routine sequences of tasks, and a Web-based interface for monitoring applications, system resources and processes.

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 18


TIBCO Summary & BEA Co-exist Strategy

Figure 2.12 – TIBCO Business Works

Figure 2.13 – TIBCO BusinessWorks Designer

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 19


TIBCO Summary & BEA Co-exist Strategy

2.12 TIBCO BUSINESSWORKS WORKFLOW The TIBCO® BusinessWorks Workflow software product gives companies the ability to coordinate business activities, measure their efficiency, and optimize them over time. TIBCO BusinessWorks Workflow provides visibility into business activities, along with the ability to collaborate on the modeling and modification of the rules and flows that define business those activities.

2.13 TIBCO SUBSTATION ES TIBCO Substation ES™ enables the inclusion of mainframe applications as a seamless part of automated business processes by non-invasively enabling them to send and receive event-driven messages and information to and from non-mainframe systems.

2.14 TIBCO BUSINESSWORKS SMARTMAPPER TIBCO® BusinessWorks SmartMapper software extends the capabilities of TIBCO BusinessWorks business integration software so customers can easily create and manage cross-referencing relationships and code conversions. Using TIBCO BusinessWorks SmartMapper’s intuitive graphical user interface, business managers can create and maintain cross-referencing and code conversion relationships without the help of IT staff.

2.15 TIBCO TURBOXML TIBCO TurboXML™ is an Integrated Development Environment (IDE) for developing and managing XML assets. With facilities for creating, validating, converting, and managing XML schemas, XML files and DTDs, TurboXML provides a best-of-class XML implementation platform that combines industry leading XML solutions (XML schema authoring, XML instance editing, and XML project management) into an simple and intuitive IDE.

2.16 TIBCO XMLVALIDATE TIBCO XMLValidate is an enterprise-grade solution for validating streaming XML documents or messages against an XML Schema or DTD. This SAX-based implementation for run-time validation provides organizations with the core component in developing high bandwidth, XML-based processing. Its event-driven API makes XMLValidate an ideal candidate for industry-grade processing in a run-time environment, such as the financial community, which must reliably process between 10-20 million transactions a day.

Figure 2.14 – TIBCO XMLValidate Data Flow 24-Mar-2004

Confidential - BEA Systems, Inc.

Page 20


TIBCO Summary & BEA Co-exist Strategy 2.17 TIBCO XMLTRANSFORM TIBCO XMLTransform™ is a comprehensive design solution for creating and debugging complex Extensible Stylesheet Language Transformation (XSLT) stylesheets.

Figure 2.15 – TIBCO XML Transform GUI

2.18 TIBCO XML CANON/DEVELOPER XMLCanon/Developer (XCD) is a design-time repository that manages the development and deployment of XML assets (e.g. XML schemas, DTDs, adjuncts, instance documents, and stylesheets) utilizing a Web-based interface. XCD enables an organization to take control of their XML assets for reuse throughout the enterprise.

2.19 TIBCO UAN SOLUTIONS TIBCO BusinessWorks provides the functionality needed to design, test, deploy and manage your UAN implementations in a single easy-to-use product.

2.20 TIBCO PORTALBUILDER TIBCO PortalBuilder™ software enables companies to deploy interactive business services with a single, consistent, and personalized view to underlying corporate data and systems. TIBCO PortalBuilder lets enterprises leverage their integrated application network and B2B infrastructure to provide an integrated, personalized set of real-time content and interactive services to their portal audience. As a result, customers, vendors, partners and employees throughout the entire business community have up-to-date access to business information and services.

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 21


TIBCO Summary & BEA Co-exist Strategy

Figure 2.16 – TIBCO Portal Framework

Figure 2.17 – TIBCO PortalBuilder

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 22


TIBCO Summary & BEA Co-exist Strategy 2.21 TIBCO PORTALPACKS TIBCO PortalPack™ software products provide pre-built integration between leading enterprise applications with TIBCO’s best-of-breed portal platform. PortalPack software enhances the ability to make informed, timely decisions. TIBCO provides the following PortalPacks: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦

TIBCO PortalPack for Microsoft Exchange TIBCO PortalPack for Lotus Domino TIBCO PortalPack for Verity TIBCO PortalPack for Interwoven TIBCO PortalPack for PeopleSoft TIBCO PortalPack for Documentum TIBCO PortalPack for SAP Workplace TIBCO PortalPack for eRoom TIBCO PortalPack for Jive TIBCO PortalPack for Oracle

2.22 TIBCO BUSINESSFACTOR Business Activity Monitoring solution that provides a visual and interactive interface that makes it easy to analyze your operations in context of business objectives, past performance, and current conditions so you can more quickly and intelligently identify and address risks and opportunities.

Figure 2.18 – TIBCO BusinessFactor Technology Stack

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 23


TIBCO Summary & BEA Co-exist Strategy 3 3.1

TIBCO Product Suite – Strength & Weaknesses TIBCO STRENGTH AND WEAKNESESS

TIBCO Product

Strengths

Weaknesses

TIB/Rende zvous

Very stable & mature product, used in implementations of TIB technology since 1992.

Security is “security through obscurity”.

Decoupled integrations easily implemented via subject-based addressing.

Every packet of every message goes to every rvd, including:

Optimistic messaging via UDP, so initial network load is light.

Admin broadcasts

No support for standards-based messaging.

Acknowledgements Application broadcasts Each message sent may result in numerous broadcasts, as UDP restricts packet size to 64kb. Network cost is high in the event of either failure or the selection of higher quality of service level. TRDP does not guarantee a message will be received. RVCM does not guarantee a message will be received only once. RVCMQ uses TRDP between scheduler and worker, so not certified end-to-end. RVTX requires a second daemon (and licenses) for sender and receivers using transactional delivery

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 24


TIBCO Summary & BEA Co-exist Strategy BusinessW orks (Integration Manager)

A wide variety of inbound communication protocols are supported. Each protocol, represented by a channel transport, creates a listener for that protocol. The Integration Manager provides a simple to use GUI. The GUI has a built-in lightweight process engine for testing and debugging. Custom scripting tasks allow for built-in programmatic functions. Workflow engines provide fault-tolerance and load balancing. Division of class, message, and process diagrams promotes reuse. Message diagram design allows for easy restructuring of workflow triggers and associated communication media.

Process diagrams have many node options making the tool too low level to be used by the business analyst. Fault-tolerance and load balancing rely on checkpoints in business processes, in order to pass execution to other workflow engines. Some tasks cannot be passed from one workflow engine to another. For example, an in process request/reply that has not received the reply. While IM supports inbound and outbound certified messaging in a process, RVCM ledger files are not supported for outbound messages. This means all message sources in a process use in-memory ledgers only and data could be lost if the source rvd should fail. Separate programming support required for custom task nodes. TIBCO suggests the FESI EcmaScript Interpreter.

Adapter SDK

Built-in HAWK support for custom adapters is provided.

The SDK does not provide a script or batch file for creating a template adapter.

The same designer tool is used for custom and pre-built adapters. Developers for custom adapter configuration do not require new skill sets.

The SDK is proprietary. The SDK libraries do not provide a testharness for testing of standard or custombuilt adapters.

Each adapter has its own Designer project (equivalent to a Repository instance) and can maintain any number of adapter operations. Configurable resource operation templates, called palettes, make designing adapter logic simple. Adapters, though they require coding, are easy to write due to a limited set of required classes for adapter creation.

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 25


TIBCO Summary & BEA Co-exist Strategy TIB/Hawk

Hawk is fault tolerant as there is no central server dependency. Hawk provides an easy-to-use display for monitoring and configuration of the rulebase. Rules may be exported/imported across systems.

Hawk messages are broadcast onto the network even if no listeners are available on the Rendezvous network.

Hawk monitoring domains are logical, making it painless to add new systems to the domain.

The Hawk Display must be configured in the same domain as the monitored systems.

Hawk can monitor applications, Rendezvous, operating system.

Hawk is a proprietary implementation of software monitoring and management. It therefore does not provide direct interoperability with third-party management software as JMX and SNMP are not supported.

Hawk is self-monitoring, allowing Hawk to monitor and restart itself, if necessary. Hawk also supports execution of OS programs and scripts via custom microagent.

Logging via Hawk Agents occurs at the OS level, and on each system independent of the others. Though alerts are always propagated for central display, logging is not stored centrally.

The Repository provides a single metadata and configuration store for all TIBCO clients.

Repository is not a general data store – designed only for TIBCO configuration and metadata.

The Repository may be configured as a local instance for use in development environments,

Client API is not published for Repository functions.

The Repository may be configured as a remote Server instance for single view of TIBCO implementation from all clients. Supports high-availability for multiple Repository instances. Using Distributed Queue

Portal Builder

24-Mar-2004

Rules are dependent on micro-agent capabilities, varying across OS and applications.

Management and monitoring tasks occur via installable micro-agents.

Hawk can auto-restart applications, Rendezvous.

Repository

Rules must be configured for monitoring and management; few rules are pre-built. Consequently Hawk cannot be installed and ran without upfront effort.

Requires a TIBCO proprietary client for access. Local repositories must always be filebased. Recovery in event of failure is only to last backup of the file. Repositories configured in a load-balanced environment (Distributed Queue) must be read-only repositories.

Collections of servlets designed to run on best-of-breed servlet engines, including WLS

Requires BusinessWorks for real time access to backend systems and data resources.

Supports browser and wireless clients with built-in support for Wireless Application Protocol. (WAP)

Presentation not JSP, but rather translation of proprietary tags into HTML. Many 3rd-party tools required for installation and run-time

Confidential - BEA Systems, Inc.

Page 26


TIBCO Summary & BEA Co-exist Strategy Business Connect

BusinessConnect provides out-of-the-box support for SOAP 1.1 with attachments.

The BusinessConnect product is obviously B2B written by EAI experts.

BusinessConnect also provides base support for a wide range of installable business protocols.

Dependent on functional BusinessWorks components for access to backend systems.

Web-based configuration and administration is provided.

tibXML and SOAP do come with the BusinessConnect product out of the box. However, all other business protocols require purchase and separate installation.

Re-use of IM Editor as Process Designer allows reuse of skills.

tibXML only truly useful between BusinessConnect installations. Non-TIBCO B2B servers will not honor tibXML features. BusinessConnect requires many 3rd-party products for operation, meaning.

Business Partner

Simple to implement. Low cost of purchase.

Supports connections to only one trading partner. Must communicate with BusinessConnect user. Supports only a single protocol in communication.

Partner Express

Zero-weight on the client side, as fully browser-based. Little to no installation on the server side, as BusinessConnect supports PartnerExpress functions natively

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 27


TIBCO Summary & BEA Co-exist Strategy

3.2

TIBCO SUMMARY

Strengths: ♦ ♦ ♦ ♦ ♦ ♦ ♦

Weaknesses:

Long time EAI player, invented Publish and Subscribe messaging Brand recognition, large reference and install base (2000+ customers worldwide) Effective selling approach using impressive demos and POCs Strong selling ability targeting both IT and LOB managers Solid partnerships with major SIs and ISVs Products perform well; Rendezvous is a rock solid messaging bus Vertical emphasis and expertise in Energy, High Tech Manufacturing, heavy roots in Financial Services through Reuters relationships Perceived as a leader in pure-play market

♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦

24-Mar-2004

Products are not fully integrated, multiple runtimes underneath one common development environment. Low developer productivity No unified development environment (different user interfaces). No practical lightweight B2Bi offering (lightweight client limited to one trading partner) Products are still proprietary-based (e.g., RV) TIBCO’s Publish and Subscribe messaging architecture is not well suited for EAI (transactional, asynchronous messaging) No J2EE foundation (security, clustering, RASP) TIBCO Portal functionality is limited to Rendezvous, not well integrated with the rest of the TIBCO Product Suite No application server, leading to inability to integrate custom applications

Confidential - BEA Systems, Inc.

Page 28


TIBCO Summary & BEA Co-exist Strategy 4

TIBCO & BEA Product Comparisons

A comparison of features of core TIBCO and BEA products are presented in the following sections.

4.1

TIBCO RENDEZVOUS AND BEA JMS

TIBCO Rendezvous

BEA Enterprise Message Bus/Message Broker

Proprietary messaging

Open standard messaging

Non-secure, non-guaranteed publish and subscribe multicast messaging.

Secure reliable messaging that supports transactions.

Requires RVD

Requires JMS Server

Has an API

Has an API

Uses UDP on IP

Uses TCP on IP (though UDP is used for enhanced multicasting.

RVRD is used to multicast across subnets.

No multicasting across subnets.

Clustering is achieved through RVCMQ (distributed queue). Requires certified messaging to be used and only certified to scheduler.

Clustering is supported, though a manual migration is necessary in the event of failure.

Subject-based addressing forms the basis of subscriptions

Filters

Communications via Rendezvous are out-ofprocess (and may traverse many process boundaries.)

Communications via JMS are in-process. JMS Bridge can be used for out-of-process communication e.g. communication with other JMS Server

Security exists primarily at the application level via subscriptions and application encryption.

Security can be structured at the connection level (SSL).

4.2

BUSINESSWORKS/ INTEGRATION MANAGER AND BEA WLI

BusinessWorks(Integration Manager)

WebLogic Integration (WLI)

Provides workflow capability for application integration. Uses TIBCO adapters for connecting external applications with TRV. XML tools for processing XML data are not tightly integrated. No support for XML – Java Object mapping. Additional, effort to implement webservices.

Standards based integration engine and development environment. Provides enhanced GUI development tool environment for development and deployment of process flows. Enhanced ability to build composite applications. Ability to expose process flows as webservices. Provides all the tools necessary to develop SOA applications. Integration data transformation capability. Out of the box, XML – Java Object mapping capability using XML

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 29


TIBCO Summary & BEA Co-exist Strategy Beans. WLI has integrated development, test and debugging environment – WebLogic Workshop. It is also a RAD tool. WLI is built on top of industry tested application server – WebLogic Server. Two-way editing (graphical & source view). Source code control integration. High developer productivity. Checkpoints are used to determine boundaries for execution, as there are some tasks that cannot be passed from workflow engine to workflow engine.

Communication between workflows fully supported.

Limited transaction support for some workflow nodes (requires use of database node or messaging node using RVTX.) Explicit beginTransaction and endTransaction nodes must define the transaction boundary. Any nodes not supporting transactions included between beginTransaction and endTransaction nodes will be executed, but the transaction will not apply to them on commit or rollback.

Full support for transactions in workflow. Transaction boundaries can be defined automatically by the process or manually by developer at design time.

Compensating transactions required for rollback for nodes not supporting transactions.

Automatic commit and rollback supported within transaction contexts.

BusinessWorks Designer/Editor for process design. No portal development – separate tools needed. Separate tools for XML development.

Uses WebLogic workshop for development, test and deploy. Supports composite application development. Supports various mechanisms for process flow invocation, conditional logics, loops, manual Java coding, and Java controls. A number of BEA and partner based Java Controls comes out of the box. Drag and drop integration with controls. Processes are automatically exposed as webservices. Integrated portal and page flow development. Portals can be tightly integrated with process flows. Workshop also provides environment for Java development.

Processes are node-based, with configuration of activities at the node level.

Processes are node-based. Configuration at node level as well as controls level.

Supports custom scripting for non-TIBCO tasks.

Supports manual Java coding, invoking java methods and EJBs.

4.3

TIBCO ADAPTERS AND BEA WLI / JCA

Adapter SDK

WebLogic Integration / JCA

Designer tool for configuration of adapters.

Application Explorer, and WLAI console for configuration.

Requires Rendezvous

Requires WLS

Proprietary

Standards-based

Easy API for coding custom adapters.

Adapter Development Kit for developing

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 30


TIBCO Summary & BEA Co-exist Strategy custom adapters. Palettes for configuring adapter logic: publication and subscription, as well as application events and services.

Application views for configuring events and services. Can also use webservices, JMS for communication without application views.

Security and transaction context propagation requires coding.

Supports propagation of security and transaction contexts via JCA where supported by back end application.

4.4

TIBCO HAWK AND BEA WLI / WLS

Hawk

WLI / WLS

Proprietary monitoring and management system

Based on open standards: SNMP and JMX

Built-in management and monitoring of applications and systems

3rd-party management and monitoring

Monitoring and configuration through Hawk Display

Monitoring and configuration through: WLS console, logging, 3rd-party JMX and SNMP tools

Can use Application Monitoring Interface (AMI) to build micro-agent functionality into custom applications

Can use JMX to build monitoring and management capability into J2EE applications. BEA JRockit implements JVMPI, JVMDI interfaces for integration with 3rd party profiling and debugging applications.

Hawk Agent installed on each physical host to be monitored.

WLS administration server for each WLS domain (the admin server has the embedded SNMP agent)

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 31


TIBCO Summary & BEA Co-exist Strategy 4.5

TIBCO REPOSITORY AND WLI REPOSITORY

Repository

WebLogic Integration

Repository holds configuration and metadata.

File based XML repository; can be version controlled. WLS domain configuration files hold configuration data.

TIBCO proprietary clients required for access to Repository data.

JMX and MBean API are available for accessing configuration data.

N/A

XML Repository stores not only configuration and metadata, but can also store application data, such as: transformation maps, document types, document examples, etc.)

4.6

TIBCO BUSINESSCONNECT AND WLI B2B

BusinessConnect

BEA WebLogic B2B

Standards-based

Standards-based

TibXML SOAP 1.1 with attachments

SOAP 1.1 via web services (WLW/WLS)

RosettaNet, ebXML, cXML, ChemXML, BizTalk, xCBL

RosettaNet, ebXML

HTTP, HTTPS, FTP, SMTP

HTTP, HTTPS, T3, T3S (WLS)

Web-based administration and configuration

Web-based administration and configuration

Authentication, Access Control, Encryption, and Non-Repudiation

Authentication, Access Control, Encryption, and Non-Repudiation

Process Designer for creating internal and external processes

WebLogic Workshop development environment for creating public and private processes

4.7

TIBCO BUSINESSPARTNER AND BEA BUSINESSCONNECT

BusinessPartner

BEA BusinessConnect

Scaled-down TIB/BusinessConnect server.

Stand-alone document handling application.

HTTP, HTTPS, FTP, SMTP

HTTP, HTTPS

Communicates only with a single partner who implements BusinessConnect

Communicates only with a single partner who implements WebLogic Integration

Any of the supported BusinessConnect protocols, though only one may be used per BusinessPartner implementation.

EbXML

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 32


TIBCO Summary & BEA Co-exist Strategy 4.8

TIBCO PARTNEREXPRESS AND WLI ZERO-WEIGHT CLIENT

PartnerExpress

WLI WebServices

Browser-based on client side.

Browser-based on client side.

Requires additional servlets to be installed on supporting BusinessConnect support.

JSP support for zero-weight client.

HTTP, HTTPS

HTTP, HTTPS

4.9

TIBCO PORTALBUILDER AND WEBLOGIC PORTAL

PortalBuilder

WebLogic Portal

Run-time translation of proprietary tags for presentation.

JSP-based presentation. Struts support.

Static web application design.

Dynamic web application design, using pageflow. Highly efficient GUI based development, test and deployment environment. Higher developer productivity. Tightly integrated with process flow development. Can invoke Java controls directly.

No hooks to any specific application or web server.

WLS-specific libraries are required. Can use 3rd party webservers through WLS plugins.

User-controlled page layout via profiles.

User-controlled page layout via profiles.

Coarse-grained, container-based information display.

Fine-grained, rules-based campaign management.

Custom Worklist clients and WLI processes may alert users.

User and admin defined alerts for users/roles may be sent to email, user pages, or WAP devices.

N/A

Commerce components out of the box.

Static HTML templates on file system, other configuration components stored in LDAP.

Standard EAR and WAR deployment

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 33


TIBCO Summary & BEA Co-exist Strategy 4.10 SUMMARY

TIBCO

BEA

TIBCO offers a fragmented architecture with proprietary roots. There is no common look and feel to TIBCO’s products; customers will suffer from added complexity and higher support costs from having to maintain so many unique skill sets.

BEA offers a unified solution based on standards at the core. BEA provides comprehensive, unified and standards-based integration; proven solution designed for BPM and Service-Oriented Architectures; greater ease-of-use and process adaptability

Multiple runtime engines that are not fully integrated; no migration path off legacy technology to Business Works (Integration Manager, Message Broker, TRV); different mapping tools

Common runtime engine means faster deployment of solution; less time needed for troubleshooting, testing/debugging

No J2EE foundation; BusinessWorks not a JMS provider; not all adapters are JCA, most still tied to proprietary messaging bus (TRV); SDK not JCA

Leverages the proven J2EE foundation of WebLogic Server resulting in consistent support for standards

Business Works must rely on TRV for clustering, load balancing, fault-tolerance

Leverages same features native to WebLogic Server (clustering, load-balancing, fail-over, security)

No app server (uses EJB adapter)

Tight integration with app server means less work required to integrate custom-built applications

Pub/sub messaging not well-suited for BPM; cannot support guaranteed messaging

Supports guaranteed messaging (once and only once, and in sequence). Supports asynchronous messaging.

Weak transactional support (RVTX not highly performant)

Leverages the high performant transaction management capabilities native to the leading J2EE app server

Deploying a Service-Oriented Architecture is difficult (no tools to promote reuse or composite application assembly). Creating Web services is hard

Supported by the leading ISE (Weblogic Workshop) for service-oriented development and Web services creation/orchestration

Although BusinessWorks is main development environment, there are different user interfaces (BW, IM, Hawk, portal, B2B, JMS, RV, SDK). Users must be trained in different environments for process design, admin, deployment and monitoring; difficult to test and debug. Lot of coding required.

Common development model across integration, portal and app server means less complexity and high developer productivity. Can model/monitor processes across entire platform including custom built apps and portal projects. Changes to process model are immediately executed in underlying process engine (process view and source view are always in synch). Graphical development environment, less coding required.

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 34


TIBCO Summary & BEA Co-exist Strategy 5 5.1

Working with TIBCO – Recommended Strategy & Architecture SERVICE ORIENTED ARCHITECTURE FOR ENTERPRISE

Figure 5.1 presents a business view of a Conceptual Enterprise Reference Architecture based on Service Oriented Architecture.

Figure 5.1 – Business View of Conceptual Service Oriented Architecture (Source: Doculabs)

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 35


TIBCO Summary & BEA Co-exist Strategy A services-oriented architecture can be depicted as providing a number of individual service layers. Together, these layers provide an unprecedented level of flexibility in application design, while minimizing cost and providing more pertinent applications and business value to customers. The benefits of Service Oriented Architecture include: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦

Lower TCO Leverages existing development skills / investments in technology Accelerates movement to standards-based server and application consolidation Provides a standards based data bridge between incompatible technologies Provides the ability to build composite applications Enables the compilation of a unified taxonomy of information across an enterprise and its customer and partners Business Value Quick time to market Management of business functionality closer to the business units Leverages Reduces reliance on expensive custom development

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 36


TIBCO Summary & BEA Co-exist Strategy 5.2

ENTERPRISE TECHNOLOGY COMPONENTS PROVIDED BY TIBCO & BEA

Common technologies found in the major architectural layers and lists of products provided by BEA and TIBCO in those technologies is provided in Table 5.1. Layer

Technologies

BEA

TIBCO

Enterprise Application & Data Systems

ƒ ƒ ƒ ƒ ƒ

Enterprise Resource Planning Content Management Mainframe & Legacy Applications CRM …

No No No No

No No No No

Data Services

ƒ ƒ ƒ ƒ

Application & Data Adapters Data Model & persistence engines Legacy Integration Data Aggregation Engine

√√ √√ √√ √√

√√ √√ √√ No

Application Services

ƒ ƒ ƒ ƒ ƒ ƒ ƒ ƒ ƒ

Enterprise Messaging Application Container/Servers Standards Based Interfaces Metadata Repositories Transactional Asynchronous Event Services - Publish/Subscribe Business Process/workflows Business Rules Human Workflow

√ √√ √√ √1 √√ √ √√ No √√

√√ No √2 √√ √ √√ √√ No √√

Presentation/Interface Services

ƒ ƒ ƒ

Web Portal Mobile device support (WAP, Java) Standards based (EDI, ebXML, etc)

√ √ √

√ √ √√

Enterprise Lifecycle Services

ƒ ƒ ƒ ƒ

Analysis/Activity Monitoring Assembly/Development/Deployment Application Management Design/Modeling

No √√ √√ No

√√ √ √√ No

Business Services

P

P

P

Table 5.1 1 P

File System Based For WebServices only P

2 P

P

No √ √√ study

– Product functionality not available – Product functionality available – Product functionality available and superior of the two (TIBCO & BEA) based on preliminary

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 37


TIBCO Summary & BEA Co-exist Strategy 5.3

RECOMMENDED PRODUCT STRATEGY FOR EDS

TIBCO and BEA provide products/product components that excel in its relevant functional area. Based on the high-level comparative study of BEA and TIBCO products, I would recommend a co-existence strategy for projects where both technologies are required. In addition, I also recommend the following core products be used for EDS Enterprise Application Integration as may be applicable.

TIBCO Rendezvous – For Enterprise message bus

TIBCO BusinessWorks – For business process management that: ƒ Require integration with TIBCO Rendezvous ƒ Do not require custom application integration ƒ Is not developer centric ƒ Is publish/subscribe based workflow ƒ Is non-human workflow ƒ Is message oriented integration

TIBCO Application and Data Adapters – For integrating applications directly with TIBCO Rendezvous /BusinessWorks where needed

♦ ♦

TIBCO BusinessFactor – For Business Activity Monitoring TIBCO Hawk – For management of TIBCO components

BEA WebLogic Server – For J2EE Application Server/Container functionality

BEA WebLogic Workshop – For custom and Rapid Application Development

BEA WebLogic Integration – For management of business processes that does not require direct and only connectivity to TIBCO message bus, may involve integration with custom applications, developer centric, RAD requirement, asynchronous and transactional messaging, human workflow and portal integration, service oriented architecture implementation instead of message oriented integration, standards based (J2EE-CA) applications integration

BEA Application and Data Adapters – For connecting with enterprise applications

BEA WebLogic Portal – For Portal and front-end development

BEA Liquid Data – For real-time data aggregation from diverse sources

BEA WebLogic Enterprise Security (WLES) – For enterprise application security

In addition to the core products mentioned above, other products from BEA and/or TIBCO may be considered as appropriate for the integration/application Use Case.

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 38


TIBCO Summary & BEA Co-exist Strategy 5.4

HIGH-LEVEL USECASES FOR TIBCO, BEA IMPLEMENTATIONS

A typical TIBCO implementation looks as follows:

Figure 5.1 – Typical TIBCO Implementation Architecture

This section presents high-level use cases that can or are implemented using TIBCO, BEA or both products. 5.4.1

Publish Stock Quotes

The functional requirements for a stock quote publishing application can be summarized as follows: ♦ ♦ ♦ ♦ ♦ ♦ ♦

High speed publish/subscribe messaging Real time Event driven, non-transactional Point to point or one to many application messaging Involves no/minimal BPM Involves no Human Intervention Basic EAI

A high level architecture for implementing this use case can be represented as shown in Figure 5.2

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 39


TIBCO Summary & BEA Co-exist Strategy

Figure 5.2 – High Level Architecture of Stock Quote Publish Application TIBCO’s architecture is best suited for pure publish and subscribe messaging that does not require the use of transactions or asynchronous messaging (e.g.: Energy Trading and Securities). TIBCO Rendezvous provides the high performing publish/subscribe messaging bus for the Stock Quote application. TIBCO Adapters link TIBCO Rendezvous with back-end systems. TIBCO Hawk provides the system and application management capability. An EAI scenario which requires real-time integration for enterprise applications using publish/subscribe, does not require human interaction/front end is a perfect scenario for using TIBCO integration technologies.

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 40


TIBCO Summary & BEA Co-exist Strategy 5.4.2

Order Processing

Functional requirements for an Order Processing scenario (e.g., Siebel Order Management, SAP Financial, Credit Card Authorization, Batch Order intake) can be summarized as follows: ♦ Synchronous, Asynchronous messaging ♦ Reliable, transactional ♦ Complex Business Process Management ♦ Exception Handling, compensating transactions ♦ One-to-one, one-to-many, or many-to-many application messaging ♦ Data Transformation ♦ Human Workflow, Web front-end/Portal ♦ Custom Application integration ♦ Standards based integration for integrating heterogeneous applications Use Cases for this EAI scenario can be as follows: ♦ Order Processing ƒ Create Customer ƒ Create Order ƒ Credit Card Authorization (CCA) ƒ …

Figure 5.3 – Order Processing – Use Case Scenarios

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 41


TIBCO Summary & BEA Co-exist Strategy A high level architecture for implementing this use case can be represented as shown in Figure 5.4

Figure 5.4 – Order Processing – High Level Architecture The process flow for this use case is shown in Figure 5.4. The process flows / workflows for this use case scenario are as follows: ♦ ♦ ♦ ♦ ♦

SiebelReceive CreateSAPCustomer CreateSAPOrder WebOrderReceive AuthorizeCreditCard

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 42


TIBCO Summary & BEA Co-exist Strategy SiebelReceive

AuthorizeCreditCard

HTTPS Control

CreateSAPOrder

CreateSAPCustomer

HTTPS

CCA HTTP/ WebService

Siebel Adapter

WebOrderReceive

SAP Adapter

SAP BAPI-JCO/ WebService WebOrderApplication

File Control FTP/Local File Read

Figure 5.5 – Order Processing – Process Flow Architecture BEA provides standards based approach for integrating enterprise applications including custom developed applications. BEA WebLogic Integration (WLI) has business process management engine, where processes automatically generate execution code with minimal programming, using PD4J. WLI also features human workflow integration with portals to facilitate interface building. WLI has XQuery based transformation capability compared with XSLT based functionality with TIBCO XMLTranslate. WLI also shares the WebLogic Workshop RAD interface which can be used to build processes, configure integration details, build and expose processes as web-services. BEA XMLBeans technology provides easy mapping between XML documents and java objects – a functionality fully utilized in Workshop. TIBCO uses Multicast Messaging (publish and subscribe) architecture, that is not well suited for transactional, asynchronous EAI. It is more difficult to integrate custom application using TIBCO due to the complexity involved while using TIBCO proprietary APIs. WebLogic Integration also provides service and message brokering capabilities needed for EAI.

5.4.3

Joint BEA – TIBCO Use Case Scenarios

Functional requirements for a Use Case scenario where both BEA and TIBCO technology can be used to utilize the benefits of both technologies can be as follows: ♦ ♦ ♦ ♦

High speed publish/subscribe as well as asynchronous transactional messaging Real time/Event driven, non-transactional as well as transactional Involves extensive BPM, complex EAI Involves Human Intervention/workflow, Web front-end/Portal

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 43


TIBCO Summary & BEA Co-exist Strategy ♦ ♦ ♦ ♦ ♦ ♦ ♦

Synchronous, Asynchronous messaging Reliable, transactional Exception Handling, compensating transactions One-to-one, one-to-many, or many-to-many application messaging Data Transformation Custom Application integration Standards based integration for integrating heterogeneous applications

The high level component diagram for a BEA – TIBCO co-existence implementation is shown in Figure 5.6.

Figure 5.6 – High Level Component Diagram for TIBCO – BEA co-exist Architecture The product components chosen for this architecture is based on the recommended product strategy in Section 5.3. Sample architecture of a Use case where both BEA and TIBCO technologies can be used is shown in Figure 5.7.

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 44


TIBCO Summary & BEA Co-exist Strategy

Figure 5.7 – BEA – TIBCO co-exist Sample Architecture

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 45


TIBCO Summary & BEA Co-exist Strategy 5.5

BEA – TIBCO INTEGRATION

BEA and TIBCO product suites can be integrated using the following technologies: ♦ ♦ ♦ 5.5.1

JMS Bridge Conexus Control for TIBCO WebServices JMS Bridge

BEA and TIBCO both have implemented JMS Bridges to communicate with foreign JMS providers. Applications running on BEA WebLogic Server can communicate with TIBCO Rendezvous by publishing messages to JMS Topics/Queues which are mapped to TIBCO Enterprise JMS Topics/Queues via the JMS bridge infrastructure. Similarly, TIBCO Rendezvous messages can be received by WebLogic applications via the JMS Bridge and Message Driven Beans.

Figure 5.8 – TIBCO – BEA Integration using JMS Bridge

5.5.2

Conexus Control for Tibco

The Conexus Control for Tibco provides a native interface between WebLogic Integration and the Tibco Rendezvous messaging system. Use of the control enables publishing documents from WebLogic Integration Processes to Rendezvous, and receiving documents into WebLogic Integration Processes from Rendezvous. The TIBCO control from Conexus offers the following features: ♦ ♦ ♦

Native, high-performance interface to Rendezvous messaging Provides a lower-level JMS-modeled API for accessing Rendezvous messaging High-level WebLogic Integration control for visual integration of Rendezvous messaging into WebLogic Integration Processes

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 46


TIBCO Summary & BEA Co-exist Strategy ♦ ♦

Support for XML Schemas Automatic type conversion between Rendezvous message format and XML

Incoming TIBCO Events

Destination

Process

Destination Events

TIBCO Message Broker

Rules & Transform Destination

Destination Channel

Figure 5.9 – TIBCO – BEA Integration using TIBCO Control Events Functionality 5.5.3

WebServices

BEA and TIBCO both have implemented WebServices stack to invoke remote webservices as well as expose business components as webservices. For BEA WebLogic these business components include EJBs, process/work flows, etc. BEA WebLogic and TIBCO applications can perform synchronous bidirectional communication using the webservices infrastructure that BEA and TIBCO have implemented.

Figure 5.9 – TIBCO – BEA Integration using WebServices

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 47


TIBCO Summary & BEA Co-exist Strategy 5.6

THE BEA PLATFORM ADVANTAGE

BEA WebLogic Integration (WLI) is based on a Unified Product Architecture that is built on top of industry standards based J2EE framework – BEA WebLogic Server.

Figure 5.10 – BEA WebLogic Platform – Standards based from the core WebLogic Integration is a result of the technology convergence effort that BEA had initiated with all components of enterprise application integration being part of a single platform. WLI is part of the industry’s leading Application Platform Suite (APS) – the BEA WebLogic Platform. The BEA WebLogic Platform stack is shown in Figure 5.10 and comprises: ♦

WebLogic Server – J2EE Application Server

WebLogic Workshop – WebLogic development and deployment environment for J2EE components, WebLogic Integration, WebLogic Portal, Data Transformation etc.

WebLogic Integration – BPM, J2EE/CA application and B2B (RosettaNet, ebXML) integration, Data transformation, XML Beans – XML-Object mapping, Adapters, UAN

WebLogic Portal – Portal Framework

Liquid Data – Real-time data aggregation from multiple data sources

WebLogic Enterprise Security – Enterprise Security management with or without WebLogic Platform.

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 48


TIBCO Summary & BEA Co-exist Strategy

Figure 5.11 – BEA WebLogic Platform The advantages of BEA WebLogic Platform include: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦

Standards Based (consistent across integration & entire platform) Application Framework, Integration, Portal Technology convergence - delivered as a unified, comprehensive solution; Single, pre-integrated software stack. Single product install Converging development with integration Enhanced productivity and RAD Comprehensive platform to support projects spanning portal, EAI/BPM and workflow, data integration, and custom applications Architected to support standards consistently throughout the platform and down to the core Common process model and runtime engine for EAI, BPM and human workflow (single install) Common runtime engine and toolset means faster deployment of solution; less time needed for troubleshooting, testing/debugging Automatic code generation. Less manual coding required Changes to process model are immediately executed in underlying process engine Assures ease-of-use, faster time to integration, greater process adaptability, and lower maintenance overhead Transaction management; inherent with WLS (XA, two-phase commit, compensating transactions) Security (in WLS/WLES; can also support 3rd party security services) Consistent support for Web services across EAI, BPM, workflow, (easy to expose a process as a Web service) Leverages same features as native to WebLogic Server (clustering, load-balancing, fail-over, security) Tight integration with app server means less work required to integrate custom-built apps Ease-of-use means greater process adaptability Can model/monitor processes across platform including custom built apps and portal projects Common development model across integration, portal and app server means less complexity and high developer productivity

A unified platform can increase time-to-market by accelerating application development/deployment cycle. It can cut development costs by shifting complex work performed by senior Java developers/

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 49


TIBCO Summary & BEA Co-exist Strategy architects to less expensive resources (i.e., corporate developers). The cost of maintenance and process changes after initial app deployment reduces dramatically with a unified development and deployment platform.

24-Mar-2004

Confidential - BEA Systems, Inc.

Page 50

ddddd  

dddddddddddddddddd