Temenos T24 Transact core banking software is a real-time core banking system and this integration with T24 allows UAC to Schedule, trigger & Monitor the Daily Close of Business (COB) process in the T24 System automatically and it also helps to build your own COB workflow including the COB Pre and post-COB conditions which might be critical for the COB execution process.
Please be noted that COB Monitoring with this Integration is about looking for active COB agents in TSM, For Detailed COB Monitoring please use the universal extension "Temenos COB Monitor" which gives a granular view of the execution status by each COB execution phase, Notify Batch Failures & Reporting
So this universal Task along with Temenos COB Monitoring universal extension provides effective COB Monitoring capabilities.
This integration requires a Universal Agent and a Python runtime to execute the Universal Task.
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.
Software Requirements for Universal Agent
Both Windows and Linux agents are supported:
Universal Agent for Windows x64 Version 220.127.116.11 and later with Python options installed in T24 machine.
Universal Agent for Linux Version 18.104.22.168 and later with Python options installed in T24 machine.
Universal Agent with below Python modules
requests (default with agent python pack)
Pretty Table - Needs to be installed additionally in the agent python pack
Software Requirements for Universal Controller
Universal Controller Version 22.214.171.124 and later.
This Integration provides the following main features:
The ability to schedule, automate and execute Daily COB in T24 via the Stonebranch Universal Controller.
Monitoring COB run from an overall perspective is only possible from this Integration. To facilitate COB stage-wise monitoring its is required COB Monitor universal extension plugin from the integration Hub.
UAC helps to monitor the COB execution progress and alert in case of failures or slowness in the execution process.
Tailoring the Daily COB execution process using the UAC workflow including COB Pre and Postconditions.
Some of the key T24 functionalities supported are as follows :
Start/Stop TSM service
Start/Stop/Monitor COB Service
Start TSM in Phantom Mode
Status Check Actions
Check Agent Status in T24
Check COB Status
Check TSM Status
Fetch COB Batch status
Clear TSA Status
COB Precheck Action
COB Date check
Holiday Calendar check
EB EOD Error Check
COB Report RT & JT Analyze
Run a DBTOOL command (OSF or JQL or SQL ) in T24
Import the Universal Template
To use the Universal Template, you first must perform the following steps.
This field is visible with the option RT & JT ANALYSE
Specify the Universal controller credentials for REST API purposes
Specify the Runtime Directory for the Universal Agent Run time user if needed
Select a T24 Function
Start COB (Close of Business) Service
Scenario: To start the COB in T24 from the universal Task. Please specify any environment variables that would be needed for triggering the COB start OFS command, for example, JAVA_HOME as in the below screenshot
COB Date Check Validation
Monitor COB Service in T24
Example COB workflow
Scenario: Example COB workflow demonstrating the COB Pre-conditions check, COB execution & COB Monitoring capabilities using UAC
Note: Temenos COB Monitor universal extension jobs included in the workflow below for the COB stage-wise Monitoring
Example COB execution monitor Dashboard
Note: COB execution progress and its details (Widget: COB-Monitor-Table & COB-Monitor-Progress) in the dashboard needs to be pulled from the Temenos COB monitor extension task instance
The exit codes for this Universal Template are described below.
Status Classification Code
Status Classification Description
SUCCESS: Successful Task execution
FAILED: COB Execution request date is a Holiday
FAILED: TSM service is not in Running status
FAILED: No Active TSM or COB Agent Found after initiating Start
FAILED: Exception while executing
STDOUT and STDERR
STDOUT and STDERR provide additional information to User. The populated content can be changed in future versions of this integration without notice.
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", "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.