🛠️Production support
Incident diagnosis, record locking, batch monitoring, escalation checklists, and the first 30 days after a go-live.
19 articles in this topic.
TPH fundamentals
The moment TPH becomes real is usually around 2am during a production incident. Payments are not going out. Thirty people are on a call. This is what you actually need to know before that call happens.
Read the articleTPH diagnosis
Trace a failed TPH payment from arrival through validation, routing, posting, scheme handoff, acknowledgement, repair, and retry while controlling duplicate risk.
Read the articleInfrastructure
A high-level look at running Temenos Transact in containers, orchestrating TAFJ workloads with Kubernetes, and migrating to AWS, Azure, or Temenos Cloud.
Read the articlePlatform governance
What the Temenos Extensibility Framework (TEF) is, why it replaces legacy L3 core modifications, and how it makes T24 upgrades faster, safer, and cheaper.
Read the articleProduction support
The difference between a junior analyst and an experienced one is often ten minutes and a short checklist. Five questions to answer before you pick up the phone.
Read the articleOperations
The project team has gone. The environment is live. A practical account of what operations teams encounter in the first month after a TAFJ cutover — and what to do about it.
Read the articleProduction support
A practical guide to record locking in T24: why locks exist, when they become a support problem, and how to investigate before clearing them.
Read the articleTAFJ operations
TAFJ distributes its logs across six different locations maintained by different parts of the stack. Where each one lives, what it covers, and the order to check them in — before an incident makes the question urgent.
Read the articleCOB and support
A practical T24 operations guide to proving that a completed batch produced the expected business outcome, not only a successful return status.
Read the articleGetting started
New to T24? The fastest way to get useful is not to memorise commands. It is to understand flow, state, and what healthy looks like before the details have anywhere to stick.
Read the articleIntegration operations
When the ActiveMQ Artemis paging-store directory grows during TAFJ operation, the first question is whether it is expected or a signal of a deeper issue. A practical guide to reading the evidence safely — queue metrics, consumer checks, safe containment, and when to escalate.
Read the articleIntegration & Production support
A systematic diagnostic sequence for tracing a failed OFS request from entry point to T24 processing — transport, authentication, syntax, validation, posting, and response-delivery failure stages, with log sources and redaction guidance.
Read the articleTAFJ operations
A WAR file was deployed, the logs show success, but the browser still shows old behaviour. Why? Because deployment and activation are not the same thing. A practical guide to the TAFJ deployment lifecycle, cache layers, and how to verify what is actually running.
Read the articleCOB operations
A practical guide to the checks to make when T24 COB does not continue normally after a database restore — state verification, evidence gathering, validation, and reconciliation.
Read the articleProduction support
A practical guide to T24 database storage growth — the difference between data and transaction-log storage, why growth and reusable space are not the same thing, and what support teams should monitor before capacity becomes a problem.
Read the articleProduction support
A practical, environment-neutral guide to validating a restored T24 service — covering infrastructure, database, application, integration, batch state, business validation, and sign-off evidence.
Read the articleIntegration support
A systematic diagnostic sequence for when a T24 messaging queue has depth but no consumer is processing — distinguishing inactivity from connectivity, channel, application, retry, and dead-letter conditions.
Read the articleIntegration troubleshooting
When an E-Advice PDF arrives with the wrong content — or no content at all — the problem is almost never the PDF itself. A systematic guide to diagnosing parser errors caused by unexpected response content, covering response type, headers, encoding, upstream error pages, document generation, and transport.
Read the articleOFS troubleshooting
Diagnose T24 OFS response failures by transport, authentication, syntax, validation, authorisation, posting, and response-delivery stage.
Read the article