You are on page 1of 34

T24 Architecture

Libyan Qatari Bank

August 2010
Agenda

T24 Architecture
Architecture Components
TAFC
HOT Standby
LQB Architecture
Branch Resilience
Interfaces
TEMENOS T24 - Technical Architecture

Presentation
Zero footprint
Multi-Channel
Scale

SOAP
Internet Web Enterprise Open
Browser
Bank Services Console Development and
implementation tools

Web server
e.g. jBOSS,
Web Layer

Websphere
TCP/IP
Scale

Application Server,
Web Server
Oracle, Weblogic

XML
Application

Linux, AIX, HP-UX,


Solaris, Win 2003
Scale

C object code
Server level API
C# Java
NON-STOP Common Presentation
No Batch: NON STOP
Database

Oracle, DB2, jBASE 5,


Scale

SQL Server 2005

Clustering e.g. RAC


Component Architecture

Java EE Application Server


T24 Browser T24 ARC-IB
(BrowserWeb.war) (ARC-IB.war)
“AGENT” “AGENT”
Industry Standard TAFC JCA

TAFC JCA Provides connection, transaction


(jremote-ra.rar) and security management within a
scalable JEE environment.

Temenos Application Server

Temenos Application Framework


jbase_agent jbase_agent jbase_agent jbase_agent
TAFC runtime providing access to
T24 subroutines.

E A A D
B A C X
Web Layer

 Web Server provides the web container in which T24 Browser


servlet is managed and run.

 Web Servers hosts Web Application Servers


 jBOSS
 IBM WebSphere Application Server
 Oracle WebLogic
 Any J2EE complaint Web Servers.

 T24 Front end Components.


 T24 Browser
 T24 ARC-IB
 Other Components.
 Java
 jremote-ra.rar adapter (To communicate with T24 Application Server in
AGENT Architecture)
T24 Application Layer

 T24 Application Server hold the actual T24 software.


 Holds Database as well in case the database is TAFC.
 Software is in the form of Binary file and Libraries files, which are
compiled for native OS.
 T24 Components
 T24 Software.
 TAFC runtime environment.
 C – Compiler for the native OS.
 Database Drivers incase the DB is other than TAFC.
 TAFC Agents to communicate with T24 Browser (Part of TAFC)
T24 Application Server Components Contd

 TAFC (jBASE Database, Data files)

 Database Drivers in case Database other than jBASE.

 TAFC Dataguard.
 Transaction Journaling.

 Log Replication on Hot Standby

 Online Backup
Database Layer

 Database Layer is to define different types of DB that can be used with


T24.

 Stores the actual T24 data in form of tables.

 Database layer is part of T24 Application Server in case the DB is


TAFC.

 TAFC uses drivers to communicate with Database (Oracle, DB2, SQL).

 Clustering can be used, if DB allows in case of Multi-Server


architecture.
TEMENOS T24 - Technical Architecture

Presentation
Zero footprint

Browser

Web server
e.g. jBOSS,
WebSphere
Web Layer

Application Server,
WebLogic
TCP/IP

XML
T24 Browser Servlet

Web Server

• AIX
Application

•TOCF EE
•jBASE Run time.
T24 Server
•T24 Libraries
Database

Database Oracle, DB2, jBASE 5


SQL Server 2005
T24 Browser
T24 Browser

 T24 Browser is a thin client browser based interface into the T24
application.

 No business logic or data is held locally on the client computer.

 All requests from the T24 Browser to T24 are message based.

 Between the browser and the Web Server, these messages are in
HTML format, but are translated into XML at the Web Server by the
T24 Browser Servlet for the rest of their journey into T24.

 Communication between the Browser and T24 is stateless in that any


request or transaction from the T24 Browser is completely independent
of the last or subsequent requests or transactions.

 Works with Microsoft Internet Explorer 6 and Firefox Mozilla.


T24 Browser

Presentation

 XSLT
HTTP  Translates XML into
REQUEST HTML HTML
 And vice versa
 CSS
Web Layer

Web Container  Template used to format


HTML
Browser Servlet

XML XML
REQUEST RESPONSE

JMS Consumer
Application

jBASE Agents
T24 Application Server
Database

DB
TAFC

TAFC
TAFC

 TAFC is an application development and database management


system.

 TAFC uses the ‘C’ compiler to compile programs.

 TAFC is an open database and can communicate with external


database like Oracle, DB2 etc with help of drivers.

 TAFC uses jEDI (jBASE External Database Interface) to


communicate with other Databases.

 T24 Application uses TAFC runtime to execute the package.


TAFC Modular Component Architecture

TAFC Utilities
jSHELL Queries jAgent jSpool …
Java
BASIC
OBjEX
Application
Code TAFC Library Functions
(.lib, .bin) jEDI
OLE DB
ODBC
TAFC files Oracle User JDBC
native via OCI Defined

