Transact Architecture Overview TR1PRARC -

R23 Revision 1 English

©2023 Temenos Headquarters SA - all rights

reserved.
Warning: This document is protected by copyright
law and international treaties. Unauthorised
reproduction of this document, or any portion of
it, may result in severe and criminal penalties, and
will be prosecuted to the maximum extent
possible under the law.
 Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Table of Contents

Table of Contents ................................................................................................................................................................................... 1

Document History .................................................................................................................................................................................. 5
Introduction ............................................................................................................................................................................................. 6
Lesson Overview ............................................................................................................................................................................................... 6
Your Course » Objective and Learning Outcomes .................................................................................................................................. 7
Your Course » Timetable ................................................................................................................................................................................ 8
Technology Overview ...................................................................................................................................................................................... 9
Technology Overview » Temenos Banking Cloud ................................................................................................................................ 11
Technology Overview » Two Ways to Consume ................................................................................................................................... 12
Technology Overview » Temenos Banking Architecture .................................................................................................................... 13
Technology Overview » Key Characteristics .......................................................................................................................................... 15
Technology Overview » Bunch of Technologies ................................................................................................................................... 17
Technology Overview » Temenos Offers Choice .................................................................................................................................. 18
Lesson Summary ............................................................................................................................................................................................ 19
Enterprise Framework ......................................................................................................................................................................... 20
Lesson Overview ............................................................................................................................................................................................ 20
Enterprise Framework » Overview ............................................................................................................................................................ 21
Enterprise Framework » Design Framework » Overview.................................................................................................................... 22
Enterprise Framework » Design Framework » SDLC ........................................................................................................................... 23
Enterprise Framework » Data Framework .............................................................................................................................................. 24
Enterprise Framework » Data Framework » DLM ................................................................................................................................. 25
Enterprise Framework » Data Framework » TDH ................................................................................................................................. 26
Enterprise Framework » Platform Framework ....................................................................................................................................... 27
Enterprise Framework » Platform Framework » TAFJ ......................................................................................................................... 28
Enterprise Framework » Platform Framework » TAFJ ......................................................................................................................... 29
Enterprise Framework » Platform Framework » Common Components ....................................................................................... 30
Enterprise Framework » Security Framework ........................................................................................................................................ 31
Enterprise Framework » Security Framework » Authentication & Authorization ........................................................................ 32
Enterprise Framework » Security Framework » PAPUI Editor ........................................................................................................... 33
Enterprise Framework » Integration Vs Interaction ............................................................................................................................. 34
Enterprise Framework » Integration Options ......................................................................................................................................... 35
Enterprise Framework » API Framework ................................................................................................................................................. 36
Enterprise Framework » API Framework » REST API ............................................................................................................................ 37
Enterprise Framework » API Framework » Rest Structure .................................................................................................................. 38
Enterprise Framework » API Framework » IRIS R18 ............................................................................................................................. 39

2 ©2023 Temenos Headquarters SA - all rights reserved

 Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » API Framework » IRIS Architecture ............................................................................................................. 40

Enterprise Framework » Event Framework ............................................................................................................................................. 41
Enterprise Framework » Event Framework » Overview ...................................................................................................................... 42
Enterprise Framework » Event Framework Design Time.................................................................................................................... 43
Enterprise Framework » Event Framework Runtime ........................................................................................................................... 44
Enterprise Framework » Event Framework Runtime ........................................................................................................................... 45
Enterprise Framework » Extensibility Framework » Overview .......................................................................................................... 46
Enterprise Framework » Extensibility Framework » Overview .......................................................................................................... 47
Enterprise Framework » Extensibility Framework » How it Works .................................................................................................. 48
Enterprise Framework » Extensibility Framework » Key Features ................................................................................................... 49
Enterprise Framework » Extensibility Framework » Key Features ................................................................................................... 50
Enterprise Framework » Extensibility Framework » Adapter ............................................................................................................. 51
Enterprise Framework » Extensibility Framework » Adapter ............................................................................................................. 52
Enterprise Framework » Extensibility Framework » Use case ........................................................................................................... 53
Enterprise Framework » Summary ............................................................................................................................................................ 54
Lesson Summary ............................................................................................................................................................................................ 55
Practice ................................................................................................................................................................................................... 56
Quiz.................................................................................................................................................................................................................... 56
Architecture and User Journey ......................................................................................................................................................... 57
Lesson Overview ............................................................................................................................................................................................ 57
Transact Architecture » Traditional On Premise ................................................................................................................................... 58
Transact Architecture » Transact UXP Browser Architecture ............................................................................................................ 59
Transact Architecture » User Agents ........................................................................................................................................................ 60
Transact Architecture » UXP Browser ....................................................................................................................................................... 61
Transact Architecture » UXP Browser ....................................................................................................................................................... 62
Transact Architecture » UXP Browser Architecture .............................................................................................................................. 63
Transact Architecture » Component Flow .............................................................................................................................................. 64
Transact Architecture » Transact Java ..................................................................................................................................................... 65
Transact Architecture » Transact Java ..................................................................................................................................................... 66
Transact Architecture » TAFJ ...................................................................................................................................................................... 67
Transact Architecture » TAFJ ...................................................................................................................................................................... 68
Transact Architecture » Transact Database............................................................................................................................................ 69
Transact Architecture » Transact Database............................................................................................................................................ 70
Transact Architecture » Client Application / External Systems ......................................................................................................... 71
Transact Architecture » Client Application ............................................................................................................................................. 72
Transact Architecture » JMS Queues ....................................................................................................................................................... 73
Transact Architecture » JMS Queues ....................................................................................................................................................... 74

3 ©2023 Temenos Headquarters SA - all rights reserved

 Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Enterprise Resources ....................................................................................................................................... 75

Transact Architecture » Enterprise Resources ....................................................................................................................................... 76
Transact Architecture » Enterprise Resources ....................................................................................................................................... 77
Transact Architecture » Enterprise Resources ....................................................................................................................................... 78
Transact Architecture » Inside J2EE Application Server ...................................................................................................................... 79
Transact Architecture » Transact Architecture ...................................................................................................................................... 80
Transact Architecture » Queue-less Transact Explorer Architecture .............................................................................................. 81
Transact Architecture » Transact Explorer .............................................................................................................................................. 82
Transact Architecture » TB-Server ............................................................................................................................................................ 83
Transact Architecture » Transact Explorer » Queue-less Architecture ........................................................................................... 84
Transact Architecture » Transact Explorer » Queue Architecture .................................................................................................... 85
User Journey » Steps to Capture New Customer .................................................................................................................................. 86
User Journey » Using UXP Browser ........................................................................................................................................................... 87
User Journey » Input Customer Record ................................................................................................................................................... 88
User Journey » Save Customer Record .................................................................................................................................................... 89
User Journey » Login as Another User ..................................................................................................................................................... 90
User Journey » Authorize Customer Record .......................................................................................................................................... 91
User Journey » Query Customer ................................................................................................................................................................ 92
User Journey » View Result ......................................................................................................................................................................... 93
User Journey » Using Transact Explorer .................................................................................................................................................. 94
User Journey » Input Customer Record ................................................................................................................................................... 95
User Journey » Save Customer Record .................................................................................................................................................... 96
User Journey » Login as Another User ..................................................................................................................................................... 97
User Journey » Authorize Customer Record .......................................................................................................................................... 98
User Journey » Query Customer ................................................................................................................................................................ 99
Lesson Summary ..........................................................................................................................................................................................100
Practice ................................................................................................................................................................................................ 101
Quiz..................................................................................................................................................................................................................101
Glossary................................................................................................................................................................................................ 102
Glossary » Acronyms ...................................................................................................................................................................................102
Glossary » Acronyms ...................................................................................................................................................................................103
Glossary » Acronyms ...................................................................................................................................................................................104

