Welcome to the T24 Evolution and Architecture Course

1
Here is the agenda of this course. We will start with the Learning
Objectives

2
Here are our Learning Objectives

3
We will now look at a definition

4
Software Architecture is conceptual and is about fundamental things. It is
high-level design and is an overall structure of the system.
Architecture is the structure, including the principles and guidelines
governing their design and evolution over time and includes several
components and connectors.

5
We now look at the Evolution of this Architecture

6
T24’s architecture has undergone major changes so far. You will now learn
about how these changes came to be. What you see here is a very simple
T24 architecture. T24 was previously called GLOBUS. The very early
implementations of GLOBUS had a simple client-server architecture. The
database that was used previously was a product of IBM, called uniVerse.
1. In a typical client-server architecture, GLOBUS and uniVerse were
installed on one Server called the Application Server.
2. In this type of architecture, the clients PCs had to use a terminal
emulation software to access GLOBUS. A terminal emulation software will
allow the users access to a text terminal and to all its applications such as
command line interfaces (CLI) and text user interface applications through
telnet, ssh, or dial-up. There are lots of terminal emulation software
available like putty and reflection.
3. All client machines connected to the GLOBUS Server used a telnet
protocol.
4. Founded 1993

7
What you see here are sample screens of the Character User Interface.
This character User Interface is also called as Classic. Though this type of
an architecture was used in the initial stages, this architecture is not
completely washed away. You can still work with the Character User
Interface of T24 even today.

1. Here is the sign on screen where a user can provide username and
password to login.
2. Then you see the first screen that a user will see after login. The initial
screen might differ depending upon the user profile settings of the
logged in user. What you see here is the Application prompt.
3. Lastly you see a sample application screen.

8
From 1995, GLOBUS moved away from its classic user front end to a
Graphical User Interface front end, called the GLOBUS Desktop. It was a
client software written in Visual Basic. In this architecture too GLOBUS
with its database – universe or jBASE used to exist on a server along with
the operating system. The operating system could be Windows or Unix.
GLOBUS Desktop had to be installed on all client machines and it
connected to the server via a telnet connection. jBASE also supported a
socket connection to the server. It should be noted that the GLOBUS
Desktop was a thin client that needed to be deployed on all client
machines and did not hold any business logic.

9
1995 What you see here are sample screens of the Graphical User
Interface, Globus Desktop.
1. First you see the sign on screen
2. Then a sample Application screen

You must remember that Release7 and above do not support Globus
Desktop. You should either use the Classic Interface or a web browser to
access T24.

10
T24’s architecture changed drastically from release R04 . A web browser software like
Internet Explorer or Mozilla Firefox can now be used as the User Interface. This change
introduced a lot of new layers to the T24 architecture. From release R4 onwards,
Globus was renamed to T24 due to its massive improvement on the technology front.
T24 stands for Temenos 24. 24 denoted 24 hour non stop processing. At this time,
Temenos started working on a front end known as T24 Browser. T24 Browser is an
Intranet based browser solution. It was initially designed to accompany the existing
GLOBUS Desktop software. It was not a replacement for Desktop back then, but rather
a complementary product that offered basic functionality like contract capture and
enquiries. It was ideal for large-scale implementations because it eliminated the need
to install Globus Desktop software on client PCs. Today, T24 Browser is the standard
front end for T24. With the advent of the T24 Browser, many layers now exist in the
T24 technical architecture. These layers are built-in for resilience so that there is no
single point of failure henceforth.
What you see here is a simple architecture drawn to understand the new multi-layer
architecture.
1. The client software used to access T24 can be any browser which is compliant with
T24 Browser. You can use browsers like Internet Explorer and Mozilla Firefox as a
client. This has to be installed on all client PCs.
2. The Web Server layer can hold one or more web servers. A Web Server will serve
the client. Any request coming from a client will be processed by the Web Server.
The Web Server receives the request from the client and forwards it to the T24
Application Server. It also sends back the processed response to the client.
3. Like the Web Server Layer, the T24 Application Server Layer can have one or more
T24 Application Servers. It will receive the requests from the Web Server, process
it and send back a response to the Web Server. Each T24 Application Server will
have jBASE installed. The reason for this is that it provides the run-time for T24
4. The Database Server Layer is where all the T24 data is stored.

11
What you see here are sample T24 Browser Screens.
1. This is the T24 Sign on screen for a client accessing T24 via a Web
Browser.
2. This is the home page for the logged in user, this might differ from user
to user, depending upon the User profile settings.
3. This a sample Application screen.

