When we deploy Core Banking systems, one of the most critical parts is their integration into existing satellite systems such as CRM or E-Banking. We prefer standardized communication gateways such as OFS (Open Financial Services) provided by T24 Transact.
Please read this blog to learn crucial OFS modes and their performance-tuning considerations. You can send your transaction in the OFS format to T24 and receive the response in the same standardized OFS format.
OFS Modes
There are four OFS modes that you can use depending on your use case. Choosing the appropriate mode is crucial to avoid performance bottlenecks or high development efforts.
TELNET: For online processing through third-party applications
SESSION: For online processing through browser
GLOBUS: For inter-application processing
BATCH: For processing offline requests from third party
OFS Requests
OFS Write or Update
We use Transaction requests when we update or write information to T24.
Sample OFS VERSION request:
VERSION.NAME/FUNCTION/PROCESS.TYPE/GTS/NO.OF.AUTH,T24SIGNONNAME/PASSWORD,RECORD.ID,MESSAGE.DATA Ex: CUSTOMER,INP/I/PROCESS/0/0,INPUTT/PASSWORD,,NAME.1=ANYNAMEOFS Read request
We use OFS ENQUIRY requests when we read data from T24.
Sample OFS ENQUIRY request:
ENQUIRY.SELECT, T24SIGNONNAME/PASSWORD,ENQUIRY.NAME,SELECTION.CRITERIA Ex: ENQUIRY.SELECT,,INPUTT/PASSWORD,%INDUSTRY
Things to consider in OFS Requests
You should provide the correct function, process type, and version name. Don’t get confused with VALIDATE and VERIFY.
GTS CONTROL for overrides and error checks. The value passed in the OFS string takes prominence over the value in the version.
Number of auth for defining authorizers required. The value passed in the OFS string takes prominence over the value in the version.
NAU processing to define what will happen to the not authorized transaction when we overwrite it through another OFS string.
NAU processing codes
0 Reject OFS message
1 Overwrite the message applicable to INAU records
2 Deletes NAU and reverse life, applicable for RNAU
3 The behavior of 1 and 2
Success or failure indicator in the response
1 SUCCESS
-1 FAILURE, check details in ORD
-2 OVERRIDE, check details in ORD
-3 T24 is offline
OFS Performance considerations
Version level: Proper design and version routine level tuning.
Enquiry level: Proper enquiry design, especially if it’s a NOFILE one.
OFS SOURCE level: Controlling the log and ORD details.
Splitting the time into 3 parts and analyzing the issue
Third-party app to T24 time.
EJB/MDB level and queue waiting time.
T24 processing time.
OFS is a powerful communication gateway. The design of any complex system is crucial for optimal performance. We are happy to support your OFS performance tuning activities.
Happy Performance Engineering!