4 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Document History

Author Version Release Date Comments

TLC CaTS 1.0 1-Jan-23 Initial document.

5 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Introduction
Lesson Overview
In this lesson, I am going to describe what your course is all about, and Technology Overview.

6 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Your Course » Objective and Learning Outcomes

This course will allow you to: Explain Transact Architecture Overview and key components. In particular you will be able to:
Discuss Temenos Technology. Outline Temenos Banking Architecture Landscape. Analyze the key characteristics of Temenos
Technology. Identify Temenos Transact Enterprise Framework. Explain Transact UXP Browser Architecture. Outline Transact
Explorer Architecture.

7 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Your Course » Timetable

’ W ’ , ’
Architecture and User Journey.

8 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Technology Overview
Transact architecture has undergone major changes so far. We will now discuss how these changes came to be. What you
see here is a very simple Revolutionary Architecture. Client Server Architecture: Transact was previously called GLOBUS.
The very early implementations of GLOBUS had a simple client-server architecture. The database that was used previously
was a product of IBM, called uniVerse. In a typical client-server architecture, GLOBUS and uniVerse were installed on one
, ’ o
access GLOBUS. A terminal emulation software would allow the users access to a text terminal and all its applications such
as command line interfaces (CLI) and text user interface applications through telnet, ssh, or dial-up. There are lots of terminal
emulation software available like putty and reflection. All client machines connected to the GLOBUS Server used a telnet
protocol. GLOBUS moved away from its classic user front end to a Graphical User Interface front end, called the GLOBUS
Desktop. It was a client software written in Visual Basic. In this architecture too GLOBUS with its database – universe or jBASE
used to exist on a server along with the operating system. Multi-Tier Architecture: Transact architecture changed drastically
from release R04. Web browser software like Internet Explorer or Mozilla Firefox can now be used as the User Interface. This
change introduced a lot of new layers to the Transact architecture. You can use browsers like Edge and Chrome as a client.
The Web Server will serve the client. Any request coming from a client will be processed by the Web Server. The Web Server
receives the request from the client and forwards it to the Transact Application Server. It also sends back the processed
response to the client. Like the Web Server Layer, the Transact Application Server Layer can have one or more Transact
Application Servers. It will receive the requests from the Web Server, process it and send back a response to the Web Server.
Each Transact Application Server will have runtime (TAFC) installed. The reason for this is that it provides the run-time for
Transact. The Database Server Layer is where all the Transact data is stored. We moved to run Transact as Java by
introducing a runtime TAFJ which is completely built and runs on Java. With this, we have introduced Enterprise Framework
Architecture. Cloud Ready: We were Cloud ready and our Transact can be deployed on Virtual Machines. Cloud Native and
Agnostic: Our Software is Cloud Native and Cloud Agnostic, Temenos Banking Cloud: The Temenos Banking Cloud is the
next ’ , R ,
Wealth, Corporate, SME, etc. The focus was to scale instantly and securely and also enhance our functional solutions. We
are still growing and progressing in the Banking Cloud platform.

9 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

10 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Technology Overview » Temenos Banking Cloud

What you see here is Temenos Banking Cloud overview. Let us first explore the key components of Temenos Banking Cloud.
Temenos Banking Capabilities (TBC) are self-contained business functionality/capabilities that can exist on their own or in
combination with other Banking Capabilities to realize a Banking Service. It has a collection of APIs and events and may
contain Microservices. These are grouped by Business Domain. Each of them can be independently upgradable Examples:
Loans, Deposits. Temenos Banking Services (TBS) – these are specific solutions that we compose from the underlying
Banking Capabilities and Microservices. They are designed for rapid consumption and are focused on very specific
opportunities. Examples would include our Buy Now Pay Later service, Deposits, Retail Lending Fulfilment Service, etc. TBS
combines the functionalities of one or more TBCs. Temenos Enterprise Services (TES) – These are the main banking
platforms that we provide – they represent our main product lines and are consumed by banks as a way to offer a broad
strategic solution to their innovation and operational needs. It is available as: Retail Enterprise Service; Business Enterprise
Service, etc. Temenos Banking Services and Capabilities can be consumed on the Temenos Banking Cloud or run by the
bank on the cloud or on-premise – ’ -composed Temenos
Banking Services, or flexibly assemble, configure, and extend underlying Temenos Banking Capabilities, and combine with
pre-integrated solutions from the Temenos Exchange. Temenos Composable Banking allows you to: Compose from the
broadest, deepest collection of pre-assembled services and banking capabilities. Deliver fast and continuously - managed
by yourself or by Temenos – on-premise or in the cloud. Innovate on top, extend banking capabilities, or consume
pre-integrated partner solutions. We deliver solutions on our Open Platform for Composable Banking This lets all our clients
and stakeholders: Explore what is possible through our APIs and open documentation. Develop around our solutions using
our Open APIs and Extensibility Framework. Deploy and test solutions on a Continuous Deployment basis. And then Extend
the solutions by collaborating with Temenos Exchange fin techs and innovators.

11 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Technology Overview » Two Ways to Consume

Temenos offers a choice of who runs the Temenos Software. Temenos Banking Cloud - Temenos SaaS offering – Temenos
runs the Software. Temenos Banking Cloud is a suite of cloud hosting, management services and development tools that
help clients harness the true potential of the Temenos banking software in a managed cloud environment, enabling them to
run, test and deploy applications in the cloud in a rapid manner, achieving speed to market and faster return on investment.
“ ” or their banking applications to the
Temenos SaaS team. Bank runs the software. Although Temenos SaaS is an option for clients to use our software, SaaS is
N “ ” -Premise, or within their
own cloud subscription. The summary here is we follow a single code base for all our software delivery and consumption
models regardless of how you deploy, no matter your bank size, location or business focus.

12 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Technology Overview » Temenos Banking Architecture

What you see here is a simple architecture diagram to understand Temenos Architecture. Within the Temenos Banking
Cloud, clients can find all our solutions broken down into granular capabilities that they can choose to take as complete
solutions, or as individual pieces to run within their own ecosystem. This is Composable banking. Let us understand
Composable Banking by referring to the Temenos Banking Architecture shown here in this slide. Manufacturing Services is
where you have your Core Banking capabilities such as Temenos Transact Core Banking system that allows you to run the
business such as Accounts, Lending, and Deposits or it could be your Payment System running Payments related services
such as Temenos Payment Hub. Distribution services are all about how you sell, how you market, and how you service those
Manufacturing Products and services. In Temenos, we distribute the Manufacturing Services through Temenos Infinity via
Channels that cover Banking on Wealth, Retail, Corporate, and SME Banking. Open API has become the standard of
collaboration and shared information between financial ecosystems that allows customers to integrate better internal
systems, cost savings and a better position to evolve business solutions. So how do the Manufacturing and Distribution
services integrate and communicate with Enterprise APIs? Temenos Transact is enriched with a broad variety of
functionalities such as Retail banking, Corporate Banking, and Wealth Banking. Here not only do you have rich functionality,
but you can also deploy them separately or compose them together. The idea of Composed Banking services has been
around for a while. This is not just composed around the Periphery components, but this is building up the real essence of
the solution itself. So you can pick up the building blocks of Banking capabilities from Temenos Transact – you can select
from a variety of Banking domains. Each of these capabilities knows where it runs and where it gets its data , ’
loosely coupled and it is not bi-directional. This is not just our Temenos Software, you can also plug in Temenos Exchange
Partners into the ecosystem. These are all capabilities composed up and can also be extended out using the Extensibility
Framework. Apart from Temenos Transact and Temenos Infinity, you could also select other Temenos Banking Services that
provide new, discrete, packaged services that can be turned on and launched without the need for a larger project. Temenos
Banking Services also provides functionalities such as Analytics, Explainable Artificial Intelligence, Financial Crime Mitigation,
and Funds Administration.

