Evolution & Architecture of T24

Day 1

Session 1 & 2
Induction Trainings

Evolution and Architecture of T24

 Objectives

At the end of the session you will have

` Adequate knowledge to understand
• Evolution of T24
– Classic
– Desktop
– Browser

• Multi-tier architecture – An Overview

2 Thesys Training Centre

Slide 2
 Stage 1 – Front End ‘Classic’
Client PC With A Terminal Emulation
Software Globus Server

Globus (Application)
uniVerse (Database)
Unix/Windows (Operating
Telnet Connection System)
Client PC With A Terminal Emulation
Software

Client PC With A Terminal Emulation

Software

Terminal Emulation Software

Example : Reflection, Putty

3 Thesys Training Centre

Slide 3
 Stage 2 – Front End ‘Desktop’
Client PC With Globus Desktop
Globus Server

Globus (Application)
uniVerse/jBASE (Database)
Unix/Windows (Operating
Telnet Connection
Client PC With Globus Desktop System)

Client PC With Globus Desktop

4 Thesys Training Centre

Slide 4
 Stage 3–Front End Browser

Key Features

` Stateless Connection

` Resilience

` Scalability

` Ease Of Deployment (Light Client)

5 Thesys Training Centre

Slide 5
T24 Architecture – An Overview
Web Browser Web Browser Client Web Browser Web Browser

Http Request Network Dispatcher Http Response

Web Server Web Server Web Server

ƒ Tomcat / WebSphere / Oracle ƒ Tomcat / WebSphere / Oracle ƒ Tomcat / WebSphere / Oracle

application Server application Server application Server
ƒ T24 Browser ƒ T24 Browser ƒ T24 Browser
ƒ TCC (Temenos Connector ƒ TCC (Temenos Connector ƒ TCC (Temenos Connector
Client) Client) Client)
Web Server Layer (Presentation Layer)

BrowserXML Request
MQ Server BrowserXML Response
IBM MQ / Sun MQ etc

T24 Server T24 Server

ƒTCS (Temenos Connector ƒTCS (Temenos Connector
BrowserXML Server) Server) BrowserXML
Request Response
ƒT24 with OFS ƒT24 with OFS
ƒJEDI driver & jBASE ƒJEDI driver & jBASE
T24 Application Server Layer

Database Server Database Server Database Server

ƒOracle / DB2 / MS ƒOracle / DB2 / MS ƒOracle / DB2 / MS
SQL / jBASE SQL / jBASE SQL / jBASE
6 Database Server Layer Thesys Training Centre

Slide 6
Understanding The Components Of
The Multi Tier Architecture
` Web Browser
` Network Dispatcher
` Web Server/Application Server
– Web Server Software / Application Server Software
– T24 Browser Servlet
– Temenos Connector Client

` Message Queuing Software

` T24 Application Server
– Temenos Connector Server
– T24 Runtime
– jBASE
– jEDI XML Oracle Driver

7
` Database Server - jBASE / Oracle / DB2
Thesys Training Centre

Slide 7
 Web Browser

` This forms the top layer in our T24 architecture

` Standard web browsers T24 supports are Internet Explorer and Mozilla
firefox

8 Thesys Training Centre

Slide 8
 Network Dispatcher

` Network Dispatcher /Load Balancer

• Routes requests from the web browser to any one of the available Web Servers

9 Thesys Training Centre

Slide 9
 Web Server/Application Server
Can be a Web Server or an Application Server

Web Server Web Server Web Server

Tomcat/Web sphere/Oracle Application Server Tomcat/Web sphere/Oracle Application Server Tomcat/Web sphere/Oracle Application Server
T24 Browser T24 Browser T24 Browser
TCC (Temenos Connector Client) TCC (Temenos Connector Client) TCC (Temenos Connector Client)

Web Server Layer

In order to use T24 with Browser as the front end, a Web

Server would suffice
All that T24 requires is a servlet container

10 Thesys Training Centre

Slide 10
 What Is A Web Server?

` Web Server
• Handles the HTTP protocol
• Receive a HTTP request
• Respond with a HTTP response
• Works on a delegation model
• Receives a request
• Passes on the request to the program that can best handle the request (In this
case T24 Browser)
• Example : Tomcat

11 Thesys Training Centre

Slide 11
 What Is An Application Server?

` Application Server
• Exposes business logic to client applications through various protocols
• While a Web server mainly deals with sending HTML for display in a Web
browser, an application server provides access to business logic for use by
client application programs
• Exposes business logic through a component API, such as the EJB (Enterprise
JavaBean) component model found on J2EE (Java 2 Platform, Enterprise
Edition) application servers
• Example : Web sphere, Oracle application Server etc.

12 Thesys Training Centre

Slide 12
 Web Server – T24 Browser Servlet

