Trace Ability

Traceability
Release: R19 AMR

May 2019
Information in this document is subject to change without notice.
No part of this document may be reproduced or transmitted in any form or by any means, for any purpose, without the express written permission
of TEMENOS HEADQUARTERS SA.
© 2019 Temenos Headquarters SA - all rights reserved.

Traceability
Table of Contents
Overview 3
Setup 4
Deal Processing 6
Enquiry 11
2
Traceability
Overview
The financial institutions are subject to a high number of complex banking oper-
ational sectors that might have to prove to certain regulatory auditors or even cus-
tomers when there is a deviation in financial data such as account balance etc.
Banking institutions must be able to trace the property elements coming in a trans-
action request from multiple third parties into T24 System. Then this trace prop-
erties information send to a trace data repository called micro services for further
usage. This push operation is an asynchronous process from the main transaction
request.
3 Overview
Traceability
Setup
l To enable traceability for an application in T24, you need to setup
T24.TRACE.PARAMETER application as ID.
l It can also be restricted to specific version level traceability using

VERSION.NAME field.
l TRACE.REQURIED field should be set to YES for enabling traceability for this
setup.
l When traceability enabled for,
1. Application level only – It allows tracing for the entire application’s
request if it is a successful transaction.
2. Specific list of versions only – It allows tracing only for the application
request coming with the specified versions, if it is a successful trans-
action.
l DESTINATION.STATIC field should be configured with destination queue
name, connection factory and reply queue name delimited by #. These details
are essential to send trace log information to Micro service.
The format should be,
<TraceabilityDestinationQueue>#<ConnectionFactory>#<TraceabilityReplyQueue>
Where, Destination queue and Reply queue is mandatory. System defaults second
position with ‘ConnectionFactory’ if no value is given.
Setup 4
Traceability
T24.TRACEABILITY.SERVICE sends trace log from T24.TRACE.INFO to the destination

queue mentioned in this field first position and expects response in reply queue
given in 3rd position of this same field. The DESTINATION.STATIC of application
level record takes precedence over SYSTEM level record in this
T24.TRACE.PARAMETER if defined.
5 Setup
Traceability
Deal Processing
With traceability enabled for an application or version in T24.TRACE.PARAMETER
and if IRIS has integrated to send traceability property elements as ‘key name value
pair’ in OFS header 25th position, then T24 accepts and extracts those elements,
and store them in T24.TRACE.INFO. T24.TRACE.INFO is a store and forward table in
T24, which is FIN level live table.
Sample OFS Request format with Traceability properties in User info header sec-
tion:
FUNDS.TRANSFER,INPUT/I/PROCESS,INPUTT/123456/GB0010001/////////////////////-
/$TMK$TRACE.ORIG.MSG$TMK$$TMV$DFS123%%##@@$TMV$$TMK$TRACE.SIGNATURE$TMK$$TM-
V$@#$%^f-
ds$%^%$TMV$$TMK$TRACE.PUBLIC.KEY$TMK$$TMV$@#$%%^d-
ffsssff$TMV$$CMK$CATEG.TXN.ID$CMK$$CMV$FT234568901$CMV$$CMK$CATEG.COMP.CODE-
$CMK$$CMV$JPMCBANK$CMV$/,,TRANSACTION.TYPE-
=AC,DEBIT.ACCT.N-
NO=10944,DEBIT.AMOUNT=1000,DEBIT.CURRENCY=USD,CREDIT.ACCT.NO=10995
Note: The OFS Response is as usual and there is no change in that

format for traceability feature.
The Trace log storage is possible if the IRIS transactions or third parties send such
OFS request to T24 system where traceability enabled for that corresponding applic-
ation or version and then the incoming traceability property elements are captured
into this log only if it is a successful transaction in T24 system. The enquiry
T24.TRACE.INFO can be used to view this log content.
Trace Log View:
Deal Processing 6
Traceability
Trace log stored with unique key in T24.TRACE.INFO table.

TRACE.TYPE:- Trace type of that particular transaction request. That is, trace
enabled for an application or version then that corresponding transaction’s OFS
request containing version id or application name will be stored in this TRACE.TYPE
field.
TRANSACTION.ID:- Holds transaction id of that particular successful transaction for
which this trace has been logged.
COMPANY.CODE:- Holds Company id for which the transaction happened.
CREATION.TIME:- Holds the trace log creation date and time. Server date time
stored in this field.
CREATION.TIME.LOC:- Holds local zone date time in which this trace log has been
created. This will have value only when USE.LOCAL.TIME field in SPF is enabled.
TM.KEY.NAME:- Holds Trace property elements key name, which comes in an
incoming OFS request from IRIS. In OFS Header, user info section 25th position
comes with trace property elements key value pair. That key name will be stored in
this field, which is associated multi value to TM.KEY.VALUE field in this log table.
The key value pair format from OFS header 25th position of user info section is:
$TMK$keyname1$TMK$$TMV$keyvalue1$TMV$$TMK$keyname2$TMK$$TMV$keyvalue2$TMV$
$CMK$c-
ategKey-
name1$CMK$$CMV$CategKey-
value1$CMV$$CMK$categKeyname2$CMK$$CMV$categkeyvalue2$CMV$
7 Deal Processing
Traceability
Where, key name between $TMK$ will be extracted and store in this

