EAIESB TIBCO EXPERTISE

1. Vijaya Maddela
TIBCO Enterprise Business Integration
EAIESB

2. TIBCO Enterprise Business Integration: Inbound

3. TIBCO Enterprise Business Integration: Outbound

4. TIBCO Enterprise Business Integration
 Tibco Gateway Server receives the EDI message from Trading Partner
 Tibco BC validate the Identifiers and allows the EDI message
 Tibco BC converts the EDI message into EDI XML
 Tibco BW, On-Startup process reads EDI XML message and invokes the Sub-Process to convert the message from EDI XML to
iDoc message
 Converted iDoc message will be published on to external Division System
 Audit log is implemented at every step though out the implementation to track the status
 CLE framework is in place to handle the errors
Implementation Process
 Tibco 5x / 6.x – Tibco Designer 5.x / 6.x, EDISIM, Tibco BW, BC , BE and Spotfire
 Source Layout: EDI
 Source Type: Message Order
 Source Version: Enterprise Supported
 Target Layout / Type: Non-EDI
 Setup an Integration Layer to transform EDI message into Non-EDI standard message and exchange
with Trading Partners vise versa.
Enterprise Scenario
Technology Stack
 External Division Partners
 External Trading Partners
Business Units
 Tibco comes with wide range of products include BW, EMS, BC, BPM, BE and so on. These products can
be used to integrate, manage and monitor the enterprise applications and enables high performance
reliable delivery.
 Tibco products include applications for coordinating business process and activities, securely
exchanging information with trading partners, creating and maintaining documents, and managing
distributed systems.
 Each enterprise has their data in applications like ERP, S/FTP, DB, Legacy Systems and so on. The data is
to be of their own standards include X12, Rosettanet, OAGIS, Flat File and so on.
 Tibco BC is configured to convert source data coming from trading partner systems in to trading
partner expected format and send it to Tibco BW.
 Tibco BW will receives the message validates it and sends it to external division systems, and the
exchange of message between partners will happen vise versa.
Business Integration
 Setup an Integration layer to exchange EDI & Non-EDI data between partners by implementing Tibco BW, BC, BE & Spotfire
for this integration and vise versa
 Configure AS2 Partner Profile/Identifiers settings
 Configure Gateway Tokens to accept EDI transactions
 Implement Tibco BW’s to transform the EDI message into iDoc message
Design Proposals
Logical Flow Reference Model

5. For any questions please write us to tibco@eaiesb.com we will get back to you soon