13 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

14 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Technology Overview » Key Characteristics

Temenos provides market-leading software and service solutions to banks and financial institutions in all sectors and of all
W ’
have become cloud-native and cloud-agnostic. This means that they can be provisioned, either by Temenos as SaaS or by
banks directly, on all of the major cloud platforms. Because the software runs natively on the cloud platforms, it takes
advantage of the automatic scaling capabilities available, as well as ensuring ’
and resilience capabilities which come from running in the cloud. The software solutions can be delivered as SaaS or, if
required, on the cloud or on-premise for banks to manage themselves. This is achieved by means of Temenos continuing to
invest in technology, particularly focusing on a series of key areas: Cloud-native, Cloud-agnostic Platform: Designed for the
new digital banking age, our software allows faster updates, quick provisioning, lower infrastructure costs, elastic scaling,
resilience and security. This is built using API-first and DevOps principles and engineered to deploy in containers and
Microservices. Containerization and Microservice Framework: Temenos utilizes containerization to accelerate cloud
adoption, delivering efficient scalability built around a containerized deployment model. Temenos transforms banking
capabilities by breaking down the software into independently scalable Microservices that can be deployed rapidly, enabling
you to make high-impact changes frequently, predictably and seamlessly. Rest APIs: APIs enable financial institutions to use
standardized integration patterns to reduce the cost and complexity of user interface development and system integration.
They are the foundation for building an ecosystem of applications that the most successful banks leverage to innovate faster
and at a lower cost. Temenos Transact is built and delivered on an API-first basis. Extensibility Framework: Temenos APIs
and Extensibility Framework offer customer-driven solutions and extensions to integrate Transact with a wide range of
internal or external systems, thus stimulating faster product and service innovations. In simple terms, Extensibility Framework
enables the developer to extend or customize the Temenos product solutions, for their specific business requirements.
Explainable Artificial Intelligence: AI empowers banks to provide individualized, frictionless customer experiences, drive
customer loyalty and profitability, and automate processes. Our goal at Temenos is to build and enable AI capabilities into
our Banking platform to support these objectives and make our banking solutions smarter, faster and with a lower total cost
of ownership. Temenos is the first to bring transparency and explainability of AI automated decision-making to the banking
’ ( )
; ‘ ’ offering little if any discernible insight into how they reach
their decisions. Event Streaming, Embedded Analytics: Typically, banks have relied on vendor-specialized experts to develop
complex coded interfaces between all of their systems. This approach, called point-to-point integration, is complex, lengthy
’ ,
competitive and profitable. It allows for the codeless definition of the events, payload and enrichments, including the
definition of inward requests for all Transact functional areas, data enrichment, and the definition and delivery of events to
modern streaming and messaging platforms. Continuous Integration and Deployment: With Continuous Deployment,
Temenos has industrialized development and testing services delivered in two service modules: Extend, where users can
provision environments on demand quickly, and perform configuration tasks, and; Assemble, where users can consolidate,
test and triage configuration activities. These streamlined functions allow banks to commence their cloud journey at any
point in their software development lifecycle. Temenos Continuous Deployment is complemented by the Temenos
Workbench. This enables banks to accelerate their DevOps capabilities and adapt their Temenos Transact better, faster, and
more frequently, with Temenos Workbench. Temenos Workbench supports the Software Development Lifecycle (SDLC) and
your DevOps capabilities, providing a single entry tool to configure Temenos Transact modules with easy-to-use, intuitive
and consistent tooling. It provides an embedded packaging facility to promote changes from your development environment
all the way up to production.

15 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

16 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Technology Overview » Bunch of Technologies

What you see here is the list of software that will be used as part of Temenos Software implementation. Deployment: As we
have discussed earlier, in terms of deployment, you can either deploy Temenos software on the Cloud that runs by Temenos
or by the client themselves or it could be a traditional On-premise deployment. Database: Temenos Software supports
Database agnostic – you can go for a wide range of supported SQL databases such as Oracle, SQL Server, PostgreSQL and
NoSQL databases (mainly used in some of the Microservices) such as Mongo DB, Azure Cosmos DB. Integration: Integration
between systems is supported via Open API, SOAP, and Enterprise Service Bus(IIB, Biztalk, Mule, OSB). You can perform
Camel routing, and also it supports Event streaming platforms such as Kafka, and Kinesis. DevOps and Extensibility: Temenos
enables banks to accelerate their DevOps capabilities and adapt their Temenos Transact better, faster, and more frequently,
with Temenos Workbench. Temenos Workbench supports the Software Development Lifecycle (SDLC) and your DevOps
capabilities, providing a single-entry tool to configure Temenos Transact modules with easy-to-use, intuitive, and consistent
tooling. Security: Temenos Security Framework provides secure, consistent identification, authentication, and access control
’ -open standards. In terms of Security Authentication, you can
use OpenId, SAML and for authorization – XACML is being supported. Ecosystem: Basecamp allows you to explore, learn,
and develop Temenos Products and Temenos Exchange provides the capability for fintech collaboration.

17 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Technology Overview » Temenos Offers Choice

To summarize, Temenos offers a choice on who runs Temenos Software – Temenos Banking Cloud runs the software for
clients on the Cloud or the client/partner runs the software themselves on the Public / Private Cloud or it could be a traditional
On-Premise deployment. Temenos offers the below choice of Architecture - Decoupled - we have built out this platform
separating the components, introducing new components that allow you to have loosely coupled, event-driven Architecture.
Embedded – you can take the same components and the same code base and deploy them. Hybrid – can be deployed as a
Hybrid version where some components can be embedded and some decoupled. Deployments - We have done work on
major Public/Private Cloud deployments, or you could take the same Infrastructure as Code / Architecture and deploy it as
On-Premise deployment using our Cloud like deployment based on Containers, Kubernetes and we still support the
traditional Java App Server deployment. The idea of Package – Here to use the Commodity functionality that comes out of
the box or to differentiate, choose where to add value. As part of Package software, the idea is to perform continuously
upgradeable safely. We have Regional models that allow us to accelerate Tier implementations and an Extensibility
Framework for safe extensions without Impacting the underlying Temenos Banking Services.

18 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Lesson Summary
In this lesson, I described what your course is all about, and Technology Overview.

19 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework
Lesson Overview
In this lesson, I am going to describe Enterprise Framework.

20 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Overview

Let us start by describing the Temenos Enterprise Framework. What is the Framework in Technology around Transact? As
we already discussed, we have Transact as the Manufacturing System which is a Core Banking system from Temenos. Behind
the scenes, we have an Enterprise Framework that works together in order to make Transact smooth and efficient in
performance and focus mainly on Business processing We will now explore in detail what each of the listed frameworks is
used for and their key features.

21 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Design Framework » Overview

The Design Framework (DSF) provides an environment for model-driven design with their metadata to create configurations
and customizations through simple graphical models. DSF Separates design time from run-time data. The implementation
of the DeSign Framework is provided by two design products: OLD: Design Studio (based on Eclipse) is still available. NEW:
Temenos Workbench (>=R20). Composed of the Workbench itself plus the Packager. So, in short: Temenos Workbench
allows you to configure and extend Temenos Transact easily and package all your Changes in a few Clicks. It simplifies the
Configuration of our Products and helps Banks to reduce Development Time. In conjunction with the Packager, it helps
Banks to put in Place a light or advanced SDLC with ease and Standard Practices of the Market.

22 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Design Framework » SDLC

