Live status for every T24 agent service. COB pipeline tracking across all 5 stages. One-click start/stop without SSH. Runs on your existing WebSphere server — nothing new to provision.
Agent Monitor connects directly to your T24 Monitor Services via SOAP and delivers live status — no polling agents, no cloud dependency, no Temenos licence required beyond what you already have.
Running, Stalled, Down, and Stopped status for every T24 agent service — pulled via TSASTATUSDETS SOAP and refreshed every 30 seconds automatically.
5-stage Close of Business progress view (A → S → R → D → O) with per-stage batch counts, completion percentage, and pulse animation on active stages.
Send SERVICECONTROL=AUTO or SERVICECONTROL=STOP to any agent directly from the browser via WSUPDATETSASERVICE. No SSH session needed.
TSM is always the first service shown — displayed as a hero card with a live pulse ring when running, and an "Unreachable" fallback if the SOAP query fails.
Secure login with JWT tokens, file-based user store, and AES-encrypted SOAP credentials. No credentials are ever returned to the browser in plain text.
SOAP endpoint, credentials, and T24 service list are all editable from the Settings page — no WAR redeploy needed. Changes take effect within 60 seconds.
Configurable auto-refresh intervals for both agent status (default 30s) and COB pipeline (default 10s). Topbar toggle lets ops teams enable or pause refreshing.
Single WAR file deployment on your existing WebSphere server. No agents to install, no cloud accounts to create, no network changes required.
Tested on IBM WebSphere running on AIX — the most common T24 production environment in the Middle East and Africa. Also runs on standard Linux.
Agent Monitor sits alongside your T24 installation and speaks SOAP directly to T24 Monitor Services — the same interface Temenos itself uses.
Queries each agent service individually by SERVICE.NAME filter. Namespace-aware XML parsing prevents silent empty results.
Single call with no filter returns all COB batches. Parses RECID, BATCHSTAGE, and PROCESSSTATUS (0/1/2) to build the pipeline view.
START sends SERVICECONTROL=AUTO, STOP sends SERVICECONTROL=STOP. Service names with '/' are automatically converted to '^' for T24 compatibility.
No consultants needed on-site, no complex installation procedures. If you can deploy a WAR to WebSphere, you can deploy Agent Monitor.
Copy agent-dashboard.war to your WebSphere server and deploy through the WebSphere Admin Console. Standard WAR deployment — takes under 10 minutes.
Log in with the default credentials, open Settings, and enter your T24 Monitor Services host, port, credentials, and service path. Changes are encrypted and take effect immediately — no restart needed.
Paste your T24 agent service names into the Service List editor in Settings — one per line. Agent Monitor will query each one on the next refresh cycle. Add or remove services any time without redeploying.
Agent Monitor is designed to work with the infrastructure T24 banks already have — no new licences, no cloud accounts.
Agent Monitor makes SOAP calls from your WebSphere server to your T24 instance — both on your internal network. No T24 data is ever sent to CompNucleus or any external service. Your bank's operational data never leaves your environment.
How Agent Monitor translates raw T24 SOAP values into the dashboard display.
A COB stage is marked "completed" only when ALL batches in that stage have status 2. This ensures the overall progress bar accurately reflects the actual COB position.