Your use of this download is governed by Stonebranch’s Terms of Use, which are available at Stonebranch Integration Hub - Terms of Use.
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.
Template Name | Version |
---|---|
Temenos | 1.1.4 |
Refer to Changelog for version history information.
Both Windows and Linux agents are supported:
Universal Agent for Windows x64 Version 7.1.0.0 and later with Python options installed in T24 machine.
Universal Agent for Linux Version 7.1.0.0 and later with Python options installed in T24 machine.
Universal Controller Version 7.1.0.0 and later.
This Integration provides the following main features:
To use the Universal Template, you first must perform the following steps.
This Universal Task requires the Resolvable Credentials feature. Check that the Resolvable Credentials Permitted system property has been set to true.
To import the Universal Template into your Controller, follow these instructions.
When the files have been imported successfully, refresh the Universal Templates list; the Universal Template will appear on the list.
Modifications of this integration, applied by users or customers, before or after import, might affect the supportability of this integration. For more information refer to Integration Modifications.
For a new Universal Task, create a new task, and enter the required input fields.
The input fields for this Universal template are described below.
Field | Input Type | Default Value | Type | Description |
Select a T24 Function | Required | Start COB Service | Choice | The action performed upon the task execution. Valid values are:
|
Temenos Credentials | Required | - | Credentials | Credentials for Temenos TAFJEE DBTOOLS command utility
|
Transact User Credentials | Required | - | Credentials | Credentials for Temenos T24 Transact User credentials as follows
|
Only Running Agents | Required | - | Boolean | This option can be set to true or false when the Check Agent status Choice is selected |
Enter a TAFJEE DBTOOLS Command | Required | - | Large Text Field | Enter an OSF or JQL or SQL commands that need to be executed in T24 Server via TAFJEE DBTOOLS. (T24 Function : Run a DBTOOL command (OSF or JQL or SQL command) Example: DBTOOLS -u t24user -p xxxxx –s JQL CLEAR-FILE F.EB.EOD.ERROR |
Max number of times to check | Required | - | Text | The Field is required when the selected T24 function is either "Check TSM Status" or "Check COB status". Specify the maximum limit that you may need to check the status of COB and TSM |
Poll Interval (seconds) | Required | - | Text | The Field is required when the selected T24 function is either Check TSM Status or Check COB status. Specify the duration in seconds to poll the status of COB and TSM service |
Status to Check | - | - | Choice | This Choice Field is required when the selected T24 function is either "Check TSM Status" or "Check COB status". It's possible to select the status as either Running or Stopped, So this would help to check the status of COB or TSM for the specified max number of times and the poll interval |
TSM Phantom Mode (File Name) | Required | - | Text | This field is required when the selected T24 function is Start TSM in Phantom Mode. Specify the script file name which would start the TSM in Phantom mode |
Log Level | Required | INFO | Choice | Specify the Required Log level, It could be either INFO or ERROR or DEBUG |
Transaction ID | Required | Text | Specify the Transaction ID when the selected T24 function is EB EOD ERROR or COB date check or Holiday Check | |
COB ID | Required | COB | Text | This field is optional when the selected T24 function is START/STOP/CHECK COB Specify the COB ID which would be required to Start or Stop or Check COB Status |
UAC Base URL | Required | Text | This field is visible with the option RT & JT ANALYSE This would create 2 global variables in the below-specified format when the task is executed : 1)${ops_task_name}_RT_fname (Example Value : RT.20220515.CSV) 2)${ops_task_name}_JT_fname (Example Value : JT.20220515.CSV) Specify the Universal controller Base URL below Example : http://localhost:8080/uc | |
UAC Credentials | Required | Credentials | This field is visible with the option RT & JT ANALYSE Specify the Universal controller credentials for REST API purposes | |
Runtime Directory | Optional | Text | Specify the Runtime Directory for the Universal Agent Run time user if needed |
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
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
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.
Exit Code | Status Classification Code | Status Classification Description | Status Description |
---|---|---|---|
0 | SUCCESS | Successful Execution | SUCCESS: Successful Task execution |
99 | FAILED | Failed Execution | FAILED: COB Execution request date is a Holiday |
10 | FAILED | Failed Execution | FAILED: TSM service is not in Running status |
5 | FAILED | Failed Execution | FAILED: No Active TSM or COB Agent Found after initiating Start |
1 | FAILED | Failed Execution | FAILED: Exception while executing |
STDOUT and STDERR provide additional information to User. The populated content can be changed in future versions of this integration without notice.
This document references the following documents:
Document Link | Description |
---|---|
Universal Templates | User documentation for creating, working with and understanding Universal Templates and Integrations. |
Universal Tasks | User documentation for creating Universal Tasks in the Universal Controller user interface. |
Credentials | User documentation for creating and working with credentials. |
Resolvable Credentials Permitted Property | User documentation for Resolvable Credentials Permitted Property. |
T24 OSF Generator | 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.
Users and customers are encouraged to report defects, or feature requests at Stonebranch Support Desk.
Initial Version