You are on page 1of 49

1

2
3

Supermarket, buy what you need

It means that Bank can pick and choose the banking modules they need based on their
business requirements. For example Bank A can begin to use the Forex and Money
Market modules and 2 years later activate the Securities and Asset Management
module as per the business offering evolution.

6
7
8
9
10
11
12
13

Supermarket, buy what you need

It means that Bank can pick and choose the banking modules they need based on their
business requirements. For example Bank A can begin to use the Forex and Money
Market modules and 2 years later activate the Securities and Asset Management
module as per the business offering evolution.

15
16
17
18
19
TOCF = HTTP, Queue, WS
Interaction Framework = HTTP, Queue, WS + OData
21
22
23
24
25
26
28
=============
= PRESENTATION =
=============

This layer contains all the user interfaces connecting to T24.
Mainly T24 User Interface (T24 Browser or NEO), T24 Internet Banking, T24 Mobile Banking, or any third party user interface
based on the Interaction Framework.

========
= DESIGN =
========

Allow the design to be separate from T24 (eg Eclipse or Visual Studio). Offer
repository management including Source Control Management (Versioning) via 3
rd

party. Allow to deploy and maintain ModelBank more efficiently. Provide to Bank a
very professional solution for versioning and control management (via 3
rd
party).

T24 Global Design : T24 screen design, T24 Query Design etc.
T24 Product Design : T24 banking product parameter design. This is for AA Product Catalogue maintenance.
T24 Event Design : Design time for defining integration event. This is based on the Integration Framework
T24 WebService Design : Design time for defining and generating WebServices (current TWS solution via Eclipse or Visual
Studio)
T24 Workflow Design : Design time for defining BPMN Workflow. This is a graphical modeling tool based on
Eclipse. (current PW Designer solution)

==========
= EXTERNAL =
==========

Service
--------
3
rd
party WebService consumed by the Interaction Framework.

Program :
----------
Program part of a 3
rd
party txn
(When we have fully componentized, every component will have public and private interfaces. The public interfaces will be the
guaranteed programming interface for the product. We will no longer have a common area and there will be no more
programming by side effect.)

Access :
--------
When events are directly delivered to an ESB adapter (BizTalk adapter, Jboss ESB adapter, WebSphere Message Broker adapter,
Oracle AIA adapter) or queues (with 2PC). This is based on the Integration Framework.
Note: Events are delivered to an adapter for getting events OUT of T24. OFS or
component interfaces can be used to get events IN.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
-----------------------------
====================
= INTERACTION FRAMEWORK =
====================

Objective : to provide channels and to enable a single UI to mash up several systems at the
back end. The interaction Framework is leveraging the market standard Odata and
REST software architecture style. The Interaction Framework would perfectly fit with
an architecture where the UI logic is moved out from T24.

====================
= INTEGRATION FRAMEWORK =
====================

Objective : Integrate T24 with all other Bank systems. (synchronizing master data, getting
transaction through the value chain)
This also allows using standard market tools (ESB) for further message routing and transformation. The routing / transformation
stage transforms the event format to match with expected format of the external service.

===================
= COMPONENT FRAMEWORK =
===================

This contains the T24 Business logic executing inside an Application Server (JEE Application Server or Microsoft AppFabric)

The Component Run-Time is a container allowing to manage components. (For example : start and stop component
individually, Install/Uninstall, Inspect (look at the manifest))
28
Based on OSGi technology. (http://en.wikipedia.org/wiki/Osgi)


User replaceable component :
------------------------------------
Program part of our txn (this is an exit point in T24 implemented as a component)
(diff between both : who handles the txn)


New Banks component :
----------------------------
Bank may write (eg in Java) their own component for T24 (eg Limit) respecting our interface.


===================
= PLATFORME FRAMEWORK =
===================

Operation, Security and System Management are part of the Platform Framework. The Platform Framework objective is to
move the management of platform resources to the application server. So we would
mainly rely on the Application Server capabilities to manage those.

Security Management : we have an SSO call out to the security manager for
authentication, SSO call outs for decryption and encryption on a per message basis,
and calls to the security manager for access control each time we touch a resource.


Database Connectivity :
---------------------------
Market standard mechanism to connect to database (eg JDBC for T24 Java, the connections (pool) is handled by the JEE App.
Server)

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
---------------------------

==========
= DATABASES =
==========

Reporting :
------------



Transaction :
---------------
This database store all the transaction data (read-only).
New advantage : the Database being smaller can be moved in memory where we can expect dramatic performance
improvement (approx 10-20x times)

Design :
---------
The design time is also storing its design data on a database. T24 rely on the 3
rd
party Source Control Management repository
for this.





28
29
TOCF = HTTP, Queue, WS
Interaction Framework = HTTP, Queue, WS + OData
31
The step 6 facilitate 3
rd
party design time by knowing what kind of T24 event messaging are available for exposure. (eg by
BizTalk)
32
The step 6 facilitate 3
rd
party design time by knowing what kind of T24 event messaging are available for exposure. (eg by
BizTalk)
33
The business transaction (txn 1) only deals with a single resource manager (RM) (the database) so this is a local transaction with
a one phase commit. The integration transaction (txn 2) deals with two resource managers (the database and the queue) so this
is a distributed or XA or two phase commit transaction (these all mean the same thing). Hope that helps explain.
34
35
36
R15 Architecture (Plan)


===================
= COMPONENT FRAMEWORK =
===================

In R15, the Component Framework should allow managing any kind of TEMENOS components (T24, TAP, WealthManager, AML etc..) for
transaction or reporting purpose as well as 3
rd
party components. Note that OFS and the Integration Framework should be componentized and fully
taking part of the Component Framework.



---------------------------------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------
==========
= DATABASES =
==========
In R15 we plan a separation of transactions data (OLTP) from reporting data (OLAP)


OLAP :
-------
This is the new R15 database dedicated for Reporting and BI analysis


OLTP :
---------
In R15, this OLTP database is storing only transactions. This database is expected to be used in memory to improve
dramatically performance.


Design :
---------
This is the design time data coming from the Global TEMENOS Design including Event definition, TWS or PW GUI design
time .







36
37
38
39
T24 Java: T24 compiled to byte-code (class file) that can run on any Java
Virtual Machine (JVM) regardless of computer architecture)