12
We are now able to deploy T24 on a java platform.
• Pick Basic Runtime/Compiler in JAVA for a JVM 1.6 and above
• Compile once deploy anywhere (T24 ends up being 1 .jar
file)
• With TAFJ, T24 runs 100% inside JEE Application Server
• Standard clustering and scalability mechanism inherent to
JEE Application server
• Runtime completely separated from database
• Support of Oracle, DB2, MSSQL
• Tested on WebSphere, WebLogic, JBOSS

13
We will now learn about the components of this architecture

14
T24 stands for Temenos 24. 24 denotes 24 hours non stop processing. T24
Browser is an Internet based browser solution and is the standard front
end for T24. With the advent of T24 Browser, there exist many layers in
the T24 architecture. These layers are built in for resilience so that there is
no single point of failure.
1. The client software used to access T24 can be any T24 compliant
browser. You can use browsers like Internet Explorer and Mozilla Firefox as
a client. This has to be installed on all client PCs
2. With TAFJ, T24 runs 100% inside JEE Application Server
3. The Database Server Layer is where all the T24 data is stored.
Oracle AQ – Oracle Advanced Queuing

15
One of the highlights of the T24 design architecture is its run-time technology independence.
T24 is available on three platforms C, Java and .Net.
TAFC – Temenos application framework C
TAFJ – Temenos application framework Java
TAF.Net – Temenos application framework .Net

Interaction Framework – Framework for varied user interfaces like ARC Mobile, ARC IB, T24
Browser, Design Studio, TCIB etc. to communicate with T24
Component Framework – Framework to componentize T24 into independent implementable
components.
Integration Framework – Framework for T24 components to integrate and communicate with
non-T24 banking systems.
Platform Framework – Framework to make T24 independent of the platform to utilize the full
functionality provided by the platform.

16
• TAFJ (Temenos Application Framework Java) is Temenos proprietary
runtime and compiler for jBC code, written in 100% java. It allows
compiling and running jBC programs on Java. jBC code is parsed by the
TAFJ parser and compiled by javac compiler and translated into
equivalent Java classes. The java compliant files generated can then be
run in a JVM taking the full advantage of Java functionality like
portability, platform independence etc.
• TAFJ has been written specifically for T24 needs thereby allowing T24 to
be deployed on J2EE application Servers. This enables T24 to harness
the full functionality of J2EE application servers like connection pooling,
threading, security etc.
• TAFJ also manages the connectivity on JDBC compliant databases like
Oracle, Microsoft SQL Server, DB2, DB2 – zOS

17
What’s in it for a developer ?

 Development on a market standard IDE

 Excellent debugger for efficient and faster bug fixing

 Help is just a click away …. Google your queries. For e.g. if you
want to configure a Printer on Linux, simply Google CUPS. This is so
because all software's used are contemporary market standards.

An integrated development environment (IDE) or interactive development

environment is a software application that provides comprehensive
facilities to computer programmers for software development. An IDE
normally consists of a source code editor, build automation tools and a
debugger. Most modern IDEs offer Intelligent code completion features.

18
A TAFJ standalone is nothing but just the TAFJ runtime and the
precompiled jars of a T24 release like R12 along with a backend database.
You can run T24 classic in this setup from a VT100 console.

The application server setup is required if you need to connect to T24 via
the Browser frontend.

19
Use java –version at your command prompt to check the java version
installed in your machine. It should be 1.6 or above. If the version
reported is not 1.6 (or above), you should install it. Java JDK can be
downloaded here:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
Set-up an environment variable called JAVA_HOME pointing to the root
directory of your java installation. Then, reference JAVA_HOME/bin in your
PATH environment variable.

20
 After unzipping you will notice Patch.xxx and Setup.xxx and a jar file. To do
a fresh TAFJ installation from scratch and not starting from the dev image,
then run the Setup. This will create a folder (name it as TAFJ for
convenience) with all the runtime related files. This folder becomes your
TAFJ_HOME.

[Note : For upgrading the runtime in an existing DEV image, we make use
of “Patch_TAFJ.<version>.bat” on windows and “Patch_TAFJ.<version>.sh”
for Unix. If however the upgrade is from a very low version to the recent
version , then a Setup_TAFJ.<version>.bat/sh is advised. ]

