We upgrade our devices, such as phones or computers, weekly or as soon as a new version is available. Keeping our data secure and having the latest features available are among the top reasons for these frequent upgrades. These new features come with a price and require the full attention of product companies. They must support older device generations but also not introduce slowdowns or crashes. Still, you might experience massive performance issues after upgrading because the developer might not consider your extraordinary configuration, hardware, and data volume.
If we look at the media, we see change-related issues almost daily across all industries. People are getting scared to change and improve things because of unexpected adverse side effects such as performance problems or software errors.
Changes and upgrades are necessary to make room for the new and prepare your team for the future. It's not a bad idea to introduce continuous product upgrades to avoid technical depth.
Upgrade in T24 will usually involve Globus to TAFJ or TAFC to TAFJ upgrades because of its enhanced facilities in TAFJ. Still, some banks prefer Globus to TAFC or TAFC lower release to TAFC higher release upgrades either due to its simple core banking setup or stability in TAFC releases.
What is the general T24 upgrade process?
1. Current T24 system analysis including creation of functional and non-functional requirements
2. Business/Functional changes to be implemented, such as
· LD/MG to AA upgrade
· Implementation of TPH and FCM for payments
· IRIS and IF implementation for better integration and interfaces design
· TAFC to TAFJ upgrade
· DB2/SQL to Oracle upgrade
3. Technical code changes
· Involves selecting a preferred programming language as per the latest T24 release.
· Infobasic to Componentised/L3 JAVA/Python code conversion
· Code changes as per the functional requirements
4. T24 Environment setup and implementing the functionality and code changes
5. Unit, FT, SIT, Performance and UAT testing.
6. Mock upgrade runs, GO LIVE, and post GO LIVE support.
7. Ensure a proper monitoring from the end user down to the code level of all your T24 transactions to identify and fix issues before anyone is impacted.
Globus to TAFC or TAFC lower release to TAFC higher release
The procedure is as follows.
· Extracting temp.release
· Access rights
· Setting TEMP.RELEASE record
· Pre-upgrade checks
· T24 Upgrade object code update
· Post GLOBUS.RELEASE Actions
· Conversion programs
· RUN.CONVERSION.PGMS
· Authorising Records
· Service Pack Installation for T24 jBase
· Patch Installation for T24 jBase
· Restoring Patch in temp.release Directory
· Installing a Patch.
· INSERT files and local developments
· Installing a New Product
· Contact your account manager
· SPF
· COMPANY
· Multi-company processing
· GLOBUS.RELEASE15
TAFC to TAFJ or TAFJ lower release to TAFJ higher release upgrade
Procedure for up to R17 releases
· PREREQUISITES
· PRE-UPGRADE PROCESS
· STOP JBASE AGENT AND ANY OTHER CONNECTIONS
· STOP THE TSM AND OTHER SERVICES
· ENSURE NO OTHER PROCESS IS RUNNING IN THE ENVIRONMENT
· UPGRADE BACKUP
· NOTES / CORRECTIONS / SETUP CHANGES IN R13 BASE
· DATES CHECK
· LIBRARIES AND BINARIES INSTALLATION
· RELEASE PACK
· SYSTEM FILE PATH
· RUN T24.BUILD.LIBRARIES
· VERIFY NEW LIBRARIES AND BINARIES
· NEW FILES AND DATA RELEASE
· PRE-RELEASE FILES
· SETUP SPOOLER DIRECTORY
· RELEASE NEW FILES AND DATA
· AFTER RELEASE BACKUP
· SPF FOR T24 UPDATES
· UPDATES INSTALLATION
· UPDATER INSTALLATION
· CONVERSION
· CONVERSION PGM EXCEPTIONS
· CONVERSION SERVICE
· EXCEPTION AUTHORISATION
· MANUAL VERIFICATION & AUTHORISATION
· MANUAL CORRECTIONS
· AUTHORISE ALL OTHER RELEASED EXCEPTIONS
· LOCAL CODES COMPILATION(SKIPPED FOR MOCKDEV AND MOCK1)
· REPGEN COMPILATION
· AFTER UPGRADE AND PRE-COB BACKUP
· COB
· POST-COB BACKUP
· BROWSER SETUPS
· CLEAR ENQUIRY.SELECT
· PURGE HOLD REPORTS & COMO RECORD
Procedure for T24 R18 and higher releases
Offline Upgrade
· Extracting Temenos Transact temporary release package
· Creating the temp.release record
· Pre-upgrade checks
· Updating Temenos Transact libraries
· Run T24.PRE.RELEASE
· Updating VOC entries
· Running the T24.UPGRADE service
· Running the RUN.CONVERSION service
· Restructure mechanism
· Authorising records
· Auto authorisation by online service
· Post Upgrade Activities
Online Upgrade
· Prerequisites
· Upgrading TAFJ
· Upgrading Temenos Transact libraries and
· Initiating Temenos Transact upgrade
· Stopping channels and services
· Releasing primary data
· Moving the Temenos Transact system from offline to online stage
· Releasing secondary data
· Multi-App server state
· Restructure mechanism
· Enquiries to monitor online upgrade
· Post Upgrade Activities
If you are worried regarding your upgrade to the latest core banking system please reach out. Good luck on your journey and don't miss the validation of your performance requirements early in the development process.
Keep up the great work! Happy Performance Engineering!