41
TAFJ : Empowers JEE Application Server capabilities
===============================

Main message :

- T24 is performing 100% inside standard JEE Application Server.
- T24 benefits of direct and standard JDBC mechanism to connect to database.
- All T24 functionalities fully available and running in pure java.

Slide description (bottom to top)

DATABASE
======
- T24 is still database independent and supports , Oracle, DB2, SQL Server and jBASE. The main difference is that the
connections (pool) is handled by the JEE App. Server

JEE APPLICATION SERVER
================

- JDBC DataSource: standard and direct access to the database. (No need of Direct Connect Driver anymore.) Connection to
database are managed and maintained by the App. Server.
- TAFJ : TAFJ is the RUN-TIME of T24. TAFJ is entirely written in java and is fully EE compliant. It is making the binding
between the next layer (T24) and the App. Server.
- T24.jar : The T24 business logic resides and executes into the JEE Application Server.
- MDB : Message Driven Beans are Java EE components that are automatically woken up by the App. Server as soon as a
message is available.

Wikipedia definition :
Message Driven Beans are business objects whose execution is triggered by messages instead of by method calls. The Message
Driven Bean is used among others to provide a high level ease-of-use abstraction for the lower level JMS (Java Message Service)
specification. It may subscribe to JMS message queues or message topics, which are typically injected into the bean.

- Message Broker : The Message Broker is providing and managing messages on demand. This is the Queues container.
The Message Broker used can be internal to the App.Server or a 3
rd
party. On the physical deployment model this layer may
be separated from the T24 JEE App. Server.

The connection to the Message Broker is done using JMS.

- UI Servlet T24 Browser Servlet or ARCIB Servlet that are hosted by the Servlet Container of the App. Server. On the physical
deployment model this layer may be separated from the T24 JEE App. Server.

CLIENT LAYER
=========

This is the technology used to access T24 from a workstation. Flash or ADOBE AIR if using NEO or HTML if using T24 Browser.

Remark :

The physical deployment model may be divided in four separated layers (database, T24 JEE App. Server, Message Broker, Web
Layer). However, the idea of this slide is to underline the fact that TAFJ and all TEMENOS components (in blue) are part of the
JEE Application Server. Therefore this slide has been designed to put in the center the JEE App. Server to visually reinforce that
message.



41
42
TAFJ : Empowers JEE Application Server capabilities
===============================

Main message :

- T24 is performing 100% inside standard JEE Application Server.
- T24 benefits of direct and standard JDBC mechanism to connect to database.
- All T24 functionalities fully available and running in pure java.

Slide description (bottom to top)

DATABASE
======
- T24 is still database independent and supports , Oracle, DB2, SQL Server and jBASE. The main difference is that the
connections (pool) is handled by the JEE App. Server

JEE APPLICATION SERVER
================

- JDBC DataSource: standard and direct access to the database. (No need of Direct Connect Driver anymore.) Connection to
database are managed and maintained by the App. Server.
- TAFJ : TAFJ is the RUN-TIME of T24. TAFJ is entirely written in java and is fully EE compliant. It is making the binding
between the next layer (T24) and the App. Server.
- T24.jar : The T24 business logic resides and executes into the JEE Application Server.
- MDB : Message Driven Beans are Java EE components that are automatically woken up by the App. Server as soon as a
message is available.

Wikipedia definition :
Message Driven Beans are business objects whose execution is triggered by messages instead of by method calls. The Message
Driven Bean is used among others to provide a high level ease-of-use abstraction for the lower level JMS (Java Message Service)
specification. It may subscribe to JMS message queues or message topics, which are typically injected into the bean.

- Message Broker : The Message Broker is providing and managing messages on demand. This is the Queues container.
The Message Broker used can be internal to the App.Server or a 3
rd
party. On the physical deployment model this layer may
be separated from the T24 JEE App. Server.

The connection to the Message Broker is done using JMS.

- UI Servlet T24 Browser Servlet or ARCIB Servlet that are hosted by the Servlet Container of the App. Server. On the physical
deployment model this layer may be separated from the T24 JEE App. Server.

CLIENT LAYER
=========

This is the technology used to access T24 from a workstation. Flash or ADOBE AIR if using NEO or HTML if using T24 Browser.

Remark :

The physical deployment model may be divided in four separated layers (database, T24 JEE App. Server, Message Broker, Web
Layer). However, the idea of this slide is to underline the fact that TAFJ and all TEMENOS components (in blue) are part of the
JEE Application Server. Therefore this slide has been designed to put in the center the JEE App. Server to visually reinforce that
message.



42
T24 Java: T24 compiled to byte-code (class file) that can run on any Java
Virtual Machine (JVM) regardless of computer architecture)

T24 Java: T24 compiled to byte-code (class file) that can run on any Java
Virtual Machine (JVM) regardless of computer architecture)

45 45