Temenos University 21 21
1. Set your JAVA_HOME to the location of your JDK
2. Run the Setup.xxx.bat file. Specify a location for your TAFJ_HOME. This
creates a folder called TAFJ by default. This folder contains all the
runtime files and is referred to as <TAFJ_HOME>
3. Copy the appropriate H2 database drivers from
<TAFJ_HOME>\dbdrivers\<database> to <TAFJ_HOME>\ext.
[Note: The H2 database version can be identified from the h2<Version>.jar
in <h2_home>\bin. For e.g. - h2-1.3.161.jar]

22 22
Let us understand TAFJ_HOME in detail. This folder contains the TAFJ Runtime files
Appserver - Application server configuration files are kept here. These files are necessary for deploying
T24 on AS like jboss, Websphere, Weblo, etc.
Bin - executable scripts (tRun, tCompile, ...).
CodeCoverage – contains cobertura jars for calculating and reporting test coverage. Primarily used in
regression tests
Conf - configuration directory where the project property files are maintained.
Data - Contains 2 folders - classes and java. Classes folder holds .class files generated and java folder
holds .java files generated, on compiling a jBC code.
Dbdrivers - drivers of the various databases supported in TAFJ can be found in this folder, for use if
needed.
Dbscripts – when you install a new database instance of say H2 or oracle, you need to run some stored
functions on the database to ready the new database for storing T24 data. These are available as scripts
in this folder, database wise.
Eclipse – contains the tafj plugins which enable jBC coding in eclipse IDE. These must be linked/added to
the plugins or dropins folder of your eclipse software.
Ext - This directory contains all java classes (or jars) ‘extending’ or ‘replacing’ the T24 jBC subroutines.
Additionally this is the folder to keep the external jars like jbossall-client.jar for jboss which contains all
the client class of jBoss, database drivers, component framework jars etc.
JMSInjector – Contains JMSInjector to inject OFS into queues - for benchmark
Lib - TAFJ runtime libraries. Regression – contains scripts to perform regression testing.
Doc – TAFJ user guides. Log and log_T24 – end to end runtime logs and T24 logs for splunk
respectively
Samples – sample basic codes TAFJSessionMonitor – contains TAFJ MW42 monitor.
RELEASE – contains code fix info Pom.xml – required for running maven builds

23
3. Edit your default property file in your new <TAFJ_HOME>\conf. You can
identify the default property file from the .default file. It should be
tafj.properties.
4. Note that the property tafj.home is already set to your new
<TAFJ_HOME> based on the directory that you specified when running
Setup.
5. Set the precompile path in the property temn.tafj.directory.precompile
to the location of your T24 core libraries.
6. Set your database URL, driver, username and password properties to
point to the H2 database
[Note : The URL description and the specific driver information for each
database is mentioned under the Database Setup section. For H2 it is
jdbc:h2.tcp://<host or IP>:<port No>/<db_name>. The default H2 port is
9082. Since we are starting H2 at port 9007, the same is mentioned. The
database name is DEV. For the H2 database that we are using the
username is tafj and password is tafj]

24 24
9. From a vt100 console execute the command tRun EX to launch T24
Classic.

[Note: Execute tRun from <tafj_home>\bin]

25 25
26 26
27 27
When you execute a tafj command, a check is made to see if you have used
the –cf option with the command. If the configuration file exists, then the
properties settings of the configuration file specified are used for execution.
If –cf option is not used, then a check is made to see if the .default file exists.
If yes, read .default entry. If the configuration file specified in .default exists
then use that file, else use tafj.properties which is the default. If
tafj.properties is not available, then display error.

28 28
tafj.home - points to the TAFJ folder in your tafj area which contains the
runtime libraries and other related files.
temn.tafj.directory.basic, folder location to all your basic source files. You
can specify multiple paths with the separators “:” or “;”.
temn.tafj.directory.insert, folder location where the INSERT files for your
project is kept. The Insert file can be in the basic source folder itself or in a
different path.
temn.tafj.directory.java, folder location where the java source files should
be generated. This property is mandatory and you can set only one path.
temn.tafj.directory.classes, folder location where the classes files should
be generated. This property is mandatory and you can set only one path.
temn.tafj.directory.precompile, refers to the folder location where the
precompiled class files are kept. Usually contains the precompiled t24
class files required by your t24 basic code. Multiple paths can be specified
using the separators. The precompile paths are overridden by
”temn.tafj.directory.classes” paths. For e.g. you have a class TEST.SUB in
the precompile path. You compile a TEST.PRG which inturn calls TEST.SUB.

