Getting Started with Fintegrator TODS

Introduction

Fintegrator TODS is a data flow engine for Temenos Transact (T24), built on the Morph Flow processing core. Morph reflects the transformation of Transact XML and JSON structures into normalised, relational SQL, with the ability to drive bulk updates back into Transact through OFS messages.

This guide walks you through accessing the application, navigating the UI, and performing the most common operations.

Access

Web UI (MorphTool)

Open your browser and navigate to:

https://todsdev.fintegrator.eu

This is the main workspace where you can:

  • View and edit T24 field mappings
  • Run and monitor replication jobs
  • Configure system settings
  • Review replication logs

API (Swagger / OpenAPI)

For programmatic access and interactive API exploration:

https://todsdev.fintegrator.eu/api/swagger

Health checks

https://todsdev.fintegrator.eu/api/health
https://todsdev.fintegrator.eu/api/health/ready

Both return Healthy with HTTP 200 when the service is up.

Authentication

MorphTool uses Keycloak for single sign-on. Opening the app redirects you to the Keycloak login page. After a successful login you are returned to your requested page.

Roles:

Role Access
viewer Read-only — browse mappings and replication status
editor Full CRUD — create, edit, and delete mappings and settings

Logout: click your username in the top-right header, then the sign-out icon.

Contact your administrator to request a role assignment.

Quick Start

1. Verify the application is running

curl https://todsdev.fintegrator.eu/api/health
# Expected: Healthy

2. Open the web UI

Navigate to https://todsdev.fintegrator.eu. You should see the MorphTool home page with the navigation menu on the left.

The UI uses Blazor Server with a persistent SignalR WebSocket connection. Ensure your browser has JavaScript and WebSockets enabled.

3. Browse T24 applications

The home page lists all T24 applications registered for replication. Common examples:

Application Description
CUSTOMER Customer master data
ACCOUNT Account information
FUNDS.TRANSFER Payment transactions
TELLER Teller transactions
STANDING.ORDER Standing orders

Via API:

curl https://todsdev.fintegrator.eu/api/applications
# Returns: ["CUSTOMER", "ACCOUNT", "FUNDS.TRANSFER", ...]

4. View field mappings for an application

In the UI: select an application from the dropdown in the Field Mapping page. The grid loads all mapped fields — field name, SQL type, Map Name, Index Type, and more.

Via API:

curl https://todsdev.fintegrator.eu/api/mappings/CUSTOMER

Example response entry:

{
  "t24Application": "CUSTOMER",
  "fieldNumber": 0,
  "fieldTag": "c0",
  "fieldName": "CUSTOMER.CODE",
  "fieldType": "D",
  "fieldFormat": "10R",
  "fieldTypeSql": "int",
  "fieldIndexType": -1,
  "multiValue": "S",
  "mapName": "CustomerCode",
  "mapGroup": null,
  "mapDescription": "Customer unique identifier"
}
Field Description Example
fieldName T24 field name CUSTOMER.CODE
mapName ODS column name CustomerCode
fieldTypeSql SQL Server data type int, varchar(50)
fieldIndexType Indexing: 0 = clustered, -1 = none -1
multiValue S = single value, M = multi-value S

5. Edit a field mapping

In the UI: click a row in the Field Mapping grid, edit the cell inline (Map Name, SQL Type, Index Type, etc.), and save. Changes are immediately persisted.

Via API:

curl -X PUT https://todsdev.fintegrator.eu/api/mappings/0 \
  -H "Content-Type: application/json" \
  -d '{
    "t24Application": "CUSTOMER",
    "fieldTag": "c0",
    "fieldName": "CUSTOMER.CODE",
    "fieldTypeSql": "int",
    "fieldIndexType": -1,
    "multiValue": "S",
    "mapName": "CustomerCode",
    "mapDescription": "Customer unique identifier"
  }'

Returns HTTP 204 on success.

6. Regenerate ODS objects

After editing mappings, click Create Views for the application to regenerate the ODS table, view, and replication stored procedure. This is required before the next replication run picks up your changes.

Key Concepts

T24 Application — a business entity in Transact (e.g. CUSTOMER, ACCOUNT). Each application has fields that store data in T24.

Field Mapping — a configuration record that links a T24 field to an ODS column, defining the column name (MapName), SQL data type, indexing strategy, and metadata.

ODS (Operational Data Store) — the SQL Server database (Morph26) where T24 data is replicated for reporting and analytics.

spCreateViews / Create Views — the operation that reads all field mappings for an application and generates the corresponding ODS table (tbXXX), view (vwXXX), and replication procedure (spXXX).

Replication — the process that reads change data from the source system (via CDC) and populates the ODS. Triggered manually via the Replication panel or scheduled.

UI Overview

┌──────────────────────────────────────────┐
│  Header — logo, connection status        │
├──────────────┬───────────────────────────┤
│  Left menu   │  Main content area        │
│              │                           │
│  Field Map.  │  Grid / form / log view   │
│  Replication │                           │
│  Settings    │                           │
│  ...         │                           │
└──────────────┴───────────────────────────┘

The data grids (Syncfusion) support:

  • Sortable columns — click a column header
  • Filterable columns — use the column filter dropdown
  • Inline editing — click a cell to edit
  • Pagination — controls at the bottom of the grid

The connection status indicator in the top-right shows the SignalR state. The UI auto-reconnects if the connection drops.

Tips

  • Use column filters when working with applications that have many fields (some have 500+).
  • Test on dev first — always validate field mapping changes on a non-production environment before applying to live.
  • Back up before bulk changes — the Fields Advisor can rename many fields at once; ensure a DB backup is current beforehand.
  • Create Views after every mapping change — edited mappings do not affect the ODS table until Create Views is run.
  • Supported browsers: Chrome 90+, Edge 90+, Firefox 88+, Safari 14+ (limited). JavaScript and WebSockets required.

Keyboard Shortcuts

Shortcut Action
Ctrl+F Focus the search / filter box
Enter Confirm an inline edit
Esc Cancel an inline edit
F5 Refresh the current grid