Professional Documents
Culture Documents
GEN1-Evolution and Architrecture of T24-R08.01
GEN1-Evolution and Architrecture of T24-R08.01
GEN1-Evolution and Architrecture of T24-R08.01
Slide 3
Stage 1 – Front End ‘Classic’
Globus (Application)
uniVerse (Database)
Unix/Windows (Operating
Telnet Connection System)
Client PC WithA Terminal Emulation
Software
Slide 4
Stage 2 – Front End ‘Desktop’
Globus (Application)
uniVerse/jBASE (Database)
Unix/Windows (Operating
Telnet Connection System)
Client PC With Globus Desktop
Slide 5
Stage 3–Front End Browser
Key Features
Stateless Connection
Resilience
Scalability
Ease Of Deployment (Light
Client)
Slide 6
T24 Architecture – An Overview
Web Browser Web Browser Client Web Browser Web Browser
Slide 7
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
Slide 8
Web Browser
Slide 9
Network Dispatcher
Slide 10
Web Server/Application Server
Slide 11
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
Slide 12
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.
Slide 13
Web Server – T24 Browser Servlet
Slide 14
Web Server – Temenos Connector Client (TCC)
Slide 15
Message Queuing
MQ Series
MQ Server
IBM MQ/Sun MQ etc.
Optional component of the architecture
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
Slide 16
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
Slide 17
T24 Architecture With MQ – An Insight
T24 Application Server
Slide 19
T24 Application Server - TCS
Slide 20
T24 Application Server – T24 Run Time
Slide 21
T24 Application Server – T24 Run Time
Slide 22
T24 Application Server - jBASE
Middleware
T24 run time resides on jBASE
Enables communication between T24 runtime and the Database
Slide 23
T24 Application Server – jEDI XML Driver
Slide 24
T24 Application Server – jEDI XML Driver
Slide 25
Database Server
Slide 26
jEDI Driver – Data Storage
ApplicationName:SECTOR
jEDI Driver (Cont.)
Enables storage of data in XML SECTOR.CODE DESCRIPTION SHORT.NAME
format
SECTOR application when stored in 1000 Financial FinancialCorps
jBASE Corporations
jBASE uses FM (Field Marker) to 1100 CentralBanks CentralBanks
delimit values of different fields
1200 BuildingSocieties BuildingSocs
DESCRIPTION
SECTOR table when stored in an TableName:orauser_SECTOR
external database
RECID XMLRECORD
orauser is the name of the schema
being used 1000 <c1>FinancialCorporations</c1>
Will differ from one company <c2>FinancialCorps</c2>
to another and may differ 1100 <c1>CentralBanks</c1>
from one installation to <c2>CentralBanks</c2>
another
1200 <c1>BuildingSocieties</c1>
<c2>BuildingSocs</c2>
Slide 27
jEDI Driver – Data Storage
TableName:ebSECTOR
SECTOR table when stored in an
external database RECID XMLRECORD
1100 <c1>CentralBanks</c1>
<c2>CentralBanks</c2>
1200 <c1>BuildingSocieties</c1>
<c2>BuildingSocs</c2>
Slide 28
jEDI Driver – Data Storage
ApplicationName:TRAINING
jEDI Driver – Sub Value Support
TRAINING application when TRG.CODE DESCRIPTION TRAINER
stored in jBASE
jBASE uses SM (Sub Value 1 BasicTechnical Alm
Marker) to delimit sub values Training Alam
2 Advanced Sara
TechnicalTraining Sheriffa
3 Utilities Ramki
Gerard
Nanda
TableName:stTRAINING
TRAINING table when stored in
an external database RECID XMLRECORD
st is the product to which the
application TRAINING 1000 <c1>BasicTechnicalTraining</c1>
belongs to <c2>Alm</c2>
<c2m=‘1’s=‘2’>Alam</c2>
1100 <c1>AdvancedTechnicalTraining</c1>
<c2>Sara</c2>
<c2m=‘1’s=‘2’>Sheriffa</c2>
1200
<c1>Utilities</c1>
<c2>Ramki</c2>
<c2m=‘1’s=‘2’>Gerard</c2>
<c2m=‘1’s=‘3’>Nanda</c2>
Slide 29
Message Flow And Transformation From And To Browser
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.
Slide 31
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
Slide 32
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
Slide 33
Additional Information Only
Failure Scenarios
Thank You