29 29
 In this case the TEST.SUB in the precompiled path will be called. Now if you
generate a new TEST.SUB in classes path, then TEST.PRG will not call the
TEST.SUB in the precompile path. Instead it calls the one in the classes
path. This path could be a folder or JAR file.
[Note : The preferred location for T24 precompiled is <t24_home>/lib in
your Dev area]

Temenos University ‹#› 29

To connect to T24 using the Browser we have to setup the application. We
will use Jboss for out illustration.

30
The TAFJ J2EE application is packaged as one enterprise archive file -
TAFJJEE_EAR.ear. An EAR (Enterprise ARchive) is a file format used by Java
EE for packaging one or more modules into a single archive. The modules
packaged into TAFJJEE_EAR.ear are
1. TAFJJEE_MDB.jar – contains all the MDB (Message driven bean) classes
which listens for messages to arrive on a JMS queue or topic. The MDB’s
act as consumers of messages which come from the various message
sources for e.g., Browser, ARCIB, TWS etc.

2. TAFJJEE_EJB.jar – contains EJB’s (either local or remote). They act as

interfaces to T24 code.
3. TAFJJEE_WAR_TAFJ.war – contains a simple servlet to send message in
the EXEC JMS Queue to execute commands on the TAFJ Runtime for e.g.,
tRun START.TSM.

The EAR facilitates the deployment of the various modules onto an

31
 application server to happen simultaneously and coherently. It also
contains XML files called deployment descriptors which describe how to
deploy the modules. In addition to the TAFJ-EE package, we must also have
the T24 precompiled libraries and the TAFJ Runtime libraries on the jBoss
AS.

Temenos University ‹#› 31

So what are the advantages…

32
Introduction to External Database

1 In order to create a new CUSTOMER, a record must be created

and committed. The user can use any T24 front end like Browser or
Classic to do this.

2 T24 always validates data before it is updated to the database.

3 Once the validations are through, the record is ready to be stored.

The logic in the Customer application tells the system to write it to
the table FBNK.CUSTOMER. But where is this table located?

4 Unlike TAFC, TAFJ does not use the VOC file to locate the
database table.

Temenos University 33 33
Introduction to External Database

The DB Drivers can be found under TAFJ_HOME/dbdrivers

There is some configuration done in the TAFJ properties file.

The database URL is used to connect to the database.

Temenos University 34 34
Introduction to External Database

1 In the detailed T24 architecture diagram, you may have noticed multiple database servers in
the database layer. This is possible only when an external database is used and if the database
in turn supports clustering. This has nothing to do with T24, as the functionality is controlled
entirely by the external database.
2 To connect to the database you will need to configure the corresponding JDBC Driver. This
must be configured on each application server.
3 There are a few pre-requisites that come with each release of T24 depending on the External
Database chosen. For example, the T24 R15 using Oracle, would need
R15 version of TAFJ
ORACLE Version 11g. Or higher

Temenos University 35 35
Introduction to External Database

1 All T24 data tables in Oracle will have only two columns.
2 One to store the ID and the next to store the entire data record
delimited with XML tags.
3 This is done because Oracle does not support the multi-value, sub-
value concept that T24 uses widely.

4 The naming conventions used for the table names in Oracle are
similar to the ones used in jBASE, the only difference being dots are
changes to underscores and dollar signs are changed to hash signs.

5 For example, in jBASE, FBNK.CUSTOMER$NAU would be

changed in Oracle to FBNK_CUSTOMER#NAU.

Temenos University 36 36
Introduction to External Database

This is a sample of how T24 data is stored in Oracle or any other

external database for that matter. We will see what it all means in the
next slide.

Temenos University 37 37
Introduction to External Database

Different XML tags are used to differentiate one column from another
in the Oracle table. The first column is RECID this contains the ID’s
of the records. The second column is XMLRECORD and this
contains the whole record delimited by XML tags. In the
XMLRECORD column each field in the record is assigned a number.
Field 1 will be c1, field 2 will be c2 and so on. We will open and close
the ‘c’ tags for each field using XML syntax. For example in the
illustration on screen, we see that Description is field number one in
the SECTOR table. For record ‘1000’ the description would be stored
as <c1>Financial Corporations</c1>. The one after the ‘c’ denotes
the field number in the table.

Temenos University 38 38
Introduction to External Database

