T24 TECHNICAL ARCHITECTURE

DateOf Issue Version Changes By

February 1.0 Initial Alagammai
2006 Palaniappan

Information in this document is subject to change without notice.

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 Holdings NV.

Copyright 2002-2003 TEMENOS Holdings NV. All rights reserved.

T24 Technical Architecture

Table of Content
Table of Content..................................................................................................................................... 2
Introduction............................................................................................................................................. 3
Technical Architecture............................................................................................................................ 3
GLOBUS And GLOBUS Desktop........................................................................................................ 3
T24 And T24 Browser......................................................................................................................... 3
Components Of T24 Browser Installation........................................................................................... 5
Internet Explorer.............................................................................................................................. 5
Network Dispatcher......................................................................................................................... 5
Web Server..................................................................................................................................... 5
MQ Server....................................................................................................................................... 6
T24 Server....................................................................................................................................... 6
bnk.data directory – NFS Mounted.................................................................................................. 6
Database Server............................................................................................................................. 6
Message Flow........................................................................................................................................ 6
Message In......................................................................................................................................... 6
Message Out....................................................................................................................................... 6

TEMENOS Training Publications Page 2 of 7 February 2006

T2ITT – R05 – 1.0
T24 Technical Architecture

Introduction
The term T24 refers to ‘Temenos 24’ meaning 24 hours NON-STOP processing where by transactions
can be input while the system is running ‘Close Of Business’ (End Of DAY). For the T24 non-stop
processing to be implemented, there are a number of technical and architectural changes that have
been made. This document aims at giving an insight into the technical and architectural changes done
to T24.

Technical Architecture

GLOBUS And GLOBUS Desktop

All this while, GLOBUS and its database jBASE/uniVerse used to exist in the same server along with
the operating system and GLOBUS Desktop would be installed on all client machines . Whenever a
client wishes to access data in GLOBUS, it used to be done using Desktop and there used to exist a
physical network connection between the client and the server. The communication between GLOBUS
Desktop and the GLOBUS server would be a telnet connection. It should be noted that GLOBUS
Desktop is a thin client that needs deployment on all client machines that need to access data but
does not hold any business logic.

Client Machine with Client Machine with Client Machine with Client Machine with
GLOBUS Desktop GLOBUS Desktop GLOBUS Desktop GLOBUS Desktop

GLOBUS Server
 GLOBUS
 jBASE/uniVerse
 Unix/NT

T24 And T24 Browser

T24 Browser is an Intranet based browser solution, designed as an accompaniment to the existing
GLOBUS Desktop software. It is not a replacement for Desktop, but rather a complementary product
that offers basic functionality (i.e. contract capture and enquiries), needed for large-scale
implementations - without the need to install software on client PCs. T24 Browser is a ‘light client’,
which like Desktop does not hold any business logic but does not need to be installed at any of the
client machines (no deployment required). With the advent of T24 Browser, there will exist many
layers in the T24 technical architecture. These layers are built in for resilience so that there is no single
point of failure henceforth.

TEMENOS Training Publications Page 3 of 7 February 2006

T2ITT – R05 – 1.0
T24 Technical Architecture

Web Web Web Web

Browser Browser Browser Browser
Clients

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 Client) TCC(Temenos Connector Client) TCC(Temenos Connector Client)
Web Server Layer

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

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

NFS Mounted bnk.data

OFS Request Directory OFS Response

Database Server Database Server Database Server

Oracle/DB2/SQL Oracle/DB2/SQL Oracle/DB2/SQL
Server/jBASE Server/jBASE Server/jBASE

Database Layer

TEMENOS Training Publications Page 4 of 7 February 2006

T2ITT – R05 – 1.0
T24 Technical Architecture

Components Of T24 Browser Installation

Internet Explorer
This is the front end that the clients will be using to access data in T24. All that the user needs to do is
to supply a ‘url’ that will enable him to connect to T24.

Network Dispatcher
This is a third party software. The job of the network dispatcher is to receive the messages from the
IE, and route it to any one of the available web servers. This is used for load balancing purposes.

