Temenos T24 Transact core banking software is a real-time core banking system.
This integration with T24 allows monitoring of the triggered COB (Close of Business) process from UAC by COB execution stages with an intuitive interface providing the centralized Dashboard and reporting features and notify in case of COB failures or any SLA violations in the course of COB execution.
Temenos COB Monitor
This integration is tested on Temenos(T24) R20 Version (Windows)
Universal Agent installed in the T24 server having the TAFJ DBTOOLS utility to execute a SQL / JQL / OFS statements.
This integration requires a Universal Agent and a Python runtime to execute the Universal Task.
Software Requirements for Universal Agent
Both Windows and Linux agents are supported:
Universal Agent for Windows x64 Version 188.8.131.52 and later with Python options installed in T24 machine.
Universal Agent for Linux Version 184.108.40.206 and later with Python options installed in T24 Machine.
Software Requirements for Universal Controller
Universal Controller Version 220.127.116.11 and later.
This extension provides support for:
Monitoring COB execution using the user-specified time intervals.
Segregate COB execution monitoring by stages - Application, System wide, Reporting, Start of day, Online & Overall.
Notify COB execution failures via the user-defined task, for example through email/slack/Teams/Jira/Pagerduty/ServiceNow.
Possibility to create Custom Report, Widget & Dashboard for monitoring the COB execution stage wise with the below information.
Percentage of progress
Failed Job count
Failed Job Name
Execution duration of the COB stages
COB Batch status is fetched from the T24 system using OFS inquiry.
Import the Universal Template
To use the Universal Template, you first must perform the following steps.
Online portal to generate T24 OSF Message Generator
Modifications applied by users or customers, before or after import, might affect the supportability of this integration. The following modifications are discouraged to retain the support level as applied for this integration.
Python code modifications should not be done.
"Name", "Extension", "Variable Prefix", "Icon" should not be changed.
Universal Template Details Section
"Template Type", "Agent Type", "Send Extension Variables", "Always Cancel on Force Finish" should not be changed.
Result Processing Defaults Section
Success and Failure Exit codes should not be changed.
Success and Failure Output processing should not be changed.
Fields Restriction Section The setup of the template does not impose any restrictions, However with respect to "Exit Code Processing Fields" section.
Success/Failure exit codes need to be respected.
In principle, as STDERR and STDOUT outputs can change in follow-up releases of this integration, they should not be considered as a reliable source for determining success or failure of a task.