0% found this document useful (0 votes)
695 views30 pages

T24.Architecture - TAFC Directory Structure

This document discusses T24 architecture and the Temenos Application Framework C (TAFC). It provides an overview of T24 modules and introduces TAFC, including its directory structure, environmental variables, .profile file, and file types. It describes how to log on to TAFC and maintain files, such as using jstat to view file statistics and determine if resizing is needed.

Uploaded by

Yasith Liyanage
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
695 views30 pages

T24.Architecture - TAFC Directory Structure

This document discusses T24 architecture and the Temenos Application Framework C (TAFC). It provides an overview of T24 modules and introduces TAFC, including its directory structure, environmental variables, .profile file, and file types. It describes how to log on to TAFC and maintain files, such as using jstat to view file statistics and determine if resizing is needed.

Uploaded by

Yasith Liyanage
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 30

T24 Architecture & TAFC

Directory Structure
Agenda

T24 – Introduction
T24 Architecture - An Overview
Temenos T24 Technical Architecture
T24 Modules - Introduction
Logging on to TAFC
TAFC directory structure
TAFC environmental variables
TAFC .profile file
TAFC File Types
File maintenance in TAFC
T24
T24 is a fully integrated modular core banking solution covering a broad spectrum of
functional requirements for Retail Banking, Private Banking, Corporate Banking,
Universal Banking, Islamic Banking and Microfinance sectors.

T24 was launched in 2003, as the successor to their then flagship product Temenos
GLOBUS. It provided an innovation in the core banking software industry by
eliminating the requirement for an offline End Of Day (EOD) batch process. For the
first time, Financial Institutions could turn to a packaged solution to support all their
business channels online and in real-time 24/7.
Open Standards
TEMENOS T24 runs on
Open hardware
Scalable architecture that permits adding further servers as volumes expand
Open database
Open user interface through browser, HTML and open connectivity through XML and
Web services
T24 Architecture-An Overview
T24 Architecture
Layers in T24 Architecture
T24 Modules- Introduction
Temenos provides various Modules under T24
Modules normally group together features related to a business or technical
function
Examples: Core Module, Teller Module, Money Market Module, etc
T24 modules can be:
Core
Functional
Technical
Core Modules are provided as a default when T24 is installed, they provide basic
building blocks to build business applications
Functional Modules
Functional Modules handle different banking products and services
Modules have to be purchased or licensed separately
Examples: Letters of Credit, Mortgages, Funds Transfer Modules provide
functionality for a specific business area
Consist of Main Application, Parameter Applications and Close of Business programs
Technical Modules
Features provided as part of the software
Used across the system
Enables Customization of the system
Example: Enquiry Module, Delivery Module
T24 Facilities
TAFC (Temenos Application Framework C
version)
TAFC was previously called as jbase
An application development & Database Management System
Allows easy migration from other DBMSs.
T24 uses TAFC to store data
Open database – Can communicate to other databases
Platform independent
Uses the ‘C’ compiler to compile code
Logging Onto TAFC
TAFC Directory Structure
TAFC Directory Structure
config – Contains various configuration files relating to the jam daemon, the
configuration file for the creation of library files and other configuration files.
lib – Contains the library files that are required for the working of base. This
directory contains all the libraries required for linking and executing jobs compiled
routines
temp - This is a general purpose temporary directory for runtime use.
spooler - This is the spool directory of base. It contains all the files that are required
for spooling to work in base. This directory is created as a part of the printer set up
of base and does not get installed when base is installed.
TAFC Environmental Variables
JBCRELEASEDIR – Holds the directory where TAFC has been installed.
JBCGLOBALDIR – Contains the path to the config directory of TAFC
PATH – It is a Unix variable which holds the path of the executable files of Unix
& TAFC
LIBPATH – Holds the path of the TAFC library files specific to the operating
system
LIBPATH = /us/job/lib (AIX)
SHLIB_PATH = /us/job/lib (HP)
LD_LIBRARY_PATH = /us/job/lib (Others)
JBCSPOOLEDIR – Holds the path to the spooler directory of TAFC
JBCBASETMP – Holds the path of the ‘tmp’ directory of TAFC
TAFC Environmental Variables
JBCLISTFILE – Contains the path of the &SAVEDLISTS& directory that is used to store
select lists
JBCLISTFILE = $HOME/&SAVEDLISTS&