` T24 Browser Servlet is supplied by Temenos

` Transforms the incoming HTTP request into a BROWSER XML request
` Passes on the request to Temenos Connector Client

13 Thesys Training Centre

Slide 13
 Web Server – Temenos Connector Client
(TCC)
` Temenos Connector Client (TCC) is a client component written in java
` Embedded into the T24 Browser Servlet
` Written using the APIs published by the Temenos Connector Service
(TCS)
` Can communicate
• To TCS directly using tcp, ssl etc
• To a message queuing software like IBM MQ, SUN MQ etc

` Main jobs is to
• Post requests to TCS or MQ depending on the configuration
• Get responses from TCS or MQ depending on the configuration

` TCS has a published set of APIs. Hence custom TCCs can be developed
for interface requirements
14 Thesys Training Centre

Slide 14
 Message Queuing
MQ Server
IBM MQ/Sun MQ etc.
` MQ Series
• Optional component of the architecture
• Enables storage and forward of messages
• Receive requests from
III party systems
TCClient API

• TCC posts (mqput) requests to MQ

• TCS picks up requests (mqget) from MQ
• TCS posts responses(mqput) to MQ
• TCC picks up responses(mqget) from MQ
• Example : IBM MQ, Sun MQ or any JMS Compliant message queuing system

15 Thesys Training Centre

Slide 15
 Message Queuing

` MQ could be installed on
• A separate server dedicated for MQ
• Multiple dedicated servers for MQ when MQ clustering is required
• The T24 application servers
• Web servers
• T24 application servers and Web servers when clustering is required
• When MQ is used, TC Servers pick up requests from MQ - Race Condition

16 Thesys Training Centre

Slide 16
 T24 Architecture With MQ – An Insight

17 Thesys Training Centre

 T24 Application Server
` T24 Application Server
• Holds the T24 business logic – T24 run time
• Does not store data. All data is stored at the database server layer
• Each of the servers are identical copies of the other
• The servers do not speak to each other and hence are totally independent of
each other
• All T24 application servers can be used while running COB (Close Of
Business) provided the MS (Multi Server) module is installed

T24 Server T24 Server

TCS (Temenos Connector Server) TCS (Temenos Connector Server)
T24 with OFS T24 with OFS
JEDI Driver & jBASE JEDI Driver & jBASE

T24 Application Server Layer

18 Thesys Training Centre

Slide 18
 T24 Application Server - TCS
` Temenos Connector Server (TCS)
• Entry point into T24
• Server component in the TCC – TCS architecture
• Written in java
• Launches tSS processes to communicate with T24 Run Time
• Number of tSS processes to launch is configurable
• Can scale up or scale down tSS processes depending on the number of
requests
• Receives requests from TCC or fetches requests from MQ
• Keeps responses ready for TCC or posts responses to MQ
• Can attach user defined request/response formatters to TCS
• Offers different ways of connection with T24
MQ Series
TCP
19
SSL etc. Thesys Training Centre

Slide 19
 T24 Application Server – T24 Run Time

` Is the business logic of T24

` Contains library files and executables
` Library files (contain object codes) and executables are produced by
compiling code using the ‘C’ compiler

20 Thesys Training Centre

Slide 20
 T24 Application Server – T24 Run Time

` Contains the standard interface module in T24 called OFS

` OFS works on
• Request – Response based approach
• Provides options to customize message processing through user-defined
subroutines (User exits)
• Support for multi-value and sub-value data
• Support for multi company processing
• Can receive requests from
III party systems
Temenos Connector Server

• Supports logging of messages and optional audit trail for each message

21 Thesys Training Centre

Slide 21
 T24 Application Server - jBASE

` Middleware
` T24 run time resides on jBASE
` Enables communication between T24 runtime and the Database

22 Thesys Training Centre

Slide 22
 T24 Application Server – jEDI XML Driver

` jEDI stands for jBASE External Device Interface

` jEDI XML Driver is used to communicate with external databases such as
Oracle, DB2 and SQL Server
` When jBASE is the database, a jEDI XML Driver is not required for
communication with the database layer
` Driver is database specific
• jEDI XML Oracle driver
• jEDI XML DB2 driver

23 Thesys Training Centre

Slide 23
 T24 Application Server – jEDI XML Driver
` Needs to be installed on each of the T24 application servers
` Contains the database details of the external database such as
• Database name
• User name and password (encrypted) to log on to the external database
• Schema name, Table space name, Role name etc. (When Oracle is used).

` Establishes connection to the external database residing on the database

server
` Converts all T24 requests into SQL/DML/DDL statements and sends it to
the external database. Performs the vice versa for responses

T24 Server T24 Server

TCS (Temenos Connector Server) TCS (Temenos Connector Server)
T24 with OFS T24 with OFS

jBASE & jEDI Driver jBASE & jEDI Driver

T24 Application Server Layer

24 Thesys Training Centre

Slide 24
 Database Server
` Holds all the data
` Oracle, DB2, SQL Server or jBASE can be used as the database
` Oracle RAC installation done for support of multiple servers and data
stored in a Storage Area Network Disk
` Multiple servers are used for resilience
` When a database supports clustering, multiple database servers can be
used, else only one
` When jBASE release prior to 1.5 is used, only one database server can
be used as jBASE releases prior to 1.5 do not support clustering

25 Thesys Training Centre

Slide 25
 jEDI Driver – Data Storage
Application Name : SECTOR
` jEDI Driver (Cont.)
• Enables storage of data in XML format SECTOR.CODE DESCRIPTION SHORT.NAME

