Overview

This section helps you to get familiar with the key TAFJ multitenant concepts.

In TAFJ multitenant architecture, all participants or tenants share same application server resources and Temenos Transact or TAFJ code base but use separated databases and configurations. JMS resources are shared and do not differ from a regular deployment.

A common master database is used for Temenos Transact – TAFJ configuration. This database is not used for business purpose.

The multitenant mode must be enabled through specific configuration parameters.

Once the application is switched to multitenant mode, tenants participant can be defined and execute Temenos Transact operations, targeting their own separate database and eventually local code.

The below diagram shows the TAFJ multitenant architecture: