🔄Migration
TAFC to TAFJ migration — compilation, DBTools, descriptors, go-live challenges, and how to avoid the blind spots that derail most upgrades.
11 articles in this topic.
TAFC to TAFJ
The routine compiled. It ran. It produced an output file with a header and a footer. There were no detail lines. A real migration debugging case involving derived DICT fields and the TAFJ selection layer.
Read the articleTAFC to TAFJ
In TAFC you ran a SELECT in the command line. In TAFJ that is gone. The replacement is DBTools — a separate console with its own users, its own modes, and a 200-row default limit nobody mentions.
Read the articleTAFC to TAFJ
In TAFJ, editing source code changes nothing until you compile, package, and deploy. The full pipeline: tCompile, tIntegrate, tComponentSplitter, tMerge — and what each one does.
Read the articleTAFC to TAFJ
The honest answer is: it depends on what you are building. A practical guide to choosing between jBC and Design Studio in TAFJ, with a simple decision rule that works in production.
Read the articleTAFC to TAFJ
The DICT item still exists. The routine compiles. But the runtime behaviour is different. A practical guide to descriptor-driven logic in TAFJ and why it is not what it looks like.
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 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 articleMigration risk
The status report says green. The project team says on track. Six warning signals that tell you what the dashboard does not — and the questions that surface the truth.
Read the articleCareer
The TAFC-to-TAFJ migration wave is still moving through the industry. Consultants who can credibly pitch migration expertise are commanding better contracts. The three knowledge layers, how to frame your experience, and the mistakes that make experienced people sound junior.
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 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 article