Multi value fields are stored with special XML tags that represent
which multi value the data belong to. The letter ‘m’ is used to indicate
a multivalue and this will be embedded as part of the field number
tag.

For example here we see the SECTOR table that has two fields.
Description will be ‘c1’ and Short.Name will be ‘c2’. Short.Name is a
multi-value field. For record ‘1000’ the Short.Name has 3 multi-
values. Short.Name is field number 2 so the first multi-value will be
stored as <c2> Financial Corps</c2>. We do not include the multi-
value position for the first multi-value. The second multi-value will be
stored as <c2 m=‘2’>Financial Insts</c2>. Let us understand this.
The ‘c2’ is required because it is still part of field 2. We then need to
indicate the multi-value position within field 2. Hence, for this, we use
m=‘2’.

Temenos University 39 39
Introduction to External Database

Just like multi-values, sub-values are also stored with special XML
tags. Sub-values are stored in a similar way to multi-values. The
letter ‘s’ is used to indicate a sub-value. The field number indicated
by ‘c’ plus the multi-value position indicated by ‘m’ must also be
included when specifying a sub-value.

For example we can see for record ‘1000’ that it has 2 sub-values for
the TRAINER field. The second sub-value would be stored as <c2
m=‘1’ s=‘2’>Alam</c2>. It is field number 2, multi-value 1 and sub-
value 2.

Temenos University 40 40
Introduction to External Database

Above we see a Customer Record from the T24 Browser.

Temenos University 41
So what are the advantages…

42
We will discuss the advantages in the following slides. First we will cover
the Stateless Connection, then resilience, scalability and finally the ease of
Deployment.

43
Let us understand stateless connection with an example. When we are
engaged in a mobile conversation, The speaker at one end, waits for a
response, to proceed further. The speakers at both ends stay connected .

In contrast, a stateless connection is one in which no information is

retained by either the sender or the receiver. The sender transmits a
packet to the receiver and does not expect an acknowledgment of receipt.
The recipient receives the packet without any prior connection setup.
When we send a SMS, the recipient can read the SMS later & respond at
his convenience and the sender does not wait for a response .

Stateless Connection – a physical connection does not exist between the

various layers of the architecture. A stateless connection is one in which no
information is retained by either the sender or receiver. The sender
transmits a packet to the receiver and does not expect an
acknowledgment of receipt. The recipient receives the packet without any
prior connection setup. For stateless interactions, it does not matter
whether different requests are processed by different servers. T24 Browser
uses a stateless connection.

44
Resilience: Since there are multiple servers in each layer, there is no single
point failure. There is always a failover mechanism available.

45
Scalability is about the ability of a system to easily expand or contract its
resource pool to accommodate heavier or lighter loads. Alternatively, the
ease with which a system or a component can be modified, added, or
removed, to accommodate a changing load.
In business terms, scalability simply means the business model that T24
has can scale up its product when required. This could be due to increasing
demands by adding any number of servers at any point.

46
To deploy T24 browser, you must have the BrowserWeb.war file containing
all browser configurations. This must be deployed in the “deploy” folder of
the Application server. For online banking , there is no need to install any
new software. TCIB*.war, which has settings for online banking has to be
deployed in the same folder. The browser in both instances can be Internet
Explorer or Mozilla FireFox.

47
Temenos T24 is based on open standards. This means that clients can
select the best vendor or environment to suit their needs – whether this is
because of low cost, high performance, local support or any other factor.
If this changes in the future, they can switch vendors without altering their
investment in TEMENOS T24.
This will provide true longevity to their chosen system.
T24 can run on jBase, on Oracle database or on a variety of other
databases. Clients can choose a database they are comfortable with.
Large banks have also been concerned about the scalability and the
resilience of the software. T24 has been able to address these concerns by
an architecture which provides for multiple application & database servers
at various levels. Additional processing capacity can be added by simply
adding more servers. The architecture also ensures that there is no single
point of failure.
Thus, T24 is flexible through out. A Bank can buy only those business
applications they currently need. As it enters into new fields, for example a
retail Bank decides to enter into the Private Banking domain, it can buy the
additional applications and seamlessly continue its operations.
These business philosophies of scalability and flexibility are built into all

48
 facets of T24

Temenos University ‹#› 48

These are the T24 Supported Platforms

49
We will now talk about Business Insight