In systems engineering, information systems and software engineering, the systems development life cycle (SDLC), also
referred to as the application development life cycle, is a process of planning, creating, testing, and deploying an information
system. The systems development life cycle concept applies to a range of hardware and software configurations, as a system
can be composed of hardware only, software only, or a combination of both. What is important is to define how the bank
will: Customize and add new features to Transact. Enable developers to collaborate. Deploy customizations/new features to
target environments. Support testing methodology best practices. The diagram below shows at a high level the phases of
SDLC. Developers use Code/Data packager modules to customize Transact. Connect to a development environment.
Customize/configure in the dev environment. Update package content from the dev environment. Collaboration: Using a
Source Control (SCM) enables modern development methodology. The code is readable and mergeable. The configuration
is readable and mergeable. Deployment: Packages can be built and deployed using modern standard tooling. Build of
packages can be done with Maven (for data also with simple zip). Deployment of data packages can be done with the
command line (Maven), Rest API call, or through a web interface. All steps are automatable and can be embedded in a
DevOps toolchain.

23 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Data Framework

Data Framework aimed at stopping the Transact database from growing as transactions accrue, thereby improving
throughput. The live OLTP (Online Transaction Processing) database size is expected to reduce with DLM (Data Life Cycle
management). Over time the Data framework will separate the transactional data model optimized for OLTP from the
reporting data model optimized for OLAP (Online Analytics Processing).

24 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Data Framework » DLM

Looking at the first product, Data Lifecycle Management, we will examine the key challenges which it brings solutions for.
Firstly, and most obviously, is the size of the database. This is both the current size of the database with history, and the
incremental monthly growth. Left unmanaged, this could grow to 10s of TB in a few years for a medium to large bank. The
solution “ ” , -volatile data into a separate database, but still
allow access to that data in a Live enquiry! Next are the operational challenges around the management of such a large
database. The obvious item here is Backup and recovery timing, and the corresponding time to have the target system
operational again. By having a greatly reduced Live database size, these times are greatly reduced. Third is the database
performance. Whilst a size management product does not directly address performance, even the most advanced database
will start to exhibit performance degradation with large data volumes (without the implementation of additional hardware).
DLM aims to reverse any degradation in performance by keeping the database size managed. All these challenges can
compromise the ability of a bank to scale, and the implementation of DLM provides a single solution to these challenges.

25 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Data Framework » TDH

Transact Data Hub (TDH) is a packaged data platform solution for Temenos Transact banks to stream, transform, store,
optimise, and distribute Transact data into a variety of formats and solve numerous data-driven problems faced by banks.
Transact Data Hub provides data platform capabilities to integrate real-time data from Transact into a highly optimized (see
on the right) Operational Data Store (ODS).

26 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Platform Framework

Framework to push platform functionalities like threading, memory management, caching, locking, database pooling etc out
of Transact into the JEE server/database. Platform Framework enables the same source code to run as a native application
in Java and C called TAFJ (Temenos Application Framework Java) and TAFC (Temenos Application Framework C).

,
, , , ,

27 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Platform Framework » TAFJ

Platform TAFJ was built for the middleware and database that underpin the other frameworks. TAFJ is the abstract layer
between Transact, Operating System and the Database. TAFJ: Maintains the cross-platform capability. Java Data Base
Connectivity (JDBC) is part of the platform Framework. Application Server is based on Java Enterprise Edition (JEE):
WebSphere, WebLogic or jBoss. Supports different databases ( , Q , Q , …)

( )

( )
W ,W
( , Q , Q ,
)

28 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Platform Framework » TAFJ

Transact Java: Transact compiled to byte-code (class file) that can run on any Java Virtual Machine (JVM) regardless of
computer architecture. Key Features of TAFJ Platform: Executing 100% inside JEE Application Server - Independent of
Hardware and Operating System. Empowers JEE Application Server capabilities and standards: Automatically benefit from
High Availability and Resilience of AppServer, performance by scaling out. Clustering; Scalability; JDBC mechanism for
database interaction. Integrated use of internal or external Message Broker - Flexibility of Message based Communication.
Use common JEE Application Server knowledge - Resources on the market, Attract your employees, Use external services.
Transact functionality totally preserved - Run the same Transact, totally transparent for the users.

( )

29 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Platform Framework » Common Components

Platform Framework provides Common Components: These Common Components are not only for Transact but also for all
the other Temenos Products. These Common Components can be re-used by any Temenos Products by linking via APIs.
Common components are very he ’ W
versioning with Common Components. Below are the Common Components that we provide as the part of Platform
Framework. Security, Health check, Distributed cache (multiple servers, cloud). Monitor: log, trace, metrics, All levels
use a Universally Unique IDentifier (UUID),
it is therefore easier to follow through all levels. Grafana dashboard to visualize and analyze. Also, possible to keep Splunk
installed.

30 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Security Framework

The primary objective of the Security Framework is to provide a secure, consistent identification, authorization and
access control across Temenos product suite based on industry open standards. Centralized administration point for access
’ ( & ) -alone product
implementations. Flexible & granular access control set-up at the attribute level. Support of role-based and attribute-based
access control, multi-tenant and cloud-native deployment.

31 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Security Framework » Authentication & Authorization

This slide summarises the main Temenos capabilities and certifications with regard to security. SCA =
Strong Customer Authentication. Security framework provides capabilities for all Temenos products to : Externalize
, ,R , ’ (Identity and Access Management). Standardize
integration for user identity and attributes through security tokens (SAML, Open ID Connect, JWT). Build access control based
on XACML(eXtensible Access Control Markup Language) open standard and standardized run-time libraries. Standard Policy
Authoring User Interface (Policy Editor) for Access control. Security Assertion Markup Language (SAML) is an open standard
that allows identity providers (IdP) to pass authorization credentials to service providers (SP). What this means is that you
can use one set of credentials to log into many different websites. OpenID Connect (OIDC) is an identity layer built on top
of the OAuth 2.0 framework. It allows third-party applications to verify the identity of the end-user and to obtain basic user
profile information. OIDC uses JSON web tokens (JWTs), which you can obtain using flows conforming to the OAuth 2.0
specifications. JSON Web Token is an Internet standard for creating data with optional signature and/or optional encryption
whose payload holds JSON that a ’
( ’ ’ ( ’
IAM)). We use HTTPS, Application Encryption, also TDE - Transparent Data Encryption and Transport Layer Security. We also
comply with GDPR – General Data Protection Rules. Some of the certifications we have, mainly for our Cloud solution, are
listed.

&

32 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Security Framework » PAPUI Editor

What you see here is the Design time tool of Security Framework - The Policy editor. PAP-UI stands for Policy Administration
Point User Interface. PAP-UI is an interactive GUI that can be used by the security policy administrator to create/edit the
XACML policies.

33 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Integration Vs Interaction

Integration, as you can see above, involves communication between two resource managers or servers, as opposed to
interaction which involves communication between a user agent and a resource manager.

34 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Integration Options

Now, let us look at the integration patterns we support. Open APIs – We have several Rest APIs available out of the box from
Temenos and are consumed by Channels and other real-time systems. They adhere to standard OAS specifications. Event-
driven integration provides system-to-system integration near real-time with XML/JSON structured messages. Data Event
Streaming streams data to Analytics & Transact Data Hub platforms. Files – We support file-based and Message-based
interfaces for banks sending messages to us and we send them to the bank or their systems. When one uploads a file to a
secure FTP server the system will consume the file and allocate the information to the appropriate applications. Useful for
systems like Payments and Clearing. The folders in SFTP are secured with appropriate credentials for access. The SFTP server
is hosted in Temenos SaaS. Note that SFTP/FTPS Servers are very Old interfaces for file transfer and are still supported by
us. We can handle both incoming and outgoing file transfers. We use SFTP in Payments where Temenos can send/receive
messages and use the SFTP mechanism. Messaging Interfaces to other systems: The Adapter Framework enables integration
between systems. It supports bulking, debulking, API to Event and Event to API options. Note that if some cloud providers
like Azure do not have it, then our alternative is to use VMs. We receive messages through JMS compatible, Active MQ etc.
We can also send messages outside to other systems of banks using JMS or that provided by Cloud service providers like
Azure. Based on the solutions supported, the best option will be chosen.

