DFE - User Guide - V1.0
DFE - User Guide - V1.0
User Guide
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.
Document History
Screen of Content
1. Release Highlight.................................................................................................. 4
3. User Guide............................................................................................................ 6
3a.Overview........................................................................................................... 6
3b.Setup................................................................................................................. 7
3d. Reports/Enquiry..............................................................................................26
Reference Documentation....................................................................................27
1. Release Highlight
Data Formatting Engine (DFE) is a common interface framework which is designed in such a way that
it supports both uploading of messages/files received from external system into T24 as well extract
data from T24. DFE is capable of handling both online messages and offline files. DFE supports
delimiter based files and fixed position messages/ files. DFE is capable of handling both synchronous
and asynchronous messages
Background
To maintain and control the interface developments, a common interface engine for data processing is
required which can be parameterized to configure and control various interfaces. The interface
framework has been enhanced further to meet heterogeneous interfacing requirement for SIP.
DFE is capable of supporting both real time and batch processing operational behavior.
Previous Functionality
N/A
New Functionality
A common interface framework that supports both uploading of messages/ files received
from external system into T24 as well as extracting data from T24.
Capable of handling of both online and offline messages/ files and also both synchronous
and asynchronous messages.
Supports delimiter based files and fixed position messages/ files.
Model
Benefits
Provision to set up all the mapping and also to design the layout
Ability to default specific values for delimiter in the flat file
3. User Guide
All applicable sections to be filled out completely for new user guide. Use only the relevant sections
if amending an existing guide
3a.Overview
Data Formatting Engine (DFE) is a common interface framework which is designed in such a way
that it supports both uploading of messages/files received from external system into T24 as well
extract data from T24. DFE is capable of handling both online messages and offline files. DFE
supports delimiter based files and fixed position messages/ files. DFE is capable of handling both
synchronous and asynchronous messages. To maintain and control the interface developments, a
common interface engine for data processing is required which can be parameterized to configure
and control various interfaces. The interface framework has been enhanced further to meet
heterogeneous interfacing requirement for SIP.
3b.Setup
DFE.PARAMETER
This is the overall parameter table to define the file type, mode of transaction and the corresponding
upload and extract path and connector details to be entered. This file holds the details of the system
wide parameters that are required to run the DFE Frame Work. The table captures the interface
information that needs to do the extraction/upload/real-time inward data flow and real time outward.
In addition to that the record can configured with unique file path where the file needs to get extract
or path to pick the file for upload.
DFE MAPPING:
This table is used to define the mapping for each extract file. The ID of this table will be used in the
field DFE.MAPPING.ID in the DFE.PARAMETER table. Mapping Table defines where data for
Inward / outward messages is located within the raw message data passed to APPLICATION OR
Extract from T24 APPLICATION by the DFE framework. The data which is received or extracted by
DFE which then uses the Mapping Table to locate each field from within that raw data
DFE Connector Details: This is mapping table to do the connector details for the outward real-time
service calls / transaction calls to publish the data to the external system
This table is used to give details of the server for the outgoing files from T24 processed online
The connector details will be mandatory in DFE.PARAMETER when the Type and mode of
transaction is selected as “OUT” and “Online”
DFE XML transform: This file holds the XSLT details for transforming the simple XML message
The third party system sends flat file to T24 which holds the information that needs to be updated in
T24. Data formatting engine picks the file from appropriate directory mapped in the interface
parameter table.
To meet the resilience and load balancing behavior, the Batch processing is broken down in to 2
Jobs. JOB2 has to run only after successful completion of JOB1.
JOB1 will be single-threaded job that would pick the incoming file and split them into multiple records
and populate to a WORK table. The work table id will be in the combination of
<MNE>.<INTERFACEID>.<TODAY>.<LINE.NO> of the file for which the record [based on delimiter]
is being processed. The behavior of this JOB1 should be re-runnable, meaning for any rerun there
should not be any duplicates records written to WORK table. On successful completion of JOB1, the
‘.in’ file from DFE.PARAMETER>INPUT.DIR will move to DFE.PARAMETER>ARCHIVE.DIR with an
extension as ‘.pro’.
JOB2 will be multi-threaded job that would pick the records from WORK table and process them
based on DFE.MAPPING definition. On successful completion of processing, the records in WORK
table will be deleted. DFE is capable of logging the processing status and error log.
DFE.PARAMETER: FILE.UPLOAD
Inward file:
BATCH:
Configure the DFE inward batch routines to process the inward file.
Job.1 DFE.INWARD.PRE.PROCESS
Job.2 DFE.INWARD.FILE.PROCESS
TSA.SERVICE: Create a service for the above batch BNK/FILE.UPLOAD and run the service
After the service is over, the file is processed and is available in the path mentioned under the
DFE.PARAMETER
Transaction is updated with the value passed from the inward file.
The third party system sends message to T24 through web application server. Data formatting
engine processes the message and post/update the message in the appropriate T24 table.
DFE’s real time inward processing API forms the OFS message based on the interface mapping
definition and post the message into the t24 application configured in the interface mapping table.
DFE is capable of logging the processing status and error log. If any critical error or warning
message occurs while processing the message details are updated in DFE.INTRF.LOG.
Inward Real-time message process: DFE is capable to process the real-time message coming
from external system to T24 through tSS service. DFE requires the below mapping setup to be done
before processing the message.
DFE.REALTIME.PARAMETER
DFE.TSS: External interface code needs to be updated in the EXTERNAL.CODE field with the
respective DFE interface ID and the field position, length where the system can read the external
interface name.
DFE.TSS
Request Message: SUPERSHARES,20130806,101,112
Output without formatting the response message
Real-time message with formatted response: Configure the response mapping ID to do the
formatting for the OFS response as shown below
Response
JOB1 is multi-threaded that extracts the data from T24 and populate to a WORK file in case of FINAL
MSG SYNC /ASYNC or publish it to third party in case of EACH MSG SYNC/ASYNC. On successful
completion of JOB1, JOB2 is invoked. If the OUT.MSG.POST.TYPE field in DFE.PARAMETER table
is defined as each message synchronous/asynchronous, then JOB1 publishes the message to
CALLJEE sequentially. Else, if it is keyed in as final message synchronous/asynchronous, then JOB1
writes the message to temporary work file.
JOB2 is single-threaded job that picks the records from WORK file. If the OUT.MSG.POST.TYPE
field defined as final message synchronous/asynchronous, then JOB2 concatenates all the
messages in the temporary work file and publishes it as a single message to CALLJEE. DFE updates
the processing status and error log through the API’s.
Real-time Outward – XML: DFE service capable to do the XML extract and converting in to as
SOAP request to post in JMS queues / web service / MQ Queues
DFE.PARAMETER
DFE.MAPPING
DFE.CONNECTOR.DETAILS
The JEE_HOST / PORT is configured in the above table and the record ID must be configured in
DFE.PARAMETER>Connector ID.
DFE.TRANSFORM
Define the XSLT mapping to convert the simple XML in the below mapping table
JOB1 is a multi-threaded that extracts the data from T24 and populate to a temporary WORK files.
The work files get updated in the temp directory path configured in DFE. PARAMETER.
JOB2 is a single-threaded job that picks the records from WORK file. JOB2 concatenates all the
messages in the temporary work file into a single output file. Once concatenation is completed,
temporary work files are deleted.
Outward File Extract – Delimited File: DFE is capable to extract from a valid T24 tables based on
the field configuration done in DFE.MAPPING.
BATCH
BNK/CUSTOMER.EXTRACT
Configure the batch with the below jobs to do the extract.
Job.1 DFE.OUTWARD.FILE.EXTRACT
Job.2 DFE.OUTWARD.FILE.EXTRACT.POST
After running the service the file should be extracted in the configured path defined in the
parameter.
EXTRACT
Output file
3d. Reports/Enquiry
Goto Role Based Home pages >>> Finance Operations >>> Home Page – Finance Manager >>>
General Parameters >>> DFE Framework >>> File extract status
This enquiry will display the overall number of records being extracted out from T24
Exclusions
N/A
Reference Documentation
(Mention very clearly under following heads, what is to be done. )
Section of Model: Retail/Corporate/Wealth/Payments/Treasury/Frameworks/Finance…
Type : NEW (for new feature) or AMEND (to amend existing)
a) Role Based Home Pages
Role Based Home Pages >>> Finance Operations >>> Home Page – Finance Manager >>> General Parameters
>>> DFE Framework
b) Products
c) Processes
Given under section 3c – Deal processing
d) Parameters
Given under section 3b – Set up
e) Outputs