top of page
Search

A Practical Guide to Directories and Dictionaries in Temenos T24

  • Writer: Josef Mayrhofer
    Josef Mayrhofer
  • 9 hours ago
  • 3 min read

In Temenos, the ‘bnk’ folder serves as the primary directory for all applications. It primarily comprises the following subdirectory structure, with each directory designated for specific storage functions.


  1. Bnk.data: This directory holds all application and transaction data.

  2. Bnk.dict: This directory contains the dictionary files associated with the applications.

  3. Bnk.help: This directory contains the help text files for the applications.

  4. Bnk.jnl: This directory stores F.JOURNAL files, which are replicas of all transactions in T24, with a storage duration of one day.

  5. Bnk.run: This directory contains all runtime files, including .profile, bin, and lib files for T24, as well as local executables.

  6. Bnk.backup: This directory is designated for storing pre and post COB backup files.

  7. BP directory: This can refer to any local BP used for storing and compiling routines within the bank.


Language and Dictionary in T24:


English is established as the default language for the Model Bank. Regions where English is not the primary language must translate the entire Model Bank configuration into their local language to effectively demonstrate and implement the system. Currently, Temenos Transact allows for the translation of individual screens, inquiries, and other configurations by specifying the local language and loading the translated text. However, Temenos Transact supports a maximum of 12 languages. Consequently, any language-specific multi-value field is limited to no more than 12 distinct languages.


EB.DICTIONARY is utilized to standardize terminology within the Model Bank configuration and to create a dictionary of terms that facilitates the translation of the Model Bank configuration and the maintenance of translated terms. Additionally, EB.DICTIONARY supports the translation of VERSION and ENQUIRY labels and headers, enabling the system to retrieve labels from the compiled dictionary of terms. Temenos Transact now accommodates up to 99 languages in the LANGUAGE record, with translation functionality available for 12 languages.


The Front Office - PM files mentioned are situated within a subtree under the parent directory $AAAHOME. The primary files can be found in $AAAHOME/aaaprofile, which includes definitions for Unix variables.

  • Install

  • config

  • ddl

  • msg

  • bin


Technical Data Dictionary: The relevant APIs are utilized alongside their respective packages (EDS, TDH, TDE). The table below enumerates the REST API.

  • API for SDS metadata dictionary

  • API for ODS metadata dictionary

  • API for EDS metadata dictionary

  • App Name as a query parameter


Dictionary caching:

Currently, dictionary caching is limited to the TAFJ local caching mechanism since the Object is a complex entity rather than a String. This local caching mechanism ensures the quickest access. Dictionaries are infrequently updated. The entire dictionary cache occasionally expires and is governed by the temn.cache.dict.expiry.time property, which is specified in milliseconds. The default duration is 4 hours. The cache is also purged if STANDARD.SELECTION is rebuilt, although this occurs only on a single node and is not applicable cluster-wide.

 

The parameter files in T24 are essential tables that must be established for each application and are crucial for the functioning of T24 applications. Some of the parameter files are outlined below.


  1. SPF - System Parameter File: The ID will be SYSTEM; this is the principal parameter file for the entire T24 system. It retains all the applications or modules installed in T24, release updates, cache details, and much more.


  2. PF – PGM.FILE: The ID will be unique for each application; this table monitors all T24 applications by distinguishing them with the field ‘TYPE’.


  3. FILE.CONTROL: The ID will be unique for each application; this table regulates the type of information that must be stored in each application.


  4. CREATE.FILE: This is used to create insert files in earlier releases.


  5. SS - STANDARD.SELECTION: The ID will be unique for each application; it retains all field names and field types, including local fields that can be added at any time.


  6. EB.DEV.HELPER: In the latest releases, all the above applications can be created with one click. In older releases, usually in GLOBUS, all the entries were created separately.


If you are interested in T24 training or performance tuning, please contact us. As part of the Dynatrace implementation, we have our own T24 fast pack services that enable deep monitoring across COB and other modules in T24. At Performetriks, we would be happy to assist you.

Happy Performance Engineering! #T24 #T24FastPack #SoftwareEngineering


Comments

bottom of page