& &
R & &
N , ,
,
( )

( Q, )

35 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » API Framework

API framework provides a new interaction layer that enables routing of requests to resource managers for different user
agents, providing server-side mash-up and synchronous call-out capabilities. API framework has been designed to enable
user agent interaction with a REST application architecture. Enables banks to easily expose banking services to any user
interface (UI) or app. Create innovative combined services and undertake highly efficient multi-device/channel UI
management.

36 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » API Framework » REST API

What is an API? API is the acronym for Application Programming Interface, which is a software intermediary that allows two
applications to talk to each other. Each time you use an app like Facebook, send an instant message or check the weather
on your phone, you're using an API. What is REST? REST stands for Representational state transfer. It is an architectural style.
In simple words, Rules for designing an API. Why is it so popular? Because it uses HTTP Methods –which we all use for
browsers and the format can be anything like JSON, XML etc. It deals with CRUD operations like Create, Read, Update, and
Delete using HTTP methods Post, Get, Put and Delete. Can we have an example? A person walks into a bank and wants to
be a customer of the bank. Banks add him to a database where all customers are listed, and this is done using the create
N , ,“ ”
database using the Get method and then update it to add new address details using the Put method. Finally, the customer
left the bank and the bank does not want to hold his details anymore. So, we simply use the Delete method to delete the
record. What is described here by a bank officer, can be done by systems using APIs. What are the other benefits? It can
work with any format like JSON – java Script Object It can also be on any programming language and work to get data from
any database.

37 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » API Framework » Rest Structure

What does an API look like? It has a pre-defined format to exchange data. What you see on screen, is the list of all components
in the endpoint of a Temenos API. Let us deconstruct the API structure. Operation or HTTP Method– Get an existing record
or Post a new request to create a customer. HTTPs – protocol- web. Base URL- api.temenos.com. V1.0.0- Version. Party- API
Domain. Onboarding – Collection of APIs in Party Category. Customer-specific API name. Parameter - customer ID – say
100336. Payload- Response back from API- This is in JSON format.

N N R ,
N N R ,
( , ) ,
R ,
( ) ,
,
( )
R,
W N ,
N R
( ) N

38 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » API Framework » IRIS R18

An implementation of the API Framework can be found in
Interaction, Reporting & Information Services (IRIS). It Is a standalone, lightweight edition of Temenos Interaction Framework.
It communicates to Transact using Open Financial Service (OFS). It uses Java Message Service (JMS) and Message Driven
Bean (MDB). It is based on Open API.
APIs are implemented in both – Enterprise APIs and Experience APIs. IRIS APIs are also REpresentational State Transfer
(REST)ful.
(software architectural style that defines a set of constraints to be used for creating Web services).

R R
,R & (R )
R

( )

( ) ( )

R R (R )
( W )

39 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » API Framework » IRIS Architecture

IRIS R18 is a lightweight, REST standards-based solution that uses OFS message format to communicate with Temenos
Transact. This allows all Temenos Transact customers across all release versions to use this solution. The diagram provides
an overview of the solution and its components. Enterprise API: The first stage of producing the API is to create an Enterprise
API layer. This requires using Temenos Transact functionality to produce Enquiries, Versions, and Activities that are
compatible with IRIS, and using the IRIS tooling to expose them as REST APIs. IRIS builds a Java Web Application which, when
deployed, can accept REST requests from clients and communicate with Temenos Transact using appropriate connectors
(JMS or TCS for TAFC, JMS for TAFJ). Mappers – map Transact field names with API field names. Processors – identify
downstream systems, execute parallel requests, aggregate responses etc. Transformers – transform JSON to OFS and vice-
versa. Experience API: If it is required to produce an API that meets a specific standard or definition, or if fine control of the
API interface is needed, the Enterprise API generated from Temenos Transact artefacts will not match exactly. The API
Framework can produce an Experience API layer that uses Apache Camel to map from the API design or specification being
targeted to the Enterprise API. Users will see the Experience API, and internally it will make calls through the Enterprise API
to Temenos Transact. An Experience API can combine functionality of different Enterprise API endpoints and transform or
enrich values in or out of the Enterprise API. An Experience API may not be required if your architecture includes another
layer for API transformation, such as an API gateway. Connectors: Standard connectors available to connect to Temenos
Transact based on the Temenos Transact deployment (TAFC or TAFJ). Service Catalog: The Service Catalog can expose
automated documentation of your APIs alongside the API functionality itself, in the industry- (“ ”)
form. This can be enabled alongside Enterprise APIs or Experience APIs. Apache Camel: This open-source framework is used
to define REST endpoints, transform data and route messages in the Enterprise and Experience layers. The Consent
Management Microservice stores the consents received from the Third-party provider (TPP).

40 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Event Framework

Event Framework is a capability that enables the bank to (and the people performing integration for it) exploit industry
standards, skills and intuitive tools to perform event-based asynchronous Integration with Temenos Transact in a rapid and
cost-efficient manner. Event Framework allow you to deliver the data between system via Java Messaging Service or
Enterprise Service Bus.

41 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Event Framework » Overview

Let us identify the key features of Event Framework. 1. Supports asynchronous integration capabilities allowing system-to-
system linking. 2. Supports business system-to-business system integration either inbound to or outbound from Transact. 3.
Scalable inward request processing with minimal overload of the core banking system. 4. Event messages are generated
under the cover by the Event Framework, saving time and costs and significantly reducing potential errors and
inconsistencies. 5. Provides - Intuitive visual drag-and-drop integration tool: Ability to visualize anticipated enhancements -
Designer, codeless definition of the events, payload and enrichments (additional data) 6. Custom adapters for Integration.
Outbound adapter for events into Transact. Inbound adapter for events out of Transact. Other features of Event Framework.
Performance - No need for batch data extracts during the close of business (COB), as data movement happens in near-real
time, allowing customers to run with a smaller infrastructure while offering better service. Resilience: Event-driven
“ ” ; ,
Re-usability: Temenos has built a large bank of message descriptions (schemas) and transformed them into industry-
standard formats which are reusable. Lower cost of development and maintenance: We allow the codeless definition and
collection of data from Temenos. This also protects the development from underlying product changes thus reducing
maintenance costs. Scalability: The event framework relies on extremely scalable technologies, streaming or messaging
platforms supporting our event delivery. Flexibility: Change of the event collection definitions, adopting new parts of the
model banking solution in a codeless approach allowing new areas to be on-boarded at a rapid pace. Highly efficient and
guaranteed event data capture and inward request processing.

42 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Event Framework Design Time

Let us understand how you can design and emit event data using Event Framework with an example. The first step is to
define Event and Flow in Design Studio using Event Designer Plugin. 1. The Event designer is the plugin in IDE used to define
the event and the flow enrichments. Event Designer is available as a plugin for IDE-Eclipse. 2. Event Definition – The Business
transaction that will trigger the Event data to be sent outside Transact. 3. Flow Definition - The message enrichment (Event
data) to be sent out. 4. Once the definition of Event and Flow are completed, this detail has to be published to Transact, so
that the actual data can be emitted when the event occurs in an appropriate application in Transact.

43 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Event Framework Runtime