Operating System

Hardware
TAFC Overview

 Can be viewed as tool set


 Used to construct T24 into standard ‘C’ code

 C code compiled using standard compilers into

Native System Executables

Native System DLLs

 Execution handled as any other standard Windows/Unix executable and


set of dynamic linked or shared libraries

 Can be viewed as a Database


 jBASE Hash Files and tools
TAFC Hash Files

 Provide very fast data access using hashing algorithms to balance and
locate data

 Hash files are implemented on top of the native file system.

 jBASE Hash files consist of a structure of primary groups/buckets


located at specific offsets in the file dependent upon the frame/bucket
size for the file type. J4 use 4096 bytes frame size.

 jBASE Hash J4 files on some platforms can utilize OS memory


mapping functionality or alternatively can also be configured for use
over networked file systems using the standard OS read and write API
Hash File Maintenance

 Tools for Hash file maintenance and modification

 jstat Provides statistical information about file


 Jrf Tool to resize file
 jcheck Tool to verify structure of file
 jbackup Database file backup
 jrestore Database file restore
 jchmod Tool to modify file properties
LOG - Log updates to transaction journal
TRANS - Include updates as part of transaction
BACKUP - Include as part of jbackup process
NETWORK - Network file use read/write API

All above tools have a help option (-h) to display available


options
TAFC Locks

 TAFC provides advisory locking capabilities for records independent of


the underlying database

 Record locks
 Locks taken on physical records in a hash file
 Usually as a result of an advisory lock statement (READU)

 Binary locks
 Internal to jBASE
 Taken when the system needs to lock a resource
 For example when updating a file group (Hash files only)
 Or updating journaling logs
TAFC Profile Tools

 jdiag -dvL
 Provides snapshot of current environment/configuration

 WHERE (V
 Provides verbose output about executing processes

 jprof
 Online profiling tool to determine process profile

 JDIAG
 Environment variable to provide low level information
jEDI (jBASE External Database Interface) Architecture.

T24 Application

TAFC Library Functions


jEDI (Native) jEDI (ORACLE) jEDI (????)

DATA-FILE DATA-FILE
#1 #5
(j4 File) (Any)

DATA-FILE ORACLE DATA-FILE


#2 Data-File #6
(j4 File) #3 & #4 (Any)
Branch Resilience

Branch Resilience (BR)


Branch Resilience

 Why Branch Resilience??

 To provide a minimum service to the customers, incase


communication between Data Center and the Branch is interrupted
Branch Resilience

 T24 BR Module

 Concept of storing a copy of some amount of data at the branch level


as well as Central Server.

 BR module allows maintenance of a backup system at branch level.

 Not possible to run full branch service.

 Used to give basic but important service to customers.

 Used to re-establish data when the connection to the main server is


back-up.

 Currently only TELLER, TELLER.ID & PASSWORD.RESET is


supported.

 System is said to be “OFFLINE” if not connected to central server.


Branch Server

 Branch Server Contains

 A Web Server (eg : jBOSS)

 TAFC – jBASE Agents

 T24 Libraries

 TAFC Database
Branch Resilience

Branch Resilience Work Flow - ONLINE


Branch Server

Branch Resilience WorkFLOW for TELLER - ONLINE


Branch Resilience

Branch Resilience Work Flow - OFFLINE


Branch Resilience

BR Work Flow After the CONNECTION RESUMED


Branch Resilience

Training Recommended for Branch Resilience (BR) Module for


setup and functional details.
T24 Interfaces

T24 Interfaces
T24 Interfaces solution

There are 3 groups of interfaces protocol


 Batch (Inbound/Outbound)
• Daily extraction
• Pseudo real-time extraction (every x minutes)
• MetaData extraction…
Use of
TOCF BatchFileListeners for INBOUND
T24 Extractor for OUTBOUND
 Message based (asynchronous/synchronous, Inbound/Outbound)
• Cross system validation/control
• Transaction from/to third party…
Use of
TOCF Message and Delivery MDB (jca/TAFC EJB dispatcher)
Temenos Web Services – TWS
 Point to point
• ATM switch…
Use of
Temenos maintained adapter (ISO…)
To refer to Temenos Interface team
Architecture Blueprint
Business Channels
Call End User Branch
CRM X systems Corporate
Centre (MC) User

Accounting, Business
Analytics & CRM Call Centre Multi-Channel Branch Other B2B
System System Platform Platform Platform
Channel
Countries
Reporting Services

Internal Gateways
Reporting
Message Bus
ATM/POS
Gateways
MIS

Payment/Bill
Data
Gateways
Warehouse
T24
GL E-mail/SMS
Gateways

Financial Acct
Internet/Intranet
Gateways
Control

Treasury Risk Card


Compliance Central Bank
& trading Mgmt system

Agencies Core Business Support


LQB – T24 Architecture

You might also like