top of page

How to implement Problem Alerting for T24 OFS Message Queues

In a T24 Core Banking system, the OFS (Open Financial Standard) layer connects satellite systems to your T24 banking engine. We use OFS modes such as SESSION, TELNET, GLOBUS, BATCH, and OFS types such as READ or WRITE.


Choosing the appropriate mode is crucial to avoid performance bottlenecks or high development efforts. As a reminder of this critical concept, please keep the following OFS modes in mind:

  • 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

 

You should ensure that you keep such OFS messages and process them promptly. In T24, we distinguish OFS online and OFS offline queues. As their name explains, the former is often more critical than the latter. 





Spikes in OFS messages?

There can be situations in which many OFS requests are generated, and your core banking system can't process them in real time. We use the concept of message queues to ensure no information is lost, even during peak hours. Think about a file upload process. You get a big payment file with thousands of payment records. Your file upload process generates OFS messages, and the T24 core banking system must run steps such as AML, payment execution, and confirmation.


When your system slows down, OFS messages could pile up, and your Bank might process customer requests too late. 


Problem Alerting on a high number of OFS messages

In one of our projects, our customer's requirement was: "As a T24 service owner, I would like to receive a problem ticket if there are more than 1000 OFS messages in the online or the offline queue."


Our monitoring approach was

  • Validate the number of messages in the OFS offline and OFS online queue

  • Visualize these numbers on Dashboards

  • Create metric events and add appropriate thresholds

  • Add alerting conditions to escalate such issues


If you want to transform your monitoring from reactive to proactive and reduce MTTR by 90%, reach out; we are happy to help.


Keep up the great work! Happy Performance Engineering!





58 views0 comments

Recent Posts

See All

Comments


bottom of page