Professional Documents
Culture Documents
An Overview
Objectives
Slide 2
Scenario
Requirements:
Slide 3
Step 1: Design
an event
Step 2: Raise
event
Step 3:
Consume data
Event designer
Message
Customer Name
Contact Details
Account currency
T24
Slide 5
T24
Message
Action: Account I
Integration Framework
David Hooper
USA
USD
Slide 6
T24
push
Message Ready
to be sent
Integration Service
Message in
JMS queue
3rd Party
System
pull
ESB Adapter
ESB
Integration Framework
OFS
BrowserML
Outbound
Message
T2
4 Module
VERSION
Integration
Framework
Event
out
Components
Service
Event
out
Middleware
Inbound
Message
Enrichment
Event
Generic term for the notification which T24 emits when a business event
occurs.
Exit Point
Slide 9
Flow Catalog
Integration Flow
A T24 table which contains details of all the Integration Flows which have
been created by the system integrators.
Defines the layout of an XML message which will leave T24 when a
business event occurs
Service Repository
Slide 10
Catalogue - IF.INTEGRATION.FLOW.CATALOG
Holds records which bind the notification exit points with their integration
flows.
Slide 11
Service that performs the delivery of the events which are stored in the
store and forward table.
5
Events
XSD
Integration
Framework
Flows
13
Routing
Transformation
BizTalk
JMS
Adapter
Fiorano
ESB
Adapter
IBM
Integration
Bus
Adapter
Oracle
AIA
Adapter
RM
Txn 2
(on
demand)
2b
T24 Banking
2a
Database
Transaction
1
Exit Point
RM
Txn 1
Interface table
Quiz
Match the following
Integration framework uses this
method to deliver message
INTEGRATION.SERVICE
Asynchronous
IF.EVENTS.INTERFACE.TABLE
Slide 15
Summary
Slide 17
Thank You