Next, carry out the action that raises the event (for example: Create a new Payment Order – PO Input). The Event framework
will emit the data that has to be sent out.

44 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Event Framework Runtime

Sending the message to a third-party system could be handled in two ways. Push the message out of Transact. Pull the
message from Transact. For Java systems, Integration Service pushes the message into a JMS queue, from where it can be
picked up by a third-party system. Alternatively, a third-party system could use a custom adapter on an Enterprise Service
Bus to pull out messages from the store and forward table. Temenos currently provides custom adapters for ESBs such as
Fiorano ESB, Oracle Service Bus, IBM Integration Bus and Microsoft Biztalk Server, Mule, TIBCO.

45 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Extensibility Framework » Overview

The main aim of the framework is to provide extensibility features for our Transact solutions, that: Provides a unified
extension mechanism for all Temenos Domains like Retail, Corporate, Payments, Wealth etc through a common Design
Configuration tool. Provides clear separation of core and extensions with independent maintenance and ownership. This
means the possibility for: Separate additional Custom Data from Core. Separate additional Custom Processing Logic from
Core. Separate any Custom Calculation Logic from Core. Our solutions are constantly evolving, and hence regular updates
and functional testing are required. The framework supports it with a simple mechanism to create, manage and deploy
packages using an embedded packager mechanism within the framework. Simplify the design and packaging with the use
of Temenos Workbench for all products.

R , ,
,W ,

46 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Extensibility Framework » Overview

Simplify configuration and customization of Temenos software without the need for complex technical expertise in order to
boost productivity for development teams and reduce time to market. Reduce configuration & development times using
Temenos tooling built and used in on-premises or Cloud. Manage environments using Infrastructure as Code (IaC) templates.
Promote changes using DevOps and APIs. Integrate using APIs and out-of-the-box adapters from the Temenos Integration
Platform as a Service (IPaaS).

47 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Extensibility Framework » How it Works

Let us understand in a simple way how the Extensibility Framework works. It provides a framework to develop around the
periphery of the system but not inside Transact. This is highlighted in the diagram shown. This means that it does not provide
any features, that impact transaction flow or Service Level Agreements of Temenos Core products and solutions. In simple
words, No Custom code is possible from the framework. Uses frameworks such as API (IRIS) and Event framework in addition
to Extensibility features and tooling such as Adapter Microservice for interfaces to legacy systems. Uses Transact Data Hub
(TDH) - Operational Data Store (ODS) for Enquiries/Reporting and is accessible via Semantic Query layer APIs. Uses Temenos
Workbench tooling for configuration/extensibility and packaging requirements.

48 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Extensibility Framework » Key Features

Here you can see the list of key features supported as the part of Extensibility Framework. Data Extensions: This is to extend
the data model to capture and expose additional custom fields. New custom tables can be created too. RegEx and Python
scripts can be used to validate and default values in IRIS API request fields and Transact User Agents. ODS- Operational Data
Store provides the ability to report the data for reporting/ Enquiry/Analytics purposes. Integration can be done using API/
Events or using Adapter Microservices. A new API can be created too. Application-specific User agents can be built using the
Low/No Code capabilities of the framework.

49 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Extensibility Framework » Key Features

What you see here is the list of features that can be configured in Temenos Workbench Profile. Transact UI: New Enquiry
creation; New Version creation; Amendment to existing version- next version; Amendment to existing version- Associated
version; Amendment to existing version- Label, tool tips, language support, etc.; Composite Screen; Tabbed Screen; UXP
Browser-based Composite Screen; Menu. Data Model: User field; User Table Reference. Security: Policy Editor. Adapters:
Create Process Steps; Create Adapters. Microservices: Configure Data Extension Mapping; Create Virtual Table. APIs: API
(IRIS) Workbench based on Fabric; Upload inventory, Generate and Download Swagger; Vocabulary; IRIS API; Microservice
API; Automatic inheritance of fields to APIs; Automatic propagation of fields to APIs; Dynamic editor based on APIs; Import
API Definition.

50 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Extensibility Framework » Adapter

Temenos Adapter Microservice provides standard adapter functionalities as services for Temenos Enterprise applications to
interface with third-party legacy systems. Adapter Microservice (MS) provides flexibility to support simple data
transformation and API execution or file operations through Camel Spring XML configurations, that is, extending existing
features just by defining this configuration. Adapter MS uses Apache Camel for routing configurations. Design time available
in Temenos Workbench to add or modify adapter configurations.

51 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Extensibility Framework » Adapter

Adapter Microservice Use cases are listed below. API to API: An API exposed from the Adapter Microservice is used to send
a request to call another API request for the incoming payload for the API. Event to API: Listen for Events and Translate each
event into the respective API Call. Debulking: External systems provide data files (CSV/JSON) in a configured directory. Read
data from the data file. Push data into the target system as API supported in the Target System. File Format: CSV/XML/JSON.
Cloud Storage Service: AWS S3, Azure File Share, Directory. Bulking: Receive data as events and batch events into a flat file.
Send Files periodically.

52 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Extensibility Framework » Use case

Let us see an example that explains how you can make use of the Extensibility Framework for custom development. During
the , “ ” N ( ) R
to verify the Tax ID of the customer and store that information to be fetched when needed. The diagram shown here
illustrates the flow of the above example. You could notice that the Extensibility Framework uses the Adapter Microservice
to talk to external systems and Virtual Table Microservice to create and store additional data(local application) as the part of
Business requirement.

53 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Enterprise Framework » Summary

Let us summarize Temenos Transact Enterprise Framework and its key attributes. Platform Framework: Use of standard JEE
App Servers and database. Extensibility Framework: Supports configuration/ extension of the service without impacting the
upgradeability of the underlying banking service. Design Framework: Enables model-driven dev & DevOps. API Framework:
Provides an open banking (API) platform. Event Framework: Supports real-time event-based messaging. Data Framework:
Reduction in live transactional DB. Manages, unlocks and extracts value from data. Security Framework: Secure your Banking
software. Security controls are present at many levels.

( )

&

R
, &

54 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Lesson Summary
In this lesson, I described Enterprise Framework.

55 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Practice
Quiz
True True Event to API ; API to API ; Bulking ; Debulking Event Framework False – Virtual Table Microservice is used to
configure and store data records of local applications.

Q
, W
, ,

56 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Architecture and User Journey

Lesson Overview
In this lesson, I am going to describe Transact Architecture and User Journey.

57 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Traditional On Premise

What you see here is a traditional On-Premise deployment of Temenos Transact Solution. Now we will discuss the detailed
components that get deployed as part of Transact Solution in On-Premise deployment. Firstly, we will discuss the Transact
UXP Browser Architecture. Secondly, we will discuss how the Transact Architecture works for BrowserWeb (Legacy Browser),
Channels such as Internet Banking solutions, Mobile banking solutions, or 3rd party solutions. Thirdly, we will discuss the
new Transact Explorer Architecture.

58 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Transact UXP Browser Architecture

What you see here is the Transact UXP Browser Architecture diagram. Let us discuss each of the components in the
Architecture diagram in detail. First, we will discuss What is User Agents?

59 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » User Agents

What is it? A User agent is any software that retrieves and presents Web content for end users or is implemented using Web
Technologies. What Role does it play? User agent is any set of screens/user interactions focused on a user role. For example,
it could be a User Interface for the end user, a customer service agent used for Customer service-related options, a Wealth
manager handling Wealth business, etc. 3. In Transact, it could be internet, mobile and human adviser banking, executing
across multiple platforms i.e., smartphones and tablets apart from the web browser.

W
W

W R

,
,

,W
W ,

60 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » UXP Browser

Now we will discuss UXP Browser and its related components.