jsh..>SELECT FBNK.CUSTOMER
100 records selected
>SAVE.LIST TRG.FILE1
jsh..>LIST FBNK.CUSTOMER
JEDIFILENAME_MD – Holds the path of the VOC file
JEDIFILENAME_MD = $HOME/VOC
($HOME – Home directory of the T24 user)
VOC – Vocabulary
Known as Master Dictionary
Contains various types of entries
Example of VOC
PA – Paragraph
JED VOC TR01
PA Paragraph Entry
ETS Sentence 1
EX Sentence 2
DATA TRAINEE01 Sentence 3
DATA 123456 Sentence 4
F – File pointer
JED VOC FBNK.CUSTOMER
0001 F
0002 ../bnk.data/st/FBNK_CUSTOMER
0003 ../bnk.dict/F_CUSTOMER]D
.profile file
When a user needs to logon into t24 running on base, he supplies the Unix user
name and password.
Unix validates the user name and password with the /etc/passwd file and if
successful, executes the ‘.profile’ file under the home directory of the user(bnk.run).
Find the contents of the .profile file of a user in a base environment.
export HOME=/globus/bnk/bnk.run
export JBCRELEASEDIR=/usr/jbc
export JBCGLOBALDIR=%JBCRELEASEDIR%
export JBCOBJECTLIST=$HOME/lib;$HOME/globuspatchlib;$HOME/globuslib
export LIBPATH=$JBCRELEASEDIR/lib
export SHLIB_PATH=$JBCRELEASEDIR/lib
.profile file
export JEDIFILEPATH=$HOME
export JBCLISTFILE=$HOME/&SAVEDLISTS
export JBCSPOOLERDIR=$HOME/jspooler
export JEDIFILENAME_MD=VOC
export JEDIFILENAME_SYSTEM=/usr/jbc/src/SYSTEM
export
PATH=$JBCRELEASEDIR/bin;$HOME/globuspatchbin;$HOME/globusbin
export JBCDEV_BIN=$HOME/bin
export JBCDEV_LIB=$HOME/lib
TAFC File types
Every file in TAFC has 2 portions

1 xxx yyy 1 xxx yyy


2 xxx yyy 2 xxx yyy
3 xxx yyy 3 xxx yyy
Data portion Dict portion
Data File - Contains the records
Dict File – Contains the field names and the field definitions
TAFC File types
TAFC supports 2 different types of files –
Non-hashed file
Hashed file
Non-Hashed files
Sequential files
Unix level directories
Used to store programs
Type = UD
TAFC File types
Hashed Files
Store and retrieve data randomly
Improve performance
Used to store data & dict files
Type = J3, J4 or JR
Have a modulo and separation and secondary buffer
Modulo – Number of frames
Separation – Size of a frame
Secondary Buffer – Size of the secondary buffer size.
Default size of secondary buffer : Size of 1 modulo * 2
Non Hashed Files
Example: Create a non-hashed file TEST1

CREATE.FILE TEST1 TYPE=UD

CREATE.FILE TEST1 TYPE=UD

File TEST1]D created ,type = UD

File TEST1 created , type = UD


Hashed Files
Hashed File – Type J3
Modulo 4 and Separation 4
Default size of 1 modulo(frame) is 1024 bytes

Data File Dict File


Eg: J3 file with modulo 3 & separation 3-

CREATE.FILE TEST TYPE=J3 3,3 3,3


File TEST]D created ,type = J3
File TEST created , type = J3
Hashed Files
Hashed Files – Type J4
Modulo 4 and Separation 4
Default size of 1 modulo(frame) is 4096 Bytes

Data File Dict File


File Maintenance in TAFC
A badly sized file will result in low performance of the system. Therefore it is
absolutely necessary to resize files periodically.

Jstat
jstat is the command in TAFC that is used to determine the statistics of a
hashed file.
Options with jstat
f - free space display
r - record display
s - short summary display
v - verbose
w - do not wait on locked records
File Maintenance in TAFC
Output of JSTAT
jsh R13NEW ~ -->jstat FBNK.ACCOUNT
File Path = ..\bnk.data\ac\FBNK_ACCOUNT
File Type = JR, Hash method = 5, Created = Mon May 19 23:22:48 2008
Frame size = 4096, OOG Threshold = 2048
File size = 1966080, Freespace = 0 frames
Internal Modulo = 3/7/19, External Modulo = 31
Record Bytes = 652117, Record Count = 1280
Bytes/Record = 509, Bytes/Group = 1393
Data Frames = 456, Ptr Frames = 13
OOG Bytes = 16865, OOG Frames =6
Sum Squares = 326719300, Std Dev Mean = 592
jsh R13NEW ~ -->
Summary
• In this learning unit/course, you learnt about the T24 Architecture and Directory
Structure
• T24 Technical Architecture
• T24 Modules Introduction Functional module and technical module
• Logging into TAFC and TAFC Directory Structure
• TAFC Environmental Variables and VOC
• .profile file setup
• TAFC File types
Hashed file – J3, J4 or JR
Non Hashed file – CREATE.FILE FILE.NAME TYPE=UD
• File Maintenance in TAFC – jstat
Thank
You

You might also like