Evolution & Architecture of T24
Day 3 - Session 2
Evolution and Architecture of T24
Technical Courses
20/04/2011
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
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
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
Stage 3–Front End Browser
Key Features
Stateless Connection
Resilience
Scalability
Ease Of Deployment (Light Client)
5 Thesys Training Centre
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)
MQ Server
BrowserXML Request 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
Database Server - jBASE / Oracle / DB2
7 Thesys Training Centre
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
8 Thesys Training Centre
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)
Main jobs is to
• Post requests to TCS or MQ depending on the configuration
• Get responses from TCS or MQ depending on the configuration
9 Thesys Training Centre
T24 Architecture With MQ – An Insight
10 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
T24 Server T24 Server
TCS (Temenos Connector Server) TCS (Temenos Connector Server)
(Close Of Business) providedT24the
T24 with OFS MS (Multi Server) module is
with OFS
JEDI Driver & jBASE JEDI Driver & jBASE
installed
T24 Application Server Layer
11 Thesys Training Centre
T24 Application Server - TCS
Temenos Connector Server (TCS)
• Entry point into T24
• 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
SSL etc.
12 Thesys Training Centre
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
13 Thesys Training Centre
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
14 Thesys Training Centre
T24 Application Server - jBASE
Middleware
T24 run time resides on jBASE
Enables communication between T24 runtime and the Database
15 Thesys Training Centre
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
16 Thesys Training Centre
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 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
17 Thesys Training Centre
jEDI Driver – Data Storage
Application Name : SECTOR
jEDI Driver (Cont.)
• Enables storage of data in XML format [Link] DESCRIPTION [Link]
• SECTOR application when stored in
1000 Financial Financial Corps
jBASE
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
RECID XMLRECORD
orauser is the name of the
schema being used 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>
18 Thesys Training Centre
jEDI Driver – Data Storage
Application Name : SECTOR
jEDI Driver – Multi Value Support
[Link] DESCRIPTION [Link]
• 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 Table Name : ebSECTOR
external database
RECID XMLRECORD
eb is the product to which
1000 <c1>Financial Corporations</c1>
the application SECTOR <c2>Financial Corps</c2>
belongs to <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>
19 Thesys Training Centre
jEDI Driver – Data Storage
Application Name : TRAINING
jEDI Driver – Sub Value Support
[Link] DESCRIPTION TRAINER
• TRAINING application when stored
1 Basic Technical Alm
in jBASE Training Alam
• jBASE uses SM (Sub Value Marker) 2 Advanced Sara
to delimit sub values Technical Training Sheriffa
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 <c2>Alm</c2>
<c2 m=‘1’ s=‘2’>Alam</c2>
the application
1100 <c1>Advanced Technical Training</c1>
TRAINING belongs to <c2>Sara</c2>
<c2 m=‘1’ s=‘2’>Sheriffa</c2>
1200 <c1>Utilities</c1>
<c2>Ramki</c2>
<c2 m=‘1’ s=‘2’>Gerard</c2>
<c2 m=‘1’ s=‘3’>Nanda</c2>
20 Thesys Training Centre
Message Flow And Transformation From
And To Browser
IE to Web Server – HTTP Request T24 builds BROWSER XML response
T24 Browser transforms HTTP and passes it on to Tss
request to Browser XML request tSS sends the response to TCS
TCC sends the Browser XML request TCS sends the Browser XML
to TCS response to TCC
TCS sends the Browser XML request TCC sends the Browser XML
to tSS response to T24 Browser
tSS sends the Browser XML request T24 Browser converts the Browser
to T24 XML response to a HTTP response
T24 processes the request
21 Thesys Training Centre
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.
22 Thesys Training Centre
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
23 Thesys Training Centre
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
24 Thesys Training Centre
jBase File Management
Fixed byte length allocates unnecessary space
For faster data retrieval
For sequential and random access of data
25 Thesys Training Centre
File Types
File Types
Hashed File Non-Hashed
File
26 Thesys Training Centre
File Management
Every file created in jBase has
• Data Portion
• Dictionary Portion
Data Portion -> Record that has many fields
Dictionary Portion -> Field name & Properties e.g. length
Data & Dictionary files are divided into groups called modulo
27 Thesys Training Centre
Hashed Files
Stores & retrieves data randomly
Used for data and dict. files
Data files are stored as hash files
Uses Hash Algorithms to dynamically read and write data
All Globus data files are Hashed files of Type = J4
28 Thesys Training Centre
Hashed Files
J3
Types:
J4
Contains
• Modulo -> No. of frames
• Separation -> Size of a frame
29 Thesys Training Centre
Hashed Files Creation
Syntax:
[Link] <File-Name> TYPE=<File-type> <Dict.-portion>
<Data-portion>
J3 Type -> [Link] <File-Name> TYPE=J3 <Dict.-
portion> <Data-portion>
J4 Type -> [Link] <File-Name> TYPE=J4<Dict.-
portion> <Data-portion>
30 Thesys Training Centre
Hashed Files Creation
Example: [Link] [Link] TYPE=J4 4,2,3 4,3
4 2 3 4 3
Dict Modulo Dict Dict Data Modulo Data Separation
Separation Secondary
Buffer size
31 Thesys Training Centre
Hashed Files Creation
Hashed File is created as shown
32 Thesys Training Centre
Non-Hashed Files
Contains sequential files
Unix level directories
Stores Program & Report
ID < 255 characters
Stores Undefined (UD) Type files
33 Thesys Training Centre
Non-Hashed Files
No set key, length & structure
• So, record sizes vary greatly
Stores Basic Programs, executables & subroutine in
directory files
34 Thesys Training Centre
Non-Hashed Files Creation
Syntax:
[Link] <File-Name> TYPE=UD
35 Thesys Training Centre
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 : [Link]
email : marketing@[Link]