61 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » UXP Browser

What is it? The UXP browser is a new Temenos Transact Browser based on the Temenos Connect User eXPerience technology
and the IRIS data layer. What Role does it play? Delivers a completely new look and feel. Modern three-tier architecture
‘ ’( )R (R ) n time and build separation.
Separate authentication layer.

W R

R (R )

62 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » UXP Browser Architecture

’
direct 2-tier to a 3-tier architecture. When any screen in the UXP browser reads or writes data to Temenos Transact, the
process of reading or writing data is described in this illustration: The communication between UXP Browser and IRIS R18 is
established using JSON over HTTP(S). IRIS R18 communicates with Temenos Transact using TAFJ client libraries, which
results in JDBC data calls to the database. The UXP Browser is made up of three components that are used by the application
server (that is, WebLogic, JBoss or WebSphere, etc). 1. Browser.war – Contains the Temenos Connect engine and other code
that renders the screens. 2. irf-rp-services.war, irf-t24catalog-services.war is the middle tier that connects the back-end
Transact to Browser.war. Catalog service returns the metadata for the screen design from Transact on demand initially. This
is cached in the Resource Server database and used for subsequent calls. The entire cache can be deleted, and the metadata
regenerated using a special button in UXPB. Rp-service fetches the data to be displayed. UXPB uses this data and the cached
metadata to generate the screens. Metadata that is not available in the cache is generated. 3. ResourceServer.war –
Generates display artefacts on demand (known as GoD – Generate on Demand mode) and stores them using the
ResourceServer component in a separate database (referred to as Resource Server DB (RSDB) in the diagram) to store run
time generated ifp files. It is used for caching to avoid generating each time. The database connection is configured using a
separate set of properties files. Both the UXP Browser and IRIS WAR ship with a common security module that is responsible
for user authentication. It authenticates the user against the Temenos Transact USER records. It has been engineered so that
it is easy to adapt to local Single Sign On requirements.

63 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Component Flow

Here the diagram depicts the high-level irf-t24catalog-services flow with Temenos components in the solution. The UXP
Browser (UXPB) consumes irf-t24catalog-services to retrieve the Temenos Transact artefact metadata information. Based on
that information, UXPB builds its version or enquiry user interface screens. Irf-t24catalog-services: This component uses
camel-based rest services to manage the routing of the endpoint to process the user request. The irf-t24catalog-services has
the following dependencies to communicate with Temenos Transact: irf-t24communicator: This component handles the
connectivity implementation for InMem and ejb mode available for communication. InMemory mode: The
t24communicator makes use of t24-catalogservice-tafj-provider, which has built-in session management through the OFS
source setting. EJB mode: The t24communicator makes use of ejb-connector, which is an ejb lookup client JAR developed
to communicate with EJB on the remote system. ejb-connector: EJB connector is an internal EJB lookup client component
developed by Temenos to make a communication establishment to remote EJB to access Temenos Transact data. Temenos
platform(Transact and TAFJ) helps the EJB JAR to communicate with Temenos Transact to process the user request and
provide the response.

64 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Transact Java

Next, we will discuss what are Transact Libraries.

65 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Transact Java

What is it? Transact Java (t24lib) represents the Transact Java Class files that make up the Transact business logic and
functions. Here is where the Transact application binary/library files are. They are deployed within the context of the TAFJ
environment, on the Application Server. They are also known as the Transact Pre-Compiled jars. As shown here, the Transact
Java (t24lib) code is organized module-wise and component-wise. The App server uses a static load operation to load the
components on-demand basis.

( )

66 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » TAFJ

Next, we will discuss Temenos Application Framework Java (TAFJ)

67 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » TAFJ

TAFJ (Temenos Application Framework Java) is our proprietary runtime and compiler for jBC code. It allows compiling and
running jBC programs on Java. This enables core banking to harness the full functionality of J2EE application servers like
connection pooling, threading, security, etc. TAFJ manages the connectivity on JDBC-compliant databases like Oracle,
Microsoft SQL Server, PostgreSQL and for development purposes on H2. Transact on TAFJ runs on JDK 1.8 and above.

W R

68 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Transact Database

Now, we will discuss Transact Database.

69 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Transact Database

What is it? Transact Database Server is a database layer that allows to store and retrieve the live transaction data. Transact
is database-independent and supports Oracle, SQL Server, and PostgreSQL. TAFJ manages the connectivity of databases like
Oracle, Microsoft SQL Server, and PostgreSQL.

, Q ,
Q

,
Q , Q

70 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Client Application / External Systems

Now we will talk about how Transact TAFJ architecture works for Client Application / 3rd party channel integration. The
physical deployment model may be divided into four separate layers (database, Transact JEE App Server, Message Broker,
Web Layer). Transact Libraries, TAFJ and all TEMENOS components (in blue) are part of the JEE Application Server. The
connectivity model for any client applications other than UXP Browser uses JMS Queues as shown here. We will discuss each
of these components in detail.

71 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Client Application

What is it? Client Application is a software/web application used to access Transact from a workstation. What Role does it
play? Client Application consumes the banking capabilities exposed by Transact. For example, it could be Mobile Banking,
Internet Banking, etc.

W R

, ,

72 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » JMS Queues

Next, we will discuss JMS Queues in detail.

73 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » JMS Queues

What is it? JMS (Java Messaging Service) is an API that provides the facility to create, send and read messages. JMS is also
known as a Messaging Service. What Role does it play? In Transact, the messages or requests from the Client application
such as Internet and Mobile banking are forwarded to the JMS Queue. The request/response are fetched from the JMS
Queues.

Q
W

( )
,

W R

,
Q

74 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Enterprise Resources

Next, we will discuss Enterprise Resources in detail.

75 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Enterprise Resources

What is it? TAFJEE is an Enterprise component that allows enabling interaction capabilities from external applications to
Transact. What Role does it play? TAFJEE application is the glue between client applications like Browser and Transact. It
handles incoming requests from client applications, passes them to Transact, and returns responses. The communication
model used is JMS.

R
W

W R

,
,

76 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Enterprise Resources

The main components of TAFJEE: JMS (Java Messaging Service) for handling IN and OUT queues. The JMS queues are
configured in an external JMS Server or may be configured within the jBoss server. MDB – Message Driven Bean - The MDBs
consume the requests coming to the IN queue asynchronously and in turn call a local or remote EJB. EJB – Enterprise Java
Bean - The EJB acts as an interface to Transact libraries and calls the related Transact library for processing the request and
returns the response. Every JMS queue configured has a corresponding MDB. The MDBs and EJBs are deployed in the EJB
Container.

R
( ) N

77 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Enterprise Resources

There are three types of channels configured. 1. A JMS Request/Reply Channel – has both an IN and OUT JMS queue. This is
used by message sources like BrowserWeb, InteractionAPI, TWS, CALL@ and SEAT injections. 2. Phantom Request Channel
– N‘ ’ ( ) –
Uses a topic (publisher-subscriber messaging model) and not a queue. The TEC Events published to the associated topic are
broadcast to all third-party clients subscribed to this topic.

W
,
Q W ,
,

78 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Inside J2EE Application Server

