Database Mapping and Deployment Changes
This section details the additional datasources that are provided by the application server hosting the deployment to provide access to each tenant databases.
A multitenant JEE deployment is similar to a standard deployment apart from the databases access made by Temenos Transact – TAFJ. Since each tenant is making use of its own database, the application server hosting the deployment needs to define additional datasources to provide access to each tenant databases.
The usual regular Temenos Transact datasources are used by the master database to run management operations and host the system configuration. This master database is not used to run any Temenos Transact business operations.
The tenant specific database or JNDI datasources mapping is done at tenant definition level through tenant compliant properties. For more information, see About Tenant Definition.
This configuration mapping allows the TAFJEE deployment to be tenant agnostic.
Default Database Mapping
By default, when you create a tenant, a default datasources mapping is created in the following pattern:
temn.tafj.appserver.tenant.t24.datasource.prefix-tenantId temn.tafj.appserver.tenant.t24.notx.datasource.prefix-tenantId
Where the master configuration defines default prefixes for the JNDI mappings with the help of properties.
These default mappings can be changed in case of need. The default mapping is made to work with default Temenos Transact or TAFJ JBoss EAP – Wildfly deployment.
| temn.tafj.appserver.tenant.t24.datasource.prefix |
java:/jdbc/t24DS- |
|
temn.tafj.appserver.tenant.t24.notx.datasource.prefix |
java:/jdbc/t24LockingDS- |
After creation of tenant, the tenant ID is appended to the default prefix.
|
temn.tafj.appserver.t24.datasource |
java:/jdbc/t24DS-tenantId |
|
temn.tafj.appserver.t24.notx.datasource |
java:/jdbc/t24LockingDS-tenantId |
Creating Datasources
Datasources for the added tenants should be created to allow each tenant to access its database. For more information on how to create datasources, see TAFJ application server documentation.
JBoss – WildFly CLI Command
The example below shows the usage of scripting and allows creating the main datasources for a tenant identified with tenant ID tenant1. The jndi-name should match with tenant1 definition temn.tafj.appserver.t24.datasource and temn.tafj.appserver.t24.notx.datasource.
/subsystem=datasources/data-source="t24DS-tenant1":add(jta="true",use-ccm="true",use-java-context="true",enabled="true",jndi-name="java:/jdbc/t24DS-tenant1",max-pool-size=220,min-pool-size=5,flush-strategy="FailingConnectionOnly",driver-name="${env.DB_DRIVER}",connection-url="${env.DB_URL_T1}",user-name="${env.DB_USERNAME_T1}",password="${env.DB_PASSWORD_T1}")
/subsystem=datasources/data-source="t24LockingDS-tenant1":add(jta="false",use-ccm="true",use-java-context="true",enabled="true",jndi-name="java:/jdbc/t24LockingDS-tenant1",max-pool-size=220,min-pool-size=5,flush-strategy="FailingConnectionOnly",driver-name="${env.DB_DRIVER}",connection-url="${env.DB_URL_T1}",user-name="${env.DB_USERNAME_T1}",password="${env.DB_PASSWORD_T1}")
In this topic