Sei sulla pagina 1di 17

Integration Framework

An Overview

TEMENOS EDUCATION CENTRE


Warning: This document, is protected by copyright law and international treaties. No part of this document
may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any
purpose, without the express written permission of TEMENOS HEADQUARTERS SA Unauthorized
reproduction or distribution of this presentation or any portion of it, may result in severe civil and criminal
penalties, and will be prosecuted to the maximum extent possible under applicable law. Information in this
document is subject to change without notice

Objectives

At the end of this session, you will be able to

State the purpose of Integration Framework


Name the Terminologies used in Integration Framework
Identify T24 Objects used in Integration Framework
Describe the design time and run-time of Integration Framework

Slide 2

Scenario

Before creating an Account, a Bank wants to know whether the


customer is involved in money laundering activity, using a 3rd party
system.

Requirements:

What do we need to do? Customer details have to be checked against the


3rd party system
How do we do it? Send customer information from T24, whenever an
account is created.

Slide 3

Solution Integration Framework

Step 1: Design
an event

Step 2: Raise
event

Step 3:
Consume data

Using a design time tool, describe the information to be


emitted and when. For instance, define the customer details
that needs to be sent to the third party system when a new
account is created

At runtime, call the operation that raises the event. i.e.


Create a new account . The emitted data is captured in a
store and forward table.

Send the data to the 3rd party system asynchronously

Define the event at design time

Step 1 : Define the Data that has to be sent out of T24

Event designer
Message

Event : Create an Account

Customer Name
Contact Details
Account currency

T24

Slide 5

Trigger the event at runtime and emit data

Step 2 : Create a new Account

T24
Message
Action: Account I

Integration Framework

David Hooper
USA
USD

Slide 6

Consume the emiited data

Step - 3: Send the data to the 3rd party system asynchronously

T24
push
Message Ready
to be sent

Integration Service

Message in
JMS queue
3rd Party
System

pull

ESB Adapter

ESB

Integration Framework

T24 (Information Resource)

OFS
BrowserML

Outbound
Message

T2
4 Module
VERSION

Integration
Framework

Event
out

Components

Service

Event
out

Middleware
Inbound
Message

Good to know - Terms

Enrichment

Event

Process of retrieving data which is stored in T24 for inclusion on the


notification message

Generic term for the notification which T24 emits when a business event
occurs.

Exit Point

Defines the hook, or API, in T24 to which an Event can be linked

Slide 9

Good to know - Terms

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

Contains details of all the available component services, their operations,


plus the data types and direction (in/out/inout) for each operation argument.

Slide 10

T24 Objects to support Integration Framework

Catalogue - IF.INTEGRATION.FLOW.CATALOG

Serves as a catalog for the Integration Flow records.


Integration Flows created by Event designer stored here at design time.
Flows are attached to Exit Points

Exit points - IF.EXIT.POINTS

Holds records which bind the notification exit points with their integration
flows.

Slide 11

T24 Objects to support Integration Framework

Store and Forward Table - IF.EVENTS.INTERFACE.TABLE

Event Batching - INTEGRATION.SERVICE

Service that performs the delivery of the events which are stored in the
store and forward table.

Parameter Table - IF.INTEGRATION.SERVICE.PARAM

Store and forward table for event messages.


Events stored here will be processed by a service or adapter
The processed events would get their timestamp updated

Contains configuration parameters for the Integration Service

Note Integration Service is not required with custom adapters


Slide 12

Event designer (Design time)


Event designer
T24
1
Service
Repository

5
Events

XSD

Integration
Framework

Flows

Source Control Management

13

Integration Framework (Run Time)


ESB

Routing

Transformation
BizTalk

JMS
Adapter

Fiorano
ESB
Adapter

IBM
Integration

Bus
Adapter

Oracle
AIA

Adapter

RM
Txn 2

(on
demand)

2b

Event Delivery Service

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

Exit points are

Asynchronous

T24 object that stores the message


before it is delivered to an external
system is

Hook, API, in T24 to which an Event


can be linked

This is the service that is specific to


Java platform to deliver the
message`

When the T24 contract / transaction


is committed.

Exit Point gets triggered

IF.EVENTS.INTERFACE.TABLE

Slide 15

Summary

Now you will be able to

State the purpose of Integration Framework


Name the Terminologies used in Integration Framework
Identify T24 Objects used in Integration Framework
Describe the design time and run-time of Integration Framework

Slide 17

Thank You

TEMENOS EDUCATION CENTRE


Warning: This document, is protected by copyright law and international treaties. No part of this document
may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any
purpose, without the express written permission of TEMENOS HEADQUARTERS SA Unauthorized
reproduction or distribution of this presentation or any portion of it, may result in severe civil and criminal
penalties, and will be prosecuted to the maximum extent possible under applicable law. Information in this
document is subject to change without notice