Just to understand inside JEE Application Server with the diagram shown here. Going further, looking at the architectural
diagram shown, for each channel, TAFJ-EE application uses IN & OUT JMS queues. The Message Driven Beans(MDB) are
’ n calls a local or
remote Enterprise Java Bean (EJB). The EJB acts as an interface to Transact. When EJB passes the message request to
Transact, Transact processes the request and returns the response. The responses are posted on the JMS OUT queue. The
TAFJ EE application also allows to execute a request directly on the runtime for e.g. tRun START.TSM. However, for such, a
special JMS Exec queue onto which such a request is placed and is picked up by an MDB. The request is executed as a
background thread. The JMS Exec queue does not have an associated EJB as the request is executed by the runtime. To
perform a Transact deployment on an Application Server using TAFJ as the runtime, it is necessary to first understand the
TAFEE architecture flow. Requests to Transact can come from various sources or user (client) agents (message source).
From the message source, the request is created and dropped to the IN queue of the JMS. The MDBs consume the requests
coming to the IN queue asynchronously and in turn calls a local or remote EJB. The EJB acts as an interface to Transact
libraries and calls the related Transact library for processing the request and returns the response. The responses are posted
on the JMS OUT queue. The TAFJ EE application also allows you to execute a request directly on the runtime for example
using tRun START.TSM. There is a special JMS Exec queue onto which such a request is placed and is picked up by an MDB.
The request is executed as a background thread. The JMS Exec queue does not have an associated EJB as the request is
executed by the runtime. The TAFJ EE application also provides an entry point to make a synchronous call to the EJB.

79 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Transact Architecture

Transact Explorer is a new Browser released as the part of R23 AMR release. The Key features of Transact Explorer are:
Lightweight deployment and scalable architecture. Supports both auto-generated and hand-crafted screens. Provides
Customizable settings and layouts. Integrated with Keycloak for Authentication. Enables External Authentication using
XACML. Transact Explorer supports two types of Architecture: Queue-less Architecture. Queue Architecture. Let us discuss
each Architecture in detail.

R R

Q
Q

80 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Queue-less Transact Explorer Architecture

The diagram shown here represents the Queue-less Architecture of Transact Explorer. Let us describe the key components
and the message flow.

81 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Transact Explorer

What is it? Transact Explorer is a new Browser developed with Angular Framework using web components and UUX under
the hood. What Role does it play? Transact Explorer includes UI components and configurations to render the screen. It
comes along with readymade UI components for faster and customized screen development. UI Components include a Login
Component, Menu Component, Query Component (Enquiry, Chart & Fast-path Enquiry), Screen Component (Application &
Version), Composite Component (COS & Tabbed screen), and Performance Component. Web Component wrapper
components for all standalone web application components.

W R

, ,Q
( , & ), ( & ),
( & ),
W

82 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » TB-Server

What is it? TB-Server includes API endpoints for Transact and their configuration. TB-Server API framework is built in Java;
What Role does it play? TB-Server API framework is built in Java; it accepts a request in JSON format, processes it via Transact
Runtime using XML format and returns responses back to UI in JSON format. Performs major operations at Transact. Supports
Queue and Queue-less architecture.

W R

; N
, R
N

Q Q

83 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Transact Explorer » Queue-less Architecture

Let us discuss how the request is processed in Transact Explorer Queue-less Architecture. Transact Explorer (UI) sends the
requests in JSON format to TB-Server. Since Transact understands the request in XML format - TB-server converts JSON
format to XML format before placing the request to Transact. Once the request is converted to XML format, it will make a
direct call to Transact using the Transact runtime component-TAFJ. Using JDBC connectivity – the data storage and retrieval
happens. The generated response will be converted back from XML format to JSON format and returned to the UI.

84 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Transact Architecture » Transact Explorer » Queue Architecture

Let us discuss how the request is processed in Transact Explorer Queue Architecture. Transact Explorer (UI) sends the
requests in JSON format to TB-Server. Since Transact understands the request in XML format - TB-server converts JSON
format to XML format before placing the request to Transact. Once the request is converted to XML format, it will execute
the API endpoints using API Framework. The request is placed in the Queue. TAFJ runtime components(TAFJEE.ear) –
Message Driven Bean(MDB) picks the request message and processes it via EJB(Enterprise Java Bean) call. Using JDBC
connectivity – the data storage and retrieval happens. The generated response will be converted back from XML format to
JSON format and returned to the UI.

85 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

User Journey » Steps to Capture New Customer

You are now familiar with Transact Architecture and key components deployed in the Transact solution. Let us briefly take
a look at a simple User Journey (using the four eyes principle) in Transact as explained in the flow here.

86 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

User Journey » Using UXP Browser

Launch Transact Browser URL - http://localhost:9089/Browser/. Provide a valid Sign On Username and Password. INPUTT
123456 And click the Login Button.

87 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

User Journey » Input Customer Record

In the Command line, enter the command CUSTOMER I F3 and hit enter key. You could see a new record has been launched
to input Customer – enter the mandatory fields Mnemonic, Short Name, Name1, Sector and Language. Click the Commit
icon to save the changes to the Transact Database.

88 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

User Journey » Save Customer Record

Customer Record is committed now. Make a note of the Customer number 190344 which will be required in authorize
process.

89 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

User Journey » Login as Another User

Login to another user using the same URL - http://localhost:9089/Browser/ Provide a valid Sign On Username and Password
provided to you. For Example, for Temenos Model bank in a local environment, you can use AUTHOR and 123456. And click
the Login Button.

90 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

User Journey » Authorize Customer Record

Enter the command CUSTOMER A 190344 and hit enter. The record will be opened in Authorize mode. Click the Authorize
button. The record should be authorized now.

91 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

User Journey » Query Customer

Using an Enquiry, you can fetch the Customer data from the Transact Database and display the Customer info in the Browser.
Enter the command ENQ CUSTOMER.DETAILS and hit enter. Provide the Customer number 190344 created in the previous
step and click on the find button. You can see the result of the Customer Enquiry.

92 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

User Journey » View Result

The customer record is displayed from the Enquiry output.

93 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

User Journey » Using Transact Explorer

Launch Transact Browser URL - http://127.0.0.1:9089/transact-explorer-wa/#/login Provide a valid Sign On Username and
Password. For example, for Temenos Model bank in a local environment, you can use INPUTT and 123456. And click the
Login Button.

94 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

User Journey » Input Customer Record

At the bottom of the screen, you can notice the Command line, enter the command CUSTOMER I F3 and hit the enter key.
Enter the mandatory fields Mnemonic, Short Name, Name1, Sector and Language. Click the Commit icon to save the changes
to the Transact Database.

95 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

User Journey » Save Customer Record

The Customer Record is committed now. Make a note of the Customer number 190346 which will be required in authorize
process.

96 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

User Journey » Login as Another User

Login to another user. Provide a valid Sign On Username and Password. For Example, for Temenos Model bank in a local
environment, you can use AUTHOR and 123456. And click the Login Button.

97 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

User Journey » Authorize Customer Record

Enter the command CUSTOMER A 190346 and hit enter. The record will be opened in the Authorize mode. Click the
Authorize button. The record should be authorized now.

98 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

User Journey » Query Customer

Using an Enquiry, you can fetch the Customer data from the Transact Database and display the Customer info in the Browser.
Enter the command ENQ CUSTOMER.DETAILS and hit enter. Provide the Customer number 190346 created in the previous
step and click on the find button. You can see the result of the Customer Enquiry.

99 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Lesson Summary
In this lesson, I described Transact Architecture and User Journey.

100 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Practice
Quiz
1. The UXP browser is a new Temenos Transact Browser based on the Temenos Connect User eXPerience technology and
the IRIS data layer 2. True 3. Irf-t24catalog-services 4. Queue Architecture and Queue-less Architecture 5. tb-server

Q
W
R R N ( )

N
N N
R

101 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Glossary
Glossary » Acronyms

R R

R ,R &

W W

102 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Glossary » Acronyms

W W

N N

103 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

Glossary » Acronyms

W NW

R R

104 ©2023 Temenos Headquarters SA - all rights reserved

Transact Architecture Overview TR1PRARC - R23 Revision 1 English

105 ©2023 Temenos Headquarters SA - all rights reserved