TM.KEY.NAME field.
Corresponding key value between $TMV$ will be extracted and store in
TM.KEY.VALUE field as both
the fields are associated multi value set.
TM.KEY.VALUE:- Holds Trace property elements value of that corresponding key
name stored in TM.KEY.NAME field.
CM.KEY.NAME:- Holds category property elements key name(s) between $CMK$.
CM.KEY.VALUE:- holds category property elements key value(s) between $CMV$ of
those key name(s).
Trace Data Repository:
In Synchronous way, this trace log will be send to a micro service through MDB by
T24.TRACEABILITY.SERVICE and then deleted from T24.TRACE.INFO log table for
successful response from Micro service. In case of failure response, T24 service will
store MS.ATTEMPT field with number of attempts and then retry to send in next iter-
ation.
In this example, the TraceabilityQueue and TraceabilityReplyQueue configured in
T24.TRACE.PARAMETER and same in Jboss application server has been projected
here in Jboss Administration Console to see this sample message(s) inflow and out-
flow.
After Starting T24.TRACEABILITY.SERVICE from Application server Context(TAFJEE –
Execute Servlet), Note down the Message Count reduced after MDB consumed
these messages from TraceabilityQueue and send it to Micro Service. This T24 ser-
vice can be run as AUTO service according to bank need, to pick up all trace log
data from T24.TRACE.INFO to send to Micro Service in parallel, as Online Trans-
actions are continuous inflow during business days. So according to this, the Queue
count also varies as how many messages consumed or added and how many mes-
sages are yet standing in queue for MDB to consume etc.
Deal Processing 8
Traceability
Then MDB updates Response in TraceabilityReplyQueue. This picture represents

the Messages added is 4 and Message Count 3 is standing in ReplyQueue which is
yet to be received by T24 service to act accordingly.
Once the response for all these messages received at T24 side from this JMS queue,
then this message count in TraceabilityReplyQueue will be reduced accordingly and
corresponding T24.TRACE.INFO log entry is deleted for the successful response.
Otherwise, attempt tried count will be updated in MS.ATTEMPT by
T24.TRACEABILITY.SERVICE. T24.log updated for either Successful or failure
response for sending trace log message to Micro Service. Now, current all trace
logs are sent successfully, so T24.log also updated with successful response details
for corresponding trace log id i.e UUID.
In case of JMS failure or time out reason the T24 receives failure response will not
delete trace log in T24 and then When T24 Service re-try to send same message in
next iteration the MDB/Micro service will have intelligence to check whether same
message already posted in Micro service and it just sends back successful response
indicator to T24 so that trace log entry will be deleted from T24. There will not be
any duplicate message update in Micro service for any re-try attempt from T24.
T24 trace log posted by T24 service to Micro Service can be viewable from REST Cli-
ent with this URL if Micro service deployed and running on specific port and host.
Refer Micro Service Deployment guide for more details.
Now, Micro service running in 8085.
URL: http://localhost:8085/system/traceLogs?category=<anycategory>
Category is nothing but, the one which is sent in Json Message from T24 service.
Sample Json message format send by T24 service is:
9 Deal Processing
Traceability
{ "categories": [ "CATEG.TXN.ID: FT1234568901",

"CATEG.COMP.CODE: JPMCBANK"],
"message": { "encoding": "none", "content": { "TRACE.ORIG.MSG":

"DSH33123124#$$%*DSFSD34", "TRACE.SIGNATURE": "erwer2314&%$ds6%4dsdf",
"TRACE.PUBLIC.KEY": "jfkl239%h5$"} } }
These are the values framed from T24.TRACE.INFO which is from OFS 25th position.
One of category key name CATEG.COMP.CODE has been used in URL to view mes-
sage in Micro Services.
GET URL: http://localhost:8085/system/traceLogs?category=CATEG.COMP.CODE:
SMBCBANK
Deal Processing 10
Traceability
Enquiry
The Enquiry T24.TRACE.INFO can be used to view Trace log table in T24.
You can find the new enquiry link by navigating under System Administration menu
> ‘Traceability’ > ‘Trace Log Display’.
11 Enquiry

Trace Ability

Uploaded by

Copyright:

Available Formats

Trace Ability

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Trace Ability

Uploaded by

Copyright:

Available Formats

Traceability

Release: R19 AMR

Information in this document is subject to change without notice.

© 2019 Temenos Headquarters SA - all rights reserved.

l It can also be restricted to specific version level traceability using

T24.TRACEABILITY.SERVICE sends trace log from T24.TRACE.INFO to the destination

Note: The OFS Response is as usual and there is no change in that

Trace Log View:

Trace log stored with unique key in T24.TRACE.INFO table.

Where, key name between $TMK$ will be extracted and store in this

Then MDB updates Response in TraceabilityReplyQueue. This picture represents

{ "categories": [ "CATEG.TXN.ID: FT1234568901",

"message": { "encoding": "none", "content": { "TRACE.ORIG.MSG":

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.