Web Server
Web server handles the HTTP protocol. When the Web server receives an HTTP request, it responds
with an HTTP response, such as sending back an HTML page. To process a request, a Web server
may respond with a static HTML page or image, send a redirect, or delegate the dynamic response
generation to some other program such as CGI scripts, JSPs (JavaServer Pages), servlets, ASPs
(Active Server Pages), server-side JavaScripts, or some other server-side technology. Whatever their
purpose, such server-side programs generate a response, most often in HTML, for viewing in a Web
browser.
Web server's delegation model is fairly simple. When a request comes into the Web server, the Web
server simply passes the request to the program best able to handle it. The Web server doesn't
provide any functionality beyond simply providing an environment in which the server-side program
can execute and pass back the generated responses. The server-side program usually provides for
itself such functions as transaction processing, database connectivity, and messaging.
While a Web server may not itself support transactions or database connection pooling, it may employ
various strategies for fault tolerance and scalability such as load balancing, caching, and clustering—
features oftentimes erroneously assigned as features reserved only for application servers.

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.
For T24, a web server is sufficient.
Following web servers are supported by T24
 Apache Tomcat
Following application severs are supported by T24
 IBM Web Sphere
 Oracle Application Server
As an example, when a user wishes to open a version, then the fields to be displayed and their
properties are sent to the web server. The web server then creates the web page and sends it to the
user via the network dispatcher. The sessions are persisted on to a database at the web server level.
The web server holds the TCC (Temenos Connector Client) and the T24 Browser. The T24 Browser is
the one that will parse any HTTP request to XML request and send it for further processing. The Web
Server is capable of storing tokens that are related to each message (Tokens is discussed in detail
later in this section). TCC is an API published by T24 that enables various third party tools to
communicate with T24 using these APIs.

TEMENOS Training Publications Page 5 of 7 February 2006

T2ITT – R05 – 1.0
T24 Technical Architecture

MQ Server
MQ stands for message queuing. This piece of software enables load balancing and message queuing
and guarantees message delivery. Following message queuing software is widely used in T24
implementations
 IBM MQ
 Sun MQ

T24 Server
This is the T24 server and there can be more than one of them. Each of these servers will contain a
separate T24 installation (minus the bnk.data directory) and jBASE installation. The OFS module
and the TCS (Temenos Connector Server) have to be compulsorily installed on each of these servers.
TCS is the entry point into T24. It is in the T24 server, that all the business logic is held and the actual
validation of data happens at this server. The JEDI (jBASE external database interface) driver enables
communication between T24 and external databases.

bnk.data directory – NFS Mounted

This is the T24 ‘data’ directory that is mounted on to a network file system. All T24 servers will access
this ‘data’ directory when they need any information. The data files in this directory will not contain any
data. They will only contain references to the related Oracle/DB2/SQL Server tables where the data is
actually stored.

Database Server
T24 is database independent, and supports several different databases, including Oracle,DB2,SQL
Server and J4(jBASE). It is in this database server that Oracle/DB2/SQL ServerJ4 is installed. This is
where the T24 data will reside in XML format. Oracle/DB2 databases support clustering and therefore
a single Oracle/DB2 installation can be done across multiple servers. J4 does not support clustering
and therefore only one database server can be used if J4 is to be used as a database. In order to
make use of T24 capabilities, we would require the database to provided online backup mechanism
(taking backup when users are logged in).

Message Flow
Message In
The user initiates a request from the Internet Explorer. This will be a HTTP request. This request is
received by the Network Dispatcher and is routed to any one of the Web Servers. The T24 Browser
which resides on the Web Server parses the HTTP request to XML and passes it on to the TCC
running on the same server. The TCC then routes the request to any one of the T24 servers via MQ.
Though MQ the request reaches TCS. As mentioned above, the entry point into T24 is the TCS. The S
running on the T24 server then parses the XML request into OFS format and gives it to T24 (OFS) for
processing. Then the request is processed and the database is updated. At this point the jBASE
drivers are used to convert the data into XML format and then the data is updated in the database.

Message Out
Once the database update is complete, the response is sent to any one of the T24 servers. The jEDI
driver parses the response to OFS format and gives it to TCS. TCS then places the response in MQ.
From there, the TCC(running on any one WebServer)picks up the response and passes it on to the
T24 Browser running on the same server. The T24 Browser then does any required processing on the
response and sends the HTML response to the network dispatcher. The network dispatcher then
sends it to the appropriate Internet Explorer screen. The Web Server has the in built intelligence using

TEMENOS Training Publications Page 6 of 7 February 2006

T2ITT – R05 – 1.0
T24 Technical Architecture

which it can decide which IE session initiated the request and hence will instruct the next layer to send
the response to the IE session that actually initiated the request.

TEMENOS Training Publications Page 7 of 7 February 2006

T2ITT – R05 – 1.0