• SECTOR application when stored in

jBASE 1000 Financial Financial Corps
Corporations
• jBASE uses FM (Field Marker) to delimit
1100 Central Banks Central Banks
values of different fields

1200 Building Societies Building Socs

• SECTOR table when stored in an DESCRIPTION

external database Table Name : orauser_SECTOR

orauser is the name of the schema RECID XMLRECORD

being used
Will differ from one company to
another and may differ from
one installation to another
1000 <c1>Financial Corporations</c1>
<c2>Financial Corps</c2>
1100 <c1>Central Banks</c1>
<c2>Central Banks</c2>
1200 <c1>Building Societies</c1>
<c2>Building Socs</c2>

26 Thesys Training Centre

Slide 26
 jEDI Driver – Data Storage
Application Name : SECTOR
` jEDI Driver – Multi Value Support
SECTOR.CODE DESCRIPTION SHORT.NAME
• SECTOR application when stored in
jBASE
1000 Financial Financial Corps
• jBASE uses VM (Value Marker) to Corporations Financial Insts
delimit multi values Financial Entities
• jBASE uses SM (Sub Value Marker) to 1100 Central Banks Central Banks
delimit sub values
1200 Building Societies Building Socs

• SECTOR table when stored in an

external database
eb is the product to which the
application SECTOR belongs to
27
Table Name : ebSECTOR
RECID XMLRECORD
1000 <c1>Financial Corporations</c1>
<c2>Financial Corps</c2>
<c2 m=‘2’>Financial Insts</c2>
<c2 m=‘3’>Financial Entities</c2>
1100 <c1>Central Banks</c1>
<c2>Central Banks</c2>
1200 <c1>Building Societies</c1>
<c2>Building Socs</c2>
Thesys Training Centre

Slide 27
 jEDI Driver – Data Storage
Application Name : TRAINING
` jEDI Driver – Sub Value Support
TRG.CODE DESCRIPTION TRAINER
• TRAINING application when stored in
1 Basic Technical Alm
jBASE Training Alam
• jBASE uses SM (Sub Value Marker) 2 Advanced Sara
Technical Training Sheriffa
to delimit sub values
3 Utilities Ramki
Gerard
Nanda

Table Name : stTRAINING

• TRAINING table when stored in an

RECID XMLRECORD
external database
1000 <c1>Basic Technical Training</c1>
st is the product to which the
<c2>Alm</c2>
application TRAINING belongs <c2 m=‘1’ s=‘2’>Alam</c2>
to 1100 <c1>Advanced Technical Training</c1>
<c2>Sara</c2>
<c2 m=‘1’ s=‘2’>Sheriffa</c2>
1200 <c1>Utilities</c1>
<c2>Ramki</c2>
<c2 m=‘1’ s=‘2’>Gerard</c2>
28
<c2 m=‘1’ s=‘3’>Nanda</c2>
Thesys Training Centre

Slide 28
 Message Flow And Transformation From
And To Browser
` IE to Web Server – HTTP Request
` T24 Browser transforms HTTP
request to Browser XML request
` TCC sends the Browser XML request
to TCS
` TCS sends the Browser XML request
to tSS
` tSS sends the Browser XML request
to T24
` T24 processes the request
29
` T24 builds BROWSER XML response
and passes it on to Tss
` tSS sends the response to TCS
` TCS sends the Browser XML
response to TCC
` TCC sends the Browser XML
response to T24 Browser
` T24 Browser converts the Browser
XML response to a HTTP response
Thesys Training Centre
Slide 29
 Message Formats That T24 Handles

` Browser XML
• Published
No

• Who can use this?

Used only when front end is Browser

• Can interfaces send requests in Browser XML?

No. It is not a published XML.

30 Thesys Training Centre

Slide 30
 Message Formats That T24 Handles

` OFSML
• Published
Yes

• Who can use this?

Any interface that wants to interact with T24 can use this

• Who transforms OFSML to OFS and vice versa?

TCS

• If an OFSML request is posted to tSS directly, will it be able to handle the

request
No

31 Thesys Training Centre

Slide 31
 Message Formats That T24 Handles

` OFS
• Native T24 message format
• Not an XML message format
• Is the OFS format available for interfaces to use?
Yes

• Can messages in OFS format be sent to TCS?

Yes

• Can messages in OFS format be sent to tSS?

Yes

32 Thesys Training Centre

Slide 32
All product names and other company names used herein are for identification purposes only and may be
trademarks or registered trademarks of their respective owners. Errors and omissions excepted,
all specifications are subject to change without notice.

© 2009 Thesys Technologies Incorporated. All rights reserved.

FOR MORE INFORMATION

Visit : www.thesys.co.in
email : marketing@thesys.co.in