50
T24 also supports a sophisticated reporting suite called Temenos Insight. It
is used to generate reports for various purposes like audit review, financial
analysis and market analysis. These reports can be used for analyzing the
financial status and for creating strategies for better growth. Insight, also
known as Business intelligence (BI) is a broad category of applications and
technologies. These are used for gathering, storing, analyzing, and
providing access to data to help enterprise users make better business
decisions. Business intelligence solutions help a company in making
business decisions faster, more accurately and more market-oriented.
Data will be extracted from the T24 database into the Insight server using
the Temenos ETL tool. ETL stands for Extract-Transform-Load. This tool
extracts data for analyzing. Once extracted, Insight will load it into its own
database using the File Transfer Protocol and then use the data for
building reports.

51
When a user inputs a transaction into T24, details of the transaction gets
stored in the T24 database. TheT24 Database is an OLTP server which
stores transaction details. OLTP stands for Online Transaction Processing. It
can also be used to refer to processing in which the system responds
immediately to user requests.
Data will then be extracted from T24’s database into the Insight database
using the ETL tool. The Insight database is an OLAP server which stores
aggregate data of a branch or company in total unlike transaction-wise
details. OLAP stands for Online Analytical Processing. It is a methodology
to provide end users with access to large amounts of data in an intuitive
and rapid manner to assist with decisions based on investigation
reasoning.
Once the data is loaded, it will be processed inside the Insight Database
and information will be stored in data cubes. (also called multi
dimensional database). Using the information available in the cubes,
Insight provides a variety of reports like profitability analysis, revenue
analysis, customer profitability, Dashboards containing information on KPIs
and trends and variances. So Insight, integrated with T24, is designed to
enhance management reporting and financial analysis, and give access to
the information needed to manage business.

52
What was the previous name of T24?
GLOBUS

Name the protocol used by all client machines to connect to the

GLOBUS Server?
TELNET

Name the component which transforms HTTP requests to Browser

XML?
BrowserServlet

T24 Database is an OLAP (Online Analytical Processing) server?

False

Temenos Insight is an OLTP (Online Transaction Processing) server?

53
 False

Temenos University ‹#› 53

We will now look at the software Lifecycle, first a description

54
Tired of doing things manually and with the invention of the computer,
man started thinking of creating software for every possible walk of life.
Software helps you work more effectively and accurately. Based on the
requirement, the first step would be to design and code the software.
Testing to see if all is well is the next most important step. After this is
done, the software is ready for use and can be implemented in real time.
Nothing in this world is perfect and neither is software. Using a software in
most cases will bring up issues, some simple and some critical. These are
commonly referred to as bugs. Reported bugs are then fixed for the
clients.
Every software evolves with time. There might be new enhancements or
functionality changes which will result in updating the code and
redesigning the software. These are then tested and released as an
improved version of the existing software. Every new version of a software
is referred to as a release.
This is the cycle all software go through.

55
Now we will now learn about the concepts of Project Build, Release and
Updates

56
Project Builds are released on a monthly basis which comprises of new
functionalities, bug fixes and enhancements
Project Builds are named in the format YYYYMM. (where YYYY stands for
the year of the build and MM for the month in which that particular build
is released). Examples of Project Builds are 201401 and 201402.
1. A Generally Available release is released once in a year.
2. A GA is derived from one or more Project Builds.
3. Once a GA is officially launched, no further enhancements are applied
to it.
4. The naming convention is in the format RXX.000 where XX stands for
the year of release and 000 denotes that it is a GA release
5. Examples of GA releases are R14 and R15
If in case there are any critical issues to be fixed in a particular Project
Build which cannot be postponed to the next Project Build, then multiple
Project Builds for a single month can be released.
The naming convention for multiple Project Builds is YYYYMM.NNN where
(YYYY stands for the year, MM stands for the month and) NNN stands for
the Nth release of the Project Build. Examples of multiple Project Builds
are 201402.002 and 201403.006. This means that the number of Project
Builds that have been released for the month was six.

57
What is a software update?

It provides bug fixes and minor software enhancements and is made

available by free download.

It is also called a software patch because it is applied over the software

that you already have installed.

It does not provide a full software package installation.

58
This last section is about the T24 Release Methodology. We will start a
description of the principle

59
Similar to any software life cycle, T24 also has a life cycle. Temenos
releases a new version of T24 every year with newer functionality to keep
up with the growing demands of the market. This yearly release is called a
GA release which stands for Generally Available release.

