Architecture and Artefacts

This section describes the functional architecture of Transact Explorer and its design and runtime components.
Transact Explorer is a Temenos Transact browser that provides menu-based and enquiry-based access to applications, COS, and versions that connect to Transact using the tb-server API data layer.
The below functional architecture of Transact Explorer illustrates the process of reading data from and writing data to Temenos Transact.

The communication between Transact Explorer and the tb-server API is established using JSON over HTTP(S). The tb-server API communicates with Temenos Transact using TAFJ client libraries, which results in JDBC data calls to the database.

The API layer supports both Queue and Queue-less modes. By default, it supports Queue-less mode of architecture, where the API hits Transact Runtime (TAFJ) directly and communicates with Temenos Transact. If required, you can change the mode to JMS to activate the Queue mode. It uses ReplyQueue and ResponseQueue to post Open Financial Service (OFS) requests and to receive OFS responses respectively.

Deployment Artefacts

Deploying Transact Explorer requires the below artefacts.

Artefact	Description
transact-explorer-wa.war (UI)	This war includes UI components and their configurations.
tb-server.war (API)	This war includes API endpoints and their configuration. Some of the configurations in tb-server are related to python scripts execution.

Product Compatibility

The below table shows the browser compatibility of Transact Explorer.

Browser Name	Version
Mozilla Firefox	Version 60 and above
Google Chrome	Version 60 and above
Microsoft EDGE	EDGE Chromium 87 and above