The good old saying, "Old ways won't open new doors." underpins that we must keep changing and improving everything to succeed.
We see this transformation in every industry. For example, there is a significant movement from human interactions to digitized services.
Old ways won't allow you to address the needs and expectations of the next generation of customers. However, you can open new doors if you migrate to Microservices or standardized platforms.
One significant movement in the Core Banking industry is the migration from do-it-yourself to the Java-based Temenos platform. If you are on such a migration journey, follow our good practices below.
Performance of conversion process
Improve the performance of the conversion process during the upgrade by installing the latest updates and changes to PGM.FILE while running RUN.CONVERSION service
Use of componentized/L3 java coding
Design Studio improves every Stage of Development
State-of-the-art Coding and Design Tools for every artifact
Version control T24 Objects like Version, Enquiry, or ParametersCentralize and sync your development
Manage automated tests and deployment.
A component is a logical and technical grouping of jBC artifacts. By « jBC artifacts» we mean subroutines, functions, commons, and tables. This grouping was already existing, but by naming conventions only.
A component is self-describing. Protect users have to know the underneath implementations
COMMON variable access is done through getters and setters—no more side-effects of changing a standard variable without knowing it.
Constants (EQU) are defined in the component and not copied across like a $INSERT. So There is no risk of clashing with different versions.
L3 Java coding
Since R19 TAFJ, TEMENOS recommends writing L3 code in JAVA using the JAVA extensibility/Development module. All those tools can be used together; however, existing JBC codes can also be compiled.
Functional changes to address customizations
Some local developments can be achieved through Parameter table changes in T24 rather than routines. Such implementations can be done by analyzing the T24 system during or after the upgrade.
Data Lifecycle Management, jBase to relational database conversion
For Implementations on a relational Database (MSSQL, DB2, Oracle), there is an option to separate the Read/Only data from transactional data in the context of Data Lifecycle Management. The benefits of the separation are:
Reduce transactional data drastically (around 70%), so the essential data can be placed on cheaper disks.
Backups will be much faster, as well as restore procedures, because the daily backup plan will only include the small transactional portion, and you can back up the read-only data in separate lower frequencies.
Cloning environments are faster due to the size of the transactional data. T24 test instances can have their transactional database, while many can point to the same Non-Volatile (Read Only) Database.
Data archiving for high-volume clients
Enables customers with high volumes of Core Banking data to manage database growth effectively, reduce storage costs, improve performance, address regulatory compliance, and reduce operational risk.
An extended version of Core Banking Data Archiving Assessment Service is now available as a full service comprising all three lifecycle phases; Assessment, Build & Implementation.
The service is suitable for customers whose Core Banking database structures, data volumes, customization, and archiving requirements do not present high degrees of complexity.
Implementing Integration and Interaction Framework (IRIS) in TAFJ
Interaction Framework (IRIS)
You can use the Interaction Framework for Human-to-Machine Interaction. It is designed with a RESTful mindset and uses the OData protocol allowing you to operate on resources using HTTP GET, PUT, POST, and DELETE.
The Interaction Framework is a layer between the user interface and T24 (and our other acquired products or any other resource manager or data source of the bank). It separates the user interface from the banking capability. In addition, it delivers a flexible, reusable interface with the agility to meet continuously evolving customer and employee requirements. Another benefit is that it reduces dependency on T24 (and our other products), so Temenos/Clients can concentrate on excellent UI development.
The Integration Framework is used for Machine-to-Machine integration. We distinguish between Inbound and Outbound Integration Frameworks.
Publish content to the ESB
Produce flat files using event details
Reduce extracts from T24
Expose operations for native messages
Formats supported are OFS, Native
Expose business services in T24
COB Performance improvement
Our blog posts and workshops share detailed knowledge about COB performance tunings. It would be best if you considered the following aspects when optimizing your migrated TAFJ COB :
Like in every migration project, make sure you use the latest 3rdparty services and libraries. This practice helps your team to overcome fundamental issues such as security vulnerabilities.
In addition, you should review the design and consider replacing SWIFT, ACH, and other touchpoints with the IF framework.
We are here to assist your team during the TAFC to TAFJ migration process. Contact our T24 experts anytime. We offer performance tuning, monitoring, customization services for your T24 core banking system.
Happy Performance Engineering! Keep up the great work!