After a GA is released, Temenos will work towards releasing the next GA.
But what if a client faces an issue with the latest GA installed? If reported
the Development team will work to fix it in the GA stream. The fix will be
packed into an update for the component on which the fix is done. This
update will be available on the updates portal for the client to download
and install.

If the client requests for new functionality, the new functionality will only
be provided in the next release. New enhancements will not be
introduced into a released GA stream. However an implementing client
can get a project build which is basically an early release before the
software gets finalised for the next GA. The project builds are software

60
 releases but there are no streams created after a project build. Which
means if there is a bug in the project build it is fixed in the Dev stream and
is available only in the next project build

Temenos University ‹#› 60

As you already know, Project Builds are released every month. For a
particular month there can be multiple Project Builds. At the end of the
year, a Generally Available release is released based on the Project Builds
for that particular year. After a GA release is released, Updates may be
released to fix any bugs in the GA release.

61
We will now look at T24 updates

62
The T24 family of products, T24 itself, TAFC, TAFJ, T24 Browser, ARC-IB and T24
Toolbox need periodic updates.

They can be updated, either automatically or manually.

For example, a new version of T24 Browser together with T24 can be provided in
an update, the server code will install automatically and the setup files for the
browser are extracted for you to install. The T24 Updater will also verify the
current version you are using and advise if the one supplied is not a valid
update.

It is possible that an update could contain several products, like TAFC, T24
Browser and ARC-IB. You are more likely to keep your system updated with
smaller updates so you can self-manage the impact of changes.

In summary, T24 Updater has a built in version checker for the T24 products and
a dependency checker that will safeguard the installation of your selected
updates.

Updates should not be done until the appropriate levels of backups have been
made according to what parts are being updated.

63
This is an overview of how the T24 Updates system works.
The bank requires an update.
It can search for the updates in the Temenos Customer Support Portal, or
TCSP, provided that the bank has registered with the tcsp.
After the registration, the bank should register its T24 system with the
Temenos Customer Support Portal. This is a one time step. The system
information, which is in the form of an xml file, should be extracted from
the bank’s T24 Server using toolbox. The T24 system can be registered with
tcsp with the extracted information.
The bank should login to the tcsp, select the registered T24 system and
then check for available updates.
A list of available updates will be provided to the bank.
Then, the bank may choose an appropriate update, then download and
install it using the T24 updater tool.
For a detailed explanation on every step, refer to the course on T24
Updates.

64
Finally we will discover how a new implementation is done

65
TAABS is the T24 Automated Analysis and Build system. It is a web portal
that can be accessed through Browser to ensure smooth delivery of the
Initial System Build (ISB) via a single access point. The Initial System
Build, or ISB, is a T24 environment delivered to a client. The delivery of
the ISB involves the Distribution team, Implementation Team, TAABS
team and TAM. TAABS integrates and co-ordinates their various
activities to deliver the ISB to the client. The TAABS process starts with
the initiation of a request for a Client T24 Environment by the
Implementation Team. A preliminary questionnaire, which is available on
the TAABS web portal, is first filed by the implementation team with
details like the Products purchased by the Client, the Client Details, the
Local Currency, the Bank Date, the Database and the Operating System.
Upon verification of this information with the signed document of the
software agreement, the Distribution team applies for the License and
maintenance codes. A second questionnaire on TAABS captures the T24
parameters based on the Client Requirements, which will be loaded into
the T24 Environment during the System Build. Using these details, the
TAABS team prepares the Base System Build (BSB). After running
sufficient health checks, the TAABS team forwards the environment to
TAMS, who prepares the Initial System Build. The Distribution Team adds
OS and Database Conversions to the Initial System Build, and then ships
the software via FTP.

66
For banks with existingT24 implementations, we periodically perform an
upgrade. This moves the software to a higher release to ensure that the
clients benefit from the new enhancements in the software.

67
1. QUESTION : There should be only one Project Build released for a
particular month
TRUE
FALSE – Multiple Project Builds possible
2. QUESTION : GA is released multiple times in a year
TRUE
FALSE – Only once a year
3. QUESTION : Updates comprises of new functionalities, enhancements
and bug fixes
TRUE
FALSE – Only bug fixes
4. QUESTION : Project Builds comprises of new functionalities,
enhancements and bug fixes
TRUE
FALSE
5. QUESTION : Naming convention for GA is RXX and Naming convention
for Project Build is YYYYMM
TRUE
FALSE

68
Here is what you have learned in this course.

69
70